When two regulated venues move funds between each other, a data message usually travels with the payment. It names the sender, the recipient and the account on each side. That is the travel rule in practice, and it is the reason a withdrawal can be delayed by a question that has nothing to do with the blockchain.
What the rule asks for
Frameworks that implement the travel rule require the sending institution to pass originator and beneficiary information to the receiving institution, and to keep a copy. The thresholds, the exact fields and the treatment of self-hosted wallets differ by jurisdiction, so treat any specific number you read as local rather than universal.
The principle is constant. The payment and the identity travel together, so the receiving venue can decide whether to accept the funds before they are credited.
That is a screening decision made at the door, not an audit after the fact.
What travels, field by field
Originator
Name, account number or address, and often the customer’s address. Some regimes add a national identity number or date and place of birth. The sending venue already holds this from onboarding, which is why supplying it is usually instant.
The weak field is the address. An account number at a venue is verifiable. A self-custody address is a string, and its ownership is asserted rather than proven.
Beneficiary
Name and account or address. Where the beneficiary is another venue’s customer, the receiving venue can match the name to its own file. Where the beneficiary is a self-hosted wallet, the fields are thinner and there is less to match against.
That gap is not a loophole. It is the place where manual review happens.
Why a self-custody withdrawal gets questions
A transfer to your own wallet is a payment to an unnamed counterparty from the venue’s point of view. The venue cannot verify who controls the address, so it may ask for proof of ownership, a screenshot of the wallet, a signed message, or a short statement about the purpose.
This is usually a file that needs an answer before release, not a suspicion. The practical cost is time, and the practical fix is consistency. A labelled withdrawal address, used repeatedly, gives the venue a history to look at instead of a one-off question.
Address hygiene matters here too. Our note on address poisoning covers the copy-paste failure that sends a correct payment to a lookalike destination, which then needs a very different conversation.
What “not supported” means
A message saying a jurisdiction or a destination is not supported usually describes the sending venue’s own list. Venues maintain country lists, counterparty lists and product lists, and they revise them without a public changelog.
Read the message literally. It says this venue will not send there, today, on this rail. It does not say the destination is unlawful, and it does not say another venue would refuse.
The useful follow-up is to ask which list the decision came from and whether a different rail changes it. Sometimes the answer is a network restriction rather than a country one.
The trail you keep
Save the withdrawal record at the time of transfer: amount, asset, network, fee, address and date. An explorer link is useful, but it does not name you. A venue record does.
That record is also what a receiving venue will ask for if it holds the deposit. Producing it in ten minutes is the difference between a delay and a week.
| Field | Usually collected by | What happens if it is missing |
|---|---|---|
| Originator name | Sending venue, at onboarding | Transfer held until the field is supplied |
| Originator account or address | Sending venue, per transaction | Receiving venue cannot match the payment |
| Beneficiary name | You, at the withdrawal screen | Held for clarification |
| Beneficiary address | You, per transaction | Extra ownership evidence requested |
| Purpose or relationship | Sometimes, for self-hosted wallets | Manual review, with no fixed timeline |
What to do next
Keep one labelled withdrawal address per purpose, and use it consistently. Keep the venue receipt for each transfer, not only the explorer hash. If a transfer is held, answer with the record rather than with an explanation.
Cost is the secondary issue. An ERC-20 withdrawal ran $2 to $10 in FeeEdge’s 17 August 2026 survey, above $50 in congestion, while a Solana SPL withdrawal was about 0.5 to 1 USDT. A held transfer costs more than either, in time if not in fees.
The rule does not change what a chain records. It changes what a venue must know before it credits you, and that is the part you can prepare for. The venue board lists 24 venues as of October 2026, and the methodology note explains how the columns are built.
0 comments
No comments yet — ask a question and we will answer it here.