Chapter 1. Three markets, three ways in.
In the Gulf, payment acceptance is handled market by market. Saudi Arabia, the United Arab Emirates, and Kuwait share dollar-pegged currencies and near-universal card acceptance. Yet each runs on its own payment infrastructure and answers to its own regulator. In all three countries, the domestic switch (the technical hub that routes authorizations between acquirers and issuers) belongs to the central bank or to the local banks. None is a private operator facing competition. You therefore negotiate your connection with an institution that holds a de facto monopoly, and the lack of an alternative weighs on both your launch timeline and your room to negotiate pricing.
| 🇸🇦 Saudi Arabia | 🇦🇪 United Arab Emirates | 🇰🇼 Kuwait | |
|---|---|---|---|
| Currency | Saudi riyal (SAR) | UAE dirham (AED) | Kuwaiti dinar (KWD) |
| Domestic debit | mada, launched in 2015 | Jaywan, launched in 2024, and the UAESWITCH switch | KNET, in service since 1992 |
| Operator | Saudi Payments, a SAMA subsidiary | Al Etihad Payments, a wholly owned CBUAE subsidiary | The Shared Electronic Banking Services Company, a consortium of Kuwaiti banks |
| Instant rail | sarie (2021), phone number alias | Aani (2023), aliases and QR codes | Wamd (2024), phone number alias |
| Regulator | Saudi Central Bank (SAMA) | Central Bank of the UAE (CBUAE) | Central Bank of Kuwait (CBK) |
| Main barrier to entry | Local online stores must process through the national system | License by service category, with a UAE entity | De facto routing through the bank consortium, with no domestic alternative |
The first decision in a payment acceptance project is legal status, before any question of technical integration. To accept payments, you need either a license from the local regulator or a contract with an acquirer already connected to the national switch. A license takes quarters to obtain and ties up capital. A licensed acquirer gets you into the market in a few weeks, at the cost of a margin on every transaction and an operational dependency. The choice comes down to expected volume and how long you plan to operate.
Chapter 2. Saudi Arabia: mada and the local processing requirement.
Domestic routing is a requirement that merchants send their authorizations through their country's national switch rather than an international network. Since 2018, Saudi Arabia has imposed it on online stores established in the Kingdom. Their payments go through the national mada system. A Saudi merchant therefore doesn't choose the authorization path. The only decision left is the provider, which must be able to use that path.
Cost, and why a European pricing grid doesn't apply
The merchant service charge is the amount the acquiring bank keeps on each transaction the merchant accepts. On mada, the scheme caps it. According to the official documentation, the acquiring bank takes at most 0.80% of the purchase amount, up to SAR 40 per transaction. Two examples published by mada give a sense of scale. A SR 35 purchase costs about SR 0.28, while a SR 20,000 purchase costs about SR 40, or 0.20% of the order.
// mada merchant service charge: 0.80%, capped at SAR 40 per transaction
// Source for the cap: official mada documentation, accessed in 2026
function mscMada(orderSAR) {
return Math.min(orderSAR * 0.008, 40);
}
mscMada(35); // SAR 0.28 -> 0.80% of the order
mscMada(5000); // SAR 40.00 -> exact point where the cap kicks in
mscMada(20000); // SAR 40.00 -> 0.20% of the order
// Modeling consequence: above SAR 5,000, the acceptance cost
// becomes FIXED. Any pure-percentage simulation overstates the expense.| Cart | mada fee (capped) | Effective rate | What it means for the merchant |
|---|---|---|---|
| SAR 50 | SAR 0.40 | 0,80 % | Only the percentage applies, with no fixed amount to absorb |
| SAR 500 | SAR 4.00 | 0,80 % | Linear range: the cap hasn't kicked in yet |
| SAR 5,000 | SAR 40.00 | 0,80 % | Tipping point: above this, the cost stops rising |
| SAR 20,000 | SAR 40.00 | 0,20 % | High-value sale: steering buyers to mada is worth more than negotiating a discount |
- Check the acquirer's license in the SAMA register, not in the provider's sales brochure
- Show mada first at checkout: domestic debit carries most online volume
- Model costs with the cap, or every margin forecast on orders above SAR 5,000 will be wrong
- Distinguish SARIE from sarie in your specs: the first is the RTGS system in service since 1997, the second the retail instant payment service launched in 2021
- Plan to use sarie for payouts: marketplace payouts, refunds, and supplier payments become instant, with alias addressing
Chapter 3. Kuwait: accepting payments behind KNET.
KNET is both Kuwait's national switch and its debit scheme. It is run by The Shared Electronic Banking Services Company, a consortium owned by Kuwaiti banks, and has been operating since 1992. All domestic card acceptance, in store and online, goes through this infrastructure. There is no second path for authorizing a Kuwaiti debit card. Domestic acceptance comes down to a single connection.
- A single domestic integration to plan, either directly or through a Kuwaiti acquiring bank that is already connected
- A distinct payment flow: the cardholder is redirected to the network's authentication page, which rules out a checkout hosted entirely by the merchant
- A continuity plan that a second acquirer won't solve: both acquirers sit behind the same switch
- Little room on pricing: facing a market-wide bank consortium with no competitor, your leverage lies in ancillary services more than the unit price
| System | Operator | In service since | What a merchant uses it for |
|---|---|---|---|
| KNET | The Shared Electronic Banking Services Company | 1992 | Domestic card acceptance, in store and e-commerce: the only way through |
| Wamd | KNET, with the Central Bank of Kuwait | 2024 | Instant account-to-account payments by phone number, from banking apps |
| KASSIP | Central Bank of Kuwait | 2004 | Real-time gross settlement: the interbank leg, never a retail rail |
| KECCS | Central Bank of Kuwait | 2015 | Check image clearing, worth knowing for guarantees and trade credit |
Wamd is Kuwait's instant account-to-account payment service. Launched in 2024 by KNET with the central bank, it addresses the payee's account by phone number from the payer's banking app. Its infrastructure provider reported more than 1 million registered accounts after one year. For merchants, the use case available today is payouts: refunds, payments to third-party sellers, and compensation payments. It doesn't yet cover collecting payments at checkout.
Chapter 4. UAE: Aani, Jaywan, and the payment acceptance stack.
The United Arab Emirates has the most payment rails of the three markets covered here. Access is open through several channels, so the challenge in a payment acceptance project is choosing the right rail for each use case. Since 2023, the CBUAE has housed its newer rails in a subsidiary, Al Etihad Payments. The central bank still runs the legacy systems itself, and they still carry a large share of volume.
| Rail | In service since | Merchant use | Watch out for |
|---|---|---|---|
| Aani (Instant Payments Platform) | 2023 | Instant payment by alias or QR code, request to pay, immediate payouts | AED 50,000 limit per transfer: above that, the payment moves to UAEFTS |
| Jaywan | 2024 | Domestic debit, co-badged with Visa, Mastercard, UnionPay, and Discover | Acceptance is in place, but issuance is still ramping up: don't size a plan on the card base |
| UAEPGS (UAE Payment Gateway System) | 2016 | Direct collection from the payer's bank account, with one integration covering many banks | Often left out of integration plans, even though large billers use it for recurring collections |
| UAEDDS (UAE Direct Debit System) | 2012 | Direct debit under a mandate registered with the central bank, for fixed or variable amounts | Designed to replace post-dated checks held as security: the legal framework differs from a European mandate |
| UAEFTS | 2001 | Dirham settlement, high-value payments, links to regional systems | Aani's settlement leg, not a retail payment rail |
Integrating Aani involves three decisions. The first is addressing: by phone alias, Emirates ID, or merchant QR code, each with its own enrollment flow. The second is request to pay, which replaces a card payment link for deferred payments. The third is the limit. An order above AED 50,000 drops off the instant rail and falls back to a standard credit transfer, with different timing and a different customer experience.
- Identify the license category that applies to your setup: the CBUAE's Retail Payment Services and Card Schemes regulation, published in 2021, defines nine services in four categories
- Choose the rail by use case: Aani for instant payments and payouts, UAEPGS for recurring account-based collections, and cards for international customers
- Treat direct debit as a legal product, not a credit transfer in reverse: UAEDDS mandates are registered with the central bank
- Align cut-offs with the Emirati calendar: the UAE weekend has been Saturday–Sunday since January 1, 2022, while it is still Friday–Saturday in Saudi Arabia and Kuwait
Chapter 5. Pay later: Tabby, Tamara, and cash on delivery.
Cash on delivery and BNPL serve the same buying habit: paying only after seeing the product. Cash on delivery leaves the merchant with no payment guarantee until delivery. BNPL shifts that guarantee to the provider, which advances the funds to the merchant. In the Gulf, BNPL requires a central bank license, and that regulation sets how costs are split between merchant and customer.
This ban shapes the product's business model. The provider earns a fee negotiated with the merchant, not charges paid by the buyer. That fee pays for two separate services: paying the merchant up front and taking on the credit risk. Tabby describes this model on its merchant page: four interest-free installments, up to 12 with its longer pay-over-time option, the merchant paid within a few days, and the risk carried by the provider.
| mada card / domestic debit | Local BNPL | Cash on delivery | |
|---|---|---|---|
| Who carries the credit risk | The issuer, once authorized | The BNPL provider | The merchant, until delivery |
| When the merchant gets paid | After capture, when the acquirer settles | Up front, within a few days of the order | After the carrier collects the cash and remits it |
| Who bears the cost | The merchant, under the mada network cap in Saudi Arabia | The merchant: charging the consumer is prohibited in the Kingdom | The merchant, outside any fee schedule |
| Traceability | Transaction ID, settlement file | Order ID on the provider's side | Carrier delivery slips, line-by-line reconciliation |
| Failure after acceptance | Rare once authorized | Rare: any decline happens before the order | Common by design: refused at the door |
Calculating the all-in cost of cash on delivery
A card fee shows up on the acquirer's invoice, but the cost of cash on delivery has to be rebuilt line by line. It has five components, and none of them appears in a payment pricing grid. You fill in the calculation below from the merchant's contracts and its own operating data. It makes the two options comparable as a single cost per delivered order.
Reference order: SAR 300
a Carrier cash-collection fee ......................... SAR ....
b Extra logistics cost of refused deliveries .......... SAR ....
c Returns, storage, restocking ........................ SAR ....
d Cash tied up (days x cost of capital) ............... SAR ....
e Manual reconciliation minutes x hourly cost ......... SAR ....
Cost per DELIVERED order = (a + d + e) + (b + c) x t / (1 - t)
where t = refusal rate at delivery
Compare, for the same order, with:
mada min(300 x 0.80%, SAR 40) = SAR 2.40 (regulatory cap)
BNPL contractual merchant fee, paid up front
Items a through e are ASSUMPTIONS: fill them in from your contracts.
The mada cap, by contrast, is regulatory: mada documentation, 2026.- Don't drop the option overnight where it still matters: giving up cash on delivery means buyers must agree to pay before they see the product, and that shift takes several purchase cycles
- Offer an alternative that does the same job: local BNPL gives buyers the same peace of mind, with an authorization and a payment guarantee
- Measure the refusal rate by city and time slot, not as a national average: the refusal rate feeds directly into the cost per delivered order, and an average blends areas that differ enough to make cash on delivery profitable in one place and loss-making in another
- Count reconciliation in team hours: without a transaction ID or a clearing file, this cost doesn't shrink as volume grows
Chapter 6. PSP license, local entity, and acquiring partner.
Passporting is the mechanism that lets an institution licensed in one country operate in neighboring countries without a new license. No such mechanism exists among the Gulf states. A provider operating in Riyadh and Dubai holds two licenses, issued by two authorities, with two sets of reporting obligations. Kuwait adds a third. This budget line requires local compliance staff from the application stage, well before transaction volume can pay for it.
| Jurisdiction | Authority | Legal basis | Key takeaway |
|---|---|---|---|
| 🇸🇦 Saudi Arabia | SAMA | Implementing Regulations of Payments and Payment Services Law, Circular No. 000044093096 of June 13, 2023 | This text repeals and replaces the 2020 Payment Services Provider Regulations. Categories: Micro PI, Major PI, Micro EMI, Major EMI, payment initiation, and account information |
| 🇦🇪 United Arab Emirates | CBUAE | Retail Payment Services and Card Schemes Regulation, published in 2021 | Nine retail payment services across four license categories, I to IV; stored value facilities fall under a separate regime |
| 🇰🇼 Kuwait | CBK | Instructions for Regulating the Electronic Payment of Funds, May 2023, revising the 2018 instructions | Five license types based on volume and type of service; minimum capital of KWD 50,000 for a small provider and KWD 250,000, maintained at all times, for a large one |
The Saudi regime specifies the legal form an applicant must take. The 2023 regulations require a joint stock company for a Major PI, Major EMI, or Micro EMI license. The Micro PI regime allows lighter structures, including a limited liability company. The scope also covers anyone who presents itself as a payment service provider in the Kingdom, so operating from abroad without a local presence doesn't exempt you from licensing.
- Classify the service before you classify the entity: acquiring, aggregation, payment initiation, and account information fall into different categories in all three countries
- Check the license in the regulator's register, never on the partner's marketing site, because several regional players have recently changed their company name or status
- Sequence by country, not by region: Saudi Arabia and the UAE account for most of the volume, while Kuwait opens faster through an acquirer that is already connected
- Budget for periodic reporting from year one, with a named local compliance officer
- Scope the connection to the national switch as a separate project, with its own certifications and release windows
Chapter 7. E-invoicing: ZATCA, then the UAE.
In Saudi Arabia, e-invoicing controls when the buyer can receive the invoice. A standard invoice that the tax authority hasn't cleared cannot be sent. A sales system that skips this step therefore produces paid orders with unusable invoices. The system is run by ZATCA, the Kingdom's tax authority, not the central bank.
| Standard invoice (mainly B2B) | Simplified invoice (mainly B2C) | |
|---|---|---|
| Processing | Cleared in advance by ZATCA | Reported after issuance |
| Deadline | Before it goes to the buyer | Within 24 hours of generation |
| Cryptographic stamp | Applied by the tax authority | Applied by the merchant's solution |
| Submission format | XML | XML, never PDF/A-3 |
| Special case | – | Can be used for B2B when the value of taxable supplies is under SAR 1,000 |
- Two phases, two dates: generation has been mandatory since December 4, 2021, and integration with FATOORA since January 1, 2023, rolled out in successive waves with at least six months' notice
- Every device must be onboarded: each terminal that issues invoices under the same VAT number must be registered and receive its own stamp identifier
- Invoices must be in Arabic: the XML structure stays in English, the visible data must be in Arabic, and other languages can be added
- A scanned paper invoice is not an e-invoice: a paper invoice converted by photocopy or scan is still non-compliant
- Plan for outages: if the connection drops or the server is down, you must report the incident to ZATCA, issue the invoice, then resubmit once service is restored