Africa's Premier Tech Intelligence Platform
All Tech Policy & Regulation Cybersecurity & Cybercrime AI & Emerging Tech Africa Startups Fintech & Payments Opinion & Analysis
Intelligence Brief

Nigeria's Telecom Giants Must Choose: Routing Sovereignty or Fintech Feudalism

With 241,000 active .ng domains and a policy push to localise internet routing, Nigeria's infrastructure debate has reached a fork—and how MTN and its peers respond will determine whether African fintech startups inherit sovereign rails or a new set of corporate gatekeepers.

Nigeria's Telecom Giants Must Choose: Routing Sovereignty or Fintech Feudalism

Nigeria's internet sovereignty argument has been framed almost entirely as a cost and security question—domestic traffic routed through foreign exchange points, dollars bleeding out, data exposed. Technology policy adviser Jide Awe is right to call it an economic drain Source: Nairametrics. But the argument most African fintech founders should be making is subtler and more urgent: who controls the local infrastructure that replaces the foreign one?

That question matters because the same telecom operators now positioned to anchor Nigeria's routing sovereignty—MTN foremost among them—are aggressively expanding into the very services that would run on top of it. MTN's new pan-African streaming platform is the latest signal of an operator that has decided connectivity is a commodity and that value now lives in digital services, content, and fintech Source: TechCabal. If those operators also own or control the local routing layer, Nigerian and broader African startups will have traded one set of foreign gatekeepers for a domestic one—better for sovereignty optics, no better for competitive access.

The .ng domain surge is instructive here. NiRA recording 241,000 active domains, with 98,285 new registrations in a single year, is not a vanity metric Source: Nairametrics. It signals a genuine, grassroots move toward locally anchored digital identity. Fintech developers building on .ng domains for payments, KYC, or merchant onboarding are, in effect, pre-investing in the infrastructure architecture that local routing would complete. Each registered domain is a node in a potential sovereign payment web—but only if the routing layer beneath it is open, regulated, and interoperable rather than owned end-to-end by operators with competing commercial interests.

Advertisement
Advertisement

This is where Nigerian regulators—the Nigerian Communications Commission and the Central Bank of Nigeria in particular—face a structural test. The policy momentum behind local routing is real. What does not yet exist is a framework that separates infrastructure ownership from service competition. Without mandated open access to locally routed exchange points, the sovereignty argument becomes a legitimising narrative for vertical integration by incumbents. Startups in Lagos building cross-border payment rails to Accra, Nairobi, or Kigali cannot absorb the cost of negotiating access with an operator that also competes in their lane.

The open question fintech founders should be pressing regulators to answer: will local internet exchange points be treated as regulated shared infrastructure—like roads—or as proprietary assets that operators can monetise selectively? The answer shapes whether Nigeria's routing sovereignty produces a genuine payments infrastructure dividend or simply restructures dependency.

Africa's broader fintech ecosystem should watch Nigeria's resolution of this tension closely. The continent's most consequential cross-border payment corridors—Lagos to Accra, Nairobi to Kampala, Kigali to Dar es Salaam—all run over infrastructure that no single African government fully controls today. If Nigeria proves that sovereign routing and open-access regulation can coexist, it creates a replicable template. If it allows telecom operators to consolidate both layers, it proves only that the gatekeeping address has changed.

Nigeria's industrial policy history—marked by gaps between vision and execution—suggests that regulatory clarity will not arrive automatically. Founders and developers who want to benefit from this infrastructure moment cannot wait for it to resolve. They should be at the table with the NCC now, arguing for interoperability standards before the architecture is locked in. The .ng domain numbers show appetite. The routing debate shows the opportunity. The outcome depends on whether the people who will actually build on this infrastructure are shaping its rules.

CyberSpaceChronicles — Add to your home screen for the best experience.