stablecatch

Free tool, no sign-up

USDT and USDC payment checker

Paste a transaction hash to see what actually arrived: amount, token, network, sender, recipient and confirmations. Add the invoice amount to catch underpayments, overpayments and payments sent on the wrong network.

Searches Tron, Ethereum, Base, Arbitrum and Polygon at once. Read-only: we never ask for keys.

What the checker tells you

  • Underpaid or overpaid: the exact difference between the invoice and what reached the chain, down to the last cent.
  • Wrong network: the token arrived on a different blockchain than the one on your invoice.
  • Not sent to you: the transfer went to a different address than yours.
  • Split payments: one transaction with several transfers that each need matching.
  • Failed or pending: the transaction exists but no funds have moved yet.

Questions

Which networks does the checker support?

USDT on Tron (TRC-20), USDT and USDC on Ethereum, USDC on Base, and USDT and USDC on Arbitrum and Polygon. The checker searches all of them at once, so you do not need to know where the payment was sent.

Where do I find the transaction hash?

Ask the payer for the transaction ID (also called TxID or transaction hash), or copy it from your wallet or exchange history. On Ethereum, Base, Arbitrum and Polygon it starts with 0x. On Tron it is 64 characters without 0x.

How does it detect an underpayment?

Enter the invoice amount. The checker adds up every USDT or USDC transfer in the transaction (or only those to your address, if you enter it) and tells you if the total is short, over or exact.

What does wrong network mean?

The payer sent the right token on a different blockchain than you asked for, for example USDC on Polygon instead of Base. If you control the same address on that network the funds are usually recoverable, but it needs separate handling in your books.

Is this free? Do you store the hashes?

The checker is free and needs no sign-up. Transaction data is public on the blockchain; we look it up on demand and do not save your lookups.