
Verification Process
When performing liveness detection, the system attempts to:- Detect and analyze faces in the captured images/video
- Perform liveness detection to prevent spoofing
- Validate the quality and authenticity of the biometric data
Automatic Decline Conditions
The following conditions will always result in an automatic decline regardless of application settings:NO_FACE_DETECTED- No face was detected during the liveness checkLIVENESS_FACE_ATTACK- The system detected a potential spoofing attemptFACE_IN_BLOCKLIST- The face matches an entry in your face blocklist
Configurable Verification Settings
Applications can configure how the system handles various verification issues:-
Low Liveness Score
- Risks:
LOW_LIVENESS_SCORE - Configurable thresholds:
- Review threshold: Sessions with scores below this threshold are set to “In Review”
- Decline threshold: Sessions with scores below this threshold are automatically declined
- Risks:
-
Duplicate Face
- Risks:
POSSIBLE_DUPLICATED_FACE,DUPLICATED_FACE - Configurable action: Decline, Review, or Approve
- Risks:
-
Multiple Faces Detected (Passive Liveness only)
- Risks:
MULTIPLE_FACES_DETECTED - Configurable action: Decline, Review, or Approve
- Note: The largest face is always used for liveness scoring and face comparison
- Risks:
-
Face Quality (Passive Liveness only)
- Risks:
LOW_FACE_QUALITY - Configurable thresholds:
- Review threshold: Sessions with face quality below this threshold are set to “In Review”
- Decline threshold: Sessions with face quality below this threshold are automatically declined
- Risks:
-
Face Luminance (Passive Liveness only)
- Risks:
LOW_FACE_LUMINANCE,HIGH_FACE_LUMINANCE - Configurable thresholds:
- Minimum threshold: Sessions with luminance below this are flagged
- Maximum threshold: Sessions with luminance above this are flagged
- Configurable action for each: Decline or Review
- Risks:
Warning Rejection Tags
The following warnings may occur during liveness detection. While these warnings don’t necessarily indicate fraud, they should be carefully evaluated based on your security requirements:Tag | Description |
|---|---|
FACE_IN_BLOCKLIST | The face has been identified as matching an entry in your face blocklist. This occurs when the biometric data matches a previously blocklisted individual. |
POSSIBLE_FACE_IN_BLOCKLIST | The system identified a possible face in the blocklist, which means the face is not allowed to be verified. |
LOW_LIVENESS_SCORE | The liveness check resulted in a low score, indicating potential use of non-live facial representations or poor-quality biometric data. |
NO_FACE_DETECTED | The system couldn’t identify a face during the liveness check, which may be due to poor image quality, improper positioning, or technical issues. |
LIVENESS_FACE_ATTACK | The system detected a potential attempt to bypass the liveness check. |
DUPLICATED_FACE | The system identified a duplicated face from another approved session, requiring further investigation. |
POSSIBLE_DUPLICATED_FACE | The system detected that this face may match another user already approved in the system, suggesting a potential duplicate account or identity. |
MULTIPLE_FACES_DETECTED | Multiple faces were detected in the liveness image. The system uses the largest face for liveness verification and face comparison, but the presence of multiple faces may require additional review. (Passive Liveness only) |
LOW_FACE_QUALITY | The facial image quality is below the acceptable threshold, which may affect the reliability of liveness detection. This could be due to camera resolution, focus, or compression artifacts. (Passive Liveness only) |
LOW_FACE_LUMINANCE | The facial image is too dark, which may affect the accuracy of liveness detection. Better lighting conditions are recommended. (Passive Liveness only) |
HIGH_FACE_LUMINANCE | The facial image is too bright or overexposed, which may affect the accuracy of liveness detection. Reduced lighting or avoiding direct light is recommended. (Passive Liveness only) |