The right payment gateway for a Saudi business is the one that supports the methods your customers actually use, mada first, then Apple Pay and cards, and that fits where you sell: only inside the Kingdom, across the Gulf, or internationally. Fees matter, but a gateway that is missing mada or approves your account slowly costs more than a small difference in rates.
This guide covers what to compare, how the main gateways differ, and the integration details that decide whether payments work on launch day.
Which payment methods do Saudi customers expect?
mada is Saudi Arabia's national debit card network and the card most local shoppers carry, so a store without mada turns away many buyers at checkout before price or design even come into it. After mada, the methods to plan for are:
- Credit and debit cards (Visa, Mastercard) for customers paying by card outside mada.
- Apple Pay, which many customers prefer on mobile because it skips card entry.
- Digital wallets such as STC Pay (now part of STC Bank), depending on the gateway.
- Buy now, pay later, through providers such as Tabby and Tamara, for higher-value carts.
Which of these you can switch on depends on the gateway and on the approval you receive for your merchant account, not only on the gateway's website.
What should you compare between gateways?
Compare gateways on these points, in this order:
- Payment methods: mada, Apple Pay, cards, wallets and installments.
- Where you sell: Saudi Arabia only, the Gulf, Egypt, or international customers.
- Onboarding: the documents required and how long approval takes for your business type.
- Fees and settlement: the rate per method, fixed fees, and how many days until money reaches your bank account.
- Integration options: hosted payment page, embedded form, mobile SDKs, plugins for your platform, and the quality of the API documentation.
- Refunds and disputes: whether partial refunds and voids are supported, and how chargebacks are handled.
- Reporting: settlement reports you can reconcile against your orders.
Ask each provider for its current fee sheet in writing. Rates differ by payment method and by merchant, so published numbers are only a starting point.
How do the main gateways differ?
| Gateway | Payment methods | Best for |
|---|---|---|
| HyperPay | Cards, mada, Apple Pay, local wallets | Businesses selling mainly inside Saudi Arabia |
| Moyasar | mada, cards, Apple Pay, STC Pay | Stores and apps that want a developer-friendly API |
| Amazon Payment Services | Cards, mada, wallets, installments | Stores that want a trusted brand at checkout |
| Geidea | Online checkout and point-of-sale devices | Selling online and in a physical branch |
| MyFatoorah | Many local methods across the Gulf | Growing stores that want fast onboarding |
| Tap Payments | Cards, mada, regional methods such as KNET | Selling across several Gulf countries |
| PayTabs | Hosted pages, API and ready plugins | Merchants across Saudi Arabia and the Middle East |
| Checkout.com | International cards and local methods | High-volume merchants with detailed reporting needs |
| Paymob | Cards and wallets | Selling in Saudi Arabia and Egypt together |
| Stripe | Global cards, subscriptions | Products sold mainly to international customers; check whether it accepts your business entity, as it has not onboarded Saudi-registered companies directly |
| PayPal | PayPal balance or linked card | International customers who prefer PayPal |
For a business selling inside the Kingdom, the shortlist usually starts with a Saudi gateway that has strong mada and Apple Pay support. Add a second provider only when you have a clear reason, such as international customers or installments.
Do you need more than one gateway?
Often, yes, but for specific reasons rather than by default. Common combinations are a local gateway for mada and Apple Pay plus an international one for foreign cards, or a main gateway plus Tabby or Tamara for installments. Each extra provider means another integration to maintain, another settlement report to reconcile, and another set of webhooks to secure.
What decides whether payments work on launch day?
Most payment problems appear in edge cases, not in the normal flow. Before going live, test:
- Approved, declined and expired cards, and the message the customer sees for each.
- 3D Secure challenges that pass, fail or are abandoned, and the return to the correct order page.
- Webhooks that arrive late, twice or out of order, so an order is never marked paid or shipped twice.
- Full refunds, partial refunds and voids, and the matching status in your dashboard.
- Totals with discounts, shipping and 15% VAT, so the amount charged matches the invoice.
- Closing the page mid-payment, pressing back, and double-clicking the pay button.
Keep card data off your own servers. Hosted payment pages and the gateway's SDKs mean card numbers go straight to the gateway, which keeps most of the PCI DSS burden with the provider.
How long does integration take?
The code is rarely the slow part. Merchant approval, collecting documents and setting up production keys and callback URLs usually take longer than building checkout. Start the gateway application while the store or app is still being built, so approval is not what delays the launch.
Summary
Choose the gateway by payment methods and market first, then by onboarding, fees and integration quality. Make sure mada and Apple Pay are covered, test every edge case in the sandbox, and confirm with one small live payment before launch.
Payments are one part of a compliant store: read what ZATCA e-invoicing requires, and whether Salla, Zid or a custom store suits you.
If you want help choosing or integrating a gateway, see our payment gateway integration service or contact our team.