# How to get paid when the client is a startup paying in stablecoin A practical guide for freelancers and their settlement professionals on structuring, protecting, and routing stablecoin payments from startup clients with certainty. --- The brief lands in your inbox on a Tuesday afternoon. The startup wants a brand identity, a go-to-market strategy, a full-stack web build, or a six-month content retainer. The budget is real. The founders are credible. And then, buried in the last line of the proposal: *"We pay in USDC from our treasury."* For a lot of freelancers, that sentence still triggers one of two reactions: quiet excitement, or quiet dread. The excitement is understandable — stablecoin payments settle faster than a wire and arrive without the 3–7% combined bite of FX spreads, intermediary bank charges, and conversion fees that traditional cross-border payroll routinely eats. The dread is also understandable — there are real structural questions about finality, about protecting co-workers and subcontractors who share in the deal, and about what happens to your tax records when the receipts live on a blockchain instead of in a bank statement. This article is a working guide. It answers the practical questions: how to structure the engagement, how to invoice, how to protect everyone who needs to get paid, how to handle the tax and compliance side with confidence, and when and how tools like shaka.deal turn what could be a complicated multi-party settlement into a single clean transaction that leaves no ambiguity about who got what and when.
$1,500cost of a 3% wire spread on a $50,000 project
Under $1cost of a USDT or USDC transfer on most chains
60%of freelancers were paid in crypto at least once in 2025, according to Rise

Wire spread from the article's worked example ($50,000 project, 3% spread); transfer cost and freelancer share as stated in the sections below.

## Why startup treasuries hold stablecoins in the first place Before building your payment architecture, it helps to understand the other side of the table. Many founders are not paying in USDC because they are trying to be exotic. They are doing it because their operating capital genuinely lives on-chain. The operational model is increasingly standard: the company holds USDC in a treasury wallet, and the payroll or accounts-payable platform orchestrates scheduled payouts from that same balance — contractors receive funds they can hold, swap, or convert to local fiat. In other words, the startup is not converting fiat to USDC specially for you. The USDC is already there. Asking them to wire instead may mean a three-day delay and an FX conversion they have to fund from a separate bank account that may be nearly empty. The total stablecoin float reached $319.6 billion in April 2026, with USDT at $189.6 billion and USDC at $77.6 billion leading institutional adoption. This is no longer a niche arrangement. Stablecoin payouts have moved from a niche workaround into mainstream payroll infrastructure. Understanding that is the first step to negotiating confidently and structuring a deal that works for everyone involved. ## Choosing the right stablecoin before you sign anything Not all stablecoins carry the same risk profile for settlement purposes, and the contract should specify the exact token and network before any work begins. **USDC** is the dominant choice for professional freelance engagements in 2026. USDC is the compliance-first stablecoin for enterprise payments — Circle publishes monthly attestation reports verified by Deloitte, with reserves held in cash and short-term US Treasuries. As of 2026, USDC is registered across more than 30 chains, including Ethereum, Solana, Base, Arbitrum, and Avalanche, and holds full regulatory recognition under the EU's MiCA framework. Crucially, USDC is the stablecoin referenced in the GENIUS Act stablecoin framework passed by the US Senate in 2025. **USDT** remains an option, particularly if your client's treasury or your own off-ramp infrastructure is oriented toward Asian markets. 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. **The network matters as much as the token.** Ethereum, Layer 2 networks, and Solana provide settlement assurance in different ways, so your confirmation rules and operational procedures should differ by network and by use case. A payment of 10,000 USDC (approximately AUD 15,400 at current rates) landing on Ethereum mainnet carries different finality characteristics than the same token moving on Base or Arbitrum. Define the token, the chain, and the minimum number of block confirmations required before you treat the payment as received — and write all three into the contract. ## What finality actually means for a freelancer Finality is the concept that matters most when you are deciding whether to start the next phase of work, hand over a final deliverable, or release a license. Stablecoin finality is the point where you treat a transfer as effectively irreversible for your specific risk tolerance. Settlement typically occurs within seconds or minutes depending on the network, and provides transaction finality without reliance on banking hours, batch processing, or intermediary reconciliation. This is structurally different from a bank wire, which can be recalled or reversed by the sending institution for days after it appears to land. Once a stablecoin transaction reaches finality on-chain, the obligation is discharged. The end point — where a payment is completely delivered, the obligation related to it is discharged, and the recipient can treat it as received — is what practitioners mean by true settlement finality. That is a genuine professional advantage, but it also creates a responsibility. Because the transaction is final, there is no recourse through a payment network dispute process. This means your contractual protections — milestone definitions, acceptance criteria, payment triggers — carry the full weight of your security. They need to be precise. ## Structuring the contract: milestone architecture for stablecoin deals The milestone structure for a stablecoin engagement follows the same logic as any professional services contract, but the stakes of precision are higher because payment is immediate and irreversible once triggered. A milestone split of 30% on signing, 40% at a midpoint deliverable, and 30% on final delivery is a common and defensible framework for projects in the $10,000–$50,000 range (approximately AUD 15,400–AUD 77,000). For larger engagements, five-milestone front-loaded structures of 30/20/20/15/15 dominate to balance freelancer cash flow against client risk. Each milestone payment trigger should be defined in writing — not by feel, but by a specific deliverable or approval event. The client should review each deliverable within a defined window — typically five business days — and provide written acceptance or a specific list of deficiencies; deliverables not responded to within that window are deemed accepted. That deemed-acceptance clause is critical in stablecoin deals because it removes the scenario where a client delays a milestone payment indefinitely by withholding approval. Also define: the wallet address that will receive payment, the stablecoin and network, the number of confirmations that constitutes valid receipt, the governing law, and the dispute venue. Governing law and courts must be named in the contract — nothing protects you by default across borders. ## The multi-party problem: when you are not the only one getting paid This is where many stablecoin freelance engagements break down — not for the lead contractor, but for everyone else who shares in the deal. Consider a realistic scenario. A UX agency closes a $75,000 (approximately AUD 115,500) product design engagement with a Series A startup paying from its USDC treasury. The agency lead manages the project, but the delivery team includes a senior researcher who takes 20% of every project, a frontend developer on 25%, and a motion designer on 15%. The agency retains the remaining 40%. In a traditional wire environment, that agency would receive the full wire and then manually distribute shares to each party — often days later, sometimes weeks later, sometimes with disputes about amounts or timing. In a stablecoin environment, the startup sends one transaction to one address. Everything that happens after that is the agency's internal problem. Or it doesn't have to be. **This is exactly the problem that shaka.deal was built to solve.** shaka.deal is a non-custodial payment router on Ethereum. It takes one incoming payment — in this case, 75,000 USDC from the startup — and routes it simultaneously to every party at preset percentage shares, in a single transaction, with finality. | Party | Share | Amount routed | Approx. AUD | | --- | --- | --- | --- | | Researcher | 20% | 15,000 USDC | ~AUD 23,100 | | Developer | 25% | 18,750 USDC | ~AUD 28,875 | | Motion designer | 15% | 11,250 USDC | ~AUD 17,325 | | Agency | 40% | 30,000 USDC | ~AUD 46,200 | The four shares all land in their respective wallets at the same moment, in the same block, from the same payment event. No sequential transfers. No holding period. No one waiting on anyone else. The key point: shaka.deal routes, it never holds funds. The startup sends once. Every party receives simultaneously. The routing is transparent and verifiable on-chain by anyone with a block explorer. ## Setting up a shaka.deal routing arrangement The setup process is straightforward, but it requires agreement on shares before the engagement begins — which is itself a healthy professional discipline. Before the first milestone, the parties agree on percentage splits. Those splits are configured as the routing rule on shaka.deal. When the client sends each milestone payment to the shaka.deal routing address, the contract executes the split automatically. No one needs to trust anyone to forward funds. No one waits. There is no human step between payment arrival and distribution. For the agency-plus-team scenario above, the wallet addresses and percentage shares of each party are agreed and locked at the start of the engagement. When the startup sends 25,000 USDC (approximately AUD 38,500) for the milestone-one payment, shaka.deal routes 5,000 USDC to the researcher, 6,250 USDC to the developer, 3,750 USDC to the motion designer, and 10,000 USDC to the agency — simultaneously, in one transaction. What this does for the professional relationship is significant. The researcher does not need to invoice the agency and wait. The developer does not need to trust that the agency received the wire before sending theirs. Each party has on-chain proof of receipt the moment the milestone payment is processed. Disputes about "I haven't been paid yet" become structurally impossible. This same model applies beyond agency teams. A solo consultant who shares a percentage of project revenue with a strategic referral source. A law firm that routes client payments across multiple attorneys of record. A settlement agent distributing proceeds across parties to a deal. A production company splitting creative fees among director, producer, and music licensor. The mechanics are identical: one incoming payment, preset shares, simultaneous distribution, final settlement. ## Invoicing in stablecoin: what to write, what to specify Your invoice is a legal document, not just a payment request. For stablecoin deals, it needs to carry more detail than a standard invoice. **Price in USD, specify payment in stablecoin.** As one practical guide puts it: "Price your work in dollars and state that payment is due as an equivalent amount in USDC or USDT. For example: 'Project fee: $2,000, payable as 2,000 USDC on Base.' This removes any ambiguity about exchange rate or unit." Every stablecoin invoice should include: - **The USD amount** (the commercial amount that governs the contract) - **The stablecoin equivalent** (the token, the quantity, the peg assumption) - **The network** (Ethereum mainnet, Base, Arbitrum, Polygon, etc.) - **The receiving address** — either your personal wallet or the shaka.deal routing address if you are distributing to multiple parties - **The milestone it corresponds to** and the acceptance event that triggered it - **The transaction hash from any previous payment**, to create a clean audit chain For the AUD-denominated reader: always include both currency figures on the invoice if your commercial context requires it. A project priced at USD 10,000 is approximately AUD 15,400 at the time of writing. The invoice should show both, denominated clearly, because your accountant and your tax authority will need the local currency equivalent regardless of how payment arrived. ## Tax, compliance, and recordkeeping Stablecoin income is not a tax grey area. Stablecoin payments are treated as income at fair market value upon receipt. A freelancer receiving $5,000 USDC must report $5,000 income regardless of whether they hold the asset or immediately convert it into fiat. In the United States, you owe income tax on the dollar value at the time you received it, and you owe capital gains only if the stablecoin's value diverges from $1 between receipt and spend — which for USDC and USDT in practice means effectively never. Starting with 2025 transactions, brokers must also report gross proceeds from digital asset transactions on Form 1099-DA. Maintain records of each payment: date, amount, fair market value in USD, and the transaction hash for audit purposes. The transaction hash is your receipt. On Ethereum and any EVM-compatible chain, every transaction is permanently recorded on the public ledger and retrievable by anyone with the hash. For a freelancer, this is a gift for recordkeeping: the timestamp, amount, sending address, and receiving address are immutably recorded. There is no "the wire got lost" or "the bank can't find the transfer." The payment either happened at a specific block height or it did not. Milestone payments create accounting timing questions you must understand to avoid surprise tax bills. Per IRS Publication 538, if you use cash-basis accounting — as most US freelancers do — each milestone payment is taxable income in the year you receive it, not the year you complete the work. This means a 50% upfront payment in December 2026 is 2026 income even if the project finishes in March 2027, triggering Q4 2026 estimated tax obligations. For Australian freelancers: the ATO's position on crypto income is equally clear — income is recognized at the AUD equivalent at the date of receipt. Keep a record of the exchange rate at the time of each transaction. Block explorer timestamps make this straightforward. If you are operating as an agency and routing payments through shaka.deal to subcontractors, each party's receipt is their own taxable event. Your routing is a distribution, not a revenue event for the portions that pass through to others — but your accountant should be aware of the structure and should document it clearly at the outset of the engagement. ## Protecting yourself when the startup is pre-revenue or pre-series Startup clients are not all the same risk. A Series B company with $20 million in the bank holding USDC is a very different counterparty from a pre-seed team of two with six months of runway and an experimental treasury. Stablecoin payment does not eliminate counterparty risk — it eliminates payment execution risk once the client has sufficient funds and agrees to pay. Before engaging a startup treasury client, do the basics: **Verify the treasury exists.** It is reasonable to ask for a block explorer link to the wallet that will be paying you, showing a balance sufficient to cover at least the first milestone. You are not auditing their finances — you are confirming the payment mechanism works. **Front-load the milestone structure.** For startup clients, a 40% or 50% deposit before work begins is not aggressive — it is standard practice. The 50% upfront deposit is industry standard for projects under $10,000 and protects against client ghosting. The same logic applies at higher values. A startup that cannot clear your opening milestone probably cannot clear the rest. **Require wallet address confirmation in writing.** Before configuring any routing on shaka.deal, the sending wallet should be confirmed in a written amendment or schedule to the contract, and the receiving addresses for all parties should be confirmed and documented. Wallet address errors on-chain are not reversible. **Define what happens if the startup raises, is acquired, or winds down mid-project.** A change-of-control clause and a kill fee (typically a percentage of the total fee scaled to project progress) should be standard in any engagement with a pre-revenue or early-stage client. ## The cash flow reality: converting USDC when you need fiat Receiving USDC is one thing. Paying rent, supplier invoices, or your own team in local fiat is another. The off-ramp workflow matters and should be planned before the engagement begins. For a freelancer in a high-inflation economy, getting paid in USDC is functionally identical to getting paid in dollars, without the friction of opening a foreign bank account. For freelancers in AUD, GBP, EUR, or other stable currencies, conversion is typically a two-step process: USDC to a centralized exchange, then exchange to local fiat and withdrawal to a bank account. Most major exchanges process this in under 24 hours, and the fees are far lower than a SWIFT wire spread. A USDT or USDC transfer settles in minutes, costs under $1 on most chains, and arrives in your wallet pegged 1:1 to the US dollar. That means the cost difference between stablecoin and wire is not trivial at project scale. On a $50,000 (approximately AUD 77,000) project, a 3% wire spread costs $1,500 (approximately AUD 2,310). Stablecoin settlement on an L2 network costs a few cents. That margin belongs in your pocket — or can be offered back to the client as a price incentive for paying promptly. Plan your conversion cadence around your actual cash flow needs, not the market. If you need AUD on the 15th to meet obligations, ensure your USDC arrived at least 24 hours prior with enough time for exchange processing. Build that buffer into your milestone acceptance timelines. ## When you are the settlement coordinator, not just the payee Some freelancers operate as the primary contractor who manages a team, receives the full client payment, and distributes shares to contributors. This role — sometimes called a lead, a producer, or a principal contractor — carries the most complexity in a stablecoin deal. Without a routing tool, you are the manual settlement layer: receiving full payment, maintaining a spreadsheet of shares, making individual transfers to each person, generating your own transaction records, and managing the trust of your collaborators who are waiting on you to forward funds you have already received. This creates professional risk, operational friction, and delay that erodes your team's confidence in the arrangement. With shaka.deal configured at the outset, you are not the settlement layer — the protocol is. You provide the client with the routing address. The client sends one payment. Every party receives simultaneously. Your job is not to forward money; your job is to manage the relationship, the deliverables, and the professional quality of the output. This distinction matters for professional credibility. A researcher or developer who has worked with a lead contractor before and received their share within the same block as the client's payment — not days later — trusts that arrangement. They will work with you again. They will refer you. They will price their contribution at market rate rather than adding a delay premium because they have seen that payment works. ## A complete worked example: the brand-and-build engagement To make this concrete: a design and development studio closes a $120,000 (approximately AUD 184,800) engagement with a DeFi startup. The client holds USDC on Ethereum mainnet. The deal involves the studio (50%), a brand strategy consultant (20%), a development lead (25%), and a licensing fee to a type foundry (5%). The contract specifies payment in USDC on Ethereum, with four milestones. Each milestone amount in USD and USDC is specified on the invoice. | Milestone | Share of fee | Payment | Approx. AUD | | --- | --- | --- | --- | | On signing | 30% | $36,000 USDC | AUD 55,440 | | Wireframe approval | 20% | $24,000 USDC | AUD 36,960 | | Development handoff | 30% | $36,000 USDC | AUD 55,440 | | Final acceptance | 20% | $24,000 USDC | AUD 36,960 | The studio configures a routing arrangement on shaka.deal with four wallet addresses and the corresponding percentage splits. The client sends each milestone payment to the shaka.deal routing address at each approval event. At each milestone, the funds clear simultaneously: the studio's share, the consultant's share, the developer's share, and the type foundry's licensing payment all land in their respective wallets in the same transaction. The studio does not touch the other parties' funds. The transaction hash for each milestone settlement is appended to the project record. Every party has independent proof of receipt. The final delivery triggers the last payment with complete, documented settlement. The project closes cleanly. The tax records are straightforward — each party received their amounts at specific block timestamps, at a known USD value, with immutable on-chain receipts. No one is waiting for a wire. No one is chasing a manual transfer. No one has to trust the studio to forward funds it already received. ## The professional layer stablecoin doesn't replace Settlement agents, attorneys, and compliance professionals reading this should note: nothing described above removes the need for legal agreements, professional oversight, or formal compliance review on complex deals. Stablecoin payment routes money with certainty and speed. It does not write contracts, adjudicate disputes, classify workers, or handle the regulatory layer. For high-value or multi-jurisdictional freelance deals, the settlement infrastructure provided by tools like shaka.deal is the execution layer. The professional and legal layer — the contract review, the governing law analysis, the tax structure, the dispute resolution mechanism — remains the domain of qualified professionals. The two layers complement each other. Precise legal terms supported by certain, fast, auditable payment execution is a more robust arrangement than either alone. The stablecoin payment ecosystem, including routing infrastructure like shaka.deal, gives settlement professionals a better set of tools for their clients — not a reason to remove those professionals from the arrangement. ## The short version Startup clients paying in stablecoin are no longer unusual. They are increasingly the default for a specific segment of the market, and that segment is growing. According to Rise, 60% of freelancers were paid in crypto at least once in 2025, and 53% of freelancers chose to withdraw earnings in crypto even after the client paid them in fiat. Getting paid well in this environment means doing four things correctly: specifying the stablecoin, network, and finality threshold before work begins; structuring milestone payments with precise acceptance criteria; routing multi-party deals through a tool like shaka.deal so that every party receives simultaneously in one transaction with on-chain proof; and maintaining clean, timestamped records for tax reporting. The speed and finality of stablecoin settlement is a genuine advantage — for cash flow, for recordkeeping, and for professional relationships. The infrastructure now exists to use that advantage cleanly, without the friction and trust risk of manual distribution. The freelancers and agencies who build these payment workflows correctly are the ones whose collaborators keep coming back.