# How to invoice a client in crypto How a freelancer sends a crypto invoice a client can actually pay, what to include, and how funds settle directly to the freelancer. --- ## How to invoice a client in crypto Sending a crypto invoice is not as simple as swapping out your bank account number for a wallet address and calling it done. The denomination question, the chain question, the expiry problem, the tax clock — all of it has to be resolved before the invoice leaves your outbox, or you will create problems downstream that no blockchain can fix. This article is for freelancers who want to get paid in crypto cleanly: what the invoice needs to contain, how to structure it so a client can actually execute the payment, what happens to that money the moment it lands, and where the real friction points sit so you can solve them before they hit you. ## Why a crypto invoice is different from a fiat invoice A fiat invoice is a demand for value. A crypto invoice is a demand for value *and* a set of precise technical instructions. If a client misreads a sort code, their bank catches it. If a client sends USDC on Ethereum to a Solana address, that money is gone. The document you send carries weight that a standard PDF invoice never did, which means the payment-instructions block of a crypto invoice is not a footnote — it is the most operationally critical section of the whole document. 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: the receiving wallet address, the chain, the asset, and an expiry. Everything else on the document — your name, your client's name, invoice number, line items, due date — is exactly what it would be on any professional invoice. The crypto-specific layer sits inside the payment instructions block, and getting that block right is what separates a clean settlement from a support nightmare. ## The denomination decision: fiat value, crypto amount, or both The first decision on any crypto invoice is what unit you are billing in and whether that unit can move before the client pays. You have two core models: either specifying a direct crypto amount, or stating a fiat amount that will be converted to crypto at payment time. Each has a different risk profile. **Billing in a fixed crypto amount** — say, 1,000 USDC — is clean when you are invoicing in a stablecoin because the value is anchored. It gets complicated fast when you bill in ETH or BTC, because the dollar value of 0.35 ETH the day you issue the invoice may have moved materially by the day the client pays. Most professional freelancers billing cross-border should avoid billing volatile assets at a fixed token quantity unless they have a specific reason to hold that asset. **Billing in fiat with crypto settlement** is the cleaner model for most situations. You state the invoice amount as $4,500 USD — your client's accounting team understands that, your contract references that — and your payment instructions specify the equivalent in USDC or USDT at the time of payment. Quote your rates in fiat but allow crypto payment. This way, you and your client agree on value before markets move. The one wrinkle here is that you need to either include an expiry on the crypto equivalent (so the quoted token amount does not become stale) or denominate entirely in a stablecoin pegged 1:1 to your fiat figure. 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, 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. For the vast majority of freelancers, invoicing in USDC or USDT and denominating in the same dollar amount as your contract eliminates the conversion problem entirely. The invoice says $4,500 USDC. The client sends $4,500 USDC. You receive $4,500 USDC. No FX math, no rate expiry, no ambiguity. ## Choosing the right stablecoin USDC and USDT are the two dominant options, and the choice matters more than people think. For most freelancers, USDC is the safer regulatory choice. Circle is a US-regulated company, publishes monthly reserve attestations, and USDC is the stablecoin referenced in the GENIUS Act stablecoin framework passed by the US Senate. If your client base is US or EU-domiciled, and especially if you anticipate any regulatory scrutiny of your invoicing practices, USDC is the cleaner credential to present. USDT has deeper liquidity and wider adoption on Asian exchanges, making it the practical choice if your clients or off-ramps are in Asia-Pacific markets. If you are working with clients who have treasury operations in Singapore, Hong Kong, or anywhere in Southeast Asia, USDT on Tron (TRC-20) is often what their finance team already holds and can move immediately. Specifying USDC on Ethereum when your client's treasurer holds USDT on Tron means they need to convert before they can pay you — and that conversion has a friction cost. Accepting stablecoins also eliminates the capital gains event that arises when volatile crypto appreciates between receipt and sale — they do not appreciate, so there is nothing to track beyond ordinary income. That simplicity compounds in your favor at year end. The practical rule: ask yourself where your client holds their operating treasury, then specify a stablecoin and chain they can actually send from without a conversion step. If you do not know, default to USDC on a low-fee EVM chain such as Base or Polygon, and note in your invoice that you can accept USDT on Tron as an alternative. Give the client a path that requires zero friction on their end. ## What a complete crypto invoice must include A crypto invoice must carry every field a standard professional invoice carries, plus a complete payment-instructions block. Missing either breaks something — missing the standard fields creates a tax and audit problem; missing or imprecise crypto fields creates a payment-execution problem. ### Standard invoice fields Every invoice — crypto or otherwise — needs: your legal name or business name and address; your client's legal name and billing address; a unique invoice number; an issue date and due date; a description of services with line items; the total amount due; and any applicable taxes or discounts. Always include a unique invoice number and a clear due date for payment tracking. The invoice number is your reconciliation anchor. When a payment hits your wallet, that number is how you match the inbound transfer to the work that generated it. Some freelancers add the invoice number to the transaction memo field when requesting payment — a minor instruction that saves real time when you are reconciling. ### The crypto payment-instructions block This is where most crypto invoices fail. Specify the exact cryptocurrency and network for payment — for example, "USDC on Ethereum ERC-20" or "USDT on Tron TRC-20." Never write "send USDC" without specifying the chain. USDC exists on Ethereum, Base, Polygon, Solana, Arbitrum, and others. They are different tokens on different networks. A client who sends USDC on Solana when you are configured for Ethereum will have their wallet show the payment as sent — but the funds will land somewhere you cannot access them. Include your wallet address, the network, and the exact amount in USD terms. Specify the chain explicitly — sending USDC on Ethereum when you expect Polygon means the funds land in the same wallet address but on a different network, which can cause confusion. Beyond the address and chain, the instructions block should include: - **The exact amount due in the stablecoin you specified.** Not "approximately." Exactly. - **A payment expiry if you are quoting a token equivalent of a fiat amount.** 48 to 72 hours is standard. - **A QR code** if you are sending the invoice as a PDF. A client with a mobile wallet can scan and confirm the address in two seconds rather than manually copying a 42-character string. - **A plain-language "how to pay" paragraph** — one short paragraph explaining the steps: open your wallet, select the network, paste the address, confirm the amount, send. A one-paragraph "how to pay" section in your invoice eliminates 90% of client questions. If your client is a larger company whose finance team may never have paid crypto before, lead with the client's benefit: "If you pay via USDC instead of wire transfer, you skip the $30–50 bank fee and the payment settles in minutes instead of days." Corporate clients with finance teams respond well to concrete numbers. ## The wallet: what you receive into and why it matters Before you issue a single crypto invoice, you need to decide what kind of wallet you are receiving into — and that decision has security, operational, and tax implications. Options include hot wallets (internet-connected like MetaMask or Trust Wallet) or cold wallets (hardware-based like Ledger for higher security). For day-to-day invoicing and payments under roughly $5,000 per transaction, a well-secured hot wallet is operationally straightforward — you can check balances from any browser, the wallet address stays stable, and you can sign transactions immediately when needed. For larger balances or high-volume months, a hardware wallet for storage with a hot wallet for receiving is the professional setup. The hot wallet receives the payment; you move the majority to cold storage once confirmed. One operational decision that pays dividends: keep a separate wallet for freelance income and another for personal use. It makes record-keeping significantly simpler. When your business income wallet has one job — receive client payments — your transaction history is clean. You are not hunting through a mixed wallet trying to separate personal transfers from billable income. The other thing to confirm before you finalize your wallet address: the address is correct for the chain you specified in the invoice. A receiving address on Base will be identical in format to an Ethereum address, but they are different networks. Before you add any wallet address to an invoice template, send a test transaction of $1 to yourself on the correct chain and confirm receipt. Do it once. Never second-guess a live payment. ## Delivery format: PDF, payment link, or invoice platform You have three practical delivery options, and each fits a different situation. ### Plain PDF invoice A PDF with crypto payment instructions embedded is appropriate when you invoice infrequently — five or fewer invoices per month — and your clients are already comfortable with crypto. A plain PDF or DOCX template is free, manual, and fine for under five invoices per month. It includes the deposit address as plain text, and the payer manually copies it into their wallet. The limitation is reconciliation: you have to manually watch your wallet for the inbound payment and match it to the invoice yourself. That works at low volume. At higher volume, it becomes error-prone. ### Crypto invoicing platform A dedicated platform — Request Finance, Acctual, and similar tools — automates the back end of the workflow. 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. The value of a platform is primarily in steps two and four. The platform generates a unique deposit address per invoice — so even if you invoice the same client twice in one month, each invoice has its own address and the payment is automatically matched to the right invoice. Confirm the transaction hash on a block explorer and archive it with the invoice for audit purposes. Most platforms surface the transaction hash automatically; you just download it and attach it to your records. Stablecoin invoicing platforms live or die on reconciliation. Sending an invoice is easy. Matching an incoming USDC transfer on Base to an invoice that was quoted in USDT on Arbitrum, while handling a 2-cent underpayment and a late fee, is where most tools fall apart. If you are serious about crypto invoicing at volume, the reconciliation capability of whatever tool you pick matters more than the invoice design. ### Payment link A payment link is not a replacement for an invoice — it is the payment execution layer embedded in or attached to an invoice. You create the payment link for the exact amount, attach it to the invoice PDF, and the client clicks through to a hosted page where they connect their wallet and sign the transaction. 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. This is where Shaka is built to operate for freelancers working in deal-oriented contexts — where the payment needs to go to more than one wallet at closing. If you are a consultant working with a sub-contractor, or a creative working with a producer, and the client payment needs to split immediately at the moment it is sent — your name and your collaborator's name both on the job — Shaka's onchain payment routing handles that in a single transaction. You set the wallets, you set the percentages, the client sends once, and everyone receives their share directly. No collecting and redistributing, no waiting for a second transfer. ## How settlement actually works Once the client executes the payment, the blockchain does exactly what the blockchain does: it validates, confirms, and writes the transaction to the ledger. Depending on the network, confirmation is near-instant (Base, Solana, Tron) or takes a few minutes (Ethereum mainnet under light load). The payment lands in the recipient's wallet within seconds to minutes regardless of which country the payer is in. There are no business days, no cut-off times, no correspondent bank taking a relay fee in transit. The client signs, the transaction hits the mempool, miners or validators process it, and you see the inbound transfer in your wallet. On most low-fee chains that is measured in seconds. What you do next depends on your operating model. If you are holding stablecoins as working capital, you are done — the money is in your wallet and its value is stable. If you convert to fiat, you move the stablecoin to an exchange, sell for your local currency, and initiate a withdrawal to your bank account. Depending on the exchange and your jurisdiction, that withdrawal takes a few hours to a few business days. Every transaction is logged on the blockchain, providing a transparent record that can come in handy for audits or as proof of payment. That transaction hash is your receipt — immutable, timestamped, publicly verifiable. For professional service invoicing, that is a stronger paper trail than a bank confirmation email. ## The tax clock starts the moment it lands This is the part most guides bury at the end, but it is operationally urgent: the moment crypto hits your wallet, a tax event has occurred. Whatever the fair market value is at that exact timestamp, that is the income you have recognized. Not when you convert. Not when you move it. When it arrives. The IRS treats cryptocurrency as property, meaning that when you receive it as income, this is taxed as ordinary income. If you worked as an independent contractor and were paid with a digital asset, you must report that income on Schedule C (Form 1040), Profit or Loss from Business. For USDC or USDT, this is administratively straightforward — a $4,500 USDC payment is $4,500 of self-employment income, full stop, because the stablecoin value does not move. Accepting stablecoins eliminates a capital gains event because they do not appreciate, so there is no separate capital gains tracking to do after receipt. If you receive ETH or BTC, you have to record the USD-equivalent value at the exact moment of receipt as your income basis, and then separately track any gain or loss from the moment of receipt to the moment you dispose of it — two tax events from one payment. For every crypto payment received, record the date, the token and amount, the USD-equivalent value, the transaction hash (TXID), and the client name. A simple spreadsheet works. At low volume, that spreadsheet is all you need. Do not wait until year end. Record each transaction as it comes in, take three minutes, and move on. When you hit meaningful volume — dozens of payments per quarter — crypto tax software like Koinly or CoinTracker can import your wallet's transaction history and generate the income figures your accountant needs. Consult a tax professional familiar with digital assets in your jurisdiction. Crypto tax law is still evolving, and the cost of a one-hour consultation is far less than an audit penalty. ## Communicating with clients who are new to crypto Not every client you want to bill in crypto has ever sent a stablecoin before. That friction is real, and how you handle it determines whether the payment happens at all. The single most effective reframe is economic. Freelancers who position crypto as a mutual cost reduction — not a personal preference — report higher acceptance rates. You are not asking the client to do something exotic. You are offering to let them skip a $40 wire fee and receive a payment confirmation in two minutes instead of five days. Keep the technical instructions in your invoice as concrete as possible. Name the wallet app you expect them to use if they are a first-time sender. Offer to take a five-minute call to walk through the transaction. For larger engagements, the friction cost of a brief onboarding conversation is trivial compared to the settlement speed and certainty of an onchain payment. Keep traditional payment methods available. Your invoice should list "Bank Wire," "PayPal," and "Stablecoin (USDC/USDT)" as parallel options. Presenting crypto as the preferred method while making it one of several valid options removes the pressure and lets crypto-ready clients self-select. Over time, your client base shifts. You do not need to force it in any single transaction. ## Net terms and late fees in a crypto context Standard invoicing practice applies to crypto invoices with one important adjustment: because settlement is near-instant once the client executes, your late-fee trigger can be tighter than on a wire transfer where you have to account for processing delays. Because stablecoin settlement is near-instant once the payer signs, late-fee triggers can be tighter than on ACH or wire. A typical stablecoin invoice specifies net-15 with a 1.5% per-month late fee. There is no ambiguity about when payment was "received" — the block timestamp is the receipt time. If you specify net-15 from the invoice date, the blockchain confirms exactly when the payment arrived, and any dispute about timing evaporates. This precision also works in your favor when following up on overdue invoices. You can send a client the transaction hash for an unpaid invoice date and time, and a link to the block explorer showing what happened. There is no "check is in the mail" in crypto. It either settled or it did not, and you can see the ledger. ## The multi-party scenario: when you are not the only recipient Some projects involve more than one payee. A brand consultant brings in a copywriter; a developer brings in a designer; a strategist bills for a team of three. In these situations, the naive approach — collect the full payment, then redistribute — creates two separate problems. You have collected income you must report on your taxes. And you have to execute a second set of transfers, manually, with all the delay and confirmation risk that involves. The cleaner approach is to structure the payment so that each collaborator receives their share directly and simultaneously, in a single transaction from the client. That is the problem Shaka is built to solve: you create a payment link, specify each recipient's wallet and their percentage of the total, and when the client pays, the funds route to each wallet in one transaction. No redistribution step, no holding the float, no second round of tax events for funds that never belonged to you in the first place. For freelancers working in production teams, consulting collectives, or any arrangement where a single client payment needs to reach multiple professionals, that kind of onchain routing infrastructure is not a convenience — it is a structural solution to a genuine business process problem. A crypto invoice, executed well, is not more complicated than a wire transfer — it is just complicated in different ways, and those ways are entirely front-loaded. Get the denomination right, specify the chain precisely, document every receipt at the moment it lands, and handle the client communication with the economic framing it deserves. Do those things once on your first invoice, build them into your template, and every subsequent invoice is a straightforward execution. The blockchain does not have business hours, processing delays, or correspondent bank fees. That is the entire point — and the workflow to access it is one clean invoice away.