On June 15, 2026, the Central Bank of Nigeria quietly issued a circular that every business handling payments in Nigeria needs to understand. It doesn't make headlines the way interest rate changes do, but its impact on how Nigerian businesses store and manage financial data is significant β and the clock is already ticking.
What Did the CBN Actually Say?
In simple terms: if your business processes payments in Nigeria, the transaction data generated from those payments must be stored and managed inside Nigeria. Not on a server in the United States. Not on infrastructure in Europe. Inside Nigeria.
The compliance deadline is January 1, 2027 -roughly six months from when the circular was issued.
The directive covers deposit money banks, microfinance banks, mobile money operators, payment processors, switching companies, payment terminal service providers, and other licensed payment operators. If your business falls into any of these categories, this applies to you directly.
Does This Mean You Have to Stop Using AWS or Google Cloud?
No, and this is where many people misread the directive.
The CBN isn't banning global cloud providers like Amazon Web Services, Microsoft Azure, or Google Cloud. What it's saying is that if you use these platforms, the relevant payment data must be hosted and managed through their Nigerian infrastructure, not their default global servers.
AWS, for example, already has a Lagos local zone, a facility physically located in Nigeria that allows businesses to keep data in-country while still using AWS tools. This is one path to compliance. There are others.
Why Is the CBN Doing This?
Several reasons, and they're worth understanding rather than dismissing as bureaucratic overreach.
Regulatory access. When Nigerian payment data sits on foreign servers, CBN examiners have to navigate foreign jurisdictions to access it during audits or investigations. Localising that data removes that friction entirely.
Data sovereignty. Data stored outside Nigeria is subject to the laws of wherever it's physically hosted, not necessarily Nigerian law. The CBN wants sensitive financial transaction data to sit firmly within Nigeria's legal framework.
Foreign exchange conservation. This one is particularly relevant given Nigeria's current economic climate. Nigeria reportedly spends around $850 million annually on offshore data hosting and cloud services, with roughly 90% of regulated financial businesses still relying on foreign providers. Paying for local hosting in naira rather than dollars reduces pressure on an already stretched foreign exchange market.
Systemic risk. The Nigerian payments market has grown enormously, one major operator alone reportedly processed over 1.6 billion transactions worth over β¦400 trillion monthly in 2025. The CBN wants to ensure that this scale of activity isn't exposed to failures or disruptions caused by dependency on foreign infrastructure.
Is Nigerian Infrastructure Ready for This?
This is the honest question most industry voices are asking, and the answer is: mostly yes, with some genuine gaps worth watching.
On the positive side, local data hosting in Nigeria actually offers real performance improvements. Routing payment transactions through foreign servers adds communication delay, some estimates put this at over 80 milliseconds for offshore processing versus around 15 milliseconds for locally hosted infrastructure. For high-volume payment processing, that difference is meaningful.
There's also a financial argument: institutions paying for hosting in naira rather than dollars are directly insulated from exchange rate volatility, which has been a recurring and costly problem for Nigerian businesses over the past few years.
The concerns are real too, though. Nigerian data infrastructure is maturing fast, but it isn't yet as deep or as geographically distributed as global cloud providers. Around 84% of existing Nigerian data centre capacity is concentrated in Lagos, which means a single regional disruption could create serious problems if backups aren't deliberately spread across locations. Global providers have decades of multi-region failover experience that local operators are still building toward.
Migration is also more complex than simply moving files. Replicating databases, re-architecting systems, and validating data integrity, all without interrupting live payment processing, is a substantial technical undertaking. Six months is tight, though most industry commentators consider it achievable for businesses that start immediately rather than waiting until Q4 2026.
What Are Your Compliance Options?
There are four practical paths, and they're not mutually exclusive:
Colocation with local operators -renting space and power inside existing Nigerian data centres (such as MDXi, Rack Centre, Open Access Data Centres, or telco-backed facilities from MTN and Airtel) and running your own servers or private cloud infrastructure there.
Global cloud through local presence -using AWS, Azure, or Google Cloud via their Nigerian infrastructure rather than their default global servers, keeping data physically in-country while retaining familiar tooling.
Nigerian-native cloud providers -a fast-growing segment of local providers who specifically offer naira billing and guaranteed in-country data residency as their core proposition.
Huawei's local cloud service -launched in Nigeria in December 2024, explicitly built around Nigerian data residency requirements.
What Should You Do Now?
If your business is directly covered by this directive, the worst thing you can do is wait. Six months sounds generous until you factor in the actual migration work, infrastructure procurement timelines, and the inevitable end-of-year slowdowns in Q4. Businesses that start their compliance assessment now will have options. Businesses that start in October will be scrambling.
If you're not sure whether this directive applies to your specific operations, or what your most practical compliance path looks like given your current infrastructure, that's a conversation worth having with a qualified IT consultant sooner rather than later.
