What to do when a cross-chain transfer fails to arrive

A cross-chain transfer that fails to arrive may still have completed on the source chain, so check its status and recovery path before sending again. A bridge moves assets or messages between blockchains, which do not share one transaction system. A route can therefore succeed on one chain and stall on the other. The first task is to find out which step failed.

Each route handles that gap differently. Some lock tokens on the source chain and release matching tokens on the destination; others use liquidity, meaning funds already available there. For a fuller explanation of how routes and their providers can differ, see this bungee bridge explainer. Those differences matter because a refund depends on the route’s own rules.

Does a failed arrival mean the funds are lost?

No: a missing destination transfer does not by itself show that the source transaction failed or that the funds are lost. Check the source transaction in the wallet or chain explorer, a public tool for viewing on-chain activity. If it is pending, the network may still be processing it. If it is confirmed, look for a destination transaction or a route status showing where the transfer stopped.

A transfer can wait for a relayer, a service that carries transaction data between chains, or fail because the destination action could not complete. The route may also have a minimum amount, token, or network requirement. A status page can narrow down the problem, but it does not replace the transaction record on each chain.

How does a bridge refund work?

A refund returns funds through the recovery process set by the route. Depending on its design, that might happen automatically, require a claim transaction, or involve support from the provider. A claim transaction is a separate on-chain action, and it may require a network fee. Some routes instead offer a retry or another recovery step.

Before acting, find the exact route and transfer record. Check:

• Whether the source transaction is confirmed, pending, or failed.
• Whether the destination transaction exists or the route reports a delay.
• What recovery options the route lists for that specific transfer.
• Whether a claim or retry needs a fee, and which wallet and network it uses.

When should you retry a transfer?

Retry only after you understand what happened to the first transfer. If it is still pending, a second send could create a second transfer. If the source transaction failed, check whether the wallet has already returned the funds. If the source succeeded but the destination leg failed, follow the route’s recovery instructions instead of assuming a new send will recover the first one.

Use the route’s official status page or help channel, reached from a source you trust. Never share a seed phrase or private key to claim a refund; those give control of the wallet. Keep the transaction hashes, which are public IDs for on-chain actions, and any route reference number together. They help identify the transfer if you need support.

The practical rule is simple: confirm the source result, locate the destination step, then use the recovery path attached to that route. “Failed to arrive” describes what you see, but the transaction records show what happened and which refund options remain.