TRM Labs screens transactions for blockchain risk. Your AML/KYT Trigger (Screening Policy) decides which transactions are sent to TRM Labs, and your Outcome (Post-Screening Policy) decides what happens based on the result. See Building a Compliance Policy for how Trigger and Outcome work in general, and About AML/KYT for how AML/KYT fits into screening.
This integration is in Early Access. Contact your Customer Success Manager to join. It is also a premium feature that requires an additional purchase, separate from Early Access enrollment. Fireblocks Support enables it on your workspace, and you connect it in the Console. TRM Labs is available on Mainnet only.
How it works
Fireblocks sends TRM Labs the chain, the asset, the amount and its USD value, the destination address, the transaction hash, a Fireblocks transaction reference, and the Customer Reference ID. TRM Labs returns a categorical risk level (Unknown, Low, Medium, High, Severe), along with the specific risk categories matched, if any.
Screening differs by direction: incoming transactions are evaluated through TRM Labs' transaction monitoring, and outgoing transactions through TRM Labs' wallet screening. Outgoing transactions are not registered with TRM Labs' transaction monitoring in this Early Access release.
Because TRM Labs' screening is asynchronous, a result is not always immediate. The Outcome (Post-Screening Policy) includes a Wait action, specific to TRM Labs, that holds a transaction until a new result arrives or a time window you define elapses. TRM Labs supports the Outcome actions Accept, Reject, Alert, and Wait.
You can view screened transactions on the Transaction History page, the Audit Log, or via the API. Transaction rejection information is available only from Fireblocks, not from TRM Labs directly. TRM Labs can also send you alerts for indirect risk exposure through its own UI.
TRM Labs returns results asynchronously. The bypass-on-failure setting does not apply to TRM Labs. If TRM Labs does not answer, the Outcome rules for the Failed status decide. Without such a rule, Fireblocks waits up to one hour, then rejects an outgoing transaction and alerts on an incoming one.
Setup
Before you begin, Fireblocks Support must enable AML/KYT on your workspace.
- Create an API key in TRM Labs. TRM Labs documents API access in the TRM Labs documentation. You need Know Your Transaction (KYT) API access in TRM Labs to create the key. If you are later removed from the TRM Labs account, create a new key.
- Connect it in the Fireblocks Console:
- Go to Policies > Compliance > AML > Policy > Connect.
- Select TRM Labs.
- Enter your API key.
Default Trigger (Screening Policy) and Outcome (Post-Screening Policy) rules apply until you create your own. The default rules are greyed out in the Console and cannot be edited or removed; any custom rules you add above them take precedence, and rules are evaluated top to bottom.
You can read the policies and a transaction's result through the API; connecting the provider is Console-only. See TRM Labs on the Developer Portal.
To switch to a new API key later, submit a ticket to Fireblocks Support with the new key.
Timing parameters
Because results can arrive asynchronously, the TRM Labs Outcome (Post-Screening Policy) includes two timing fields alongside the usual ones: Valid After (the minimum time that must pass before a rule applies) and Valid Before (the maximum time within which it applies). These work together with the Wait action to hold a transaction only as long as it makes sense for your policy.
Timeouts
TRM Labs uses longer timeout windows than other providers, measured in hours, because it monitors the transaction and polls for alerts instead of resolving it immediately. If no result arrives before the window closes, Fireblocks applies a default verdict unless your policy says otherwise: reject for outgoing transactions, and accept for incoming transactions, since the funds have already arrived. The bypass-on-failure setting in your compliance policy does not apply to TRM Labs.
Testing transaction rejection
You can test that rejection rules work before relying on them in production:
- Incoming: add a rule that accepts transactions above a small threshold (for example, $0.0568) and a final rule that rejects everything else, then send test transactions above and below that threshold.
- Outgoing: add a rule that rejects transactions TRM Labs identifies as high-risk, then mark one of your own destination addresses as high-risk in TRM Labs to trigger it.
Transactions that receive an "Unknown" result are not affected by these test rules, and both only apply within your configured blocking-timeout window.
Supported assets
Download the attached spreadsheet of supported assets.
TRM Labs supports a broad range of blockchains, including Bitcoin, Ethereum, Solana, and TRON. Testnet assets are not currently supported.
Limitations
- Only one AML/KYT provider can be connected to a workspace at a time. To switch or disconnect a provider, contact Fireblocks Support.
- Outgoing transactions are not registered with TRM Labs' transaction monitoring during Early Access.
- Testnet assets are not supported.