Payments infrastructure is one of the least glamorous and most decisive parts of digital commerce. A merchant in Amman, a merchant in Lagos, and a merchant in Kuala Lumpur each expect their customers to pay the way those customers already pay, and each sits behind a different set of banking relationships, regulatory obligations, and preferred payment methods. Serving all three from a single business is a genuinely difficult problem.
MontyPay, a global payment technology and services provider, has spent the past several years solving exactly that problem. Today the company supports merchants in more than 50 countries across the Middle East, Africa, and Asia, offering over 100 payment methods spanning global card schemes and regional digital wallets.
A deliberate choice about where to compete
MontyPay was established as the fintech arm of Monty Mobile, a telecommunications group with operations in more than 70 countries and headquarters in the United Kingdom. That parentage gave the company something most payment startups lack: existing commercial relationships in markets that are notoriously hard to enter cold.
What it did not give the company was payment infrastructure. And here the leadership team made a decision that shaped everything after it. Building a payment gateway, routing engine, merchant management system, tokenization layer, and fraud tooling from scratch is a multi-year engineering programme. Doing it while also pursuing acquiring relationships, certifications, and market licences is longer still. MontyPay concluded that the years spent on that build would be years not spent signing merchants.
So for its payment gateway and orchestration platform, the company adopted a proven technology foundation, working with Akurateco, a PCI DSS-certified payment software vendor, and redirected its own resources toward the things a payment provider actually competes on: merchant relationships, market coverage, local payment expertise, and product breadth.
What the company actually sells
MontyPay’s offering has widened well beyond a checkout page. The company provides an online payment gateway, in-store POS terminals, self-service checkout, QR-based payment tools for hospitality venues, and e-commerce enablement for merchants building their first digital storefront. Akurateco’s role is limited to the gateway and orchestration layer; MontyPay’s other products, including POS, QCheck and its e-commerce services, sit outside that partnership.
That breadth matters commercially. A restaurant group does not want one vendor for card terminals and another for online ordering. A retailer expanding into a second country does not want to renegotiate its entire payment stack. By covering in-person and online commerce under one brand, MontyPay positions itself as the payments partner a growing merchant does not need to replace.
Regulatory diversity as an operating condition
The harder part of MontyPay’s model is regulatory. Payment providers in this part of the world encounter a patchwork of requirements: some markets impose data residency obligations, requiring payment data to be processed and stored within national borders. Others impose specific licensing regimes, local integration mandates, or reporting standards.
Many fintechs treat each of these as a separate crisis. MontyPay planned for the infrastructure side in advance, retaining the ability to configure its deployment model market by market. Where local requirements allow, cloud-hosted infrastructure supports fast entry. Where a jurisdiction requires payment data to remain local, the same platform can be deployed as a dedicated on-premises system inside that market and connected to local payment rails.
These deployment options address different technical and data-hosting requirements. They do not, on their own, satisfy the licensing or regulatory requirements of any given market, which are handled separately in each jurisdiction. The practical effect is narrower but still valuable: meeting a market’s hosting requirements becomes a deployment decision rather than a platform rebuild.
The lesson for the region’s fintechs
There is a persistent assumption in fintech that owning your entire technology stack is the mark of a serious company. MontyPay’s trajectory suggests a more precise version of that idea: own the things that differentiate you, and buy the things that do not.
No merchant in Nairobi or Dubai chooses a payment provider because that provider wrote its own routing engine. They choose based on which payment methods are supported, how quickly they get onboarded, how reliably transactions settle, and whether the provider understands their market. Those are the areas where MontyPay has invested, and the results are visible in its footprint.
For founders across MENA weighing the same decision, the question worth asking is not whether to build or buy. It is which parts of the business will still matter to a customer in five years, and whether the engineering calendar is being spent on those parts or on infrastructure that a partner has already solved.
Featured image credit: MontyPay
