Face Authentication

When to use it

Face Authentication lets a customer register their face once, then re-authenticate against that registration for subsequent logins or transactions — a face-based replacement (or second factor) for a text password on future sessions, rather than a one-time onboarding check.

Lifecycle

1. Register a customer's face — from a selfie, from the face captured on their ID card, or both. Optional gesture and video capture add a liveness check at registration time, and you can attach your own metadata to the record.
2. Authenticate a customer against their registered face on a later session, and get back a match verdict and confidence score. Each check can be tagged with why you're asking for it (login, payment, transfer, password reset, or a reason of your own), and you choose how strong a liveness check to require — from a light check up through full active-liveness verification.
3. Check registration status — confirm whether a customer is already registered, and see their registration history, before prompting them to register again.
4. Unregister a customer's face when they opt out or need to re-enroll.
5. Unlock an account that's been locked or deactivated after repeated failed authentication attempts.

Standalone vs. combined with eKYC onboarding

TrustVision documents two deployment patterns for Face Authentication under "Suggested scenarios (FaceAuthen System deployed On-premise or Cloud)" on the eKYC Core API page:

• Standalone — your backend calls Register/Authenticate directly for login or transaction authentication, independent of any onboarding flow.
• Combined with onboarding — Face Authentication runs alongside user onboarding on TrustVision's eKYC system, so the same registered face used to onboard a customer can later authenticate their logins or transactions.