Adding BNPL to UAE and GCC Online Stores: Tabby vs Tamara, and Where Stripe Fits

If you sell online in the UAE or wider GCC, the question is no longer whether to offer Buy Now, Pay Later, but which providers to wire in and how cleanly they sit inside your checkout. Tabby and Tamara have become near-default expectations at Gulf checkouts, and shoppers increasingly abandon carts that do not show them. The hard part is not the marketing case for BNPL, it is the engineering: making instalments, cards, and wallets coexist in one checkout that settles correctly, handles refunds, and does not buckle under Arabic, RTL, and multi-currency.

This is a build decision, and it is what we do. Karve integrates BNPL and card payments into Shopify and fully headless storefronts for Gulf businesses, so the rest of this piece is about the choices that actually matter at implementation time, not a vendor brochure.

Why BNPL is now table stakes in the Gulf

BNPL adoption in the region has moved from novelty to habit. Market reports put the UAE BNPL market at roughly USD 2.8 billion in 2025, with forecasts pushing it toward USD 4.8 billion by 2030. Tabby, which started in the UAE, reports more than 15 million users and over 40,000 merchants across Saudi Arabia, the UAE, and Kuwait, and raised at a 3.3 billion dollar valuation in early 2025. Tamara, founded in Riyadh, crossed a one billion dollar valuation off the back of Saudi demand. Those are not fringe numbers, and they explain why Gulf shoppers now expect to see at least one of these options at checkout.

There is a structural reason BNPL fits the region specifically. Both Tabby and Tamara are interest-free to the shopper and aligned with Sharia principles, which removes the friction that conventional credit carries for a large share of Gulf consumers. The shopper splits the bill at no extra cost; the merchant pays a commission and, in the typical arrangement, receives the full order value upfront while the provider carries the repayment risk and settles to the merchant on an agreed cadence.

Tabby vs Tamara: what the difference means for your build

For most catalogues the two providers overlap heavily, and plenty of Gulf stores run both. The distinction that matters is product shape and market centre of gravity. Tabby is best known for a Pay in 4 style split and has its roots and largest brand recognition in the UAE. Tamara offers a pay-within-30-days option alongside instalment splits, and its strongest pull is in Saudi Arabia, where it originated. If your demand is weighted toward KSA, Tamara tends to be non-negotiable; if you are UAE-first, Tabby is usually the anchor. Running both is common, and the only real cost of doing so is checkout clutter if it is not designed deliberately.

When to add which

• UAE-first store, mid-range basket: lead with Tabby, add Tamara if you see meaningful Saudi traffic.
• Saudi-first or cross-GCC store: Tamara is the priority integration, with Tabby alongside for UAE and Kuwait coverage.
• Higher-value baskets (furniture, electronics, beauty bundles): instalment splits matter most here, because that is where the affordability nudge changes the buy decision.
• Both providers operate across UAE, Saudi Arabia, Kuwait, and Bahrain, and settle in local currency, so multi-currency handling is a build requirement, not an afterthought.

Where Stripe fits: the card layer underneath BNPL

BNPL is not a replacement for cards, it is a layer on top of them. A meaningful share of Gulf checkouts still complete on Visa, Mastercard, Apple Pay, or Google Pay, and those need a robust processor behind them. In the UAE, Stripe supports Visa, Mastercard, Apple Pay, Google Pay, and Link, charges around 3.5 percent per successful transaction with an additional fee on international cards, and settles in AED. The right mental model is that Stripe handles the conventional card-and-wallet rail while Tabby and Tamara handle the split-payment rail, and a well-built checkout presents all of them without the shopper feeling they are choosing between competing systems.

This matters for headless builds in particular. If you are running a custom storefront, Stripe gives you the most control over the card flow, including Apple Pay and Google Pay buttons, saved cards, and 3D Secure, while BNPL providers slot in as additional payment methods. Getting the orchestration right, so that one cart can route to the correct rail and reconcile cleanly, is the engineering work that separates a checkout that converts from one that quietly leaks orders.

The conversion and AOV case, honestly stated

The reason merchants add BNPL is commercial, and the published evidence is consistent even if the exact figures vary by source and category. Providers and independent studies report average order value lifts in the region of 20 to 40 percent when instalments are offered, with the strongest effect on higher-consideration purchases, and conversion improvements driven mainly by reduced checkout abandonment. Treat these as directional rather than guaranteed; the lift is real, but it depends on your category, your basket size, and whether the BNPL option is visible early, ideally on the product page, not buried at the final step.

That visibility point is an implementation detail with revenue consequences. Showing the instalment breakdown on the product page, in the cart, and at checkout is what converts the affordability message into a completed order. It is also where a lot of off-the-shelf integrations fall short, because the widgets are bolted on rather than designed into the page.

How Karve integrates BNPL into Shopify and headless storefronts

On Shopify, Tabby and Tamara both ship official apps, and the basic install is straightforward: connect the app, enter the API keys from the provider portal, and the payment option appears. The work we add is making it correct rather than merely present: positioning instalment messaging on product and cart pages, handling AED and SAR correctly, making sure the Arabic and RTL versions render the widgets properly, and confirming refunds and partial captures behave as expected before anything goes live. Shopify also has known constraints around processing payments in the UAE, so part of our job is choosing the right gateway and BNPL combination for the specific market rather than assuming the default works.

On headless and custom builds, BNPL stops being a plugin and becomes an API integration. Tabby and Tamara expose APIs for creating sessions, capturing payments, and handling webhooks, and we wire those into the storefront and the order backend directly. In a typical headless stack we run a Next.js front end against a commerce backend, with Stripe handling cards and wallets and Tabby and Tamara added as first-class payment methods through their APIs. The deliverable is a single checkout where the shopper sees cards, wallets, and instalments side by side, every method settles to the right place, and webhooks keep the order state honest even when a customer drops off mid-flow.

We have shipped Shopify and headless commerce for Gulf brands across exactly this terrain, including beauty and automotive retail, where multi-currency, Arabic-first content, and a clean payments mix are non-negotiable. The pattern is always the same: get the data model and currency handling right first, then make the payment methods feel native to the storefront rather than stapled on.

What to decide before you build

• Which markets you are actually selling into, because that decides Tabby, Tamara, or both, and which currencies your checkout must settle in.
• Whether you are on Shopify or going headless, since that changes BNPL from an app install to an API integration and changes how much control you have over the checkout.
• Where instalment messaging appears, because product-page and cart visibility is what drives the AOV lift, not a logo at the final step.
• How refunds, partial captures, and webhook reconciliation are handled, because that is where unmanaged integrations break in production.

BNPL in the Gulf is no longer a question of if, it is a question of which providers, which markets, and how cleanly they sit in your checkout alongside cards. If you are choosing a build partner to get that right for a UAE or GCC store, that is the work Karve does day to day.