Understand the asset
TRX is the native asset of the TRON network. It is distinct from a USDT token transfer on the same network.
Before you send
Follow the invoice’s asset label as well as its network label. A TRC-20 USDT invoice is not automatically a request for TRX.
What privacy means here
The public ledger can expose transaction relationships. Keep account security and payment confidentiality as separate design goals.
After payment
Payment should be confirmed only after the invoice has been reconciled under its confirmation policy. If a payment is delayed, provide the transaction identifier and invoice number through a verified support channel. Never provide a wallet recovery phrase or private key.
TRON is configured for USDT TRC-20
The configured customer payment asset on TRON is USDT, not native TRX. A sender may need TRX or other network resources to submit the token transfer, but those resources are not the invoice asset. Sending TRX to the USDT recipient does not by itself pay the USDT order.
Keep the payment record useful
Retain the order reference, quoted asset and network, expiry and transaction identifier. Contact support through a verified channel if reconciliation is needed. A support enquiry should never include a wallet seed, private key or signing credential.
A little more clarity.
Is native TRX an accepted checkout asset?
No. The configured TRON customer route is USDT TRC-20. Native TRX is discussed as network context rather than an accepted invoice asset.