How a freelancer gets paid by a startup in tokens or stablecoin
Getting paid by a web3 startup is not like getting paid by any other client. The money itself is different, the way it moves is different, and the decisions you make at the offer stage follow you for months or years afterward. Whether you’re a designer, developer, legal drafter, or growth contractor, the moment you accept work from a crypto-native startup, you step into a compensation structure that mixes cash-equivalent stablecoins with speculative native tokens — and the two are not remotely the same thing. This article covers exactly how each works in practice, what to negotiate, what to watch for, and how to make sure the money actually lands.
The two types of crypto payment you’ll encounter
When a web3 startup says it wants to pay you in crypto, it is almost certainly offering one of two things, or a blend of both: stablecoins or its own protocol tokens. Understanding the difference before you sign anything is the single most important decision you’ll make in this engagement.
Stablecoins — predominantly USDC and USDT — are dollar-pegged tokens. A stablecoin is a digital token pegged to a real-world currency, almost always the US dollar, and each token is backed by reserves held by the issuer, so one USDC is designed to always be worth one dollar. When a startup pays you 5,000 USDC for a three-week sprint, you have received, in economic terms, $5,000. You bear minimal price risk. Unlike traditional crypto payments, stablecoins don’t fluctuate daily — a freelancer paid $1,000 in USDC today can rely on that same value tomorrow. The stablecoin is not an investment. It’s a payment rail.
Native tokens are the startup’s own protocol tokens — the same asset that investors and core team members hold. They are speculative by nature. They may not yet be publicly traded. Their value on the day you receive them could be zero on paper, a dollar, or fifty dollars. They could triple in eighteen months or go to zero. This is not a payment in any conventional sense. It is an equity-like allocation wrapped in a different legal structure, and it should be evaluated that way.
Most startups will offer you a blend: a stablecoin base rate that covers your immediate income needs, plus a token allocation that gives you upside exposure to the project. Knowing which bucket any given dollar falls into is the foundation of everything else.
Getting paid in stablecoin: the mechanics
Startups in the web3 and decentralized finance sectors are increasingly turning to stablecoins like USDC and USDT for payroll, citing faster settlement and alignment with the digital ecosystem. For a freelancer, this is genuinely good news. The operational experience of receiving stablecoin payment is fast, direct, and verifiable.
Stablecoins win three properties at once: settlement is final in seconds to minutes rather than days, per-transfer fees fall to single-digit cents on most chains rather than $15 to $50 per wire, and the payment instrument is programmable. If you’ve been grinding through multi-day wire delays and $30 SWIFT fees on international client payments, stablecoin settlement changes your cash-flow dynamics in a meaningful way.
The operational steps are straightforward but precision matters. Freelancers can receive USDT or USDC by agreeing on the stablecoin token, specifying an exact blockchain network, sharing a wallet address that supports that network, and requesting a small test payment before the full transfer. That last step — the test payment — is not paranoia. It is professional practice.
The network is the most common point of failure. Choosing the wrong one can make funds disappear from view, even if the transaction completed. Your Ethereum address and your Arbitrum address may be the same string of characters for EVM-compatible chains, but the assets exist on separate networks. If your startup sends USDC on Base and you’ve shared an Ethereum mainnet address, the funds may land on a network your wallet isn’t actively displaying. Always confirm the chain explicitly. Not the token. Not just the address. The chain.
Which stablecoin to request
The two dominant options are USDC and USDT, and they are not interchangeable from a regulatory or counterparty standpoint, even if they both read as “$1.00” on your screen.
USDC is preferred by freelancers and companies seeking compliance documentation. Circle’s payment APIs and partnerships with PayPal and other fintech platforms make USDC more practical for invoicing and payroll in regulated environments. If you are in the US or EU, USDC is generally the cleaner choice for record-keeping, and Circle’s reserve attestation cadence gives you more transparency about what backs the dollar you’re holding. USDT on Tron is popular for low-cost, high-speed international transfers, particularly in emerging markets, while USDC is increasingly used by businesses and payroll providers in the US and EU.
USDC and USDT handle the majority of business payout volume. USDC is favored for its compliance posture and reserve attestations, USDT for deep liquidity in emerging markets, and EURC for euro-denominated payouts. If your startup’s treasury is predominantly USDT and you’re based in Southeast Asia or Latin America, there is nothing wrong with accepting USDT. The practical question is: which stablecoin can your client send most easily, and which can you off-ramp most efficiently in your market?
The network question isn’t an afterthought
A USDC transfer on Solana finalizes in roughly 400 milliseconds. On Ethereum L2s like Base, Arbitrum, and Optimism, soft confirmation arrives in about 2 seconds. Most web3 startups operate on one of these faster, cheaper chains rather than Ethereum mainnet, where congestion can make small transfers expensive. Know which chain your client uses for treasury operations before you share your wallet address, and make sure your wallet is configured to receive on that specific network.
The practical invoice line should read something like: “Project fee: $4,500, payable as 4,500 USDC on Base.” Specifying the dollar amount, the token, and the network in writing removes every point of ambiguity.
Getting paid in native tokens: a completely different conversation
When a startup offers to pay part of your compensation in its own protocol token, you are no longer in payment territory. You are making an investment decision, and you should treat it as one.
The structure: vesting, cliffs, and lockups
A web3 professional’s compensation package often includes a significant grant of the protocol’s native tokens. For freelancers, the structure typically differs from what full-time team members receive. For DAOs and projects that rely on freelance contributors, the model is different. Compensation is typically project-based rather than time-based. Bounties are small, one-off tasks with a fixed token payment upon completion, with no vesting. For larger engagements, you may encounter grant structures where tokens are paid in tranches tied to milestone delivery, sometimes with a short vesting tail to keep you engaged after the work ships.
Token compensation almost always carries a vesting schedule. While vesting periods as short as six to twelve months with no cliff exist, a standard vesting schedule of four years with a one-year cliff is more common. If you’re taking on a longer-term contractor role that blurs the line between freelance and core team, you may encounter this four-year structure. Understand it precisely before you sign.
The cliff refers to a waiting period at the beginning of a vesting plan, during which no tokens become accessible. Once the cliff ends, token unlocking begins — typically in monthly intervals — over a set vesting period. A one-year cliff means that if you disengage from the project before your anniversary date, you leave with zero tokens regardless of how much work you delivered in month eleven. Even a generous token or equity number can be misleading if you do not understand vesting and unlock schedules. In web3, these details matter a lot.
On top of vesting, there may be a separate lockup — a restriction on transferability even after tokens vest. Lockups can apply to both investors and core team members, and they’re used to manage token supply and market dynamics. This aligns token holders to the same unlock dates, because you don’t want any stakeholder to sell immediately upon launch or ahead of anyone else. A token that vests in month twelve but can’t be sold until month twenty-four is not a liquid asset. Model that into your rate.
The pre-TGE problem
One of the thorniest situations in freelance web3 compensation is being offered tokens in a project that has not yet had its Token Generation Event — where the token exists internally but has no public market, no listed price, and no immediate path to liquidity.
Lockups may be implemented by pre-TGE companies, meaning the tokens you receive today cannot be sold until after the project launches publicly, which may be many months away, and even then only after any post-TGE lockup period expires. In the meantime, you cannot know what those tokens will be worth at the moment you can actually sell them. The token could launch at a price that values your grant at ten times what you expected, or it could never launch at all.
If a startup is offering you pre-TGE tokens as a meaningful share of your total compensation, the right response is not to refuse — it may be a legitimate upside opportunity — but to price your stablecoin base rate as if the token allocation doesn’t exist. Take the tokens as speculative upside on work you’ve already been paid for in real money. Do not discount your invoice rate in exchange for illiquid pre-launch tokens.
How to evaluate a token grant
Don’t just look at the current USD value. You must analyze the project’s tokenomics, the token’s utility, the vesting schedule, and the overall potential of the project.
In practice, this means asking: What is the total token supply? What percentage of supply does the team allocation represent? Are investors and founders subject to the same lockup timelines as contributors? What is the token’s utility within the protocol — does demand for the token grow as the protocol grows, or is it purely speculative? Is there an existing market, or does this require a TGE that may or may not materialize?
To minimize the outsized impacts of day-to-day price swings common in tokens for any of these vesting schedules, consider using something like a 90-day moving average when pricing grants and refreshers. If your startup quotes your token allocation as “$50,000 worth of tokens” based on a single day’s price, that number could be dramatically different — in either direction — by the time your cliff hits. A 90-day average is a fairer basis for calculating the real value of what you’re being offered.
The tax mechanics you cannot afford to ignore
Crypto payments — stablecoin or token — do not exist outside the tax system. Every jurisdiction that recognizes digital assets as property treats receipt as a taxable event, and web3 startups are no exception to the reporting requirements that apply to any client relationship.
The income recognition moment
In most jurisdictions, receiving stablecoins as payment for services is a taxable event — the fair market value of the tokens at the time of receipt counts as ordinary income, just like a bank deposit. This is the foundational rule, and it applies whether you receive USDC, USDT, or a native protocol token. If you’re a freelancer or self-employed, your crypto earnings count as taxable income. Whether you get paid in Bitcoin, earn staking rewards, or receive tokens through mining or airdrops, the value of the crypto at the time you receive it is considered income. This income needs to be reported and is usually subject to income tax.
For stablecoins, the practical impact is minimal: you received $5,000 worth of USDC, you report $5,000 of income. The subsequent gain or loss when you off-ramp to fiat is negligible because the peg is stable. If you hold the stablecoins and later convert them to fiat or another crypto asset, any gain or loss from that conversion is a separate capital gains event. For USDT and USDC, the gain is typically negligible since the price stays near $1.00, but you still need records.
For native tokens, the income recognition moment is more consequential. If a startup deposits 10,000 of its protocol tokens into your wallet at a moment when each token is priced at $0.40, you have received $4,000 of income — and that’s what you report, regardless of what those tokens do afterward. If you hold them for six months and they climb to $2.00, the subsequent gain from $0.40 to $2.00 is a capital gains event when you eventually sell. When you sell, trade, or convert crypto you’ve earned, it becomes a taxable event. This could mean capital gains or losses.
Basis tracking is your responsibility
A token grant can create three numbers on the same day: compensation expense, taxable income, and a cost-basis lot. In web3 accounting, that is where clean books usually start to fail.
For every crypto payment you receive, record the date, the token and amount, the USD-equivalent value, the transaction hash (TXID), and the client name. Do this at the time of receipt, not at year-end when you’re staring at a wallet with dozens of inbound transactions and no context attached to any of them. The token’s fair market value at receipt is your cost basis for every lot you later sell. If you receive token grants in monthly tranches, each month’s vest is its own basis lot at that month’s price.
Independent contractors receiving crypto payments must report the fair market value on Form 1099-NEC if annual payments exceed the applicable threshold. Your startup client has its own reporting obligations, but your responsibility to report the income exists whether or not a 1099 arrives. The on-chain record is public and permanent.
The legislative landscape is shifting
If you receive payment in a regulated payment stablecoin, proposed legislation would generally provide nonrecognition of gain or loss on dispositions — meaning you wouldn’t owe tax simply from converting or transferring the stablecoin, as long as your cost basis stays close to its $1 redemption value. This would effectively treat regulated stablecoins more like cash for tax purposes. This is a significant shift. Right now, even stablecoin transactions can technically trigger gain or loss. The proposed treatment would make stablecoins function more like the near-cash instruments they’re designed to be.
These proposals have not yet become law, and the rules that apply to you today remain unchanged. But the direction of regulatory travel is toward treating compliant stablecoins as near-cash, which matters for how you structure your payment preferences with clients going forward.
Negotiating your rate: how to think about compensation structure
When a startup approaches you with a blended compensation offer — some stablecoin, some tokens — the negotiation should be grounded in the same logic you’d apply to any offer that mixes cash and illiquid equity.
Your base rate is non-negotiable on quality
The stablecoin portion of your compensation should reflect your market rate for the work. Not a discounted version of it. The fact that a startup is exciting, or early-stage, or building something genuinely important in the ecosystem does not change the value of your time. The token component is the speculative premium — it’s what you’re accepting in exchange for the possibility that the project succeeds. It is not a substitute for being fairly paid on the cash side.
Consider asking for performance bonuses or a portion of your compensation in stablecoins for income stability. If a startup is pushing hard to pay you primarily in tokens, the honest response is to ask what percentage of the core team’s compensation is token-denominated. If the founders are drawing dollar salaries while asking contractors to take tokens, that asymmetry tells you something important about how much faith the founders themselves have in the token’s short-term value.
What’s actually negotiable
In web3, almost every component of your package is negotiable in some way. Token and equity grant size can be discussed — ask how your grant compares to others at your level and clarify whether increasing it is possible. For senior or critical roles, it is often reasonable to request a shorter cliff or partial acceleration on certain milestones.
For project-based freelance work, ask for milestone-based stablecoin payments rather than a single payment at completion. This protects you from the scenario where the project stalls or the startup runs out of runway before your final deliverable. Structure your contract so that a meaningful portion of the stablecoin payment lands before you’ve completed the bulk of the work — not as distrust of the client, but as normal professional cash flow management.
If the token component is large relative to the stablecoin base, negotiate explicitly for the vesting terms in your contract. A token that vests after one year with a twelve-month cliff is very different from a token that vests monthly from day one with no cliff. For a three-month engagement, monthly vesting means you can actually receive something. A one-year cliff on a three-month contract means you receive nothing from the token side unless you stay engaged with the project far beyond the original scope.
The payment itself: how it lands and what happens next
When a startup pays you in stablecoin, the transaction is direct, final, and immediate. Stablecoin payments bring unprecedented visibility into financial operations. Every transaction — sender, receiver, amount, timestamp — is verifiable on-chain, which reduces disputes, simplifies auditing, and builds trust between employers and freelancers.
From a practical standpoint, there’s no “bank in transit” ambiguity. You either have the funds in your wallet or you don’t. This transparency protects freelancers, who can verify when and where their payments were made — no more “bank in transit” uncertainty.
When a project involves multiple contributors — a common reality in web3, where a startup might be paying a developer, a designer, and a legal advisor across the same sprint — coordinating who gets paid how much, from which wallet, and in what proportions becomes a real operational friction. This is exactly where a tool like Shaka earns its place: the startup creates a single payment link, sets each contributor’s wallet address and their split percentage, and a single transaction splits the funds automatically, landing directly in each wallet simultaneously. The payment is final. There’s no round-tripping, no manual distribution, no one person holding the funds while they figure out who owes what.
Off-ramping to fiat: your options
If you need your USDC or USDT in your local currency, the process is straightforward but involves a choice of exchange and sometimes a meaningful friction point depending on where you are. Most major exchanges and payment platforms let you convert stablecoins to fiat. Conversion ease depends on exchange liquidity, regional fiat on-ramps, and platform fees.
The blockchain part of stablecoin payments largely works, but the moment you need to convert between a stablecoin and a local fiat currency, the infrastructure there introduces major friction. Most real-world payment flows require touching local fiat at some point. For freelancers in markets with robust exchange infrastructure — the US, EU, UK, Singapore, Australia — this is a minor operational step. For freelancers in markets with thinner off-ramp infrastructure, the conversion process may involve higher spreads or fewer options.
For freelancers in countries with weak banking infrastructure, high inflation and financial turmoil, receiving payment in USDC or USDT provides financial stability and protection against local currency devaluation. In those contexts, holding USDC rather than converting to local fiat may be the financially rational choice, not because of crypto speculation but because the dollar peg beats the local currency’s performance.
Security: your wallet is your responsibility
When a startup sends payment directly to your self-custody wallet, you control the funds from the moment they confirm. That is the upside. The downside is that there is no institution to call if you lose access. Security risks, including hacks, phishing attacks, or lost private keys, also pose serious threats since crypto transactions are generally irreversible.
Use a separate wallet for business payments. Keep the recovery phrase offline, physically. For any amount that represents meaningful income, consider moving funds off a hot wallet to a hardware wallet. These are not technical considerations that require deep blockchain expertise — they’re the equivalent of keeping your professional accounts separate from your personal accounts, which any competent freelancer already does.
When to push back on the token-heavy offer
There are legitimate reasons a startup wants to pay contractors in native tokens — treasury management, alignment, avoiding cash burn — and there are bad-faith reasons. The legitimate version is: “We believe in this project, we want contributors who believe in it too, and we want you participating in the upside.” The bad-faith version is: “We don’t have the stablecoin liquidity to pay you fairly, so we’re offering you something we can mint.”
Be cautious if a client offers an obscure or unknown coin, if there is no contract, or if local laws restrict crypto use. An obscure native token from a project with no public market, no published tokenomics, and no verifiable on-chain treasury is not compensation. It’s a promise. A promise may eventually be valuable, but you cannot pay rent with a promise, and you cannot report it as income at a value that doesn’t exist.
If a startup can’t or won’t pay any portion of your engagement in a recognized stablecoin, that is a significant data point about the health of the business. Legitimate, well-funded web3 projects pay in stablecoins for base compensation and offer tokens as an additional incentive. A project that can only offer tokens may be illiquid, or may not have the operational maturity to structure a legitimate contractor relationship. Either way, price your risk accordingly — which usually means requiring a larger token allocation to compensate for the illiquidity premium, or walking away from the engagement entirely.
The practical reality of getting paid by a crypto startup is that the tools now exist to make it work cleanly. Stablecoins settle faster than wires, cost less than international transfers, and leave a verifiable record that makes accounting and tax reporting straightforward. Native tokens are a different animal entirely — part compensation, part investment, part incentive — and they require you to think carefully about vesting structures, liquidity timelines, and the real probability of the project succeeding. The freelancers who navigate this well are the ones who separate the two clearly in every contract they sign: one line for the payment, one line for the bet. The work gets paid today in something stable. The upside follows, if the project earns it.
