Taking payments in the Gulf and Iraq: what to plan for
Payment integration is usually the longest approval in an app project and the one most often started last. The methods customers expect also differ by market.
Key takeaways
- Payment methods differ by market; cash on delivery remains significant in Iraq and is an operational commitment.
- Digital content consumed in-app generally must use platform in-app purchase, which changes flow, pricing and margin.
- Gateway onboarding takes weeks and is free to start early; begin it in week one of the project.
- The hard case is a payment with an unknown result: never double charge, always give a checkable state.
Payment integration across the Gulf and Iraq involves three separate problems: choosing methods customers will actually use in each market, satisfying the platform rules about what must go through in-app purchase, and completing gateway onboarding, which regularly takes longer than the technical work. Start the approvals in week one of the project, not when the feature is ready to test.
Methods differ by market
- Cards are the default across the UAE and Saudi Arabia, with local card schemes carrying meaningful share alongside international ones.
- Digital wallets and bank-transfer flows have grown quickly, and in some segments they are preferred over entering card details.
- Cash on delivery remains significant in parts of the region, particularly Iraq, and an app that cannot offer it excludes real demand. It is an operational commitment as much as a payment method, since it requires reconciliation and carries a return rate.
- Instalment providers are widely used for higher-value purchases and often materially improve conversion at those price points.
The platform rule that catches teams out
Digital content and services consumed inside the app generally must use the platform's in-app purchase system, with its commission, rather than your own gateway. Physical goods and services delivered in the real world use your gateway. The boundary between these is where apps get rejected, and a subscription unlocking in-app features is squarely on the in-app purchase side. Decide this before designing the checkout, because it changes the flow, the pricing and the margin.
Onboarding is the schedule risk
Gateway approval requires trade licence documentation, bank details, sometimes a site visit or a compliance review, and it varies considerably by provider and by country. Several weeks is normal and longer is not unusual. Because it runs in parallel with development at no cost, starting it immediately is free schedule insurance. Teams that start it when the checkout is built routinely lose a month waiting.
Design for the failures
Payment failure is common in the region: intermittent connectivity, three-domain-secure authentication steps that time out, and cards declined for international transactions. Handle a payment whose result is unknown, which is the genuinely hard case. Never charge twice, always give the customer a clear state and a way to check, and make the reconciliation path something support can follow without engineering.
Currency and presentation
Show prices in local currency with correct formatting and the conventional decimal handling for that currency. In Arabic interfaces decide deliberately between Western and Eastern Arabic numerals and stay consistent between the app, receipts and any messages you send. Small inconsistencies here read as carelessness on precisely the screen where trust matters most.
Gateway approval runs in parallel with development at no cost. Starting it in week one is free schedule insurance.
Sources