Settle a real invoice in stablecoins
A stablecoin can move an invoice payment between wallets. The parties still have to decide what amount settles the bill, who absorbs costs and what happens if they need to refund it.
Agree on the unit and the route
Put the amount owed, pricing currency, token name, network and precise issuer identifier in the payment instructions. Specify whether the invoice requires a fixed token quantity or a local-currency value converted at a particular rate and time. Those terms can produce different answers during a price deviation. A dollar-referenced token can also move against the merchant’s own spending currency.
Confirm both sides support that exact version. For example, Circle distinguishes native USDC on supported networks from bridged versions, and its institutional deposit routes have their own supported assets. A wallet can receive a genuine token that a merchant’s chosen exchange cannot credit. Ask who pays the sending fee, whether a processor deducts a fee, and how much must actually be credited to close the invoice.
Match payment to the order
Use an invoice number in the merchant’s private records. If a public memo is required, choose a reference that does not expose a customer’s name, personal address or what they bought. Ask the payer to supply the transaction identifier through the agreed channel. A screenshot showing their wallet’s balance, or a receipt for a transfer to a similar address, cannot settle this order.
The recipient should check the transfer on the intended network and compare destination, exact token, quantity and status against the open invoice. Record what the merchant actually received and any processor deduction. For a duplicate, underpayment or late payment, agree what closes the order before anyone sends again. A finalized transfer can coexist with a still-unpaid invoice if it went to an unsupported route or failed the amount condition.
Decide how a refund or cash-out works
Write down whether a refund owes the original token quantity or the invoiced local-currency amount, how conversion is measured and who pays the fee. Verify a refund destination with the customer through the authenticated order. Returning money blindly to a transaction’s sending address can credit the wrong party if a custodial service funded the original transaction from a shared wallet.
Agree who carries the conversion risk between receipt and payout. A merchant that accepts a fixed token amount but waits a week to sell has made a separate holding decision. Preserve the original settlement amount and record the later sale as its own event.
Issuer redemption and exchange cash-out have separate terms. A public issuer statement about reserves does not guarantee that a retail merchant can directly redeem at a specific price or immediately reach its bank. Record the local-currency value, preserve the invoice and receipts, and obtain an actual off-ramp quote if that is how the proceeds will be spent. For a time-critical payment, agree on an alternative when either party cannot use the stated route.
Worked example
A 120-unit invoice arrives net of a fee
The processor reports 120 USDC collected, a 1 USDC service fee and 119 USDC paid to the merchant. If the contract makes the merchant responsible for this fee, record the gross payment and expense separately. If the customer sent only 119, that is a different situation. The settlement statement reveals which happened.
What to remember
- Specify the unit of account, issuer, network and exact required receipt.
- Reconcile the order with the actual transfer and processor statement.
- Agree refund valuation and verify the refund destination.
Sources and further reading
- Circle · USDC terms and redemption conditions
- Circle · Supported chains and currency versions
- BTCPay Server · Merchant refund workflow
Sources checked 21 November 2026 · De Leon Coin