Creating a crypto invoice means writing a billing document that asks the customer to pay in a stablecoin or other digital asset, sending it through a tool that generates a unique deposit address, and reconciling the inbound transfer back to your accounting system. The mechanics are simpler than a wire transfer once a tool is set up, but the first invoice has six discrete steps. This guide walks through each step using USDC on Base as the worked example, lists the templates available, and explains where each kind of invoicing tool fits.
​

By the time you finish, you should have a $1,000 test invoice paid and reconciled in under 15 minutes from invoice creation to ledger update. The same flow scales to enterprise B2B billing once you swap the manual steps for API calls.
​

A crypto invoice is a billing document that requests payment in a digital asset—most commonly a stablecoin such as USDC or USDT—and includes the metadata a payer needs to send that payment onchain: receiving wallet address, chain, asset, amount, and an optional memo. The line items are usually denominated in fiat (US dollars or euros) for accounting purposes, with the equivalent stablecoin amount calculated at the moment of invoice creation or fixed at signature.
​

Crypto invoices are most common for international freelance work, B2B SaaS, contractor payroll, and e-commerce in regions with limited card processing. For a primer on the mechanics underneath, see Stablecoin Invoicing: Get Paid in USDC/USDT.
​

Below is the end-to-end procedure. The same steps apply whether you use a managed tool like Coinbase Commerce, a crypto-native platform like Request Network, or a direct API integration.
​

The two-question version: which asset, which chain. USDC on Base is the safest default for US freelancers and SMBs (sub-cent fees, EVM tooling, US-regulated issuer). USDT on Tron dominates Asia-Pacific. EURC on Ethereum or Polygon for EU billing. PYUSD on Solana for PayPal-aligned flows. The chain matters because it determines on-chain gas—a USDC transfer on Base costs less than $0.01, the same transfer on Ethereum mainnet often costs $1–$5. Confirm the payer can hold and send on the chain you pick.
​

Per-invoice deposit addresses are the difference between a clean reconciliation and a hand-mapped spreadsheet. Most invoicing tools generate them automatically. If you are working from a basic template plus a single wallet, append a unique memo or invoice ID to the invoice and ask the payer to include it—though memos are unreliable on EVM chains because they are not natively supported. The cleanest approach is a deposit-automation tool. See the Eco primer on stablecoin deposit automation for production-grade options.
​

Standard invoicing fields apply. Itemize the work or product, list the unit price in fiat, calculate subtotal and total, and add tax if applicable. Two crypto-specific fields belong here: the equivalent stablecoin amount (e.g., “$5,000.00 = 5,000 USDC”) and the chain (“USDC on Base”). Some sellers add a price-fix clause: the stablecoin amount is locked at invoice send time, expires in 7 days, and renews to current rates after that. This protects the seller against minor depeg events without making invoices indefinite.
​

Net-30 still applies. Because stablecoin settlement is near-instant once the payer signs, late-fee triggers can be tighter than on ACH or wire. A typical SaaS or freelance invoice in stablecoin specifies net-15 with a 1.5% per-month late fee. Include the deposit address, the chain, the asset, the amount, and an expiry. Add an OFAC-screening note if you bill outside your home jurisdiction.
​

Send via email or a payment-link landing page. Most tools generate a hosted page with a payment button and a QR code; the payer clicks “Pay,” selects their wallet, and signs the transfer. Make sure the email includes a fallback chain ID and address as text in case the link breaks. Stripe’s stablecoin payments product launched in 2024 ships hosted payment pages by default; Coinbase Commerce and Request Network do the same.
​

The platform watches the deposit address, detects the inbound transfer, and writes a paid-status update to your accounting system via webhook or QuickBooks/Xero connector. Confirm the transaction hash on a block explorer (Basescan for Base, Etherscan for Ethereum) and archive it with the invoice for audit purposes. Tax records require the receipt-date USD value of the stablecoin even if the asset is itself a 1:1 dollar peg. See the stablecoin invoicing tax treatment guide for record-keeping requirements.
​

Three template categories are in production use. Pick based on volume.
​

Plain PDF or DOCX template. Free, manual, fine for under five invoices per month. Includes deposit address as plain text and the payer manually copies it into their wallet. Templates are widely available from Invoice Simple, Wave, and similar generalist tools—just edit the payment-instructions block to specify stablecoin and chain. Reconciliation is manual.
​

Smart-contract invoice (Request Network style). The invoice is itself an onchain object with verifiable status. The payer pays directly to the contract; the contract emits an event when paid. Useful for B2B contracts where both parties want public verifiability and dispute resolution.
​

Hosted payment page (Coinbase Commerce, Stripe, Mural). The invoice URL renders a payment page with QR, deposit address, asset selector, and chain selector. Reconciliation is automatic via webhook. This is the standard for any team running more than ten invoices per month.
​

Match the tool to your situation:

Three mistakes account for nearly every operational failure on a first crypto invoice.
​

Wrong-chain transfer. The payer sends USDC on Polygon to a deposit address that only watches Base. The funds are recoverable but the seller has to import the address into a Polygon-capable wallet. Mitigation: per-invoice addresses bound to a specific chain plus a payer-facing chain selector.
​

Wrong-asset transfer. The payer sends USDT instead of USDC. Most platforms reject this at the UI; some smart-contract deposit addresses revert the transfer automatically. Mitigation: explicit asset selector in the payment page and bold the requested asset in the invoice email.
​

Memo confusion. Some payers paste an invoice ID into a Tron memo field and assume the seller will see it. EVM chains do not natively support memos; only chains like Stellar, XRP, and Tron do. Mitigation: always use per-invoice deposit addresses, never rely on memos for reconciliation.
​

For sellers building a custom invoicing flow, Eco Routes provides the underlying execution layer that lets a single payment link accept any major stablecoin on any of 15+ chains. The payer pays in their preferred asset and chain; the seller receives the asset and chain they configured. Eco Portal wraps the same routing in a no-code interface for sellers who want one-click stablecoin acceptance without the API integration. Either path collapses the multi-chain selector problem into a single button.
​

Open Coinbase Commerce, create a charge, set the amount in USD, send the resulting payment link to your client by email. The platform generates a per-invoice address and reconciles automatically. Total setup time is under 10 minutes if you already have a Coinbase account.
​

You need a place to receive funds. Custodial platforms like Coinbase Commerce and Stripe hold the balance for you and let you withdraw to a bank account. Non-custodial flows require a wallet you control—MetaMask, Coinbase Wallet, Phantom, or similar. Most freelancers start custodial and migrate as their crypto holdings grow.
​

Yes. QuickBooks Online and Xero have third-party connectors that add stablecoin payment links to invoice emails. The connector handles address generation and writes paid status back to your ledger when the transfer confirms. Setup is a one-time install plus a wallet authorization.
​

Once the payer signs the transaction, settlement depends on chain. Solana finalizes in roughly 400ms, Base in 2 seconds, Tron in 3 seconds, Ethereum mainnet in 12 seconds, plus 1–2 confirmation blocks for safety. End-to-end from sign to ledger update is typically under 30 seconds on a low-fee chain.
​

Hosted payment pages with on-ramp options are the easiest path. The payer pays with a card or bank transfer at checkout; the platform converts to stablecoin and credits you. Card fees apply on the payer side, but the wallet-onboarding step disappears for the first-time crypto payer.
​