A crypto-only checkout leaves one fact you can actually verify

A storefront, a booking form or a direct message that asks you to pay in USDT or another token is handing you one specific technical detail: an address to send to, and a token it expects you to send. That address and that token's contract are the only two things a block explorer can confirm before money moves. How polished the page looks, or how much urgency the message carries, has no bearing on what the explorer shows.

The name 'USDT' in your wallet is not proof of which token it is

Tether's USDT runs on exactly one contract per network: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON, and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A wallet app displays whatever ticker and label a token's creator attached to it, which is why a token can carry the symbol USDT while running on a contract that has nothing to do with Tether. If the contract address behind the payment doesn't match one of those two, the token isn't Tether's USDT, regardless of what it's called on your screen.

As a made-up example: a token could show up in a wallet app as 'USDT', with the familiar logo, while sitting on a contract that copies the real one except for a single character somewhere in the middle of the address. The wallet's display never reveals that difference. Only comparing the full address does.

A received transfer joins the balance that was already there

USDT on Ethereum is an ERC-20 token, and on TRON it is a TRC-20 token. Those are the two networks' standards for how a token is issued and tracked, and both keep a single balance per address. When a transfer lands, the amount is added to whatever that address already held. There is no separate, isolated amount you can point to afterward and call 'the one from this payment'. That matters at a crypto checkout because, if a payment page shows you a 'received' figure or running total of its own, that figure is a number the site chose to display. The chain holds a transfer record and a balance, and nothing on it ties a sum on a web page to the token you sent.

The explorer entry for the transfer itself, the one that lists sender, recipient, contract, amount and time, is what you can actually check against the chain. A number on a checkout page is not.

Reading the contract field on Tronscan or Etherscan

Confirming which token the page wants takes a few minutes, and you can do it before you send anything, using the address the payment page gave you and the transfers that address has already received.

  • Copy the exact address from the payment page, and note which network it names, TRON or Ethereum.
  • Search that address on Tronscan for a TRON address, or Etherscan for an Ethereum one. Both list the sender, recipient, token contract, amount and time for every transfer tied to the address.
  • Open the token transfers the address has already received. Since you have not paid yet, none of them are yours; they show what other people have sent there and under which contract. For each one listed as USDT, compare the token contract field character by character with TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON or 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum.
  • If the contract on those transfers matches neither address, you are looking at a different token that has borrowed the USDT name. If the address has no transfers at all, the explorer has nothing for you to compare, and the check stays unresolved.

What the contract check doesn't settle

A matching contract tells you the token is genuine Tether USDT. It says nothing about whether the page asking for it, or the business behind that page, deserves your money. That is a separate question about the site rather than the token, and our website checker is built for it: enter the page's domain and it reports what we found about that site. If it flags the site, a matching contract does not make the payment safe.

To look at the destination address's history before paying, our wallet checker pulls the same transfer record you would read on an explorer and lays it out in one place, so you can see what the address has received without working through the explorer's tables. It gives you a second view of the same data. The contract comparison, character by character against the two Tether addresses, is still yours to make.

If the contract matches and the page checks out, the technical part is done and you can pay. If it does not match, or the address has no transfers to compare, hold the payment until you know which token you are dealing with: a token on any other contract is not Tether's USDT, whatever the checkout calls it.

Frequently asked questions

Does TRON's version of USDT get checked the same way as Ethereum's?

Yes. TRON's TRC-20 standard keeps one balance per address the same way Ethereum's ERC-20 does, and Tronscan lists the same fields for a TRON transfer, sender, recipient, contract, amount and time, that Etherscan lists for an Ethereum one. The same contract comparison works on either network.

I already sent the payment. Does checking the contract now help?

An explorer shows what already happened on that address's record; it doesn't undo a transfer. Comparing the contract address before you send is what prevents paying into the wrong token in the first place.