The Transfer of Funds Regulation (TFR) is Regulation (EU) 2023/1113 of the European Parliament and of the Council, which sets the information that must accompany transfers of funds and of crypto-assets in the European Union. It applies the FATF Travel Rule to crypto-asset service providers (CASPs) as well as to banks and payment service providers, so that the identity of the sender and recipient can be traced to fight money laundering and terrorist financing and to apply sanctions.
The regulation was adopted in 2023 as a recast of an earlier 2015 regulation on information accompanying fund transfers, and has applied since 30 December 2024, the same date that most of MiCA took effect. It is part of the EU's wider anti-money laundering package.
The TFR is often described as the EU Travel Rule. Its aim is that no transfer, whether a bank payment or a token movement on a blockchain, should leave a regulated firm without the details needed to identify who sent it and who received it. Authorities can then follow funds across firms and borders, and providers can screen both ends of a transaction.
Scope
The TFR covers transfers of funds, in any currency, where at least one of the payment service providers involved is established in the EU, and transfers of crypto-assets where at least one CASP involved is established in the EU. Certain payments, such as some card transactions for goods and services and transfers between providers acting for their own account, are excluded. For conventional wire transfers, the earlier rules carry over largely unchanged, including lighter information requirements for some low-value transfers.
Information requirements for crypto-asset transfers
For crypto-assets there is no minimum threshold: the information requirements apply to every transfer, however small. The CASP of the originator must send:
- Originator details. The originator's name, distributed ledger address or crypto-asset account number, and address, official document number, customer identification number or date and place of birth.
- Beneficiary details. The beneficiary's name and distributed ledger address or account number.
- Legal entity identifier. Where available, an identifier for legal persons.
The information must be sent before or at the same time as the transfer, in a secure way, but need not be written onto the blockchain itself. The originator's CASP must verify its own customer's data. The beneficiary's CASP must have risk-based procedures to detect missing or incomplete information and decide whether to reject, return or suspend the transfer or ask for the data, and must report CASPs that repeatedly fail to provide it.
Self-hosted wallets
Transfers to or from an unhosted wallet, also called a self-hosted address, are treated separately. The CASP must still collect the originator and beneficiary information from its own customer. For transfers above EUR 1,000 involving a self-hosted address, it must also take adequate steps to assess whether that address is owned or controlled by its customer. CASPs are expected to apply risk-mitigating measures to such transfers in line with their risk assessment.
A CASP that sends or receives a transfer through an intermediary CASP must make sure the information travels with it. Records of the information must be kept so that it can be produced at the request of authorities, and the regulation overrides contractual terms that would prevent sharing. For crypto-asset transfers between two CASPs, both must check that their counterparty is able to receive and protect the data before sending.
Guidance and supervision
The European Banking Authority (EBA) issued Travel Rule guidelines in 2024, applying from 30 December 2024, which set out what information is required, how to handle missing data, and how to deal with counterparties in countries that have not yet adopted the Travel Rule. National competent authorities supervise compliance as part of firms' AML compliance programmes, and the TFR also amended the AML directive so that CASPs became obliged entities for customer due diligence.
Practical challenges
Compliance depends on CASPs being able to identify each other and exchange data securely. The industry uses several competing messaging protocols and directories, which do not always connect, and counterparts outside the EU may not yet be subject to equivalent rules, the so-called sunrise problem, which mirrors a sunrise period in other regimes. Firms also need to reconcile the TFR with data protection law, since personal data travels with every transfer, and to integrate Travel Rule data with transaction monitoring and sanctions screening. The approach is close to the broader Travel Rule regimes adopted in other jurisdictions, but the absence of any threshold makes it stricter than many.
External links
Ref 1050000666