Identity Verification codes
Beta

Last updated: November 28, 2024

Checkout.com's Identity Verification products can have the following:

Identity Verification statuses
Identity Verification attempt statuses
Identity Verification response codes – Also applicable to Face Authentication
AML Verification statuses
Face Authentication statuses

Information

When we add new response codes, we always ensure backward compatibility. However, we recommend basing your business rules on the status value and using response_codes as additional information.

Identity verifications can have the following statuses in API responses and webhook notifications:

Status	Description	Recommended action	Response codes
`created`	You successfully created the identity verification.	Create an attempt.	None
`pending`	You successfully created an attempt and the identity verification session is available.	Redirect the user to the web flow using the `verification_url`.	None
`capture_in_progress`	The user is performing the capture.	Wait for the next status.	None
`checks_in_progress`	Checkout.com is checking the identity verification data.	Wait for the next status.	None
`approved`	The user's identity was successfully verified	Accept the user's request.	`10000`
`declined`	The user's identity was not successfully verified due to an irregularity.	Refuse the user's request. Or, create a new identity verification.	Document issue `62101 – 62103` Copy issue `62201`, `62202` Identity fraud `62301 – 62307` Suspicious behavior `62401 – 62403`
`retry_required`	Checkout.com could not complete all of the required checks and the user needs to retry the flow.	Create a new attempt.	User engagement `61101`, `61111 – 61113`, `61121` Technical issue `61201 – 61205` Document capture `61301 – 61302`, `61310 – 61313`, `61315` Face capture `61401`, `61402`, `61410 – 61412`, `61414` Internal error `61901`, `61911`
`inconclusive`	Checkout.com could not complete the checks and you can no longer retry.	No action is available.	`64001`
`refused`	The user refused to perform the identity verification.	Suggest an alternative way of verifying their identity.	`63001`

Each attempt for an identity verification can have the following statuses in API responses and webhook notifications:

Status	Description
`pending_redirection`	The `verification_url` is available, but the user has not been redirected yet.
`expired`	The `verification_url` expired without the user being redirected to it.
`capture_in_progress`	The user is performing the capture.
`checks_in_progress`	Checkout.com is checking the identity verification data.
`completed`	The user successfully completed the flow in this attempt.
`checks_inconclusive`	Checkout.com could not complete the checks and you can no longer retry.
`capture_aborted`	The user exited the web flow without completing the capture.
`capture_refused`	The user explicitly refused to perform the capture.
`terminated`	You created a new attempt and this attempt is terminated.

Response code	Summary	Description	Status
`10000`	`approved`	Checkout.com approved the identity verification or face authentication.	`approved`
User engagement issue
`61101`	`applicant_never_started`	The user was not redirected to or did not start the web flow.	`retry_required`
`61111`	`applicant_not_ready`	The user clicked a button to state they wanted to perform the flow later.
`61112`	`applicant_no_document`	The user clicked a button to state they did not have their ID document with them.
`61113`	`camera_access_refused`	The user did not give access to their device camera when instructed.
`61121`	`applicant_drop`	The user left the flow before the capture stage and the verification URL expired after 15 minutes.
Technical issue
`61201`	`connexion_insufficient`	The user's connection was too poor to perform the capture.		`retry_required`
`61202`	`browser_not_supported`	The user's browser was not suitable for video streaming.
`61203`	`camera_not_found`	The user's device did not have a camera.
`61204`	`focus_lost`	The user switched tabs or applications during the flow.
`61205`	`sms_not_received`	The user did not receive the SMS.
Document capture issue
`61301`	`document_video_blurry`	The user's document video was too blurry. This is generally due to too much movement. If this error persists, camera quality may be an issue.	`retry_required`
`61302`	`document_video_lighting_issue`	The user performed the document capture in poor light.
`61310`	`document_front_not_captured`	The user did not capture the front of the document.
`61311`	`document_back_not_captured`	The user did not capture the back of the document.
`61312`	`document_partially_hidden`	Part of the document was hidden in the capture.
`61313`	`document_not_tilted`	The user did not move the document dynamically.
`61315`	`document_barcode_unreadable`	The document's barcode was not readable.
Face capture issue
`61401`	`face_video_blurry`	The face video was too blurry. This is generally due to too much movement. If this error persists, camera quality may be an issue.	`retry_required`
`61402`	`face_video_lighting_issue`	The user captured the face video in poor light.
`61410`	`face_not_captured`	The user did not present their face to the camera.
`61411`	`face_partially_hidden`	The user did not present a full front view of their face.
`61412`	`face_not_turned`	The user did not move enough to prove liveness.
`61414`	`various_faces_detected`	The user also captured another person's face.
Internal error
`61901`	`internal error`	Checkout.com could not complete the identity verification due to an internal error. We do our best to reduce how often this occurs.	`retry_required`
`61911`	`corrupted videos`	The videos received could not be played.	`retry_required`
Document issue
`62101`	`document_expired`	The user presented an expired document.	`declined`
`62102`	`document_not_accepted`	The user presented a document that we do not accept.
`62103`	`document_damaged`	The user presented a damaged document.
Copy issue
`62201`	`document_photocopy`	The user presented a photocopy of the document.	`declined`
`62202`	`document_screenshot`	The user presented a screenshot of the document.	`declined`
Identity fraud
`62301`	`document_counterfeit`	The user presented a counterfeit or falsified document.	`declined`
`62302`	`document_stolen`	The user presented a document that has been declared lost or stolen.
`62303`	`document_swap`	The user presented the front and back of two different documents.
`62304`	`face_mismatch`	The user's face in the face video did not match the document photograph.
`62305`	`face_not_live`	The user presented a physical or digital photo or video of another person's face.
`62306`	`face_alteration`	The user altered their appearance.
`62307`	`videos_digital_alteration`	The user digitally altered the videos.
`62311`	`face_face_mismatch`	The face authentication face video does not match any previous identity verification or face authentication for this user.
Suspicious behavior
`62401`	`declared_identity_mismatch`	The user's identity did not match the details they provided.	`declined`
`62402`	`suspicious_device`	The user used a device that has been technically altered.
`62403`	`consent_unclear`	The user seems to have performed the capture under coercion.
User refusal
`63001`	`applicant_refusal`	The user clicked a button to refuse to perform the flow.	`refused`
Programmatic actions
`64001`	`forcibly closed`	The user forcibly closed the flow and the verification URL is no longer valid.	`inconclusive`

AML verifications can have the following statuses in API responses and webhook notifications:

Status	Description	Recommended action
`created`	You successfully created the AML verification.	Wait for the next status.
`screening_in_progress`	Checkout.com is generating the risk score or performing database checks.	Wait for the next status.
`approved`	The risk score is `LOW`, `MEDIUM`, or `HIGH`, and no screening alerts were raised.	Accept the user’s request.
`review_required`	The risk score is `LOW`, `MEDIUM`, or `HIGH`, but screening alerts were raised and a case has been created.	Investigate the case.
`declined`	The risk score returned `PROHIBITED`.	Refuse the user’s request.

Face authentications can have the following statuses and response codes:

Status	Description	Recommended action
`created`	You successfully created a face authentication.	Create an attempt.
`pending`	You successfully created an attempt.	Redirect the user to the `verification_url`.
`capture_in_progress`	The user is capturing their face video.	Wait for the next status.
`checks_in_progress`	Checkout.com is checking the face video.	Wait for the next status.
`approved`	The user is successfully authenticated. They are the same person whose identity you've verified.	Accept the user's request to access services.
`declined`	The user was not authenticated. They are not the same person whose identity you've verified.	Refuse the user's request to access services, or create a new face authentication.
`retry_required`	Checkout.com could not perform all the required checks. The user needs to retry the flow.	Create a new attempt.
`inconclusive`	Checkout.com could not perform all the required checks and you can no longer retry.	No further action is available.
`refused`	The user refused to start the web flow.	Suggest another way for the user to confirm their identity.

Information

Identity Verification statuses

Identity Verification attempt statuses

Identity Verification response codes

AML Verification statuses

Face Authentication statuses