One API for NIN, BVN, and face verification
FaceTrust AI links a NIN or BVN registry identity to a real, live face, then reuses that same proof for 1:N identification — as a documented, versioned API, not a screen you have to reverse-engineer.
What the API verifies
NIN & BVN registry validation
Check a NIN or BVN against the registry and get back a masked name and status — active, not-found, or mismatch — without ever exposing the registry photo directly.
Face verification (1:1)
A live capture is matched against the registry photo at proof time, with a liveness check run first to reject a printed photo or a screen replay before it reaches the matching engine.
1:N face identification
Identify a person against your enrolled population from a live camera capture — the same call the Merchant Desk and Institution Console make themselves, designed for a sub-second response.
One canonical embedding, not a photo album
A successful face proof is converted into a single canonical face embedding per person. The raw registry photo isn't retained after that step.
Built like infrastructure, not a demo
The same endpoints power every FaceTrust AI surface — consumer app, Merchant Desk, and Institution Console. See the full endpoint reference on the Developers page.
Idempotency
Identity-linking and identify calls accept an idempotency key, so a retried request after a dropped connection can't double-enroll or double-log a scan.
Per-identifier rate limiting
Endpoint classes are rate-limited independently, with tighter per-NIN/BVN throttling on face-verify calls as a brute-force control.
Versioned, real endpoints
Every route is the same one the consumer app, Merchant Desk, and Institution Console call themselves — nothing is UI-only or mocked for the docs.
Data handling and access
Photo access is gated behind a successful face proof, every comparison is audit-logged, and staff access is layered by role. Read the full breakdown on the Security page and how data is processed under the Privacy Policy. API reference access is granted to approved institutions and merchants after onboarding — see how the verification pipeline works end to end.
Request API access
Tell us what you're building — NIN/BVN validation, face verification, or 1:N identification — and we'll size the integration with you.