USDT TRC20 not received even though the transaction succeeded?
TRONSCAN says SUCCESS but your USDT is still missing? A successful TRON transaction can still fail to appear at an exchange if the destination does not credit USDT on TRON, the address is wrong, the amount is below a minimum, or the platform has not credited it yet.
A TRON transfer confirms in seconds, so if the deposit is missing the cause is almost never the chain. Paste the TxID before you open a ticket.
What usually causes this
These are the common explanations for this category of problem. Which one applies to your transfer depends on your transaction, the network it used and the destination's deposit rules — that is what the check above works out.
- The destination doesn't credit USDT on TRON
- The deposit address shown was for a different network
- The amount is below the destination's minimum
- The platform hasn't credited a valid deposit yet
Where USDT is credited, by network
USDT exists on several networks and every platform picks its own subset. A transfer over a network outside that subset confirms perfectly and is never credited, which is why "I definitely sent it" and "they definitely have not received it" are both true at once.
| Platform | Networks credited | Approximate minimum |
|---|---|---|
| Binance | Ethereum (ERC20), TRON (TRC20), BNB Smart Chain (BEP20), Polygon (PoS), Arbitrum One, Optimism and Solana (SPL) | 1 USDT |
| Coinbase | Ethereum (ERC20) | 1 USDT |
| Kraken | Ethereum (ERC20), TRON (TRC20), Polygon (PoS), Arbitrum One, Optimism and Solana (SPL) | 5 USDT |
| Crypto.com | Ethereum (ERC20), TRON (TRC20), BNB Smart Chain (BEP20), Polygon (PoS) and Solana (SPL) | 1 USDT |
| Bybit | Ethereum (ERC20), TRON (TRC20), BNB Smart Chain (BEP20), Polygon (PoS), Arbitrum One and Solana (SPL) | 1 USDT |
| OKX | Ethereum (ERC20), TRON (TRC20), BNB Smart Chain (BEP20), Polygon (PoS), Arbitrum One, Optimism and Solana (SPL) | 1 USDT |
| KuCoin | Ethereum (ERC20), TRON (TRC20), BNB Smart Chain (BEP20), Polygon (PoS), Arbitrum One, Optimism and Solana (SPL) | 1 USDT |
| Revolut | Ethereum (ERC20), TRON (TRC20) and Polygon (PoS) | 1 USDT |
Approximate, reviewed 2026-08.
Confirmations required, platform by platform
The same transfer is 'not yet confirmed enough' at one platform and long since credited at another, because the threshold is a business decision rather than a property of the network. Comparing them is the quickest way to see whether your wait is normal.
| Platform | Bitcoin | Ethereum | TRON | Polygon | Solana |
|---|---|---|---|---|---|
| Binance | 1 | 6 | 1 | 100 | 32 |
| Coinbase | 3 | 35 | 1 | 200 | 32 |
| Kraken | 4 | 20 | 20 | 120 | 32 |
| Crypto.com | 1 | 12 | 1 | 100 | 32 |
| Bybit | 1 | 6 | 1 | 100 | 32 |
| OKX | 1 | 12 | 1 | 100 | 32 |
| KuCoin | 2 | 12 | 1 | 100 | 32 |
| Revolut | 3 | 30 | 20 | 150 | 32 |
Approximate, reviewed 2026-08. A dash means the platform does not credit deposits on that network, or does not publish a figure.
Where the platform deposit figures come from
- Binance support centre
- Coinbase support centre
- Kraken support centre
- Crypto.com support centre
- Bybit support centre
- OKX support centre
- KuCoin support centre
- Revolut support centre
Policy snapshot 2026-08; verify in-account.
TRONSCAN success still needs a hash in the ticket
A SUCCESS status on TRONSCAN is the chain talking. Coinbase, Kraken or Binance still need the TxID, the TRON network name and the destination address in one message. Copying a screenshot of the green tick without the hash does not search their watcher.
- Create a TRC20 USDT support message — Pulls the TRON hash, amount and destination from the public record.
What you get, and what it costs
Free, always
The transaction check: network, asset, amount, both addresses, timestamp, on-chain status, confirmation count, and a copyable evidence message for support. No diagnosis.
£9.99, one-off
The diagnosis: the likely cause, recovery outlook, step-by-step instructions, the official support route, wording written for that case, and 72-hour monitoring. No subscription.
Questions
TRON says confirmed — why hasn't the exchange credited it?
Because on-chain confirmation and exchange crediting are separate. The exchange must be watching that address, on that network, for that asset, and be able to attribute it to your account.
Related
Platform requirements on this page were last reviewed 2026-08. They change without notice, which is why every diagnosis is phrased as a likely cause rather than a certainty.
TXLens is read-only. We only use your transaction ID and public blockchain data. We never ask for your private keys, seed phrase or exchange login.