Learn/Product Advisory and Cross-Functional Work
Nigerian Regulators You Will Actually Meet
About 14 minutes
Tech & Counsel provides education only. Nothing on this site is legal advice, and nothing here creates a solicitor–client relationship.
One app can interest several regulators at once. Learn the map well enough to ask which door the product is walking toward. Mandates change. Treat the table as a field guide, and check the current instrument before you tell a client they need a particular licence.
| Body | What to listen for in the product meeting |
|---|---|
| NDPC | Personal data, audits, breach notification |
| NITDA | Information-technology standards, software and local-content questions |
| CBN | Payments, wallets, remittance, anything that smells like banking |
| NCC | Telecommunications, value-added services, messaging rails |
| SEC | Digital assets, crowdfunding, wealth products offered to the public |
A payments feature plus a contact list plus a investment wallet is not “just an app.” It may be three conversations.
Sandboxes
When the product does not fit a current category, shutting it down is one regulatory outcome. A sandbox — the Central Bank and the Securities and Exchange Commission have both run versions — is a supervised, limited trial with real users and lighter rules, so the regulator can watch the thing before a full licence. Your role is to know the programme exists and to ask whether the team is eligible, not to promise admission.
Keep a calendar. Filing dates and licence conditions are operational facts. A product counsel who discovers a renewal the week it is due has not been in the sprint.
Create a free account to mark this lesson complete.