# Verify identities using the Dashboard
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](https://dashboard.checkout.com/support/new?topic=case_account_management_and_access&issue=issue_account_changes).
---
## Before you start
- Integrate Identity Verification in your [web app](https://www.checkout.com/docs/business-operations/manage-identities/integrate-via-web.md) or [mobile app](https://www.checkout.com/docs/developer-resources/sdks/identities-sdks.md).
- [Handle statuses, attempts, and response codes](https://www.checkout.com/docs/developer-resources/codes/identities-codes.md).
- [Configure your webhook server](https://www.checkout.com/docs/developer-resources/event-notifications/receive-webhooks/configure-your-webhook-server.md) and subscribe to [Identity Verification webhooks](https://www.checkout.com/docs/developer-resources/event-notifications/event-types.md#Identity_Verification).
- [Create an applicant profile](https://www.checkout.com/docs/business-operations/manage-identities/manage-applicants.md).
### Configuration
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
---
## How it works
1. Create an identity verification linked to the applicant's profile.
2. Create an attempt.
3. Redirect the applicant to the attempt URL.
4. View the identity verification to see the result.
5. Download the identity verification report.
6. If requested, you can remove the applicant's personal details from the identity verification.
---
## Create a verification
To create an identity verification and an initial attempt, you need one of the following [user roles](https://www.checkout.com/docs/business-operations/use-the-dashboard/manage-users/user-permissions.md):
- Admin
- Identities manager
- A custom role with the `Process identities checks and manage configurations` permission
**Existing applicant**
If the applicant you want to verify already has a profile, [retrieve their applicant ID](https://www.checkout.com/docs/business-operations/manage-identities/manage-applicants/using-the-dashboard.md#View_an_applicant_ID), and then follow these steps:
1. Sign in to the [Dashboard](https://dashboard.checkout.com/).
2. Go to _Identities_ > _Identity verification_.
3. Select _Create verification_.
4. In the _Create verification_ window, enter the applicant's full name.
5. Enter the applicant ID, prefixed with `aplt_`.
6. Select the configuration you want to apply to the verification from the drop-down.
7. Enter the URL to redirect the applicant to after they complete the verification. For example, your success or failure URL.
8. Select _Create verification_.
The verification ID and the attempt URL are displayed, which you can copy if required.
**New applicant**
If you want to verify a new applicant who does not already have a profile, follow these steps:
1. Sign in to the [Dashboard](https://dashboard.checkout.com/).
2. Go to _Identities_ > _Identity verification_.
3. Select _Create verification_.
4. In the _Create verification_ window, enter the applicant's full name.
5. Select _Create new applicant_.
6. Optionally, enter your reference for the applicant.
7. Optionally, enter the applicant's email address.
8. Select the configuration you want to apply to the verification from the drop-down.
9. Enter the URL to redirect the applicant to after they complete the verification. For example, your success or failure URL.
10. Select _Create verification_.
The applicant ID, 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_created.md) 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_opened.md) webhook.
---
## Create an attempt
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
1. Sign in to the [Dashboard](https://dashboard.checkout.com/).
2. Go to _Identities_ > _Identity verification_.
3. Search or filter for the verification you want to create an attempt for, and select it.
4. On the _Verification details_ page, select _Create attempt_.
5. 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.
6. Select _Confirm_.
The verification ID and URL are displayed, which you can copy if required.
7. 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_opened.md) webhook.
---
## Redirect the applicant
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.
**Successful attempt**
The following table describes the process of a successful attempt:
| Scenario | Description |
| --- | --- |
| Applicant starts the attempt | The identity verification and attempt statuses change to `capture_in_progress`.
You receive an [Identity verification started](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_started.md) webhook.
When successfully completed, the attempt status changes to `completed`.
You receive an [Identity verification capture completed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_capture_completed.md) 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_checks_completed.md) 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_report_created.md) webhook. |
**Unsuccessful attempt**
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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_link_expired.md) 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_capture_refused.md) 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_capture_aborted.md) 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_retry_requested.md) webhook.
When you create a new attempt, the status of the previous attempt changes to `terminated`.
You receive an [Identity verification closed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_closed.md) webhook, followed by an [Identity verification reset](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_reset.md) 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_checks_inconclusive.md) 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.
### View attempts
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
1. Sign in to the [Dashboard](https://dashboard.checkout.com/).
2. Go to _Identities_ > _Identity verification_.
3. Search or filter for the verification you want to view an attempt for, and select it.
4. On the _Verification details_ page, under _Verification_, all attempts appear on the _Timeline_ tab.
---
## View the verification
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
1. Sign in to the [Dashboard](https://dashboard.checkout.com/).
2. Go to _Identities_ > _Identity verification_.
3. 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](https://www.checkout.com/docs/developer-resources/codes/identities-codes.md#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 |
---
## Download the report
A detailed report for the identity verification is provided in PDF format.
When the report is ready, you receive an [Identity verification report created](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_report_created.md) 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
1. Sign in to the [Dashboard](https://dashboard.checkout.com/).
2. Go to _Identities_ > _Identity verification_.
3. Search or filter to find the verification you want to download the report for, and select it.
4. On the _Verification details_ page, select _Download report_.
The report is downloaded as a PDF file.
> **Information**
>
> [Download a sample report](https://www.checkout.com/docs/files/Sample_Identity_verification_report.pdf).
>
> If using Safari, hold down the _Option_ key when selecting the link to download the file.
### Audits
If the identity verification is later audited and the status updated, you receive an [Identity verification audit completed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_audit_completed.md) webhook.
---
## Remove personal details
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
1. Sign in to the [Dashboard](https://dashboard.checkout.com/).
2. Go to _Identities_ > _Identity verification_.
3. Search or filter for the verification you want to remove the PII for, and select it.
4. On the _Verification details_ page, select _Remove personal details_.
5. 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](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/identity_verification_anonymized.md) webhook.