Crypto invoices, explained end to end

Everything a conventional invoice needs still applies: your business details, the client's details, an invoice number, issue and due dates, itemised work and a total. Being paid in crypto does not remove the need for clean records.

The payment block is the part that changes. State the asset, the network, the receiving address exactly as it should be copied, and the amount expected. Vagueness about the network is the most common reason a crypto payment goes to the wrong place.

If you invoice in a stablecoin such as USDT or USDC, the amount your client sends is the amount you expected. If you invoice in BTC or ETH, decide in advance whether the invoice is fixed in crypto units or fixed in fiat value, and write that choice on the document.

A practical middle ground is to price the work in your accounting currency, state the crypto amount due, and give a short payment window so the figure stays fair to both sides.

Crypto settles on-chain. On Pro, an invoice priced in USDT and paid on TRON (TRC20), Ethereum (ERC20) or Polygon is confirmed for you from the public blockchain when the exact amount arrives. For every other asset, network or amount, confirmation is your own check: look at the receiving wallet, match the amount and the timing, then mark the invoice paid. VegaPal never touches the funds.

Keeping the transaction hash beside the invoice in your own records makes end-of-quarter reconciliation far less painful.

Plenty of clients would rather pay by transfer, and finance teams often have no choice. One VegaPal invoice can show a bank account and a wallet address side by side, so you do not need two documents or a follow-up email.

The public payment page lays out the bank fields for a manual transfer and gives the wallet a copy button and a QR code.

Meridian Data Labs bills a client for a data pipeline build. The header is an ordinary tax invoice: their trade licence number, the client's registered name and address, invoice number INV-2026-0311, issued 2 June, due 16 June. Two line items: 'Pipeline architecture — 1 × 3,000.00' and 'Deployment and handover — 1 × 1,200.00'. Amount due 4,200.00 USDT.

Underneath, the payment block has two halves. The bank half lists account holder, IBAN, SWIFT and a note asking the client to quote INV-2026-0311 as the reference. The crypto half reads 'USDT on TRON (TRC20)' with the address, and one line stating that the amount received must equal 4,200.00 USDT. The client's finance team picks whichever half suits them, and Meridian never has to explain the options in an email.

Treating the crypto payment block as a substitute for the rest of the invoice. Wallet address and amount are not an invoice; you still need a number, dates, a description and your business details, or the document fails the same checks any other invoice would.

Leaving the pricing basis unstated on a volatile asset. If the invoice is for BTC or ETH, say whether the figure is fixed in crypto units or fixed in fiat value at a stated rate, and give a payment window. Silence here becomes a dispute when the market moves.

Naming an asset without the network. USDT, USDC and many other tokens exist on multiple chains with different address formats. The asset alone is an incomplete instruction.

Assuming every payment is confirmed automatically. Only USDT invoices paid on TRON (TRC20), Ethereum (ERC20) or Polygon with the exact amount are, and only on Pro. For BTC, ETH, USDC or BEP20, check your own wallet and then update the document.