What Is the Crypto Travel Rule? A 2026 Guide for VASPs

The name is older than crypto. The travel rule has applied to traditional wire transfers for decades: the required information has to travel with the payment. In 2019 the Financial Action Task Force extended the same principle to virtual assets, and regulators around the world have been writing it into their crypto rules ever since.

What is the crypto travel rule?

The crypto travel rule is a requirement that a VASP sending a crypto transfer on a customer's behalf must share that customer's information, and collect the recipient's, with the VASP on the other side. A VASP is a virtual asset service provider: exchanges, custodians, and similar regulated businesses. It does not apply to two individuals moving coins between their own self-hosted wallets, but the moment a regulated business is on one or both ends of a transfer above the threshold, the rule attaches. The point is to remove the information gap that would otherwise let value move between institutions with no record of the parties.

What is the travel rule threshold?

Thresholds vary by jurisdiction. In the United States, the Bank Secrecy Act sets a $3,000 threshold for wire transfers, and FinCEN clarified in 2019 that it covers convertible virtual currency transfers as well. FATF's international recommendation uses a $1,000 or 1,000 EUR figure, and individual countries set their own: Canada uses CAD 1,000, Singapore SGD 1,500, and the European Union applies a zero threshold for transfers between crypto asset service providers. FinCEN has also proposed lowering the US threshold to $250 for certain international transfers, though that remains a proposal rather than a rule as of 2026.

Exact required fields vary by jurisdiction. Confirm current obligations with counsel or your regulator.

Who does the travel rule apply to?

It applies to VASPs, not to ordinary users moving their own coins. Exchanges, brokers, custodians, and payment firms that hold or transmit crypto for customers are in scope; a person sending bitcoin from one personal wallet to another is not, on their own. The wrinkle is transfers to and from self-hosted wallets: when a customer at a regulated exchange withdraws to a private wallet, many jurisdictions still expect the VASP to collect information about that counterparty, which is where on-chain analysis becomes part of compliance.

How does on-chain data support travel rule compliance?

The travel rule is about the parties, but the transfer itself is on-chain and public, and that is where a compliance team gets independent context. Before releasing a withdrawal, a team can screen the destination address for sanctions matches and exposure to labeled high-risk entities, using an address screening API, and monitor ongoing flows with transaction monitoring. That does not replace collecting originator and beneficiary data, but it adds a risk signal about where funds are actually going. Full multi-chain investigations suites like the tools covered on our TRM Labs alternative page sit at the heavy end of this; a Bitcoin-native data layer covers the on-chain screening piece over an API you drive.

What are the penalties for non-compliance?

Failing to meet the travel rule is treated as an anti-money-laundering failure, and enforcement runs through each jurisdiction's financial regulator. In the US that means the Bank Secrecy Act regime, where inadequate controls can bring civil penalties, consent orders, and reputational damage, and repeated or willful failures carry heavier consequences. Because the specifics change and depend on your license and location, keeping an auditable record of your controls and decisions matters, and a dedicated compliance controls platform helps track obligations across a regulated business. This article is informational only and is not legal advice; confirm your obligations with qualified counsel.