Middle East Payment Playbook: Gulf Card Networks, Cash on Delivery, and Regulators

Middle East Payment Playbook: Gulf Card Networks, Cash on Delivery, and Regulators

In commercial usage, the Middle East usually means the six Gulf markets plus a handful of priority markets such as Egypt and Turkey. The most common misjudgement in this region is that international card logos appear on many local checkouts, while what local consumers actually use day to day is often a debit card issued on their own domestic network. Those two coverages are not equivalent. This article is a deep dive into the region; for the cross-region panorama, see the global local payment methods overview. No rates, market shares, or license numbers appear here, and wherever a qualification threshold is mentioned, treat the local regulator and the channel operator as the authority.

1. What the Six Gulf Markets Share

The first shared trait is that the domestic debit network comes before international cards. Saudi Arabia, the UAE, Kuwait, Bahrain, Qatar, and Oman each run a clearing network operated by the central bank or by a company inside the central bank's orbit, and locally issued debit cards settle across banks on those networks. A cross-border acquirer holding international scheme membership can only process on the international rails; covering domestic debit in practice requires connecting to the domestic network, and that usually requires a licensed acquirer as the entry point.

The second trait is that regulation comes before commerce. Central banks in the Gulf are the primary regulators of payment services, and acquiring, wallets, and settlement accounts each fall under different access requirements. A foreign entity that wants to collect locally usually needs a local commercial registration or a partnership with a licensed institution. Under the partnership model, who is the merchant of record, who carries clearing responsibility, and who handles disputes must be written into the contract, otherwise the first chargeback exposes the gap.

The third trait is the persistence of cash and cash on delivery. Payment infrastructure and urbanization in the Gulf are not weak, yet cash on delivery still holds a significant position in e-commerce orders. The reasons include consumer habit as well as caution about online dispute handling. This is covered separately below, because it directly rewrites the assumptions behind a collection design.

2. Saudi Arabia: The Domestic Debit Network and the Regulatory Frame

Saudi Arabia is the largest single Gulf market and the one with the clearest access thresholds. Online payment runs on two rails: a domestic debit network and international cards. To a merchant the difference looks like one extra acceptance logo; on the clearing side they are entirely different chains, with different responsible parties, different exception handling, and different settlement rhythm.

2.1 The Standing of the Domestic Debit Network

The Saudi domestic debit network is operated by a payment company inside the central bank's orbit, and locally issued debit cards transact mainly on it. For a merchant targeting local consumers, accepting only international cards leaves out a meaningful share of cardholders, because many local users concentrate their daily payments on domestic debit. Connecting to this network requires a licensed acquirer, and foreign entities generally cannot integrate directly, which is why choosing a provider in Saudi Arabia is effectively choosing a local acquiring partner.

One easily overlooked property of the domestic network is that its chargeback and refund flows differ from the international card system. The evidence required, the handling deadlines, and the escalation path are all different. An operations team that writes its process purely from international card experience will find no matching entry point when a domestic card dispute arrives. The domestic network should therefore be modelled separately in the system rather than treated as a variant of an international card.

2.2 The Regulatory Frame and Access Routes

The Saudi Central Bank governs access to and supervision of payment services, with different rules for acquiring, wallets, and settlement. Foreign entities usually have two paths: establish a local entity and apply for the relevant permissions, or partner with a licensed local acquirer that acts as merchant of record or clearing party. The second path starts faster, but pricing, settlement cycles, and refund timing are all decided by the intermediary, so contracts must state who owns each exception scenario.

Saudi electronic invoicing requirements also land directly on billing and reconciliation, so the collection system and the invoicing system have to be designed together rather than bolted on later. A common sequencing mistake is to finish payment integration first and only then consider invoicing, discovering that order amounts, tax amounts, and invoice numbers cannot be aligned, forcing a data model rewrite. Designing the two systems side by side at kickoff removes a large amount of rework.

3. The UAE: Cards and Digital Wallets Side by Side

The UAE is the closest thing to an international standard in the Gulf. Card coverage is comprehensive, users are familiar with international card flows, the domestic switch clears local debit cards, an instant payment platform lets account-to-account transfers settle in real time, and the Central Bank of the UAE is the regulator. E-commerce and cross-border business density in Dubai and Abu Dhabi is high, and acceptance of installments and wallets among local consumers is rising.

Three details matter in practice. First, free zone entities and onshore entities are subject to different rules on account opening and acquiring permissions, and that choice affects which channels are available later. Second, the population has a very high share of expatriate residents, so the checkout must serve international card users and domestic network users at the same time, and dropping either depresses conversion. Third, cash on delivery remains a default option in some categories, especially high-ticket and first-time orders, so the collection design has to connect to the delivery partner's proof-of-collection flow.

Multi-currency needs are also more visible in the UAE than in neighbouring markets. Cross-border sellers often quote in US dollars, collect in local currency, and settle in a third currency, so conversion loss and reconciliation definitions must live in one model; see the multi-currency collection account guide for the mechanics.

4. Kuwait, Bahrain, Qatar, and Oman: Domestic Clearing Networks

These four markets are small but carry respectable ticket sizes and payment capacity, and the issue is that each has its own shared network, so integration cost must be calculated per country. Kuwait's KNET is a mandatory element of online acquiring, and local consumers depend on it heavily. Bahrain clears local payments through Benefit. Qatar runs NAPS alongside a domestic card scheme. Oman is served by a national switch and local payment gateways.

For a cross-border merchant, these four are better covered through an aggregator than through direct bilateral integration. The reason is simple: single-country volume rarely absorbs local integration and compliance costs, while an aggregator bundles them behind one interface. The price is little bargaining room on pricing and settlement terms, plus exception handling that passes through an intermediary. Only when revenue in a given country covers the fixed cost of a local entity does a direct local acquiring conversation make sense.

Note that small markets do not mean loose rules. The central banks in these countries set equally explicit licensing requirements for payment services, and how a foreign entity appears and how funds move in and out must be explained in the partnership structure up front. Plans built on the assumption that small volume means the rules can be sidestepped tend to collapse at the first compliance inquiry.

5. Egypt and North Africa: Cash Collection Networks

Egypt is the most important market at the junction of the Middle East and North Africa, and one of the most distinctive payment structures anywhere. The regulator is the Central Bank of Egypt, and online payment is shared among international cards, a domestic card scheme, and an instant payment network. What actually reaches the long tail of consumers is the agent network spread across every neighbourhood, with Fawry as the leading example: the user receives a reference number with the order, pays cash at a convenience store, pharmacy, or mobile operator shop, and the merchant confirms receipt through the collection network. This mechanism does not depend on cards and does not require a bank account, which makes it highly effective where card penetration is limited.

Other North African markets are similar. In Morocco, card clearing is run centrally by an interbank institution; Algeria and Tunisia each have their own clearing bodies, and cash holds a persistently high share of retail payment. Running e-commerce in this belt means accepting that some orders will ultimately settle in cash, and fulfilment, returns, and reconciliation must all make room for it. Egypt also separates local currency settlement from foreign currency settlement, so the paperwork and cycle for remitting funds abroad must be confirmed early, subject to local regulatory and channel requirements.

Turkey is a different shape again: a domestic card centre and a national card scheme run in parallel, the regulator sets separate requirements for payments and acquiring, and local acquirers are often more complete in product than international institutions. If a business covers both the Gulf and Turkey, treat them as two independent projects rather than merging them into one regional plan.

6. Why Cash on Delivery Still Matters

6.1 Rejection Rates and Cash Recovery

Cash on delivery pushes the payment moment behind fulfilment. It lowers the barrier to ordering and transfers risk to the merchant. The most direct problem is rejection: the recipient is unavailable at delivery, changes their mind, or refuses to pay, so the courier returns the parcel, leaving the merchant with two-way shipping cost and uncertain resale. The second problem is cash recovery: cash is consolidated through delivery partners or collection agents before being settled to the merchant, which introduces a payment lag, and reconciliation often stops at batch level rather than per order.

Together these two problems materially change the cash flow model. A purely online, instant-settlement business can forecast receipts by the day; a business mixing in cash on delivery must forecast weekly or longer, and inventory and marketing budgets have to move to that rhythm. Many teams model only the conversion lift and ignore the cost of rejections and lag, then find that scaling makes the squeeze worse rather than better.

6.2 Designing COD Into the Product

The right response is not to ban cash on delivery but to make it a controlled option. Common measures include requiring a partial prepayment on large first orders, using a small online payment to filter out users with no real intent; making a pre-delivery phone or SMS confirmation mandatory, with automatic cancellation on failure; allowlisting regions or categories with low rejection rates; and modelling shipped-but-unpaid as its own order state that drives inventory, refunds, and support workflows.

One practical lesson: make COD eligibility a configurable policy rather than hard-coded logic. Rejection behaviour varies widely by country, category, and delivery partner, and operations needs to adjust rules without shipping a release. That requires payments, orders, and logistics to share a single definition of order state.

7. Language, Currency, and Localization Details

Arabic is written right to left, so the checkout, invoices, and email templates all need mirrored layouts, and the direction of numbers, dates, and amounts must not flip along with the surrounding text. Currency symbol placement, thousands separators, and the Eastern Arabic numerals some users prefer all need separate front-end handling. Three Gulf currencies use three decimal places; if the back end stores everything with two, rounding residue accumulates and becomes very hard to explain during reconciliation.

Time has its own details: the definition of the weekend differs between countries, so support coverage, settlement batches, and campaign timing must follow local calendars. Address handling is another trap. Some countries have no usable standard postal code, and delivery depends heavily on phone confirmation, which means the order form must tolerate looser address formats and phone validation rules must be looser than in Europe or North America.

On compliance, invoice formats and electronic invoicing requirements are set by tax authorities, and the field mapping to the collection system must be agreed in advance. Marketing localization is not just translation either: price presentation, promotional wording, and even how a payment method's name is written should be reviewed by a local team. Otherwise users hesitate over an unfamiliar brand name at checkout, and hesitation is where conversion is lost.

8. Rollout Path and Priorities

8.1 A Staged Rollout

Stage one should cover Saudi Arabia and the UAE. They are the largest markets with the clearest local method landscape, and both international and local acquirers offer mature options, so pricing and conversion can be validated quickly. Stage two adds Kuwait, Qatar, Bahrain, and Oman, covered in bulk through an aggregator to avoid per-country integration cost. Stage three is Egypt and North Africa, where the key decisions are not payment APIs but the choice of collection network and delivery partner, plus the design of local currency collection against foreign currency settlement.

Turkey, considered on its own, demands deeper localization and should wait until revenue expectations are clear. The ordering throughout is driven by the ratio of revenue contribution to integration cost, not by the length of a provider's coverage list. Open the fewest possible doors to validate purchase intent first, then invest in deep localization for the markets that actually matter.

8.2 Provider Combinations

Regional acquirers win on breadth: Adyen and Nuvei are mature in multi-currency and multi-market combinations, while Checkout.com and Stripe are stronger on developer experience and product completeness. Localization depends on local acquirers: HyperPay and PayTabs are common in Saudi Arabia and the wider Gulf, Paymob covers collection and local methods well in Egypt, and Turkey offers iyzico and PayTR.

Supporting work matters just as much. Configure fraud and chargeback rules per region, following the payment fraud prevention strategies and the chargeback reason code and evidence playbook. Unify multi-currency collection and settlement into one model. Treat success rate as a continuous operating metric rather than a one-time configuration, as described in the payment success rate optimization guide. More payment topics are collected under the Payment category.

Source: 16IDC original. Product capabilities, pricing and eligibility requirements follow the relevant providers’ official documentation and contract terms.