If a USDT deposit is not showing up in a TRON wallet, it almost always comes down to one of five causes: the transfer was sent on the wrong network, the sender’s transaction failed, the wallet is hiding the token, the address was copied incorrectly, or the exchange has not credited the deposit yet. In most cases the funds are not lost — they are simply not on the page you are looking at.
This guide follows the exact troubleshooting order we use when a client reports a missing deposit: run the simplest checks first, and read the on-chain record before making any guesses. Every cause comes with a fix.
Quick triage table
| What you see on TronScan | Most likely cause | Jump to |
| Status SUCCESS, wallet still empty | Token hidden by the wallet app | Cause 3 |
| Status SUCCESS, exchange balance still empty | Exchange wait, or deposit below the minimum | Cause 5 |
| Status FAILED | Sender ran short of energy | Cause 2 |
| No transaction found | Wrong network, or wrong address | Cause 1 / Cause 4 |
First, check whether the transaction is on-chain
Ask the sender for the transaction ID (TxID) and paste it into the search bar at tronscan.org. For a transfer sent from a wallet app, you will find the TxID on the transaction detail page of the outgoing transfer; for an exchange withdrawal, it is in the withdrawal history.
One distinction will save you a lot of arguments: when an exchange withdrawal page says “completed”, it only means the exchange pushed the transaction out — not that the TRON network accepted it. Only the Status field on TronScan tells you what actually happened:
- SUCCESS — the network executed the transfer and the USDT moved. Skip to Cause 3 or Cause 5.
- FAILED — the transfer was attempted and reverted, and the failed attempt still burned part of the sender’s resources (our guide to checking TRON energy usage history after a transaction shows where to find that record). See Cause 2 for the usual reason.
- Nothing found — the transfer never reached the TRON network. See Cause 1 or Cause 4.
One detail here has tripped up almost everyone. At the top of a USDT transaction page, the “To” field usually shows the USDT token contract address, not your wallet address. The real recipient address appears further down, in the Token Transfer record. If you read only the header, every incoming USDT transfer looks as though the funds went to some other address. They did not.
Cause 1 — The USDT was sent on the wrong network
USDT exists on several blockchains, and those chains do not talk to each other. TRC-20 USDT lives only on TRON, and it can only arrive at a TRON address starting with T. If the sender picked the wrong network — ERC-20 (Ethereum) or BEP-20 (BNB Chain) — the tokens were sent to a different chain, and your TRON wallet will never display them.
The quickest way to settle it is to ask the sender for a screenshot of their withdrawal receipt. An exchange receipt states the network explicitly — “Network: TRC-20” or “Network: ERC-20” — and that single line resolves most disputes.
The fix: if a wrong-network transfer did happen, recovering the funds depends on the platform you were receiving on. With an exchange, support can usually credit a deposit sent on the wrong chain after verifying your ownership — have the TxID ready. With a self-custody wallet, the same private key may need to be imported into a wallet that supports that chain. Always start with the receiving platform’s official support team, and never trust a third party who offers to recover the funds for a fee. Wrong-network recovery is often possible, but the process is manual and slow — which is exactly why spending five seconds checking the network field before any transfer is worth more than every remedy in this article.
Cause 2 — The sender’s transaction failed for lack of energy
Energy is TRON’s unit of computing cost. (If the concept is new to you, our complete guide to TRON energy starts from zero.) A USDT transfer is a smart-contract call, and executing the contract burns energy. (A plain TRX transfer consumes bandwidth only; a token transfer consumes both, with energy as the main cost.) The sender pays this energy — but how much it costs depends on the recipient’s wallet.
- If the recipient’s wallet already holds USDT, the transfer costs the sender about 65,000 energy.
- If the recipient’s USDT balance is currently zero — including a brand-new wallet — it costs the sender about 130,000, roughly double.
If the sender’s energy plus the TRX they can burn falls short of what the transaction requires, the transaction reverts and the status reads FAILED. The funds never reach your address, and the sender still burns some TRX to pay for the resources that were consumed.
From an exchange, the sender will usually see the withdrawal marked as failed and the tokens returned to their account balance; from a wallet app, the failed transaction sits in the wallet’s own transaction history. In either case, your wallet is completely fine — the problem happened at the sending end.
The fix: the sender needs to rent energy or hold enough TRX before resending — and to size it, we put together a walkthrough on how to check if you have enough TRON energy for a USDT transfer. The billing tier depends on your current USDT balance, not on how long the account has existed. As soon as your address holds USDT, any later deposits to it consume energy at the cheaper tier.
Cause 3 — Your wallet is not showing the token
A USDT balance is not stored inside your wallet app. It is a row in the token contract’s own records, indexed by your address. Many wallets hide tokens you have not added manually, so your funds can already be on-chain while the app shows nothing.
The fix: open tronscan.org, paste your own address, and check the Tokens tab. If USDT appears in the list, the money has arrived and the problem is display only. Then, in your wallet, switch the network view to TRON / TRC-20 and add USDT as a token — the official contract address is TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. In most wallets the path is: Assets → Manage token list → Add custom token → paste the contract address → confirm, and the amount should appear right after. Only add tokens by contract address; names and symbols can be faked, a contract address cannot.
Cause 4 — The address was copied wrong
A TRON address is a long string starting with T, and a single wrong character sends the money somewhere else entirely. Two formatting rules let you spot a wrong address in seconds: TRON addresses start with T and are 34 characters long, while an address starting with 0x belongs to an EVM chain such as Ethereum or BNB Chain — not TRON.
Also beware of address-poisoning scams: scammers send small amounts to your address from an address that closely resembles yours. The goal is that when you later make a transfer, you copy the address from your transaction history instead of getting the correct one from its original place in your wallet — and your funds end up at the scammer’s address.
The fix: after every paste, check the first and last 4–6 characters, and always copy the address from where it was originally generated — the wallet or the exchange account page — never from a history entry. For a large transfer, ask the sender to send a small test amount first and confirm it arrives before sending the rest.
Cause 5 — The exchange has not credited the deposit yet
The TRON network itself settles quickly — about a minute, with a new block produced every 3 seconds on average. But an exchange credits the funds only after its own required number of block confirmations, which takes longer during peak periods. An on-chain transaction record and an exchange account balance are not the same thing. Two more exchange-side rules are worth knowing:
- Minimum deposit. Most exchanges publish a minimum deposit for USDT TRC-20, often around 10 USDT. A deposit below the minimum frequently arrives on-chain but is not credited automatically — recovering it usually takes a support ticket.
- Frozen funds are rare but real. Tether can blacklist an address on TRON, freezing its USDT. If a transaction shows SUCCESS but the exchange will not credit it and will not explain why after several days, ask support directly whether the transfer was flagged.
The fix: wait a reasonable amount of time first, then contact the exchange’s support with the TxID. A confirmed transaction record on TronScan is exactly the evidence they need.
FAQ
My exchange says the withdrawal is completed, but TronScan shows nothing. Where is it?
“Completed” only means the exchange released the transaction — if it truly went out, a TxID exists. With no TxID at all, the withdrawal never actually left the exchange; treat it as an exchange-side problem and chase their support. If there is a TxID but nothing on TRON, the withdrawal was sent on a different network — see Cause 1.
Does my wallet need to be activated before it can receive USDT?
No. A brand-new TRON address that has never been activated can still receive USDT — the deposit costs you nothing and needs no resources on your side. Activation only becomes necessary when you want to send from that wallet.
Receiving is free for me, but what does the sender pay?
The sender pays the transfer’s energy (about 65,000 or 130,000 depending on your USDT balance, see Cause 2) plus a small amount of bandwidth for the transaction bytes. When energy is short, the network burns TRX instead — about 6.5 or 13 TRX per transfer at the current burn price. And if you also move USDT on other chains, we compared USDT transaction fees on every major network in a separate guide.
My USDT arrived, but why can’t I send it out?
If the wallet holds USDT but no TRX, the first outgoing transfer must also activate the address, and it needs energy — about 65,000 units, or roughly 6.5 TRX burned if you hold no energy. Topping up a small amount of TRX unblocks it; renting energy is usually the cheaper route — our TRON energy rental guide shows how it cuts the cost of a transfer by 70–90%.
Sources
- TRON Developer Documentation — Resource Model and “Paying for resources”, checked September 2026 (energy burn price 100 sun; 1 TRX = 1,000,000 sun; a TRC-20 transfer consumes both bandwidth and energy, about 350 bytes of bandwidth; 600 free bandwidth points per activated account per day).
- TRON Developer Documentation — Network Parameters, Account model and address format, September 2026 (account creation fee 1 TRX, burned and charged to the sender of the activating transfer; TRON addresses start with T and are 34 characters).
- USDT TRC-20 contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON mainnet, observed September 2026 (typical energy ≈65,000 per transfer when the recipient already holds USDT and ≈130,000 when the recipient’s USDT balance is zero; USDT uses 6 decimals).
- TronSCAN transaction pages, September 2026 (Status field SUCCESS / FAILED; the header “To” shows the token contract while the real recipient appears in the Token Transfer record; block time about 3 seconds).
- Major exchange USDT TRC-20 deposit pages, checked September 2026 (most publish a minimum deposit, commonly around 10 USDT; deposits below the minimum are typically not credited automatically).
- Tether blacklisting activity on TRON mainnet, observed 2026 (Tether’s treasury can blacklist addresses, freezing USDT balances and blocking transfers to and from them).
- Tronsell.io rental desk support records, 2026 (the frequency ranking of the causes above, from the questions we handle week to week).
This article is for information only and is not financial advice. Figures are network parameters observed in September 2026 and can change through governance; minimum deposits and credit policies differ between exchanges — re-check before you size a large transfer.