Payment Gateway Integration Dubai: Tabby, Tamara, Stripe & More

Plexi integrates the full UAE payment stack into Shopify, WooCommerce, Magento, and custom e-commerce stores — including Tabby and Tamara BNPL, Stripe, PayTabs, Telr, Network International, and cash on delivery with deposit logic. The right payment mix at checkout is one of the highest-leverage conversion levers for any UAE online store.

Why UAE payment integration is not a plug-and-play task

Every payment gateway claims a five-minute install. In practice, UAE e-commerce payment integration requires careful configuration that default setups miss:

BNPL display placement. Tabby and Tamara convert better when the monthly instalment amount is visible on the product page and the cart, not just at checkout. The plugin installs the checkout widget; surfacing instalment messaging on PDPs and in cart summaries requires theme-level work.

COD with deposit. A blanket COD option with no deposit capability exposes merchants to high order abandonment and fraud loss on big-ticket items. We configure COD rules by order value threshold and product category, with optional deposit collection at checkout for high-risk orders.

3DS2 and local card behaviour. UAE cardholders expect 3D Secure authentication. Gateways that do not handle 3DS2 correctly produce abandoned checkouts when the bank OTP flow breaks. We test every gateway integration through the full 3DS2 flow on UAE-issued cards before launch.

Multi-gateway fallback. High-volume stores benefit from routing card transactions across two gateways by product category or cart value to minimise downtime risk during gateway outages.

UAE payment gateways we integrate

Tabby

Tabby is one of the UAE’s most widely used BNPL platforms. Shoppers split the order into 4 equal instalments with no interest and no fees. Integration covers:

• Checkout widget (Tabby’s hosted payment screen)
• Product page instalment widget — “Pay AED X/month with Tabby” displayed on the PDP
• Cart widget — instalment amount shown in the cart drawer or cart page
• Order minimum and maximum eligibility configuration
• Available on Shopify (official app), WooCommerce (official plugin), and Magento (official module)

Tamara

Tamara offers buy-now-pay-in-3 and pay-in-30-days options, giving UAE shoppers more flexibility than a fixed 4-instalment model. Integration follows the same scope as Tabby — checkout, PDP widget, cart widget, and eligibility rules.

Stripe

Stripe operates in the UAE with a Dubai office and settles in AED to a local bank account — a UAE-registered business can use it directly, without the offshore-entity workaround that older guides still describe. It is a strong choice for stores with international ambition or subscription billing: the same integration handles GBP, EUR, and USD alongside AED (cross-currency charges carry an FX conversion fee). It supports Apple Pay, Google Pay, and saved cards through tokenization. We configure Stripe Radar rules to reduce fraud on high-risk product categories.

PayTabs

PayTabs is a regionally licensed payment gateway with strong adoption across the UAE and GCC. Supports AED, multi-currency, and recurring billing. Official plugins available for Shopify, WooCommerce, Magento, and custom API integration.

Telr

Telr is UAE-based with CBUAE licensing. Strong choice for businesses that prefer a local gateway relationship. Supports all major card schemes, 3DS2, and Apple Pay. We use Telr for clients where a UAE-domiciled gateway is a procurement or compliance requirement.

Network International

Network International (now part of Mastercard) is the enterprise-grade gateway used by large UAE retailers and ADCB / Emirates NBD merchant accounts. Its N-Genius product is API-based and requires more development work than plug-in gateways — typically used on Magento or custom builds where volume justifies a negotiated rate.

Beyond the core gateways

No store needs the same six providers. Depending on your markets and volume we also integrate:

• Amazon Payment Services (formerly PayFort) — a regional processor with deep UAE, KSA, and Egypt coverage; a natural fit for merchants already inside the Amazon ecosystem.
• Checkout.com — a global processor with a strong MENA footprint and a direct API, used by higher-volume merchants who want granular control over routing and negotiated rates.
• Tap Payments — a single integration that spans the GCC (including Mada and KNET), useful when you sell into Saudi Arabia and Kuwait as well as the UAE.
• Mamo Business — a UAE fintech with fast onboarding and payment links, a pragmatic option for smaller catalogues and service businesses.
• Postpay — an additional UAE BNPL provider to run alongside Tabby and Tamara when a third instalment option is worth offering.

We wire the providers that fit your catalogue, average order value, and the markets you ship to — not a fixed bundle.

Cash on delivery

We configure COD as a first-class checkout option, not an afterthought:

• COD availability by product category (excluded for digital goods, high-value electronics)
• COD availability by delivery zone (available in UAE, disabled for international)
• Optional deposit at checkout (e.g. 20 % upfront, balance on delivery)
• COD fee display in the checkout if the merchant charges a handling fee

Digital wallets and local card schemes

Apple Pay is close to mandatory in the UAE — iPhone share is high, and Apple Pay express checkout strips almost every field out of the purchase, which lifts mobile conversion measurably. We enable Apple Pay and Google Pay on every gateway that supports them, and Samsung Pay where relevant. For stores selling into Saudi Arabia we also enable Mada, the Saudi domestic card scheme, which PayTabs, Telr, Tap, and Network International all support. Wallet tokens also mean returning shoppers skip re-entering card details, which shortens the highest-drop-off step in the funnel.

Matching the gateway to the store

Most comparison guides rank UAE gateways on headline fees. For an integration decision, the questions that actually shape the build are how the gateway connects, which platform plugins exist, and what it is genuinely best at. This is the practitioner view we work from:

The default UAE stack is one card gateway, both Tabby and Tamara, and COD — that covers the way the market actually pays. A second card gateway is worth adding only once volume makes outage risk and card-type approval rates matter; below that threshold it adds reconciliation overhead for little gain.

How the integration actually connects: hosted page, drop-in, or direct API

Every gateway offers one or more of three integration models, and the choice drives both the checkout experience and your PCI DSS scope:

• Hosted payment page (redirect). The shopper is sent to the gateway’s own page to enter card details, then returned to your store. Card data never touches your server, so you sit in the lightest compliance bracket. The trade-off is a redirect away from your checkout.
• Drop-in / embedded fields (iframe). Card fields sit inside your checkout but are served and secured by the gateway — Stripe Elements and PayTabs’ hosted fields work this way. The shopper stays on your page and you keep the light PCI scope. This is our default for most custom checkouts.
• Direct server-to-server API. Your server captures and forwards the raw card number. It offers the most control and the smoothest single-page flow, but it drags the whole checkout into the heaviest PCI DSS audit (SAQ D / full QSA assessment). Almost no store needs this; the compliance burden rarely pays for itself.

For the vast majority of UAE stores the right answer is a hosted page or drop-in fields plus tokenization — the gateway stores the card and returns a token, so repeat purchases and subscriptions work without you ever holding a card number.

Getting a merchant account approved in the UAE

Integration code is only half the job. The store also needs a live merchant account with each provider, and that is where launches slip. Approval hinges on a handful of things:

• A valid UAE trade licence whose activity matches what you actually sell — a mismatch is the most common rejection.
• A UAE bank account for AED settlement.
• A website with visible refund, terms, privacy, and contact pages; gateways will not approve a store that reads as unfinished.
• The correct merchant category (MCC) for your products, which also influences the rates you are offered.

Locally licensed card gateways move fastest; enterprise providers like Network International run a longer review. High-risk categories — supplements, travel, subscriptions with chargeback exposure — attract extra scrutiny. We prepare the merchant application alongside the build so approval and go-live line up, instead of a finished store sitting idle because it cannot yet take money.

Integration process

1. Gateway selection review — confirm the right combination for the business model and risk appetite
2. Developer account setup — sandbox credentials, merchant ID, and API key configuration
3. Plugin / module installation — on Shopify, WooCommerce, Magento, or custom API
4. Checkout widget configuration — BNPL display on PDP, cart, and checkout
5. Test transaction suite — successful payment, declined card, 3DS2 OTP, COD, BNPL approval and rejection flows
6. Go-live and monitoring — production keys, first-week transaction monitoring, gateway dashboard access handover

The test suite is not optional. A live store that fails silently on a Tamara decline or a 3DS2 timeout loses orders with no error message to the merchant.

What breaks after go-live — and how we build against it

Payment problems rarely show up in a demo; they show up on live traffic, at the edges. The integrations we ship are built to survive those edges rather than assume the happy path:

• Mark the order paid on the webhook, not the redirect. Shoppers close the tab before the browser redirect completes. If an order is only confirmed on return-to-store, paid orders get stuck as “pending.” We confirm payment from the gateway’s server-side webhook so status is never lost.
• Idempotent, retry-safe handling. Gateways resend webhooks and can deliver them out of order. Without idempotency keys you double-count a payment or double-fulfil an order. Every handler we write is safe to receive the same event twice.
• Refunds and partial captures. Authorising the full amount then capturing part of it — a partial shipment, an out-of-stock line — and issuing full or partial refunds are wired and tested, not left to a manual dashboard workaround.
• Reconciliation. The gateway’s settlement report, the orders in your store, and the deposits in your bank all have to agree. We map the fields so finance can reconcile at month-end instead of chasing mismatches on payout day.
• Disputes and chargebacks. A defined flow for when a customer disputes a charge — including the evidence each gateway needs — keeps recoverable revenue from being lost by default.
• 3D Secure the way UAE banks issue it. UAE-issued cards run a 3DS2 OTP challenge. We test the full challenge flow, not just the frictionless path, on real UAE cards — a broken OTP step kills conversion silently at the last click.

This is the layer generic installs skip, and it is where a store quietly leaks money without ever throwing an obvious error.

Payment integration sits inside our wider e-commerce development service, and the gateway work is the same discipline whether your store runs on Shopify or WooCommerce.

If you are launching a store or replacing a gateway setup that is quietly leaking orders, tell us three things: your platform, the gateways you run today, and your average order value and main categories — send us your current checkout and we will map the card, BNPL, and COD mix your catalogue actually needs. The pricing guide marks where a standard integration ends and multi-gateway routing or a headless checkout becomes its own scoped workstream.