USDT Transfer Still Hasn't Arrived? Troubleshoot in This Order

Written August 2026. The order below is "confirm facts first, then find causes" — it avoids most of the panic and the wrong fixes.

When a transfer doesn't arrive, the instinct is to refresh, refresh again, then panic. But on-chain, "hasn't arrived" means five completely different things, each with a different fix. Work through this order and you can usually locate the problem in ten minutes.

Step 1: did the transaction actually go out?

Get the transaction hash and look it up on the block explorer for that chain. This determines every branch below:

• No such transaction. It may never have broadcast (wallet stuck, gas too low and dropped). Your funds are still yours; nothing lost.
• Pending. It's queued — see the next section.
• Failed. It made it on-chain but reverted. The tokens did not move, but the gas was still spent. Usually an insufficient gas limit or a contract error.
• Success. The chain is done; the problem is on the receiving side. Jump to step 3.

See What is a transaction hash and how do you check status?

Step 2: stuck on pending

A long pending state almost always means the gas price was too low — validators prioritise higher bids.

Your options:

• Wait. Once congestion eases, low-priced transactions usually get included. This is normally the right choice.
• Speed up. Resend with the same nonce at a higher gas price to replace it.
• Cancel. Send a zero-value transaction to yourself with the same nonce to displace the original.

Note: both speed-up and cancel cost new gas and neither is guaranteed. Background in What are gas fees, and why do failed transactions still cost money?

Step 3: on-chain success, but nothing in the wallet

This is the most common false alarm. Three causes:

1. Wrong network selected. You're looking at Ethereum while the USDT arrived on BSC or Tron. Switch networks and it appears.

2. Token not imported. Wallets show only some well-known tokens by default; others must be added by contract address. Note that USDT has a different contract address on every chain — use the one for the right chain.

3. Wrong address. You may hold several accounts, and the receiving one isn't the one on screen.

Details in Why can't I see my tokens in my wallet or a dApp?

Step 4: sent to an exchange but not credited

On-chain success, recipient is an exchange deposit address, balance unchanged. Usually one of these:

• Not enough confirmations yet. Exchanges require a number of block confirmations before crediting; it varies by chain, from minutes to tens of minutes. This is the most common cause — just wait.
• Expired or wrong deposit address. Some platforms rotate addresses; using an old one needs a ticket.
• Wrong chain. See Sent crypto on the wrong network? What you can still do.
• The platform doesn't support that asset on that chain. On-chain success, platform doesn't recognise it — ticket required.
• Missing memo or tag. Some chains require a memo; omitting it routes funds to the platform's omnibus account and always needs a ticket.

Step 5: compliance or risk review

For larger amounts, new accounts, or flagged patterns, platforms may review deposits and withdrawals manually. It looks like "confirmed but still processing."

Here you wait or open a ticket. Do not keep retrying the transfer — repeated attempts can make the risk flag worse.

When to open a ticket

Symptom	Action
Pending on-chain	Wait; speed up if needed
Success on-chain, not in wallet	Switch network / import token
Success, exchange not credited, under 1 hour	Wait for confirmations
Success, exchange not credited, several hours	Open a ticket with the hash
Missing memo / wrong chain	Open a ticket immediately
Failed on-chain	No ticket needed; funds never left

Include the hash, sending address, receiving address, chain, asset, amount and timestamp in one go — it materially shortens handling time.

FAQ

Do I get gas back on a failed transaction?

No. Gas pays for computation the network already performed, successful or not.

Can I make the exchange go faster?

A complete ticket helps more than chasing. Opening several tickets for the same issue usually lengthens the queue.

Why is it sometimes seconds and sometimes half an hour?

It depends on block time, congestion, the gas you paid, and how many confirmations the recipient requires.

Further reading

• What is a transaction hash and how do you check status?
• What are gas fees, and why do failed transactions still cost money?
• What are stablecoins? USDT vs USDC

References

• Etherscan: transaction lookup
• Tronscan: Tron explorer
• MetaMask: how to speed up or cancel a pending transaction