Failure Reasons#
Introduction#
This page lists the possible failure reasons that may occur during the execution of a flow and its underlying technologies.
- A flow is a sequence of steps consisting of multiple technologies.
- An error may occur either at the level of the entire flow or within a specific technology.
- The tables below provide error codes and descriptions returned when a verification attempt fails.
These failure reasons can be used for displaying messages to users, debugging integrations, or building analytics on rejections.
Liveness#
Failure Type | Failure Detail | Description |
---|---|---|
SERVICE_ERROR | Could not send image to liveness service | Failed to send image to the Liveness service (network or server error) |
REQUEST_ERROR | None | Request error (invalid format or corrupted data) |
CLIENT | Could not find face distance | System could not detect the distance to the face |
CALC_RESULT | Closed eyes | Eyes closed, verification not possible |
CALC_RESULT | Low prediction | Low probability of successful verification |
CALC_RESULT | Low overall prediction | Overall score too low for confirmation |
OTHER | Incorrect image hash | Image failed integrity check (possibly tampered or corrupted) |
CLIENT | Liveness result for this session already exists | Liveness result already exists for this session |
SERVICE_ERROR | None | Internal service error |
CLIENT | Operation aborted by user | User aborted the process |
OTHER | Operation aborted by user | Process stopped by external cause |
CLIENT | No active or future subscription for technology | No active subscription for the technology |
CLIENT | Subscription does not have access to technology | Subscription does not grant access to the technology |
CLIENT | Could not send image to liveness service | Failed to send photo to the Liveness service |
NO_CAM | None | Camera not found or disabled |
TIMEOUT | None | Request timed out |
CLIENT | Medical mask check failed | Medical mask detected, verification failed |
CALC_RESULT | Mask Attack | Mask attack detected |
CLIENT | Illumination check failed | Poor lighting conditions (too dark/bright) |
CLIENT | Glasses check failed | System could not properly process face with glasses |
SERVICE_ERROR | Can`t connect to liveness service | Unable to connect to Liveness service |
CLIENT | Maximum number of attempts has been used | Maximum number of attempts reached |
DIFFERENT_FACES | Different faces in liveness detections | Different faces detected across frames |
Face2Face#
Failure Type | Failure Detail | Description |
---|---|---|
SERVICE_ERROR | Can`t connect to face2face service | Unable to connect to Face2Face |
CALC_RESULT | Different faces | Faces on selfie and reference do not match |
SERVICE_ERROR | No face found | No face detected on the image |
Document Recognition#
Failure Type | Failure Detail | Description |
---|---|---|
NO_CAM | None | Camera not found or disabled |
CLIENT | Wrong document country | Document from unsupported country |
OTHER | Wrong document country | Document country not supported |
OTHER | Wrong document side | Wrong side of document provided |
CLIENT | Wrong document side | User uploaded wrong side of document |
OTHER | Document type mismatch | Document type not supported |
TIMEOUT | None | Document upload timed out |
CLIENT | Error while parsing document | Error while processing document |
CLIENT | Document Recognition result for this session exists | Document recognition result already exists |
CLIENT | Document type mismatch | Document type does not match expected |
CLIENT | Operation aborted by user | User aborted document upload |
OTHER | Operation aborted by user | Document recognition process aborted externally |
SERVICE_ERROR | Error while parsing document | Internal error while processing document |
OTHER | Error while parsing document | Document parsing error |
E-Document#
Failure Type | Failure Detail | Description |
---|---|---|
REQUEST_ERROR | None | Error while forming request |
CLIENT | Subject not found in MCDB | User not found in MCDB |
CLIENT | Document type is not the same as requested type | Document type does not match requested type |
CLIENT | Profile is not found | User profile not found |
CLIENT | Document does not exist | Document does not exist in the database |
CLIENT | Operation aborted by user | User aborted the process |
SERVICE_ERROR | DL service not available now. | Document issuing service temporarily unavailable |
SERVICE_ERROR | Government service error | Error on government service side |
CLIENT | Too many requests to e-document service | Too many requests to e-document service |
SERVICE_ERROR | E-Document service is not available now | E-Document service unavailable |
SERVICE_ERROR | Could not send request to E-Document service | Failed to send request to E-Document service |
SERVICE_ERROR | Can`t connect to E-Document service | Could not connect to E-Document service |
CLIENT | Access to document is not found or is not active | Access to document not found or inactive |
Address v1 / v2#
Failure Type | Failure Detail | Description |
---|---|---|
SERVICE_ERROR | Can`t connect to address service | Unable to connect to Address service |
CLIENT | TIMEOUT | Request timed out |
CLIENT | INVALID | Invalid input data |
CLIENT | NOT_FOUND | Address not found in database |
SERVICE_ERROR | Internal service error |
GBDFL v1 / v2#
Failure Type | Failure Detail | Description |
---|---|---|
CLIENT | Person not found, invalid IIN or IIN not found | User with given IIN not found |
SERVICE_ERROR | A server error occurred. | Internal GBDFL service error |
CLIENT | INVALID | Invalid input data |
CLIENT | NOT_FOUND | Data for IIN not found |
REQUEST_ERROR | None | Request error |
CLIENT | GBDFL token already received | GBDFL token already received |
OTHER | Service error | Other service error |
REQUEST_ERROR | Unexpected error | Unexpected error |
Face2Face (NPCK)#
Failure Type | Failure Detail | Description |
---|---|---|
CLIENT | Credentials not provided | Credentials not provided |
SERVICE_ERROR | F2F NPCK service unavailable | Face2Face (NPCK) service unavailable |
Kz-Info#
Failure Type | Failure Detail | Description |
---|---|---|
SERVICE_ERROR | Exec proc info request failed | Error executing request in Kz-Info service |
DS Identifier / DS Signer#
Failure Type | Failure Detail | Description |
---|---|---|
CLIENT | Digital Signature invalid input | Invalid data for Digital Signature (incorrect input or format mismatch) |
CLIENT | Digital Signature Identity card does not exist | Identity card not found in Digital Signature database |
CLIENT | Digital Signature Organization Client does not exist | Organization client for Digital Signature not found |
CLIENT | Digital Signature Client does not exist | Digital Signature client not found |
CLIENT | Digital Signature Organization does not exist | Organization for Digital Signature not found |
CLIENT | Digital Signature Identifier result for this session does not exist | DS Identifier result does not exist for this session |
CLIENT | Digital Signature Identifier result for this session already exists | DS Identifier result already exists for this session |
CLIENT | Failure reason for this Digital Signature Identifier result already exists | Failure reason for DS Identifier already logged for this session |
CLIENT | Client does not have access to Digital Signature Identifier technology | Client does not have access to DS Identifier technology |
SERVICE_ERROR | Cannot connect to Digital Signature service | Could not connect to Digital Signature service |
SERVICE_ERROR | Digital Signature service is not available now | Digital Signature service temporarily unavailable |
Flow#
Failure Type | Failure Detail | Description |
---|---|---|
EXPIRED | Flow session was expired | Flow session expired (user did not complete the KYC process in time) |
OTHER | Any | Unexpected error |