Screen AML databases using the API
Beta
Last updated: January 21, 2026
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.
- You must have already integrated Identity Verification and verified the applicant.
- Handle statuses.
- Subscribe to AML Screening webhooks.
Your account manager provides you API credentials and access to our partner ComplyAdvantage's dashboard, where you can manage and investigate cases.
Enter your ComplyAdvantage API credentials in the IDV Dashboard.
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.
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:
- Retrieve the applicant ID.
- Create a screening.
If you want to receive alerts for future database matches for the applicant, enable monitoring. - Checkout.com returns an applicant risk score. If the risk is acceptable, we screen the databases and approve or decline the applicant.
- If alerts are raised that require your review, we create a case for you to investigate.
- Investigate the case in the ComplyAdvantage Dashboard, and approve or decline the applicant.
- View the screening to see the result.
Call the Create an AML screening endpoint:
applicant_idfield – Provide the applicant ID.search_parameters.configuration_identifierfield – Provide your AML Screening configuration ID.monitoredboolean – To enable monitoring, set totrue.
post
https://identity-verification.checkout.com/aml-verifications
The response returns the screening ID in the id field, prefixed with amlv_. You need this to view the screening result.
The screening status changes to created and you receive an AML verification created webhook.
Checkout.com generates a risk score for the applicant as follows:
| Risk score | Description |
|---|---|
| The risk is acceptable and we start the screening. The screening status changes to You receive an AML verification onboarding started webhook. |
| 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 |
|---|---|
| There were no databases matches and we approved the applicant. You receive an AML verification onboarding completed webhook. |
| There were exact or fuzzy matches for the applicant. We created a case for you to investigate. You receive an AML verification monitoring alert webhook. |
| There were database matches and we declined the applicant. You receive an AML verification onboarding completed webhook. |
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 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 webhook.
To view the final result, call the Get an AML screening endpoint, and provide the screening ID from the Create a screening response as the {aml_verification_id} path parameter.
get
https://identity-verification.checkout.com/aml-verifications/{aml_verification_id}