Glossary / Regulation & tax
Travel Rule
Also known as FATF Travel Rule.
- Definition
- The Travel Rule requires the exchange sending your bitcoin to hand your name and account details to the exchange receiving it, the way banks pass details with a wire.
None of this appears on the blockchain: the data travels on a separate messaging channel between the two firms. In the European Union the requirement has applied since December 30, 2024 with no minimum amount, while the United States threshold sits at 3,000 dollars. It is the reason an exchange asks who owns the wallet you are withdrawing to.
How it works
The Travel Rule is a message that accompanies a transfer, not a change to how bitcoin itself moves.
The obligation is old. US recordkeeping rules have required originator and beneficiary details to travel with wire transfers of 3,000 dollars or more since 1996, codified at 31 CFR 1010.410. The global standard-setter extended the same idea to virtual asset businesses in June 2019, and national laws have been catching up ever since. A report published on July 16, 2026 found 83 percent of surveyed jurisdictions had passed travel rule legislation, up from 73 percent a year earlier.
The data set is standardised. A sending provider transmits the originator's name, account or wallet identifier, and usually an address, national identity number or date of birth, plus the beneficiary's name and account. Firms exchange it over messaging networks built for the purpose, using a common format so a message from a Singaporean venue can be read by a German one.
Two problems make the practice messier than the rule. The first is the sunrise problem: when the sending firm is in a country that has implemented the rule and the receiving firm is not, there is nobody to receive the message, and each firm must decide whether to send anyway. The second is the self-hosted wallet. Under the EU transfer of funds regulation, a provider must verify that its customer actually controls a self-hosted address when a transfer exceeds 1,000 euros, which is why you may be asked to sign a message with the wallet, send a small test amount, or record a screen capture.
Why this matters when you buy bitcoin
The Travel Rule is the reason a withdrawal to your own wallet asks questions that feel like an interrogation.
Expect the destination question. European platforms now ask whether the receiving address belongs to you, to another person, or to another exchange, and a wrong answer creates a mismatch later. If you withdraw to another venue, the name on both accounts must match, because a transfer arriving under a different name is exactly the pattern the rule exists to flag.
Expect proof for larger self-custody withdrawals. Signing a message with your own key is the cleanest method, and most hardware wallets support it. Learning how before you need it saves days.
Understand the privacy consequence, which is the part rarely spelled out. When the rule is applied to a withdrawal, your identity is recorded against a specific bitcoin address at two companies rather than one, and both keep it for years. The address you gave is now permanently associated with your name in databases you cannot see. Use a fresh receiving address for every withdrawal, and do not reuse an address that a regulated firm already has on file.
Where you live determines how sharply this bites. Across the 231 country guides here the picture varies: EU customers face the strictest version with no minimum, Trinidad and Tobago passed its virtual asset act in December 2025 ahead of an international review, Peru requires providers to register with the financial intelligence unit and set its own start date, and in several countries the rule exists on paper with no supervision behind it. The direction is one way, and the number of jurisdictions with no obligation at all keeps shrinking.
What the receiving exchange actually gets
Picture a 2,000 euro transfer from a Bitpanda account in Austria to a Kraken account in the same name.
Before the coins move, Bitpanda sends Kraken a structured message: your full name, your account identifier, your residential address or an equivalent identifier such as a national number, the amount, and the beneficiary name and account at Kraken. Kraken checks the beneficiary details match its own customer record. The bitcoin transaction itself carries none of this, and a block explorer shows only the ordinary transfer of an output.
If the names do not match, the receiving firm may hold the credit and open a review. If the destination had been a self-hosted wallet instead, Bitpanda would have needed to satisfy itself that you control the address, because the amount is above the 1,000 euro line.
Travel Rule vs Know Your Customer
Verification tells one company who you are; the Travel Rule sends that answer to a second company that never asked you anything. Know Your Customer is a relationship between you and the platform you signed up with, performed once and refreshed occasionally. The Travel Rule is a transfer-level obligation that fires each time coins leave, and it copies your identity outward to firms you have no account with, in countries whose data protection rules you have not read. That is why the two feel similar at the counter and differ sharply in consequence: verification creates one record, and the Travel Rule multiplies it.