GTR (Global Travel Rule) is one of the providers you can connect for Travel Rule messaging. See Building a Compliance Policy for how Trigger and Outcome work in general, and About Travel Rule for how Travel Rule fits into your compliance policy overall.
This is a premium, opt-in feature that requires an additional purchase. Contact your Customer Success Manager for more information. Setup is through the API only, and Fireblocks Support configures the rules on request.
How it works
A transaction with GTR moves through the same three rule stages as Sumsub:
- Trigger (Screening Policy): decides whether a transaction needs Travel Rule review at all: Screen (continue to the next stage) or Pass (approve immediately, no review).
- Missing Travel Rule Message. If a transaction needs review but no Travel Rule message exists for it yet, this stage decides what happens while one is being obtained: Wait, Accept anyway, or Reject.
- Outcome (Post-Screening Policy): once GTR returns a result, this stage applies the final action: Accept, Reject, Alert, or continue to Wait if the result is still pending.
Each stage evaluates its rules top to bottom, with a required catch-all default, the same as any other Trigger or Outcome.
If a transaction has multiple destinations, each one is evaluated independently, and the most restrictive result across all of them applies to the transaction as a whole.
If a Travel Rule message you created for the same transaction already exists, Fireblocks links it when its ID is on the transaction. For incoming transfers, Fireblocks also asks GTR for a matching message by transaction hash, address, amount, and asset. For outgoing transfers, you supply the message ID.
A transaction's screening status is either Completed, Pending, Bypassed (approved without review, per your Trigger rule), or Failed.
Setup
Before you begin, contact your Customer Success Manager to enable this feature, and plan your legal entity structure.
Setup happens through the API rather than the Console, and follows the same legal entity process as Sumsub. Unlike Sumsub, GTR does not send your credentials to Fireblocks automatically: you configure your public key in the GTR Dashboard yourself.
See GTR on the Developer Portal for the API steps.
Rule configuration for all three stages is not self-service. You fill out a policy template and submit it to Fireblocks Support, who apply it on your behalf. Policy changes should go through your organization's compliance approval process before you submit them.
Policy templates and examples are on the Developer Portal’s GTR page, Step 3.
To update credentials later, submit a ticket to Fireblocks Support.
Supported assets
Download the attached spreadsheet of supported assets.
System timeouts
Fireblocks enforces non-configurable limits so a transaction never waits indefinitely: 1.5 hours maximum for outbound transactions, 7 days maximum for incoming ones.
Testing
Start with testnet assets before testing with real value.
Monitoring
The Transaction History page in the Console shows the applied policies and rules, GTR's responses, and the final verdict with an explanation for each transaction.
Limitations
GTR runs alongside Sumsub and TRUST, not Notabene. Disconnecting through the API removes the policy and permanently deletes the stored credentials. Deleting a legal entity deletes its integrations and messages. GTR does not generate a key pair for you; you configure your public key in the GTR Dashboard.
Developer Portal
See GTR for the API steps, message encryption, and the policy templates. See Sumsub in the Travel Rule support integration guide, including Sumsub encryption.