When a crypto transfer is held for a Travel Rule check, it can be in one of three materially different states: the sending platform has not broadcast it, the blockchain transfer is confirmed but the receiving platform has not credited it, or a provider is waiting for originator, beneficiary, institution, or wallet information. Identify the state before taking action; do not resend, split, reroute, or change networks to evade the review.

Pause before retrying.

Key Takeaways

Preserve the platform reference, transaction ID if one exists, asset, network, address, amount, timestamps, notice, and case number.

Check the blockchain state independently without assuming that “pending” means one thing.

Answer only through a self-opened official app or website and provide truthful minimum-required information.

Do not promise yourself a release time: law, counterparty response, risk review, and provider queues differ.

Never pay an unlock fee or disclose a password, MFA code, seed phrase, or private key.

Use the online security guide to secure the email and account channels involved in the case.

When a crypto transfer is held for a Travel Rule check, at which stage is it?

Evidence	Likely state	Safe next action
No transaction ID; exchange says reviewing	Not yet broadcast or internal hold	Ask whether cancellation is available; do not resend
Transaction ID exists but has no confirmations	Network submission or fee issue	Follow the provider's transaction status guidance
Confirmed on-chain; destination balance absent	Receiving-side credit or compliance review	Give the receiver the transaction ID and case reference
“Action required” asks party or wallet details	Travel Rule information incomplete	Verify request in the authenticated account and answer truthfully
Rejected or returning	Provider has chosen an outcome	Ask for return method, reference, and any required next step
Message exists only in email or chat	Possible phishing	Stop and independently contact official support

The Travel Rule overview defines the parties and data. A general pending withdrawal guide is useful only after you separate an ordinary operational delay from a Travel Rule request.

Step 1: Freeze a clean evidence record

Record the exact status text and take a dated screenshot. Save the exchange transfer ID, blockchain transaction ID, asset, network, amount, fee, sending and destination addresses, memo or tag, initiation time with timezone, and every case number. Keep the original notice and note whether it also appears in the signed-in account.

Do not edit screenshots or combine separate attempts into one timeline. Redact unrelated balances, transactions, account numbers, and identity documents before sharing, when the provider permits redaction. Keep originals privately in case a formal review needs them.

Step 2: Verify whether the transfer was broadcast

Copy the transaction ID from the authenticated platform and inspect it with a reputable explorer for the correct network. Match the asset, network, amount, destination, and time. Do not rely on a search-engine advertisement for an explorer, and never connect a wallet just to view a public transaction.

If there is no transaction ID, ask the sender whether the transfer remains internal and whether canceling is possible. If it is confirmed, contact the receiving provider with the ID. A confirmation does not force an exchange to credit an account when required information is missing; equally, a compliance label does not prove that a transaction was broadcast.

Step 3: Authenticate the Travel Rule request

Open the provider from a bookmark, typed domain, or known app. Check its message center and transfer details. Compare the request with the saved reference. A legitimate workflow may ask whether the counterparty is a person, company, exchange, or self-hosted wallet and may ask for originator or beneficiary details.

Stop if the message asks you to move funds to a “verification wallet,” install remote-access software, reveal recovery words, share an MFA code, or pay a release charge. Report the message through verified support. Do not let urgency turn an unverified request into an identity-data breach.

Step 4: Identify which Travel Rule field is missing

Read the provider's error and ask for the field category if it is unclear. Common categories include legal name, entity type, residential or registered address, country, counterparty institution, wallet type, and proof of control. Enter only facts you can verify. A nickname is not a legal name, and the owner of an exchange account is not necessarily the operator of the exchange.

If the beneficiary form rejects otherwise truthful data, use the beneficiary information rejection guide. If the request concerns a self-hosted address, use the wallet ownership proof guide.

Step 5: Submit a minimal, traceable response

Use the in-account form or authenticated case. Include the transfer reference and answer the requested fields without adding unrelated documents. If uploading evidence, confirm the accepted file type and redact unrelated information when allowed. Save the submission confirmation, filename, timestamp, and case number.

Do not send different versions to multiple agents. If you made an honest error, correct it through the documented route and explain the correction. Never invent an address, alter a statement, choose a supported exchange that was not involved, or describe someone else's wallet as your own.

Step 6: Ask for a status, not a guarantee

Ask whether the transfer is awaiting your information, a counterparty response, internal review, return processing, or a technical action. Ask whether any further item is required and how updates will appear. The EU framework permits covered providers to decide, under risk-based procedures, whether to execute, reject, return, or suspend certain transfers with missing information.［1］ The EBA guidelines develop that handling within the EU; they do not impose one consumer deadline on every exchange worldwide.［2］

Kraken describes provider-specific UK procedures in which some deposits may be held pending required Travel Rule information.［3］ Treat that as an example, not a promise about another platform. Support queues, legal regimes, counterparty messaging, and transaction states can all change timing.

Step 7: Escalate with the same facts

If the published support interval passes, reply in the existing case instead of opening many duplicates. Provide a concise timeline, transaction ID, status, prior submission confirmation, and the precise unanswered question. If value has been returned, request the return transaction or payment reference before sending again.

For a material amount or prolonged unresolved restriction, consider qualified legal or financial advice in your jurisdiction. Preserve records for complaints or dispute processes. Do not threaten staff, post identity records publicly, or trust unsolicited “recovery” accounts.

What not to do while a transfer is held

Do not resend the same transfer, switch chains, split the amount, change IP location, use another person's account, or mislabel a self-hosted wallet as an exchange. Those actions do not answer the missing information and can create duplicate losses or a broader review. Do not cancel unless the platform confirms that cancellation is available and explains the result.

Summary

Separate not-broadcast, on-chain confirmed but uncredited, and information-pending states.
Preserve one complete evidence set and authenticate the request independently.
Correct truthful information through the official case; never fabricate a beneficiary or wallet relationship.
Ask what is pending and what evidence remains, without relying on a release estimate.
Avoid repeat transfers, evasion, wallet-secret disclosure, and recovery scams.

Frequently Asked Questions

How long does a Travel Rule check take?

There is no reliable universal duration. The provider, jurisdiction, counterparty response, transaction state, and review type determine timing.

Should I resend if there is no transaction ID?

No. Ask whether the first instruction is still pending or can be canceled. Resending can create a duplicate transfer.

What if the transfer is confirmed on-chain?

Give the receiving provider the transaction ID and its matching details. Confirmations prove network movement, not automatic account credit.

Can I split the transfer below a threshold?

Do not split or structure transfers to avoid checks. It may trigger additional review and can violate law or provider terms.

Why is the exchange asking about my wallet?

It may need to classify the counterparty or verify control under applicable rules. Use only its documented, authenticated method.

Can support ask for my seed phrase?

No legitimate ownership or Travel Rule check requires your seed phrase or private key. Stop and report such a request.

Can a VPN release the held transfer?

No. A VPN cannot provide missing compliance data, prove identity or wallet control, alter records, or release the transfer.

What if the exchange gives no detailed reason?

Ask for the status category and permissible next step. Providers may be limited in what risk information they disclose, so preserve the response and consider formal complaint routes.

Disclaimer: This article is for general informational purposes only and is not legal, financial, investment, tax, or platform-specific advice. Requirements, timelines, and outcomes vary by provider and jurisdiction.

Used on its own, a VPN cannot authenticate a compliance request, provide required records, or make a platform release a transfer.

Sources

EUR-Lex — Regulation (EU) 2023/1113: https://eur-lex.europa.eu/eli/reg/2023/1113/oj
EBA — Travel Rule Guidelines: https://www.eba.europa.eu/sites/default/files/2024-07/6de6e9b9-0ed9-49cd-985d-c0834b5b4356/Travel%20Rule%20Guidelines.pdf
Kraken Support — Updates to Crypto Transfer Procedures for UK Clients: https://support.kraken.com/articles/updates-to-crypto-transfer-procedures-for-uk-clients

Sources checked 12 September 2026.

Related articles:

Crypto Transfer Is Held for a Travel Rule Check