✓
Transaction hash
A transaction hash is present. Open the explorer to confirm the token transfer details.
USDT transaction checker
Diagnose whether a USDT transfer can match an order
Paste the transaction facts and the order facts to see the exact checks a payment gateway should perform before marking an order as paid.
Matching worksheet
Fetch on-chain USDT transfer facts, then compare them with order facts.
Local browser diagnosis
Result
This transfer looks matchable
The key gateway checks pass. In production, the backend should still verify the token contract, block timestamp, duplicate tx hash, and order expiration window.
✓
Receiving address
The transfer destination matches the order settlement address.
✓
Exact USDT amount
The transfer amount matches the order amount after 6-decimal normalization.
✓
Order can still be matched
The order status is still eligible for payment matching.
✓
Safe confirmations
The transfer has reached the required confirmation threshold.
✓
Selected network
Check that the explorer transaction is a USDT Transfer on TRC20, not another token or native coin transfer.
01
Always verify token contract
A native ETH, BNB, or TRX transfer is not the same as a USDT token Transfer event.
02
Keep tx hash unique
A single transaction hash should never complete more than one merchant order.
03
Use support diagnostics
When customers pay late, wrong amount, or wrong network, compare explorer facts with order facts first.
Payment troubleshooting
Why a USDT payment may not be detected
Most support cases are not blockchain failures. They are usually a wrong network, a wrong token contract, an amount mismatch, an expired order, or a transaction that has not reached the gateway confirmation rule.
Wrong network
A TRC20 payment cannot complete an ERC20 or BEP20 order. The network selected by the order and the explorer transaction must match.
Wrong token contract
Only USDT token Transfer events should be matched. Native ETH, BNB, TRX, or another stablecoin contract must be rejected.
Amount mismatch
Gateways usually require the exact USDT amount generated for the order. Even a small difference can keep the order pending.
Not enough confirmations
The transaction can appear on the explorer before it reaches your safe confirmation threshold. Wait until the configured block depth is reached.
Expired order
A valid on-chain transfer may still need manual review if the order expired before the payment was detected.
Duplicate tx hash
One blockchain transaction should never settle multiple orders. Keep transaction hashes unique in your payment database.
FAQ
USDT payment detection questions
These checks match how a production USDT gateway should investigate pending or unmatched payments.
Why is my USDT payment still pending?
Check the selected network, USDT contract address, transfer destination, exact amount, order status, and confirmation count. A mismatch in any of these fields can keep the payment pending.
Can I test a USDT payment without sending a new transfer?
Yes. For diagnostics, you can use a real historical USDT Transfer transaction from the matching network and compare its amount and destination with a test order.
Does this checker complete an order?
No. It is a diagnostic tool. It queries and compares facts, but it does not mark orders as paid, write payment records, or trigger webhooks.
What is the most common reason for unmatched USDT payments?
The most common causes are wrong network selection, sending native coin instead of USDT, wrong receiving address, exact amount mismatch, or insufficient confirmations.