# Screen AML databases using the Dashboard The AML Screening solution enables you to check if a verified applicant appears in any of the following anti-money laundering (AML) databases: - Politically exposed persons (PEPs) with a prominent public function, and their close family and associates - Sanctions - Adverse media that may lead to reputational damage > **Information** > > To enable AML Screening, 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 - You must have already integrated [Identity Verification](https://www.checkout.com/docs/business-operations/manage-identities/verify-identities.md) and verified the applicant. - The applicant must already have a [profile](https://www.checkout.com/docs/business-operations/manage-identities/manage-applicants.md#Create_an_applicant) and an applicant ID, prefixed with `aplt_`. - [Handle statuses](https://www.checkout.com/docs/developer-resources/codes/identities-codes.md#Check_statuses). - [Subscribe to AML Screening webhooks](https://www.checkout.com/docs/developer-resources/event-notifications/event-types.md#AML_Screening). ### Configuration Your account manager provides you API credentials and access to our partner [ComplyAdvantage](https://complyadvantage.com/mesh/)'s dashboard, where you can manage and investigate cases. Enter your ComplyAdvantage API credentials in the [IDV Dashboard](https://dashboard.ubble.ai/). In the ComplyAdvantage Dashboard, you can configure the following to meet your business requirements: - The risk score model for all your screenings - The checks Checkout.com performs for a specific screening – for example, which databases to screen and how to handle fuzzy matches You receive a unique configuration ID that you must provide every time you create a screening. For example, `8eb79430-c014-41e5-be73-2c2c091322b8`. This is different to your Identity Verification and Face Authentication configuration IDs. ### Monitoring If you want to receive alerts for future database matches for the applicant after the initial screening, Checkout.com continues to monitor the applicant's AML status. We inform you if any alerts for database matches are raised. Subscribe to the following webhooks: - [AML verification monitoring alert](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_monitoring_alert.md) - [AML verification monitoring reviewed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_monitoring_reviewed.md) --- ## How it works 1. [Retrieve the applicant ID](https://www.checkout.com/docs/business-operations/manage-identities/manage-applicants/using-the-dashboard.md#View_an_applicant_ID). 2. Create a screening.
If you want to receive alerts for future database matches for the applicant, enable monitoring. 3. Checkout.com returns an applicant risk score. If the risk is acceptable, we screen the databases and approve or decline the applicant. 4. If alerts are raised that require your review, we create a case for you to investigate. 5. Investigate the case in the ComplyAdvantage Dashboard, and approve or decline the applicant. 6. View the screening to see the result. --- ## Create a screening To create an AML screening, 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 1. Sign in to the [Dashboard](https://dashboard.checkout.com/). 2. In the Business entity selector, select the relevant entity. 3. Go to _Identities_ > _AML screening_. 4. Select _Create screening_. 5. In the _Create screening_ window, enter the applicant ID. 6. Select the configuration you want to apply to the screening from the drop-down. 7. Optionally, select _Monitor applicant_. 8. Select _Create screening_. 9. Copy the screening ID to use to view the result, and then select _Done_. If the screening is created successfully: - You receive a screening ID, prefixed with `amlv_`, which you need to view the screening result. - The screening status changes to `created`. - You receive an [AML verification created](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_created.md) webhook. ### Risk scores Checkout.com generates a risk score for the applicant as follows: | Risk score | Description | | --- | --- | | `LOW`

`MEDIUM`

`HIGH` | The risk is acceptable and we start the screening.

The screening status changes to `screening_in_progress`.

You receive an [AML verification onboarding started](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_onboarding_started.md) webhook. | | `PROHIBITED` | The risk was unacceptable and we automatically declined the applicant.

You cannot create a new screening. | The result can be the following statuses: | Screening status | Description | | --- | --- | | `approved` | There were no databases matches and we approved the applicant.

You receive an [AML verification onboarding completed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_onboarding_completed.md) webhook. | | `review_required` | There were exact or fuzzy matches for the applicant.

We created a case for you to investigate.

You receive an [AML verification monitoring alert](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_monitoring_alert.md) webhook. | | `declined` | There were database matches and we declined the applicant.

You receive an [AML verification onboarding completed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_onboarding_completed.md) webhook. | --- ## Investigate the case If there are alerts for database matches, Checkout.com creates a case. You review the case in the ComplyAdvantage Dashboard and decide whether to approve or decline the applicant. You can: - Change the status of a database match. - Use an allowlist to reduce unnecessary alerts. - Change the result. When you change the result from `review_required` to `approved` or `declined`, you receive an [AML verification onboarding reviewed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_onboarding_reviewed.md) webhook. If you re-open a case, the result changes from `approved` or `declined` to `review_required` and you receive an [AML verification status changed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/aml_verification_status_changed.md) webhook. --- ## View the screening To view an AML screening, 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_ > _AML screening_. 3. Search or filter for the screening you want to view, and select it. On the _Screening details_ page, you can view the following information: | Page section | Data | | --- | --- | | _Screening details_ | - Screening ID
- Screening status
- Created – The date and time when the screening was created.
- Last updated – The date and time when the screening was last updated.
- Monitored – Indicates whether you enabled monitoring for the applicant.
- Configuration ID | | _Applicant_ | - 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_. | | _Screening timeline_ | This can include the following:

- Applicant profile created
- Screening created
- All webhook events |