Expand (Payments) Into the Middle East

How to Build the Perfect Payment Stack for the Middle East The payment opportunity is concentrated. The infrastructure is not. Saudi Arabia, the UAE, and Israel account for approximately 63% of the comparable nominal GDP within the 14-market definition used in this guide. The six GCC economies together represent nearly two-thirds of the same total. Yet the region’s population is concentrated elsewhere. Iran, Iraq, and Yemen together contain approximately 60% of the people covered by this guide. That difference changes the expansion decision. A merchant cannot rank Middle Eastern markets by population and assume that commercial access, digital-payment adoption, provider availability, settlement, and purchasing power will follow. Nor can it sign one Gulf-focused PSP contract and conclude that the region is covered. Saudi Arabia has a mature national card system and a rapidly expanding digital-payment economy. Kuwait has KNET. Bahrain has BENEFIT and BenefitPay. Qatar operates Himyan, Fawran, and Qatar Mobile Payment. Oman has OmanNet and its mobile-payment clearing infrastructure. The UAE has Aani and the newly introduced Jaywan scheme. Jordan connects bank accounts and mobile wallets through CliQ and JoMoPay. These systems do not form one merchant integration. The regional opportunity therefore comes from building one payment platform beneath several local acceptance strategies.

Merchants should centralize the elements that create operating leverage—tokens, payment state, fraud tooling, reporting, experimentation, and provider management—while treating payment methods, acquiring, settlement, tax, and checkout configuration as country-level decisions. That discipline is especially important in 2026. Current World Bank and IMF assessments describe substantial uncertainty caused by regional conflict, trade disruption, energy shocks, and financial volatility. Expansion plans should therefore use staged commitments and explicit pause conditions rather than fixed multi-year assumptions. (IMF)

Middle East Payment Expansion Snapshot Dimension Merchant view Defined scope 14 markets: the GCC, Iran, Iraq, Israel, Jordan, Lebanon, Palestine, Syria, and Yemen Estimated population Approximately 296 million in 2024 Comparable economic scale Approximately $3.7 trillion in nominal 2024 GDP across 12 markets with reasonably comparable observations Economic concentration Saudi Arabia, the UAE, and Israel represent approximately 63% of the comparable total Digital maturity Very high across the GCC and Israel; substantially more varied in Iraq, Jordan, Lebanon, Palestine, Syria, and Yemen Leading first-wave markets UAE and Saudi Arabia; Israel for merchants with a suitable product and operating model Second-wave Gulf markets Kuwait, Qatar, Bahrain, and Oman Priority payment foundation International cards, local currency, mobile checkout, tokenization, and country-specific domestic debit access Important national rails mada, sarie, Aani, Jaywan, KNET, Wamd, BENEFIT, Fawri+, OmanNet, Fawran, Himyan, QMP, CliQ, JoMoPay, MASAV Faster Payments, and iBURAQ Currency landscape 13 national currencies plus a multi-currency Palestinian market Recurring-payment readiness Strongest through cards in the Gulf and Israel; inconsistent across wallets and instant-payment methods Local-acquiring relevance Worth evaluating in the largest Gulf markets and Israel once volume justifies it Regulatory structure National payment licensing and supervision; no single Middle East or GCC merchant-payments license Primary complexity

Domestic rails, merchant eligibility, sanctions, local acquiring, tax, settlement, refunds, and country-specific operations Best-fit verticals Gaming, digital goods, travel, SaaS, marketplaces, ecommerce, streaming, subscriptions, and education Primary takeaway Build one regional core, but do not build one regional checkout The economic figures above are calculations based on World Bank country data. Syria and Yemen are excluded from the comparable GDP total because their latest available observations are from earlier years. Population estimates include all 14 markets. (World Bank Open Data)

What This Guide Means by “the Middle East” “Middle East” can describe a geographic area, a sales territory, an Arabic-language market, a treasury region, or a provider’s contracting organization. Those definitions are not interchangeable. This guide includes the six GCC states, the Levant, Iraq, Iran, and Yemen. It excludes North Africa, Türkiye, Cyprus, the Caucasus, and Central Asia. The GCC is the strongest reusable commercial cluster Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, and the UAE share: * High digital connectivity * Significant use of international cards * Large expatriate customer segments * Arabic and English checkout requirements * Closely linked travel and commercial activity * Strong government investment in payment infrastructure * Relatively stable currency environments * Potentially reusable providers and technical integrations They do not share: * One domestic card system * One instant-payment system * One PSP licensing regime * One merchant eligibility standard * One tax implementation * One settlement process * One local-acquiring contract * One checkout preference The GCC is therefore a valid planning and infrastructure cluster, but not a single payment market. Israel should be treated as a standalone commercial stack Israel belongs in a geographic Middle East analysis, but its merchant requirements differ from the Arabic Gulf and Levant markets. It has: * Hebrew and English localization requirements * A separate tax and invoicing environment

* Its own acquiring and payment-system participants * Faster Payments operated through MASAV * Strong card, bank, and technology-sector infrastructure * Distinct customer behavior and regulatory institutions The Bank of Israel operates and oversees a combination of real-time gross settlement, ACH, faster retail payments, and payment-card infrastructure. It has also been opening core payment systems to additional nonbank participants. (Bank of Israel) Iran is geographically important but commercially exceptional Iran has the largest population in the defined region, but international payment access is materially affected by sanctions and limited connectivity to global payment networks. It should not be included in a standard Middle East launch merely because it represents a large consumer population. Any contemplated activity requires specialist sanctions, banking, product, and legal review. OFAC maintains an active Iran sanctions program and continues to update related designations and guidance. (OFAC) North Africa is intentionally separate Egypt, Morocco, Algeria, Tunisia, and Libya are frequently included in MENA reporting. They are excluded here because their payment structures, mobile-money environments, currencies, and African commercial relationships justify treatment in the Africa hub or a separate MENA comparison.

Why the Region Matters to International Merchants The Middle East contains three commercially important but different opportunities. High-value consumer markets Saudi Arabia, the UAE, Kuwait, Qatar, Bahrain, and Israel combine relatively high purchasing power with strong connectivity and developed banking systems. The World Bank reported internet-use rates of approximately 95% to 100% across the GCC in 2024. Saudi Arabia also reported that electronic payments represented 85% of retail transactions during 2025, up from 79% in 2024. (World Bank Open Data) These markets can support: * Ecommerce * Digital goods * Gaming * Streaming * Travel * SaaS * Education * Marketplaces * Subscription services * Premium and luxury retail Regional operating hubs The UAE is particularly valuable as a regional commercial, logistics, treasury, and contracting hub. Bahrain can be attractive for financial-services and fintech operations. Saudi Arabia offers the largest Gulf consumer market but often requires deeper local preparation. The best operating hub is not automatically the best customer market. A merchant may contract or manage providers from the UAE while prioritizing Saudi Arabia for customer acquisition. Emerging digital-payment markets Jordan, Iraq, and Palestine demonstrate that the next wave of regional payment development may come through interoperable bank transfers, mobile wallets, digital identity, and instant payments—not simply more international cards.

Jordan’s CliQ connects participating bank accounts and mobile wallets through JoMoPay. Palestine’s iBURAQ is integrated with banks and licensed electronic wallets. Iraq’s 2025–2029 National Financial Inclusion Strategy sets a policy objective of increasing the proportion of Iraqis making digital payments, but that objective should be treated as a future target rather than evidence of current merchant readiness. (JOPACC)

Which Middle Eastern Markets Should Merchants Enter First? There is no universally correct sequence. The right order depends on vertical, transaction model, customer demand, and the amount of local operating complexity the merchant is prepared to accept. The following tiers are strategic recommendations rather than claims that every merchant will receive the same result. Tier 1: Regional anchor markets United Arab Emirates Why it belongs in the first wave * Strong position as a regional operating hub * High internet use * International customer base * Developed card and banking infrastructure * Support for digital goods, travel, ecommerce, SaaS, and marketplaces * Aani instant payments * Jaywan domestic card infrastructure * Potential to reuse providers and operations elsewhere in the Gulf What must still be localized * AED pricing * Arabic and English checkout * Local acquiring decision * Jaywan and Aani availability through the selected provider * VAT reporting * Refund and settlement operations * Marketplace or stored-value licensing implications Aani was launched as the UAE’s national instant-payment platform in 2023. Jaywan entered official issuance and acceptance phases as the UAE’s national card scheme in 2026. These are important infrastructure developments, but merchants should verify actual ecommerce availability through their acquirer or PSP rather than assuming national-system availability equals merchant access. (Central Bank of the UAE) Saudi Arabia Why it belongs in the first wave

* Largest economy and consumer market in the GCC * High digital-payment adoption * Large gaming, entertainment, travel, ecommerce, and digital-service opportunity * mada domestic card relevance * sarie instant-payment infrastructure * Growing open-banking environment * Strategic importance to any serious Gulf expansion What must still be localized * SAR pricing * mada acceptance * Arabic-first customer experience * Local acquiring economics * 3-D Secure and issuer behavior * Tax and electronic invoicing * Refunds * Recurring-payment treatment * Local legal and merchant eligibility requirements mada supports POS, ATM, and ecommerce transactions, while sarie enables instant low-value transfers between domestic banks. Saudi Arabia’s open-banking program also provides a framework for approved third parties to offer services based on securely shared financial information. (Saudi Central Bank) Israel—for suitable merchant profiles Israel may belong in the first wave for: * SaaS * Business software * Technology services * B2B platforms * Ecommerce * Travel * Digital content * Marketplaces It should not be treated as a technical extension of a Gulf launch. It requires a separate operating plan covering ILS, Hebrew localization, tax, acquiring, payment access, refunds, and local customer support.

Tier 2: High-value Gulf expansion markets Kuwait Kuwait is commercially relevant because local debit behavior can make KNET more important than a cards-only global checkout would suggest. The KNET payment gateway accepts debit cards issued by participating Kuwaiti banks. Kuwait also introduced Wamd for instant transfers through domestic banking applications in 2024. (KNET Payment Gateway) Merchant recommendation: Enter after the core Gulf stack is stable, and treat KNET support as a launch requirement for consumer ecommerce unless merchant-specific research shows otherwise. Qatar Qatar combines high purchasing power with travel, hospitality, events, premium commerce, and digital-service demand. Its domestic infrastructure includes: * Himyan debit cards * Fawran instant payments * Qatar Mobile Payment * NAPS * QPAY (Qatar Central Bank) Merchant recommendation: Prioritize Qatar for travel, premium retail, digital services, and high-value customer segments. Validate whether the merchant’s provider offers the national rails required by its target audience. Bahrain Bahrain is smaller but digitally mature and can be valuable for: * Financial technology * Digital services * Gaming * SaaS * Regional business operations * Subscription services BENEFIT operates core domestic infrastructure, while BenefitPay supports merchant payments and account transfers. Fawri and Fawri+ provide domestic transfer capabilities. (Benefit)

Merchant recommendation: Use Bahrain as a cluster expansion rather than a standalone engineering program. Reuse the Gulf card core, then add Benefit-supported capabilities where commercially justified. Oman Oman should be considered by merchants with: * Travel and hospitality demand * Regional ecommerce customers * Education services * Subscription or digital-service customers * Existing Gulf infrastructure OmanNet is the domestic ATM and POS switch, and the Central Bank of Oman reports continued growth across OmanNet, ACH, and the Mobile Payment Clearing and Settlement System. (Central Bank of Oman) Merchant recommendation: Add Oman after Saudi Arabia and the UAE unless there is demonstrated product demand or strategic travel exposure.

Tier 3: Selective expansion markets Jordan Jordan is smaller than the Gulf anchors but has useful payment infrastructure and a comparatively strong digital-connectivity profile for a middle-income market. CliQ supports instant transfers between participating bank accounts and mobile wallets, while JoMoPay provides interoperability among mobile-wallet providers and participating banks. (JOPACC) Jordan may be attractive for: * Education * Gaming * Digital services * SaaS * Freelance and creator platforms * Regional marketplaces Merchant recommendation: Enter when the merchant has proven Arabic-market demand and can support lower average order values, local wallet or transfer behavior, and country-specific settlement. Iraq Iraq offers population scale and long-term digital-payment potential, but merchants should not confuse government policy targets with present commercial readiness. The Central Bank of Iraq has been developing electronic-payment regulation and a national financial-inclusion strategy, but the merchant must still validate: * Provider access * Customer payment behavior * Cash dependence * Foreign-exchange treatment * Settlement * Banking relationships * Refunds * Compliance * Regional differences inside Iraq (البنك المركزي) Merchant recommendation: Treat Iraq as a partnership-led market rather than a standard PSP switch-on. Launch only after confirming local demand, a compliant provider route, settlement, and complete payment lifecycle support.

Selective and constrained opportunities Lebanon Lebanon has connected consumers and strong demand for international products in some segments, but banking, currency, settlement, and economic conditions create significant operating risk. Merchant recommendation: Accept opportunistic cross-border demand where legally and operationally feasible. Do not commit to a full local payment model without specialist treasury, provider, and legal review. Palestine Palestine has modernizing payment infrastructure, including iBURAQ, QR Quick, and E-SADAD. Current conflict, economic contraction, banking access, settlement, and provider eligibility materially affect merchant feasibility. (سلطة النقد الفلسطينية) Merchant recommendation: Treat the market as selective and dependent on current operating conditions. Verify payment availability, customer access, sanctions screening, settlement, and continuity immediately before launch.

Watchlist or specialist-only markets Iran Iran should not be included in a standard international rollout. Its domestic payment ecosystem does not create straightforward access for merchants relying on international card networks or conventional global PSPs. Recommendation: Do not launch without specialist sanctions counsel, approved banking access, provider confirmation, and documented product eligibility. Syria Broad U.S. sanctions treatment changed during 2025, but targeted sanctions remain, and financial infrastructure, provider access, conflict risk, and settlement require specialist review. Merchants should not rely on outdated assumptions in either direction. (OFAC) Recommendation: Watchlist for ordinary commercial expansion. Yemen Conflict, banking fragmentation, sanctions screening, infrastructure, currency, and settlement make Yemen unsuitable for a standard regional launch. Recommendation: Restrict activity to legally approved, specialist use cases with appropriate banking and compliance support.

Two Practical Regional Launch Paths Consumer, gaming, travel, and ecommerce path 1. UAE 2. Saudi Arabia 3. Kuwait and Qatar 4. Bahrain and Oman 5. Jordan 6. Iraq or other selective markets only with local evidence and partners This sequence prioritizes spending power, digital readiness, travel relevance, and the ability to reuse a Gulf payment core. SaaS, B2B, and technology-platform path 1. UAE 2. Israel 3. Saudi Arabia 4. Qatar and Bahrain 5. Kuwait and Oman 6. Jordan 7. Iraq selectively This sequence places greater weight on business customers, technology adoption, recurring billing, invoicing, and regional company operations. Neither sequence should be followed mechanically. Use What to Evaluate Before Entering a New Market to validate actual product demand before assigning engineering resources.

Which Merchant Verticals Fit the Middle East? Vertical Best initial markets Payment requirements Main operating issue Opportunity Gaming and digital goods Saudi Arabia, UAE, Kuwait, Qatar, Israel Cards, domestic debit, wallets, mobile checkout, carrier billing where relevant Fraud, low-value transactions, mobile authentication, refunds Strong immediate fit SaaS and business software UAE, Israel, Saudi Arabia, Qatar, Bahrain Recurring cards, tokenization, invoicing, bank transfer for B2B Tax, failed-payment recovery, entity and contract model Strong immediate fit Travel and hospitality UAE, Saudi Arabia, Qatar, Israel, Oman, Jordan International cards, wallets, local currency, high-value authorization Refunds, cancellations, fraud, multi-currency settlement Regional-scale opportunity Retail ecommerce UAE, Saudi Arabia, Kuwait, Qatar, Israel Cards, local debit, wallets, BNPL where justified Returns, local acquiring, method ordering, address quality Strong but country-specific Marketplaces UAE, Saudi Arabia, Israel Customer payments, seller onboarding, payouts, split accounting Licensing, KYC, funds flow, settlement Attractive but complex Streaming and subscriptions Saudi Arabia, UAE, Israel, Kuwait, Qatar Tokenized recurring cards, account updater, retries Local methods may lack recurring support Strong in anchor markets Education and online learning Saudi Arabia, UAE, Jordan, Qatar, Kuwait Cards, bank payments, installments for higher values Refund policy, recurring terms, student identity Selective high-growth fit

Luxury and premium commerce UAE, Saudi Arabia, Qatar, Kuwait, Israel International cards, local debit, wallets Fraud, high-value authentication, returns High-value niche Creator and freelance platforms UAE, Saudi Arabia, Jordan, Israel Collections plus compliant seller or creator payouts Marketplace regulation, identity, payout access Selective On-demand services UAE, Saudi Arabia, Israel, Bahrain Tokenized cards, wallets, low-friction mobile checkout Local operations and licensing Local-presence dependent

The Middle East Payment Ecosystem A regional merchant transaction may pass through: 1. Customer 2. Merchant checkout 3. Gateway or payment API 4. PSP or payment facilitator 5. Local or cross-border acquirer 6. International card network, domestic card scheme, wallet, or bank-payment system 7. Issuer or customer bank 8. Clearing and settlement system 9. Acquirer or PSP balance 10. Merchant bank account or treasury structure The parts that vary most by country are: * Merchant eligibility * Domestic-method access * Acquiring * Customer authentication * Clearing * Settlement currency * Refund processing * Data requirements * Licensing * Tax * Reconciliation The Arab Monetary Fund’s Buna platform supports cross-border interbank payments in eligible regional and international currencies. This is important financial infrastructure, but it does not replace ecommerce acquiring, a customer-facing payment method, or merchant settlement arrangements. (صندوق النقد العربي) That distinction illustrates the central regional problem: Infrastructure can be interoperable at one layer while remaining fragmented at the merchant layer.

Priority Domestic Payment Infrastructure Market Important infrastructure Merchant implication Saudi Arabia mada and sarie mada may be essential for broad domestic card coverage; sarie creates future account-to-account opportunities UAE Aani and Jaywan Monitor provider access to instant payments and the national card scheme; do not assume automatic ecommerce enablement Kuwait KNET and Wamd KNET is a central consumer ecommerce consideration; Wamd expands domestic instant-transfer behavior Bahrain BENEFIT, BenefitPay, Fawri, Fawri+ Bank and mobile-payment integration may be valuable beyond international cards Oman OmanNet and MPCSS Domestic switch and mobile-clearing access should be evaluated for local reach Qatar Himyan, Fawran, QMP, NAPS Domestic debit and instant/mobile systems may increasingly affect local acceptance Jordan CliQ and JoMoPay Bank-account and mobile-wallet interoperability makes local transfer acceptance strategically relevant Israel MASAV Faster Payments and domestic card infrastructure Requires a distinct Israeli provider and settlement assessment Palestine iBURAQ, QR Quick, E-SADAD Modern infrastructure exists, but current accessibility and continuity must be validated Iraq Regulated electronic-payment providers and developing national infrastructure Use a verified local provider path; do not infer readiness from policy announcements (Saudi Central Bank)

Payment-Method Priority Matrix Method Relevant markets One-time use Recurring use Main operating issue Priority International credit and debit cards GCC, Israel, Jordan, selected other markets Strong Strong where card-on-file is supported Cross-border declines, 3DS, fraud, FX Regional foundation mada Saudi Arabia Strong Provider-dependent Domestic acceptance, acquiring, refunds Launch essential in Saudi Arabia KNET Kuwait Strong Generally not equivalent to recurring cards Redirects, refund support, local provider access Launch essential for Kuwaiti consumer ecommerce Jaywan UAE Emerging Validate Scheme rollout and provider availability Increasingly important Himyan Qatar Emerging domestic debit Validate Acquirer and PSP enablement High-value local addition OmanNet Oman Strong domestic relevance Validate Domestic routing and integration access High-value local addition BenefitPay and BENEFIT services Bahrain Strong local relevance Feature-dependent Wallet and bank-transfer operations High-value local addition Instant account-to-account payments UAE, Saudi Arabia, Kuwait, Qatar, Bahrain, Oman, Jordan, Israel, Palestine Strong potential Usually requires separate recurring capability Merchant initiation, refunds, reconciliation Cluster-specific priority Device wallets GCC and Israel Strong Card-dependent Underlying card acceptance and token support High-value regional addition Domestic mobile or bank wallets Bahrain, Qatar, Jordan, Palestine, other markets Strong Varies materially Funding source, refund model, settlement Country-specific

B2B bank transfer All accessible markets Strong Invoice-driven Matching, reconciliation, delayed confirmation Essential for B2B Direct debit Selected Gulf markets and Israel Useful Potentially strong Mandates, returns, customer protection Segment-specific Installments or BNPL Gulf and Israel where demand supports it Strong for higher values Usually not recurring-subscription replacement Credit regulation, refunds, merchant economics High-value addition after validation Carrier billing Gaming and digital goods Strong for lower values Provider-dependent Revenue share, refunds, telecom contracts Segment-specific Cash on delivery Selected cash-reliant markets Possible No Returns, failed delivery, cash operations Validate rather than assume Prepaid or vouchers Gaming and underbanked segments Strong No Distribution, fraud, refund limitations Segment-specific The purpose of this matrix is not to recommend every method. It is to distinguish the reusable regional foundation from methods whose value depends on a specific country, merchant vertical, or customer segment.

Card Strategy: Regional Foundation, National Exceptions Cards should normally form the first reusable payment layer for the Gulf and Israel. That layer should include: * International card networks * Network tokenization where available * Secure card-on-file storage * 3-D Secure support * Exemption and authentication-data handling where applicable * Merchant-initiated transaction controls * Account updater capability where supported * Smart retry rules * Issuer and BIN-level reporting * Domestic versus cross-border segmentation * Refund and chargeback workflows Cards alone are not always enough. Saudi consumers may require mada. Kuwaiti ecommerce customers may expect KNET. Qatar and the UAE are developing domestic card ecosystems. Oman and Bahrain have domestic switching and payment infrastructure that may influence coverage. A merchant should therefore separate two questions: 1. Can the checkout accept cards issued in the country? 2. Can it accept the domestic card products and routing paths customers commonly use? Those are not always the same. Local acquiring Local acquiring may: * Improve domestic routing * Reduce unnecessary cross-border processing * Support domestic debit products * Provide local-currency settlement * Improve access to local issuer relationships * Change transaction economics It does not guarantee higher authorization. Performance depends on: * Issuer mix * Merchant category * Customer behavior * Fraud configuration * Authentication * Transaction history * Routing * Provider performance

* Cross-border indicators * Order value Merchants should test local and cross-border routes using controlled traffic and compare completed orders, cost, fraud, refunds, and settlement—not authorization alone. Read Global Payment Gateway vs Local PSP and the future local-acquiring research library before committing to another provider or entity.

Instant Payments Are Growing, but They Are Not One Regional Method The Middle East now includes a growing collection of instant-payment systems: * sarie in Saudi Arabia * Aani in the UAE * Wamd in Kuwait * Fawran in Qatar * Fawri+ in Bahrain * MPCSS in Oman * CliQ in Jordan * MASAV Faster Payments in Israel * iBURAQ in Palestine These systems often share characteristics such as: * Near-real-time confirmation * Mobile or banking-app initiation * Alias-based addressing * QR functionality * ISO 20022 messaging in some markets * Domestic bank interoperability They do not necessarily share: * Ecommerce merchant APIs * Refund capabilities * Chargeback rights * Recurring-payment mandates * Foreign-merchant access * Settlement terms * Reconciliation formats * Transaction limits * Consumer-protection treatment Merchants should not create one generic “bank payment” object and assume every national system behaves the same way. The shared software abstraction may be regional. The implementation and operating model remain national.

Wallets Must Be Separated by Funding and Operating Model “Digital wallet” is too broad to guide a regional strategy. Device wallets These usually tokenize an underlying card. Merchant implications: * Card acceptance remains the foundation * The customer experience can be faster * Authentication may shift to the device * Refunds usually return through the underlying card * Recurring use depends on the token and provider model Bank-linked wallets These may initiate payments from a bank account or domestic payment system. Examples include services connected to Bahrain’s BENEFIT infrastructure, Qatar’s mobile-payment switch, and Jordan’s bank-wallet interoperability. Merchant implications: * Settlement may differ from cards * Refunds may require a separate API or manual process * Dispute rights may differ * Merchant access may require a local participant * Recurring functionality may not exist Stored-value wallets These hold customer balances. Merchant implications: * Wallet licensing and safeguarding rules matter * Refund timing can differ * Customer identity requirements may apply * Cross-border acceptance may be limited * Wallet popularity is often country- and segment-specific Mobile money Mobile money should not be assumed to have the same regional importance it has in parts of Africa. It is relevant in particular Middle Eastern markets and segments, but not a defining payment method for the high-income Gulf as a whole.

Currency, Pricing, and Foreign Exchange The regional currency landscape includes: * AED * BHD * ILS * IQD * IRR * JOD * KWD * LBP * OMR * QAR * SAR * SYP * YER * Multiple currencies in the Palestinian economy The merchant must distinguish: * Presentment currency: what the customer sees * Processing currency: what enters the payment network * Settlement currency: what the PSP or acquirer uses * Payout currency: what the merchant receives * Reporting currency: what finance uses internally These may not be the same. Recommended customer-pricing approach Use local-currency pricing in: * Saudi Arabia * UAE * Kuwait * Qatar * Bahrain * Oman * Israel * Jordan, where commercially feasible Local pricing can improve transparency and reduce the possibility that customers encounter unexpected conversion. It also creates requirements involving: * FX rates * Price rounding * Tax * Refund conversion * Settlement * Reporting * Treasury exposure Gulf currency stability does not create payment interoperability Even where exchange-rate volatility is limited, merchants still face: * Separate currencies * Separate settlement accounts * Different PSP conversion margins * Distinct refund exchange rates * Local payout rules * Different tax calculations * Country-level reporting A common currency engine can serve the region. Settlement and treasury must still be mapped country by country. Markets requiring additional treasury caution * Lebanon * Iraq * Iran * Syria * Yemen * Palestine

In these markets, currency availability, banking access, exchange controls, settlement continuity, or repatriation may be more important than the checkout conversion rate.

Local Acquiring Versus Cross-Border Processing Start with cross-border processing when: * The merchant is testing demand * The existing PSP supports the merchant and country * International cards reach enough of the target audience * Volume is uncertain * Local methods are not yet commercially justified * Settlement into the merchant’s existing structure is acceptable Evaluate local acquiring when: * Domestic debit coverage is missing * Cross-border acceptance is underperforming * Local currency or settlement is strategically important * Transaction volume is sufficient * Processing costs justify the operational investment * The local provider supports refunds, reconciliation, and reporting * The merchant has or can obtain the required contracting structure Do not confuse: * Local PSP with local acquiring * Local acquiring with local settlement * Domestic processing with domestic card support * Local payment methods with a local legal entity * Regional contracting with country-level production approval A provider can offer one of these capabilities without offering all of them. Use How to Select a PSP for International Expansion to evaluate the complete provider model.

Regulation, Licensing, and Market Access There is no single Middle East payments rulebook. The GCC has economic agreements, shared policy goals, and regional integration initiatives, but payment services remain supervised through national central banks and regulators. (GCC-SG) Merchants must identify responsibilities belonging to: * The merchant * PSP * Acquirer * Payment facilitator * Marketplace * Merchant of Record * Wallet provider * Seller * Customer Matters requiring country-level review * Payment-services licensing * Marketplace and seller onboarding * Stored-value activity * Customer-funds handling * Recurring-payment terms * Refund obligations * Card surcharging * Consumer protection * Data privacy * Data localization * National identity use * AML and KYC * Foreign-exchange controls * Cross-border settlement * Restricted merchant categories * Sanctions * Local entities * Bank accounts Sanctions and restricted-market screening Sanctions screening should not be limited to Iran. The merchant should review: * Countries * Customers * Banks * PSPs * Beneficial owners * Sellers * Payout recipients * Logistics counterparties * Product restrictions * Transaction purpose OFAC sanctions can be comprehensive or selective and are updated frequently. Current status must be checked before launch and during operation. (OFAC)

This article provides general information and does not constitute legal, regulatory, tax, sanctions, or accounting advice. Merchants should confirm applicable obligations and operating requirements with qualified advisers and relevant payment partners.

Tax and Invoicing A regional payment integration does not create a regional tax model. Merchants should review: * VAT registration * Digital-service rules * Import treatment * Marketplace liability * Tax-inclusive pricing * Customer invoice requirements * Business invoice requirements * Credit notes * Refund tax adjustments * Electronic invoicing * Merchant of Record responsibilities Saudi Arabia operates a phased electronic-invoicing system that includes structured invoice requirements and integration with ZATCA systems for affected taxpayers. The UAE has its own VAT reporting and ecommerce-supply requirements. Israel maintains a separate VAT system. (Zatca) The merchant should not infer that complying in one GCC state establishes compliance in another.

Checkout Localization Translation is only one part of localization. Reusable regional capabilities * Right-to-left interface support * Arabic typography * English fallback * Currency formatting engine * Configurable address fields * Configurable phone prefixes * Local payment-method components * Mobile-responsive redirects * Local error-message framework * Country-level experimentation * Customer-support routing Country-level configuration Gulf markets * Arabic and English * Local currency * Domestic payment methods * International and expatriate customer needs * Mobile-first layout * Local phone formats * Recognizable bank and payment logos * Clear tax and delivery treatment Israel * Hebrew and English * ILS * Right-to-left layout * Local address and phone conventions * Local tax and invoice requirements * Israeli card and bank-payment support Jordan and Palestine * Arabic-first experience * Local currency or multi-currency treatment * Mobile-wallet and bank-payment recognition * Clear redirect instructions * Support for lower bandwidth or older devices where customer research indicates a need Iraq and constrained markets * Arabic and potentially Kurdish or other language requirements * Clear payment confirmation * Strong customer support * Payment-method availability based on actual provider coverage * Conservative handling of timeouts and asynchronous status Payment-method order The same checkout order should not be used throughout the region. Examples:

* Saudi Arabia: mada and locally important card options may need prominent placement. * Kuwait: KNET may deserve priority over a generic international-card button. * Bahrain: BenefitPay may be prominent for suitable customers. * Israel: cards and bank-based options should be tested within a separate local checkout. * Jordan: CliQ or wallet options may be relevant for particular segments. Order methods by completed orders and customer contribution—not by which logo is easiest to add.

Authentication and Customer Verification Customers may encounter: * 3-D Secure * OTP * Banking-app approval * Wallet authentication * QR confirmation * Device biometrics * Redirects * Identity verification * Seller or beneficiary KYC The merchant controls: * When authentication is requested * Checkout preparation * Device and browser support * Messaging * Timeout handling * Recovery after redirect * Duplicate-payment prevention * Webhook processing * Customer support The merchant does not fully control: * Issuer challenge decisions * OTP delivery * Banking-app availability * Customer-device configuration * Issuer risk models * Bank downtime Measure authentication success separately from authorization and order completion.

Recurring Payments and Subscription Readiness Cards provide the most reusable recurring-payment foundation across the accessible Middle East. A subscription stack should support: * Initial customer authentication * Stored payment credentials * Merchant-initiated transaction indicators * Token lifecycle management * Account updater where available * Soft-decline retries * Payment-method replacement * Renewal notifications * Grace periods * Cancellation * Refunds * Dunning by country and language Do not assume popular local methods support subscriptions Instant payments, debit gateways, and wallets may support: * One-time payment only * Customer-initiated renewal * Scheduled transfer * Mandate-based payment * No recurring ecommerce function These are different operating models. Cluster Subscription readiness Primary recommendation UAE and Saudi Arabia Strong through tokenized cards; local methods require validation Build cards first, then test local recurring options Kuwait and Qatar Strong card opportunity; domestic debit may be one-time or provider-dependent Preserve a card-on-file fallback Bahrain and Oman Cards plus selected bank or wallet capabilities Confirm mandates and refunds Israel Strong standalone card and bank environment Local provider and tax configuration Jordan Possible through cards; wallet and account methods vary Target suitable customer segments Iraq, Lebanon, Palestine Operationally variable Do not launch subscriptions until collection and recovery are proven Iran, Syria, Yemen

Not suitable for standard regional recurring deployment Specialist review required

Refunds, Reversals, and Disputes A payment method should not be considered ready merely because it can collect money. Before launch, verify: * Full refunds * Partial refunds * Multiple partial refunds * Void or reversal support * Refund time limits * Refund currency * Original-payment-method rules * Customer notification * Dispute model * Chargebacks * Evidence submission * Provider fees * Refund reconciliation * Failed refund recovery Card payments Cards generally provide standardized network dispute and refund frameworks, but acquirer processes, timing, data requirements, and customer communication vary. Instant bank payments An instant payment may be final at the payment-system level. A merchant refund may therefore be a separate credit transfer rather than a reversal of the original transaction. That changes: * Customer communication * Fraud exposure * Reconciliation * Reference matching * Refund timing * Support procedures Wallets Refund support depends on: * Funding source * Wallet rules * Customer-account status * PSP integration * Merchant eligibility * Cross-border restrictions Travel and high-return ecommerce Merchants with frequent cancellations or returns should treat refund capability as a payment-method selection criterion, not a post-launch operational detail.

Settlement, Treasury, and Repatriation Payment success and usable merchant funds are separate events. A complete flow must answer: 1. Did the customer complete the payment? 2. Did the provider confirm it? 3. Was the transaction cleared? 4. Was it settled to the PSP or acquirer? 5. Was the merchant paid? 6. In which currency? 7. Were fees and FX deducted? 8. Can finance reconcile the payout? 9. Can the funds be moved or used? What can be centralized * Treasury policy * Reporting currency * FX governance * Provider balance monitoring * Settlement expectations * Reconciliation software * Exception-management procedures * Cash forecasting What may remain local * Settlement bank * Local currency balance * Domestic bank account * Legal entity * Payout schedule * Reserve * Repatriation * Tax deduction * Transaction-level reporting * Bank reference formats Treasury priorities by cluster Saudi Arabia and UAE Evaluate local settlement once volume justifies it. Compare: * FX cost * Payout timing * local expenses * refund funding * reserve treatment * reconciliation quality Smaller GCC markets Centralized contracting may be possible, but each domestic method can still have separate settlement and reporting. Israel Maintain a separate ILS, tax, settlement, and reconciliation model. Jordan and Iraq Validate local-currency settlement, bank access, FX conversion, and usable-fund timing before launch. Lebanon, Palestine, Iran, Syria, and Yemen Treasury feasibility may determine whether the market is launchable at all.

Fraud and Risk The region should not be assigned one fraud score. Risk varies by: * Country * Vertical * Customer type * Device * Payment method * Domestic versus cross-border card * Transaction value * Digital versus physical delivery * New versus returning customer * Account age * Shipping * Refund behavior Important risk patterns Gaming and digital goods * Account takeover * Stolen cards * Rapid low-value attempts * Resale of digital items * Refund abuse * Friendly fraud Travel * High transaction values * Long delay between purchase and fulfillment * Cancellation disputes * Cross-border customers * Card-testing and stolen credentials Ecommerce * Address mismatch * Reshipping * Promotion abuse * Return fraud * Account takeover Marketplaces * Seller identity fraud * Collusion * Payout diversion * Triangulation * Refund abuse * Restricted products Regionalize the platform, localize the rules Regional capabilities: * Device intelligence * Behavioral analysis * Account protection * Velocity controls * Sanctions screening * Case management * Chargeback tooling * Machine-learning infrastructure Country configuration: * Thresholds * Payment-method rules * authentication * local identity signals * delivery assumptions * refund policy * manual review * high-risk issuer or route treatment

Which Provider Model Works Best? One global PSP Best when: * Testing regional demand * Cards cover most target customers * The PSP supports required currencies * Merchant eligibility is confirmed * Settlement is acceptable * Local methods are not yet essential Main risk: * “Country support” may not include domestic debit, local acquiring, settlement, or the merchant’s category. Global PSP plus local specialists Best when: * One provider supplies the regional card foundation * Local providers add mada, KNET, BenefitPay, domestic wallets, or local acquiring * The merchant has enough volume to justify operational complexity This is the most realistic long-term model for many large regional merchants. Regional PSP Best when: * The provider has meaningful Gulf coverage * Contracts and support can be centralized * Local-method depth is stronger than a global-only provider Main risk: * Regional branding does not guarantee equal capabilities in every country. Merchant of Record Potentially useful for: * Digital products * SaaS * Streaming * Smaller merchants * Markets where tax and seller responsibilities would otherwise be burdensome The merchant must verify: * Who is seller of record * Tax responsibility * Refund ownership * Chargeback responsibility * Customer support * Settlement * Merchant control * Pricing * Data access Read Merchant of Record vs PSP. Payment orchestration Appropriate when: * Several PSPs are active * Routing has a defined economic purpose * Failover is operationally supported

* Tokens can be used across routes * Reporting fragmentation is becoming costly * Markets need configurable provider logic Orchestration should not be added solely because the merchant operates in several countries. Read Payment Orchestration for International Expansion.

What Should Be Shared—and What Must Remain Local? Capability Regional Cluster-level Country configuration Separate local implementation or review Core payment API Yes

Payment-state model Yes

Token vault Yes

Card integration Yes

Fraud platform Yes

Analytics Yes

Experimentation Yes

Currency engine Yes

Localization framework Yes

Provider abstraction Yes Yes

Reconciliation tooling Yes Yes Yes

Customer-support platform Yes Yes Yes

Arabic right-to-left interface

Gulf and Arab cluster Yes

International-card acquiring

Often Yes Sometimes Domestic debit

Yes Instant-payment acceptance

Yes Payment-method ordering

Currency pricing

Authentication configuration

Local acquiring

Yes Local settlement account

Yes Legal entity

Legal review Payment licensing

Legal review Tax registration

Tax review Electronic invoicing

Country implementation Sanctions analysis Yes

Yes Specialist review Refund workflow

Yes Yes Sometimes Merchant-category approval

Provider and regulatory review The best regional architecture avoids both extremes: * Rebuilding the payment stack for every country * Assuming one Gulf or Middle East integration covers every market

Regional Market-Entry Sequence Stage 0: Validate demand Markets Any country under consideration. Capabilities * Existing PSP * International cards * Local currency where possible * Basic language localization * Country-level analytics * Legal and sanctions screening Go criteria * Meaningful qualified traffic * Acceptable completed-order rate * Product-market fit * Confirmed merchant eligibility * Viable settlement * Manageable support demand No-go criteria * Customers cannot use available methods * Provider access is uncertain * Settlement is unusable * Compliance cannot approve the model * Refunds cannot be operated * Payment economics are negative Use What to Evaluate Before Entering a New Market. Stage 1: Launch anchor markets Recommended markets * UAE * Saudi Arabia * Israel where commercially relevant Required capabilities * Local currency * Arabic and English; Hebrew for Israel * International cards * mada for Saudi Arabia where required * 3DS and redirect recovery * Tokenization * Refunds * Settlement * Reconciliation * Customer support * Country-specific tax review Use How to Expand Payments Into a New Country. Stage 2: Expand through the Gulf cluster Recommended markets * Kuwait * Qatar * Bahrain * Oman Required additions * KNET * Qatar domestic-method evaluation * BENEFIT or BenefitPay evaluation * OmanNet or local-payment evaluation * Country currencies * Local checkout ordering * Separate settlement reporting Go criteria * Core Gulf components are reused * Incremental integration cost is controlled

* Local method has a defined customer or revenue contribution * Finance can reconcile the new provider Stage 3: Add country-specific acquiring and optimization Focus * Local acquiring * Domestic routing * Domestic wallets * Instant payments * Cost optimization * Provider redundancy * Country-specific fraud rules Go criteria * Sufficient volume * Measurable problem with existing route * Complete refund and settlement support * Expected benefit exceeds integration and operating cost Stage 4: Enter exception markets Potential markets * Jordan * Iraq * Lebanon * Palestine * Other constrained markets Requirements * Local evidence * Approved provider * Compliance review * Treasury and banking model * Local customer support * Operational continuity * Defined pause and exit conditions Iran, Syria, and Yemen should remain outside an ordinary commercial rollout unless specialist legal, banking, and operational approval is obtained. Use the International Payment Expansion Checklist before every launch stage.

Recommendations by Merchant Stage Testing the region * Start with UAE or Saudi Arabia based on customer demand * Use the existing PSP * Enable local currency * Measure issuer and country performance * Avoid unnecessary provider additions * Validate refunds and settlement before marketing aggressively Launching several Gulf countries * Build one card and tokenization core * Add country configuration * Integrate essential domestic methods * Establish regional provider governance * Standardize reconciliation * Create Arabic and English support workflows Moving from cross-border to local acquiring * Compare completed orders, not only authorization * Include FX, fees, fraud, chargebacks, settlement, and operating cost * Run controlled routing tests * Confirm token portability * Avoid a local entity unless the economic benefit is clear Consolidating providers * Identify duplicate coverage * Preserve providers with unique local methods or acquiring * Measure provider cost per completed order * Assess contract concentration * Standardize data before reducing redundancy Optimizing an established operation * Segment results by country and domestic versus cross-border route * Test payment-method order * Improve authentication recovery * Add account updater and retry logic * Evaluate instant-payment merchant acceptance * Reduce reconciliation exceptions * Optimize refunds and customer communication Read How to Build a Global Payments Strategy for governance beyond the region.

How to Measure Regional Payment Performance Do not use one blended “Middle East authorization rate.” A large Saudi or UAE business can hide problems in every smaller market. Country-level metrics * Payment-method visibility rate Customers shown the method ÷ eligible checkout sessions * Payment-method selection rate Customers selecting the method ÷ customers shown the method * Payment-method completion rate Successful payments ÷ customers selecting the method * Authorization rate Authorized card attempts ÷ submitted card authorization attempts * Payment success rate Successful payments ÷ valid payment attempts * Completed-order rate Paid completed orders ÷ checkout starts * Authentication success Successful authentications ÷ initiated authentications * Technical-error rate Technical failures ÷ payment attempts * Refund success Completed refunds ÷ refund requests * Chargeback rate Use the relevant card-network or operational denominator consistently. * Cost per successful payment Processing, method, fraud, FX, and operating cost ÷ successful payments * Settlement delay Time from customer payment to usable merchant funds * Reconciliation exception rate Unmatched transactions ÷ transactions requiring reconciliation * Support-contact rate Payment-related contacts ÷ completed or attempted orders Regional operating metrics * Time to launch a new country * Percentage of payment infrastructure reused * Number of active PSPs * Provider overlap * Local-method contribution * FX cost * Treasury delay

* Operational cost by country * Percentage of transactions with complete reconciliation * Percentage of payment methods with automated refunds Required segmentation * Country * Market cluster * Payment method * Provider * Acquirer * Issuer * Device * Customer type * Currency * Domestic versus cross-border processing * New versus returning customer * Order value * Merchant vertical * Checkout version

Middle East Regional Launch Checklist Scope and opportunity * Define which Middle Eastern countries are actually in scope * Separate the Gulf plan from Israel and constrained markets * Confirm customer demand by country * Confirm product and merchant-category fit * Select first-wave and second-wave markets * Define markets that are explicitly deferred Provider and acceptance * Confirm merchant eligibility * Confirm production—not theoretical—country support * Confirm international-card acceptance * Confirm domestic debit requirements * Confirm wallet and instant-payment availability * Review local acquiring * Review provider redundancy * Document refund and dispute support Currency and finance * Select presentment currencies * Confirm processing and settlement currencies * Confirm payout currencies * Model FX * Confirm reserves and payout timing * Validate usable-fund access * Validate repatriation where relevant * Build transaction-to-payout reconciliation Legal, compliance, and tax * Review payment regulation * Review entity and bank-account requirements * Review sanctions * Review data requirements * Review marketplace or stored-value implications * Review VAT and digital-service obligations * Review invoicing and electronic-invoicing requirements * Confirm merchant and provider responsibilities Checkout and technology * Configure Arabic and right-to-left support * Configure Hebrew where relevant * Localize currency and fields * Order methods by country * Test mobile redirects * Test 3DS and OTP recovery

* Test duplicate prevention * Test asynchronous status * Test refunds and reversals * Test webhook reliability * Confirm token and recurring-payment behavior Operations * Prepare country-specific customer support * Prepare fraud rules * Prepare dispute handling * Prepare refund communication * Assign finance and compliance owners * Define launch gates * Define pause and exit criteria * Schedule post-launch reviews * Link each launch to the appropriate country payment guide

Recommended Country-Guide Handoffs Country Why a dedicated guide is necessary Unique payment premise Main operating challenge Publication priority Saudi Arabia Largest Gulf opportunity mada, sarie, high digital-payment use, localization Local acquiring, tax, e-invoicing, recurring payments Highest UAE Regional hub and first-entry market Aani, Jaywan, international customer base Provider model, VAT, marketplace rules Highest Kuwait Local debit can materially affect conversion KNET and Wamd Domestic method access and refunds Highest Qatar High-value, travel-oriented market Himyan, Fawran, QMP Small scale versus integration effort High Bahrain Strong fintech and domestic payment infrastructure BENEFIT, BenefitPay, Fawri+ Wallet, bank-transfer, and settlement operations High Oman Important Gulf cluster extension OmanNet and MPCSS Provider coverage and local-method economics High Israel Separate high-value operating environment Cards, faster payments, technology economy Hebrew, tax, acquiring, regulation Highest Jordan Bridge between Gulf digital commerce and emerging account payments CliQ and JoMoPay interoperability Scale, local settlement, customer economics High Iraq Large long-term opportunity with substantial complexity Policy-led digital-payment transition Cash, provider access, regulation, settlement High research priority Palestine Modernizing domestic infrastructure under severe operating constraints iBURAQ and QR payments Conflict, continuity, settlement, eligibility Update frequently Lebanon

Digitally connected customers but difficult financial environment Multi-currency customer behavior Banking, currency, settlement Selective Iran Large domestic market disconnected from normal global payment access Domestic ecosystem and population scale Sanctions and banking access Specialist research only Yemen Long-term mobile and digital potential Underdeveloped and fragmented environment Conflict, banking, compliance Watchlist Syria Changing sanctions context but limited standard merchant access Re-emerging market uncertainty Banking, infrastructure, sanctions Watchlist Each guide should link back to: * Global Payments Atlas * Explore Regional Hubs * Explore Country Payment Guides * This Middle East regional hub * How to Expand Payments Into a New Country * International Payment Expansion Checklist

Final Merchant Recommendation Gaming, digital-goods, travel, SaaS, marketplace, ecommerce, streaming, and education merchants should prioritize the Middle East when they have demonstrated customer demand in the Gulf or Israel and can support local currency, mobile checkout, authentication, refunds, and regional customer service. For most consumer merchants: 1. Begin with the UAE and Saudi Arabia. 2. Establish international cards, tokenization, fraud controls, local currency, Arabic and English checkout, and complete refund and settlement operations. 3. Add mada in Saudi Arabia and verify access to UAE domestic infrastructure through the selected provider. 4. Expand next into Kuwait, Qatar, Bahrain, and Oman, adding KNET and other domestic methods only where the customer and revenue contribution justifies them. 5. Treat Israel as a separate high-value stack, not as an extension of the Gulf rollout. 6. Add Jordan selectively once the merchant can support bank-wallet interoperability and local economics. 7. Enter Iraq, Lebanon, or Palestine only after local provider, compliance, treasury, and continuity risks are resolved. 8. Defer Iran, Syria, and Yemen from an ordinary regional rollout unless specialist legal, banking, and product conditions are met. Reuse: * Payment API * Tokens * Card logic * Fraud platform * Analytics * Currency engine * Localization framework * Reporting * Reconciliation * Provider governance Localize or separately implement: * Domestic debit * Instant payments * Wallets

* Acquiring * Currency * Language * Payment-method order * Authentication * Refunds * Settlement * Tax * Invoicing * Sanctions controls Accelerate expansion when a country demonstrates: * Qualified customer demand * Strong completed-order economics * Reliable settlement * Complete refund support * Sustainable fraud performance * Reusable infrastructure * Manageable support and compliance requirements Pause expansion when: * Provider eligibility remains uncertain * Customers cannot use the enabled methods * Refunds or reconciliation are incomplete * FX and settlement eliminate the margin * Compliance conditions change * Operational continuity cannot be maintained The correct regional strategy is not to make every country behave like the UAE or Saudi Arabia. It is to build a payment platform strong enough to reuse—and disciplined enough to recognize when a market requires a different route.

The following draft applies the regional framework, market-prioritization requirements, operating-model analysis, and editorial standards in the uploaded Middle East brief. Regional Editorial Brief Region The Middle East Working title How to Build the Perfect Payment Stack for the Middle East Geographic and commercial scope This guide uses a commercial payments definition of the Middle East rather than the broader Middle East and North Africa classification. Included markets * Bahrain * Iran * Iraq * Israel * Jordan * Kuwait * Lebanon * Oman * Qatar * Saudi Arabia * State of Palestine, represented in international datasets as West Bank and Gaza * Syria * United Arab Emirates * Yemen Excluded markets * Egypt and the rest of North Africa: covered in the Africa regional hub or a future MENA comparison. * Türkiye: treated as a cross-regional market with stronger editorial connections to Europe and Asia. * Cyprus: covered within Europe. * The Caucasus and Central Asia: covered within Asia or a future Eurasia cluster. * Overseas territories: none are included. The guide covers sovereign states and the Palestinian payment market. It recognizes the six-country Gulf Cooperation Council as an important commercial and payment-infrastructure cluster, but it does not imply that the GCC has one payments license, one acquiring market, or one merchant-operating model.

A merchant’s Middle East operating map may differ from this geographic map. Provider contracts, sanctions, treasury arrangements, tax registrations, customer-support operations, and merchant eligibility may produce a substantially narrower commercially accessible region. Regional evidence anchors 1. The 12 included markets with reasonably comparable 2024 World Bank GDP data represent approximately $3.7 trillion in nominal GDP. Saudi Arabia, the UAE, and Israel account for roughly 63% of that total. Syria and Yemen are excluded from this calculation because their latest available World Bank GDP observations are from earlier years. This makes the region economically concentrated rather than uniformly attractive. (World Bank Open Data) 2. The included markets had an estimated population of approximately 296 million in 2024, but population and immediately addressable payment opportunity are distributed very differently. Iran, Iraq, and Yemen represent about 60% of the included population, while the most accessible high-value digital-commerce opportunities are more concentrated in the Gulf and Israel. The latter is an editorial inference based on economic scale, connectivity, payment infrastructure, provider accessibility, and sanctions—not population alone. (World Bank Open Data)

3. Internet use in the six GCC countries ranged from approximately 95% to 100% of the population in 2024. In contrast, the World Bank’s Global Findex study found that internet use averaged 68% across the low- and middle-income Arab economies it surveyed, while fewer than 30% of adults made or received a digital payment in 2024. The Gulf should therefore not be used as a proxy for the rest of the Middle East. (World Bank Open Data) 4. National payment infrastructure is advancing quickly but along separate country tracks. Saudi electronic payments represented 85% of retail-payment transactions in 2025. The UAE has introduced Aani instant payments and the Jaywan domestic card scheme, while Kuwait, Qatar, Bahrain, Oman, Jordan, Israel, and Palestine operate or are developing their own domestic switches, instant-payment systems, wallets, and card infrastructure. (Saudi Central Bank) Editorial position Merchants should approach the Middle East as a portfolio of concentrated digital-payment opportunities connected by reusable infrastructure, rather than as one regional acquiring and checkout market. The resulting operating recommendation is to build one configurable regional payment core, enter through two or three anchor markets, and add domestic rails, local acquiring, tax workflows, and settlement structures only where country-level economics justify them. Primary reader This guide is written for: * Gaming and digital-goods companies * Retail ecommerce businesses

* SaaS and subscription companies * Marketplaces * Travel and hospitality merchants * Streaming and media services * Education platforms * Payment, finance, treasury, compliance, and regional-expansion teams It is most useful to merchants that are: * Choosing their first Middle Eastern market * Planning a multi-country Gulf rollout * Adding local payment methods * Evaluating local acquiring * Consolidating or expanding PSP relationships * Moving from cross-border testing to local operations * Optimizing an established regional payment portfolio Search intent The reader wants to determine: * Which Middle Eastern countries should be entered first * Whether a Gulf-first strategy is appropriate * Which markets can share infrastructure * Which markets require separate treatment * Whether one PSP can support a regional launch * Which domestic methods materially affect customer reach * Where local acquiring may be worth evaluating * Which markets should remain selective or be deferred * What must be validated before committing engineering and operating resources Writer influence Ben Thompson’s strategic-framework tradition The guide borrows high-level strengths including: * Separating reusable platforms from local distribution layers * Explaining operating leverage * Distinguishing regional scale from country-level control * Organizing recommendations around merchant archetypes * Making direct market-sequencing decisions It does not imitate recognizable language or personal style. Regional premise

* This region matters because: a small group of markets combines substantial spending power, high connectivity, growing digital-payment usage, travel demand, and government-backed payment modernization. * It should not be treated as one market because: domestic networks, acquiring, licensing, currencies, tax, settlement, sanctions, and customer behavior remain national. * The strongest opportunity is: a Gulf-first rollout led by Saudi Arabia and the UAE, with a separate Israel strategy where the merchant’s product and operating model fit. * The most reusable capability is: a provider-neutral card, tokenization, fraud, reporting, and localization layer. * The most important exception is: domestic debit and instant-payment infrastructure must be accessed and operated country by country. * The highest-priority verticals are: gaming, digital goods, travel, SaaS, marketplaces, subscription services, ecommerce, and education. * First-wave markets: UAE and Saudi Arabia for most consumer merchants; UAE and Israel for many B2B and SaaS merchants. * Payment priority: international cards first, followed by the domestic methods that materially expand customer access or performance in each anchor market. * The operating model must be tested against: merchant eligibility, local acquiring, refunds, recurring billing, settlement, tax, sanctions, and reconciliation. * Introduction influence: strategic system design and market concentration. Market clusters Cluster Included markets

Defining merchant characteristic Likely stage Gulf anchor markets Saudi Arabia, UAE Greatest combination of scale, connectivity, payment modernization, and regional operating relevance First wave Smaller high-income Gulf markets Kuwait, Qatar, Bahrain, Oman Strong digital access and local purchasing power, but separate domestic rails and smaller addressable populations Second wave Advanced standalone market Israel Mature digital economy and payment infrastructure requiring a distinct language, tax, acquiring, and operating strategy First or second wave by vertical Digitally connected bridge market Jordan Smaller commercial scale but established interoperable bank and mobile-wallet infrastructure Selective second or third wave Large transition market Iraq Substantial population and policy-led digital-payment development, with greater cash, provider, compliance, and operating complexity Selective Financially or operationally constrained Levant Lebanon, Palestine High digital connectivity in parts of the market but major economic, settlement, conflict, or operating constraints Selective Restricted or exception markets Iran, Syria, Yemen Material sanctions, conflict, provider-access, currency, settlement, or financial-infrastructure barriers Watchlist or specialist-only Anchor countries * Saudi Arabia: largest commercial anchor and essential for regional consumer scale. * United Arab Emirates: strongest regional operating hub and practical first market for many international merchants.

* Israel: high-value standalone opportunity for SaaS, B2B, ecommerce, digital services, and technology businesses. * Kuwait: important because KNET can materially change a consumer merchant’s payment mix. * Qatar: smaller population but high purchasing power, travel relevance, and developing domestic infrastructure. * Jordan: important as a regional test of interoperable account and mobile-wallet payments outside the high-income Gulf. Priority verticals * Gaming and digital goods * SaaS and business software * Travel and hospitality * Retail ecommerce and luxury goods * Marketplaces * Streaming and subscriptions * Education technology * Creator and digital-content platforms Payment strategy Share regionally * Core payment API * Card integration * Token vault * Payment-state model * Fraud and risk platform * Experimentation framework * Currency engine * Localization framework * Reporting and analytics * Reconciliation tooling * Customer-support workflows * Provider-management standards Configure by country * Local currency * Arabic, English, Hebrew, or other language presentation * Payment-method order * Authentication treatment * Address, phone, and identity fields * Refund rules * Tax and invoice fields * Fraud thresholds * Customer communications Implement separately where required * Domestic debit schemes * Instant-payment merchant acceptance * Local acquiring * Local bank accounts * Local entity or contracting arrangements * Wallet integrations * Tax registrations * Electronic invoicing

* Sanctions and restricted-party workflows * Country-specific reconciliation Recommended article structure Regional payment-stack architecture combined with market-entry sequencing Merchant recommendation Merchants entering the Middle East should begin by validating Saudi Arabia, the UAE, and—where relevant—Israel; prioritize cards and the domestic rails that influence customer access; reuse tokenization, fraud, reporting, and orchestration capabilities; localize currency, language, payment ordering, authentication, and refunds; and validate eligibility, settlement, tax, sanctions, and unit economics before committing significant regional resources.

Editorial and SEO Recommendations Title options 1. How to Build the Perfect Payment Stack for the Middle East 2. Middle East Payment Expansion: What to Standardize, Localize, and Launch First 3. Expanding Payments Into the Middle East: A Merchant’s Market-by-Market Strategy 4. The Middle East Payment Stack: From Gulf Anchors to Local Payment Rails 5. Which Middle Eastern Payment Markets Should Merchants Enter First? Recommended SEO title

Recommended H1 How to Build the Perfect Payment Stack for the Middle East Meta description Build a Middle East payment strategy covering Saudi Arabia, the UAE, GCC markets, Israel, local methods, acquiring, settlement, regulation, and launch sequencing. URL slug /global-payments-atlas/middle-east/ Primary keyword Middle East payment expansion Secondary keywords * Payments in the Middle East * Middle East payment methods * GCC payment methods * Expand into the Middle East * Middle East payment gateway * Local payment methods Middle East * Saudi Arabia and UAE payment strategy * GCC ecommerce payments * Middle East PSP * Middle East local acquiring Related entities * Gulf Cooperation Council * Saudi Central Bank * Central Bank of the UAE * mada * sarie * Aani * Jaywan * KNET * BENEFIT * OmanNet * Himyan * Fawran * CliQ * JoMoPay * Bank of Israel * Palestine Monetary Authority * Buna * Local acquiring * Payment orchestration * Merchant of Record Search intent Strategic commercial research with provider, infrastructure, and market-entry intent. Article excerpt The Middle East’s largest payment opportunities are concentrated in a handful of markets, but its payment infrastructure remains national. Learn which countries merchants should launch first, which domestic methods matter, and what can be reused across the region. Social description

Should your Middle East payment expansion begin in the UAE, Saudi Arabia, Israel, or a smaller Gulf market? Explore a country-by-country strategy for payment methods, acquiring, settlement, infrastructure, and launch sequencing.

Internal-Link Recommendations Primary Atlas links * Global Payments Atlas * Explore Country Payment Guides * Explore Regional Hubs Market-decision resources * How to Expand Payments Into a New Country * International Payment Expansion Checklist * What to Evaluate Before Entering a New Market * How to Build a Global Payments Strategy Provider resources * One Global PSP vs Multiple Local PSPs * How Many PSPs Does a Global Merchant Need? * How to Select a PSP for International Expansion * Global Payment Gateway vs Local PSP * Merchant of Record vs PSP Infrastructure resources * Payment Infrastructure for Global Expansion * Payment Orchestration for International Expansion * How to Launch Payments Without Rebuilding Your Stack

Recommended Original Assets 1. Middle East Payment-Stack Architecture Purpose: Show which technical layers can be reused and where country-specific infrastructure enters the transaction. Intended reader: Payments, product, and engineering teams. Required data: * Shared API layer * Tokenization * Fraud * Currency and localization * PSP and acquiring layer * Domestic schemes by country * Settlement and reconciliation Format: Layered architecture diagram. Placement: After the regional snapshot. Decision supported: Whether a merchant needs separate country stacks or a configurable regional platform. Suggested caption: One regional payment core can support several Middle Eastern markets, but domestic acceptance, acquiring, and settlement remain country-specific. Alt text: Diagram showing a shared merchant payment platform connecting to country-specific card schemes, instant-payment systems, acquirers, and settlement accounts across the Middle East. 2. Market-Prioritization Matrix Purpose: Compare commercial attractiveness with operating complexity. Intended reader: Executives, expansion teams, and payment leaders. Required data: * Commercial scale * Digital readiness * Provider access * Domestic-method importance * Regulatory complexity * Treasury complexity * Reusability Format: Two-axis matrix. Placement: Before the country-prioritization section. Decision supported: Which markets belong in the first, second, selective, or watchlist waves. Suggested caption:

The largest market is not always the best first launch: prioritize the combination of opportunity, payment feasibility, and infrastructure reuse. Alt text: Matrix positioning Middle Eastern payment markets by commercial opportunity and merchant operating complexity. 3. Domestic Payment-Rail Footprint Purpose: Visualize the fragmented national infrastructure hidden beneath the regional label. Intended reader: Payment and provider-selection teams. Required data: * mada * sarie * Aani * Jaywan * KNET * Wamd * BENEFIT * OmanNet * Himyan * Fawran * CliQ * JoMoPay * MASAV Faster Payments * iBURAQ Format: Annotated regional map or country-card grid—not a decorative political map. Placement: Before the payment-method matrix. Decision supported: Which integrations can be shared and which must be sourced locally. Suggested caption: The Middle East contains multiple domestic card, wallet, and instant-payment systems; regional provider coverage does not guarantee access to each one. Alt text: Map identifying important domestic card and instant-payment systems across Gulf, Levant, and Israeli payment markets.

Visual Recommendations Hero concept

Avoid: * Skylines * Flag collages * Decorative maps * Generic credit cards * Desert imagery Diagram concept A “shared core versus local edge” diagram: Shared core: API, tokens, fraud, analytics, currency, reporting Local edge: domestic methods, acquiring, tax, settlement, language Chart concept A bar chart comparing 2024 GDP across the included markets, accompanied by a note that economic opportunity is highly concentrated. Use only comparable-year data and separate markets lacking current observations. Map concept A payment-infrastructure map rather than a geography map. The map should identify national rails and market clusters, not merely country borders.

Human Review Recommendations Reviewer Priority Review focus Middle East payments specialist Required before publication Country classification, payment rails, market sequencing Saudi payments specialist Required before publication mada, sarie, acquiring, e-invoicing, merchant access UAE payments specialist Required before publication Aani, Jaywan, local acquiring, licensing Compliance and sanctions counsel Required before publication Iran, Syria, Yemen, Palestine, restricted parties Tax reviewer Required before publication VAT, digital services, e-invoicing, marketplace rules Treasury specialist Strongly recommended Currency, settlement, reserves, repatriation Payment operations specialist Strongly recommended Refunds, disputes, reconciliation, support Fraud specialist Strongly recommended Vertical risk patterns and authentication Israel payments specialist Strongly recommended Payment systems, acquiring, tax, localization Arabic localization specialist Strongly recommended RTL checkout, terminology, customer messaging Country specialists for Iraq and Jordan Optional enhancement Local provider and customer-payment behavior

Recommended First-Hand Contribution

The contribution should explain: * What the merchant initially expected to reuse * Which country exception emerged

* What was measured * What future launches reused from the experience Do not include performance percentages unless they are based on approved, representative merchant data with defined denominators.

Final Fact-Check List Verify immediately before publication: * Included country list * 2024 GDP values and aggregate calculation * 2024 population values * Share represented by Saudi Arabia, UAE, and Israel * Current 2026 conflict and economic outlook * Saudi electronic-payment share * mada ecommerce availability * sarie capabilities * Aani merchant-payment availability * Jaywan rollout status and ecommerce acceptance * KNET refund and recurring capabilities * Wamd availability * BENEFIT and BenefitPay capabilities * OmanNet and MPCSS capabilities * Himyan, Fawran, and QMP availability * CliQ and JoMoPay merchant-payment support * Israel faster-payment and acquiring access * iBURAQ and QR Quick availability * Iraq payment-provider and regulatory status * Local-acquiring requirements in every market * Local-entity and bank-account requirements * Tax registrations * Saudi electronic-invoicing phases * UAE ecommerce VAT reporting * Israeli VAT treatment * Sanctions affecting Iran, Syria, Yemen, Palestine, banks, or counterparties * Currency controls and repatriation * Provider production eligibility * Recurring-payment support * Refund support

* Every country guide’s publication and last-reviewed status