The obvious fix everyone assumes exists turns out to be broken. But the real answer is already sitting inside Nigeria's own infrastructure.
Every single day, millions of Nigerians perform a small, unnecessary task. They open an app, walk up to an agent, or dial a code. They want to put airtime on a number. And before anything else happens, the system stops them and asks: which network is this number on?
MTN. Airtel. Glo. 9mobile.
Pick one.
It is a two-second interruption. Small enough that most people have stopped noticing it. But it is also completely unnecessary, and the reason it still exists in 2026 is more interesting than most people would expect.
The Obvious Answer That Everyone Assumes Is Already Working
If you ask most people why unified recharge has not been built, they will tell you the answer is obvious. Nigerian phone numbers follow prefix patterns. MTN owns certain number ranges. Airtel owns others. So any platform could just read the first few digits, identify the network, and route the transaction automatically. No selection required.
It sounds clean. It sounds simple. It sounds like something that should have been done years ago.
The problem is that it is wrong. And the reason it is wrong changes the entire conversation.
Number Portability Broke the Prefix Logic
Nigeria launched number portability years ago. It allows any subscriber to move from one network to another while keeping their existing number. Your MTN number stays your number even after you switch to Airtel. The digits do not change. Only the network underneath changes.
This means the prefix tells you where a number started. It does not tell you where it lives today.
A number beginning with 0803 looks like MTN. It may have been MTN for a decade. But if that subscriber ported to Airtel six months ago, sending airtime to the MTN routing for that number will either fail or land in the wrong place. The prefix is a historical record, not a live address.
Any system built purely on prefix detection will get ported numbers wrong. And with millions of Nigerians having ported over the years, that is not a small edge case. It is a real and growing problem that makes prefix-based auto-detection unreliable as a foundation for unified recharge.
So the simple answer does not work. Which means the real answer has to come from somewhere else.
The Real Infrastructure Already Exists
Here is what most people outside the telecoms industry do not know. Nigeria has a Number Portability database. It is maintained and governed by the NCC. Every time a subscriber ports from one network to another, that database is updated. It holds the ground truth about which network any given Nigerian number actually belongs to at any given moment.
That database can be queried. Not by consumers directly, but by licensed platforms and operators through an API. The live current-network status of any number, ported or not, is accessible in real time through that infrastructure.
This changes the problem completely. The question is no longer whether auto-detection is possible. It clearly is, if you are reading from the right source. The question is why that real-time lookup is not already sitting quietly inside every recharge transaction, sparing users the manual selection entirely.
Why It Is Still Not Happening
The infrastructure exists. The lookup is technically possible. So what is the hold-up?
Querying the NCC number portability database requires a formal arrangement. Not every VTU platform, fintech app, or bank has that integration in place. Some do. Most do not. Building it costs time and money, and there has been no regulatory requirement that forces platforms to do it.
The current system works. Users have adapted. Shops that process recharges for customers have learned the prefixes as a rough guide and correct manually when something fails. The inconvenience is real but small enough that it has never generated the kind of public pressure that forces platforms to invest in fixing it.
A unified routing layer would require all four major networks to formally agree on how transactions are identified, routed, and settled when a recharge comes in through a neutral platform rather than their own channels. That commercial negotiation has not happened at the level required to make unified recharge a standard.
This is the most direct lever. The same regulator that governs the number portability database could require that all licensed recharge platforms integrate the live network lookup before processing a transaction. It has not issued that directive. Until it does, integration remains optional, which means most platforms skip it.
What a Proper Unified Recharge System Would Actually Look Like
The user experience is simple. You enter a phone number. You enter an amount. You pay. The system handles everything else.
Behind that simple experience, three things happen that the user never sees.
The platform queries the NCC number portability database with the phone number in real time. It receives back the current network that number is registered on, regardless of what the prefix suggests and regardless of whether the number has ever been ported. It routes the recharge to that network through a pre-arranged settlement relationship and confirms completion.
The only thing the user touches is the denomination. Everything else is infrastructure doing its job silently.
This is not speculative technology. The lookup capability exists. Large fintech platforms already have relationships with all four networks for settlement purposes. The NCC database is queryable. The missing piece is an operator, a regulator, or a commercial agreement that brings these three things together under one standard.
Who Could Actually Build This
The honest answer is that several parties have the pieces already.
OPay, PalmPay, and Moniepoint process airtime recharge across all four networks from a single interface. They have the settlement relationships. They have the engineering capacity. What they would need to add is the real-time NCC port-status lookup and the removal of the manual selection step. That is not a ground-up build. It is an upgrade to infrastructure that already exists.
The NCC itself could accelerate this by requiring port-status lookup as a mandatory step in any licensed recharge transaction. That single regulatory requirement would make manual network selection obsolete across every platform that processes Nigerian airtime.
A bank or super-app that made this a visible product feature, positioning it as zero-friction recharge that always gets the network right, would have something genuinely differentiated in a crowded market. The promise is simple and verifiable: enter any number, any amount. We handle the rest.
The Bottom Line
The reason you still pick a network every time you recharge is not because the technology to avoid it does not exist. It exists. It is not because nobody has thought of building it. People have. It is because the obvious solution, reading prefixes, does not actually work in a world where numbers can be ported.
And the real solution, querying the live NCC database, has not been turned into a product, a standard, or a regulatory requirement.
Nigeria built the infrastructure to know, in real time, which network any phone number belongs to. That infrastructure just has not been connected to the moment that matters most for ordinary users: the moment they want to put airtime on a phone.
That connection is not hard to make. It just has not been made yet.
0 Comments