Policy & Regulation
The Crypto Travel Rule: What the EU Requires and Where It Breaks
Why an exchange asks you to sign a message or send a test amount: how the EU applies the Travel Rule to every crypto transfer, how the UK, Australia and the US differ, and where the sender's data…

The 1995 Travel Rule and How Crypto Inherited It
The Travel Rule rests on a plain idea: when value moves between two financial institutions, the names behind the payment move with it. The American version, issued by the Treasury in January 1995, sits at 31 CFR 1010.410(f). For any transmittal of $3,000 or more, the sender's institution must pass on the sender's name and address (and the account number, if the payment is ordered from an account), the amount, the execution date, the identity of the recipient's institution and of its own, and whatever recipient details it received.
Crypto inherited the rule by interpretation rather than by statute. FinCEN's guidance of 9 May 2019 (FIN-2019-G001) reasoned that a transmittal order involving convertible virtual currency is an instruction to pay "a determinable amount of money", so a transfer of "$3,000 or more (or its equivalent in CVC)" may trigger the rule. The EU's own regulation, in its second recital, traces its crypto version to the changes made in June 2019 to the standards of the Financial Action Task Force (FATF), the global anti-money-laundering standard-setter.
The rule only works where two regulated providers meet and can identify each other. The European Union has written the strictest version among the four rulebooks compared here: data on every transfer whatever its size, and an ownership check above €1,000 when the other end is the customer's own wallet. That pushes the real compliance work to the edges the rule cannot see: self-hosted wallets, unlicensed offshore counterparties, and messaging systems that do not talk to each other. The United States, meanwhile, still runs its 1995 threshold.
:::callout-info In one minute: Since 30 December 2024, every crypto transfer handled by an EU crypto-asset service provider must carry the sender's and the recipient's details, whatever the amount. Moving coins to or from your own wallet is allowed. Above €1,000, the provider must assess whether you own or control that address; signing a message or sending a small test amount are among the accepted methods. A receiving provider that gets a transfer without the data can reject it, return it, or ask for the data before releasing the funds. In the United States the rule still starts at $3,000, and in October 2026 FinCEN formally withdrew its 2020 proposal on unhosted wallets. The European Commission owes a report on how the rules work, including whether crypto transfers need a minimum amount, by 30 June 2027. :::
What the EU Makes Every Transfer Carry
Regulation (EU) 2023/1113, the recast Transfer of Funds Regulation (TFR), has applied since 30 December 2024. It covers a crypto transfer whenever the crypto-asset service provider (CASP) of either the sender or the recipient has its registered office in the EU. Both key terms are borrowed: Article 3 defines a crypto-asset and a CASP by pointing to MiCA, Regulation (EU) 2023/1114. Under Article 2, a person-to-person transfer carried out without any CASP falls outside the regulation.
Article 14(1) lists what the sender's CASP must attach about its customer: name; distributed ledger address and crypto-asset account number; postal address with country, official personal document number and customer identification number, or instead date and place of birth; and, where the message format has a field for it, a Legal Entity Identifier (LEI). Article 14(2) adds the recipient's name, address on the ledger, account number and, where available, LEI. The sender's CASP must not execute the transfer before it complies in full (Article 14(8)).
There is no minimum amount. Recital 30 explains why: crypto transfers can be split into small amounts, spread across "one-time use DLT addresses" and automated, and prices move fast enough to make linked transactions hard to add up. Its conclusion is that crypto transfers "should be subject to the same requirements regardless of their amount and of whether they are domestic or cross-border transfers." Ordinary transfers of funds under the same regulation still carry lighter requirements at or below €1,000.
The data do not travel on the blockchain. Article 14(4) requires them to be submitted before, or at the same time as, the transfer, securely and in line with the GDPR, and says they need not be "attached directly to, or be included in" the transfer itself. FinCEN's 2019 guidance had taken the same view: the parties "are not required to use the same system or protocol" for the value and for the data.
The receiving side carries the enforcement. Under Article 16, the recipient's CASP must have procedures to detect missing data, and under Article 17(1) it must, on a risk-sensitive basis, reject or return the transfer, or ask for the missing data before making the coins available. When a counterparty repeatedly fails to send the data, Article 17(2) has the receiving CASP act, starting if it chooses with warnings and deadlines, up to rejecting future transfers or restricting or ending the relationship, and report the failure to its anti-money-laundering supervisor.
Self-Hosted Wallets: Where Users Meet the Rule
Article 3(20) defines a self-hosted address as a ledger address not linked to a CASP or to a non-EU entity providing similar services. Under the second limb, an address held at an exchange outside the EU, licensed or not, is not "self-hosted", so the data are owed to that counterparty and the ownership check does not apply. The EU does not ban transfers to or from self-hosted wallets. Recital 38 says the rules apply to such transfers "as long as there is a crypto-asset service provider involved."
Under Articles 14(5) and 16(2), the CASP on the regulated end collects the data on both parties, usually from its own customer, and makes sure the transfer can be individually identified. Recital 39 adds that the CASP "should in principle not be required to verify the information on the user of the self-hosted address". Above €1,000, the CASP must take adequate measures to assess whether the address is owned or controlled by its own customer.
The European Banking Authority's Travel Rule Guidelines (EBA/GL/2024/11, dated 4 July 2024 and applicable from 30 December 2024) list the accepted methods. A CASP should use at least one: unattended or attended remote verification displaying the address; sending a predefined amount, "preferably the smallest denomination", from and to the address; asking the customer to sign a specific message with the address's key; or other technical means that leave the CASP "fully satisfied". Where one method is not reliable enough, the CASP should combine several.
The €1,000 line is measured in euros at the exchange rate of the moment, regardless of fees. The sending CASP applies it when the transfer is ordered, the receiving CASP at receipt. Once satisfied, a CASP may record the address and skip the check on later transfers, which the guidelines call "whitelisting".
These are the prompts users meet: a name to declare for the recipient, a message to sign, a tiny deposit to send back. Several respondents to the EBA's consultation said the draft unfairly targeted self-hosted wallets. The EBA replied that such transfers carry "inherently higher risk" than transfers between two CASPs, because their holders face no identification requirements.
How the Data Travel Between Providers
The TFR is technology-neutral by design. Recital 50 says it should not mandate a particular technology, that industry-led standard-setting "will be critical", and that the resulting solutions should be interoperable. The EBA guidelines turn that into a test: CASPs should use systems "technically capable of the full transmission and reception of information without gaps or errors". The data may go on-chain, or off-chain through direct exchanges between CASPs, APIs or third-party solutions, but no later than the start of the blockchain transaction.
The guidelines allowed CASPs an exceptional derogation until 31 July 2025, during which technical gaps could be patched with alternative ways to collect and hand over the missing data. When choosing a protocol, a CASP is told to weigh its "reachability": how many counterparties it can actually reach, and how often transfers succeed.
The EBA notes that not all protocols on the market currently are interoperable as they often adopt different standards to comply with the travel rules. This may impact travel rule rollout and be resource-intensive where counterparties are able to comply with the transfer requirements only by integrating multiple protocols. — European Banking Authority, Final Report on the Travel Rule Guidelines (EBA/GL/2024/11)
Before any message can be sent, the CASP has to know who sits at the other end. The guidelines tell it to use technical means, "including but not limited to blockchain analytics, third-party data providers and identifiers used by messaging systems", and to ask its customer when those fail. If the answer is another CASP, it must identify that CASP accurately. A transfer to an unlicensed exchange abroad is where this step tends to fail: the exchange may sit on no messaging network, and nothing obliges it to answer.
A provider that loses the right to operate keeps the obligation. MiCA's transitional period ended on 1 July 2026, and on 23 June 2026 the European Securities and Markets Authority (ESMA) told providers without authorisation to wind down their EU business. It expects them to keep complying "with applicable transfer of funds and crypto-asset transfer traceability obligations" while they do. The same statement invited their clients to move assets to an authorised CASP or to a self-hosted wallet.
The United States Still Runs a $3,000 Rule
Washington tried to change the threshold and backed away. On 27 October 2020 the Federal Reserve Board and FinCEN proposed cutting it from $3,000 to $250 for transfers that begin or end outside the United States, and clarifying that "money" in the rule covers convertible virtual currency. Comments closed on 27 November 2020, and no final rule followed.
The federal Unified Agenda later split the proposal in two. It lists the threshold cut (RIN 1506-AB48) as withdrawn on 3 September 2021. The virtual-currency clarification (RIN 1506-AB41), which the Fall 2024 agenda still planned to re-propose, is listed as withdrawn on 16 April 2025.
A second proposal, published on 23 December 2020, aimed at unhosted wallets directly. It would have made banks and money services businesses keep records and verify their customer's identity when a counterparty used an unhosted wallet above $3,000, and report such transactions above $10,000. FinCEN withdrew it in a Federal Register notice of 6 October 2026, citing the July 2025 report of the President's Working Group on Digital Asset Markets, and wrote that it "will take no further action on this NPRM."
The 1995 rule therefore still governs American crypto transfers, through the 2019 guidance rather than through any crypto-specific statute. FinCEN's April 2026 proposal on anti-money-laundering programmes for payment stablecoin issuers keeps that frame: it would impose the Recordkeeping and Travel Rules on those issuers and make clear that transmittal orders in payment stablecoins are covered, while "not proposing to substantively change" the rules themselves.
How the EU, UK, Australia and US Compare
Every jurisdiction that adopts the rule has to settle three questions: how small a transfer it covers, what to do about wallets nobody supervises, and what happens when the other side cannot receive the data. The EU, the UK, Australia and the United States answer them differently, and each answer sets a point at which the data can stop travelling.
| EU (TFR) | UK (MLR 2017, Part 7A) | Australia (AML/CTF Act) | United States (31 CFR 1010.410(f)) | |
|---|---|---|---|---|
| Crypto covered since | 30 Dec 2024 | 1 Sep 2023 | 1 Jul 2026 for virtual-asset transfers by existing and new VASPs (the rest of the reformed rules from 31 Mar 2026) | 2019 guidance applying the 1995 rule |
| Minimum amount | None | One extra originator identifier from £800 when the chain leaves the UK | None | $3,000 |
| Self-hosted wallets | Data collected from the customer; ownership check above €1,000 | Data may be requested; funds not released if requested data never arrive | No message to send; payer and payee data collected; reports on unverified wallets from 31 Mar 2029 | Dec 2020 proposal withdrawn on 6 Oct 2026 |
| Counterparty cannot receive | Sender may not execute until the data go (Art 14(8)); receiver rejects, returns or requests (Art 17) | Collect, verify and store before sending | Data need not be sent if they cannot be received securely; reasons recorded | No exception: the sending institution must still pass the data on |
The United Kingdom's regime, in force since 1 September 2023, sends only names and account numbers when every firm in the chain is in the UK, with more data on request within three working days. When the chain leaves the UK, from £800 the transfer must also carry one further identifier for the originator (a customer identification number, an address, an identity-document number, or a date and place of birth); £800 replaced 1,000 euros on 30 June 2026.
For transfers to jurisdictions without the rule, the Financial Conduct Authority set out what it expects:
If the firm cannot receive the necessary information, the UK cryptoasset business must still collect and verify the information as required by the Money Laundering Regulations (MLRs) and should store that information before making the cryptoasset transfer. — Financial Conduct Authority, statement on the Travel Rule for UK cryptoasset businesses
Australia's reformed AML/CTF regime began on 31 March 2026, but section 12 of the AML/CTF Transitional Rules 2026 held back Part 5 of the Act, which deals with obligations relating to transfers of value, until 1 July 2026 for virtual asset service providers. Existing and newly regulated providers alike must apply the travel rule to virtual-asset transfers from that date. The reformed rules have no minimum: neither section 64 of the AML/CTF Act nor the travel-rule table in Part 8 of the AML/CTF Rules 2025 sets an amount threshold.
The Rules exempt transfers to self-hosted wallets from passing on a message, while still requiring the payer's data to be collected and verified. Reports on transfers involving unverified self-hosted wallets start on 31 March 2029, and an ordering institution may withhold data from a recipient that it has established, on reasonable grounds, cannot receive them securely.
The EU's Review Dates
The TFR set its own review dates. Article 37(2) required the Commission, after consulting the EBA, to issue by 1 July 2026 a report on the risks of transfers involving self-hosted addresses or entities outside the EU, with amendments if appropriate. The Commission had not published that report by mid-October 2026.
Article 37(3) requires a report on the application and enforcement of the regulation by 30 June 2027, with a legislative proposal if appropriate. It must weigh the costs and benefits of de minimis thresholds for crypto transfers, the state of interoperable compliance technology, and further measures on self-hosted addresses, up to "limitation, control or prohibition of transfers involving self-hosted addresses." Whether the no-threshold rule survives, and what happens at the wallet edge, will be argued over that report.
Sources
- Regulation (EU) 2023/1113 on information accompanying transfers of funds and certain crypto-assets (OJ L 150, 9.6.2023) eur-lex.europa.eu
- European Banking Authority, Travel Rule Guidelines, EBA/GL/2024/11 (4 July 2024) eba.europa.eu
- ESMA, public statement on the end of the MiCA transitional period, ESMA75-113276571-1710 (23 June 2026) esma.europa.eu
- eCFR, 31 CFR 1010.410 (Recordkeeping and Travel Rules) ecfr.gov
- FinCEN, FIN-2019-G001, guidance on convertible virtual currencies (9 May 2019) fincen.gov
- Federal Reserve Board and FinCEN, proposed rule on the Recordkeeping and Travel Rule threshold, 85 FR 68005 (27 October 2020) federalregister.gov
- Unified Agenda, Fall 2021, RIN 1506-AB48 (threshold, withdrawn 3 September 2021) reginfo.gov
- Unified Agenda, Fall 2024, RIN 1506-AB41 (second proposal planned) reginfo.gov
- Unified Agenda, Spring 2025, RIN 1506-AB41 (withdrawn 16 April 2025) reginfo.gov
- FinCEN, withdrawal of the unhosted-wallet proposed rule, 91 FR 63514 (6 October 2026) federalregister.gov
- FinCEN and OFAC, proposed AML/CFT and sanctions program rule for permitted payment stablecoin issuers, 91 FR 18582 (10 April 2026) federalregister.gov
- UK Money Laundering Regulations 2017, regulation 64C (inter-cryptoasset business transfers) legislation.gov.uk
- UK Money Laundering Regulations 2017, regulation 64G (unhosted wallet transfers) legislation.gov.uk
- The Money Laundering and Terrorist Financing (Amendment) Regulations 2026 (S.I. 2026/621), regulation 32 (amends regulation 64C) legislation.gov.uk
- The Money Laundering and Terrorist Financing (Amendment) Regulations 2026 (S.I. 2026/621), regulation 33 (amends regulation 64G) legislation.gov.uk
- Financial Conduct Authority, expectations for UK cryptoasset businesses complying with the Travel Rule fca.org.uk
- Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth), section 46A and Part 5 (sections 64 and 66A) legislation.gov.au
- Anti-Money Laundering and Counter-Terrorism Financing Rules 2025, Part 8 (rules 8-3 and 8-8) legislation.gov.au
- Anti-Money Laundering and Counter-Terrorism Financing Transitional Rules 2026, sections 11 and 12 legislation.gov.au
- Hall & Wilcox, Transitional Rules update announced for Australia's AML/CTF reforms: key guidance for reporting entities (27 January 2026) hallandwilcox.com.au