Why the Smartest Payment Companies in MENA Are Building Locally – Not Globally

There is a moment that every payment company expanding into the Middle East eventually reaches. The commercial case is solid, the merchants are interested, the local acquirer is ready to talk. And then someone in the room asks where the transaction data will physically live — and the entire timeline changes. 

That question has quietly become the single most important variable in MENA payment expansion. Not pricing. Not features. Geography.

The region rewrote the rules, and most companies missed it

Across the Gulf and North Africa, regulators have converged on the same principle: payment data belongs inside the country that produced it.

The Qatar Central Bank requires licensed payment service providers to process and store payment data within Qatar, with no allowance for offshore cloud arrangements. Saudi Arabia’s framework works the same way: SAMA’s rules for regulated entities, reinforced by the Kingdom’s Personal Data Protection Law, mean the personal data of individuals in Saudi Arabia must be processed domestically. The UAE Central Bank’s retail payment services regime and Egypt’s regulatory framework point in the same direction.

None of this is arbitrary. It sits alongside a genuine payments boom that regulators want to keep close to home. Electronic payments reached 85% of all retail payments in Saudi Arabia in 2025, up from 79% a year earlier, across 14.6 billion transactions. In Qatar, electronic payment value hit QR106.8 billion in July 2026 a 40% year-on-year jump with the Fawran instant payment rail more than doubling in value over twelve months. The MENA digital payments market is projected to grow from roughly $275 billion in 2026 to $462 billion by 2031.

So the opportunity is real, and the door has a lock on it. The strategic question is how you get through.

The build-versus-buy trap

The instinctive answer for a well-funded company is to build. Own the stack, own the roadmap, own the margin.

In practice, building a compliant payment platform from scratch typically takes two to three years before a single live transaction and that is before you begin the separate, slower work of onboarding local acquirers and passing PCI DSS certification. In a market growing at 40% a year, a three-year build is not a technology decision. It is a decision to arrive late.

The alternative most companies underrate is a white-label platform they deploy under their own brand and, critically, in their own environment. That is where the deployment model stops being an infrastructure detail and becomes the strategy itself. Two of the companies we work with chose two different paths through it  and the contrast is more instructive than any of them alone.

Qatar: get licensed first, then move the walls

TESS Payments is a Qatar-headquartered PSP serving clients including Doha Bank, QNB, Qatar Development Bank and Qatar Fintech Hub. Their obstacle was sequencing: they needed the technical and operational capacity to demonstrate to the QCB before a license, but the license before they could justify dedicated local infrastructure.

 We solved it in two phases. TESS launched on our white-label SaaS platform, which gave them a working, certified, connector-rich gateway fast enough to support their QCB licensing process and their PCI DSS certification. Once licensed, the platform migrates to dedicated on-premises infrastructure on Microsoft Azure inside Qatar, with transactions synchronised across both environments so no merchant sees an interruption.

What that platform routes matters as much as where it sits. Local cards, including Apple Pay and Google Pay, go through NAPS/QPay via both hosted-page and server-to-server flows, reaching QMP and Fawran. International cards route through CyberSource and Mastercard Payment Gateway Services into Doha Bank, Commercial Bank of Qatar, and QNB. That is not a generic gateway with a Qatari address. It is a Qatari payment topology.

The full TESS build is documented here, including the migration architecture.

Saudi Arabia: on-premises from day one

DineroPay, a licensed PSP in Saudi Arabia, faced the same residency requirement but a different starting position  and made the opposite call. Rather than a phased migration, Akurateco deployed on-premises for DineroPay immediately, on dedicated Oracle Cloud Infrastructure configured to SAMA’s requirements for local data storage and encryption, and achieved SAMA certification on that footing.

The reason was market-specific. Saudi mobile payment demand is not a future trend to plan for; it is the present. Dinero Pay needed Apple Pay and Google Pay live with proper network tokenisation, and the BNPL methods Saudi consumers actually expect — Tabby and Tamara — alongside cards. Network tokenisation in particular is not a checkbox: it measurably lifts approval rates, and it requires infrastructure you control. Building that stack natively would have consumed the exact window in which the market was being divided up. Deploying a pre-integrated platform into a compliant local environment compressed it to a fraction. Their full case study is here.

The four questions that actually decide it

The pattern across these cases e is that nobody chose a deployment model because of a technology preference. They chose based on four things: 

Does your license require it? In Qatar and Saudi Arabia, a domestic PSP license effectively mandates local infrastructure. If you are operating as an agent or reseller under someone else’s license, it may not.

 How many markets are you serving? One heavily regulated market rewards on-premises. Fifteen markets punish it. 

What is your sequencing constraint? If you need demonstrated capability to obtain a license, SaaS first and on-premises second is not indecision – it is the only order that works.

Who owns the migration risk? A move to on-premises after you have live merchants is the highest-risk moment in the business. It should be planned before launch, with dual-running and transaction synchronisation, not improvised afterwards. 

Localisation looks like a cost when you are outside the market. From inside it, it is the most durable competitive advantage available, because the same requirement that slowed you down is now keeping your competitors out. The companies that will own MENA payments over the next five years are the ones treating data residency not as a compliance line item, but as the shape of the business.

Akurateco provides white-label payment software deployed as SaaS or on-premises, with 700+ pre-integrated payment connectors across 200+ currencies.