Paying global contractors in stablecoins

Key takeaways

1. International wire fees price per transfer, so contractor payroll cost scales with headcount, not with the amount paid.
2. Correspondent banking treats each new contractor as a new relationship, which is why a growing roster means a growing payroll delay.
3. A stablecoin payroll run settles in minutes and does not wait on the slowest corridor's cutoff or holiday calendar.
4. Each contractor is vetted once before the first payment, but sanctions screening still runs on every payment after that.
5. Contractors can be paid in their local currency without the payer opening a bank account or entity in that country.

Payroll headcount and payroll cost move together on wires

A wire transfer is priced as if it were the only payment happening that day: a flat fee, sometimes an intermediary-bank fee on top, and an FX spread if the destination currency differs from the sending one. That pricing makes sense for a single large transfer. It stops making sense the moment a business is paying thirty contractors in twelve countries every two weeks, because the fee repeats in full for every single one of them. Ten contractors and fifty contractors run the same wire, fifty times over, at the same per-transfer cost. The finance team's payroll line grows with headcount even though nothing about the underlying work changed.

The same growth shows up in time, not just fees. Adding a contractor in a new country usually means opening a new banking relationship, learning a new cutoff schedule, and troubleshooting a new set of routing or intermediary-bank quirks before the first payment clears. None of that scales down as the roster grows — it repeats.

The wire is priced per relationship, not per dollar

Correspondent banking is built around bilateral relationships: a payer's bank has to have (or build, hop by hop) a chain to the payee's bank. Each contractor, in practice, is a new endpoint on that chain — a new receiving bank, a new country's clearing rules, sometimes a new intermediary along the way. The fee a business feels at the invoice line is downstream of that structure: a payer is not being charged for moving money, they are being charged for the chain's existence.

A wire fee looks like a price for moving money. It is closer to a price for the relationship that has to exist before the money can move.

Stablecoin settlement does not build a new chain per contractor. Funds move on the same network regardless of which contractor is receiving them, so the marginal cost of paying contractor fifty-one is close to the marginal cost of paying contractor two — a flat structure that a per-relationship wire cannot offer by design.

What a stablecoin payroll run looks like

A payroll run is, underneath the paperwork, a batch of payments that all need to land on roughly the same day, in each contractor's own currency, regardless of what country each one is in. On correspondent-banking rails, that batch is only as fast as its slowest leg: a run held up by one contractor's bank holiday or one intermediary's cutoff time delays the whole cycle, or forces the business to run early and eat several days of float.

On stablecoin rails, the run stops being hostage to any single corridor. Funds settle in minutes on any calendar day, so a payroll cycle that runs on the fifteenth pays contractors on the fifteenth — not on whichever day each contractor's local banking hours happen to allow. The company funds the run once in its own currency; conversion into each contractor's local currency and the on-chain leg happen inside the payment, and the contractor receives spendable local currency on the other side without ever touching a token themselves.

Vetting happens once; screening runs on every payment

The part of contractor payments that actually takes work is not moving the money — it is knowing who each contractor is before the first payment goes out. KYB and counterparty verification has to happen once per contractor, but how "once" is defined varies by provider. Some re-run verification on a schedule regardless of history; a network model verifies each contractor a single time and carries that result to every future payment, so pay cycle six does not re-litigate what pay cycle one already established. Sharing the vetting does not thin the ongoing check: sanctions and watchlist screening still runs on every payment, on every rail, regardless of how long a contractor has been on the network.

That difference compounds with headcount for exactly the reason wire fees do: a payroll team adding contractors is not just adding payments, it is adding relationships to maintain. A model that treats vetting as a one-time cost per contractor — rather than a recurring one per payment — is the same economics argued for payout platforms generally in Mass payouts scale on vetting, not volume; contractor payroll is the first-party version of the same constraint.

Paying in local currency without a local entity

None of this requires a company to open a bank account in every country it hires from, or to hold cryptocurrency on its own balance sheet. On Infinite (infinite.net), the business funds a payroll run in fiat from its own account; the stablecoin leg and the currency conversion happen inside the transfer; the contractor can receive ordinary local currency. First-Party Funds Flow covers the account side of this — a single KYB review on the paying business, not one per contractor, since the funds moving are the company's own.

That matters specifically for payroll because the two sides of the payment rarely want the same instrument. The finance team wants a payable it can fund once, in its own currency, on a fixed schedule. The contractor wants a receivable in the currency they actually spend. Stablecoin settlement in the middle, fiat on both ends, gives each side the part it wanted — without either one holding a position in something they didn't ask for.

Frequently asked questions