Identities codes
Beta
Last updated: May 28, 2025
Identities checks can have the following statuses, attempt statuses, and response codes.
Information
When we add new response codes, we always ensure backward compatibility. However, we recommend basing your business rules on the status, and then using response codes as additional information.
Checks can have the following statuses in API responses and webhooks:
Status | Description | Recommended action | Response codes |
---|---|---|---|
| You successfully created the check. | Create an attempt. | |
| You successfully created an attempt and the verification/authentication URL is available. | Redirect the applicant to the flow. | |
| The applicant is capturing their document and/or face. | Wait for the next status. | |
| Checkout.com is processing the check. | Wait for the next status. | |
| For AML Screening, Checkout.com is screening databases and generating the risk score. | Wait for the next status. | |
| For AML Screening, the risk score is | Investigate the case. | |
| The check was successful and the applicant is approved. For AML Screening, the risk score is | Accept the applicant's request. |
|
| The check was not successful and the applicant is declined. For AML Screening, the risk score is | Refuse the applicant's request, or create a new check. | Document issue |
| Checkout.com could not complete the check. | Create a new attempt. | User engagement |
| Checkout.com could not complete the check and you can no longer retry. | No action is available. |
|
| The applicant refused to start the flow. | Suggest an alternative to the applicant. |
|
Each attempt can have the following statuses in API responses and webhooks:
Status | Description |
---|---|
| The attempt is created, but the applicant has not yet been redirected to the verification/authentication URL. |
| The verification/authentication URL expired. |
| The applicant is capturing their document and/or face. |
| Checkout.com is processing the check. |
| The applicant successfully completed the flow in this attempt. |
| Checkout.com could not complete the check and you can no longer retry. |
| The applicant dropped out of the flow without capturing their document and/or face. |
| The applicant explicitly refused to perform the capture. |
| You created a new attempt and this attempt is closed. |
The following response codes provide more information about the check status:
Response code | Summary | Description | Status |
---|---|---|---|
|
| The check was successful and the applicant is approved. |
|
User engagement issue | |||
|
| The applicant was not redirected to or did not start the flow. |
|
|
| The applicant clicked a button to state they wanted to perform the flow later. | |
|
| The applicant clicked a button to state they did not have their document with them. | |
|
| The applicant did not give access to their device camera when instructed. | |
|
| The applicant dropped out of the flow before capturing their document and/or face and the verification/authentication URL expired. | |
Technical issue | |||
|
| The applicant's connection was too poor to capture their document and/or face. |
|
|
| The applicant's browser was not suitable for video streaming. | |
|
| The applicant's device did not have a camera. | |
|
| The applicant switched tabs or applications during the flow. | |
|
| The applicant did not receive the SMS. | |
Document capture issue | |||
|
| The applicant's document video was too blurry. |
|
|
| The applicant performed the document capture in poor light. | |
|
| The applicant did not capture the front of the document. | |
|
| The applicant did not capture the back of the document. | |
|
| Part of the document was hidden in the capture. | |
|
| The applicant did not move the document dynamically. | |
|
| The document's barcode was not readable. | |
Face capture issue | |||
|
| The face video was too blurry. |
|
|
| The applicant captured the face video in poor light. | |
|
| The applicant did not present their face to the camera. | |
|
| The applicant did not present a full-frontal view of their face. | |
|
| The applicant did not move enough to prove liveness. | |
|
| The applicant also captured another person's face. | |
Internal error | |||
|
| Checkout.com could not complete the check due to an internal error. |
|
|
| The videos received could not be played. | |
Document issue | |||
|
| The applicant presented an expired document. |
|
|
| The applicant presented an unsupported document. | |
|
| The applicant presented a damaged document. | |
Copy issue | |||
|
| The applicant presented a photocopy of the document. |
|
|
| The applicant presented a screenshot of the document. | |
Identity fraud | |||
|
| The applicant presented a counterfeit or falsified document. |
|
|
| The applicant presented a document that has been declared lost or stolen. | |
|
| The applicant presented the front and back of two different documents. | |
|
| The applicant's face in the face video did not match the document portrait. | |
|
| The applicant presented a physical or digital photo or video of another person's face. | |
|
| The applicant altered their appearance. | |
|
| The document and/or face videos are digitally altered. | |
|
| The face video does not match any previous identity verification or face authentication for this applicant. | |
Suspicious behavior | |||
|
| The applicant's identity did not match the details they provided. |
|
|
| The applicant used a device that has been technically altered. | |
|
| The applicant appears to have captured their document and/or face under coercion. | |
|
| The applicant presented multiple documents. | |
User refusal | |||
|
| The applicant clicked a button to refuse to perform the flow. |
|
Attempts | |||
|
| You closed the attempt and the verification/authentication URL is no longer valid. |
|