A stablecoin payroll playbook for distributed teams

Three remote-first companies. Three different approaches. One shared conclusion: SWIFT and EOR fees were eating somewhere between 4% and 11% of payroll, and stablecoin USDC payouts cut that by 80-90%. The useful parts were accounting, custody, and regional off-ramps.

The starting position

All three companies were paying contractors in 20+ countries through some combination of:

• Wise / Payoneer for low-friction wires (1.5–3% per transfer)
• An Employer-of-Record for jurisdictions that required local employment (8–12% on top of gross)
• SWIFT for the long-tail edge cases ($30–50 flat + intermediary fees + 2–5 day settlement)

"We were paying nearly $80K a year just to move payroll. Not the salaries, the act of moving them." Finance lead, ~80-person SaaS

What they kept

A few things did not change:

1. Local employment in jurisdictions that require it. Stablecoins don't replace employment law. If you have full-time employees in Germany, you still need a German employer entity (yours, or an EOR's).
2. Tax withholding for US W-2 employees. Federal and state withholding still flows through ADP / Gusto / Rippling.
3. Gross-to-net calculation. Whatever payroll engine you use to compute the net amount is still the source of truth.

What they replaced

The transfer rail. Net pay still calculated by their existing payroll engine; the actual settlement leg moved to USDC.

For contractors (the bulk of the cost), the flow became:

1. Contractor signs onto a stablecoin-friendly off-ramp in their country (Bitso, Mercuryo, Klima, etc.)
2. Their wallet address gets attached to their record in the company HRIS
3. On payday, a single batch payout fans out to all wallets via halfin
4. Off-ramp converts to local fiat in the contractor's bank account, typically same-day

The boring part: accounting

The part vendors skipped:

• The crypto leg is a payment, not a transaction. USDC out is treated like any USD wire for booking purposes. Your 1099 / equivalent reporting unchanged.
• You need a treasury wallet, not contractor wallets. Companies fund a single corporate USDC treasury held with a custodian such as Anchorage, Fireblocks, or Coinbase Prime. The wallet on payroll's books is the treasury, not each contractor's destination.
• Reconciliation is one Postgres view. Match payout_id to payroll_run_id to net_pay_amount. We provide the join keys; the view itself is yours.

The auditor cared about exactly two things: (1) is the off-chain net pay number the same as the on-chain transfer amount, and (2) can you prove the wallet belongs to the contractor.

Edge cases worth flagging

• Volatility from settlement to off-ramp. Even USDC has a few seconds of slippage on conversion. We saw worst-case 0.3% drift on small markets. Build it into your gross-up if your contracts say "X USD net".
• Local tax surprises. A handful of countries (Argentina, Nigeria, Turkey) have evolving rules on whether incoming stablecoin counts as income at the wallet or at the off-ramp. Get local advice before you onboard contractors there.
• Sanctioned jurisdictions. OFAC compliance doesn't care that your rail is crypto. If anything, it's more explicit. Our sanction-screening surface ships in the dashboard.

What it actually saved

The pattern is consistent: roughly 88% reduction on the transfer-cost line.

Operating rule

You don't need to "be a crypto company" to use stablecoin payroll. You need a treasury wallet, a custodian, off-ramp partners by region, and an HRIS field for wallet address. Everything else is the payroll process you already run.