Nigeria · Compliance evidence

Compliance evidence for Nigerian fintechs: what to show an examiner or a bank partner

A regulator or a sponsor bank does not grade intentions. It asks for records: who reported what, and when. Nigeria has more overlapping fintech rules than most African markets: the Money Laundering (Prevention and Prohibition) Act 2022 (Gazette of 13 May 2022), the CBN regulations and Guidance Note, the data protection regime and the CBN cybersecurity framework, and a 24-hour clock appears in four different places.

This page is the short version: the clocks, the regulators, and the records worth having ready. The maintained reference with every obligation, penalty and date is the Nigeria guide in the Africa Fintech Regulatory Atlas. Nigeria left the FATF list of jurisdictions under increased monitoring in October 2025 (FATF) and does not appear on the list of 19 June 2026 (FATF).

Last reviewed: 16 October 2026 · Written by StackWeaver compliance research team. Draft pending a named reviewer.

This page is general information, not legal advice. The official text is the authority. Local legal interpretation should come from qualified counsel in Nigeria.

Who asks, and for what

Sourced

The Central Bank of Nigeria. The CBN issues the AML/CFT/CPF Regulations (Reg. 3), a Guidance Note (Guidance Note), the targeted financial sanctions guidelines (TFS guidelines), the cybersecurity framework (framework), the BVN rules (BVN addendum) and the payment licence categories (9 December 2020 circular).

The Nigerian Financial Intelligence Unit. The NFIU is the "Unit" that receives suspicious transaction reports under the Act (s. 7(1)). It published its own reporting guidelines on 13 December 2024 (NFIU guidelines).

The Nigeria Data Protection Commission. The commission registers controllers and processors of major importance (s. 44(1)), receives breach notices (s. 40(2)) and hears complaints (s. 46(1)). Its directive of March 2025 sets the audit return and fee regime (GAID), and lists payment gateway service providers and fintechs among the Ultra-High Level controllers (Sched. 7).

Eight reporting clocks

Sourced

Reporting clocks for Nigerian fintechs
EventDeadlineSource
Suspicious transactionImmediately to the NFIU; written report within 24 hourssource 1, source 2, source 3
Alert examination before filingExamination not later than 72 hourssource 1
Cash transactions above the thresholdsWithin 7 days of the transactionsource 1, source 2
Cross-border transfers above US$10,000One day under the Act; 7 days under the CBN Regulationssource 1, source 2
Sanctions matchFreeze within 24 hours; report to the Sanctions Committee within 24 hourssource 1, source 2
Cyber-incident at a bank or payment service providerTo the CBN not later than 24 hours after detectionsource 1
Cyber threatTo ngCERT immediately, and no later than 72 hours after detectionsource 1
Personal data breachTo the data protection commission within 72 hours; to affected people immediately where the risk is highsource 1, source 2

One incident can start three of these clocks at once (a data breach, a CBN cyber-incident report and an ngCERT notice). The Act and the CBN Regulations also give different periods for cross-border reports, one day and 7 days (s. 3(1); Reg. 40(2)). Annual compliance audit returns for Ultra-High and Extra-High Level controllers are due by 31 March each year (GAID).

What an examiner can ask you to show

StackWeaver view, built on the sourced obligations above

  1. The suspicious transaction register, with timestamps, the written report and the NFIU acknowledgement. [1]
  2. The investigation file for each alert, and a written reason for every alert closed as not suspicious. [1] [2]
  3. The cash and cross-border report logs, with the dates the reports were filed. [1] [2]
  4. Customer due diligence files, risk ratings and verification logs, and the politically exposed person register with the senior approval for each relationship. [1] [2]
  5. The daily sanctions screening log, and the record of every freeze and every report to the Sanctions Committee. [1] [2] [3]
  6. The money laundering and terrorism financing risk assessment for each new product, dated before launch. [1] [2]
  7. The Chief Compliance Officer appointment, the training records and the report of the independent test of the programme. [1] [2] [3]
  8. The retention schedule for transaction and due diligence records, and proof that an old record can be retrieved. [1] [2]
  9. The data protection registration, the Data Protection Officer designation and the annual audit return filing. [1] [2] [3]
  10. The breach register and one incident runbook that covers the commission, the CBN and ngCERT clocks. [1] [2] [3]

This list is StackWeaver's reading of what the sourced obligations imply you should be able to produce. It is not the regulator's own checklist. The obligation, penalty and date detail, each tied to its source, is in the Atlas guide for Nigeria.

How StackWeaver gathers this into one control view

StackWeaver view, with each product statement linked to the page that says it

Configuration evidence from connectors

A connector reads settings from a system you already run, using read-only access, and keeps each check as an Evidence Object with a SHA-256 fingerprint (platform). Connector credentials are held in an encrypted vault, never in browser code (platform). A check can pass, fail, be not enabled, or be a check we could not run; failures are kept, not hidden.

Test evidence from your pipeline

Results from the tests your team already runs (for example in CI) can be attached to a control as evidence files. Direct ingestion from a pipeline is not listed as available on this site until it has produced an evidence object in production.

One control view

Evidence from both sources sits against the same control in one view, so one record can support more than one obligation. Our mappings from Nigerian obligations to controls are a draft: each carries the label "Draft mapping, pending named reviewer sign-off" until a named reviewer approves it, and the reviewed control library is still in development (platform).

What we do not do

  • StackWeaver does not issue certifications, audit opinions or regulator approvals (editorial policy; assessment page).
  • We do not say a company is compliant or has passed an audit because of us: only regulators and independent auditors decide that (editorial policy).
  • A named reviewer, not software, decides whether a mapping or a piece of evidence is accepted.

Connector status today

Connector status, 16 October 2026. We list a connector as available only when it has produced evidence in production.

Other connectors are in development and are not available yet. You can upload evidence files to the evidence vault today (platform).

Frequently asked questions

Is Nigeria on the FATF grey list?

No. The FATF removed Nigeria from increased monitoring in October 2025, and Nigeria does not appear on the list of 19 June 2026. That does not remove your obligations: the 2022 Act, the CBN Regulations and the data protection regime all apply in full, and sponsor banks still ask for your evidence.

Sources: 1, 2

How fast must a suspicious transaction be reported?

The Act requires an immediate report to the NFIU and a written report within 24 hours of the transaction. The CBN Guidance Note repeats 24 hours. The NFIU guidelines add that the examination of an alert before filing should take not later than 72 hours, so record when suspicion was formed.

Sources: 1, 2, 3, 4

What breach notices does a fintech have to send?

Three can apply to one incident. A personal data breach goes to the data protection commission within 72 hours. A cyber-incident at a bank or payment service provider goes to the CBN within 24 hours. Cyber threats go to ngCERT immediately and within 72 hours. Run one runbook covering all three.

Sources: 1, 2, 3

Does StackWeaver make a company compliant or certify it?

No. StackWeaver does not issue certifications and does not say a company is compliant or has passed an audit. Only regulators and independent auditors decide that. StackWeaver helps you collect and organise evidence; a named reviewer decides on any mapping.

Sources: 1, 2

Which StackWeaver connectors are live?

One connector is verified live in production today: Okta, with read-only checks of multi-factor sign-in, password policy and single sign-on apps. Other connectors are in development and are not available yet.

Sources: 1

Go further

Sources and method

Every statement of law on this page is recorded in the public claims ledger for Nigeria with its source, section, retrieval date and the exact supporting words, and our build checks each source before publication. Statements about StackWeaver are recorded in a second ledger and link to the page on this site that makes them. Facts are labelled "Sourced"; opinions and recommendations are labelled "StackWeaver view", as oureditorial policy explains. AI tools helped research and draft this page; a named person at StackWeaver is accountable for it. It has not yet been signed off by a named reviewer.

Spotted an error? Email [email protected].