How long does a failed destination swap refund take?

90 minutes to two hours is one published window for an Across bridge refund after a cross-chain swap fails. It measures that route’s refund processing time, not a universal deadline for every destination swap. Where the failure happened determines whether you are waiting for a refund at all.

Does a failed destination swap always trigger a refund?

No; the bridge may have delivered your funds even though the final swap failed. In that case, the tokens can be waiting on the destination chain in the asset that was bridged, rather than being sent back to your starting wallet.

A cross-chain swap is a sequence of steps: a source-chain transaction, a bridge transfer, then a destination-chain swap. The first step can confirm while later steps remain pending or fail, so a wallet’s single “failed” label may not tell you where the assets are. For a broader look at route design and payout paths, see manta bridge.

Check the transaction details and both chain balances before assuming a refund is on its way. If the bridge succeeded but the destination conversion did not, the bridge asset may be usable as-is or may need a separate swap, depending on the route and app.

How long can a bridge refund take?

It depends on the bridge and the recovery path. PancakeSwap’s cross-chain swap FAQ, for example, gives a 90-minute-to-two-hour window for an Across bridge failure; it describes a different, faster process for certain Relay transfers. Those are route-specific estimates, not a promise that every failed destination swap will resolve within that time.

A refund can require the provider to detect the failure, wait for a timeout or confirmation, and submit a return transaction. That transaction then needs to be included and confirmed on the chain where the refund arrives. Congestion, finality requirements and manual recovery can stretch the wait.

Also check what “refund” means for your route. It may return the bridge-step token rather than the exact asset you first sent, and it may arrive on the source chain or, after a destination-side failure, on the destination chain.

What should you check while you wait?

Use the route’s transaction status or recovery page, then verify the on-chain transactions in the relevant explorers. Look for a refund-pending state, a completed refund transaction, or a successful bridge delivery followed by a failed destination call. A pending status is not the same as a confirmed refund.

• Save the source transaction hash and the route or order ID.
• Check the destination wallet for the bridged token, including tokens that may not appear by default.
• Confirm the refund chain, token and receiving address shown by the route.
• Contact the route provider if its stated window has passed without a final status; include the hashes and order ID.

Do not submit the same swap again just because the interface looks stuck. First confirm that neither the destination delivery nor the refund completed: a delayed status can lag behind the chain, and retrying could send a second transfer.

When should you expect the funds back?

Expect the route’s stated window only if its status confirms that a refund is the recovery path. If the bridge completed and the destination swap alone failed, check for the bridged asset on the destination chain instead. The practical rule is simple: track each leg, identify the asset and chain involved, and use the provider’s own estimate for that exact route.