USDC After a Cross-Chain Swap Fails on the Destination
Cross chain swap gave me USDC instead of the token I wanted? If the bridge completed, your USDC is on the destination chain; retry the swap there.
iCrypto Editorial4 min read
If a cross-chain swap’s bridge leg completed but its destination swap failed, you keep the bridged token, usually USDC, on the destination chain; you do not get a source-chain refund.
A cross-chain route can move value in stages: an asset leaves on the source chain, crosses to the destination chain, then swaps into the token you selected. Each stage has its own result. When the transfer succeeds and only the last swap reverts, the destination address receives the bridged asset rather than the requested token.
A revert means the destination swap did not complete. One reason is that the amount the swap would deliver fell below its minimum output: the lowest amount accepted under the quote. The swap stops at that threshold, while the earlier bridge leg has already delivered its asset. That intermediate state is why the funds remain available as USDC on the receiving chain.
Bridge completion leaves USDC on the destination chain
USDC stays at the receiving address on the destination network after a completed bridge and failed swap. The wallet may not show the balance automatically, so look at the destination chain and the address that received the transfer. The token is associated with that chain; switching the wallet back to the source chain will not show this destination balance.
There are two different outcomes to distinguish when tracing a route. One is a completed bridge followed by a reverted swap. The other is an intent deposit that never gets filled. Across Protocol can refund an unfilled deposit on the origin chain after its fill deadline; that is a source-chain refund after expiry, not USDC delivered to the destination.
These cases can appear similar when the target token is missing, but the bridge status determines where to look. Jumper bridge brings bridge and swap routes together, while Across Protocol’s unfilled-deposit expiry is a separate outcome to compare against a transfer that already delivered USDC. Stargate Finance is another route name you may encounter when reviewing how assets moved between networks.
- Bridge completed, destination swap reverted: Look for the bridged token, often USDC, at your address on the destination chain.
- Intent deposit unfilled: After the fill deadline and expiry, look for the refund on the origin chain.
- Destination swap completed: The target token should be at the receiving address on the destination chain.
The distinction matters because the next step depends on the asset’s current chain. A destination balance can be swapped again there; an origin-chain refund must be located and used on its original network. Sending another transfer before identifying the first result can add cost without helping recover or swap the existing funds.
Trace the route, then swap the received token
Start with the transaction status in the route interface or LI.FI Scan. Follow the source transaction through the bridge delivery and destination swap, if shown. The key question is whether the bridge delivered the asset. If it did, locate USDC on the destination chain before taking another action.
Say you selected a token on a destination network and the route shows USDC arriving, followed by a failed swap. The USDC is the result of the completed bridge; the target token is absent because the destination swap reverted at its minimum output. Open the receiving address on that network and look for the USDC balance there.
To finish, request a fresh quote for swapping that destination-chain USDC into the target token. Quotes can change, so review the current minimum output and make sure the wallet has the destination chain’s gas token for the swap transaction. Gas is the network fee required to submit that transaction. The new quote may offer different terms from the failed attempt, and the swap still needs to meet its displayed minimum output.
Retrying only the destination swap is possible when the USDC has already arrived and remains in your wallet. You are making a new swap from the destination asset, not resubmitting the original bridge transfer. Confirm the token, network, receiving address, and quote before signing; this keeps the action focused on the funds that are already there.
Related
How do I make the received token show in my wallet?
Select the destination network and check the receiving address for the bridged token, usually USDC. If the balance is not visible in the wallet, use its option to display or import the token on that network, where available, then confirm against the route status or transaction details.
Can I retry only the destination swap?
Yes. When the bridge completed, use the received USDC on the destination chain for a new swap quote, and have that chain’s gas token ready. If the intent deposit instead remained unfilled, wait for expiry and locate its refund on the source chain.