Skip to main content
Travel Rule overview flow The Travel Rule requires Virtual Asset Service Providers (VASPs) to exchange originator and beneficiary information for qualifying transactions (FATF Recommendation 16). Each jurisdiction decides which transactions are in scope and which data is required. Fireblocks does not decide your Travel Rule obligations: you remain responsible for what you screen, the data you send, and any reporting your jurisdiction requires. Fireblocks handles the Travel Rule in two ways:
  • Through a Travel Rule provider, for most counterparties: Notabene, Sumsub, or GTR screens your transactions and exchanges the data with the counterparty VASP. TRUST, a separate network, lets you prove that you own your addresses.
  • Directly, for connected accounts: for exchanges and on/off-ramps, Fireblocks passes the required data to the venue, which applies its own requirements. These transactions do not go through a provider or your Travel Rule policy.
The Travel Rule is available in the Developer Sandbox, Testnet, and Mainnet workspaces.

​
How screening works with a provider

Travel Rule is the last check in the screening flow, after Address Registry Screening and AML/KYT. If AML/KYT freezes an incoming transaction, Travel Rule screening does not run.
  1. The Trigger (Screening Policy) decides whether the transaction needs Travel Rule screening.
  2. Your provider exchanges the required data with the counterparty VASP.
  3. For Sumsub and GTR, the Missing Travel Rule Message Policy decides what happens while a required message does not exist yet.
  4. The Outcome (Post-Screening Policy) acts on the message status: completed, pending, rejected, or failed to complete in time.
The available actions, and the fields rules can match on, differ by provider. TRUST has no screening policy: it covers proof of address only. See Compliance Policies for how policies work.

​
Providers

You can connect one Travel Rule screening provider (Notabene, Sumsub, or GTR) per workspace, with one exception: Sumsub and GTR can be active in the same workspace. TRUST is separate and works alongside any of them. With Notabene, Sumsub, and GTR, you encrypt the PII on your side, so Fireblocks never holds the keys to decrypt it. Each provider guide covers its encryption method and its endpoints.

​
Connected accounts

  • Exchanges: sending encrypted PII with exchange deposits and withdrawals.
  • Exchange Travel Rule Requirements: the piiData fields each exchange requires, by direction, relationship, and jurisdiction.
  • On/Off-Ramps: providing originator and beneficiary information on Trading API on/off-ramp orders.

​
On the Help Center

To connect Notabene or build Travel Rule rules in the Console, see About Travel Rule.