A platform can ask for Travel Rule information when you transfer crypto to or from a personal, self-hosted wallet. The absence of another exchange on that side does not automatically remove the platform’s information duties. Establish which provider and jurisdiction govern the transfer, then distinguish identifying the parties from proving control of an address and from a separate source-of-funds review.
The transfer context comes before the form
Self-hosted describes an arrangement in which the user, rather than a custodial service, holds the private keys. It does not identify who owns every address reached from the wallet application. The same person may use a custodial exchange account and a personal wallet, while a wallet-branded application can expose different products. Answer the question about the actual destination or source, not merely the app name.
Read the platform’s current regional instructions. Coinbase’s Travel Rule explanation distinguishes regions, transfer directions and wallet types. Its practices illustrate why a procedure encountered by another customer is not automatically the procedure for your account. A familiar term such as verification can cover several tasks with different requirements and consequences.
| Transfer context | Question the platform may need to resolve | Information to establish first | Mistake to avoid |
|---|---|---|---|
| Exchange to another exchange | Who sends, who receives and which providers participate? | Actual receiving provider and beneficiary details | Calling a custodial account a personal wallet because you own the account |
| Exchange to your self-hosted address | Who is the beneficiary and is address control being assessed? | The destination address and the applicable provider process | Assuming every personal-wallet transfer needs no information |
| Self-hosted address to an exchange | Who originated the transfer and how does it relate to the account? | Actual source, sending party and the reviewed deposit | Using the exchange’s deposit address as the sender’s identity |
| A third person’s personal wallet | What relationship and counterparty information are required? | The real sender or beneficiary and whether this transfer type is supported | Selecting my wallet merely to make the form accept the request |
| Person-to-person without a CASP | Whether the particular legal regime applies to this context | Whether a crypto-asset service provider actually participates | Applying every platform form to a transfer where no platform is involved |
The table separates cases; it is not a promise that every provider offers them. If a platform’s menu does not describe your intended transfer accurately, ask for clarification before proceeding. Do not choose another provider or relationship in the form because its option produces fewer questions. Incorrect information can leave the underlying issue unresolved even if the interface lets you continue.
EU information duties and the control threshold are different
An important example is Regulation (EU) 2023/1113, applicable from 30 December 2024. Its crypto-transfer provisions include obtaining and retaining originator and beneficiary information for transfers involving self-hosted addresses. The regulation separately singles out transfers exceeding EUR 1,000 for adequate measures to assess specified address ownership or control. That threshold is not a general data-free allowance below it.
The regulation also excludes person-to-person crypto transfers conducted without a crypto-asset service provider. That exclusion describes scope, not a rule that using a personal wallet on one side removes an exchange’s duties on the other. Keep the two situations distinct. Do not turn this EU example into a worldwide prohibition on self-custody or a statement that every jurisdiction uses the same amount and procedure.
The EBA’s final Travel Rule Guidelines, published by Estonia’s financial supervisor, explain collection from the customer and approaches to assessing control. They also address circumstances involving a third person. A platform’s decision to support only certain recipient relationships should therefore be checked as that platform’s current restriction, rather than described without qualification as a universal ban in the regulation.
Know which question each request answers
The sender’s name, the recipient’s name, wallet type and participating provider identify the transfer context. A control check asks a different question about an address. A source-of-funds request concerns how assets were obtained. Completing one does not necessarily complete the others. If a deposit remains under review, ask which requirement is outstanding instead of repeating a proof that already answered another question.
Consider a fictional user, Mei. She sends from her personal wallet to an exchange and sees the transfer confirmed onchain. The exchange asks who sent it. Mei should give the true originator details through the account’s review process and keep the transaction reference. Another network transfer or a new wallet address would not answer the missing-information request about the original deposit.
A blockchain confirmation and permission to use a platform balance are different events. A receiving service can still have information or review tasks after the network includes the transfer. Do not assume an onchain success message proves that the platform collected every required field, and do not report an information hold as a network failure without checking its stated reason.
Control checks do not require giving away the wallet secret
A platform can offer supported methods for checking address control. Coinbase’s EU transfer page describes examples, including a message-signing flow and a small-deposit test. Their availability depends on the actual service and wallet. A message intended for that verification and a real transfer are different actions; inspect the request rather than approving any prompt labelled compliance.
Use the official account workflow and the exact method it accepts. Never disclose a recovery phrase or private key to a form, agent or checker. If your wallet cannot perform the proposed method, ask the platform for an accepted alternative. Do not fund an address or send a preliminary test merely because an unsolicited contact says it will unlock the process.
Transfer information is not a passport entry in a public memo
Do not put identity documents or personal identification numbers into an onchain memo to show that you supplied Travel Rule information. Use the platform’s designated secure channel. A form about the transfer and the transaction’s public data fields serve different purposes. Confirm the recipient of your information, what is necessary and where the applicable privacy notice explains its handling.
- Identify the sending and receiving services, where present, and the actual wallet arrangements.
- Read the current instructions for the provider entity and transfer direction involved.
- Supply accurate originator, beneficiary and provider information through the official process.
- If control is requested, confirm the accepted method and the specific address concerned.
- Keep the transaction and request references, and distinguish network confirmation from account availability.
- Ask which requirement remains outstanding rather than inventing a different route or paying an outside compliance agent.
For a KOT.CASH order, read how the service works and the AML policy before a simple swap. No-account exchange does not remove risk-based reviews, and suspicious activity can lead to a pause. This article does not establish KOT.CASH’s regulatory entity, Travel Rule integration or accepted control-proof methods. Check the actual request and its responsible operator instead of assuming that a procedure described for another platform is implemented here.
FAQ
Does the Travel Rule apply when a crypto transfer involves a self-hosted wallet?
A participating platform can still have information duties even though the other side is a personal wallet. The answer depends on the applicable jurisdiction, provider and transfer context, rather than the wallet label alone.
Are EU self-hosted transfers below EUR 1,000 free of information requests?
No: the regulation’s specific ownership-or-control threshold is separate from its information duties. Do not treat that amount as a general exemption or infer that a platform cannot ask questions below it.
Should Travel Rule details be written into a public blockchain memo?
Use the platform’s designated secure information process, not a public memo containing identity information. Keep the transfer reference available so the information can be linked to the correct case.
Related on KOT.CASH
Sources
- help.coinbase.com/en/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/travel-rule
- eur-lex.europa.eu/legal-content/EN/TXT/?qid=1688748082703&uri=CELEX%3A32023R1113
- fi.ee/sites/default/files/2024-11/Travel%20Rule%20Guidelines.pdf
- help.coinbase.com/en/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/send-receive-crypto-eu