A stablecoin payroll provider pays workers with a stablecoin as the funding source, the payout currency, or both. The best one for a Latin American team in 2027 depends on the job: an employer wants a payroll app such as Deel, Toku, Rise or Bitwage, and a company building a payroll product wants payout infrastructure, where Lumx and Due sit.
Lumx wrote this list and is in it, in the second group, so read the infrastructure section with that in mind. For a payroll platform building its own payouts, see stablecoin payouts for payroll platforms.
Quick answer by need, from the tables below:
Employer paying its own team, with employment compliance: Deel or Toku.
Contractor-heavy team that wants USDC as the default: Rise.
Keep your payroll system and add stablecoin funding: Bitwage.
Building a payroll or contractor product that pays in reais and pesos over local rails: Lumx.
Building one with corridors beyond Latin America: Due, which this page does not count among the Brazil options.
The two groups are often ranked together, and that is where most "best of" lists go wrong. A payroll app owns the worker relationship, the contract and the tax paperwork. Payout infrastructure owns the conversion and the local delivery, and expects your product to own everything else. The step-by-step mechanics of a run are in paying LATAM contractors in stablecoins; this page is about who to run it with.
Two kinds of provider sell "stablecoin payroll"
A payroll platform is software an employer logs into. It onboards each worker, holds the contract, collects tax forms, and pays out on a schedule. Stablecoins show up in one of two places: the employer funds payroll in USDC or USDT, or the worker chooses to receive a stablecoin instead of local currency. Some platforms also act as EOR (employer of record, a provider that legally employs the worker on your behalf) in countries where you have no entity.
Payout infrastructure is an API. Its customer is the payroll platform, the marketplace or the operations team that already has the worker relationship and needs money to land in Brazil or Mexico in local currency. It converts the stablecoin, pays over Pix (Brazil's instant payment system, run by the Central Bank) or SPEI (Mexico's interbank transfer system, run by Banxico), and reports per payment. It does not draft contracts or file anything for your workers.
The questions that decide the choice in Latin America
Four questions sort providers faster than any feature grid.
Where does the stablecoin sit? Funding payroll from a stablecoin treasury and paying workers in stablecoins are different features. A provider can do one without the other, and the help pages are usually explicit if you read past the landing page.
Does the money land on the local rail? A worker in São Paulo wants reais in their account over Pix the same day, not a token they have to sell somewhere else. Check whether the provider delivers local currency in Brazil and Mexico itself, or hands the worker a wallet and leaves the conversion to them.
Employee or contractor? Paying a salaried employee involves withholding and statutory contributions in the worker's country. Paying a contractor is a commercial payment against an invoice. Most stablecoin features started on the contractor side, and employee support is narrower.
Which country is actually covered? Coverage pages count countries for the contractor product. The stablecoin option within that product often covers a shorter list, and Brazil is not always on it.
Payroll platforms an employer runs directly
These are the platforms we found with a stablecoin feature documented on their own pages, read on October 9, 2026, with Toku re-read on November 16, 2026.
Payroll platforms with a stablecoin option, as documented on October 9, 2026 (Toku: November 16, 2026).
Platform | Stablecoin side | Who it pays | Brazil and Mexico delivery | What to check |
Deel | Contractors withdraw a balance as USDC or USDT; eligible EOR and direct payroll employees can take part of net salary in USDC, EURC or USDT; employers can fund invoices in USDC or USDT | Contractors and employees | Local withdrawal methods, Pix among them | Employee stablecoin pay needs a USD or EUR contract and the employer must enable it |
Toku | Employer funds from a bank account or a stablecoin balance; USDC or USDT payouts, or local currency, for supported arrangements | Employees and contractors, as employer of record, agent of record or global payroll | Local currency where supported; its page says a country guide does not confirm every payout option | The early-access note of October 9 is gone from the November 16 page; ask which countries are open |
Rise | Employer funds in USD or USDC; contractors withdraw in fiat or crypto | Contractors, plus EOR | Fiat withdrawal by the contractor | Positioned around USDC; check the withdrawal route for each country |
Bitwage | Employer funds in stablecoins or crypto; workers choose local currency or a mix of stablecoins and crypto | Employees and contractors | Brazilian real and Mexican peso over SPEI listed as payout options | The stablecoin funding portal is in beta for a limited group of customers |
Remote | Contractors receive USDC through Stripe Connect | Contractors of companies billed in USD | No local delivery; USDC to a wallet | Stripe's supported-country list for stablecoin payouts does not include Brazil |
Two things stand out for a Latin American team. First, the employee side is narrow everywhere: Deel restricts stablecoin salary to USD and EUR contracts, and Toku's page asks you to confirm worker eligibility country by country. Second, Brazil is the country where a wallet-only feature hurts most, because a contractor paid in USDC still has to find their own route into reais.
Payout infrastructure that payroll products build on
If you are building the payroll product, the comparison changes. You need an API that pays many people in local currency, reports each payment, and lets you put your own margin on top.
Payout infrastructure for payroll products in Latin America, as documented on October 9, 2026 (Due and Lumx: November 16, 2026).
Provider | Local payout rails in Latin America | Run model | Funding and custody | Fees as published |
Lumx | PIX for BRL, SPEI for MXN, and COP payouts in Colombia over ACH Colombia and Bre-B | Each payout is its own idempotent API call, safe to retry without paying twice; per-payment webhooks | Custodial wallet per employer, funded by USD wire or stablecoin transfer | Monthly platform fee plus usage-based per-transaction fees; no published plans |
Due | Local rails across 80+ countries, paying in local currency; this page does not count Due among the Brazil options; virtual accounts per employer in currencies including MXN and COP | Bulk payout API, one call or a CSV for many payments | Non-custodial, by its own description | Not listed on the payroll page |
The honest differences. Due documents a bulk endpoint and Lumx does not: on Lumx each payout is its own API call with an idempotency key, safe to retry without paying twice, and your job runner sends them in parallel. When a worker must receive an exact amount in reais, Lumx locks the rate on the target BRL amount. Lumx keeps each employer's funds in a separate custodial wallet per employer, which matters when your customers want a payroll float that is theirs and not yours. The side-by-side detail for each provider is on the compare pages.
One employer, one account: the rule payroll platforms ask about
The question payroll platforms ask first is whether they can pay every employer's workers out of a single account of their own. On Lumx the answer is no. Each employer is onboarded as its own business customer, with its own KYB (know your business, the verification of a company and its owners), its own wallet and its own payees. The platform earns through a partner fee added to each payout rather than through a pooled float. The KYB explainer lists what a business is usually asked for.
I made the one-employer-one-account rule a condition for payroll platforms rather than a recommendation, and it has cost us deals. A pooled account is faster for a platform to launch: one onboarding, one wallet, every employer's money mixed together. It is also the setup where a single employer's compliance problem freezes the payroll of every other employer on the platform, and where nobody can say, from the payment alone, which company owed that wage. I would rather a platform spend one business day per employer on KYB than explain to forty employers why their payroll is held because of a forty-first.
The same structure is how marketplaces pay sellers, described in marketplace stablecoin payouts across LATAM, and how a creator platform pays creators in creator platform payouts abroad.
What changed in 2026 and what to check in 2027
Four rule changes landed or fall due between February 2026 and January 2027. None changes how a Pix or SPEI payout reaches a worker; they change what a provider must ask and report. For the same payouts cut by country, see the best stablecoin APIs for LATAM.
Rule dates that touch stablecoin payroll in 2027, as read on November 16, 2026.
Date | Rule | What the text says | What to check in 2027 |
February 2 and May 4, 2026 | Brazil: Resolution BCB 521/2025 | Article 76-A puts international payments with virtual assets in the foreign exchange market, from February 2. From May 4, Article 76-C has the provider collect each payment's purpose, and Article 82-A sends reports to the Central Bank by the fifth day of the next month | Which purpose the provider records for wages |
From July 2026 | The crypto-asset declaration replaces the 2019 model and reaches providers abroad that serve Brazil. Receita says it does not deal with taxation | What the provider files; see the Receita crypto-asset declaration guide | |
By July 1, 2026 | A provider operating under national law before December 30, 2024 could continue until July 1, 2026 or until its authorisation was granted or refused | For EUR payroll, the provider's authorisation or bank or e-money status | |
No later than January 18, 2027 | Takes effect on the earlier of 18 months after enactment on July 18, 2025 or 120 days after final federal rules | For payroll funded in stablecoin, which issuer's token the provider holds |
On Lumx, PROFESSIONAL_SERVICES is for now the closest purpose code for contractor and salary payments, so confirm the code for employees with Lumx compliance.
When stablecoin payroll is the wrong tool
When the worker is a salaried employee in a country where you already run local payroll. The withholding and the payslip have to come from that payroll, and a stablecoin leg adds a conversion for no gain.
When your whole team is in one country and you already hold that country's currency. Paying reais to Brazilians from a reais account is a domestic transfer. Converting into USDC and back adds cost and a counterparty.
When you need someone to take on employment risk. An API that pays people does not employ them. If you need an EOR, start with the platforms in the first table.
What a payroll run looks like on Lumx
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
For a payroll platform, a run on the global payments API has four moving parts. The employer is a business customer that funds its wallet with a USD wire or a direct USDC transfer. Each worker is a destination registered under that employer and marked as an employee relationship, and a destination is verified before it can receive money, so a bad Pix key fails on a weekday and not on payday. On payday each payout is its own idempotent API call, so a crashed job can be retried without paying anyone twice. Each payout reports its own status by webhook, which turns "did everyone get paid" into a list of the ones that did not.
Two details are worth knowing before the first Brazilian run. With BRL named virtual accounts (a local account number issued in the customer's own name), the worker sees the employer's registered name as the payer on the Pix, not Lumx, and each settled Pix carries its end-to-end ID for lookups. And transaction limits are set per verification tier, with higher limits available on request, so size the largest single payment before payday rather than discovering the ceiling on it. The rails and currencies per country are on the coverage page, and providers that issue such accounts are compared in best virtual account providers for Latin America.
Pricing is a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes and no pre-funding. We do not publish plans; a quote depends on your corridors and volume.
Which to pick
Pick a payroll platform if you are the employer, and pick on the employee question before the stablecoin feature, because the feature is easy to add and employment compliance is not. Pick payout infrastructure if you are building payroll for other companies.
Deel. Best for: employers that need employer-of-record coverage and want to offer stablecoin pay to contractors, and to employees on USD or EUR contracts.
Toku. Best for: employers that want to keep their current payroll system and add stablecoin funding and payouts, with employment compliance in the same countries.
Rise. Best for: contractor-heavy teams that want USDC as the default pay currency and let each contractor choose how to withdraw.
Bitwage. Best for: companies that run payroll elsewhere and want to fund it from a stablecoin or crypto treasury, with Brazilian and Mexican payouts in local currency.
Remote. Best for: companies billed in USD paying contractors outside Brazil in USDC.
Lumx. Best for: payroll platforms and operations teams that need each employer's funds in its own custodial wallet, with the employer's name on every Pix (BRL named accounts), and payouts in BRL over PIX and MXN over SPEI.
Due. Best for: payroll products that want one bulk call for many payouts and a non-custodial setup.
For the wider region, see the best stablecoin APIs for LATAM. For a Brazil-only team, the specifics are in paying contractors in Brazil.
Methodology and sources
Every provider fact on this page comes from the provider's own public pages, read on October 9, 2026, except Toku's stablecoin payroll page and Due's payroll payments page, re-read on November 16, 2026. Deel, Rise, Bitwage and Remote were not re-read in November, so their rows keep the October date. Deel: help center articles on withdrawal fees and methods, withdrawing with a stablecoin transfer, getting paid in stablecoins and funding with stablecoins. Toku: its stablecoin payroll page. Rise: its guide to paying in USDC. Bitwage: its crypto-funded payroll page, its support article on payout currencies and its December product update. Remote: its support article on stablecoin payouts, checked against Stripe's documentation on stablecoin payouts for Connect. Due: its payroll payments page. Lumx: the payroll guide, sender of record and nested payments pages of our documentation.
The rule dates above come from the linked texts, all read on November 16, 2026. We included a provider when its own pages document a stablecoin payroll or payout feature that reaches workers in Latin America. We did not test accounts, and we did not include fee figures that the provider does not publish on the pages above. Where a feature is in beta or early access, the table says so.
Verified on October 9, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Annie Spratt on Unsplash.
What is the difference between a stablecoin payroll app and payout infrastructure?
A payroll app is software an employer uses to pay its own workers, with contracts, tax forms and schedules built in. Payout infrastructure is an API that a payroll product or marketplace calls to convert stablecoins and pay workers in local currency. An employer usually wants the first; a company building payroll for others wants the second.
Can I pay employees in Brazil in stablecoins?
Some platforms let an employee take part of net salary in a stablecoin, but the salary itself still runs through a payroll that handles withholding. Deel, for example, limits stablecoin salary to employees with USD or EUR contracts. For contractors invoicing a foreign company, the common route is a stablecoin-funded payout delivered in reais over Pix.
Which stablecoin payroll providers deliver reais over Pix?
Among the payout infrastructure providers on this page, Lumx pays reais over Pix and pesos over SPEI. Due lists Pix on its payroll page, but this page does not count it among the Brazil options. Among payroll platforms, Deel lists Pix as a contractor withdrawal method, Bitwage lists the Brazilian real and the Mexican peso over SPEI, and Toku delivers local currency where supported. Stripe's stablecoin payouts, which Remote's contractor feature uses, do not list Brazil.
Do payroll platforms need a separate account for each employer?
On Lumx, yes: each employer is onboarded as its own business customer with its own wallet, and the platform earns through a partner fee on each payout. That keeps every wage traceable to the company that owes it and keeps one employer's compliance review from holding the others.
What changes for stablecoin payroll in Latin America in 2027?
The payout rails stay the same, and the rules around them move. Brazil's Resolution BCB 521 applied from February 2 and May 4, 2026, Receita's crypto-asset declaration started in July 2026, MiCA's provider transition ended by July 1, 2026, and the US GENIUS Act takes effect no later than January 18, 2027. Ask each provider what it reports and which issuer it holds. On Lumx, each payout carries a purpose code, and PROFESSIONAL_SERVICES is for now the closest code for contractor and salary payments.





