Skip to main content
Finrock’s AML screening integration lets you automatically flag or freeze transactions and addresses that exceed your configured risk threshold. This endpoint allows you to enable AML screening for your sub-account, select your preferred provider, supply your provider API key, and specify the exact risk levels and transaction directions to screen. Once configured, every deposit and/or withdrawal is checked in real time against the provider’s database of known illicit and high-risk addresses.

AML Providers and Risk Levels

Request

Method: POST URL: https://api.finrock.io/dac/v1/aml
string
default:"Chainalysis"
required
The AML provider to use for screening. Must be one of Chainalysis, Cipertrace, or AMLBot.
string
required
The API key issued by your chosen AML provider. Finrock uses this token to authenticate requests to the provider on your behalf.
string
default:"SEVERE, HIGH"
required
A comma-separated list of risk levels that trigger a freeze or block. For example: SEVERE, HIGH or SEVERE, HIGH, MEDIUM. Transactions from addresses flagged at any listed risk level will be held.
boolean
default:"true"
required
Set to true to enable AML screening on incoming deposits. When enabled, Finrock checks the sender address against the provider’s dataset before crediting the deposit.
boolean
default:"true"
required
Set to true to enable AML screening on outgoing withdrawals. When enabled, Finrock checks the destination address before releasing the withdrawal.

Example Request

Response

A 200 response confirms that the AML settings have been saved and are now active. A 400 response indicates missing required fields or an invalid provider value.
object
Confirms the AML configuration was updated successfully.
object
Returned when required fields are missing, the provider value is invalid, or the aml_token fails validation.
Once AML screening is active, deposits or withdrawals from addresses flagged at your selected risk levels will be automatically frozen. Ensure your aml_risk_levels threshold aligns with your compliance policy before enabling in production.