The crypto Travel Rule means a VASP has to hand over sender and receiver details with every transfer it processes — name, account number, sometimes more. For banks that still bank crypto businesses, this stopped being paperwork years ago; it's now the price of keeping the account open. Skip it once, and a partner bank can close your account with zero warning. Here's what you actually have to collect, where the thresholds stand in 2026, and how to stay off the blacklist.
Why banks suddenly got nervous about this one rule
Short version: the Travel Rule makes you attach sender and receiver information to every crypto transfer — the same logic as a SWIFT wire, just bolted onto blockchain rails. Think of a registered letter: the post office won't take the parcel without a return address on the envelope. Crypto transfers work the same way now, except the "return address" is a name, account details, and sometimes a wallet ID.
The rule itself comes from the FATF, the intergovernmental body that writes global anti-money-laundering standards. In 2019 it extended Recommendation 16 to VASPs — exchanges, exchangers, wallet providers. Every country has rolled it out at its own pace since then, but banks that still serve crypto businesses aren't waiting for local law to catch up. If an exchanger can't prove where a transfer came from, the account gets closed — not because a specific statute demands it, but because the bank's compliance desk doesn't want to explain the gap to its own regulator.
What dollar amount actually triggers it
The threshold varies by country, and that's exactly where exchangers get caught out. For years the reference point was $1,000 or €1,000 — FATF's original recommendation, adopted with local tweaks.
The European Union
Since late 2024, the EU's recast Transfer of Funds Regulation (TFR) dropped the threshold for crypto transfers entirely. If either side of a transaction is a registered crypto-asset service provider, sender and receiver data has to travel with the transfer regardless of size.
The US and the rest of the FATF world
In the US and most other FATF members, a $1,000–3,000 threshold still holds, depending on jurisdiction — but the direction is unmistakable: thresholds are shrinking or disappearing. Betting your exchanger's compliance strategy on "nobody checks small transfers" isn't a strategy anymore in 2026. It's a liability.
What data you actually have to send and receive
The data set barely changes from provider to provider:
- full legal name of sender and receiver;
- the account number or wallet identifier the transfer moved through;
- for larger amounts, the sender's address, date of birth, or ID number;
- the name and jurisdiction of the VASP on the other end.
If the counterparty is an unhosted wallet — one that isn't tied to any licensed provider — the requirements loosen but don't disappear. You still have to run a risk assessment on the transfer, and in some jurisdictions collect information about the wallet owner directly.
How it actually works: the messaging networks
You can't just email this data over — it needs a secure channel between the sending and receiving VASP. A handful of competing networks handle that job:
What exchangers actually use
- Notabene — one of the most widely adopted providers, connecting hundreds of VASPs worldwide;
- Sygna Bridge — popular across Asia, built around the Sygnum ecosystem;
- TRP (Travel Rule Protocol) — an open protocol backed jointly by several large exchanges;
- Veriscope, built on Shyft Network — a more decentralized option where verification runs through the chain without publishing personal data on it.
You don't need to join all of them — one or two networks usually cover most of the counterparties you actually deal with in your region.
Where exchangers keep getting this wrong
The most common mistake: assuming that if your home regulator hasn't said anything yet, there's no rush. Your partner bank disagrees — it cares about FATF-wide compliance standards, not the letter of one country's law.
The second mistake is collecting sender data just to check a box, with no fast way to produce it when a bank or a blockchain analytics firm asks. The third is having no process for the transfers where the counterparty isn't on any messaging network at all — those need manual handling and a paper trail, not a free pass.
What you actually lose by ignoring it
A regulatory fine isn't the scary part, and it's rarely the first thing that happens. What hits faster: a partner bank or payment processor freezes the correspondent account with no explanation. For an exchanger, that's an instant stop on settlements — not an abstract penalty six months down the line.
Fair warning: full Travel Rule compliance doesn't guarantee a bank won't close your account for some other reason — crypto compliance policy shifts faster than anyone would like. But it takes this specific reason off the table, and it gives you something to point to if questions come up.
Conclusion
The Travel Rule stopped being a large-exchange-with-a-legal-department problem a while ago — it now decides whether a small exchanger keeps a working bank account at all. The good news is it doesn't demand a business overhaul, just discipline: hook into one or two messaging networks, capture the right fields, and write down a process for the awkward cases. If you're choosing or upgrading the platform behind your exchanger, it's worth checking upfront how easily it exports and stores sender and receiver data — something you can evaluate on iEXExchanger.
