Overview
Most delays require checking the source transaction, asset, network, and receipt before contacting support. Follow these steps in order and avoid creating a second deposit.
Troubleshoot pending confirmations, delayed deposits, and routes that have not completed.
Most delays require checking the source transaction, asset, network, and receipt before contacting support. Follow these steps in order and avoid creating a second deposit.
1. Confirm the source hash and current route receipt. 2. Check whether the source transaction has the required confirmations. 3. Verify that the exact requested asset, amount, network, and deposit address were used. 4. If unresolved, contact support with the order ID, hash, route, amount, timestamp, and screenshots.
Never share a seed phrase or private key with support, and do not resend funds unless the active route explicitly instructs you to.
Sending a second deposit; Assuming pending means failed; Omitting the source hash from a support request.
Confirm the official site, selected networks, exact asset, receiving address, current quote, and any wallet prompt before sending or signing.
Save the order ID, receipt URL, source transaction hash, route, amount, networks, and timestamp. Never save or send a seed phrase or private key.
Use the Help Center for general questions or contact support with the order ID and public transaction details for a route-specific issue.