If the other platform doesn't support the Travel Rule, before sending crypto you need to confirm the receiving platform's compliance status, your wallet type, and whether the transaction amount will trigger restrictions. Checking these three things can prevent your funds from being stuck or returned.
Travel Rule requires virtual asset service providers (VASPs) to collect, verify, and share sender and receiver identity information when processing crypto transfers. If the receiving platform hasn't connected to this compliance system, they might not receive your coins, or the coins could be frozen after arrival.
Check if the Receiving Platform Is Connected to Travel Rule Compliance Network
Verify that the platform you're sending to supports Travel Rule information exchange: go to the withdrawal page and see if the sending platform lists the receiving platform's name. Or search the receiving platform's help center for "Travel Rule" or "transfer rules" to check for related instructions. Some platforms like Gemini only allow withdrawals to exchanges that have joined the TRUST compliance network. If the recipient isn't on the supported list, the withdrawal cannot be completed.
Completion standard: You have confirmed that the receiving platform supports Travel Rule-compliant transfers.
Risk reminder: Due to compliance requirements, some platforms only allow withdrawals to a preset list of supported exchanges and won't let you manually enter an unsupported exchange's name. If you find the receiving platform is not on the list, this transfer is technically impossible, and trying to submit it will be rejected.
Identify Your Wallet Type: Custodial or Non-Custodial
Figure out whether the wallet you're sending from is an exchange account or your own private wallet—each requires different verification information. Transfers to an exchange account require the recipient's legal name and address type; transfers to your own private wallet usually require a signature to prove you own the address. Completion standard: You have identified the wallet type and prepared the corresponding verification materials.
Case A: Transfer to another exchange account—requires the recipient's legal name and residential address. Some platforms also ask for the purpose of the transfer (e.g., personal transfer, investment, purchase of services).
Case B: Transfer to your own non-custodial wallet (like Ledger, MetaMask)—requires a message signature to prove wallet ownership. If the signature fails, some platforms also accept "visual proof" (recording a video of the wallet operation using another device) as an alternative verification method.
Check if the Transaction Amount Hits the Trigger Threshold
Check whether the transfer amount reaches the threshold that triggers Travel Rule verification on the receiving platform. Different jurisdictions have different thresholds—the EU and European Economic Area apply the Travel Rule to all transactions regardless of amount. Some platforms require Travel Rule verification for all deposits and withdrawals. If the amount hits the threshold, the receiving platform will demand supplementary sender information, otherwise funds could be frozen. Completion standard: You have confirmed whether this transfer will trigger Travel Rule verification on the receiving platform.
Common Reasons for Transfer Failures
The most common pitfall is assuming the other platform supports the Travel Rule—thinking every exchange can receive transfers normally, but some smaller platforms may not have joined any compliance network at all. Another issue is choosing the wrong wallet type—filling in a custodial exchange wallet as a private wallet or vice versa, causing mismatched verification info and leaving the transaction pending.
Next Steps
Before sending, go to the receiving platform's help center and look for Travel Rule-related information. If they clearly state they support it, proceed with the normal process. If you can't find any information, try a small test withdrawal first to see if a Travel Rule info input window pops up. If the receiving platform doesn't support it at all, you'll need to switch to a platform that does, or use a non-custodial wallet route.
