BVN
Proves this person exists in the banking system, tied to one set of biometrics across every bank they use. Doesn't prove the person in front of you is that person. A BVN can be known, borrowed, or bought.
KYC IMPLEMENTATION GUIDE
BVN, NIN, VNIN and liveness: what each one proves, and how to build an onboarding flow that holds up under examination.
For banks, payment service providers, mobile money operators, lenders, and other regulated institutions.
Download the guideIDENTITY VERIFICATION
A practical reference for Nigerian institutions
THE DISTINCTION THAT MATTERS
A customer typing an identity number into a form is identification. Querying the authoritative source, getting a response, and checking it against what the customer supplied is verification. A file full of documents nobody ever checked against anything looks complete and proves nothing.
Nigeria has an advantage most markets don't: national identity infrastructure you can query in real time. That makes real verification achievable rather than aspirational, and it raises the bar you're held to.
Proves this person exists in the banking system, tied to one set of biometrics across every bank they use. Doesn't prove the person in front of you is that person. A BVN can be known, borrowed, or bought.
Proves registration in the national identity database, reaching people who've never held a bank account. Same limit as the BVN: it confirms a record exists, not that the person presenting it owns it.
A tokenised version of the NIN, generated per enterprise, not retained after use, and created deliberately by the customer, which builds a consent trail your data protection obligations actually want.
WHAT'S INSIDE
This is a working reference. If you're building the onboarding flow right now, jump straight to Part V.
Why identification and verification aren't the same thing, and why Nigeria's identity infrastructure raises the standard you'll be examined against.
BVN, NIN and VNIN explained side by side: what each one proves, what it can't prove, and why the tokenised route matters for your interface, not just your compliance file.
Passive versus active liveness, presentation attacks versus generated video, and why an analyst watching a feed won't reliably catch a good synthetic anymore.
Why identities built from real and fabricated data pass onboarding cleanly, and why catching them later depends on whether your systems share data at all.
Eight steps from identifier verification through to passing every signal captured into your monitoring system, including the one step most flows quietly drop.
Collection presented as verification, undocumented overrides, due diligence that stops on day one, static risk ratings, and signals thrown away instead of reused.
DOWNLOAD THE GUIDE
Leave your email, and we'll send the guide, plus a note if NIMC or the CBN changes how any of these identifiers work. No spam. Unsubscribe anytime.
FAQ
Because neither one confirms the person in front of you is the person the number belongs to. A BVN or NIN check is a lookup against a record, and a record can be known, borrowed or bought by someone who isn't its owner. Liveness is the step that closes that specific gap, confirming a real person is physically present at the moment of verification rather than a photo, a screen replay, or a generated face.
Because the token is generated per enterprise, isn't meant to be retained after use, and is created deliberately by the customer rather than typed passively into a form. That combination reduces how much raw identity data you're holding and builds a consent trail that sits far better against your data protection obligations. It costs you a step in the funnel, but it's the step that protects you later.
It depends on what you're optimizing for at that moment. Passive liveness asks nothing of the customer and completes at a higher rate, but it's easier to defeat than active liveness, which asks them to turn their head or blink and is harder to fool. Most institutions run passive by default for everyone and trigger active only when risk signals say the extra friction is worth it.
Because at the moment of onboarding, nothing about a synthetic identity looks wrong. It's built from a real identity number paired with a fabricated name and a controlled phone number, and it passes every static check cleanly. These identities are patient. They behave normally for months before they're used, which means the only way to catch them is behavior over time, not a single check at the door.
Because a device fingerprint or a liveness score captured at onboarding and never seen again by any other system is money spent for nothing. Synthetic identities and mule networks get caught through relationship signals, like several unrelated accounts sharing one device or one address, and that only works if the systems that could see the connection are actually looking at the same data.
Yes, and it's worth planning for specifically rather than assuming document fraud defenses cover it. Biometric and deepfake-driven attacks are more prominent in West Africa than the document forgery that dominates in several neighboring markets. An institution that's calibrated its defenses against forged documents alone is defending the wrong perimeter.
FREE HANDBOOK
Customer due diligence, sanctions and PEP screening, transaction monitoring, and financial crime risk assessment, explained against the rules that actually apply in Nigeria.
Download HandbookFRAUD PREVENTION CHECKLIST
A starting rule set for transaction monitoring, with the action each rule should trigger and the behaviour each is built to catch.
Download GuideFRAUD RISK ASSESSMENT TEMPLATE
25 questions, a score, and a roadmap tied to where your institution actually stands, not where your policy says it stands.
Download Guide