TRC20 invoices: USDT on TRON, written so it arrives

Write the asset and the network as one phrase — 'USDT on TRON (TRC20)' — directly above the receiving address. Not 'USDT', not 'Tron', not 'TRC-20' in a footnote. The pair is the instruction; either half alone is incomplete.

Then the amount due in USDT, and a line stating that the amount received must equal the amount due so nobody deducts the network fee from your payment. Everything else on the document is an ordinary invoice: number, dates, itemised work, totals, your business details.

TRON addresses start with T and are 34 characters. They look nothing like an Ethereum address, which is the one small mercy of this ecosystem: a client pasting a TRON address into an ERC20 withdrawal usually gets stopped by their exchange.

Fees on TRON are paid by the sender in TRX, or covered by staked energy, and they are typically small enough that clients do not negotiate over them. Confirmation is fast — usually under a minute — but 'fast' still means you check your own wallet. Nothing in VegaPal watches the chain or confirms a transfer for you.

For an invoice denominated in USDT, the three things that matter to your client are fee, speed and whether their exchange supports the withdrawal. TRON scores well on all three, which is why it has become the default rail for stablecoin invoicing across the Gulf, South and Southeast Asia.

That does not make it the only choice. A client whose treasury lives on Ethereum will want ERC20, and one paying from a BNB Smart Chain wallet will want BEP20. Save whichever wallets you can genuinely receive on, and put the matching one on each invoice rather than asking the client to adapt.

Halden Systems bills a client for a security review. Tax invoice INV-2026-0146, issued 8 July, due 22 July. One line: 'Application security review and remediation report — 1 × 3,600.00'. Amount due 3,600.00 USDT.

The payment block reads, in order: 'USDT on TRON (TRC20)', then the receiving address on its own line, then 'Amount received must equal 3,600.00 USDT — network fees are paid by the sender.' The public payment page shows the same three things with a QR code and a copy button. When 3,600 USDT appears in Halden's wallet, they file the transaction hash with their copy of the invoice and mark it paid.

Writing 'USDT' and assuming TRC20. Your client may default to whatever chain their exchange puts first, which is not always TRON.

Reusing a wallet you no longer control, or one belonging to an exchange account you have since closed. Confirm the address is live before it goes on a document.

Accepting a payment net of fees. State the required received amount; it costs one sentence.

Truncating the address for tidiness on the PDF. The whole string or nothing — a client who has to ask for the rest of it will paste something wrong.

Treating a fast confirmation as a confirmation you have seen. Check your own wallet, then update the invoice.