Bagisto Gets a BNPL Option: What Tabby Integration Means for Regional Stores

Last updated: October 7, 2026

A new payment module is now available for Bagisto stores operating in the Gulf region. The Bagisto Tabby Payment Gateway lets merchants offer customers the option to split purchases into four interest-free installments at checkout, using Tabby's buy-now-pay-later (BNPL) service. The module arrived as a downloadable extension from Webkul, with full configuration handled through the Bagisto admin panel.

The integration targets stores working in UAE dirham (AED) and serving customers with GCC-issued debit or credit cards, including those on the MADA network. Merchants can toggle the payment method on or off, customize its display text, and switch between sandbox testing and live production environments without reinstalling anything.

How the Module Works

At its core, the Bagisto Tabby Payment Gateway adds Tabby's BNPL flow alongside existing payment options. When a shopper reaches checkout, they can choose to pay in four equal installments instead of covering the full amount upfront. The payments are interest-free, subject to Tabby's approval criteria.

The admin side gives store managers several levers. They can set a custom title and description for how the payment method appears during checkout. They enter their Tabby merchant code and API keys, with separate fields for sandbox credentials used during testing and live keys for actual transactions. A sort order field lets merchants position the option relative to other payment methods on the page.

Refunds can be initiated from either the Tabby dashboard or directly within Bagisto's admin panel. This matters for stores that already handle returns through their own backend and do not want to switch systems for Tabby orders.

Developer Setup Overview

Installing the module requires merging package files into a Bagisto installation, then adding the service provider to the bootstrap configuration. Developers also update the Vite build configuration and run a series of artisan commands to publish assets and run migrations. The process is straightforward for anyone familiar with Bagisto extension development, but it does involve touching multiple configuration files.

The module automatically registers webhooks for both sandbox and production environments. This means payment status updates arrive asynchronously rather than requiring the store to poll Tabby's API continuously. Order history is sent to Tabby as part of the approval process, letting the BNPL provider assess buyer risk in real time.

Promotional widgets can appear on product pages and the cart, showing customers how much each installment would be before they commit to buying. A TabbyCard widget displays at the final checkout step, reinforcing the payment timeline.

Our Analysis

For Bagisto stores serving the GCC, adding Tabby fills a gap that generic payment gateways like Stripe or PayPal do not address with a built-in installment flow. The regional specificity is the module's defining characteristic: it works only in AED and only with GCC-issued cards. This is not a global solution. It is a targeted tool for stores whose customer base is concentrated in the UAE and neighboring countries.

The four-installment structure addresses a specific checkout friction point—customers who hesitate at large upfront costs. Whether that translates to measurable business outcomes depends on factors outside this module's control: customer demographics, product margins, and Tabby's fee structure. Merchants should treat these variables as unknowns to clarify before committing.

For developers evaluating the integration, the technical footprint is modest. The setup touches several configuration files, but the webhook architecture removes the need for continuous API polling. That said, stores already running complex payment stacks may want to assess whether adding a third-party BNPL provider complicates reconciliation.

Who Should Care

Consider this module if:

• Your store processes payments exclusively or primarily in AED
• Your customer base consists predominantly of GCC cardholders
• Your product catalog includes items where the price point creates checkout hesitation
• You want refund flexibility across both Bagisto and Tabby dashboards

Look elsewhere if:

• You accept multiple currencies beyond AED
• Your customer base is international or uses non-GCC cards
• Your margins cannot absorb additional payment processing fees
• You prefer avoiding third-party BNPL dependencies

What to Watch Next

Before going live, confirm Tabby's merchant fee structure. That number will factor into whether the integration makes financial sense for your store. Also monitor whether Tabby expands to other GCC currencies or markets, which would broaden the module's applicability beyond its current scope.

Key takeaways

• The Bagisto Tabby module adds interest-free, four-installment payments for stores using AED and serving GCC customers.
• Configuration happens entirely within Bagisto's admin panel, with separate sandbox and production credential fields.
• Refunds can be processed through either Tabby's dashboard or Bagisto's admin, giving merchants flexibility.
• The module targets a specific regional market and does not support other currencies or card types out of the box.
• Evaluate Tabby's fees against your margins before committing—the module's value depends on your specific economics.