Questions we get asked a lot

No. FaceTrust AI is a verification layer that sits on top of the existing NIN and BVN registries — it validates a number against the registry, then adds the face proof step those registries don't do themselves.

Under a second end-to-end is the design target, from camera capture to a match, no-match, or flagged near-tie.

Today the consumer experience is a mobile-optimized web app — native iOS and Android apps are on the roadmap.

Any standard webcam connected to the desk's computer works — there's no special hardware requirement beyond a working camera.

The link or check is refused — no name, no number, no unlocked account. Near-tie cases are flagged for manual review rather than auto-approved or auto-rejected.

No photo album. A live capture is compared against the registry photo at proof time, then converted into a single canonical face embedding for your account — the raw registry photo isn't retained by FaceTrust AI after that.

Yes — deleting your account removes the biometric record first, before the rest of the profile, from the consumer app directly.

A liveness check runs before any face comparison specifically to catch that — a printed photo or a screen replay is rejected before it reaches the matching engine.

Banks, microfinance institutions, and other licensed businesses can onboard through a KYB flow backed by real CAC registry validation, then manage branches, desks, and staff from the Institution Console.

It depends on integration depth — a single-branch Merchant Desk pilot is fast to stand up, a full network rollout with custom requirements takes longer to scope. This gets sized during the pricing conversation.

Escalated comparisons land in a review queue your staff work through in the Institution Console, tied back to the original confidence score and outcome — not a reconstruction of what happened after the fact.

Invoices and payment status are available directly in the Institution Console's Billing tab, scoped to your institution.