Why a Cross-Chain Transfer Can Stay Pending

A cross-chain transfer can remain pending after its source-chain transaction is confirmed because the destination transaction or later settlement has not finished. The status depends on the route: a bridge may wait for confirmation, a relayer to deliver funds, or a protocol to settle records across chains.

What does pending mean on a cross-chain transfer?

Pending means the transfer has not reached the completion state reported by the bridge or tracker. It does not, by itself, show whether the source transaction failed or the destination delivery is delayed.

Bungee’s legacy API exposes separate source and destination transaction statuses, so a confirmed source transaction does not necessarily mean the destination step is complete. Across’s documentation uses “pending” for a deposit submitted but not yet filled by a relayer, illustrating why the same label can describe a particular stage rather than the whole transfer.

Why can destination delivery take longer?

Routes use different mechanisms. Some wait for source-chain confirmations before acting; others rely on a relayer or liquidity provider to send the destination asset, then reconcile that advance later. A chain’s congestion, the route’s confirmation requirements, and destination execution can all affect timing, so there is no single wait time that applies to every transfer.

The selected route also determines which token arrives and what steps follow the source transaction. For a closer look at route trade-offs, read this guide to compare Bungee bridge routes by trade-off. A quoted delivery estimate is useful for comparing options, but it is not proof that a pending transfer has failed.

What should you check while it is pending?

Start with the transaction hash and the route’s status page. Check the source chain’s explorer for the transaction result, then check the destination chain using the destination hash if one has appeared. A wallet may show only the source transaction or may not refresh the destination balance immediately.

• Source status: Confirm whether the source transaction succeeded, failed, or is still awaiting confirmation.
• Destination status: Look for a destination transaction or a tracker update that says funds were delivered.
• Route details: Match the source and destination networks, token, and recipient address to the transfer you made.
• Timing: Compare the elapsed time with the route’s estimate and status guidance; if it has passed, use the bridge’s support or tracking process.

Do not submit the transfer again just because the destination balance has not changed. First establish whether the original source transaction succeeded and whether the bridge reports delivery, expiry, or another next step. Sending a duplicate can create a second transfer rather than speed up the first.

When is a pending transfer complete?

Treat the transfer as complete when the route’s tracker reports completion and the destination chain shows the resulting transaction or funds at the intended address. Some protocols distinguish delivery from final settlement; Across’s tracking documentation, for example, separates a relayer fill from later refund or expiry states.

If the tracker shows a failed source transaction, a completed destination delivery, or an expired transfer, follow the route’s stated process for that status. Otherwise, keep the original hash and route details handy and wait for the tracker’s next update.