The Transfer of Funds Regulation (travel rule).

At a glance

What it requires

Every crypto-asset transfer handled by a CASP must be accompanied by information on the originator (name; distributed-ledger address and/or account number; and address, official ID number, customer ID, or date and place of birth) and on the beneficiary (name; DLT address and/or account number). The beneficiary’s CASP must check what arrives and hold back, reject, or return transfers with missing or incomplete information.

No de-minimis threshold between CASPs. Unlike the old funds regime, the crypto travel rule applies from the first euro on CASP-to-CASP transfers.

Self-hosted addresses: for transfers above €1,000 to or from a self-hosted address, the CASP must verify whether that address is owned or controlled by its own customer, and apply risk-based measures. The regulation does not ban self-hosted wallets — it regulates the CASP’s handling of them.

Level 2/3: the EBA’s Travel Rule Guidelines (2024) specify how CASPs detect missing information, what “repeatedly failing” counterparties mean, and interplay with AML obligations. Compliance is supervised by the AML authorities of the Member States.

Why it matters for authorised CASPs

TFR compliance is operational, not just legal: it shapes onboarding data, transaction screening, counterparty due diligence on other CASPs, and messaging infrastructure between providers. Every provider on the MiCA Radar carries these duties alongside its authorisation. See also the DORA guide for the ICT-resilience layer, and the glossary for terms.