Cross-Border MVNOs in Africa: When Mobile Connectivity Becomes Part of the Remittance Ecosystem

A Zimbabwean electrician in Johannesburg carries two numbers. The South African one gets him work, pays his rent through a wallet, and receives the OTPs his bank sends. The Zimbabwean one is how his mother reaches him and how the family account back home stays verified. He has been doing this for six years, which makes him neither a roaming customer nor a domestic subscriber. The travel eSIM was not designed for him and neither was the local MVNO, and there are roughly 25 million people in Africa living the same way.

That gap is pulling a third operator category into existence. Call it the cross-border MVNO: connectivity as the cheap, high-frequency entry point into a payments relationship, which is where the money actually sits. The volumes justify the attention. Sub-Saharan Africa took in roughly $56 billion in recorded remittances in 2024, and around $1.4 trillion moved through mobile money wallets in the region during 2025, about two-thirds of the global total by value.

The travel eSIM was built for someone else

Most travel eSIMs are data-only: no MSISDN, no SMS, no voice. That is a reasonable trade for a two-week holiday, because your home SIM stays in the phone and keeps receiving the codes your bank sends.

For a resident migrant the same design breaks in ways that compound. Keeping a home SIM live for years purely to receive SMS means paying line rental in a currency you no longer earn. Local employers, landlords and government portals want a local number and often accept nothing else. Mobile money onboarding is tied to a locally registered SIM in most markets, so a data-only profile locks the user out of the dominant payment rail in the country they actually live in.

Registration rules make this harder. Nigeria requires foreign nationals resident beyond two years to hold a National Identification Number, with shorter stays running on passport and visa pages. Malawi moved to biometric SIM registration in 2025, Ghana is folding liveness checks into its verification drive, and South Africa is overhauling RICA. A product that treats the subscriber as anonymous throughput cannot survive contact with any of this, and travel eSIM economics assume exactly that: acquire, sell 10 GB, never see the customer again.

Two numbers, one identity

Once you accept that the user lives in both places, the local number stops being a SIM and becomes a key. In the origin market it is tied to the family wallet, the utility account, school fees. In the destination market it is tied to payroll, the local wallet, the KYC record at the bank. The migrant runs two identity graphs, and every cross-border action needs both live at the same moment. Sending money home means authenticating in Johannesburg and confirming delivery in Harare. If either number lapses the transaction fails, usually at the worst possible time.

A cross-border MVNO is functionally an operator holding both ends of that graph in one account: one subscription, several MSISDNs across different countries, one identity record, one balance visible on both sides. It sounds mundane and is hard to build, which is why the category is defensible.

Why connectivity, wallet and remittance belong in one product

The remittance side explains the bundle. Sending $200 to Sub-Saharan Africa still costs around 8.8% on average against a UN target of 3%. Intra-African corridors are the worst offenders: South Africa to Mozambique has run above 14%, South Africa to Malawi close behind. Those spreads reflect thin corridor volumes, correspondent banking friction and compliance cost per transaction, plus the fact that the customer has nowhere better to go.

Bundling attacks that cost base from an unusual direction. Acquisition is already paid for by the connectivity product. KYC has been performed once for SIM registration and can be extended rather than repeated. Distribution runs through the agent network that already sells airtime. The remittance leg becomes a margin line on an existing relationship rather than a standalone business fighting for CAC payback.

Retention works the same way. Airtime sent to a relative's number is a remittance in miniature, often the first cross-border transaction a new customer makes, and a low-stakes way to build trust before moving a month's wages.

The catch is licensing. Connectivity, e-money issuance and cross-border transfer are three separate regulatory perimeters in almost every market, so the wallet ledger must stay segregated from the telecom ledger. Bundling the experience does not mean merging the balance sheets.

What a multi-country BSS/MVNE has to support

Most MVNE platforms were designed for one country, one host operator, one currency, one regulator. A cross-border MVNO breaks each assumption on day one. The load-bearing requirements:

• Multi-country, multi-currency subscriber ledger with one customer identity spanning several MSISDNs and several national KYC records, each with its own validity state.
• Per-market product catalogue and tariff engine, since bundles, VAT and sector levies differ by country and change often.
• Number and eSIM inventory management across multiple host operators: RSP integration, multi-profile provisioning, entitlement handling for secondary devices.
• Mediation across heterogeneous CDR formats, with reconciliation that flags wholesale disputes before the invoice is paid.
• KYC orchestration per jurisdiction: different ID types, biometric requirements and re-verification cycles, plus a way to attach a foreign identity document to a local subscription where rules allow.
• A segregated wallet ledger with its own audit trail, KYC-tiered limits and AML screening hooks.
• Regulatory reporting by market, because a consolidated report satisfies nobody.

Nigeria shows how fast this is formalising. The NCC has issued more than forty MVNO licences across five tiers, with fees from roughly ₦35 million to ₦500 million, and its 2026 draft Business Rules explicitly cover SIM and eSIM management alongside numbering and interconnection. Licences have proven easier to obtain than launches: by late 2025 only one Nigerian MVNO had gone commercially live, and platform readiness is much of that gap.

Settlement is where the model quietly bleeds

Four counterparty types sit in the flow: host operators, the MVNO, banks, and payment or mobile money providers on both ends. Each settles on a different cycle, in a different currency, under a different contract. Host operators invoice monthly in local currency against wholesale rate cards, often with minimum volume commitments that assume domestic growth. Payment partners want prefunded float in the payout country. Banks apply their own FX spread and cut-off times. The MVNO sits in the middle holding currency exposure it never intended to take.

Three things reduce the pain materially. Treat float as a treasury function rather than an operational afterthought, deciding deliberately where balances sit and in what currency, then pricing that into the corridor. Net where legal structure permits, so intra-group flows do not each incur a full correspondent banking leg. Use regional infrastructure where it now exists: PAPSS reached 28 countries by mid-2026 with more than 190 banks and fintechs connected and the CEMAC central bank joining, removing a hard-currency hop from a growing number of corridors.

Reconciliation discipline matters more than any of it. Telecom revenue assurance and payments reconciliation are different crafts, and this model needs both, running against one customer record. Airtime margins alone will not absorb a settlement error.

The risks that don't appear in the business case

KYC divergence. SIM registration KYC and financial KYC are not the same standard, and the gap between them is where regulators look first. A subscriber verified adequately for a SIM is nowhere near sufficient for a wallet holding a month's salary, and tiered limits have to reflect that.

Currency. Soft-currency exposure in these corridors is structural. Retail FX spread is a legitimate revenue line, but it is increasingly scrutinised, and pricing it as hidden margin invites both regulatory attention and competitive undercutting.

Data residency. The constraint most likely to force an architecture rewrite. Nigeria's NDPA restricts cross-border transfer by default, its implementation directive has been in force since September 2025, and telecom rules separately require subscriber data to sit in-country. Kenya's Data Protection Act imposes conditional transfer requirements, with its regulator consulting on cross-border guidance through mid-2026. A platform holding one customer record across five countries answers all of this at once, usually through per-country data planes and a federated identity layer rather than a single database.

Regulatory asymmetry. MVNO frameworks exist in Nigeria, South Africa, Kenya and Senegal but not uniformly across the continent, and e-money licensing, local shareholding rules and transfer permissions vary independently of the telecom regime. Corridor selection is a regulatory decision as much as a commercial one, and the corridor with the best migration volume is frequently not the one you can launch first.

None of this makes the category harder than it looks. It makes it harder than the pitch deck looks. The demand underneath is not going to soften. The open question is whether operators treat payments as a feature bolted onto a SIM, or treat the SIM as the cheapest way anyone has found to acquire a payments customer who stays for a decade.