- 01
Identify the bridge you used
A RobinSwap transfer and a canonical Ethereum bridge withdrawal follow different processes. The official canonical withdrawal has a challenge period of about seven days and a separate claim step. That schedule should not be applied to every bridge route.
- 02
Inspect the source transaction
Open the hash from the wallet or RobinSwap activity in the source network’s explorer. If it is pending, delivery may be waiting for confirmation. If it failed, inspect the failure and balance before creating a new transfer.
- 03
Check delivery on the destination
Review the status in RobinSwap activity and any destination transaction link. Compare the receiving address, network and asset with the original quote. A completed delivery can be invisible in a wallet that is looking at a different network or has not imported the asset.
- 04
Keep the evidence and avoid a duplicate transfer
If the source is confirmed but delivery remains delayed, keep the source hash, any destination hash, route, time and request identifier shown in activity. Use the support link from the service you actually used. Do not send a second transfer to “unlock” the first. Never share a seed phrase or private key with support.
Your next step
Delivery complete but balance missing?Frequently asked questions
Does “pending” mean the funds are lost?
The label alone cannot establish that. Inspect the source receipt and delivery status. Different bridge routes have different confirmation, refund and claim processes.
Where is RobinSwap activity?
Open the app, connect the wallet used for the transfer and open the activity control. Records saved in another browser may not appear locally; the transaction hash and explorer remain useful.
Sources and review
Reviewed November 9, 2026. Steps describe RobinSwap and standard wallet behaviour; wallet labels can differ.