Crypto Payroll for Freelancers: Pay the Whole Team in One Batch

Why paying a freelance team is harder than hiring one

Hiring a distributed contractor team is now trivially easy. A design lead in Lisbon, three writers in Buenos Aires and Bogotá, two React developers in Belgrade, a video editor in Manila, a bookkeeper in Nairobi — you can assemble that in a week. Paying them every month is the part nobody warns you about.

The monthly run usually looks like this. Invoices arrive between the 28th and the 3rd, in five formats. Someone tallies them into a sheet. Then the payments start, and they are not one payment — they are a dozen different systems. Two people take a domestic transfer because they happen to be in your country. Six are on one contractor-payment platform. Four are on another, because the first one does not support their country. Three want a bank wire, which means a form per person, an intermediary bank field nobody understands, and a $30–45 fee. One person's account was closed last month and they have not told you yet. And every single one of them will message you on the 5th asking whether it went out.

That is the operational half. The financial half is worse, and it is invisible to you because it lands on the freelancer. The World Bank's Remittance Prices Worldwide database has tracked the global average cost of sending small cross-border amounts above 6% for years, with banks consistently the most expensive channel of all. On a wire, each correspondent in the chain can deduct its own charge, which is why a freelancer who invoiced $1,200 sometimes reports $1,148 arriving with no explanation of where the rest went. Then their local bank converts at a spread you never see.

So the real cost of your freelance payroll is not the fee on your statement. It is that number plus the cut taken out of your contractor's fee — and your contractor prices that in.

What the monthly payment run actually costs you

Start with the hours. Most teams we talk to spend somewhere between half a day and two full days per month on the run itself: consolidating invoices, re-keying account details, chasing a rejected transfer, answering "has it been sent?" messages, then reconciling what actually left the account against what was supposed to. Two days a month of an operations person is roughly a month of their year. For a twenty-person freelance bench, that is the single most expensive administrative process in the company and it produces nothing.

Then the leakage. If your contractors are losing 4–8% between your bank and theirs, that money does not vanish into the ether — it comes back to you as higher rates at renewal. Freelancers are ruthless about effective hourly. The ones who track it will quietly quote you 5% more than they quote a client who pays them cleanly, and they will never tell you why.

Then retention, which is the part that actually hurts. The best contractors have more work than time and they optimise for clients who are easy to work with. "Pays on time, pays in full, no chasing" is a competitive advantage in a market where late payment is normal. When a freelancer has to choose between two clients for next month's capacity, the one whose money arrived in nine seconds and matched the invoice to the cent wins — and the one whose transfer bounced twice does not get told, they just get less availability.

And finally the reconciliation tail. Weeks later, your accountant asks what a $47 debit on the 3rd was. Nobody knows. It was an intermediary bank fee on a wire to Manila. Multiply by twelve months.

Why wires, PayPal and card rails fail for contractor payouts

This is not incompetence on anyone's part — it is structural. Traditional cross-border payment was designed for a world of relatively few, relatively large transfers between institutions that know each other, not for forty $900 payments a month to individuals in fifteen jurisdictions.

Correspondent banking is a chain, not a link

There is no direct pipe between your bank in one country and your freelancer's bank in another. The money hops through correspondent institutions, each of which applies its own fees, its own compliance checks and its own business hours. The chain sets your speed (days, not seconds), your cost (each hop) and your failure mode (a hold at an intermediary you have no relationship with and cannot call).

"Batch" usually means "a loop"

Most business banking portals let you upload a payment file, and then process it as a sequence of individual transfers, each subject to its own fee, cut-off time and rejection. Uploading fifty rows does not make it one payment; it makes it fifty payments you did not have to type. That is a real improvement in typing and no improvement at all in cost or coverage.

Coverage is decided by someone else's risk appetite

Whole countries are effectively off the menu. Contractor-payment platforms and banks de-risk entire corridors, and when they do, your freelancer's country simply disappears from a dropdown. You then discover it on payday. This is why teams with contractors in Argentina, Venezuela, Nigeria, Pakistan or Lebanon end up running two or three payment systems in parallel — not by choice, but because no single one covers the roster.

Custody adds a step that can stall

Most contractor-payment tools are custodial: you prefund their balance, they hold your money, and they release it on their schedule. That float belongs to you but sits with them, and any compliance review, weekend or platform incident happens after you have already paid. Your money is out of your account and not yet in your contractor's. The custodial-versus-non-custodial distinction is invisible right up until the day it is the only thing that matters.

How crypto payroll for freelancers works with Payzum

Payzum is a non-custodial, crypto-only payment processor. For contractor payouts, that sentence has a very literal operational meaning: Payzum never holds the money you are about to pay out. There is no balance to top up, no prefunding, no "available on" date. The stablecoins sit in a wallet you control until the batch executes, and then they move on-chain from your wallet to each freelancer's wallet. Settlement is the payment.

That single property removes most of the failure modes above at once. There is no float sitting with an intermediary, so there is nothing to be held during a review. There is no correspondent chain, so nobody deducts a fee mid-flight. There is no acquirer or sponsor bank deciding your contractor's country is now out of scope.

The instruments you actually use

• Stablecoin payouts on EVM networks. USDC or USDT on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche. These are the workhorse rails for a freelance run: a payout costs cents in network fees, and Base and Polygon confirm in roughly two seconds. The freelancer receives dollars-denominated value, so the invoice figure and the received figure are the same number.
• CSV mass payouts. One row per recipient — address, amount, optional reference — for batch payouts in BTC, LTC and DOGE. Useful when part of your bench specifically wants to be paid in bitcoin, which is more common among long-tenured crypto-native contractors than most finance teams expect.
• Auto-convert on the collection side. If your own revenue arrives in crypto, Payzum can auto-convert incoming payments to USDC or USDT, so the wallet you pay contractors from holds stable value rather than something that moved 9% over the weekend.
• Controls that make it auditable. 2FA on the account, encrypted secrets, and a complete audit log — who created the batch, who approved it, what was sent, to which address, when, and the transaction hash for every single line.
• API and signed webhooks. A REST API with API keys and signed webhooks, so the run can be triggered from your own system and each completed payout can post back to mark the invoice paid without anyone updating a spreadsheet.

What Payzum is not — and this matters for payroll

Be clear about scope, because "payroll" is a loaded word. Payzum is a payment rail. It is not an employer of record, not a payroll bureau, not a compliance service, and not a tax adviser. It does not classify your workers, does not calculate withholding, does not file anything, and does not decide whether the person you are paying is a contractor or an employee under their local law.

That distinction is not a disclaimer bolted on the end; it is the design. You keep your contracts. You keep your invoices. You keep whatever reporting your jurisdiction requires — in the United States, for example, payments to independent contractors are reported on Form 1099-NEC regardless of what the payment was denominated in. Changing the rail your money travels on changes none of that, and any provider that implies otherwise is selling you a problem.

What changes is the mechanics: speed, cost, coverage, custody and the quality of your audit trail. Which, on a forty-person freelance bench, is quite enough.

How it works, step by step

1. Set up the account and the wallet you will pay from. Create the Payzum account, complete KYC, enable 2FA, and connect the wallet that will fund payouts. It stays yours — Payzum never takes custody of it. Most teams keep a dedicated payouts wallet funded with USDC or USDT for the coming run, separate from treasury, so the monthly amount at risk is bounded and easy to reconcile.
2. Collect payout details once, not every month. Ask each freelancer for a wallet address and the network they want to receive on — for most people that will be USDC on Polygon or Base. Store it against their record the same way you store their bank details today. Send a small test payment the first time and have them confirm receipt; do that once, at onboarding, and never again.
3. Build the batch from your invoice list. Export the approved invoices into the CSV layout — one row per contractor with address, amount and a reference such as the invoice number. This is the step where the money is actually decided, so it deserves the same review as any payment file: check the row count against the invoice count, check the total against your approved total, and check that no address changed since last month. A changed address is the single highest-risk event in the whole process and it should require a phone call, not an email reply. See the mass payouts guide for the file format and the full pre-flight checklist.
4. Approve once, and it is done. Upload, review the totals Payzum shows you, and approve with 2FA. The batch executes on-chain: on Base or Polygon each payout confirms in around two seconds and costs cents in network fees. Every line comes back with a transaction hash. Your signed webhook can push each completed payout straight into your accounting or ops tool to mark that invoice paid, so reconciliation is finished at roughly the same moment the payments are.

There is no cut-off time in that sequence, no business day, and no fifth-of-the-month "has it arrived?" thread. If you run the batch at 9pm on a Saturday because that is when the invoices were finally approved, everybody is paid at 9pm on a Saturday.

Use cases: what a freelance crypto payroll run looks like

Four concrete shapes, all built from the same pieces:

• The content agency with a bench in eleven countries. Thirty-eight writers and editors, invoices between $300 and $2,400, paid on the 1st. Today it is three platforms and four wires and a day and a half of an ops manager. On stablecoin rails it is one file, one approval, thirty-eight transaction hashes, and an ops manager who has their Monday back. The writers in Argentina and Nigeria — the two who currently cost the most to pay and complain the most about deductions — become the easiest two on the list.
• The dev shop paying a sprint bonus mid-cycle. A client accepts delivery early, and the studio wants the five contractors who pulled it off to see the bonus the same afternoon, not in the next month's run. A small ad-hoc batch to five addresses, approved from a phone, confirmed in seconds. The gesture keeps its value because it is immediate; a bonus that lands three weeks later is just a line on a statement.
• The solo founder with six recurring contractors. No finance team, no procurement. The founder keeps a payouts wallet with next month's USDC in it, and the monthly run is a six-row file and one approval on a Sunday night. The interesting part is not the speed — it is that at no point does anyone else hold the money, so there is no platform balance to top up ahead of time and nothing to withdraw at the end.
• The mixed bench: stablecoins for most, BTC for a few. Long-tenured crypto-native contractors sometimes want to be paid in bitcoin and are happy to carry the volatility themselves. Run the stablecoin payouts on an EVM network for the majority and a CSV batch in BTC or LTC for the handful who ask, and both settle the same evening. The bookkeeping is identical: one hash per person per month.

Worth noting the symmetry: the same rails your freelancers receive on are the ones they can bill their own clients through. Several of ours started as recipients and later set up their own USDC invoicing because being paid this way once made the case for them better than any article could.

Stablecoin payouts vs wires and contractor platforms

Common objections, answered

"Half my freelancers do not use crypto."

True on day one, and the honest sequencing is: do not migrate everyone. Start with the contractors who are already asking for it — on most international benches that is 20–40% — plus the ones in the corridors where your current rail hurts most. Those two groups overlap heavily. The rest keep their existing method until they ask to switch, and in our experience they do ask, once they hear from a colleague that the money arrives the same day and the full amount. A rail that runs alongside your existing one for a few months is a much easier internal sell than a cutover.

"Is paying contractors in stablecoins a way around taxes?"

No, and you should treat anyone who implies it is as a liability. The obligation attaches to the payment, not the rail. You still have a contract, they still issue an invoice, you still book the expense, and you still file whatever your jurisdiction requires for payments to independent contractors. What changes is that the payment is more traceable, not less: every line has an immutable on-chain record and a hash you can hand your accountant. That is generally an improvement over "a $47 unexplained debit on the 3rd". This is general information, not tax advice — confirm the treatment with your accountant.

"What about volatility? I cannot pay someone in something that moves."

That is exactly why the run is denominated in stablecoins. USDC and USDT are dollar-denominated: a $1,200 invoice is a 1,200 USDC payout, and the number the freelancer sees is the number on the invoice. If your incoming revenue is in other crypto, auto-convert on the collection side means the wallet you pay from holds stable value by the time payday arrives. Volatility becomes a choice someone opts into — as with the contractors who specifically ask for BTC — rather than a risk the process imposes on your team.

"What if we send to a wrong address? On-chain payments are irreversible."

They are, and that is the same property that makes them final and unrecallable in your favour — so the control has to sit before the send, not after it. In practice: collect and verify each address once at onboarding with a small test payment; store it in your own records, not in a chat thread; require a phone or video confirmation for any address change (address-change fraud by email is the single most common attack on payment operations); and review the batch totals and row count before approving. The pre-flight checklist in the mass payouts guide covers this properly. Every line is logged with its hash, so if something did go to the wrong recipient you know precisely what and when — which is more than a wire gives you.

"We already use a contractor-payments platform."

Many teams keep one. The split that works is by corridor and by cost: keep the platform for the countries it serves cheaply and where your contractors are happy, and move the expensive, slow or unsupported corridors onto stablecoin payouts. The two do not conflict, and running both for a quarter gives you a real cost comparison instead of a projected one. What you cannot get from a custodial platform, at any price, is the property that nobody holds your float — which is also why some teams eventually move the whole run.