compliance engine for African banks and Fintechs
# ComplyAfrica
> Open-source compliance intelligence for African banks and fintechs.
> Built in Nairobi by the guy behind Keverd.
**Status:** Early. Regulatory corpus in progress. APIs coming.
**Ask:** Contribute a regulation, roast the approach, or tell us what we're missing.
---
## Why This Exists
I built Keverd to help African fintechs stop fraud. In every sales call, the same second problem came up: compliance is manual, expensive, and reactive.
- A Kenyan MFB spends 3 days preparing CBK returns every month
- A Nigerian fintech's compliance officer manually checks 4 websites for CBN circulars
- A Ghanaian startup got fined because they missed a BOG threshold change announced on Twitter
We need a shared, structured, machine-readable layer for African financial regulation.
This is my attempt. Open source because compliance shouldn't be a monopoly.
---
## What's Here Now
| Component | Status | Description |
|-----------|--------|-------------|
| `/regulations/kenya/cbk` | 🟡 In Progress | Prudential guidelines, AML rules, returns |
| `/regulations/nigeria/cbn` | 🔴 Not started | Need contributors |
| `/patterns/mobile-money` | 🟡 In Progress | AML patterns for agent networks |
| `/reports/cbk-returns` | 🔴 Not started | Auto-generation templates |
| `/api` | 🔴 Not started | FastAPI layer (see Roadmap) |
---
## The Goal
**For compliance officers:**
"Did any regulation change this week that affects my license?" → One query, one answer.
**For developers:**
`POST /screen` → Check a customer against sanctions, PEPs, and adverse media in 200ms.
`POST /generate` → Auto-draft a CBK return from your transaction CSV.
`GET /changes` → See what changed in your regulator's rules this week.
**For regulators:**
A standard format for publishing rules that machines can read. We will consume whatever you publish.
---
## Contributing
We need three things:
### 1. Regulatory Documents
Have a PDF, circular, or guideline from your central bank?
Open an issue with `[R …