Exchanges
The crypto travel rule: what it requires and what users see
The travel rule requires the firm that sends a crypto transfer to collect the sender’s and the recipient’s details and pass them to the firm that receives it, as banks have long done for wire transfers. The standard is the Financial Action Task Force’s; in the EU it has applied to every transfer by a provider since 30 December 2024, with extra checks above EUR 1,000 when the other end is a self-hosted wallet, and in the US the Bank Secrecy Act version applies from $3,000. For a user it explains two things that otherwise look arbitrary: why a withdrawal form asks who owns the address, and why a deposit can sit on hold.
This describes what the rules say, as read on 22 November 2026. It is not legal advice, and countries outside the EU and the US have their own versions.
Where the rule comes from
The FATF writes the international anti-money-laundering standard, and countries give it force through their own law. Its Recommendation 16, on payment transparency, asks countries to make financial institutions include required and accurate information about the originator, and required information about the beneficiary, with payments and value transfers. That information is to stay with the payment throughout the payment chain (the FATF Recommendations).
Paragraph 7(b) of the Interpretive Note to Recommendation 15 carries this over to virtual assets. The sending provider obtains and holds the originator’s and beneficiary’s information and submits it to the receiving provider immediately and securely; the receiving provider obtains and holds it too, and both make it available to authorities on request. A footnote adds that the information need not be attached to the transfer itself. Countries may set a threshold of USD/EUR 1,000 for virtual asset transfers, below which the names of both parties and a wallet address or transaction reference are enough, and need not be verified unless something looks suspicious (FATF guidance of 2021, paragraphs 191 and 192).
A standard is not a law, and adoption is uneven. In the FATF’s 2026 targeted update on virtual assets, 83% of respondents, 91 of 109 jurisdictions, reported having passed legislation for the travel rule, and 55 of those 91 had not yet issued findings or taken enforcement or other supervisory action focused on it (paragraphs 24 and 25). The answers were self-reported and not independently verified. The standard itself is also moving: the FATF revised Recommendation 16 in June 2025, standardising the information that must accompany cross-border peer-to-peer payments above USD/EUR 1,000, with the changes to take effect by the end of 2030.
Why a blockchain transfer needs a separate message
A wire transfer carries its payment details inside the message that moves the money. A blockchain transfer carries addresses and an amount, and nothing that names anyone. So the travel rule data usually travel separately, between the two providers, and the transfer can settle on chain whether or not the data have arrived.
The FATF’s 2021 guidance is direct about the consequence. Because the identifying information can be held apart from the ledger, a transfer can complete with that information missing, so providers have to screen it separately. Its examples of controls are holding a wallet until screening is done, or receiving into the provider’s own wallet and moving the funds to the customer’s only once screening has raised no concern (paragraph 194). The same guidance says the FATF knew of no technically proven way to identify, from an address alone and accurately in all cases, which provider manages it (paragraph 197). A sending provider therefore has to work out whether the recipient is a customer of another provider, which one, and whether that provider can be trusted with the data.
Two practical frictions follow. Several messaging systems carry travel rule data and not all of them can talk to each other, so a provider may need more than one to reach its counterparties, as the European Banking Authority notes in its Travel Rule Guidelines. And because countries adopt the rule at different times, a provider bound by it may be sending to one that is not; the FATF calls this the sunrise issue and leaves the response to each provider’s risk assessment, including requiring compliance from counterparties by contract (2021 guidance, paragraph 200).
The EU version: every transfer, since 30 December 2024
In the EU the rule is Regulation (EU) 2023/1113, the Transfer of Funds Regulation, which applies from 30 December 2024 (Article 40). It covers crypto transfers where the provider on either side, or an intermediary, has its registered office in the Union, and it does not apply to person-to-person transfers made without any provider (Article 2).
The sending provider must make sure each transfer is accompanied by the originator’s name, ledger address and account number where one is used, and either the originator’s address with an official personal document number and customer identification number, or the originator’s date and place of birth (Article 14(1)). For the beneficiary, the name and ledger address or account number are enough (Article 14(2)). The information goes before, with or alongside the transfer, securely, and does not have to be inside it (Article 14(4)). The sender’s details must be verified from a reliable, independent source, which counts as done where the customer’s identity was verified and the records kept under the anti-money-laundering rules, and the provider may not execute the transfer until all of this is in place (Article 14(6) to (8)).
The EU took no threshold. The rules for ordinary money transfers distinguish amounts up to EUR 1,000; for crypto-assets, recital 30 says transfers should meet the same requirements regardless of amount and of whether they are domestic or cross-border.
The receiving side has duties too. A receiving provider must have procedures to detect missing information (Article 16(1)). Where it finds the information missing or incomplete, it must, on a risk-sensitive basis and without undue delay, either reject the transfer or return the assets, or ask for the information before making the assets available to its customer (Article 17(1)). A counterparty that repeatedly fails to send the data can be warned, given deadlines, restricted or cut off, and the failure is reported to the authority (Article 17(2)). Records are kept for five years (Article 26).
Self-hosted wallets and the EUR 1,000 line
A self-hosted address, in the regulation’s definition, is one not linked to a crypto-asset service provider or to a non-EU entity providing similar services (Article 3(20)). There is no provider at that end to send data to, so the obligation falls on the one provider involved. Whether sending or receiving, it must obtain and hold the originator and beneficiary information and make sure the transfer can be individually identified; above EUR 1,000 it must also take adequate measures to assess whether the address is owned or controlled by its own customer (Articles 14(5) and 16(2)). Recital 39 adds that the information is usually collected from the customer and that the provider should not in principle have to verify details about the user of the self-hosted address.
The EBA’s Travel Rule Guidelines (EBA/GL/2024/11), which also apply from 30 December 2024, describe how that plays out. A provider first works out whether the other end is self-hosted, using blockchain analytics, data providers or messaging identifiers, and asks the customer if it cannot tell (paragraphs 77 and 78). It values the transfer in euros at the exchange rate at the time of the transfer, ignoring fees (paragraph 82). To assess ownership above the threshold it uses at least one of these methods (paragraph 83):
- A remote verification under the EBA’s customer-onboarding guidelines, either unattended with the customer displaying the address, or attended by a member of staff.
- A test transfer: a predefined amount set by the provider, preferably the asset’s smallest denomination, moved between the address and the provider’s account.
- A signed message: the customer signs a specific message with the key for that address in their wallet software.
- Another technical means, provided it lets the provider be fully satisfied that it knows who owns or controls the address.
Where one method on its own is not reliable enough, the provider combines them (paragraph 85). Once satisfied, it may record the address as the customer’s and not repeat the check for later transfers to and from it, keeping the whitelisted address under review for changes in risk or ownership (paragraph 86).
The US version: the Bank Secrecy Act at $3,000
The US rule is older and has a threshold. Under 31 CFR 1010.410(e), a non-bank financial institution handling a transmittal of funds of $3,000 or more must keep records, including the transmittor’s name and address, the amount, the date, any payment instructions and the identity of the recipient’s financial institution. Paragraph (f), the travel rule proper, requires the transmittor’s institution and any intermediary to include the transmittor’s name, account number and address, the amount, the date, the identity of the recipient’s institution and the recipient details received, in the order sent on. The records are kept for five years (31 CFR 1010.430(d)).
Crypto came under it through interpretation rather than a new rule. FinCEN’s guidance of 9 May 2019 (FIN-2019-G001) says it creates no new requirements. It treats a transfer involving convertible virtual currency as an instruction to pay a determinable amount of money, and so as a transmittal of funds that may fall within the travel rule at $3,000 or its equivalent in virtual currency. The required information has to be provided before or at the time of the transfer, and it may go in a separate message where the transfer protocol cannot carry it (section 2.1). The same guidance describes a person using an unhosted wallet to buy goods or services on their own behalf as not a money transmitter (section 4.2.1).
Two proposals to go further were withdrawn in late 2026. FinCEN withdrew on 6 October 2026 its December 2020 proposal, which would have required reports on transactions over $10,000 with unhosted wallets and records above $3,000. FinCEN and the Federal Reserve withdrew on 9 November 2026 their October 2020 proposal to lower the threshold from $3,000 to $250 for transfers beginning or ending outside the US and to state expressly that the rules cover virtual currency. In that second notice the agencies said more than five years had passed and cited developments since, including the federal framework for payment stablecoins enacted in July 2025. The US rule therefore stands at $3,000, with nothing in it specific to self-hosted wallets.
What it means when you send or receive
Most of this happens between firms, and users meet it in a handful of places.
Withdrawing from an EU provider. Expect to be asked for the recipient’s name and whether the address belongs to another provider or to a self-hosted wallet. If it is a self-hosted address and the amount is above EUR 1,000, expect to show that it is yours, by one of the methods above; once an address has been accepted, later withdrawals to it may not need the step again.
Depositing into an EU provider. From another provider, the receiving firm may hold the coins until the originator data arrive, ask for them, or send the transfer back. On chain the coins may already have arrived, which is why a deposit can be visible on a block explorer and not yet in the account. From your own wallet, the provider asks you for the details and, above EUR 1,000, for proof of control.
Moving between countries. A transfer between a provider bound by the rule and one in a country that has not adopted it depends on the sending firm’s risk decision, so it may be delayed or refused at either end.
Using a US provider. The record-keeping and travel rule obligations start at $3,000. Below that, and for self-hosted wallets, what a provider asks comes from the identification and monitoring procedures of its anti-money-laundering programme, which FinCEN’s guidance says a hosted wallet provider must apply to its users (section 4.2.1), rather than from a threshold rule.
The rule does not require names on the ledger. The data pass between providers, who keep them for five years in both the EU and the US, and that is what joins an address to a person when an investigator later asks; what the chain shows and what KYC adds follows that join further. The rule is one reason a withdrawal can be slower than the chain itself, which belongs among the questions in what to compare when choosing an exchange. For providers in the EU it sits alongside the licensing regime set out in MiCA explained, and what moving to self-custody gives up and gains is weighed in exchange or self-custody.