Fake payment screenshot? How to verify a USDT transaction

Key takeaways

• Never treat a screenshot as payment. Ask for the TXID, open it yourself on the explorer for the right network (Tronscan for TRC-20, Etherscan for ERC-20, BscScan for BEP-20) and confirm five things: status, token contract, recipient (your address), amount and time.
• The token name proves nothing. Anyone can create a token called "USDT". Only the contract address identifies real USDT: on TRON it is TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t (verified on 3 November 2026).
• "Pending" is not paid. Release nothing until the explorer shows the transfer as successful and confirmed, and the amount has arrived at your own address.
• Refund requests are a classic trap. An "overpayment" that needs part of it sent back should be checked on-chain before anything moves.
• If anything does not match, stop. Do not release, keep the trade inside the platform's dispute process and save the TXID, contract address and chat.

Why screenshots and "sent" messages prove nothing

A screenshot is a picture, not a record. It can be edited, cropped, reused from an older transfer or taken from a different transaction entirely, as AMLBot's TRON verification guide points out. The same applies to a wallet's "sent" screen, a forwarded email or an SMS that looks like a bank alert.

P2P platforms warn about the same pattern. MEXC and Bybit both describe counterparties sending forged receipts and then pushing the seller to release before the money has arrived. Their advice is identical: check your own wallet or bank account directly.

The blockchain is the only source that cannot be faked from the sender's side. Every USDT transfer leaves a public record that you can read in a block explorer in under a minute.

What you need: a TXID or your own address

There are two ways in, and either is enough:

• The TXID (transaction hash). A long string of letters and numbers that identifies one transfer. Ask the sender for it, not for a screenshot or an exchange order number. AMLBot treats a sender who cannot or will not provide one as a warning sign.
• Your own receiving address. Paste it into the explorer and look at its incoming token transfers. This is the stronger check, because it shows what actually reached you, whatever the sender claims.

You also need to know the network. A TXID from one network will not appear on another network's explorer, so a TRON hash returns nothing on Etherscan, and vice versa.

How to check a USDT transaction on Tronscan, step by step

1. Open Tronscan. Type tronscan.org into your browser yourself rather than following a link sent by the counterparty.
2. Paste the TXID (or your own address) into the search bar.
3. Read the result. On a completed transfer, Tronscan shows Result "Successful" and Status "CONFIRMED". Pending, failed or "not found" means the payment did not complete or does not exist.
4. Check the token and its contract. The transfer line should show USDT (Tether USD) with the contract address TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. Compare the full string, not just the first and last characters.
5. Check the recipient. The "To" address must be your address exactly. TRON addresses are case-sensitive.
6. Check the amount. Confirm it is USDT, not TRX, and that the figure matches the agreed sum.
7. Check the time. "Block & Time" is shown in UTC (the UAE is UTC+4). A transfer from before your trade started is not your payment.
8. Save the page link and TXID with your trade record.

The same check on Etherscan (Ethereum, ERC-20)

Paste the hash (it starts with 0x) at etherscan.io. Look for Status "Success" and the number of block confirmations next to the block. For a USDT transfer, "Interacted With (To)" shows the token contract, not the payee; the actual recipient and amount appear under "ERC-20 Tokens Transferred". Check that the token is Tether USD with contract 0xdAC17F958D2ee523a2206206994597C13D831ec7.

The same check on BscScan (BNB Chain, BEP-20)

BscScan is read the same way as Etherscan: status, confirmations, the token transfer line, recipient and amount. Note that the token most wallets call "USDT" on BNB Chain is labelled Binance-Peg BSC-USD, at contract 0x55d398326f99059fF775485246999027B3197955.

The five checks, with the official USDT contracts

• Status. Successful/Success and confirmed. Nothing else counts as paid.
• Token contract. Must match the address for that network (below).
• Recipient. Your own address, character for character.
• Amount. The agreed figure, in USDT, on the agreed network.
• Time. After the trade was opened, and consistent with what the sender told you.

Contract addresses, verified on 3 November 2026:

• TRON (TRC-20): TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. Listed on Tether's supported-protocols page and shown on Tronscan as the TetherToken contract.
• Ethereum (ERC-20): 0xdAC17F958D2ee523a2206206994597C13D831ec7. Listed by Tether; Etherscan shows it as Tether USD (USDT) with 6 decimals and tether.to as the official site.
• BNB Chain (BEP-20): 0x55d398326f99059fF775485246999027B3197955. This one is not on Tether's list: Tether's page does not include BNB Smart Chain for USD₮. The token is a Binance-pegged representation of USDT issued by Binance, as TransFi and Coinranking describe it. Address taken from those sources; we could not open BscScan directly.

Check these against the issuer's page yourself before a large trade. Bitso's guidance puts it plainly: the token issuer's own website is the only fully reliable source for a contract address.

Red flags

• A token called USDT with a different contract. imToken describes fake tokens named USTD, "Tether USD", USDT Pro or USDTX, often with the real logo. Some are sent through exchange withdrawals, so the explorer shows a transfer from an exchange hot wallet; imToken notes that such a label is not an endorsement. In September 2026, Bitcoin.com News reported merchants in Venezuela handing over goods for cloned USDT, including one case worth over $5,500.
• "It's pending, release now." A pending, failed or missing transaction is not a payment, however convincing the explanation.
• Wrong network. USDT sent on Ethereum will not appear on Tronscan. If the sender used a network you did not agree, the funds may not reach a wallet you control.
• The refund-the-overpayment trick. The sender pays, or appears to pay, more than agreed and asks you to return the difference quickly. As Xe explains, the original payment often turns out to be fake or reversible, and the refund is the only real money that moves.
• Pressure and off-platform chat. Urgency, threats to report you, or a request to continue on Telegram or WhatsApp.

What to do if something doesn't match

1. Do not release. Not the crypto, not the dirhams, not a "partial" refund.
2. Stay inside the platform. On a P2P platform, open an appeal or dispute rather than cancelling or agreeing a "mutual" resolution under pressure.
3. Save evidence. The TXID, the explorer link, the token contract address and the full chat.
4. Report. Report the account to the platform, and to the police if you have lost money.

What this check does not protect against

An explorer confirms on-chain facts: that a transfer of a given token reached a given address. It does not tell you whether the sender's funds are clean, and AMLBot recommends a separate AML check for significant payments; see also how to check if a USDT address is blacklisted. It also cannot verify the dirham side of a trade, which you confirm only in your own banking app, and it does not cover chargebacks on reversible payment methods.

Related guides

• How to Check a P2P Counterparty Before You Trade
• Sent USDT on the Wrong Network? What You Can Actually Recover
• The 9 Most Common P2P Crypto Scams — and How to Avoid Every One

This article is general information and is current as at the date shown above. Figures cited are snapshots from the sources listed and change over time. Nothing here is legal, tax or financial advice, and nothing on this website constitutes a financial product offer or solicitation.