Every surface FaceTrust AI ships — consumer app, Merchant Desk, Institution Console — is a thin client over one documented API. Nothing important is logic baked into a screen.
Identity linking
Validate a NIN/BVN and link it to an account with a face proof.
Verification
1:N identify calls and self-verification.
Profile & audit
Consumer profile management and the audit trail behind it.
Operators & institutions
Staff, branches, and institution-level administration.
Analytics
Accuracy, volume, and billing, scoped to your institution.
There's no single login flow — what's required to authenticate scales with what that session can do.
Consumer
Phone number + OTP, then a face proof for anything identity-linked.
Operator
Operator code + password, with a forced reset on first login.
Institution officer / branch manager
Work email + OTP + password + a face check, re-proved for sensitive actions.
Superadmin
Work email + OTP + face check + a hardware security key, with two-person approval on the most sensitive actions.
Mutating calls on identity linking and identify support an idempotency key, so a retried request after a dropped connection can't double-enroll or double-log a scan.
Endpoint classes are rate-limited independently, with tighter per-NIN/BVN throttling on face-verify calls as a brute-force control.
Every endpoint above is a real, versioned route — the same ones the consumer app, Merchant Desk, and Institution Console call themselves. Nothing is UI-only.
Full API reference and integration guides are available for approved institutions and merchants — reach out for access.
Tell us what you're building and we'll get you API reference access.