18 November 2026 | Author: ABF Swap Research Team
The crypto Travel Rule requires exchanges and other crypto-asset service providers (CASPs) to collect the names and account details of the sender and the recipient of a transfer and pass them on to the provider at the other end. In the European Union, it has applied under Regulation (EU) 2023/1113 since 30 December 2024, and it covers every transfer between CASPs, whatever the amount.
For users, the Travel Rule usually means a few extra fields when you withdraw crypto, and sometimes a request to prove that you own the wallet you are sending to. Missing or incorrect information is now one of the most common reasons for a transfer to be held.
Key takeaways
Risk notice:
Blockchain addresses are still pseudonymous, but transfers that pass through regulated providers in Europe are no longer anonymous. Every exchange already knows who its customers are through KYC, and Travel Rule crypto requirements now make it share that identity with the provider on the other side of each transfer, so both ends of the payment can be linked to real people.
The data itself never appears on the blockchain. Anyone looking at a block explorer still sees only addresses and amounts. The names, account numbers and other details travel separately, through secure messaging between the two providers, and are protected under the GDPR.
The Travel Rule is a requirement for financial and crypto service providers to send identifying information about the sender (originator) and recipient (beneficiary) along with each transfer. Regulators enforce it so that funds can be traced to real people when investigating money laundering, terrorist financing or sanctions evasion, and so that providers can screen both parties before completing a transfer.
The rule began in banking. For decades, banks have had to include sender and recipient details with wire transfers, a requirement set out in FATF Recommendation 16. In 2019, the Financial Action Task Force extended its standards to virtual asset service providers, creating what is now known as the FATF Travel Rule. The FATF Recommendations require providers to obtain, hold and securely transmit originator and beneficiary information for virtual asset transfers.
FATF standards are not law on their own. Each country turns them into its own rules, which is why Travel Rule requirements differ between the EU, the UK, South Africa and other jurisdictions.
The EU applies a zero-threshold rule to crypto transfers between CASPs. FATF allows countries to require less information for transfers below USD/EUR 1,000, but the EU Transfer of Funds Regulation does not use that option for crypto: the full set of originator and beneficiary data must accompany every CASP-to-CASP transfer, from a few cents upwards.
The €1,000 figure still appears in EU rules, but for a different purpose. It applies to transfers to or from self-hosted wallets, where it triggers a check on whether the customer owns or controls the address.
| Jurisdiction | Rule | Threshold for CASP-to-CASP data |
|---|---|---|
| FATF standard | Recommendation 16 applied to virtual assets | Countries may require less data below USD/EUR 1,000 |
| European Union | Regulation (EU) 2023/1113, since 30 December 2024 | None: full data for every transfer |
| United Kingdom | Money Laundering Regulations, since 1 September 2023 | Reduced data below €1,000 |
| South Africa | FIC Directive 9, since 30 April 2025 | Full verified data above R5,000; minimum data below |
The core Travel Rule requirements in the EU fall on the sending and receiving CASPs. The originator's CASP must collect the sender's and recipient's details, verify the sender's information and send the data before or with the transfer. The beneficiary's CASP must check that the data has arrived and is complete before making the funds available.
If information is missing or incomplete, the receiving provider must act on a risk-based basis: it can reject the transfer, return the funds, or ask for the missing data before releasing them. Providers that repeatedly fail to send the data can be warned, restricted and reported to the authorities.
The personally identifiable information (PII) sent with an EU crypto transfer is set out in Article 14 of the regulation:
| Party | Information sent |
|---|---|
| Originator | Name; blockchain address and crypto-asset account number, where one exists; address including country, or official document number, customer number, or date and place of birth |
| Beneficiary | Name; blockchain address and crypto-asset account number, where one exists |
| Legal entities | Legal entity identifier (LEI) or equivalent, where available |
The data must be transmitted securely and in line with data protection law, and it does not have to be embedded in the blockchain transaction.
Travel Rule compliance adds a step between clicking "withdraw" and the funds leaving the exchange. The sending provider must identify the receiving provider, send the data and, in many cases, wait for confirmation. When that exchange of data fails, the blockchain transfer is not sent, or the receiving side holds the funds until the information arrives.
Most Travel Rule delays are technical. Providers format the data using a common standard, IVMS 101, but send it through different messaging networks, such as TRP, TRISA, Sygna Bridge or Notabene, which do not all connect with each other. If the sending provider cannot reach the receiving one, or the receiving one cannot read the message, the transfer may be held, rejected or returned.
A related problem is the "sunrise issue": the Travel Rule took effect in different countries at different times, and some jurisdictions still have no equivalent rule. A European CASP may therefore be required to send data to a provider that has no obligation, or no system, to receive it.
Transfers between Europe and other regions face the most friction. A provider in a country without Travel Rule legislation may not respond to data requests, and EU CASPs must then decide, case by case, whether the risk is acceptable. Some refuse transfers to unidentified or unregulated providers altogether.
Before sending a large amount abroad, check whether both providers support the Travel Rule and the same messaging network, or send a small amount first to see whether it arrives without a hold.
A self-hosted, or unhosted, wallet is one where you hold the private keys and no provider stands between you and the blockchain. The EU does not regulate these wallets directly. Instead, when you send crypto from an exchange to your own wallet, or receive crypto from one, the exchange collects information about the transfer and, above €1,000, checks that the wallet is yours.
For transfers of more than €1,000 to or from a self-hosted address, the CASP must take adequate measures to assess whether the address is owned or controlled by its customer. Below that amount, it still collects and holds the originator and beneficiary information and keeps the transfer identifiable, but it does not have to check ownership of the wallet.
The EBA Travel Rule Guidelines, which apply from 30 December 2024, set out how providers should handle self-hosted addresses and missing information. Transfers that appear to be split into smaller amounts to stay under €1,000 can be treated as linked and checked together.
Proving ownership of a wallet usually takes one of the following forms:
| Method | How it works | Cost | When it is used |
|---|---|---|---|
| Satoshi test | You send a small, exact amount, such as 0.000123 BTC, from the wallet to an address set by the provider | A network fee | Any wallet that can send funds |
| Message signature | The wallet signs a text message with its private key; the provider checks the signature against the address | None | Wallets that support message signing |
| Other evidence | Information or documents the provider accepts, such as a declaration of ownership | Varies | Where the methods above are not possible |
A signature proves control without moving funds, so it is usually the faster option. Keep the transaction hash or signed message in case the provider asks for it again.
A self-custodial wallet has no operator that could receive a data request, collect customer details or block a payment. The EU therefore places all Travel Rule obligations on the regulated providers that interact with such wallets. From 10 July 2027, the EU AML Regulation will also prohibit CASPs from keeping anonymous accounts, but it does not ban self-hosted wallets themselves.
For traders, freelancers and Web3 businesses, the Travel Rule turns every withdrawal into a transfer that has to be documented. A trader moving funds between two exchanges must enter the recipient's details; a freelancer receiving monthly payments in USDT may be asked to prove ownership of the wallet where the payments arrive; a Web3 company paying contributors may have to provide data for each recipient.
Travel Rule data stays between the providers involved and their regulators; it is not published on the blockchain. Freelancers should keep invoices showing who paid them and for what, and companies should keep contracts and payment records that explain regular flows. Clear records keep compliance questions short.
Businesses that move larger sums, such as treasury transfers or institutional crypto transfers between exchanges and custodians, should agree in advance which messaging network both providers use and keep source-of-funds documents ready.
| Transfer type | Main information or check | Typical user action |
|---|---|---|
| CASP to CASP | Full sender and recipient data, any amount | Enter accurate recipient details |
| CASP to self-hosted wallet | Recipient information; ownership check above €1,000 | Prove wallet ownership if asked |
| Self-hosted wallet to CASP | Sender information; ownership check above €1,000 | Confirm the wallet is yours or name the sender |
| Self-hosted to self-hosted | No Travel Rule obligation | None, although the funds may be checked later when deposited |
Most Travel Rule holds are caused by avoidable mistakes on the user's side:
Important:
ABF Swap is operated by ABF Trade Connect (Pty) Ltd, a company registered in South Africa, which states that it is authorised by the FSCA under licence No. 52818. ABF Swap is not authorised by the FCA in the UK or as a crypto-asset service provider under MiCA in the EU. As a South African crypto asset service provider, it is subject to the Travel Rule under FIC Directive 9, which has applied since 30 April 2025.
ABF Swap processes crypto-to-fiat withdrawals, and ABF Swap describes its wallet as a self-hosted crypto wallet. Whether a wallet counts as self-hosted under the Travel Rule depends on who controls the private keys, so a sending exchange may classify transfers to it differently. Before you execute a compliant crypto swap or withdrawal, check the supported asset, network, destination details, rate and fees. Read ABF Swap's terms of transfership and Terms of Use before using the service.
The Travel Rule is a requirement for crypto-asset service providers to collect the names and account details of the sender and recipient of a transfer and share them with the provider at the other end. It comes from FATF Recommendation 16 and has applied to crypto transfers in the EU since 30 December 2024.
Yes. In the EU, transfers between CASPs must carry full sender and recipient information whatever the amount. The €1,000 threshold applies only to transfers to or from self-hosted wallets, where amounts above it require the provider to check that the wallet belongs to its customer.
When you send crypto to or receive it from your own wallet, the exchange collects the originator and beneficiary information and keeps the transfer identifiable. For more than €1,000, it must also assess whether you own or control the wallet, usually through a message signature or a small test transfer.
FATF expects providers to identify the counterparty and apply risk-based checks when it cannot receive Travel Rule data. EU CASPs may ask for more information about the recipient, delay the transfer or refuse to send funds to an unidentified or unregulated provider, depending on their assessment of the risk.
Ask the exchange which information is missing, then provide it: usually the recipient's or sender's full name, the provider involved, or proof that you own the wallet. Keep transaction hashes, exchange statements and invoices ready. If the receiving provider cannot accept the data, the funds may be returned instead.
ABF Swap's operator is a South African crypto asset service provider, so it applies the Travel Rule under FIC Directive 9, which requires verified sender and recipient data above R5,000 and minimum data below it. Check the destination details and the network before confirming any transfer, and respond promptly to information requests.
This article is for general educational purposes and does not constitute financial, investment, legal or tax advice. Cryptoassets are high-risk, their value can fall to zero, and transfers are generally irreversible. In the UK, cryptoassets are generally not protected by the FSCS, and you may not be able to complain to the Financial Ombudsman Service; in the EU, they are not covered by deposit guarantee schemes. Rules on cryptoasset services differ by country, so check whether any provider you use is authorised to serve customers where you live.





Start earning passive income from every transaction your invitees make with one of the highest rewards on the market!