Live face verification, not a photo comparison
A live camera capture, checked for liveness, then matched 1:1 against the registry photo at proof time — the step that turns a registry number into a person you can actually confirm.
What the verification call returns
A 1:1 face-verify call resolves to one of four real outcomes — the same ones the consumer app, Merchant Desk, and Institution Console branch on:
matchMatch
The captured face matches the registry photo above the confidence threshold — the identity link proceeds.
no_matchNo match
The captured face doesn't match closely enough. Nothing is linked.
too_close_to_callToo close to call
A near-tie score is flagged for manual review rather than auto-approved or auto-rejected.
liveness_failedLiveness failed
The liveness check didn't pass. The flow stops before any face comparison happens at all.
A canonical embedding, not a photo library
A successful proof is converted into a single canonical 512-dimensional ArcFace embedding per enrolled person — a numeric representation of the face, not a stored photo. When a new enrollment replaces it, the prior embedding is archived to an internal audit table rather than kept as an active, searchable record. A liveness check runs before any of this — a printed photo or a screen replay never reaches the matching engine. Full detail is in the Security page and Privacy Policy.
From a single proof to 1:N identification
The same embedding created at proof time is what later powers 1:N identification at a merchant desk or branch — see the full verification pipeline or the identity verification API overview.
Request access to face verification
Tell us how you're planning to use it and we'll size the integration with you.