A contractor in Manila invoices EUR 3,000. You send it by SWIFT on the 28th. It arrives days later, an intermediary bank has taken its cut, and the amount that lands matches neither the invoice nor your ledger. Stablecoin payroll fixes that part: value moves in minutes, on any day of the week, and arrives at the amount you sent. What it does not fix is who your team legally works for. This article covers both: how to pay a global team in USDC or USDT without a local entity, and where the rail stops being the answer.
What stablecoin payroll is, and what it is not
Stablecoin payroll is paying people, usually contractors, in a fiat-pegged token such as USDC or USDT instead of by bank transfer. The company funds in EUR or USD, the payment settles on-chain in minutes, and the recipient holds the token or converts it to local currency. It changes the payment rail, not the employment relationship or its tax obligations.
The word "payroll" oversells it. Payroll for employees means withholding income tax, paying social contributions, issuing payslips and filing returns in the employee's country. You cannot do any of that without being registered as an employer there, either through your own entity or through an employer of record (EOR). A stablecoin transfer does none of it.
So in practice, "stablecoin payroll without a local entity" means one of two things: paying independent contractors directly, or paying through an EOR that itself funds or disburses in stablecoins. Everything else is marketing.
The honest size of the opportunity is also smaller than the headlines. BCG's analysis of on-chain real-economy payments puts business-to-individual payouts (contractor payments, creator earnings, refunds and rebates) at about 10% of stablecoin payment volume. It names the brakes: strong domestic fiat rails in developed markets, regulatory considerations and tax treatment (BCG and Allium, Stablecoin Payments: The Truth Behind the Numbers). Stablecoin payroll wins where a bank corridor is failing, not because the rail is new.
Three ways to pay a team abroad without an entity
Before choosing a rail, choose the legal structure. The rail follows from it.
| Model | Legal employer | Who handles tax withholding | Role of the stablecoin | Where it breaks |
|---|
| Own local entity | You | You, in each country | Optional, for funding the entity | Months of setup per country; overkill for a handful of people |
| Employer of record (EOR) | The EOR | The EOR | Some EORs accept funding or pay out in stablecoins; salary obligations are unchanged | Per-head monthly cost; you still need a cross-border route to fund the EOR |
| Direct contractor payouts on a stablecoin rail | Nobody. It is a B2B contract | The contractor, in their own country | The rail itself | Misclassification, if the contractor in fact works like an employee |
| Freelance platform or marketplace | Nobody, unless local rules say otherwise | The contractor | The platform's payout rail | Platform fees; EU platform-work rules from December 2026 |
For most companies reading this, row three is the relevant one: a contractor base spread across Asia, LatAm and non-euro Europe, paid monthly or per milestone. The mechanics of that row are covered in our practical guide to paying contractors and affiliates in USDC. This article covers the decisions around it.
Do you need a payroll platform, or just a payment rail?
Before choosing how to pay international contractors, ask a blunter question: what are you actually paying the intermediary for?
Contractor and payroll platforms such as 4DEV, Garna, Finboo and EasyStaff can do much more than move the money. Depending on the provider and the arrangement, they may handle contracts, invoices, closing documents and contractor administration. For a company that needs that layer, the service has real value.
Not every company does. Some already manage their contractor relationships themselves: the contracts are signed, the amount due is known, and nobody needs a third party to produce the supporting documents for each payment.
The cost of that layer is easy to miss. A typical contractor payment platform may charge around 3% for the service, with another 1–2% where currency conversion is required. That can bring the total cost of the flow close to 5%. For a company paying $1,000,000 a month to international contractors, the difference is material.
| Contractor platform | INXY payment infrastructure |
|---|
| Monthly payouts | $1,000,000 | $1,000,000 |
| Example total cost | ~5% | ~0.5% |
| Monthly cost | ~$50,000 | ~$5,000 |
| Annual cost | ~$600,000 | ~$60,000 |
In this example, the payment flow through INXY costs 10x less, and in many payment flows the gap is 5x or more. The reason is the model, not a discount. A contractor platform sits between the company and the contractor and charges for the administrative layer around the transaction. INXY provides the infrastructure for the payment itself: you pay your contractors directly, and INXY handles conversion, the blockchain infrastructure, AML, KYT, transaction monitoring and reporting behind the scenes.
AI is making the administrative layer cheaper to run in-house. Creating one invoice was always easy. Creating hundreds of correctly structured invoices and payment records every month used to mean hours of repetitive finance work, which is why outsourcing the whole workflow made sense. AI and modern finance tools now automate much of the generating, checking and processing of that documentation. That does not remove legal, tax or employment obligations, but for a company that already manages its contractors internally, it changes the economics of paying a platform to do it.
So the question becomes: are you paying 3–5% because you need contractor administration, or because it was the easiest way to make the payment? If you need an EOR, employment administration, tax handling, contracts or local compliance support, use a provider that offers those services. If your contractors are genuine independent businesses, your contracts are in place and you can manage the documentation yourself, you may not need another company between you and the people you pay. You may only need a better payment rail.
The risk no payment vendor puts on the landing page
Paying someone in USDC does not make them a contractor. Classification depends on how the work is done: who controls the hours, whether the person is integrated into your organisation, whether they work only for you, and who carries the commercial risk. The currency of the invoice plays no part in it.
Someone paid the same amount on the same day every month, working your hours, with a company email address and a line manager, looks like an employee to a tax authority. That holds whether the money arrived over SEPA or TRON. A cheap, fast rail makes it easy to scale a contractor base in a country where you have no entity, and that is exactly when the classification question tends to get skipped.
For platforms, 2026 has a hard date. The EU Platform Work Directive, Directive (EU) 2024/2831, introduces a legal presumption of employment for people working through digital labour platforms where the facts indicate control and direction. The burden of rebutting that presumption sits with the platform. Member states must transpose it by 2 December 2026. For a freelance marketplace or payroll platform paying through stablecoin rails, this matters more this year than any crypto regulation does.
INXY Payments is payment infrastructure. We move, screen and settle the money; we do not determine anyone's employment status, and neither does any other payment provider. That decision belongs to you and your counsel, and it should come before the first batch, not after the first audit letter.
How the money moves: three legs, one of which you do not control
Every stablecoin payroll run has three legs. Most evaluations only look at the middle one.
Leg 1: funding, which runs on banking hours
You fund in EUR or USD from your company bank account. On INXY, conversion is automatic and your accounting stays in EUR or USD; the finance team never has to hold a wallet or pay gas.
The catch is timing. The chain settles 24/7, but your bank does not. To pay on Monday the 1st, the funding has to clear before Friday's banking cut-off. That means holding a pre-funded balance over the weekend: a small treasury float that nobody puts in the business case, and that every payroll calendar has to allow for.
Leg 2: on-chain settlement, which is the easy part
The transfer itself settles in minutes. The decisions are which token and which network.
On network, the market has already chosen for most corridors. BCG and Allium find TRON carries 60–80% of real-economy stablecoin payment flows, though its share fell from about 74% to about 60% across 2025 as Ethereum, Solana, BNB Smart Chain and Polygon gained. USDT on TRC-20 is still what most contractors in Asia and LatAm can receive and cash out locally. For EEA-facing counterparties, USDC is the practical default because it is authorised as an e-money token under MiCA. The trade-offs are covered in USDT vs USDC for business payments and what each USDT network actually costs.
INXY settles across 20 supported cryptocurrencies on ERC-20, TRC-20, BEP-20, Polygon, TON and other networks, so a single batch can pay each contractor on the network they actually use.
Leg 3: the payee's off-ramp, which sets their real pay
The contractor turns USDT into pesos, lira or rupiah through a local exchange, an OTC desk or a payment app. Their spread, their exchange's reliability and their bank's attitude to crypto-origin deposits all apply here, and you see none of it.
This is the leg that decides whether the programme lasts. A payout that is cheap on your side and expensive on theirs comes back six months later as a rate-increase request. Ask a sample of payees what they actually net after conversion, per corridor, before you roll out.
Who carries the exchange-rate move
Decide this in the contract, not on payday. There are three common set-ups:
- Invoice in EUR, pay the USDT equivalent at payout time. The contractor receives the EUR value; you carry the conversion.
- Invoice in USD, pay USDC one to one. Clean for USD-based companies. A company with EUR books carries the EUR/USD move.
- Invoice in the contractor's local currency. This gives you the most exchange-rate exposure and the most reconciliation work. Avoid it unless the contractor insists.
Running a stablecoin payroll batch: the sequence
This is the order that holds up under an audit. Steps 1–4 happen once per payee; steps 5–9 happen every cycle.
- Classify and contract. A written B2B contract that states the invoice currency, the token and network of payment, who pays the network fee, and which exchange rate applies.
- Onboard each payee. Collect identity data, the wallet address, the token and the network. The EU Transfer of Funds Regulation, Regulation (EU) 2023/1113, requires originator and beneficiary information to travel with crypto-asset transfers regardless of amount, with additional checks where a self-hosted wallet is involved. It implements FATF Recommendation 16. Collect this once, at onboarding, not at 17:00 on payday.
- Verify the address with a test transfer, and confirm receipt through a channel other than the one the address came in on.
- Put wallet changes behind a second channel. A new address takes effect only after a call or a confirmation in a separate, already-verified channel.
- Fund the balance before the banking cut-off that precedes payday.
- Build the batch. One row per payee, amounts in fiat or in tokens, uploaded as a file or sent by API.
- Let validation and screening run. On INXY, a batch passes format checks, address and network compatibility checks, KYT screening of recipient addresses, and balance and exchange-rate checks before it can be executed. A flag here is a held payment, not a bug. Decide in advance who resolves it and how quickly.
- Approve and execute, with a second approver for anything above a threshold you set.
- Reconcile each payout and send each payee a statement showing the amount, token, network, transaction hash, and the fiat value and exchange rate used. Contractors need the fiat value at receipt for their own tax records. Sending it proactively costs less than answering forty emails in April.
For the batch mechanics in more depth, see mass crypto payouts.
What breaks in production
These are the failures that show up in month three, not in the demo.
The right address on the wrong chain. Ethereum, BNB Smart Chain and Polygon share the same 0x address format, so an address is valid on all three. A payee who watches only one chain reports a "missing" payout that is in fact sitting on another. With self-custody the funds can usually be reached; with an exchange deposit address that does not support that network, recovery is at the exchange's discretion. Put the network in the contract and in the batch file, and never infer it from the address format.
The wallet-change email. Shortly before payday, an email that appears to come from a contractor asks you to update their wallet. On-chain transfers cannot be recalled. Payroll redirection fraud already happens on bank rails; on a stablecoin rail, the second-channel rule in step 4 is the only control you have.
The payday screening hold. KYT flags a recipient address because an exchange deposit address has had indirect exposure to a risky counterparty. The hold is correct, but it lands at the worst moment. Screen at onboarding, re-screen before each batch, and tell affected payees before they notice.
Rate drift between preparing and approving. A fiat-denominated batch is prepared on Thursday and approved on Monday. By then the quote has expired, the re-quote changes the total, and the approver signs off a different number from the one the preparer built. Approve on the refreshed quote, not the original.
The payee's off-ramp disappears. A local exchange pauses withdrawals, or a payee's bank starts rejecting crypto-origin deposits. You paid on-chain on time, but in practice the contractor has not been paid. Keep a fallback rail on file for every payee.
Network fees broken out by chain. A batch that pays across three networks produces three different fee lines. If your ledger books a single "contractor payroll" line, someone will chase the difference every month. Map the network fee to its own account from the first run.
When stablecoin payroll is the wrong answer
This is the section a vendor would normally leave out, so here it is plainly.
- Your team is in the euro area and has EUR bank accounts. SEPA and SEPA Instant are cheap and fast, and every accountant understands them. Adding a token adds two conversions and gains nothing.
- Your people are employees. Use an EOR or your own entity. The rail is a detail; the employment obligations are not.
- Your payees are in the UK or the US. INXY Payments does not serve those markets. Both also have strong domestic rails, which removes most of the reason to switch.
- Your payees have no clean off-ramp. If the only way to cash out is informal peer-to-peer trading, you have not removed cost and risk; you have moved them onto the person you are paying.
- You pay three people once a month. Onboarding, screening set-up and wallet verification are a fixed cost. At that scale, the bank transfer you already have may simply be cheaper to run.
Stablecoin payroll earns its place where the bank rail is weakest: contractors across Asia and LatAm with long correspondent chains, countries your bank rejects or delays, payees who want dollar-denominated pay in a volatile local currency, and contractor bases of dozens to thousands paid on a fixed cycle.
Decision framework
Pick by payee, not by rail.
| Your situation | Use |
|---|
| You need employment, tax or contractor administration | An EOR or a contractor management platform |
| You need invoices and document administration handled for you | A contractor or payroll platform |
| You already manage contracts and documents internally and mainly need to pay contractors globally | Direct stablecoin payouts through payment infrastructure |
| Employees in a country where you have no entity | An EOR or your own entity. Stablecoins are optional, for funding only |
| Contractors in the euro area with EUR accounts | SEPA |
| 10+ contractors in Asia or LatAm, and the bank corridor is slow or rejected | A stablecoin rail: USDT on TRC-20 where payees cash out locally, USDC where counterparties are EEA-regulated |
| A mixed team | Run both rails and let each payee's corridor decide |
| A freelance platform paying thousands of workers in the EU | A stablecoin rail, plus a classification review before 2 December 2026 |
If the third, sixth or last row describes you, that is the problem INXY Payments is built for. You fund in EUR or USD. Payouts settle on-chain across the networks your contractors use. Each payout passes KYT, sanctions and Travel Rule screening before it leaves, with Elliptic and Sumsub in the compliance stack. Your books stay in fiat. Pricing is a transaction fee below 1%, with no setup, monthly or hidden fees. See how it works for crypto payroll and contractor payouts for global teams, or book a demo and bring your payee list. Knowing which corridors your team is actually in is usually enough to tell whether stablecoin payroll will pay for itself.
This article describes regulatory and market conditions for general information. It is not legal, tax, or financial advice — INXY Payments is a payment infrastructure provider, not a law or accountancy firm, and decisions with regulatory consequence should be reviewed by qualified counsel in the relevant jurisdiction.
FAQ
Is it legal to pay contractors in USDC or USDT?
In many jurisdictions, paying an independent contractor in a stablecoin is permitted when both parties agree to it in the contract. How the contractor must report that income, and at what fiat value, varies by country and changes over time. Check the position for each country where you have contractors with qualified counsel, and give every payee the fiat value at receipt.
Can I pay employees in stablecoins?
Employee pay is governed by local wage, tax and social-security rules, and many countries regulate the form in which wages can be paid. Withholding obligations apply whatever the payment method. If you have employees in a country without a local entity, use an employer of record. Some EORs work with stablecoins, but the employer obligations stay with the EOR.
Do I need a local entity to pay contractors in stablecoins?
No, not for genuine independent contractors on a B2B contract. You need an entity or an EOR if the people are in fact employees, and the payment rail does not change which one they are. Classification depends on control, integration and exclusivity, not on whether the invoice is paid over SEPA or on-chain.
Should stablecoin payroll use USDT or USDC?
Use whichever token each payee can actually receive and convert locally. In most of Asia and LatAm that is USDT, commonly on TRC-20. For counterparties in the EEA it is USDC, which is authorised as an e-money token under MiCA. Many contractor programmes run both and record each payee's token and network at onboarding.
How do contractors convert stablecoins to local currency?
Through a local exchange, an OTC desk or a payment app that supports withdrawal to a local bank account. The conversion spread is paid by the contractor and is invisible to you, so ask a sample of payees what they net after conversion in each corridor. An off-ramp that is expensive for them eventually shows up as a higher rate for you.
How fast is stablecoin payroll?
The on-chain transfer typically settles within minutes and runs 24/7. The slower legs are at either end: your fiat funding, which follows banking hours and cut-offs, and the payee's conversion to local currency. Fund before the last banking day ahead of payday so the batch can run on schedule.
