Fireblocks connects to a set of tools that verify counterparties, screen transactions for risk, and exchange the information required by the Travel Rule. This article lists what is available. To configure any of them, see the linked article for that tool.

The usual order

Most transactions follow the same rough order, though not every step applies every time:

Identify the counterparty: Address Registry checks whether the receiving or sending address belongs to a known, verified entity.
Screen for risk: An Anti-Money Laundering (AML) and Know Your Transaction (KYT) provider evaluates the address and transaction against blockchain risk data.
Optionally, pause for manual review: Bring Your Own Screening lets you hold the transaction for your own verdict before it continues.
Exchange Travel Rule information, if the transaction requires it: sending the originator and beneficiary details the receiving institution needs.

Which of these run and what happens based on the result depend on how you have configured your compliance policy and on the transaction itself. A transaction to a counterparty in a restricted jurisdiction might run every step; an internal transfer between your own vault accounts might run none.

Address registry screening

Checks a transaction against Fireblocks' registry of known, verified addresses. See About Address Registry Screening.

AML/KYT

Screens addresses and transactions for blockchain risk. You can connect to one or more of the following:

Chainalysis
Elliptic
TRM Labs

See About AML/KYT.

Travel rule

Exchanges the required originator and beneficiary information with counterparties, exchanges, and payment providers. You can connect one or more of:

Notabene
Sumsub
GTR
TRUST

Exchanges and on/off-ramps are handled separately, since Fireblocks owns that integration directly rather than routing it through a Travel Rule provider. See About Travel Rule.

Bring your own screening

Pauses a transaction for your own verdict, based on whatever review process or provider you already use, rather than requiring Fireblocks to natively support it. See About Bring Your Own Screening.

Next: deciding what happens

Connecting a tool does not mean a decision has been made. To turn a connected tool into an automated decision, see Building a Compliance Policy.

Developer portal

For the API, see AML policies, Travel Rule policies, Address Registry, and Bring your own screening check.