How to Accept Crypto Payments as a Freelancer

Get paid from any country in 60 seconds — no bank, no chargebacks, 0% fees. How freelance developers accept BTC, ETH and stablecoins straight to their own wallet.

// 5 min read · updated Aug 28, 2026

Every freelance developer knows the payment tax: PayPal takes ~5% and holds funds, wire transfers take days and $30 fees, and half the world's clients can't use your local payment rails at all. Crypto fixes the rails — a client in Berlin, Lagos or São Paulo pays you in 60 seconds, the money lands in a wallet only you control, and confirmed payments can't be charged back. Here's how to set it up properly.

1. Understand what "non-custodial" buys you

The single most important word in crypto payments. A custodial processor (most exchanges) receives the money, holds it in their account, and lets you withdraw — meaning they can freeze it, delay it, or take a cut. A non-custodial gateway never touches the funds: your client's wallet sends directly to your wallet on-chain, and the gateway just generates the payment page and verifies the transaction publicly. No middleman balance, no freeze switch, nothing to skim — which is how a tool like crypt.pe charges 0% per transaction while Coinbase Commerce takes 1% and BitPay 1–2%.

2. Lead with stablecoins, offer the majors

Clients don't want volatility lectures. Quote the invoice in USD and let them pay in USDT or USDC — dollar stablecoins that arrive worth what was invoiced. Keep BTC, ETH and SOL available for crypto-native clients. One trap to avoid: stablecoins live on many networks (a USDT on Tron is not a USDT on Ethereum), so use a payment page that labels chains explicitly rather than pasting raw addresses into an email — sending on the wrong chain loses the money.

3. Set up a payment page in 60 seconds

  1. Get a wallet you control (MetaMask, Phantom, or a hardware wallet for larger sums).
  2. Claim a handle on crypt.pe — no KYC, no company, no bank account required.
  3. Paste your public wallet addresses (never a seed phrase — no legitimate tool asks for one).
  4. Share crypt.pe/you — clients scan, pick a coin, and pay from any wallet on earth. You get on-chain confirmation and an email receipt.

Freelancers invoicing bigger clients can go further: tracked orders with locked amounts, hosted checkout, and crypto subscriptions for retainers — all settling straight to your wallet.

4. Put the payment link where clients actually see it

A payment rail nobody finds earns nothing. The highest-converting spot is your bio page — the same link you already share in proposals, README profiles and email signatures. If you run a whomi.bio profile, add your crypt.pe handle under Dashboard → Integrations and your bio gets a "get paid in crypto" card — free on every tier. A prospect reads your proof-of-work, checks your GitHub activity, and can pay the deposit without leaving the page.

5. Handle the boring parts: records and taxes

Crypto income is still income. Keep it clean: one wallet dedicated to client payments (your on-chain history becomes your ledger), save the payment receipts, note the fiat value on the day each payment lands, and check your local rules on converting to fiat. Chargebacks don't exist on-chain — which protects you from fraud, but also means you should invoice clearly and deliver before disputes can't be un-disputed.

The checklist

  1. Non-custodial gateway — funds settle to a wallet only you control
  2. Stablecoins first (USDT/USDC), majors available, chains clearly labelled
  3. One shareable payment link — crypt.pe/you, live in 60s
  4. Payment card on your bio page (claim yours free)
  5. Dedicated wallet + receipts for tax season

Next: make the page clients land on worth paying — How to Build a Developer Bio That Gets You Noticed.