Paymob's $35 Million Round Is a Bet on Fragmentation

Paymob, the Cairo-founded payments company, has raised $35 million in a pre-Series C round co-led by Mubadala and the European Bank for Reconstruction and Development, with British International Investment, Global Ventures and DPI Ventures participating. According to Tech Startups, the round takes Paymob’s disclosed funding above $125 million, and the company now serves more than 390,000 merchants across the Middle East and North Africa.

Most of the coverage leads with the amount. The line I care about is a different one: Paymob gives merchants access to more than 60 payment methods through one integration. That sentence describes the problem I work on every day, in a different region and a slightly different shape, and a round like this one is a useful moment to say why I think the problem is permanent.

What “one integration” is covering up

On an investor slide, MENA is a region. For a merchant trying to take payments in it, it’s a set of separate countries, each with its own currency, its own regulator, and its own mix of payment methods that customers there expect and customers next door may never use. Nobody needs sixty payment methods in one market. You need sixty because you’re selling into many markets, and each one brings a handful of its own.

Paymob’s own reported numbers show how much of this is country by country. The company says consolidated revenue tripled over the past 18 months, and that revenue from the GCC grew sevenfold and now makes up close to half of the group total. It also says that since getting its UAE Retail Payment Services License in January 2025, it has added roughly 20,000 merchants across its three GCC markets. Those are company figures, reported through Tech Startups, and I’d treat them that way. What interests me is less the growth rate than the mechanics behind it. The UAE growth came after a UAE licence. The next market will mean the next licence and the next set of local methods. A regional business in payments gets built one jurisdiction at a time, and none of that work goes away because the merchant only sees one API.

Let’s imagine a situation to make it concrete. A merchant based in Egypt starts selling into the UAE and Saudi Arabia. Without an aggregating layer, it’s looking at a separate provider relationship in each country, separate onboarding and compliance reviews, separate reporting formats, and a finance team reconciling payouts in three currencies from three sources that each describe the same kind of transaction differently. None of these problems is exotic. It’s just a lot of them at once, and every one of them has to be solved before the merchant has sold anything.

The received wisdom I don’t buy

There’s a view in payments that fragmentation is a transitional phase. Local methods will consolidate, a few large providers will cover everything, and the need for a layer that stitches providers together will fade.

I don’t think that’s happening, and I don’t think it’s going to. My working days are spent in payment orchestration, and in seven years of it my experience has run the other way: the number of providers and local requirements a merchant has to deal with tends to go up as the merchant grows. The fragmentation I deal with most is by vertical rather than by geography. A lot of the merchants I work with sit in verticals that mainstream processors decline, such as gambling, forex, nutra and crypto, and for them coverage never comes from one provider. It comes from several specialised ones, each covering a slice of the traffic, with something on top deciding which one handles which transaction.

Paymob’s pitch is the geographical version of that same problem. The merchant doesn’t want to know how many different markets the region really is. It wants one integration, and someone else to absorb the fact that each market works differently. When a company with that premise raises money from a development bank, a UK development-finance investor, a sovereign fund and two venture firms, I take it as a sign that serious capital expects fragmentation to last. That’s my interpretation of an investor list, not something the investors have said.

I should add that funding announcements on their own tell me very little. Plenty of well-funded payments companies have turned out to be wrong about their market. The part of this one I’d weigh is the specific claim underneath it, one integration over a fragmented region, and the licensing and regional revenue figures that suggest the company is doing the unglamorous country-by-country work to back it.

Aggregation and orchestration are not the same thing

This is the part I think gets blurred most often, and it’s worth being precise about.

Giving a merchant 60 payment methods through one integration solves a coverage problem. The merchant can accept the methods its customers want in each market without building each connection itself. That’s aggregation, and in a region like MENA it’s a large amount of value on its own.

Orchestration, as I use the word, covers what happens after coverage. A transaction that declines at one provider gets retried through another. When one provider has an outage, traffic moves somewhere else instead of the checkout failing. When the merchant has two ways to process the same payment method, something decides which one gets each transaction, based on cost or approval history. And the finance team reconciles what every provider says happened against what the merchant’s own systems recorded. Routing, cascading and reconciliation are what I mean by orchestration, and they only make sense once there’s more than one provider to route between.

From the outside, I can’t tell how much of that Paymob does underneath its single integration, and the reporting on the round doesn’t say. It may do a lot of it internally across the acquirers and local schemes it connects to. What I can say is how it looks from the merchant’s side. If Paymob is the one integration a merchant has into the region, then Paymob is one provider in that merchant’s stack. A very broad one, but one. The merchant has consolidated its dependency rather than removed it, and whether that’s the right trade depends on the merchant.

For many merchants it will be exactly the right trade. For a larger one with volume in MENA and elsewhere, the sensible setup is often a regional platform like Paymob sitting inside a wider orchestration layer, as one of several providers, rather than instead of one. I don’t see those as competing ideas. They solve adjacent problems, and a merchant that confuses them tends to discover the difference during its first serious outage. I made a related point in there’s no such thing as a bad payment provider: how well a provider performs for a merchant depends heavily on whether it fits that merchant’s traffic, which is also why no single provider covers everything well.

The agentic commerce line

One more detail from the coverage: Paymob is positioning the platform for agentic commerce, where AI systems search for products and may eventually initiate transactions themselves. A lot of payments companies are saying something similar at the moment, and I’m cautious about reading much into it. I’ve written about how far ahead of consumer trust agentic checkout is being built, and nothing about a funding round changes that.

The one point I would make is that fragmentation doesn’t get easier when software does the buying. An agent shopping for someone in Riyadh and an agent shopping for someone in Cairo would each need to pay with whatever the merchant and the market support. Something has to know which methods are available where and route accordingly, and that is the same one-integration problem again, with a different party making the request.

Where this argument stops

If you sell in one country, most of this doesn’t apply to you. A direct integration with one good local provider is usually cheaper and simpler than any aggregating or orchestrating layer, and a layer you don’t need is complexity you pay for without getting anything back. The same is true if your volume is small enough that a second provider would never get meaningful traffic. I’d advise against orchestration in that situation, including Corefy’s, and I’d say the same about a regional platform if you’re only in one of its markets and a local provider serves you well there.

The single-integration model also has a cost worth naming. When everything goes through one API, it’s easy to lose sight of which underlying provider or scheme handled a given transaction, and that matters when a dispute comes in or when payouts don’t match what was expected. Whatever sits between a merchant and its providers should keep that visible.

And a funding round is evidence of investor conviction and little else. The growth figures here are Paymob’s own, and $35 million is a bet that the company can keep doing the licence-by-licence, market-by-market work that makes one integration possible. I think the premise underneath that bet is right. Whether any single company executes on it is a separate question, and it’s one a press release can’t answer.