Verify identities using the Dashboard
Beta

Last updated: January 21, 2026

The Identity Verification solution enables you to verify the identity of a person applying to use your services. This helps you meet compliance requirements and reduce the risk of fraud.

The applicant captures video of their ID document and face. Checkout.com checks if the document is genuine and matches the person in the video, and shares the result and a full report.

Information

To enable Identity Verification, contact your account manager or request support.

Integrate Identity Verification in your web app or mobile app.
Handle statuses, attempts, and response codes.
Configure your webhook server and subscribe to Identity Verification webhooks.
Create an applicant profile.

When you request to enable Identities, your account manager provides you an Identity Verification configuration ID, prefixed with usj_.

You must provide this ID every time you create a verification. It configures the following elements of the solution:

The service level agreement for receiving the result from Checkout.com
ID documents:
- The documents you want to accept, if supported by Checkout.com
- Whether you require one document or two – primary and secondary
- The data you want to extract from documents
Whether you require a video of the applicant's face
Processing type:
- Fast – Highly automated processing, with human review if required
- Expert – Systematic human review

Create an identity verification linked to the applicant's profile.
Create an attempt.
Redirect the applicant to the attempt URL.
View the identity verification to see the result.
Download the identity verification report.
If requested, you can remove the applicant's personal details from the identity verification.

To create an identity verification and an initial attempt, you need one of the following user roles:

Admin
Identities manager
A custom role with the Process identities checks and manage configurations permission

If the applicant you want to verify already has a profile, retrieve their applicant ID, and then follow these steps:

Sign in to the Dashboard.
Go to Identities > Identity verification.
Select Create verification.
In the Create verification window, enter the applicant's full name.
Enter the applicant ID, prefixed with aplt_.
Select the configuration you want to apply to the verification from the drop-down.
Enter the URL to redirect the applicant to after they complete the verification. For example, your success or failure URL.
Select Create verification.

The verification ID and the attempt URL are displayed, which you can copy if required.

If the identity verification is created successfully:

You receive a verification ID, prefixed with idv_.
The identity verification status changes to created.
You receive an Identity verification created webhook.

If the attempt is created successfully:

You receive an attempt ID, prefixed with iatp_.
You receive the attempt URL.
The attempt status changes to pending_redirection.
The identity verification status changes to pending.
You receive an Identity verification opened webhook.

To create an identity verification attempt, the identity verification status must be one of the following:

created
pending
capture_in_progress
retry_required

You need one of the following user roles:

Admin
Identities manager
A custom role with the Process identities checks and manage configurations permission

Sign in to the Dashboard.
Go to Identities > Identity verification.
Search or filter for the verification you want to create an attempt for, and select it.
On the Verification details page, select Create attempt.
In the Create attempt window, provide the URL to redirect the applicant to after they complete the verification. For example, your success or failure URL.
Select Confirm.
The verification ID and URL are displayed, which you can copy if required.
Select Done.

On the Verification details page, under Verification, the attempt appears on the Timeline tab.

If the attempt is created successfully:

You receive an attempt ID, prefixed with iatp_.
You receive the attempt URL.
The attempt status changes to pending_redirection.
The identity verification status changes to pending.
You receive an Identity verification opened webhook.

For web integration, redirect the applicant to the attempt URL, which is valid for 15 minutes.

For SDK integration, pass the following to the SDK:

The attempt URL, which is valid for 15 minutes
The client_secret, which is valid for 48 hours, to authorize the verification

Note

If an attempt is unsuccessful and the applicant needs to retry, you can create new attempts.

The following table describes the process of a successful attempt:

Scenario Description

Scenario	Description
Applicant starts the attempt	The identity verification and attempt statuses change to `capture_in_progress`. You receive an Identity verification started webhook. When successfully completed, the attempt status changes to `completed`. You receive an Identity verification capture completed webhook.
Checkout.com processes the verification	The identity verification status changes to `checks_in_progress`. Recommended action – You can ask the applicant to perform additional checks or to wait for the result. When processing is complete, you receive an Identity verification checks completed webhook. You may receive the checks completed webhook simultaneously with the capture completed webhook.
Result is available	The identity verification status changes to one of the following: `approved` – The identity verification is successful. `declined` – The identity verification is declined. If you want to enable the applicant to retry, create a new verification. You receive an Identity verification report created webhook.

Applicant starts the attempt

The identity verification and attempt statuses change to capture_in_progress.

You receive an Identity verification started webhook.

When successfully completed, the attempt status changes to completed.

You receive an Identity verification capture completed webhook.

Checkout.com processes the verification

The identity verification status changes to checks_in_progress.

Recommended action – You can ask the applicant to perform additional checks or to wait for the result.

When processing is complete, you receive an Identity verification checks completed webhook.

You may receive the checks completed webhook simultaneously with the capture completed webhook.

Result is available

The identity verification status changes to one of the following:

approved – The identity verification is successful.
declined – The identity verification is declined. If you want to enable the applicant to retry, create a new verification.

You receive an Identity verification report created webhook.

An attempt may be unsuccessful due to the following scenarios:

Scenario	Description
Attempt URL expires	The attempt status changes to `expired`. You receive an Identity verification link expired webhook. Recommended action – Create a new attempt.
Applicant refuses the verification	The identity verification status changes to `refused`. The attempt status changes to `capture_refused`. You receive an Identity verification capture refused webhook. Recommended action – Suggest an alternative verification method to the applicant.
Applicant drops out of the attempt	The attempt status changes to `capture_aborted`. You receive an Identity verification capture aborted webhook. Recommended action – You can create a new attempt.
Applicant needs to retry	The identity verification status changes to `retry_required`. You receive an Identity verification retry requested webhook. When you create a new attempt, the status of the previous attempt changes to `terminated`. You receive an Identity verification closed webhook, followed by an Identity verification reset webhook. Recommended action – Redirect the applicant to the new attempt URL.
Result is inconclusive	The identity verification status changes to `inconclusive`. The attempt status changes to `checks_inconclusive`. You receive an Identity verification checks inconclusive webhook. Recommended action – You can create a new attempt.

Information

You can use the response codes returned in webhooks to implement your own business logic.

Sharing guidance from the response codes with the applicant can help the next attempt succeed. For example, if the applicant's data connection is poor, let them know so they can try to improve it.

To view an identity verification attempt, you need one of the following user roles:

Admin
Identities manager
A custom role with the View identities checks and data or Process identities checks and manage configurations permission

Sign in to the Dashboard.
Go to Identities > Identity verification.
Search or filter for the verification you want to view an attempt for, and select it.
On the Verification details page, under Verification, all attempts appear on the Timeline tab.

You can view the identity verification at any time. For example, to check the status or details of an attempt. When the result is available, it is displayed in the Dashboard.

You need one of the following user roles:

Admin
Identities manager
A custom role with the View identities checks and data or Process identities checks and manage configurations permission

Sign in to the Dashboard.
Go to Identities > Identity verification.
Search or filter for the verification you want to view, and select it.

On the Verification details page, you can view the following information:

Page section	Data
Verification details Always visible	The verification ID The identity verification status Created – The date and time when the verification was created. Last updated – The date and time when the verification was last updated. Configuration ID
Response codes Visible if the result is available	One or more response codes if the status is one of the following: `approved` `declined` `inconclusive` `pending` `refused` `retry_required`
Risk Visible if the result is available	One or more risk labels
Captures Visible if the result is available	Document captures – Any images captured of the applicant's ID document Face captures – Any images captured from the applicant's face video
Applicant Always visible	External applicant name – The name you have on record for the applicant. Applicant email – The applicant's email address. Created – The date and time the applicant's profile was created. Last updated – The date and time the profile was last updated. External applicant ID – Your identifier for the applicant. Applicant ID – The Checkout.com identifier for the applicant. To view the applicant's full details, select View applicant profile.
Verification > Results tab Populated if the result is available	Under Identity: First name – The applicant's verified first name. Last name – The applicant's verified last name. Last name at birth – The applicant's last name when they were born. Birth date – The applicant's date of birth. Birth place – The city where the applicant was born. Nationality – The applicant's nationality or nationalities. Gender – The applicant's sex. This can be `F` for female, or `M` for male. Personal number – The applicant's personal identification number. Tax identification number – The applicant's tax identification number. Under Document: Document type Issuing country Document number Expiry date Issue date Place of issue Machine-readable zone (MRZ)
Verification > Timeline tab Always visible	This can include the following: Applicant profile created Verification created All webhook events All attempts Final identity verification status

A detailed report for the identity verification is provided in PDF format. When the report is ready, you receive an Identity verification report created webhook.

To download the identity verification report, you need one of the following user roles:

Admin
Identities manager
A custom role with the View identities checks and data or Process identities checks and manage configurations permission

Sign in to the Dashboard.
Go to Identities > Identity verification.
Search or filter to find the verification you want to download the report for, and select it.
On the Verification details page, select Download report.
The report is downloaded as a PDF file.

Information

Download a sample report.

If using Safari, hold down the Option key when selecting the link to download the file.

If the identity verification is later audited and the status updated, you receive an Identity verification audit completed webhook.

If requested by an applicant under the General Data Protection Regulation (GDPR), you can remove the following personally identifiable information (PII) from the identity verification:

External applicant name – The name you have on record for the applicant.
Applicant email – The applicant's email address.
All information on the Verification > Results tab

Note

Removing an applicant's PII is permanent. You cannot undo this action. Any information from the applicant's checks that is not linked to their personal identity is retained for your records.

You need one of the following user roles:

Admin
Identities manager
A custom role with the Process identities checks and manage configurations permission

Sign in to the Dashboard.
Go to Identities > Identity verification.
Search or filter for the verification you want to remove the PII for, and select it.
On the Verification details page, select Remove personal details.
Select _Remove personal details_to confirm the action.

On the Verification details page, you can see the date and time when the PII was removed.

You receive an Identity verification anonymized webhook.

Verify identities using the Dashboard
Beta

Information

Before you begin

Configuration

How it works

Create a verification

Create an attempt

Redirect the applicant

Note

Information

View attempts

View the verification

Download the report

Information

Audits

Remove personal details

Note