What Happens If You Send Crypto to the Wrong Network on an Exchange?
If you send crypto to an exchange using the wrong network, the funds typically arrive on the exchange’s wallet but are not credited to your account. The exchange cannot automatically detect or attribute the deposit because the transaction was made on a blockchain it does not monitor for your specific deposit address. Recovery is possible in many cases, but it is not guaranteed, often involves a fee, and can take weeks or months.
Why This Happens
Centralized exchanges assign each user a deposit address for a specific cryptocurrency on a specific network. For example, you might receive a single USDT address on Ethereum (ERC-20) and a separate USDT address on Tron (TRC-20). When you send funds to the Ethereum address over the Tron network, the transaction completes on Tron, but the exchange’s monitoring system is watching the Ethereum blockchain for that deposit. The funds end up in a wallet the exchange controls, but the exchange has no immediate way to link them to your account.
What the exchange sees
The exchange’s automated deposit system checks incoming transactions on the expected network for each address. A wrong-network deposit appears as an unexpected incoming transaction to a wallet that may or may not be monitored for that blockchain. The funds sit in a wallet the exchange holds, but they are not credited to any user. The exchange’s support team must manually investigate to identify the sender and verify ownership.
Can you recover the funds?
Recovery is possible but not guaranteed. Several factors determine whether the exchange will help:
-
Network compatibility: Some blockchains are structurally incompatible. Sending BNB from BNB Smart Chain to an Ethereum address is recoverable because both use the same address format and the exchange controls the private key. Sending Bitcoin to an Ethereum address is almost certainly lost because address formats are fundamentally different.
-
Exchange policy: Each exchange sets its own recovery rules. Some offer a standard recovery service with a flat fee. Others handle it case by case. A few exchanges will not attempt recovery at all.
-
Wallet control: The exchange must control the private key for the destination wallet. If the deposit landed on a blockchain where the exchange does not hold the wallet, recovery is impossible.
-
Time: Recovery can take anywhere from a few days to several months, depending on the exchange’s workload and the complexity of the investigation.
Typical Recovery Process
If you make this mistake, follow these steps promptly:
-
Stop all other actions on the exchange. Do not make additional deposits or withdrawals until the issue is resolved. This avoids complicating the investigation.
-
Open a support ticket immediately. Provide the transaction hash (TXID), the sending address, the receiving address, the network used, and the intended network. Attach screenshots of the transaction details.
-
Provide proof of ownership. The exchange will need to confirm you control the sending wallet. This may involve signing a message with the sending wallet’s private key or providing a small test transaction from the same address.
-
Wait for investigation. The exchange’s technical team will locate the funds on the unintended blockchain and verify they can be moved to your correct deposit address.
-
Pay the recovery fee. Most exchanges charge a fixed fee for this service. The fee varies by exchange and by the value involved. You will usually need to agree to the fee before work begins.
-
Receive the funds. The exchange moves the recovered cryptocurrency to your correct deposit address on the intended network. This may take additional time if the exchange must manually sweep the funds.
When recovery is unlikely
Some scenarios make recovery impossible or impractical:
-
Incompatible address formats: Sending Bitcoin to an Ethereum address or vice versa. The address format is completely different, and the funds cannot be routed.
-
Sending to a contract address on the wrong network: If the destination address was a smart contract that does not exist on the receiving blockchain, the funds may be permanently locked.
-
Exchange does not support the receiving blockchain: If the exchange has no wallet infrastructure on the blockchain where the funds landed, it cannot access them.
-
Very small amounts: Exchanges may decline recovery if the deposit value is less than the recovery fee.
How to avoid this mistake
-
Always double-check the network field when generating a deposit address. Most exchanges show the network name clearly next to the address.
-
Copy the address from the exchange’s interface immediately before sending. Do not reuse old addresses from previous deposits - networks can change.
-
Send a small test transaction first if you are depositing a large amount. Wait for confirmation that the test reached your account before sending the rest.
-
Use the same network for both the withdrawal and deposit. If you withdraw from another exchange on BNB Smart Chain, deposit to the BNB Smart Chain address on the receiving exchange.
-
Ignore auto-filled network fields in some wallets. They may default to a network that does not match your exchange deposit address.
Summary
Sending crypto to the wrong network on an exchange is a recoverable error in many cases, but it costs time and money. The exchange can retrieve the funds if it controls the destination wallet on that blockchain and if the address format is compatible. Always verify the network before confirming any transaction. If you make the mistake, act quickly and provide complete transaction details to support. Recovery is not guaranteed, so prevention is the only reliable safeguard.
Not financial advice. whitecoffeecat.lol publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.