AML Screening & Monitoring Integration

API-only guide

This guide provides step-by-step instructions on how to integrate AML Screening & Monitoring via our API.

Before you begin, make sure you have completed the required setup.

Flow

Click to magnify.

---

To integrate AML Screening & Monitoring via our API, follow these steps:

1. Authenticate

Create an access token to authenticate in our API:

• You provide your Fourthline API credentials.
• You receive an access_token.

Important

For security, access tokens are valid for 1 hour only.

If your token expires, create a new access token by making another Create access token request.

---

2. Create client profile

Create a profile for the client:

• You provide your unique identifier for the client, their identity data, and specify screening or monitoring.
• You receive a Fourthline client id.

Important

AML Monitoring starts automatically.

Monitor its progress using the monitoring statuses returned in the webhook notifications.

---

3. Start screening

AML Screening only

Trigger the screening for one or multiple clients:

• You provide the clientId (same value as the id returned in the Create AML client profile response) for the client(s) you want to screen.
• You receive the status of each client's screening.

Status: Check the screening status in the webhook notifications.

Client is already onboarded

If the client is already onboarded by Fourthline, to perform a single-time screening, follow these steps:

1. Make a POST Create AML client profile request using the same ProviderClientId as in the Identity Verification workflow.

2. Set MonitoringType=1 to create an AML-specific client record linked to the existing clientId.

3. Call Start one-time screening to initiate the screening.

---

4. Get hit information

If we find any hits, you can get information about them as required via the following API requests:

Possible hit outcomes include:

• validating: There is a potential hit that hasn't (yet) been investigated.
• confirmed_hit: Our investigation confirmed the hit is definitely for this client.
• false_positive: Our investigation found that a potential hit wasn't for this client.

If we find a confirmed hit, get the investigation identifier needed to download the Confirmed Hit Report:

• You provide the clientId (same value as the id returned in the Create AML client profile response).
• You receive information about the investigation and the identifier (verificationId).

Note

Multiple investigations can be associated with a single AML clientId.

---

5. Download the report

If there are any confirmed hits, download the
Confirmed Hit Report:

• You provide the investigation identifier (verificationId).
• A successful response is empty and the report is downloaded.

Note

You can also download a CDD report using the Get CDD PDF request by passing the investigation identifier (verificationId).