The Travel Rule requires regulated crypto businesses to share sender and recipient identity information when transferring funds above a threshold ($3,000 in the US, 1,000 EUR in the EU). When you send crypto from one exchange to another, the sending exchange must transmit your name, account number, and address to the receiving exchange. It is the crypto equivalent of how banks share wire transfer sender info.
What Is the Travel Rule (Crypto)?
4 min read
The short version
When you wire money from one bank to another, your name travels with the transfer so the receiving bank knows who sent it. The Travel Rule applies this same concept to crypto: if you send $5,000 from Coinbase to Kraken, Coinbase must tell Kraken who you are. This does not affect self-custody transfers (exchange to your own wallet), but does affect exchange-to-exchange movements above the threshold.
How It Works
Origin: FATF (Financial Action Task Force) Recommendation 16 requires Virtual Asset Service Providers (VASPs, meaning exchanges and custodians) to share originator and beneficiary information for transfers above the threshold. What must be shared: originator name, originator account/address, beneficiary name, beneficiary account/address. In some jurisdictions: date of birth and geographic address of the originator. Thresholds: US (FinCEN): $3,000. EU (Transfer of Funds Regulation under MiCA): 1,000 EUR (with identity verification required at 0 EUR for all transfers starting 2025). Singapore: 1,500 SGD. Japan: all amounts. Implementation challenges: unlike banks (which use SWIFT messaging), crypto has no universal inter-exchange messaging standard. Solutions in development: TRUST (Travel Rule Universal Solution Technology, used by Coinbase, Gemini, Kraken), Notabene (commercial Travel Rule compliance platform), Shyft/Veriscope, and OpenVASP (open standard). What this means for users: (1) Exchange-to-exchange transfers above threshold require identity info sharing (already happening on major exchanges). (2) Exchange-to-self-custody wallet transfers: the exchange knows you are the originator but cannot share info about the recipient (your own wallet has no VASP). Some exchanges require you to declare this is my own wallet when withdrawing. (3) Self-custody-to-self-custody: completely unaffected (no VASP involved on either side, no reporting obligation).
Sending $5,000 USDC from Coinbase to Kraken
You initiate a withdrawal of 5,000 USDC from Coinbase to your Kraken deposit address. Behind the scenes: Coinbase identifies the destination address as belonging to Kraken (via blockchain analytics and VASP registry). Since the amount exceeds $3,000, Travel Rule applies. Coinbase transmits to Kraken via TRUST protocol: your name, Coinbase account ID, and your verified address. Kraken receives this information alongside the 5,000 USDC deposit. Kraken matches it against your Kraken KYC profile. If the names match: deposit proceeds normally. If there is a mismatch: Kraken may flag the deposit for manual compliance review (delaying access to funds by hours or days). User experience: for most users this is invisible (the info sharing happens between exchanges without your action). Occasional friction: if you use different names/emails on different exchanges, the mismatch can delay deposits.
What People Get Wrong
The Travel Rule means crypto is no longer private
The Travel Rule only applies to transfers between regulated VASPs (exchanges). Self-custody wallets, DeFi protocols, and P2P transfers are not subject to it because there is no VASP on the receiving end to share info with. Privacy is reduced for exchange-to-exchange flows but unaffected for on-chain self-custody activity.
You cannot avoid the Travel Rule
For exchange-to-exchange transfers above threshold: no, you cannot avoid it (both sides are regulated). For moving crypto to self-custody: the Travel Rule does not apply to withdrawals to your own wallet (no receiving VASP). The practical implication: using self-custody reduces your exposure to Travel Rule data sharing, which is one more reason to withdraw to your own wallet rather than hopping between exchanges.
All countries enforce the same rules
Implementation varies dramatically. Japan enforces on all amounts. The US at $3,000. The EU at 1,000 EUR (full enforcement phasing in 2025-2027 under MiCA). Some countries have not implemented it yet. Cross-border transfers between jurisdictions with different rules create compliance grey areas that exchanges navigate differently.
Keep Reading
Sources & Further Reading
- FATF Virtual Assets Guidance
The international standard-setter whose Recommendation 16 defines the Travel Rule
- Notabene
Commercial Travel Rule compliance platform used by exchanges globally
Questions People Also Ask
- Does the Travel Rule affect withdrawals to my own wallet?
- No. When you withdraw to a wallet you control (self-custody), there is no receiving VASP to share information with. The exchange records that you withdrew to an external address (their own compliance records), but no inter-VASP data transmission occurs. This is why many users prefer self-custody: fewer data-sharing touchpoints.
- What happens if I send below the threshold?
- Transfers below the threshold ($3,000 US, 1,000 EUR EU) do not trigger Travel Rule information sharing between VASPs. However: exchanges still track all transactions internally for AML purposes (Suspicious Activity Reports can be filed at any amount). The Travel Rule specifically governs inter-VASP data transmission, not internal monitoring.
- When will the Travel Rule be fully enforced everywhere?
- Ongoing. US: largely enforced since 2023 among major exchanges. EU: full enforcement under MiCA Transfer of Funds Regulation expected by end of 2025. Asia (Japan, Singapore, South Korea): already enforcing. The global trend is toward universal enforcement within 2-3 years, with remaining holdouts being smaller jurisdictions.