BEP20 invoices: USDT on BNB Smart Chain

BNB Smart Chain uses the same 42-character 0x address format as Ethereum. A client looking at your invoice cannot tell from the address which chain you meant, and neither can you when you come back to it in three months.

The consequence is real: USDT sent on BNB Smart Chain to an address you only hold on Ethereum, or the reverse, lands at a place your wallet may not be watching. Naming the network next to the address is not a formatting preference on a BEP20 invoice — it is the only thing preventing the mistake.

Fees are low, though paid in BNB rather than TRX or ETH, so a client without a BNB balance can be stuck holding USDT they cannot move. Worth checking before you nominate it.

The clients who genuinely want BEP20 are usually the ones whose funds sit on Binance and who withdraw on the chain the exchange offers first. If that is your client, invoicing BEP20 removes a step for them; if it is not, TRC20 is the better default.

Write 'USDT on BNB Smart Chain (BEP20)' above the address. Spell out BNB Smart Chain rather than abbreviating to BSC, because plenty of finance staff processing the payment have never seen the abbreviation.

Add the received-amount sentence as on any crypto invoice, and keep the rest of the document conventional: number, issue and due dates, itemised work, totals, business details. The network line is the only part that is special, and it is special because it is easy to get wrong.

Tessellate Games bills a publisher 5,400 USDT for a porting milestone. Tax invoice INV-2026-0231, issued 3 October, due 17 October. One line: 'Console port milestone 2 — build delivery and QA pass — 1 × 5,400.00'.

The payment block reads 'USDT on BNB Smart Chain (BEP20)', then the 0x address in full, then 'Amount received must equal 5,400.00 USDT — network fees (BNB) are paid by the sender.' The publisher withdraws from Binance on BEP20, which is why that network was chosen rather than TRON. Tessellate confirms arrival in its own wallet, records the transaction hash, and marks the invoice paid.

Putting a 0x address on the document with no network named. On BEP20 this is the mistake that actually loses funds.

Writing BSC instead of BNB Smart Chain. Abbreviations help people who already know; the payment is often processed by someone who does not.

Nominating BEP20 for a client with no BNB for fees. They can receive USDT and still be unable to move it.

Saving one wallet labelled just 'USDT 0x…' and using it for both Ethereum and BNB Smart Chain invoices. One label, one chain.

Letting fees come out of the invoiced amount instead of stating the required received figure.