Guides

Stablecoin payroll run: a runbook from cut-off to payslip

A runbook for one stablecoin payroll run: freeze payees, check limits, fund the wallet, quote and pay each person, handle exceptions and close the books.

Caio Barbosa

Founder & CO-CEO

Forbes Under 30. One of the leading voices in Fintech & Crypto in Brazil. Writes weekly about stablecoins, payments, and the future of financial infrastructure in Latin America.

Cover image for Lumx blog article: Stablecoin payroll run: a runbook from cut-off to payslip
Cover image for Lumx blog article: Stablecoin payroll run: a runbook from cut-off to payslip

A stablecoin payroll run is one pay cycle in which an employer funds a stablecoin wallet, converts it to each worker's local currency and pays every worker over a local rail. It runs on a calendar: freeze the payee list, check limits, fund the wallet, pay each person, then reconcile. Most failures come from skipping a step, not from the rails.

This runbook is for the operations or finance lead who owns the run, at an employer or at a payroll platform that runs it for employers. It assumes the decision to pay in stablecoin is already made. If it is not, start with stablecoin payouts for payroll platforms, which covers the flow and what to require from a provider, and with the LatAm payroll provider roundup.

What does a stablecoin payroll run involve?

Five stages, each with an owner and a deadline counted back from pay day. The days below are a working default for a monthly run with workers in Brazil, Mexico, the US and Europe. Shorten them once the run is boring.

One stablecoin payroll run, stage by stage.

Stage

When

Owner

What closes the stage

What breaks if it is skipped

Freeze payees

Pay day minus 5 business days

HR or people ops

Every destination is approved and every change is in

A worker paid to an old account, or not paid at all

Check headroom

Pay day minus 3

Finance

Run total fits under the customer's limits

The run stops halfway and half the team is paid

Fund the wallet

Pay day minus 2

Treasury

Funding confirmed by webhook

Payouts fail on balance

Quote and pay

Pay day

Payments ops

One payout created per worker, each with a stored idempotency key

Double payments on retry, or amounts that drift

Close

Pay day plus 1

Finance

Every payout final, matched to the ledger and to a payslip

Nobody can say who was paid what

Treat the run as a list of individual payouts that share a calendar. There is no such thing as "the run succeeded". A run is finished when every line is either paid or sitting in the exception list with an owner.

Freeze the payee list five days out

The freeze prevents the costliest mistake in a run, paying the wrong account. After it, nobody adds a worker or changes bank details for this cycle. Changes go to the next run, or to an off-cycle payment approved by two people.

Each worker is paid over a local rail: Pix (Brazil's instant payment system, run by the Central Bank) in Brazil, SPEI (Mexico's interbank transfer system, run by Banxico) in Mexico, ACH or FEDWIRE in the US, SEPA in the euro area. For each worker, the payee record needs four things:

  • A destination registered under the employer, on the rail the worker is paid on, with the identifier that rail needs: a Pix key and its type, a CLABE (the 18-digit Mexican bank account number) for SPEI, an account and routing number for ACH or FEDWIRE, an IBAN and BIC for SEPA, a sort code and account number for Faster Payments.

  • The holder's legal name and tax ID, written the way the worker's bank has them. A CPF (the Brazilian individual taxpayer ID) with a typo is enough to make a Brazilian payout bounce.

  • The relationship between employer and worker. The Lumx payroll guide registers workers with the EMPLOYEE relationship, and it is a field a compliance review reads, so it has to be true.

  • An approved status. A destination goes through verification before it can receive money, and on Lumx a destination.approved webhook says when it is ready.

Run a completeness check against the payee list at the freeze, not on pay day. Every worker with missing or unapproved data goes on the exception list with a named owner and a date. The check usually surprises people the first time: spreadsheets rarely record the holder relationship, and bank details collected by email are often for the wrong account type.

Check the run against limits three days out

Every provider enforces limits per transaction, per day and per month, split by transaction type. A run that does not fit fails partway through, and the workers at the bottom of the list are the ones who go unpaid.

Add up the run in the currency the limit is expressed in and compare it with the remaining daily and monthly headroom, not with the nominal limit. On Lumx you read the remaining amounts on the customer record (GET /customers/{id}?includeTransactionLimits=true), and the transaction limits page in the docs lists the defaults. A business customer starts at US$100,000 per day and per month, and enhanced verification raises it.

If the run does not fit, you have two choices. Request a limit increase, which takes a supporting document and a compliance review, so do it the cycle before you need it. Or split the run across days and tell the workers paid on day two before pay day, not after.

Fund the wallet two days out

The run debits the employer's own wallet. Funding it is a treasury task with its own clock, and the clock is the bank rail that brings the money in.

An employer funding from US dollars wires into a USD account in its own name. ACH settles in one to two business days with a 2:00 PM ET cut-off, and FEDWIRE settles the same business day with a 3:00 PM ET cut-off, per the Lumx rail cut-off table. A standing conversion rule turns each deposit into USDC as it lands, so nobody has to remember to convert. An employer that already holds USDC can transfer it to the wallet directly.

Two habits keep funding out of the incident log. First, fund the run total plus a buffer for fees and rate movement, and decide the buffer once, as a percentage, instead of on the day. Second, wait for the funding confirmation webhook before anyone starts paying. "The wire was sent" is not funded. Networks and wallet sizing are covered in how to fund a stablecoin payout, and the stablecoin itself is explained in what is USDC.

Pay day: quote and pay one worker at a time

Pay day is a loop over the payee list. For each worker, create one payout from the employer's wallet to that worker's destination, and give it an idempotency key.

If you take one control from this runbook, take this one. Generate the key once per worker per run, write it to your run record before you send the request, and reuse that stored key on every retry. If a request times out and you retry with the same key, the provider returns the original result instead of paying twice. If you mint a new key on retry, you can pay the same person twice and find out at reconciliation. The idempotency keys guide has the failure cases.

On the rate, choose per run whether you promise workers a fixed local amount or a fixed USD amount. A fixed local amount needs a locked quote per payout, taken just before the payout is sent. On Lumx a locked rate lasts 30 seconds, one minute or five minutes, and the 30-second lock has no fee. Taking one quote at 9 a.m. for a list that pays out over an hour does not work, because the quote expires. The batch payouts guide walks through quoting row by row.

Send the payouts in parallel from a job runner, with a ceiling on concurrency. If the provider answers with a rate-limit error, back off and retry with the same idempotency key. Do not treat a rate-limit response as a failed payout.

The purpose code goes on every payout. As of November 9, 2026, Lumx has no dedicated payroll code: professional services fits contractors, and for employees, confirm the purpose code with Lumx compliance before the first run.

Handle the exceptions worker by worker

Some payouts will not finish on pay day. The runbook decides in advance what happens to each kind, so nobody improvises at 6 p.m. on a Friday.

Common payroll run exceptions and the first response.

What you see

Usual cause

First response

Insufficient balance

Funding short or not yet confirmed

Stop the loop, top up, resume with the same keys

Limit exceeded

Headroom check skipped or run grew after it

Pay the rest the next day or after an increase; tell the affected workers

Payout failed at the bank

Wrong account, closed account, name or tax ID mismatch

Fix the destination with the worker, then pay again as a new payout

Payout held for review

A compliance request for information

Answer with the employment contract or invoice the same day

Rail cut-off missed

Payout created after the ACH or FEDWIRE cut-off

Expect settlement from the next business day and tell the worker

A held payout is not a failed payout. On Lumx a transaction RFI (request for information, a compliance hold that asks for a document before the payout clears) is resolved by email or Slack today: compliance asks for the relationship between sender and receiver and a supporting document, and the payout continues once it clears. How to answer one quickly is in answering a cross-border payout RFI.

Then tell the worker when the money will arrive and why, before they ask. A worker who hears nothing assumes the worst.

If I ran one of these for the first time, I would keep the old payroll process alive for a full cycle and run the stablecoin run in parallel against a shadow ledger, reconciling the two line by line before switching over. It costs a month. I know no other way to find the workers whose bank data was wrong in both systems.

Close the run the next day

The run is closed when every payout has a final status and matches the payroll register, the ledger and the payslip.

Track each payout to a final state with webhooks, not by polling the dashboard. On Lumx an off-ramp moves through TRANSFERRING_STABLECOIN, TRADING and TRANSFERRING_FIAT to SUCCESS, and offramp.success, offramp.failed or offramp.expired tells you how it ended. The status reference by rail is in stablecoin payout statuses and tracking.

Put your own payroll reference on every payout. Lumx accepts a metadata object on the payout and returns it in the webhook, so the payout can be matched to the payroll line without a lookup table. For the books, export the transactions as CSV and keep the account and fee statements for the period. The payslip should show the local amount the worker received, the rate applied and the date, because that is what the worker will compare with their bank statement.

Close with a short note: how many workers, how many exceptions, what caused each one, and what changes for next month. The second run is where the calendar gets shorter.

When a stablecoin payroll run is the wrong tool

  • Domestic payroll with withholding. If the employer and the worker are in the same country and the employer must withhold income tax and social contributions, use a local payroll provider or an employer of record. A payout provider moves money; it does not file payroll taxes.

  • A handful of workers paid once a quarter. The setup (onboarding, destinations, a funding route) pays off with volume and frequency. Two invoices a quarter can go by bank transfer.

  • Workers in countries with no local rail. If a worker's country has no local payout rail with your provider, the payout becomes an international wire and the speed advantage disappears. Check the coverage page before promising pay dates.

  • Paying the employees of employers who are not onboarded. A payroll platform that pays several employers' staff from its own account is pooling funds, and providers do not allow it. Each employer has to be the payer.

What a payroll run looks like with Lumx

On Lumx the employer is the customer. It passes KYB (know your business, the verification of a company and its owners), gets a USD account in its own name and a stablecoin wallet, and registers each worker as a destination with the EMPLOYEE relationship. A payroll platform built on Lumx onboards each employer this way and runs the calendar above on their behalf, which keeps every payer visible.

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.

On pay day there is no batch endpoint: the run is one off-ramp per worker, sent in parallel from your job runner, each with its own idempotency key. A Brazilian worker paid by Pix and a Mexican worker paid by SPEI receive the money instantly, at any hour, because both rails run 24/7. A US worker paid by ACH receives it in one to two business days, and by FEDWIRE the same business day if the payout beats the 3:00 PM ET cut-off. See USDC to BRL and USDC to MXN for the corridors, and global payments for the product.

The limits, cut-offs and error cases in this runbook come from the Lumx docs, and the docs page on payroll shows the same flow as API calls.

Methodology and sources

Lumx facts were read on November 17, 2026 in the Lumx docs: the payroll use case, transactions, exchange rates, destinations, idempotency, errors, webhooks, nested payments, request for information, transaction limits and payment rail cut-off times. The stage calendar is a working default, not a provider requirement.

Verified on November 17, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Isis França on Unsplash.

  • What is a stablecoin payroll run?

    A stablecoin payroll run is one pay cycle in which an employer funds a stablecoin wallet and pays each worker in local currency over a local rail such as Pix, SPEI, ACH or SEPA. It runs on a calendar of five stages: freeze payees, check limits, fund, pay and close. On Lumx each worker is a destination under the employer and each payment is its own payout.

  • When should a payroll team freeze the payee list?

    About five business days before pay day, so there is time to verify new or changed bank details before money moves. Changes after the freeze go to the next run or to an approved off-cycle payment. On Lumx a destination has to be approved before it can receive a payout, and verification takes time.

  • How do you avoid paying a worker twice in a payroll run?

    Give every payout an idempotency key generated once per worker per run, store it before sending the request, and reuse it on every retry. A retried request with the same key returns the original result instead of creating a second payment. Lumx keeps idempotency keys for 24 hours and rejects the same key sent with a different body.

  • What happens if one worker's payout fails during the run?

    The rest of the run continues, and that worker goes on the exception list with an owner and a fix. Bank rejections usually mean wrong account data, and a compliance hold means a document is needed. On Lumx a failed payout arrives as an offramp.failed webhook, and a held one continues once the request for information is answered.

  • Who withholds payroll taxes in a stablecoin payroll run?

    The employer or its local payroll provider, not the payout provider. A payout provider moves the net amount to the worker and does not file payroll taxes, so domestic payroll with withholding belongs with a local payroll provider or an employer of record.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

stablecoin-payroll-run-runbook

A

stablecoin-payroll-run-runbook

Stablecoin payroll run: a runbook from cut-off to payslip

Copy link

Copied!

stablecoin-payroll-run-runbook

TALK TO OUR TEAM

Ready to transform your business with stablecoins?

Discover how our infrastructure can seamlessly integrate stablecoins into your financial operations quickly, securely, and efficiently.

Guides

In this page

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.