B.BlockAxis⌕ Search
Menu

Travel Rule: information accompanying transfers

The Travel Rule concerns information about the originator and beneficiary accompanying covered transfers.

IntermediateContent revised · 13.09.20263 min reading · allow 5–10 more minutes for the workshopBlockAxis

Your learning plan

Separate transfer information from public-chain data

By the end, explain the diagram in your own words, solve the case and justify the correction.

Prerequisites : Hot, warm and cold wallets · AML, KYC, CDD and EDD explained

Level 2 · Intermediate →

Reading path · 26 / 35 · Intermediate

Key takeaway

The Travel Rule concerns information about the originator and beneficiary accompanying covered transfers.

The essentials

The Travel Rule concerns information about the originator and beneficiary accompanying covered transfers. In the EU, Regulation (EU) 2023/1113 and EBA guidance provide the relevant framework for covered crypto-asset transfers. These information obligations are separate from the blockchain’s technical transfer format.

How it works

Operationally, a provider needs to identify the counterpart, exchange required information through appropriate channels and handle missing or incomplete data. Do not place personal identity information directly on a public blockchain simply because the transfer itself is on-chain. Data protection and secure transmission remain relevant.

What to watch

The EBA guidelines apply from 30 December 2024. FATF standards and national implementations should not be treated as interchangeable with the EU text. Transfers involving self-hosted addresses require careful scope analysis; an address alone does not identify its controller. A transaction-monitoring tool does not replace the necessary information and exception process.

Understand the details

Transfer-information rules concern identifying information accompanying covered transfers between relevant parties. A blockchain address alone does not establish a person’s verified identity. Information exchange can happen through a separate secure channel; placing personal information into a public transaction is not a general solution.

Boundaries and common mistakes

The workflow should establish the counterparty, required information, completeness and handling of missing or inconsistent data. Self-hosted addresses require assessment under the applicable rules rather than being assumed automatically prohibited or automatically outside all obligations. Protect the information throughout collection, exchange and retention.

The mechanism at a glance

  1. Transfer instruction
  2. Counterparty and information checks
  3. Secure information exchange
  4. Decision and retained evidence
Separate transfer information from public-chain data. Conceptual map: read these four landmarks together with the explanation above.
Applied workshop · work at your own pace

Apply the lesson to a case

A transfer arrives with a valid transaction hash but incomplete beneficiary information. Build separate technical and compliance status columns. Identify who reviews the missing information and how the decision is recorded.

Why can on-chain confirmation and completion of the information process differ?

Choose one answer.

Terms in this lesson
Travel Rule
Requirements for originator and beneficiary information accompanying covered transfers under the relevant legal framework.
Prepare a correction note

Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.