What Happens When a Cross-Chain Swap Is Delayed?

Cross-chain swaps settle across separate networks, so a delay can mean the destination side has not finished its part. Your source transaction may already be confirmed while the swap waits for a relayer, destination-chain confirmation or another settlement step.

A delay does not by itself mean your funds are lost, but it does mean you should check the transaction before sending it again.

Why can a cross-chain swap take longer?

A swap can wait because the source chain is busy, the destination chain is slow, or the service has not yet matched and completed the transfer. Some routes rely on a relayer to send funds on the destination chain before it later settles the source-side transaction; others use different mechanics.

On Across, for example, a relayer may fill a transfer using its own capital, with protocol settlement happening later. If that fast fill does not happen, a slower fallback or refund process may apply. For a route example, see how AcrossBridge turns Solana USDC into Ethereum ETH.

The quoted time is an estimate, not a guarantee. Network congestion, confirmation requirements, low relayer incentives or limited liquidity can all affect how long the route takes.

What happens to funds while a swap is pending?

Usually, the source transaction is either still confirming or has completed while the transfer awaits its destination action. The exact custody and settlement path depends on the bridge: a service may hold funds in a contract, use liquidity advanced by a relayer, or combine steps.

Check the status using the source transaction hash or the bridge’s deposit tracker. A status such as “pending” means the process is still underway; “filled” means the destination transfer was made, while “expired” may mean a refund process has started.

• Pending: Wait and check again after the source transaction is confirmed.
• Filled: Look for the destination transaction and confirm the received token and amount.
• Expired or refunded: Follow the bridge’s status page to see whether funds are being returned or have arrived.

A refund may take longer than the original transfer. On Across, an expired deposit can go through bundle settlement and additional bridge steps, so funds may not return immediately.

What should you do if a cross-chain swap is delayed?

First, confirm the source transaction on its network’s block explorer, then check the route’s own tracker for its current status and destination transaction. Compare the wallet address, token and amount shown there with the swap you intended to make.

Do not submit the same swap again just because the destination balance has not appeared: the first transfer may still complete, leaving you with two transactions. If the tracker shows a failure or refund in progress, follow the service’s stated recovery steps and wait for a confirmed outcome before starting another swap.

For most users, the practical rule is simple: verify the source transaction, track the bridge status, and only retry once the first transfer is clearly failed or refunded.