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.

How it works

A transaction with GTR moves through the same three rule stages as any other Travel Rule provider:

1. Screening. Decides whether a transaction needs Travel Rule review at all: Screen (continue to the next stage) or Pass (approve immediately, no review).
2. 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.
3. Outcome. Once GTR returns a result, this stage applies the final action: Accept, Reject, Alert, or continue to Wait if the result is still pending.

See Sumsub for the full mechanics of how these stages work, including multi-destination handling and screening statuses; they work identically for GTR.

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 other providers. Unlike Sumsub, GTR does not support automatic credential exchange: you configure your public key directly in the GTR Dashboard, rather than Fireblocks and GTR exchanging it for you.

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.

To update credentials later, submit a ticket to Fireblocks Support.

Processing

The subsections below describe how processing works.

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.

FAQ

The questions below are the ones readers ask most often.

How is setting up GTR different from Sumsub?

The policy mechanics are the same. The main difference is credentials: GTR requires you to configure your public key directly in the GTR Dashboard, rather than exchanging it automatically the way Sumsub does.

Developer portal

See Global Travel Rule (GTR) in the Travel Rule support integration guide, including GTR encryption.