Sent crypto on the wrong network: what to do
Check the asset, network, address, and transaction ID after a wrong-network transfer. Learn what recovery depends on and which details support needs.
If you sent crypto on the wrong network, stop sending more and identify the exact transfer. Recovery depends on which network received the funds, who controls the destination, which token was sent, and whether a supported recovery path exists. A matching address format alone does not prove recoverability.
Write down what actually happened
Open the sending wallet or exchange and record the transaction ID, selected network, token, amount, and destination address. Include the memo or tag if one was used. Then compare those details with the original bridge’s instructions.
“USDT” is not enough information. USDT on TRON and USDT on Ethereum are different network choices. Likewise, a 0x address can be used on several networks without a service monitoring or supporting every one of them.
Separate a wrong network from a missing confirmation
A transfer that has not been broadcast is still with the sending service. A broadcast on the correct network may simply be awaiting confirmations. A transfer on another network needs a different investigation, even if the explorer reports success.
| Situation | Useful next check |
|---|---|
| No blockchain transaction ID | Ask the sending service about the withdrawal. |
| Correct asset and network, still confirming | Track the existing transaction. |
| Different network or token | Keep the transaction details and inspect the bridge’s recovery options. |
| Correct network, missing memo or tag | Explain the omitted routing field to verified support. |
The asset and network guide is useful for comparing the two sets of instructions without guessing from the ticker.
What the bridge can and cannot fix
uSwap can handle some mismatches by identifying the received asset and offering a supported route, hold, or refund. That does not mean every token sent to any address can be retrieved. Provider-controlled addresses, unsupported tokens, ambiguous transactions, and already-broadcast payouts can require review or be unrecoverable.
Changing the destination in your browser does not move funds already sent to another address. Nor does making a new bridge give it control over a transfer to an older one. Keep working from the original record.
Ask for help without exposing access
Use the help options on the bridge. Provide the network, transaction ID, amount, expected asset, and what differs from the instructions. The bridge link itself can reveal private order details, so share it only through the verified support flow when needed.
Do not enter a seed phrase into a “recovery” website or pay someone who arrives in an unsolicited DM. Legitimate investigation starts with transaction details, not control of your wallet.
Before the next transfer
Open a fresh receiving screen and confirm the full network name, asset, address, and memo. Review the sending service’s final withdrawal screen as well. The troubleshooting guide covers the information to retain if the two still do not line up.
Common questions
No. Similar address formats do not establish which networks or tokens the receiving service supports or can recover.
More from the blog
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.
Read
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