Magento 2 Tabby & Tamara BNPL

Key Features

Tabby and Tamara registered as native Magento 2 gateway payment methods via the payment provider framework, wired through di.xml and config.xml

Split-in-4 and pay-later checkout options, each as an independently toggleable method with its own title, sort order, and applicable store views

Promotional BNPL messaging widgets on product and cart pages, rendered via layout XML and KnockoutJS UI components

Real-time eligibility and credit-limit checks against the Tabby/Tamara APIs so BNPL only shows for qualifying carts and amounts

Command-based gateway commands (authorize, capture, sale) with a webhook controller that confirms session status and places/cancels orders

Refunds mapped to Magento credit memos and partial captures mapped to invoice capture, posted back to the gateway for settlement parity

Multi-currency GCC support (AED, SAR, KWD, BHD, QAR and others) resolved at store-view scope

Admin configuration under system.xml with separate ACL resources for keys, environment toggle (sandbox/production), and merchant identifiers

Cron-based retry consumer for failed or delayed gateway callbacks, with full request/response logging for audit and reconciliation

Min/max order-value rules, category and customer-group restrictions, and per-method country/currency gating

Compatible with native Luma checkout, Hyvä, and PWA Studio (GraphQL payment method resolvers added when headless)

Works on Adobe Commerce and Magento Open Source, version-matched to your installation

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

This is a build-to-order Magento 2 / Adobe Commerce extension, not an instant Adobe Commerce Marketplace download. ECOSIRE develops it against your exact Magento version, theme, and checkout (native Luma, Hyvä, or PWA Studio), then installs and configures it on your environment.

The extension ships as a proper module under app/code/Ecosire/BnplGcc, registering both Tabby and Tamara as gateway payment methods through Magento's payment provider framework. Each method implements service contracts and is wired via di.xml, with config.xml defaults and a system.xml admin configuration section behind dedicated ACL resources for API keys, environment (sandbox/production), and merchant codes. Customers see split-in-4 and pay-later options at checkout; promotional messaging widgets render on product and cart pages via layout XML and UI components, calling the gateways' eligibility and credit-limit endpoints so only qualifying orders and amounts display BNPL.

Order flow is handled with command-based gateway commands (authorize, capture, sale) and a Vault-free webhook controller that confirms session status, places orders, and reconciles via sales_order_payment. Refunds and partial captures map to Magento credit memos and invoice capture, posting the matching call to Tabby/Tamara so settlement stays in sync. Multi-currency GCC support (AED, SAR, KWD, BHD, QAR, plus others the gateways enable) is driven by store-view scope. Failed callbacks retry through a cron consumer; every gateway request and response is logged for audit. Works on both Adobe Commerce and Magento Open Source. ECOSIRE handles installation, sandbox-to-production go-live, and post-launch support.

What you get

Custom Ecosire_BnplGcc module delivered as installable source under app/code (or Composer package), version-matched to your Magento 2 / Adobe Commerce release

Installation and configuration on your staging environment, including Tabby and Tamara sandbox credentials wiring

Sandbox end-to-end test pass: eligibility display, checkout, capture, refund, and partial-capture flows

Production go-live with live merchant credentials and webhook endpoint verification

Admin configuration walkthrough and a short operator guide for managing keys, environments, and method visibility

Post-launch support window with bug fixes and Magento patch-compatibility checks

Who this is for

GCC online retailer raising AOV

A Saudi or UAE store owner who wants split-in-4 and pay-later at checkout to lift average order value and conversion, matched to the payment habits of GCC shoppers.

Magento merchant on a custom or Hyvä theme

A merchant whose storefront isn't vanilla Luma and who needs BNPL widgets and checkout integration that respect their theme and don't break on the next upgrade.

Finance/operations lead needing reconciliation

An operations or finance owner who needs refunds, partial captures, and credit memos to stay perfectly in sync with Tabby/Tamara settlement reports and auditable logs.

How Magento 2 Tabby & Tamara BNPL Compares

Criterion	ECOSIRE	Custom Build	Competitor
Tabby and Tamara both integrated at Magento checkout	Included	Partial support	Partial support
Product and cart eligibility/limit widgets	Included	Partial support	Partial support
Refunds, partial captures, and credit-memo parity	Included	Partial support	Partial support
Matched to your Magento version, theme, and Hyvä/PWA checkout	Included	Included	Not included
Installed, sandbox-tested, and taken to production for you	Included	Partial support	Not included
Ongoing support and Magento patch-compatibility updates	Included	Partial support	Partial support
Available without a build/lead time (instant download)	Not included	Not included	Included

Frequently Asked Questions about Magento 2 Tabby & Tamara BNPL

How long until it's live on my store, and is this an instant download?

This is build-to-order, not an instant Adobe Commerce Marketplace download. After we confirm your Magento version, theme, and gateway accounts, a typical Tabby and Tamara integration is delivered, tested in sandbox, and taken to production in roughly 1 to 2 weeks. We share a firm lead time once scope is confirmed.

Do I need my own Tabby and Tamara merchant accounts?

Yes. You sign up directly with Tabby and Tamara to get your merchant codes and API keys for sandbox and production. We wire those credentials into the module's system.xml configuration and verify the webhook endpoints during go-live — we never resell or proxy the gateways.

What ongoing support and updates are included?

Every build includes a post-launch support window covering bug fixes and Magento security-patch compatibility checks. If Tabby or Tamara change their API or you upgrade Magento, we provide updates under a support agreement so the integration keeps working.

Will it work with my custom theme, Hyvä, or a headless PWA storefront?

Yes. The checkout UI components and product/cart widgets are built against your actual theme. For Hyvä we provide Alpine/Tailwind-compatible templates, and for PWA Studio or other headless setups we add GraphQL payment-method resolvers so BNPL appears in your custom checkout.

How are refunds and partial captures handled?

Refunds are driven by Magento credit memos and partial captures by invoice capture. Each action posts the matching call to Tabby or Tamara so order status and gateway settlement stay aligned, with every request and response logged for reconciliation.

Does it support multiple GCC currencies and stores?

Yes. Currencies such as AED, SAR, KWD, BHD, and QAR are resolved at store-view scope, so a multi-store GCC setup can present the correct BNPL options and limits per store view, subject to what your gateway accounts enable.