African fintech regulation, structured
The rulebook for African fintech regulation
Before entering a market, vetting a partner, or answering the board —
Know who's licensed, what licence is needed, and what it takes to hold it —
Assembled from official regulator sources, normalized to compare markets, and dated to source.
What licence is needed
The equivalent local category in each market, normalized to one canonical activity.
Who's licensed
The official register of who holds each licence, per market — provider, status as reported, and source.
Licence requirements
What it takes to hold one — minimum capital, local presence, timeline and fees, as published.
What crosses borders
The cross-border money-movement rules — what may move, and under what rule. Rules, not rates.
See the rules →Coverage
Pick your market — everything Afriset holds on it in one place: its registers, its cross-border rules, and its regulators.
Reported gaps: A market without a licence, an unreachable register, and an empty register are reported data points.
Maintained: Official sources are re-checked on a weekly schedule. Each register carries its own last-checked date.
The registers
All registers →Who holds each licence, per market — normalized so you can compare the same activity across markets.
MCP-first
Your AI tools can query this register
Connect Afriset once, and your compliance, ops and engineering tools answer African fintech licensing questions from the official registers — with the source and the date — instead of guessing. Provenance, as-of dates and source-recency signals in every response.
Ask Claude: "who can issue e-money in Ghana, and what capital does it take?" — answered from the Bank of Ghana register and the published requirements, each sourced and dated.
requirements({"category": "GH-BOG-DEMI"}) → the requirements to hold a Ghanaian e-money licence
Connect it — 1-minute setup →