CBN AML/CFT Implementation Guide for Nigerian Fintechs
StackWeaver Research · 16 min read · Published 2026-07-05 · Updated 2026-07-15
CBN AML/CFT compliance is usually approached as a documentation exercise and fails as one. This guide treats it as an engineering problem: what controls must actually run, what evidence they must produce, and how to reach a defensible state without a nine-month programme. It is written for the CTO and compliance lead who have to make it real, not for a policy binder.
Scope: what CBN AML/CFT actually requires
At its core, the regime requires a risk-based programme with five operating capabilities: customer due diligence (CDD/KYC), ongoing monitoring, suspicious-transaction detection and reporting (STR), currency-transaction reporting (CTR) where applicable, and a governance layer (a compliance officer, board oversight, training, and record-keeping). Each of these can be documented — or engineered so it runs and proves itself. This guide takes the second path.
The control set, as engineering
| Requirement | Documentation approach | Engineered approach |
|---|---|---|
| CDD / KYC | Written onboarding policy | Enforced identity checks in the onboarding flow, with per-customer evidence records |
| Ongoing monitoring | Periodic manual review | Rules engine scoring transactions in real time, alerts logged as evidence |
| STR / CTR | Manual filing when noticed | Detection thresholds wired to a filing workflow with timestamped records |
| Record-keeping | Shared drive of documents | Tamper-evident, mapped evidence store queryable on demand |
The findings we see most often
- KYC that is enforced at signup but not re-verified on risk triggers.
- Monitoring rules that exist but produce no retained evidence of having run.
- STR processes that depend on a single person noticing, with no detection threshold.
- Record-keeping scattered across tools, impossible to produce for a specific customer under time pressure.
A phased implementation path
- Baseline (phase 1): map current controls to the requirement set; identify which are documented vs. enforced. Use the CBN AML checklist.
- Engineer the gaps (phase 2): convert the highest-risk administrative controls into enforced ones — starting with monitoring and STR detection.
- Wire evidence (phase 3): route control outputs into a mapped, tamper-evident store so proof accumulates automatically.
- Operationalise (ongoing): move toward continuous compliance so readiness is maintained, not rebuilt.
Keeping evidence continuous
The failure mode after go-live is drift: rules change, a data source moves, and evidence quietly stops. An evidence-native design prevents this by capturing at the source and detecting freshness gaps. The commercial version of this work is CBN AML Compliance Readiness.
Frequently asked questions
What is "CBN AML/CFT Implementation Guide for Nigerian Fintechs" about?
A practical, engineering-first guide to implementing CBN AML/CFT controls — scope, the control set, common findings, a phased implementation path, and how to keep evidence continuous.
- CBN AML/CFT/CPF Regulations — Central Bank of Nigeria
- Money Laundering (Prevention and Prohibition) Act 2022 — Federal Republic of Nigeria
- NFIU STR/CTR filing guidance — Nigerian Financial Intelligence Unit
What this relates to
- Continuous ComplianceContinuous compliance means controls that run every day, evidence captured as work happens, and drift you can see. What it is, and four tests for it.
- Evidence-Native SystemsSystems where compliance proof is a property of how they operate -- captured at the source -- not a document produced under deadline.