Asking for USDT is easy to do badly. The two failure modes are an amount nobody agreed and a network nobody named, and both come from requesting payment in a message instead of on a document. This page is about the narrow, practical version: one stablecoin, one exact figure, one chain.
Try the live invoice generatorUSDT tracks the dollar, so unlike a BTC or ETH request there is no rate to argue about — a 1,450 USDT request should land as 1,450 USDT. That makes the failure mode narrower and easier to close: state the figure to two decimals and state that the received amount must equal it.
The only leak left is the network fee. Senders sometimes deduct it, leaving you 1,448.30 and a partial payment. One sentence on the document prevents the entire conversation.
Write the asset and the chain together — 'USDT on TRON (TRC20)', 'USDT on Ethereum (ERC20)', 'USDT on BNB Smart Chain (BEP20)' — immediately above the address. USDT exists on all three, ERC20 and BEP20 addresses are visually identical, and the network is the only instruction distinguishing them.
In VegaPal the network is attached to the saved wallet rather than typed per document, so the pair cannot drift apart between the PDF, the payment page and the QR code.
VegaPal issues the document and publishes your instructions. It does not hold USDT, convert it or connect to a wallet. On Pro it reads the public TRON, Ethereum and Polygon blockchains to confirm USDT invoices paid on those networks. No fee is taken from what you receive, because nothing you receive passes through it.
On Pro with TRC20, ERC20 or Polygon, confirmation is automatic when the exact amount arrives. Otherwise it is you: look at the wallet, match the amount and the timing, mark the invoice paid. Keeping the transaction hash beside your copy of the invoice answers most later questions before they are asked.
Orsett Freight is owed 1,450 USDT for a customs clearance fee they fronted. They issue tax invoice INV-2026-0119 with one line — 'Customs clearance disbursement, AWB 176-44821 — 1 × 1,450.00' — issued 19 November, due 26 November.
The payment page reads: Orsett Freight, 1,450.00 USDT due 26 November, the line item with the airway bill number so the client can match it to their own file, then 'USDT on TRON (TRC20)', the address with a copy button and QR code, and 'Amount received must equal 1,450.00 USDT — network fees are paid by the sender.' The client pays from their exchange the same day. Orsett confirms in their wallet, files the hash, and marks it paid.
Rounding the amount 'for convenience'. Two decimals removes any question about what was owed. On Pro with TRC20, ERC20 or Polygon, the payment page shows an exact 4-decimal amount (less than one cent extra) so the payment can be matched; ask the client to send exactly that, on-chain, in one transfer.
Naming the asset but not the chain. USDT alone is an incomplete instruction on every network.
Letting the sender net the fee. State the required received figure explicitly.
Failing to distinguish an advance request from a completed sale. Use clear proforma wording and check any local tax-invoice obligations that arise on receiving an advance.
Pasting the address rather than selecting a saved wallet, which is how a stale or truncated string reaches a client.
Request the exact figure with a reference the client can match in their own records.
Issue a numbered document instead of sending an address and hoping.
Name the network their exchange withdraws on so nothing needs bridging.
Tax invoice for something delivered or already incurred, proforma invoice for an advance.
Set the currency to USDT and enter the amount to two decimals with a due date. On Pro with TRC20, ERC20 or Polygon, the payment page then shows an exact 4-decimal amount so the payment can be matched.
Select the USDT wallet whose network you actually receive on, so the pair stays together.
Send the payment page or PDF. On Pro, the invoice turns Paid after 20 confirmations once the exact amount arrives, usually within minutes. On Free, check your wallet and mark it paid.
Crypto payment requests that are documents, not messages
USDT invoicingUSDT invoicing: the rules worth knowing before you send one
USDT invoice generatorUSDT invoice generator: the editor, step by step
TRC20 invoicingTRC20 invoices: USDT on TRON, written so it arrives
Payment requestsRequest payment with an invoice and a shareable payment page
Crypto invoicingCrypto invoices, explained end to end
Use free invoicing calculators for due dates, VAT and late fees.
Explore the invoicing and payment guides, or compare VegaPal plans.
Set the invoice currency to USDT, enter the amount to two decimals, and state on the document that the amount received must equal the amount due so network fees are not deducted. On Pro with TRC20, ERC20 or Polygon, the payment page shows an exact 4-decimal amount (less than one cent extra) so the payment can be matched; ask the client to send exactly that, on-chain, in one transfer.
The one you can genuinely receive on, named in full next to the address. TRC20 is widely supported, and VegaPal Pro confirms USDT payments on TRC20, ERC20 and Polygon automatically; ERC20 and BEP20 suit clients whose funds already live there.
Yes, in VegaPal it is. There is no separate payment-request document type — you issue a tax invoice or proforma invoice and share its public payment page.
No. There is no escrow and no custody. Funds move from your client's wallet to yours, and you set the invoice status once you have seen them; on Pro, USDT invoices paid on TRON (TRC20), Ethereum (ERC20) or Polygon with the exact amount are confirmed automatically.
The free plan includes 3 documents per month, with PDF downloads and shareable payment pages.