Crypto Sent to the Wrong Network? What Happens and What to Do
Sent USDT on the wrong network or the wrong coin to an address? Learn how TRC20, ERC20 and BEP20 mix-ups happen, the real risks, and the steps to take.
Crypto sent to the wrong network is one of the most common, and most stressful, mistakes in crypto payments. Because USDT exists on several blockchains at once, "which network should I pick?" becomes a critical question. This article explains what actually happens when funds go to the wrong network or the wrong coin is sent, which cases may be recoverable, and how to prevent these mistakes in the first place.
The short answer is that recovery is sometimes possible but never guaranteed. Prevention is by far the best strategy.
What "wrong network" actually means
USDT is not a coin that lives on a single blockchain. The same stablecoin is issued as TRC20 on TRON, ERC20 on Ethereum and BEP20 on BNB Smart Chain. These are independent networks, and USDT on one of them does not magically show up on another.
That is why exchanges and wallets ask you to choose a network when you withdraw USDT. If the recipient expects a TRON (TRC20) payment and you pick ERC20 or BEP20, the transfer never reaches the network the recipient is watching. For a deeper comparison, read what USDT is and how TRC20, ERC20 and BEP20 differ.
Address formats are your first line of defence
Fortunately, the networks use different address formats, which stops many mistakes before they happen:
| Network | Address format | Starts with |
|---|---|---|
| TRON (TRC20) | 34 characters | T |
| Ethereum (ERC20) | 42 characters | 0x |
| BNB Smart Chain (BEP20) | 42 characters | 0x |
A TRON address starts with T, while ERC20 and BEP20 addresses start with 0x. Most exchanges and wallets refuse a withdrawal when the address doesn't match the selected network, so trying to send ERC20 USDT to a T… address usually fails before anything leaves your account.
The genuinely dangerous case is a mix-up between ERC20 and BEP20. Those two share an address format, so software can't always catch the error.
Common wrong-network and wrong-coin scenarios
Scenario 1: another network sent to an address expecting TRC20
Because the address formats don't match, the transfer usually can't even be created. If it somehow went through (for example because of a rare software bug), the funds never arrive on TRON and won't appear at the MercanPay payment address. Your first point of contact is the exchange or wallet you sent from.
Scenario 2: right network, wrong coin
The address and network (TRON) are correct, but a different asset was sent, for example some other TRC20 token instead of USDT. MercanPay only supports TRX and USDT on TRON. Unsupported tokens are not matched to the invoice and are not credited automatically.
Scenario 3: right network, right coin, wrong amount
This isn't really a wrong transfer. It's an underpayment or an overpayment, and the system handles it automatically. An underpaid invoice moves to "partial" and the customer gets extra time to send the rest. With an overpayment, the full amount received is credited to your balance. See handling underpayments, overpayments and late payments.
Scenario 4: payment to an expired invoice
If a customer sends TRX or USDT to an invoice that has expired or been cancelled, relax. Those payments are still credited to your balance. On USD-priced invoices, a late TRX payment is re-priced at the current rate.
What to do with crypto sent to the wrong network
- Don't panic, and don't send again. Repeating the same mistake while "trying once more" is surprisingly common.
- Collect the details: transaction ID (TXID), sending address, receiving address, amount, the network you chose and the time.
- Look the transaction up in a block explorer. Which network did it actually happen on, and is it confirmed?
- Contact the sending side. If you sent from an exchange, talk to its support team first. Some platforms have their own procedures for wrong-network deposits or withdrawals.
- Open a MercanPay support ticket. If the payment was meant for a MercanPay invoice, create a ticket in the panel with the invoice number, the TXID and a short description. Our team will look into it.
Important: recovery of funds sent on the wrong network or in an unsupported coin cannot be guaranteed, and in some cases it's technically impossible. A support ticket gets the case reviewed. It does not guarantee an outcome.
Preventing mistakes: a checklist for your customers
As a business, the best way to reduce wrong-network risk is to give customers clear, unambiguous instructions.
- Name the network explicitly. Write "USDT (TRC20, TRON network)", not just "USDT".
- Use the hosted payment page. The MercanPay payment page shows the coin, network, exact amount, address and QR code on a single screen, so the customer doesn't have to type anything by hand.
- Remind exchange users. Most customers pay from an exchange. Tell them to choose TRC20 / TRON on the withdrawal screen.
- Mind exchange withdrawal fees. Some exchanges deduct their fee from the amount sent. Customers should make sure the full invoice amount arrives.
- Copy the amount with the button. Typos in decimals lead to underpayments.
For more on making the payment page clearer for customers, see our crypto checkout conversion tips.
FAQ
Can I send USDT over ERC20 to a TRON address?
No. TRON addresses start with T and ERC20 addresses with 0x, and most exchanges will reject the mismatch anyway. Only send USDT to a TRON address over the TRON network (TRC20).
Can I get back USDT I sent on the wrong network?
It depends on where you sent from, which network it landed on and who controls the receiving address. Sometimes recovery is possible, sometimes it isn't, and it is never guaranteed. Contact the platform you sent from first, and if the payment was for a MercanPay invoice, contact our support through the panel.
Which coins and networks does MercanPay support?
Currently only TRX and USDT on the TRON network (TRC20). Transfers from other networks or in other tokens are not processed automatically.
What if the payment arrives after the invoice expired?
As long as it was the right network and a supported coin, it is still credited to your balance. On USD-priced invoices a late TRX payment is re-priced at the current rate.
Get started with MercanPay
Cut customer mistakes with a payment page that shows the coin, network, amount and address on one screen. Apply for a MercanPay account and plan your integration with the documentation.
