How to Recover Funds After a Cross-Chain Swap Reverts

Recovering funds after a cross-chain swap reverts starts with identifying where it failed: a source-chain transaction that reverted, a message still in transit and a failed destination swap each have different recovery paths. Check the source transaction on its chain explorer and the route’s status page before retrying.

Cross-chain routes pass instructions and, in some designs, tokens between separate blockchains; a swap can therefore show different statuses on each side. For the broader messaging model, see how omnichain swaps connect chains. The route’s own status and recovery instructions determine what to do with a specific transfer.

How can I tell where the swap failed?

Compare the source transaction with the destination message record. If the source transaction reverted on-chain, the swap did not complete its source-side actions; if it succeeded but the destination record is pending or failed, the route may still need to deliver, retry or refund the transfer.

Use the transaction hash or message identifier shown by the swap interface to find both records. A wallet’s “failed” label alone may not distinguish a reverted source transaction from a destination execution problem, and a submitted transaction can remain pending before its final status is known.

What should I do if the destination swap failed?

Follow the route’s status page for its stated next step. Some messaging systems allow a failed destination execution to be retried after the cause is fixed; other routes specify a refund or recovery process. A retry may require a separate transaction and destination-chain gas, so check the route’s instructions before signing.

Keep the source hash, message ID, destination chain, token and amount together. If the route provides a recovery form or support channel, those details let its operator locate the transfer; never share a seed phrase or private key as part of recovery.

When is it safe to submit the swap again?

Submit another swap only after the original route record shows a terminal outcome—completion or refund—or the route’s instructions explicitly say a retry is safe. A pending message may still execute, and a second submission could create a separate transfer rather than recover the first one.

• Source transaction reverted: verify the on-chain status, then check whether the wallet still holds the input tokens.
• Source succeeded, destination pending: wait for the route’s stated processing window and monitor its message status.
• Destination failed or funds are unaccounted for: use the route’s documented retry or refund path and keep the transaction records.

The route’s status page is the final record to check: wait for its completion, refund or retry instructions before making another swap.