Home/Regulation/Travel Rule

Every transfer carries its names, from the first euro.

The recast Transfer of Funds Regulation brings the travel rule to crypto-assets. Since 30 December 2024, every transfer between CASPs carries information on the originator and the beneficiary, with no minimum amount, and transfers involving self-hosted wallets come with checks of their own.

€0

minimum amount between CASPs, so the rule applies from the first euro

€1,000

above which a self-hosted wallet’s ownership must be assessed

30 Dec 2024

the date the rule began to apply to crypto-asset transfers

0

parties named on every transfer, the originator and the beneficiary

What the rule asks, transfer by transfer.

The rule applies to every transfer between CASPs. Avus makes complete data the default rather than a manual step.

Art. 14

Information on the originator

The originator’s name, distributed ledger address or account number, and address, official document number, customer number or date and place of birth, plus an LEI where there is one.

Drawn from KYC and sent over whichever network the counterparty uses.

Travel Rule
Art. 14

Information on the beneficiary

The beneficiary’s name and distributed ledger address or account number travel with the transfer, with an LEI or equivalent for legal persons.

Counterparties are found by address and checked before anything is sent.

Travel Rule
Timing

Before, or with, the transfer

Information is sent before or at the same time as the transfer, securely and in a way that protects personal data.

Funds are held until the data has been accepted, then released on the record.

Travel Rule
Self-hosted

Self-hosted wallets

For transfers above €1,000 to or from a self-hosted address, the CASP must assess whether the address is owned or controlled by its own customer.

Customers prove ownership by signing a message, and the proof stays with the transfer.

Travel Rule
Art. 16 and 17

Missing or incomplete data

The receiving CASP detects missing information and decides, on a risk basis, whether to reject, return or suspend the transfer and ask for it. Counterparties that fail repeatedly are reported.

Hold, ask or return by policy, with repeat offenders surfaced automatically.

Monitoring and alerts
Records

Records kept with the transfer

What was sent and received is retained alongside the transaction, in line with EU anti-money laundering record-keeping.

Each transfer carries its own record of what was sent, what came back and who released it.

Governance and audit

Key dates.

The rule is in force across the EU, and the counterparties are now all authorised.

  1. The recast TFR enters into forceThe travel rule is extended from wire transfers to crypto-assets.
  2. EBA travel rule guidelinesWhat to send, how to detect gaps and how to treat self-hosted wallets.
  3. The rule appliesEvery transfer between CASPs carries originator and beneficiary data.
  4. Every EU CASP is authorisedWith MiCA’s transitional periods over, counterparties in the EU are known.

Data first, then value, every time.

The rule is simple to state and hard to run at volume. Keeping the jobs apart is what makes it hold.

Engine

Checks every field

Completeness and name matching run the same way on every transfer, in and out.

Agent

Chases what is missing

Case AI drafts the request to the counterparty and follows up until the data arrives.

Person

Decides the exceptions

Holds and returns outside policy go to a person, who decides on the record.

See a transfer go from held to released.

We will run a transfer to a counterparty on another network and one to a self-hosted wallet, end to end.

Sources

A summary to help you find your way, not legal advice. The official texts are the reference, and your own counsel should confirm how they apply to you.