Why do cross-chain swaps sometimes fail after I send my coins

05 September 2026

The swap fails because the service cannot complete the second half of the trade - sending you the destination coins - even though it received your original coins. This happens for three main reasons, each rooted in the mechanics of moving value between blockchains that do not talk to each other.

When you initiate a cross-chain swap, you are not actually sending coins from chain A to chain B. Instead, you send your coins to an address the service controls on chain A. The service then sends you an equivalent amount from its own reserves on chain B. This two-step process depends on the service being able to match incoming deposits with outgoing payments at roughly the same time. If anything breaks that match, your coins arrive but you never receive the swap.

Reason one: the service runs out of liquidity on the destination chain. The provider must hold inventory of the token you want on chain B. If that inventory is depleted - perhaps because many users swapped the same direction at once, or the provider did not replenish in time - it cannot pay you. Your deposit sits confirmed on chain A while the service waits to buy or borrow more destination tokens. Some services let you cancel and get a refund at this point. Others do not, and you must contact support.

Reason two: the destination token's contract has a fee or a transfer restriction. Certain tokens deduct a small percentage on every transfer, or they blacklist specific addresses. If the service tries to send you a fee-on-transfer token, the amount that arrives may be less than what the swap quote promised. The service's automated system detects a mismatch and may halt the outgoing transaction. Similarly, if the token contract has a blocklist that includes the service's hot wallet, the transfer fails outright.

Reason three: the destination network is congested or the gas price spikes. The service submits the outgoing transaction on chain B using an estimate of the required fee. If network traffic surges after you send your coins, the transaction may get stuck or run out of gas. The service can resubmit with a higher gas price, but some automated systems have a fixed retry budget. After a few attempts, they mark the swap as failed and your deposit is stuck pending manual review.

A less common variant: the service's quote expired while you were sending. Cross-chain swap quotes are time-limited because crypto prices and network conditions change. If you take too long to send your coins - say, you waited for a low-fee window on chain A - the service may no longer honor the original rate. It might still accept your deposit but then refuse to pay out, claiming the price moved against it.

What you can do. Before you send, check the destination token's contract for transfer fees. Sites like Etherscan or BscScan show the token's "tax" in its read contract functions. Also, send a small test amount first. If the swap fails, contact the service's support with the transaction ID from the sending chain. Do not send more coins to "fix" a stuck swap - that almost always makes things worse.

For a broader understanding of how this all fits together, read the hub page on swapping crypto across chains. It explains the core trade-off: no bridge, no custody, but also no guarantee that the service will always have enough of the token you want on the other side.

Back to trust wallet