How to Invoice a Client in USDC

A client has asked to pay in USDC rather than by bank transfer. None of your commercial terms need to change — amount, deadline and deliverable stay what they were. What changes is that the invoice must now name a network and an exact receiving address as precisely as it would name an IBAN, because a payment sent to the wrong one cannot be recalled. This is not tax advice.

This page covers Arc in its first weeks of mainnet. Where something is still settling we say so rather than guess, and we revise the page as the ecosystem fills in. Last reviewed: September 2026.

What does it mean to be paid in USDC?

USDC is a stablecoin: a digital token issued by Circle, designed to hold a value of one US dollar and backed by cash and short-dated US government debt. Being paid in USDC means the client sends tokens rather than instructing a bank, and the transfer settles on a blockchain — a shared ledger kept by many independent computers, which is what "onchain" means.

To receive one you need a wallet: software or a small device holding the cryptographic key that proves you control an address. That address is what the client pays to, and unlike an account number it carries no name and nobody to catch a mistake. Transfers are irreversible and settle in seconds, including outside banking hours. Choosing a wallet takes ten minutes.

What has to go on the invoice?

Five things beyond your normal invoice content: the amount and its currency, the network, the full receiving address, the deadline, and who pays the network fee.

State the amount in the currency your contract is denominated in, then name the settlement asset separately: "Total due: USD 4,800, payable in USDC." Name the network explicitly — "USDC on Arc," "USDC on Ethereum." USDC exists on many blockchains and a balance cannot move between them without a bridge. A client who pays on a network your wallet does not support has not paid you.

Give the address in full and copyable, never abbreviated in the middle; a QR code helps. Set a deadline the usual way — "net 14, settled onchain by 23:59 UTC" — and say whether the network fee falls on the payer. It usually does, and on Arc it is a fraction of a cent, small enough that arguing about it costs more than paying it.

What happens on FX if the invoice is not in dollars?

If your invoice is denominated in euros, pounds or anything other than dollars, USDC adds a foreign-exchange step, and the invoice must say who bears it and when the rate is struck. USDC is a dollar instrument, so a €5,000 invoice settled in USDC is a dollar payment sized by a rate somebody chooses.

Write the mechanism down rather than leaving it to goodwill: "EUR 5,000, payable in USDC at the ECB reference rate published on the payment date, rounded to two decimals." That fixes source, timing and rounding, which is where disputes start; a fixed rate agreed at invoice date and printed on the document works too.

Converting USDC into local currency on arrival costs a further spread; price that in. Circle also issues EURC, a euro stablecoin, and Arc runs an onchain FX engine called StableFX. Two things about it matter before you build an invoice around it. It is an institutional service: Circle's documentation describes a request-for-quote engine for vetted institutions working through an API key, not a button a freelancer presses. And the pair list is still filling in — Circle's developer documentation describes USDC and EURC conversion, while its partner-stablecoin programme names Brazilian real, Mexican peso, Japanese yen, Australian dollar, Canadian dollar, Philippine peso, South Korean won and South African rand as the intended range. Which pairs are live on Arc mainnet when you read this is changing month to month, so check Circle's StableFX documentation rather than any page's list, this one included.

How do you receive the payment safely?

Verify the receiving address with the client before they pay, through a channel that is not the email thread: read every character back on a call, or confirm it in a signed document.

Invoice redirection fraud is the most common attack on business payments and works identically here, except that nothing can be recalled: a spoofed email sends a polite "we have updated our payment details" note and the money is gone. Treat any address change arriving by email as fraudulent until confirmed by voice on a number you already had, and say so on the invoice. More such tricks are catalogued in common Arc scams.

For a large invoice, ask for a $1 test payment first, confirm it arrives, then release the balance. It costs cents and catches typos and wrong networks before they cost five figures. Confirm too that you control the address yourself: if a platform holds the key for you — custody, in the jargon — its terms, freezes and outages become yours.

How do you reconcile it and keep records?

Every USDC payment produces a transaction hash: a unique identifier for that transfer, permanently visible on a block explorer. Record it against the invoice number — it is a bank reference anyone can verify independently.

The minimum record per invoice: settlement date and time, transaction hash, network, sending and receiving addresses, amount in USDC, and the local-currency value you booked. On Arc all of it comes from the explorer; the Arcscan guide covers exporting it.

Raise two things with your bookkeeper early. USDC is generally not treated as cash in financial statements even though it behaves like it; most frameworks classify it as an intangible or a financial asset. And a gap between recognising revenue and converting may create a revaluation entry. Tax treatment is jurisdiction-specific, including whether converting USDC is a taxable disposal, so ask your accountant before the first invoice.

What is different about getting paid on Arc?

Arc is a blockchain built by Circle, the issuer of USDC, live since September 16, 2026. For someone receiving an invoice payment the difference is that gas — the small fee every blockchain charges to process a transaction — is paid in USDC on Arc rather than in a separate volatile token.

On most networks gas is paid in that chain's own asset — you can hold $4,800 in digital dollars and be unable to move it for want of $3 of something else. On Arc the money you were paid in is the money that moves it, the fee is a fraction of a cent, and settlement is final in under a second. Mainnet being weeks old, treat any quoted fee as a snapshot rather than a rate card; the order of magnitude is the durable point. See gas fees on Arc and, on the paying side, paying contractors in USDC.

Frequently asked questions

Do I have to take the whole invoice in USDC?

No. Split invoices are unremarkable — part by bank transfer, part in USDC. Put both routes on the document with their own deadlines and reconcile two receipts against one number.

What if the client sends USDC on the wrong network?

The funds sit at your address on a different blockchain. Sometimes they are recoverable, if you control that address on that network; often they are not, particularly if they went to an exchange deposit address. Which is why the network belongs on the invoice.

Is a USDC payment reversible if the client changes their mind?

No. Onchain transfers are final once confirmed, with no chargeback and no intermediary who can claw them back. A refund is a new payment in the other direction.

How do I convert USDC into my local currency?

Through an exchange, broker or payment provider that supports withdrawal to your bank. Each charges a spread, a fee or both, and requires identity verification. Compare the all-in cost before assuming it beats a wire.