We’ve configured checkout for enough Shopify stores across Manama, Dubai, and Riyadh to say this with confidence: the payment gateway decision gets less attention than it deserves, and it costs merchants more revenue than almost any other setup mistake we encounter.
Most store owners treat the gateway as a formality. Pick something during setup, tick the box, move on to product photography and ads. Then three months later they’re staring at a checkout abandonment rate that doesn’t match their traffic quality, and nobody thinks to check whether Mada cards are actually being accepted properly.
This guide walks through the gateways that actually matter for Bahrain, the UAE, and Saudi Arabia, based on what we’ve installed, debugged, and occasionally ripped out and replaced for clients over the past few years.
Why Your Payment Gateway Choice Matters More in the Gulf
Shopify Payments, the platform’s native processor, does not settle in most GCC currencies and doesn’t support the local debit networks your customers actually use. That single fact changes the entire setup conversation compared to a US or UK store, where you install Shopify Payments and you’re done in ten minutes.
Here, you’re choosing a third-party gateway from day one. And that gateway has to handle a few things Western guides never mention:
National debit schemes. Mada in Saudi Arabia, Benefit in Bahrain, KNET in Kuwait. These aren’t optional extras – for a huge share of GCC shoppers, their debit card is the only card they carry, and if your gateway doesn’t route it correctly, the transaction fails at the bank level, not at Shopify’s checkout.
Currency settlement. You need SAR, AED, or BHD settlement into a local or regional bank account, not a USD account that forces you to eat FX conversion on every sale.
Apple Pay behaviour. In Saudi Arabia specifically, most Apple Pay transactions are a Mada card sitting inside the wallet, not an international Visa or Mastercard. If your gateway’s Apple Pay integration doesn’t correctly process the underlying Mada transaction, customers see a generic decline with no explanation, and you never find out why.
Buy Now, Pay Later. Tabby and Tamara aren’t a nice-to-have anymore. For fashion, beauty, and electronics stores in particular, BNPL is now a checkout expectation, not a differentiator.
Get any of these wrong and you don’t get a slow checkout. You get a customer who typed in their card details, hit pay, and watched the page fail. That customer does not come back to try again. They assume your store is broken.
The GCC Payment Landscape, in Plain Terms
Before comparing gateways, it helps to understand what you’re actually solving for in each market, because the three core countries behave differently.
Saudi Arabia is the most card-conscious of the three, largely because of Mada’s dominance. Mada is the national debit scheme, and a meaningful share of Saudi shoppers pay exclusively through it, often via Apple Pay. SAMA-regulated gateways such as HyperPay, PayTabs, and Moyasar have built their entire local reputation around getting Mada routing right. VAT in Saudi Arabia sits at 15 percent, which is worth flagging early because it affects how you configure tax display at checkout, separate from the payment gateway itself.
The UAE has the most internationally diverse customer base of the three, with a large expat population that expects the checkout experience of a Western store, alongside Emirati shoppers who favour local bank cards and, increasingly, BNPL. This is why UAE stores typically run a wider gateway stack than Saudi or Bahraini stores.
Bahrain is smaller in absolute transaction volume but has its own national infrastructure worth respecting: Benefit, the Kingdom’s national payment network, and BenefitPay, its mobile wallet. A Bahrain-based store that ignores BenefitPay is quietly excluding a chunk of local shoppers who default to it out of habit, the same way UK shoppers default to Apple Pay.
Across all three markets, cash on delivery still shows up in order data more than most founders expect, particularly outside the top two or three cities. We generally recommend keeping COD available as an option even once digital payments are solid, rather than removing it outright — it converts hesitant first-time buyers who haven’t built trust with your brand yet.
The Gateways Worth Considering
We’re not going to cover every processor that shows up in a Shopify app store search. Several regional gateways look active but have thin Shopify documentation, slow support, or no real GCC bank relationships behind them. These are the ones we’ve actually deployed on client stores and would deploy again.
Tap Payments
Tap is the gateway we default to for merchants who want one integration covering multiple GCC markets without juggling separate merchant accounts. Founded in Kuwait and now processing for tens of thousands of merchants across the region, Tap’s real strength is breadth: a single integration can accept payments across Saudi Arabia, the UAE, Kuwait, Bahrain, Oman, and Qatar.
For a Bahrain-based brand that’s about to start shipping into Saudi and the UAE — which describes a large share of our client base — that breadth removes a lot of operational overhead. You’re not managing three separate gateway relationships as you expand.
The trade-off is that Tap’s dashboard and reporting, while functional, aren’t as polished as Checkout.com’s. For a merchant doing under a few hundred thousand riyals a month, that’s a non-issue. For an enterprise operation with a finance team that lives in payment analytics, it can feel basic.
PayTabs
PayTabs is a Saudi-founded, SAMA-certified gateway built specifically for Gulf merchants, and it shows in the detail work. Mada, cross-border card acceptance, digital wallets, bank transfer, and BNPL access can sit under one contract, with next-day SAR settlement in Saudi Arabia. It integrates cleanly with Shopify and also with Salla and Zid, the Saudi-native platforms, which tells you where its engineering priorities sit.
We reach for PayTabs when a client’s primary market is Saudi Arabia and Mada reliability is the single most important requirement. Setup typically involves a modest one-time fee and can go live within a day once documentation is approved, which is faster than most enterprise alternatives.
Telr
Telr has quietly become one of the most commonly installed gateways among UAE Shopify merchants, and for good reason: it’s a low-friction, reliable default. It handles Mada, UAE-issued cards, and settlement across AED, SAR, KWD, and BHD, with fees that sit comfortably in the mid-2 percent range for local cards.
The honest downside is the merchant dashboard, which feels dated next to Checkout.com or Stripe. If your team is used to modern analytics interfaces, budget a short adjustment period. Support response times have also been reported as slower than the newer entrants. None of that changes the core recommendation: for a UAE-first store that wants something stable and well-documented, Telr remains a sound default.
Checkout.com
Checkout.com is the gateway we bring in once a store has outgrown SMB-tier processors — generally once monthly volume moves well past six figures in AED or SAR. It offers negotiable merchant discount rates, faster settlement cycles at volume, and genuinely modern APIs that make custom checkout work far less painful for our development team.
The cost is friction at the front end. Setup takes longer, onboarding requires more documentation, and account management moves at enterprise speed rather than startup speed. We don’t recommend Checkout.com to a brand doing its first hundred orders a month. We absolutely recommend it once that brand is scaling regionally and the flexibility starts paying for itself.
Amazon Payment Services (formerly PayFort)
Amazon Payment Services carries a trust signal that shouldn’t be underestimated, particularly with an older customer demographic that recognises the brand association. It performs well for stores selling across a mixed UAE and Saudi audience and has mature fraud tooling behind it. It’s a reasonable secondary or primary option depending on your customer profile, though it’s not usually our first recommendation for a brand-new store still finding its footing.
HyperPay and Moyasar
Both are SAMA-licensed and built with Saudi Arabia as the primary market. HyperPay leans into AI-based fraud management and business intelligence dashboards, which suits merchants who want deeper reporting without building it themselves. Moyasar has a strong developer reputation for clean API documentation, which matters if you’re doing custom checkout work rather than relying purely on app-store integrations. For a Saudi-first store with development resources, either is worth evaluating alongside PayTabs.
BenefitPay (Bahrain Specific)
If Bahrain is a meaningful part of your customer base, BenefitPay deserves a dedicated mention. It’s Bahrain’s national mobile payment and wallet system, regulated by the Central Bank of Bahrain, and it operates through QR-based and app-based flows that many Bahraini shoppers use for everyday purchases, from utility bills to retail checkout. It settles in BHD and works alongside your primary gateway rather than replacing it — you’re adding it as an additional payment method, not switching your whole stack.
We treat BenefitPay the way we’d treat Apple Pay for a UK store: not the primary processor, but an option that measurably reduces friction for a specific, loyal segment of local shoppers who reach for it out of habit.
Comparison Table: Fees, Coverage and Settlement
Rates shift with volume and negotiated terms, so treat the figures below as a starting point for conversations with each provider, not a locked-in quote.
| Gateway | Best For | Local Debit Support | Typical Card Fee | Settlement Speed | Shopify Integration |
|---|---|---|---|---|---|
| Tap Payments | Multi-country GCC operations | Mada, Benefit, KNET | ~2.5–3% + fixed fee | T+2 to T+5 | Native app |
| PayTabs | Saudi-first stores, Mada reliability | Mada, cross-border cards | ~2.75–3.5% | Next-day (SAR) | Native app |
| Telr | UAE-focused SMBs | Mada, UAE bank cards | ~2.5–2.9% + AED 1 | T+3 to T+5 | Native app |
| Checkout.com | Scaling brands, AED 200k+/month | Mada, Benefit (via API) | Negotiable | T+1 to T+3 at volume | API / custom |
| Amazon Payment Services | Mixed UAE/Saudi trust-driven audience | Mada | ~2.9–3.5% | T+2 to T+5 | Native app |
| HyperPay / Moyasar | Saudi-first, developer-led builds | Mada | ~2.75–3% | T+1 to T+2 | API-first |
| BenefitPay | Bahrain local wallet coverage | Benefit network | Flat fee per transaction | Varies by contract | Third-party app |
BNPL in the Gulf: Tabby vs Tamara
Buy Now, Pay Later has moved from novelty to checkout standard across the GCC faster than most founders expected, and fashion, beauty, and electronics stores feel this most acutely. Skipping it in those categories is comparable to not accepting cards at all: technically possible, commercially costly.
Tabby is headquartered in Dubai and covers the widest geographic footprint of the two — UAE, Saudi Arabia, Kuwait, Bahrain, and Qatar. It splits purchases into four interest-free instalments, pays merchants upfront, and absorbs the credit risk itself. Its consumer app also functions as a discovery channel: shoppers browse Tabby’s own marketplace looking for stores that accept split payments, which is essentially free exposure once you’re listed. In our experience, Tabby tends to show stronger approval rates among UAE-resident shoppers, reflecting its longer operating history in that specific market.
Tamara is Riyadh-founded and is generally considered the BNPL market leader in Saudi Arabia specifically, with a Sharia-compliant structure that resonates with a segment of Gulf shoppers for whom that framing matters. It offers split-in-3 and split-in-4 options and operates across Saudi Arabia, the UAE, Kuwait, and Bahrain. Approval patterns tend to favour Tamara in the Saudi market, mirroring Tabby’s UAE strength.
Merchant fees for both typically land somewhere between roughly 3 and 6 percent depending on category, volume, and negotiated terms, which sounds steep until you look at incremental order value. A store that sees a meaningful conversion lift on the AED 200 to AED 1,500 price band from adding BNPL usually finds the fee pays for itself many times over, because those are sales that would not have completed as a single full-price card transaction.
Our practical rule for clients: if you sell primarily into the UAE, start with Tabby. If Saudi Arabia is your primary or secondary market, add Tamara early, not as an afterthought eight months in. If you sell meaningfully into both, run both from day one — most stores that do this see minimal conflict between the two, and the coverage gain outweighs the small added integration effort.
One category where BNPL rarely earns its fee: very low average order values, roughly under AED 100 or its equivalent. Splitting a small basket into four tiny payments doesn’t change buying psychology enough to justify the merchant discount rate. If your AOV sits below that threshold, we usually advise skipping BNPL and focusing spend on other conversion levers instead.
How to Choose the Right Stack for Your Store
There’s no single “best” gateway. There’s a best gateway for your specific mix of market, order volume, and category. Here’s the framework we actually use with clients.
If you’re a new Bahrain or UAE store doing under AED 50,000 a month: start with Telr or Tap. Both are fast to onboard, well-documented for Shopify, and don’t require enterprise-level paperwork. Add Tabby once you have consistent order flow to justify the integration effort.
If Saudi Arabia is your primary market: prioritise Mada reliability above everything else. PayTabs, HyperPay, or Moyasar should be your shortlist. Test Apple Pay specifically, since that’s where Mada routing issues tend to surface first.
If you’re expanding across three or more GCC countries: Tap’s single-integration coverage usually wins on operational simplicity, even if the dashboard isn’t the prettiest. The time your team saves not managing three separate merchant relationships is worth more than a marginally better reporting UI.
If you’re doing AED 200,000+ a month and negotiating leverage matters: bring Checkout.com into the conversation. The custom API work costs more upfront, but the negotiated rates and faster settlement compound at that volume.
If you’re Bahrain-based with a genuinely local customer base: don’t skip BenefitPay just because it feels like extra integration work. It’s a small lift for a segment of shoppers who will otherwise abandon at checkout when they don’t see a familiar option.
In every case, we recommend running a primary card gateway plus at least one BNPL provider plus a local wallet option where relevant, rather than betting everything on a single processor. Redundancy matters here specifically because bank-level declines on regional cards happen more often than merchants expect, and having a second route to complete the sale — even just Apple Pay through a different rail — recovers revenue you’d otherwise lose silently.
Step-by-Step: Adding a Gateway to Shopify
This is the process we follow on client builds, condensed.
- Confirm your business documentation is ready before you apply. Gulf gateways are stricter on KYC than Shopify Payments-native markets. Trade licence, bank IBAN, and owner ID are the baseline for every provider we’ve worked with. Missing paperwork is the single biggest cause of onboarding delays we see.
- Apply directly with the gateway, not just through the Shopify app listing. The app in Shopify’s store handles the technical connection, but you still need an approved merchant account with the provider itself. Do this in parallel rather than sequentially to save days.
- Install the native Shopify app once approved. Most of the gateways above have dedicated Shopify integrations rather than requiring custom API work, which keeps this step to under an hour of actual configuration time.
- Set your default currency and settlement currency correctly. This sounds obvious and we still catch it wrong on client audits regularly — a store priced in AED but settling incorrectly, or a store that never configured multi-currency and is quietly losing conversions from cross-border Gulf traffic.
- Enable every relevant local payment method inside the gateway settings, not just cards. Apple Pay, Mada, BenefitPay, or whichever wallets apply to your market need to be switched on explicitly in most dashboards — they’re rarely on by default.
- Test with real regional cards before launch, not just Shopify’s Bogus Gateway. A test transaction with an actual Mada or Benefit-linked card catches routing issues that generic sandbox testing misses completely.
- Add BNPL as a separate integration once your card gateway is confirmed stable. Layering BNPL on top of an unstable primary gateway makes debugging checkout issues far harder, because you can’t isolate which layer failed.
- Check your order confirmation and webhook flow end to end. A payment can succeed at the gateway level and still fail to mark the Shopify order as paid if the webhook configuration is off — we’ve inherited more than one client account with this exact silent failure.
Common Mistakes We See Constantly
Relying solely on Shopify Payments and wondering why conversion is flat. It isn’t available for settlement in most GCC currencies, so a chunk of your local traffic never even sees a payment method they recognise.
Ignoring Mada until launch week. We’ve inherited stores where Mada was technically “supported” by the gateway but never actually tested, and it turned out Apple Pay transactions were failing silently for weeks before anyone noticed the order data looked thin.
Treating BNPL as optional for categories where it’s now expected. Fashion, beauty, and electronics shoppers in the UAE and Saudi Arabia increasingly check for BNPL before adding to cart. Not offering it isn’t neutral — it’s a visible gap next to competitors who do.
Skipping local wallets because they feel like a small market. BenefitPay in Bahrain, for example, is a habitual payment method for a meaningful slice of local shoppers. Excluding it isn’t a rounding error, it’s excluding a segment that expects to see it.
Never renegotiating rates as volume grows. Most merchants sign their first-year rate and never revisit it. Gateways expect this conversation once you’re processing serious volume, and most have room to move.
Not testing the actual checkout on a real device with a real regional card before launch. Sandbox testing catches code errors. It doesn’t catch bank-level routing issues that only appear with a live Mada or Benefit card.
A Real Client Scenario
A skincare brand we worked with in Manama launched with a single international gateway configured mainly for card payments, on the assumption that “cards are cards.” Within the first month, order data showed a strange pattern: strong add-to-cart activity, weak completed checkouts, concentrated specifically among mobile Safari sessions.
The cause turned out to be exactly what you’d expect once you know to look for it: Apple Pay transactions were routing as generic international cards rather than being recognised as the underlying Mada or Benefit-linked cards customers actually had loaded into their wallets. The bank was declining a portion of them with no useful error message reaching the customer.
We layered in a Gulf-native gateway alongside the existing setup, explicitly enabled local debit routing, and added BenefitPay as a secondary option given the brand’s strong Bahrain customer base. Checkout completion on mobile improved meaningfully within the following billing cycle, without a single change to the store’s design, copy, or ad spend. The product didn’t change. The traffic didn’t change. The payment routing did.
This is the pattern we see more than almost any other: founders assume a conversion problem is a design or marketing problem, when it’s actually sitting one layer beneath, in the payment stack nobody’s checked since launch.
Frequently Asked Questions
Does Shopify Payments work in Bahrain, the UAE, or Saudi Arabia? No. Shopify Payments does not offer native settlement in BHD, AED, or SAR, so GCC merchants need a third-party gateway from the outset rather than treating one as an optional add-on later.
Which gateway has the best Mada support? PayTabs, HyperPay, and Moyasar are all Saudi-focused and built specifically around reliable Mada routing. Tap and Telr also support Mada but are more broadly regional rather than Saudi-first in design.
Do I need both Tabby and Tamara, or just one? If you sell meaningfully into both the UAE and Saudi Arabia, running both is usually worth the modest extra setup effort, since approval rates and brand recognition differ by market. If you sell almost exclusively into one country, starting with the market leader there is a reasonable first step.
Is cash on delivery still worth offering in 2026? Yes, particularly outside major cities and for first-time customers who haven’t built trust in your brand yet. It’s worth keeping as an option even as digital and BNPL adoption grows.
How long does gateway approval usually take? It ranges from under a day for streamlined providers like PayTabs to several business days for more document-heavy options. Having your trade licence, bank details, and owner ID ready before you apply is the single biggest factor in speeding this up.
Can I use more than one gateway on the same Shopify store? Yes, and we generally recommend it. A primary card gateway plus a BNPL provider plus a local wallet, where relevant, gives customers more than one route to complete a purchase.
What VAT rate should I be charging in each country? As of 2026, Saudi Arabia applies 15 percent VAT, Bahrain applies 10 percent, and the UAE applies 5 percent. Kuwait and Qatar have not implemented a general VAT. This affects your Shopify tax configuration separately from your payment gateway choice, so don’t assume one setting covers both.
Why is my Apple Pay conversion lower than expected in Saudi Arabia? This is almost always a routing issue rather than a customer preference issue. Most Saudi Apple Pay transactions are underlying Mada cards, and if your gateway doesn’t process that correctly, customers see unexplained declines. Test this specifically with a real Mada-linked device before launch.
Is Checkout.com worth it for a smaller store? Generally not yet. The onboarding overhead and enterprise-paced account management make more sense once you’re processing well into six figures in AED or SAR monthly. Below that, Tap, Telr, or PayTabs are usually a better fit.
Does BenefitPay only matter for Bahrain-based stores? Primarily, yes, but any store shipping meaningfully into Bahrain benefits from offering it as a secondary option, even if the brand is headquartered elsewhere in the GCC.
How often should I review my gateway setup after launch? At minimum, once a quarter, and immediately after any noticeable dip in checkout completion rate. Payment routing issues are often silent — they don’t throw obvious errors, they just quietly suppress conversion until someone checks.
Should I switch gateways if I’m already live and things seem to be working fine? Not necessarily. If your conversion data looks healthy and local payment methods are all confirmed working, a switch introduces risk for uncertain reward. We generally recommend an audit before a full migration, not the other way around.
Conclusion
The gateway conversation rarely gets the attention it deserves during a Shopify build, mostly because it feels like a solved problem the moment a checkbox is ticked. In the Gulf, it isn’t solved by default. It’s one of the few technical decisions that directly determines whether a customer with money in hand and a card in their wallet can actually complete a purchase on your site.
Get the local debit routing right, add BNPL where your category expects it, and don’t treat smaller national systems like BenefitPay as an afterthought. Those three moves alone resolve the majority of checkout issues we find during audits.
If you’re setting up a new Shopify store in Bahrain, the UAE, or Saudi Arabia, or you suspect your current gateway setup is quietly costing you sales, Velvetica Studio can review your checkout configuration and recommend a stack built for how your specific customers actually pay. Get in touch for a consultation.