AML Compliance Solutions Integration Guide

AML Compliance Solutions Integration Guide

AML Compliance Solutions is a cloud-native Anti-Money Laundering (AML) solution that helps your organization comply with legal and regulatory requirements aimed at preventing, detecting, and reporting money laundering activities.

AML Compliance uses our Match Engine to screen and monitor individuals and businesses against sanctions lists, such as the US Office of Foreign Assets Control (OFAC), Politically Exposed Person (PEP), and Adverse Media.

The Match Engine ingests data from these sources. The data is validated and deduplicated for accuracy and then screened against global watchlists. Matches are either returned as alerts or put through an optional analyst review to reduce false positives. Additionally, our optional monitoring service can continuously monitor alerts in case a database is updated with new information.

For the API specifications, go to AML Compliance Solutions Screening API.

Generate an API Key

In Kount 360, after you have activated your organization, you can generate API keys to send data securely to Equifax. Only users with the Owner role permissions can generate, delete, or edit API keys.

Caution

You must have an initialized client before you can create an API key.

  1. Sign in to Kount 360.

    There are two integration environments: sandbox and production. Only integrate into our sandbox environment if you are integrating a pre-production environment without production data for testing.

  2. Select Admin, and then Product Configuration.

  3. In System Settings, select API Keys.

    All initialized clients display.

  4. For the client you want to create an API key, select Generate API Key.

    The new API key is generated. A prompt displays with the ability to copy the API key and add a description.

  5. Copy the API key, and then store it in a secure location.

    Note

    The API key is not provided again. You must store it in a secure location for future reference. If the API key is compromised or lost, create a new API key and delete the compromised one.

  6. Enter a description detailing the store used for the API key, and then select Confirm.

API keys are organized under each client on the API Keys page. Expand the client to view your API keys, the descriptions, and when client details were created.

Create a Bearer Token

After you have provisioned your API credentials in the portal, retrieve a temporary bearer token to authenticate calls to the Kount 360 API. Provide the API key in an HTTP POST to a specific login.equifax.com URL.

With a successful exchange, the returned JSON provides a special bearer token, which is the access_token property. The exchange also provides an expiration date, the expires_in property, provided in seconds until expiration. The API to retrieve the bearer token depends on if you are calling the sandbox or production environment.

The values are:

Sandbox

Auth Server URL:

https://login-uat.equifax.com/as/token

API Service Host:

https://api-sandbox.kount.com

Production

Auth Server URL:

https://login.equifax.com/as/token

API Service Host:

https://api.kount.com

After obtaining the bearer token, use it to authenticate requests to the Kount 360 API. Include the token in the Authorization header of your HTTP API request, prefixed with Bearer {bearer token}.

To prevent authentication issues, refresh the token before it expires. Tokens issued by login.equifax.com expire after 20 minutes, but client credentials remain valid unless revoked. Minimize calls to the /token endpoint by implementing token expiration handling in your customer applications. Always check if a token has expired before requesting a new one, as excessive calls to the /token endpoint could result in rate limiting.

Bearer Token Retrieval Examples

We provide several examples in popular programming languages to retrieve and use the bearer token.

Python

Bash

TypeScript

Go

Confirm your integration

To confirm that your integration was successful, send a screening request and verify that you receive a response.

Send a screening request

Submit your request with as many fields as possible for the most accurate match results. The following example uses only the minimum required fields. For the complete list of possible fields, go to the AML Compliance Solutions Screening API.

  1. Submit the First and Last name for a person screening.

    You can enter more fields, but these are the minimum fields required for a response.

    Note

    Use a first and last name from a data source you subscribe to, such as OFAC, to ensure a successful response.

  2. A response is returned with one of the following matchSummary.review values:

    • no_match_found: The system attempted to find a match in the available data sources, but none was found.

    • machine_soft_hit: At least one match found.

    A successful response with a soft hit provides data similar to the example in this document.

Was this article helpful?
0 out of 0 found this helpful