Crypto swap pending? Check these stages first
Find out whether a pending crypto swap is waiting for a broadcast, confirmations, routing, or delivery—and what to check before sending anything else.
A pending crypto swap can be waiting for the sending transaction, required confirmations, route execution, or the receiving service. Those are different problems. Start with the original bridge and the sending transaction reference, rather than creating a second swap or paying again.
Has the sending transaction actually left?
A wallet can show a prepared payment or an exchange withdrawal request before anything has been broadcast. Look for a transaction ID and inspect it on the correct network. An internal withdrawal reference from an exchange is not always a blockchain transaction ID.
If the exchange is still processing the withdrawal, uSwap may have no deposit to detect yet. Compare the network, receiving address, memo or tag, and final amount on the withdrawal details. Keep those details together with the bridge link.
Confirmed on-chain does not mean delivered
After broadcast, a route may wait for confirmations before using the deposit. The wallet, explorer, and receiving provider can use different thresholds. A transaction marked successful in an explorer can therefore still be waiting to become usable inside the route.
| What you can see | What it establishes |
|---|---|
| Withdrawal requested | The sending service accepted your request. |
| Transaction broadcast | A transfer was submitted to the network. |
| Deposit credited | The route can use the detected funds. |
| Output delivered | The destination transfer or product delivery completed. |
The order-tracking guide explains the stages shown on the bridge. Do not use the sending wallet’s status as a substitute for the final delivery state.
The deposit is credited, but the swap is still processing
A route may contain more than one exchange or provider action. Confirmation of the input does not complete those later steps. Check whether the bridge shows a provider wait, an active route leg, or a hold that needs action.
If there is an action, read its effect before choosing it. A re-quote changes the conditions for execution; a refund is a separate transfer with its own availability and costs. Neither is the same as cancelling an unbroadcast wallet transaction.
The bridge says complete, but the wallet looks empty
Use the output reference, not the original deposit reference. Confirm the destination network and address, then check that your wallet is synchronized and displaying the correct asset. An exchange can wait for more confirmations after a payout reaches its address.
For a product, completion means checking the delivery area rather than a crypto wallet. A gift card, hosting balance, and token payout have different delivery surfaces.
What to keep for support
Keep the bridge link private. Collect the sending transaction ID, network, amount, approximate time, and the last visible bridge stage. Use the troubleshooting checklist before sending a second payment. Never include a seed phrase, login code, or redemption secret in a public message.
Common questions
No. First locate the original deposit and read the bridge status. Another deposit creates more funds to account for; it does not make the first transfer confirm faster.
More from the blog
Cross-chain swaps explained: how intent-based routing works
A practical explainer of intent-based cross-chain swaps — what gets sent where, how the route is decided, and where the failure modes hide.
Read
After you buy a gift card with crypto: delivery, redemption, and support
What to check after funding a uSwap gift-card route: route state, the redemption artifact, issuer rules, and the safest way to ask for help.
Read
How to protect a virtual card: details, balance, history, and controls
A practical checklist for keeping a uSwap virtual card's credentials private, checking its balance and history, and using its protected controls.
Read