Use case · BVN and NIN onboarding
BVN and NIN onboarding
No document.Just a numberand a face.
Most Nigerian customers know their BVN or NIN by heart and do not carry the card. Toden looks the number up with the issuing authority, compares a live selfie with the photo on that record, and returns a decision in one step, with nothing to photograph.
The workflow
A number, a selfie and the government record: the shortest route to a verified Nigerian customer. This is a starting point: add, remove or reorder any step in the workflow builder.
Step 01
Phone Verification
Proves the phone number with a one-time code
Step 02
Government database validation
Nigeria, BVN: name, date of birth and photo
Step 03
Passive Liveness
A selfie with no prompts
Step 04
Facial Match
Selfie against the photo on the BVN record
Step 05
Device Intelligence
Flags shared devices and risky networks
Step 06
Face Search
Has this face opened an account under another name?
Then your rules decide
A starting rule set
- The selfie does not match the record photoDecline
- The record is suspended by the issuerDecline
- The name on the record differs from the one you holdReview
- The same face is already verified under another nameReview
- Everything agreesApprove
Every rule is yours to change on a visual canvas, and each result records which rule decided it. Publishing a new version needs no release.
Try the workflow builderConnection map
When a face, a phone or an address turns up again, the console draws everyone gathered around it and says in plain words what the connection means and how much weight it deserves.
- Needs review2 people with this face verified under a different nameA shared address does not explain a shared face. Compare the photos before deciding.
- For context1 person with this face has the same name and documentThis may be a repeat verification. Check whether more than one account is expected.
- An illustration with invented people. In the console each card opens the customer's record.
How it works
The customer types a number
They enter a BVN, NIN or virtual NIN in your app or on a hosted link, with a one-time code to prove the phone is theirs.
The record answers
Toden looks the number up, compares the name and date of birth you hold with the record, and matches a live selfie to the record photo on our own servers.
Your rules decide
A workflow approves a clean match, sends a name that differs to review, and declines a selfie that is not the person on the record.
What powers it
The number is checked with the issuing authority, so a typed number that belongs to nobody, or to somebody else, does not pass.
Integrate
Mount the SDK with the workflow you published, or send a hosted link and write no code. The result arrives by signed webhook, and changing the workflow never needs a release.
import { TodenVerification } from "@todenhq/sdk-react"; export function Verify({ userId }) { return ( <TodenVerification apiKey="pk_test_..." workflowId="wf_AbC123dEf456" userId={userId} onSubmit={(s) => save(s.verificationId)} /> );}{ "event": "verification.completed", "data": { "verificationId": "ver_8fk2...", "status": "verified", "assuranceLevel": "gov_db", "idType": "bvn", "country": "NG", "dataMatch": true, "facialMatch": true, "facialConfidence": 91 }}Products involved
This solution combines products you can use on their own too.
Related use cases
Frequently asked
BVN, NIN and virtual NIN are verified from the number alone. Passports, driver's licences and voter's cards are verified from the document, with the government record checked as well.
BVN and NIN onboarding,in one workflow.
The sandbox opens when you sign up. Usage-based pricing, no sales call.