Stablecoin invoicing is the practice of billing a customer in a fiat-pegged digital asset such as USDC or USDT and accepting settlement onchain, typically through a payment link or wallet address attached to an invoice. The headline price is denominated in a stable unit (usually US dollars), the rail is a public blockchain, and the payment lands in the recipient’s wallet within seconds to minutes regardless of which country the payer is in. Adoption is no longer hypothetical: Artemis shows stablecoins settling an average of $333.7B in transfer volume per day, and Visa’s Onchain Analytics dashboard tracks stablecoin transfer volume across chains.
This article explains what stablecoin invoicing is, how the underlying flows work, the categories of tools available, the trade-offs versus card and wire rails, and where Eco fits when an invoice needs to settle across multiple chains. It is written for finance, ops, and freelance teams evaluating whether to bill in stablecoins.
What Is Stablecoin Invoicing?
A stablecoin invoice is a billing document where the payable amount is owed in a stablecoin such as USDC, USDT, EURC, or PYUSD, and the payer settles that amount by sending the stablecoin to a wallet or smart-contract address designated by the seller. The invoice itself can live in QuickBooks, Xero, Stripe, a dedicated crypto invoicing tool, or a plain PDF, what makes it “stablecoin” is the unit of account and the rail.
Stablecoins are blockchain-issued tokens that aim to hold a 1:1 peg to a reference currency. The largest by circulating supply are USDC by Circle at roughly $60B and USDT by Tether at roughly $140B as of mid-2025, both reporting reserves backing every token in circulation. Euro-pegged options include EURC from Circle and EURI from Banking Circle. Together these instruments give invoicing the same dollar (or euro) accounting unit a finance team already uses, but with the settlement profile of an internet protocol.
For background on the asset class itself, see the Eco primer on digital dollars and USD-backed stablecoins.
How Does Stablecoin Invoicing Work?
An end-to-end stablecoin invoice has four steps: invoice creation, address generation, payment, and reconciliation. Each step has a different technical surface depending on whether the seller uses a generalist accounting tool, a crypto-native invoicing platform, or a custom integration on top of a payments API.
Step one is invoice creation. The seller drafts a line-item invoice in their accounting system. The line items are denominated in fiat (USD or EUR), but the invoice metadata records the requested settlement asset (e.g., USDC on Base) and a payment expiry. Most modern invoicing platforms, Stripe’s stablecoin payments product launched in 2024, Request Network, and others, offer this as a checkbox at invoice creation time.
Step two is address generation. The platform generates a unique receiving address per invoice, either a fresh externally-owned account, a deposit smart contract, or a virtual account inside a custodial provider. Per-invoice addresses are critical for reconciliation: it is the only way to map an inbound transfer to a specific bill without forcing the payer to attach a memo. For a deeper look, see the Eco primer on stablecoin deposit automation.
Step three is payment. The payer opens the invoice link, sees a payable amount and a deposit address (or scans a QR code), and signs a transfer in their wallet. The payer’s wallet broadcasts a transaction on a chain such as Ethereum, Base, Arbitrum, Polygon, Solana, or Tron. Block times vary: Solana slots are configured to last about 400ms, Base in 2 seconds, Tron in 3 seconds, Ethereum mainnet in 12 seconds. Cost varies more dramatically, a USDC transfer on Base costs less than $0.01 in gas, while the same transfer on Ethereum mainnet routinely costs $1-$5. Most invoicing platforms now default to a low-fee chain.
Step four is reconciliation. The platform watches the deposit address, detects the inbound transfer, and marks the invoice paid once the payment confirms (typically 1-2 blocks). The amount, transaction hash, block number, and chain ID are written back to the seller’s ledger.
Types of Stablecoin Invoicing Setups
Three setups dominate in production today. Each suits a different stage of crypto-payment maturity.
Generalist accounting tool plus a stablecoin gateway
Teams that already run QuickBooks, Xero, or NetSuite can keep their invoicing workflow and bolt on a stablecoin acceptance layer. Coinbase Commerce, BitPay, and Stripe’s stablecoin product let the seller drop a payment link into the invoice email. The gateway handles address generation, on-chain monitoring, and (optionally) auto-conversion to USD. This is the lowest-friction path for SMBs.
Crypto-native invoicing platform
Tools built for stablecoin billing from day one, Request Network, Coinbase Wallet’s pay-by-link, Mural Pay, Bitwage, and others, treat the invoice as a smart-contract object. The seller gets per-invoice addresses, automatic recurring billing, multi-chain receiving, and crypto-native UX. Most also expose APIs for QuickBooks and Xero so the data still lands in the seller’s book of record.
Direct API integration on a payments rail
Higher-volume teams that already have engineering capacity build directly on a treasury or payments API. The team programmatically generates deposit addresses, watches inbound transfers via webhooks, and writes paid status back to their internal billing system. This is the route used by stablecoin-native fintechs, B2B marketplaces, and enterprise treasury operators. The trade-off is engineering load; the payoff is full control over chain selection, fee rebate, and routing logic. Eco’s deposit automation primer and treasury APIs comparison cover this segment in depth.
Benefits of Stablecoin Invoicing
The case for stablecoin invoicing rests on four mechanics that fiat rails cannot match end-to-end.
Settlement speed. A USDC payment on Base finalizes in under 5 seconds. ACH takes 1-3 business days. International wires settle in 1-5 business days through SWIFT. For sellers carrying receivables across borders or weekends, the working-capital improvement is concrete.
Cost. A US domestic wire costs the sender a median of $25, per NerdWallet's survey of bank wire fees. Card processing runs 2.9% + 30¢ per successful domestic card transaction on Stripe, and similar acquirers charge comparable rates. A USDC transfer on Base costs the payer less than a cent in gas. On a $10,000 invoice, that is $290 in card fees vs. less than $0.01 in stablecoin gas.
Programmability. An invoice paid in stablecoin can trigger downstream automation by default: auto-sweep to a treasury wallet, auto-convert to a target stable, auto-disburse to vendors, or trigger a contract-based release of escrowed goods. See stablecoin workflow engines for the automation layer.
Borderless reach. Anyone with an internet connection and a wallet can pay. Cross-border B2B invoicing is the single largest near-term use case, BCG’s 2024 Global Payments report covers the size of cross-border B2B payments, where stablecoin rails hold a small share.
Risks and Trade-offs
The trade-offs are real and worth pricing in before standardizing on stablecoin invoicing.
Counterparty risk on the issuer. Tether and Circle are private issuers. Circle publishes monthly attestations; Tether publishes quarterly. A depeg event, USDC briefly traded at $0.87 in March 2023 during the Silicon Valley Bank failure, means a buyer holding 1,000 USDC has 1,000 dollars of payable but the market price may diverge. Most production invoicing tools auto-convert at receipt to mitigate hold risk.
Wrong-chain transfers. If a payer sends USDC on Polygon to a deposit address that only watches Base, the transfer is recoverable but operationally painful. Per-invoice addresses bound to specific chains, plus payer-facing chain selectors, mitigate this.
Tax and accounting treatment. Stablecoins are treated as property for US tax purposes per IRS Notice 2014-21. Even a 1:1 USDC-to-USD conversion is technically a taxable disposal. EU treatment under MiCA classifies fiat-referenced stablecoins as e-money tokens, with different rules. See the stablecoin invoicing tax treatment guide for jurisdiction-specific detail.
Compliance and KYC. Receiving stablecoin payments from a sanctioned wallet creates exposure under OFAC rules. Production stablecoin invoicing platforms screen inbound payments against sanctions lists; teams building custom integrations need to do the same.
Multi-Chain Invoicing: When One Chain Is Not Enough
The largest operational pain in stablecoin invoicing is not single-chain; it is multi-chain. A US software company billing a Vietnamese contractor often finds the contractor wants to pay USDT on Tron (a widely used USDT network in Asia), while the company runs treasury on Base for US compliance reasons. A European agency invoicing in EURC may have clients paying USDC on Solana. Cross-chain settlement, letting the payer pay on their preferred chain while the seller receives on theirs, turns the invoicing tool into a routing problem.
The cross-chain layer underneath an invoice can be a cross-chain intent protocol: the payer expresses “I want to pay this invoice with USDT on another chain,” a solver delivers USDC to the seller on their target chain, and settlement with the solver happens afterward. For invoicing teams, the user-visible result is a single payment link that accepts any major stablecoin on any major chain.
Eco’s Role in Stablecoin Invoicing
Eco Routes returns a quote for a request such as “deliver $X of USDC to this address on this chain”; the payer funds the intent, a solver delivers the funds, and Hyperlane proves fulfillment. For invoicing platforms, the practical result is one integration across supported chains, with Programmable Addresses available for supported deposit flows.
FAQ
Can I send a stablecoin invoice to a non-crypto client?
Yes. Most stablecoin invoicing platforms include an on-ramp option, which lets the payer pay with a card or bank transfer at checkout while the seller still receives stablecoins. The platform handles the fiat-to-stablecoin conversion in the background. This adds card or ACH fees on the payer side but eliminates the wallet-onboarding step for first-time crypto payers.
Which chain should I default to for stablecoin invoicing?
Base, Polygon, and Arbitrum are the most common defaults for US/EU teams thanks to sub-cent fees and EVM tooling. Tron and Solana dominate volume in Asia and Latin America. The right default depends on where your clients live; multi-chain receiving via a routing layer is the cleanest answer when payer geography is mixed.
Are stablecoin invoices legal for B2B billing in the US?
Yes. The IRS treats stablecoins as property; receiving payment in stablecoins is recognized income at fair market value on the receipt date. State-level money-transmitter rules govern intermediaries, not buyer-seller direct settlement. See the tax treatment guide for specifics.
How do I prevent a payer from sending the wrong stablecoin?
Per-invoice addresses bound to a single chain plus a payer-facing chain and asset selector eliminate most wrong-asset transfers. Some platforms wrap the deposit in a smart contract that rejects unexpected tokens automatically. For high-value invoices, a pre-payment confirmation step is standard practice.
Can stablecoin invoices replace card processing for SaaS?
Increasingly, yes, especially for high-ticket B2B SaaS where the card processing fee is meaningful. Cards still win for low-value, high-frequency consumer transactions where chargeback protection and one-click checkout matter. Most SaaS teams running stablecoin invoicing today offer it as an alternative tender, not a replacement, and some discount the bill for stablecoin payers to capture part of the fee savings.

