How to Invoice International Clients (USD & USDC)

To invoice an international client and get paid fast, your invoice needs four things: a clear scope and amount, your payment rails (a US bank account for USD or a wallet address plus chain for USDC), the right tax paperwork so nothing is wrongly withheld, and a compliant off-ramp to turn the payment into spendable fiat with a documented reason. USDC is a digital dollar issued by Circle and redeemable 1:1 for US dollars, so a $5,000 invoice settles as 5,000 USDC with no SWIFT delay or correspondent-bank haircut. The part most templates skip is the compliance layer — the W-8 form on the US side and the purpose code on the India side — which is exactly what keeps you from getting taxed twice or stuck explaining an undocumented inflow.

This is general information, not legal, tax, or financial advice. Cross-border and crypto rules change; confirm current guidance with the IRS, RBI, or a qualified advisor before you rely on it. The compliance points below reflect official sources as of June 2026.

What goes on an invoice to an international client?

A cross-border invoice needs everything a domestic one does, plus the currency, the exact payment rails, and the tax status that tells the client whether to withhold.

The fields that actually get you paid faster are the unglamorous ones: a description of services specific enough that an approver doesn't have to ask questions, the amount in a named currency, and a single clear way to pay. If you accept USDC, treat the chain like a SWIFT/IBAN line — it's not optional. A client who can only send on Ethereum cannot pay an address that only exists on Solana, and that mismatch is the most common reason a stablecoin invoice stalls.

Should I invoice in USD or USDC?

Invoice in USD when the client expects a normal bank wire, and in USDC when you want the money to settle in minutes for a single transparent fee instead of a hidden FX stack.

The two aren't really in tension, because USDC is a dollar. A USDC invoice is a USD invoice that happens to settle on a blockchain, which is why you can offer both on the same document and let the client pick. The practical difference is the rails. A traditional SWIFT wire can take days, route through correspondent banks, and lose 2% or more to an FX markup you never see itemized — while a USDC payment moves peer-to-peer and arrives in minutes, with the only fee being the off-ramp from dollar-token to spendable fiat.

Offer USD for the client who wants a familiar wire, and USDC for the client who wants speed — and if you settle the USDC yourself, the only cost is one off-ramp fee instead of a headline rate plus an invisible 2% FX cut.

What tax form do I send a US client as a non-resident?

If you're a foreign entity invoicing a US client, you give them Form W-8BEN-E so the payment for services you perform outside the US isn't wrongly withheld at 30%.

US payers are required to withhold tax on certain US-source payments to foreign persons unless the recipient documents foreign status. Per the IRS instructions for Form W-8BEN-E, a foreign entity provides this certificate to the withholding agent to establish that it is not a US person. Services performed entirely outside the United States are generally treated as foreign-source income and not subject to that withholding — but without the form on file, a cautious client may withhold anyway.

Send the W-8BEN-E proactively with your first invoice, the same way you'd send banking details.

There's a structural point underneath this. A US LLC or C-Corp you own is a US person, so it invoices US clients without the W-8 friction at all — which is one quiet reason founders form a US entity rather than billing from a foreign company. If that's your path, see how to form a US company from abroad for the full sequence.

How do I get paid in USDC and which chain should I name?

Put one wallet address and one chain on the invoice, and pick the chain by balancing your client's convenience against speed and fees — the dollar value is identical on every network.

USDC exists natively on several blockchains, and the client must send on the same network your address is on. StableCorp supports USDC and USDT payouts on Solana, Ethereum, and Polygon, so you can match whatever the client already uses. Solana is the cheapest and fastest of the three — finality in roughly 400ms with sub-cent fees — which makes it the default when you control both ends. If a client insists on Ethereum, Circle's Cross-Chain Transfer Protocol moves native USDC between chains by burning it on the source and minting it 1:1 on the destination, so you're never stuck with a wrapped token.

Invoice in USD or USDC, then off-ramp to USD at 0.5% or to INR at 1% — on a compliant, purpose-code rail with a real paper trail. See pricing.

How do I get the money out — to USD or to INR — and stay compliant?

Off-ramp the payment on a rail that documents why the money came in: to your US bank balance with a US entity, or to INR against a recognized RBI purpose code.

With a US entity, an EIN, and a US business bank account, you simply convert USDC into your USD balance and treat it like any other revenue. Note that an EIN is required to open a US business bank account — applications without one are rejected, so the EIN comes first. StableCorp runs that whole chain — formation, EIN, US bank account, then USD and USDC/USDT payments — and the off-ramp for clients incorporated with it is 0.5% (on-ramp is 1.5%).

For an Indian recipient, the compliance lives in the purpose code. The grey area is the DIY route: receiving stablecoins to a personal wallet and selling them peer-to-peer with no record of why the money arrived. StableCorp's compliant off-ramp settles against supported RBI purpose codes — for software and IT consultancy exports that's typically P0802 — along with P1004, P1005, P1006, P1007, and P1009 (others on request), so each conversion is reported as export of services, not an undocumented crypto transfer. The direct off-ramp to INR is 1%.

Separately, India taxes virtual digital assets at a flat 30% under Section 115BBH, plus a 1% TDS on transfers under Section 194S, with no set-off of losses. Those rules govern how you report the asset; running the conversion on a compliant purpose-code rail is what keeps the *inflow* clean. Confirm current treatment with a qualified advisor.

What does invoicing this way actually cost?

The honest comparison isn't "crypto vs. bank" — it's one transparent off-ramp fee against a headline rate plus a hidden FX markup.

Conventional cross-border payment platforms advertise a headline rate around 2.9% but add roughly a 2% FX markup, so the effective cost lands near 5% on a typical invoice. Because USDC is already a dollar, there's no FX conversion until you choose to off-ramp, and the only fee is that conversion.

On a $5,000 invoice, a ~5% effective cost is about $250 gone; a 0.5% off-ramp is $25 — and you can see exactly where it went. That gap compounds every month you invoice, which is the real argument for stablecoin rails over a hidden-markup wire. See pricing for the full breakdown.

The differentiated point: invoice in the currency that produces your paper trail

Anyone can put a wallet address on an invoice — the valuable part is invoicing in a way that makes every payment explainable to a bank and a tax authority on both ends.

A foreign-owned US LLC has to report transactions between you and the company on Form 5472, and an Indian recipient has to justify every foreign inflow to their AD bank with a purpose code. A wallet full of peer-to-peer trades reconstructed at filing time is exactly what triggers questions. The non-obvious edge is that when the invoice currency and the off-ramp share one compliant rail, the reporting data already exists — invoice number, contract, transaction hash, purpose code, and fiat settlement all line up — instead of being pieced together months later.

That's the StableCorp wedge: not just "accept payment," but invoice on rails that produce the documentation your foreign-owned LLC filings and your bank already expect. If you want the mechanics of receiving the stablecoin itself, see how to accept USDC payments.

The bottom line

Invoicing international clients well comes down to clarity plus compliance: name the currency and rails, attach the right tax form, and off-ramp on a documented rail.

Offer USD for the client who wants a familiar wire and USDC for the one who wants speed; send a W-8BEN-E so US-source income isn't wrongly withheld; and settle to a US bank account at 0.5% or to INR at 1% against a recognized RBI purpose code. Skip the grey-area direct-wallet route — the compliant path costs a fraction of a hidden-markup wire and leaves you with a paper trail instead of a reconstruction problem. StableCorp forms the entity, gets the EIN, opens the bank account, and runs both the on-ramp and the compliant off-ramp; see pricing for the numbers.

Sources