📝 Sent USDT on the wrong network? Check the transaction and who can help
USDT missing or sent on the wrong network? Check the TXID, address and chain, then follow the right path for a self-custody wallet or receiving platform an
Tags: usdt, wrong-network, transaction-evidence, support
If you sent USDT and the recipient cannot see it, do not make another transfer to test a fix. Open the transaction history in the wallet or platform you sent from. Save the transaction ID (TXID or hash), actual network, asset, destination address, amount and time. Those details help distinguish a transfer awaiting confirmation from one recorded on a network the recipient's app does not display, or one sent to an address you do not control.
A successful block-explorer record means the transfer was recorded on that network. It does not prove that a receiving platform supports or has credited the deposit. A confirmed on-chain send generally cannot be canceled by the sender. Coinbase's sending guide explains that limitation. MetaMask's guidance explains why some transfers between compatible networks may still be accessible to the wallet owner.
First check whether the network is the problem
Copy the TXID from the original transaction record. Open a block explorer for the network shown in that record, rather than the network you expected to use. Check the transaction status, destination address, token, amount and confirmation time. If it is pending or failed, start with the sending provider; do not ask the recipient to search for an on-chain deposit that has not completed. If it succeeded, compare its details with the deposit instructions the recipient generated for this transfer.
| What you find | What to do next |
|---|---|
| No TXID yet, or a pending status | Check the withdrawal status with the sender and ask which stage it has reached. Do not assume it was broadcast. |
| Successful TXID, with address and network matching the receiving instructions | Check confirmation requirements, the minimum deposit and the recipient's deposit status. If still missing, submit the transaction reference to the receiving provider. |
| Successful TXID, but a different network from the receiving instructions | Determine who controls the destination address: the owner of a self-custody wallet or a platform holding the keys. |
| A different destination address | Treat this as a wrong-address problem, not merely a display problem. Contact the address owner if known; do not assume a platform can retrieve it. |
Binance's guide to uncredited deposits lists confirmation requirements, unsupported networks and minimum deposit amounts among possible causes. A missing balance is therefore not, by itself, proof of a wrong-network transfer. For help assembling evidence, see the iCashy transaction troubleshooting guide.
Who controls the destination address?
A self-custody wallet whose keys you control: On some EVM networks, such as Ethereum and BNB Smart Chain, the same 0x address may be controlled by the same wallet across both networks. The token may sit on the network actually used while the wallet app shows a different one. Inspect the address on the correct network's explorer, then follow your wallet provider's official instructions to display that network and token. Do not add a token through an unknown link or enter your recovery phrase into a “checker” or “recovery” site. MetaMask distinguishes EVM-compatible networks from other networks; a similar-looking address alone does not establish ownership.
An exchange or another custodial deposit provider: That provider controls the destination keys and its deposit-crediting rules. Contact the receiving platform through its official support channel. Give it the TXID, actual network, destination address, asset, amount and time, plus a copy of the receiving instructions if available. Ask whether it supports that token on that network and whether it has a formal review process for an incorrect deposit. Some providers offer limited recovery for eligible cases; others cannot recover it. Policies are provider-specific. For example, Coinbase's troubleshooting page warns that it cannot recover some wrong-network sends, while its asset recovery service covers only specified assets and networks.
Someone else's self-custody wallet: Share the TXID, actual network and destination address through a channel you already trust. Ask the recipient to inspect their wallet or contact its provider. If they control a compatible wallet, they may be able to display the token. If they deposited through an exchange, they need to contact that exchange. You cannot force a return transfer, and a third party cannot extract keys it does not hold.
A non-compatible address or smart contract: Do not rely on a generic verdict such as “always recoverable” or “always lost.” The outcome depends on the actual chain, how the address was derived, who controls its keys and what the contract or custodian can do. MetaMask's wrong-destination guide explains why non-EVM transfers and deposits into contracts may be unrecoverable.
What to send support, and what to keep private
You can adapt this description for the receiving provider's official form:
I sent [amount] USDT on [date, time and time zone] from [wallet or platform] over [actual network] to [full destination address]. The TXID is [hash], and the block explorer shows [successful/pending/failed]. The receiving instructions showed [asset, network and address]. The balance has not appeared in [account or wallet]. Please confirm whether this deposit path is supported, whether a review is available, and what official requirements or fees apply before I take another step.
Attach the transaction record and receiving instructions if the official support channel requests them. Never provide a recovery phrase, private key, password, one-time code or unrelated account data. If this transfer was an iCashy deposit or withdrawal, use the iCashy support center to ask for a review of the iCashy-side record and include the TXID. iCashy cannot intervene in a transfer made entirely between wallets or platforms it does not operate.
Before sending USDT again
Start from the recipient's current deposit page. Select USDT and the network together. Compare that network with the one selected on the sending screen, then check the entire address rather than a few characters. Several EVM networks use 0x addresses; the prefix does not tell you whether to choose ERC-20 or BEP-20. Review the provider's current minimum deposit, fees and any extra required information, then read the final send summary before confirming. A small test transfer can reveal some mistakes if the recipient accepts it and the fees make sense, but it cannot guarantee that a later transfer will arrive. Wait until the test is actually credited before sending more. Binance's deposit instructions stress matching the sending and receiving networks rather than choosing one merely because its fee is cheaper.
If someone contacts you privately and offers to “recover USDT” for a transfer fee or your recovery phrase, stop. Use only the official channel of the provider that controls the destination address. The FTC's recovery-scam warning explains how scammers target people who have already lost money.
FAQ
Can USDT sent on the wrong network be recovered?
It depends on the actual network and address, who controls the destination keys, and the receiving platform's policy. Start with the TXID and identify the custodian. A recovery feature at one platform does not establish eligibility for your transfer, and there is no universal success rate.
Why does the TXID show success while the USDT is missing?
Success means the transfer was recorded on the network used. The wallet may not display that network or token, or a platform may require confirmations, use a different supported network or set a minimum deposit. Compare the send record with the receiving instructions and contact the recipient's provider if it remains uncredited.
Does a 0x address mean I should use ERC-20?
No. Multiple EVM networks use that address format. Ask the recipient for the network name shown on the current deposit page. Do not infer it from the address prefix or a previous transfer.
Can iCashy cancel a confirmed USDT transfer?
Do not assume it can. For an iCashy transaction, support can review its own record and identify the relevant next step. iCashy cannot cancel a confirmed transfer between external wallets or platforms whose keys it does not control.
Should I enter my recovery phrase into a tool that promises to show the token on another network?
No. Do not enter it on a website, in a chat or in a tool sent by a stranger. Use your wallet provider's official instructions to check supported networks. Anyone with the phrase can control the wallet; support does not need it.
Whom should I contact if I sent to an exchange address?
Contact the receiving exchange through its official app or website, with the TXID, network, address and amount. The sending provider can supply proof or explain the withdrawal status, but it cannot credit another exchange account.
Should I pay a recovery fee requested in a Telegram message?
No. Check with the platform's official support channel whether it has an eligible recovery process and disclosed fees. Do not send funds to an address given in a private message or share wallet secrets.