✓
Transaction hash
A transaction hash is present. Open the explorer to confirm the token transfer details.
Verificador de transacciones USDT
Diagnostica si una transferencia USDT puede coincidir con un pedido
Pega los datos de la transacción y del pedido para ver las comprobaciones que una pasarela debe hacer antes de marcarlo como pagado.
Hoja de coincidencia
Obtén datos de la transferencia USDT en cadena y compáralos con los datos del pedido.
Diagnóstico local del navegador
Resultado
Esta transferencia parece coincidir
Las comprobaciones principales pasan. En producción, verifica también contrato del token, timestamp de bloque, hash duplicado y ventana de expiración.
✓
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.
Diagnóstico de pagos
Por qué un pago USDT puede no detectarse
La mayoría de casos de soporte no son fallos de blockchain. Suelen ser red incorrecta, contrato incorrecto, importe distinto, pedido expirado o confirmaciones insuficientes.
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.
Preguntas frecuentes
Preguntas sobre detección de pagos USDT
Estas comprobaciones reflejan cómo una pasarela USDT de producción debería investigar pagos pendientes o no coincidentes.
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.