How TRC20 USDT payments work: transfer, confirmation and fulfillment
TRC20-USDT is a token on TRON. A website payment order, a wallet transfer, a completed platform order and shipment by the merchant are distinct events. Investigate “sent but not received” at each stage rather than relying on a wallet screenshot.
From an order to payment instructions
The merchant submits the amount, network and callback URL through order creation and stores the returned order number. The payer follows the actual checkout address, amount, network and expiry. UUGate also supports BEP20-USDT, but TRON and BSC are separate networks: the USDT name does not make their payment routes interchangeable.
Broadcast is not completion
A transaction hash identifies a submitted transfer. The network must process it, the platform must apply its confirmation requirements, and the payment must match the order. Order lookup exposes timestamps including detectedAt, confirmedAt and completedAt. Use the returned status; a transaction hash alone does not mean completed.
Separate the costs
TRON uses bandwidth and energy; insufficient resources can result in TRX consumption. See the TRON resource model. Distinguish the payer wallet's network cost from the platform plan and payout or sweep fees. Use current pricing for platform charges instead of treating one quoted fee as the whole cost.
Confirmed on-chain but not fulfilled
Check whether the platform order is complete, then inspect callback delivery and merchant processing records. An unreachable endpoint, a modified request body or a failed database write can leave the merchant behind. Follow callback verification and idempotent processing; do not simply mark an order paid to clear an alert.
Collect evidence before recovery
- Platform and merchant order numbers.
- Actual network, token, destination, amount and transaction hash.
- Creation, payment, confirmation and expiry times.
- Callback HTTP results and local processing records.
Use this information to distinguish wrong-network transfers, mismatched amounts, late payments and callback failures. Do not ask the payer to send repeated transfers just to test receipt. Continue with the USDT integration guide.