When a Cross-Chain Swap Fails, Should You Wait or Refund?

When a cross-chain swap stalls, wait while its transactions are still progressing; request a refund when the route has failed or the protocol offers a clear recovery. A swap can involve several steps across separate blockchains, so a delay on one chain does not always mean the trade is lost. The useful question is what the transaction record shows, not just what the swap screen says.

What does pending mean for a cross-chain swap?

Pending can mean the source transaction is waiting for confirmations, the swap service has not yet observed it, or the destination transfer has not been sent. A blockchain explorer, a public page that shows transaction activity, can help identify which step is still moving. Check the source transaction hash first, then look for a linked destination transaction or a status update from the swap service.

On THORChain, for example, nodes observe the incoming transaction before processing it, and invalid swaps are refunded under the protocol’s rules. That illustrates why a swap may have more than one stage. Route design matters too: thor swap offers a fuller look at route choices for treasury transfers, where speed, cost and operational needs can pull in different directions.

When should you wait for the swap to finish?

Wait if the source transaction is confirmed and the service or chain still reports an active step. A destination transfer may be queued, or the service may be waiting for enough confirmations to treat the deposit as final. Starting another swap while the first is active can leave you with two transactions to track and two sets of fees.

Give the route time based on its stated estimate, but use the transaction status to guide you if that estimate passes. Refresh the service page and check the relevant blockchain records. If the source transaction never confirmed, the swap may not have started at all; the wallet’s transaction record can show whether it is pending, dropped or confirmed.

When is a refund the better choice?

A refund is more suitable when the service marks the swap failed, the protocol has issued a refund, or its documented recovery process says to request one. First check where the refund will go. Some protocols return funds to the original sender by default, while others use a refund address set in the swap instructions. A refund can also require a new transaction and may involve network fees or a wait for that chain to process it.

• Save the source transaction hash and the swap reference.
• Check the source and destination chain records for the latest status.
• Confirm the refund address and any stated fees before requesting recovery.

If the status is unclear or funds remain unaccounted for, contact the service that handled the swap with those transaction details. Do not send more funds to an address offered in an unsolicited message. For most readers, the safer choice is to wait while the transaction is visibly progressing, and pursue a refund once a failure or official recovery path is clear.