Skip to main content
Chainalysis screens your incoming and outgoing transactions for blockchain risk. Your AML/KYT Trigger (Screening Policy) decides which transactions are sent to Chainalysis, and your Outcome (Post-Screening Policy) decides what happens with the result. See AML/KYT Overview for how AML/KYT fits into screening. Chainalysis is a premium add-on. Fireblocks Support enables it on your workspace, and you connect it in the Console. It is available on Testnet and Mainnet workspaces.

​
How it works

Fireblocks sends Chainalysis the transaction details, including the output address, the transaction hash, and the Customer Reference ID. Chainalysis returns a categorical risk level, and the specific risk category it matched, if any. In the API, the risk level appears in the risk field as a provider-specific string, such as severeRisk, highRisk, mediumRisk, lowRisk, or noRiskInfo. Older transactions may carry legacy values such as HIGH or MEDIUM. Do not validate risk levels against a fixed list. Rejection details are available only from Fireblocks, not from Chainalysis. Chainalysis can also alert you to indirect risk exposure in its own platform.

​
Connect Chainalysis

You need a Chainalysis API key, created with Know Your Transaction (KYT) API access in Chainalysis. Enter it in the Console to connect. Default Trigger (Screening Policy) and Outcome (Post-Screening Policy) rules apply until you create your own. There is no API for connecting a provider. To switch to new credentials later, submit a ticket to Fireblocks Support. See Chainalysis on the Help Center for the Console steps.

​
Timeouts

Fireblocks waits up to 10 minutes for a result on incoming transactions, which Chainalysis resolves by transaction hash after a number of blockchain confirmations, and up to 1 minute on outgoing transactions, which it resolves by address. If no result arrives in time, bypassScreeningDuringServiceOutages decides what happens. See Compliance Policies.

​
Work with results through the API

See Compliance Policies and Transaction Screening Operations for details.

​
Supported assets

  • Chainalysis supports blockchains and tokens broadly. Newly deployed tokens are usually supported automatically.
  • Testnet assets are supported.
  • An ERC-20 token needs a USD price in Fireblocks to be screened. Outgoing transactions in an unpriced token are not registered with Chainalysis, and incoming ones do not trigger risk alerts, so Outcome (Post-Screening Policy) rules based on risk cannot apply.
  • SOL transactions with an amount of 0.0 bypass screening, with an Unsupported Route status.

​
On the Help Center

To connect Chainalysis or test your rules in the Console, see Chainalysis.