Skip to main content
Chainalysis is an AML/KYT provider. It is a premium add-on that Fireblocks Support enables on Testnet and Mainnet workspaces, and you connect it in the Console; there is no API for connecting. Through the API you read its policy and results the same way as for any AML/KYT provider; see AML/KYT Overview.

​
What is sent and returned

Fireblocks sends asset and network, amount and USD value, destination address, transaction hash and source address (for incoming and sent transfers), destination tag, and the Customer Reference ID. Chainalysis returns a categorical risk level and the risk category it matched, if any. In GET /screening/transaction/{txId}, the risk level is in the risk field as a provider-specific string, such as severeRisk, highRisk, mediumRisk, lowRisk, or noRiskInfo. Older transactions can carry legacy values such as HIGH or MEDIUM, so do not validate against a fixed list. externalId is the identifier Chainalysis assigned when Fireblocks registered the item. For an incoming transaction it identifies a transfer (GET /v2/transfers/{externalId}); for an outgoing transaction a withdrawal attempt (GET /v2/withdrawal-attempts/{externalId}), not a transfer. Use the same Chainalysis API key as your Fireblocks provider configuration. Outcome (Post-Screening Policy) actions: Accept, Reject, Alert.

​
Connect

You need a Chainalysis API key with Know Your Transaction (KYT) API access. Enter it in the Console; default Trigger (Screening Policy) and Outcome rules apply until you create your own. To switch to new credentials, submit a ticket to Fireblocks Support.

​
Timeouts

If no result arrives in time, bypassScreeningDuringServiceOutages decides what happens; see Outage and delay settings.

​
Supported assets

Chainalysis supports blockchains and tokens broadly, including Testnet assets. Newly deployed tokens are usually supported automatically.

​
Limitations

  • 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 risk-based Outcome rules cannot apply.
  • SOL transactions with an amount of 0.0 bypass screening with an Unsupported Route status.
  • Rejection details are available only from Fireblocks, not from Chainalysis.

​
On the Help Center

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