Guide: How businesses should invoice in stablecoins

A new operational guide explains how businesses should invoice and settle payments in stablecoins. It directs companies to put the commercial amount in dollars or euros while naming the token and the exact blockchain where payment should arrive, and to accept USDC or USDT only as the settlement rail on the named chain.

The guide defines stablecoin invoicing as a standard accounts-receivable document settled in a dollar-pegged token. It warns that quoting the token amount as the invoice price converts a receivable into a crypto trade. It instructs invoices to display the fiat amount, the exact token and chain, the destination address, any memo or destination tag, an invoice number that can be placed in a transfer memo when supported by the chain, and an expiry date.

Practical setups described for 2026 fall into three categories. Low-volume users can publish a wallet address and reconcile payments manually by matching transaction hash, amount, token and chain. Mid-volume firms can use a payments processor or invoicing app that issues a one-time deposit address or payment link and reports paid, underpaid or overpaid statuses. Larger teams can use Stripe Billing or Circle Mint to mint or accept stablecoins and let those platforms act as the reconciliation layer.

The guide cautions that a shared treasury address is a common failure mode because simultaneous payments to one address are difficult to attribute to specific invoices. It also notes that funds sent on the wrong chain or without a required memo or tag are often irrecoverable.

Confirming payment differs from spotting a broadcast. For manual wallets, issuers should wait for the confirmations required in their finance policy, then match token, chain, amount and destination and record the transaction hash on the invoice. For processor flows, an invoice should be marked paid only after the processor credits the payment intent as complete. The document emphasizes that mempool sightings are notifications, not proof of settled payment.

The guide asks companies to set rules for underpayments and overpayments before issuing the first invoice. Underpayments may be refunded and re-requested or accepted as short payments with separate collection; overpayments should be refunded or refunded in full with a retry. Because stablecoin transfers have no card network, refunds must be issued as new outbound transfers to verified addresses. If a processor handled the inbound payment it will typically send refunds back to the customer wallet; if the company collected directly it must perform the outbound transfer and reconfirm the recipient address.

Platform constraints are outlined. Stripe Billing supports stablecoins on invoices and subscriptions only with its send_invoice collection method and a per-transaction cap of $10,000; completed stablecoin payments settle as fiat in the Stripe balance. Circle’s Stablecoin Payins API and transient mint intents provide single-use addresses and terminal payment states of paid, underpaid or overpaid; Circle will not credit funds sent on an unassigned chain and treats those funds as lost.

After receipt, firms must decide whether to hold USDC for supplier payments or off-ramp to bank dollars. The guide notes most issuers do not use issuer redemption with Circle or Tether because that path requires high minimums. It recommends keeping a single audit record that ties together the transaction hash, invoice number, sender address and USD amount rather than relying on a chain explorer as the ledger.

The guide lists situations where stablecoin invoicing should be avoided: when the client cannot hold or send the named token, when the invoice exceeds a processor’s cap, or when the issuer cannot staff proper reconciliation. For large cross-border receivables it recommends comparing the entire payment path and settlement options rather than focusing only on on-chain fees.