Liveness

Liveness confirms that a real person is present and that their face matches the portrait from document verification. It reduces spoofing (photos, screens, masks) and is the usual companion step for full identity verification.

What it does

1. Requires a completed document step that produced a portrait
2. Prompts the user through an active liveness capture
3. Runs anti-spoof and quality checks (brightness, sharpness, occlusion, eyes, …)
4. Compares the live face to the document portrait against your match threshold
5. Optionally supports biometric uniqueness checks (contact support to enable)

Where it sits in a flow

Always after document verification (or another step that supplies a reference portrait). Without that link, face match has nothing trusted to compare against.

Outcomes you should handle

Failures often surface as DV/liveness-related reason codes such as LIVENESS_CHECK_FAILED, LIVENESS_ANTISPOOF_FAILED, or FACE_MATCH_CHECK. See Statuses and codes. Tune the minimum portrait match percent if you see too many false rejects vs fraud risk.

Configure it

→ Liveness guide · Create a flow

Related

• Document verification
• Verification process
• Scoring, combine biometric and other signals into review policy