Where the Travel Rule for crypto-assets comes from
The rule complements the checks users may see when a platform delays certain transfers after a deposit. The FATF extended the principles of Recommendation 16 on transfers to virtual assets. The aim is to ensure that certain information travels with the transaction between service providers.
The FATF monitors the implementation of the Travel Rule each year for virtual assets and VASPs. Its standards do not function directly as a worldwide law: countries transpose them into their own legal frameworks.
The European Union adopted Regulation 2023/1113 on information accompanying transfers of funds and certain crypto-assets. The text applies to transfers involving a provider established in the European Union under its stated conditions.
A platform may also impose broader checks because of its licence, risk policy or another jurisdiction. The screen shown to a user therefore does not always reveal which specific rule is behind the request.
What information can accompany a transfer?
For the sender, the provider collects, among other things, a name and data enabling identification under the applicable framework. Information is also collected about the recipient. The details and checks vary depending on the amount, country and parties involved.
This data is not necessarily recorded on the public blockchain. Providers exchange it through their own systems or specialised networks. The on-chain transaction retains its addresses and amounts, while personal information moves through a separate compliance layer.
A platform may ask for the name of the receiving exchange, the country or the type of wallet. It may also require the recipient to confirm receipt. Delays can occur when formats do not match between providers.
Users should read the privacy policy, including the retention period, recipients, legal basis, international transfers and rectification procedure. Anti-money-laundering compliance does not remove data-protection obligations.
Transfers between two platforms
When funds are sent from one exchange to another, the two providers may exchange Travel Rule information. The first must identify the recipient and receiving service. The second matches the data with the account being credited.
A difference in names, an unsupported address or a provider that is absent from the network being used can delay the credit. The blockchain may confirm the transfer while the platform keeps the funds under review.
Before making a withdrawal, check the network, address, memo and exact name of the account holder. A small test transaction can confirm technical compatibility, but it does not prevent a compliance check on the subsequent amount.
The criteria for comparing crypto platforms in Africa should include the Travel Rule procedure, processing times and support. A licensed provider must explain how to correct inaccurate information.
Sending funds to a personal wallet
A self-hosted wallet has no receiving company responsible for exchanging the data. The platform may therefore ask whether the address belongs to the customer or a third party. Depending on the risk and jurisdiction, it may request proof of control.
This proof may take the form of a message signature, a micro-transfer or a screenshot. A properly designed cryptographic signature demonstrates control of a key without revealing it. The seed phrase must never be shared.
A screenshot provides weak evidence and may expose the balance. Hide information that was not requested and use only the official channel. No legitimate agent should ask for a transfer to their personal address to “unlock” a withdrawal.
European regulation provides specific rules for transfers to or from a self-hosted address when a provider is involved. It does not automatically ban personal wallets. Internal procedures may nevertheless vary.
Peer-to-peer transfers
A direct transaction between two personal wallets, without a service provider, does not involve a Travel Rule message exchanged between companies. Local laws, tax rules and sanctions nevertheless remain applicable.
If one participant later deposits the funds on a platform, the platform may ask about their origin. The TXID proves an on-chain movement, not the other party’s economic identity. Keep invoices, contracts or other appropriate supporting documents.
Decentralised services make classification more difficult. An interface, operator or protocol may fall into a regulatory category depending on its functions. Users should not assume that the word “DeFi” rules out every compliance check.
A commercial payment also requires accounting records. The address, amount, date and counterparty should be reconciled without publishing more data than necessary.
Why a withdrawal remains blocked after confirmation
The platform may be waiting for information from the sending provider. An incomplete message, a different name or an unsupported country can trigger a review. Support must then correct the data or request documents.
An address linked to a sanction, hack or high-risk service may trigger a review separate from the Travel Rule. On-chain analysis tools assign a score and sometimes generate false positives.
The selected network can also create a technical problem. Sending a token on an unsupported chain is not a compliance issue; recovery then depends on the recipient’s infrastructure.
Ask support for the general reason, case number and exact list of documents required. Do not open multiple contradictory tickets. Keep records of the exchanges and the stated timelines.
The Travel Rule and data protection
Transmission creates databases containing identities linked to addresses. A leak can facilitate phishing, extortion or financial surveillance. Providers must therefore apply data minimisation, encryption and access controls.
A Travel Rule network should not distribute data to all its members. It should route it to the necessary counterparty and authenticate participants. Logging should enable an audit without unnecessarily exposing the contents.
Users can ask which data is retained and exercise their rights under the applicable law. Some information may not be erased immediately because of legal obligations.
Avoid sending documents through unsolicited email or instant messaging. Log in through the official application and check the domain. Fraudsters exploit blocked withdrawals to request identity documents.
Differences between jurisdictions
The FATF standard aims for international consistency, but thresholds, timelines and definitions differ. A transfer between two countries may encounter the stricter rule or a data incompatibility.
Some countries require providers to register, while others require a full licence. Some impose strict rules on personal wallets; others focus on platforms. Consult local authorities rather than relying on an outdated table.
In Africa, rules are evolving at different speeds. Guides on crypto in the WAEMU and crypto in the CEMAC show why a regional policy does not replace an analysis of the country and service involved.
A global platform may apply a uniform procedure to all its customers to simplify its operations. A request that goes beyond the local minimum does not therefore prove that a new national law exists.
Preparing a transfer without unnecessary delays
Check that the name on the source account matches the name on the recipient account when both belong to the same person. Select the correct provider from the list and check the network. Add the required memo.
For a personal wallet, prepare secure proof of control. A message signature should never require the private key. Consult the wallet and platform documentation.
Keep the TXID, withdrawal confirmation and supporting documents showing the origin of the funds. For a business, link the invoice, recipient and internal authorisation.
Allow extra time for an urgent payment. A fast blockchain confirmation does not guarantee immediate credit if a manual review takes place.
What to do when a request is abusive or unclear
Ask about the purpose, mandatory data and secure channel. Support should be able to distinguish between KYC, the Travel Rule, source-of-funds checks and wallet verification.
Never provide a seed phrase, private key or remote access. No regulation requires it. Also refuse to pay an “unlocking tax” to a crypto address supplied by an agent.
If the platform does not respond, use its complaints procedure, followed by the ombudsman or competent authority for the relevant jurisdiction. Document the dates and responses.
A compliant request may still feel intrusive. The appropriate response is to challenge its necessity or proportionality, not to falsify information. A false declaration may prolong the block.
Travel Rule checklist
Identify the country of the sending and receiving providers. Check the wallet type, network and account holder. Read the fields before confirming and correct accents or name variations where the interface allows it.
Use the official channel for documents. Hide information outside the scope of the request, keep a copy and note the retention policy. Enable strong authentication on both accounts.
After sending, monitor the blockchain and internal status. If the transfer is confirmed but not credited, provide the TXID and requested data to support. Do not initiate a second transfer as a test before understanding what happened to the first.
The Travel Rule brings crypto transfers closer to obligations already applied to traditional payments. It improves traceability between providers while creating privacy and interoperability challenges. A well-prepared user distinguishes between an on-chain transaction and the regulated exchange of data, protects their keys and keeps the necessary supporting documents without disclosing more than the procedure requires.
