🎉 Unlimited Free KYC - Forever!!

Identity Verification
Liveness
Warnings

Liveness Detection Warnings and Errors

Our liveness detection process includes automated checks to verify the authenticity of users through biometric analysis. This page outlines the potential warnings and errors you might encounter during the liveness detection process.

Liveness Detection Warnings

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 check
  • LIVENESS_FACE_ATTACK - The system detected a potential spoofing attempt
  • FACE_IN_BLOCKLIST - The face matches an entry in your face blocklist

Configurable Verification Settings

Applications can configure how the system handles various verification issues:

  1. 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

  2. Possible Duplicate Face

    • Risks: POSSIBLE_DUPLICATED_FACE
    • Configurable action: Decline, Review, or Approve

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.
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.
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.

Warning Types

Each risk is assigned a warning type based on your application's configuration settings. Warnings fall into three severity categories:


TypeDescription
ERROR
Critical issues that resulted in setting the session to `Declined`
WARNING
Issues that require attention that resulted in setting the session to `In Review`
INFORMATION
Informational messages that don't affect verification outcome
ReportHow it Works