USDT Sent but Not Received? A TRC20 Troubleshooting Guide

In short: if USDT was sent but not received, paste the TxID into Tronscan first. SUCCESS means the transfer is final and the issue is on the receiving side; FAILED means no USDT moved. On-chain TRC20 transfers settle in seconds to about a minute, so a delay beyond 10–30 minutes almost always has a specific, checkable cause.

What should I check first?

Before contacting anyone, find the transaction hash (TxID). Your wallet shows it in the transaction details; an exchange shows it in the withdrawal history once the withdrawal is broadcast (our Binance USDT TRC20 withdrawal guide shows where to find it on Binance). Paste it into Tronscan and read four fields:

1. Result. SUCCESS, FAILED (with a reason), or not found.
2. To address. Compare every character with the address the recipient gave you.
3. Token. It should be Tether USD with the contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. Tether lists TRON among its supported protocols.
4. Amount and time. Make sure it is the transfer you think it is.

Those four answers decide which branch of this guide applies. If you have no TxID at all, the transaction was never broadcast, and the problem is earlier in the process.

What does each Tronscan status mean?

TRON finalises blocks quickly, so "pending for an hour" is not a normal blockchain state on TRON. Long waits come from exchanges, processors or wallets, not from the network itself.

Why did my transfer fail, and is my USDT safe?

A FAILED result means the smart contract call reverted. No token balance changed: your USDT is still on your address, which you can confirm on Tronscan. What you lost is the fee spent on the attempt.

By far the most common reason is OUT_OF_ENERGY, where the transaction did not have enough energy and TRX to finish. It happens most often when sending to a first-time USDT holder, which on 21.10.2026 needs about 130,285 energy instead of about 64,285. Our guide to the OUT_OF_ENERGY error explains how to size energy and fee_limit so the retry goes through. For other failure codes, the TRON transaction errors reference lists them one by one.

Tronscan says SUCCESS. Why hasn't the recipient got it?

This is the most stressful case, because the sender has done everything and the recipient sees nothing. Work through these causes in order.

1. The recipient is looking at a different address. People often have several wallets or several accounts in one app. Ask them to search the exact To address on Tronscan. If the USDT is there, the funds have arrived; they are just looking in the wrong place.

2. The wallet does not display the token. Some wallets only show tokens that are enabled in the asset list. The recipient should add Tether USD (TRC20) from the official contract, not a search result with a similar name. Hardware wallet apps may also hide tokens on a TRON account that has never been activated with TRX.

3. The exchange has not credited it yet. Exchanges wait for their own confirmation threshold and run deposit checks before crediting. This usually takes minutes, but can be longer during network congestion, wallet maintenance or a compliance review. The recipient should open a deposit inquiry with the TxID. Our overview of withdrawing USDT TRC20 from an exchange covers how exchange processing works on both ends.

4. Deposits for TRC20 are suspended on the receiving platform. Exchanges sometimes pause a network for maintenance. Funds sent during a pause are normally credited once it lifts, but check the platform's announcements.

5. A memo or tag was required and missing. For USDT on TRON most platforms do not use a memo, but some custodial services and payment gateways do. If the deposit page showed one and you left it out, the platform needs your TxID to credit you manually.

Could I have sent USDT on the wrong network?

If your wallet or exchange let you pick a network, check which one the TxID belongs to. A TRON TxID opens on Tronscan; if it does not, the transfer may have gone over Ethereum, BNB Chain or another network.

• Sent from an exchange on ERC20 or BEP20 to a TRON address. Most exchanges validate address format, so this is rare. If it did happen, contact the exchange's support.
• Sent TRC20 to a 0x address. Wallets usually block this, since a 0x address is not valid on TRON.
• Sent to an exchange deposit address for a different network. The exchange may be able to recover the funds manually, sometimes for a fee, but it is under no obligation to.

The basics of how TRC20 differs from other USDT versions are in our TRC20 explainer.

What if the "USDT" I received is fake, or I sent to a poisoned address?

Two scams produce "sent but not received" situations on purpose.

Fake USDT. Anyone can deploy a token named "USDT" or "Tether USD". On Tronscan its contract address will differ from TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, and it typically has no real market value. If someone "paid" you with it, real USDT did not arrive.

Address poisoning. A scammer sends you a tiny transfer from an address whose first and last characters match a contact's. Later you copy the address from history and send real USDT to the scammer. The transfer is SUCCESS; it just went to the wrong place. Always copy addresses from the recipient directly and compare the full string.

Neither case can be undone on-chain. The fix is prevention.

How do I avoid this next time?

• Send a small test first for any new recipient or large amount, especially to an exchange.
• Get the address from the source, not from transaction history or a chat message forwarded several times.
• Confirm the network with the recipient before sending, in writing.
• Budget energy for a first-time holder so the transfer does not fail with OUT_OF_ENERGY.
• Save the TxID for every important transfer; it is the one piece of evidence every support team will ask for.

For the full sending process, including address checks and fee planning, see our step-by-step guide on how to send USDT TRC20.