Stablecoin payment use cases are business payments where a dollar stablecoin carries value across a border or a currency, such as contractor payroll, supplier payments, treasury moves and fintech dollar accounts. In Latin America they work best when the last leg runs on an instant local rail such as Pix (Brazil's instant payment system, run by the Central Bank).
Where do stablecoin payments beat bank rails in Latin America?
They win when the payment has to cross a border or change currency on its way. A SWIFT payment takes 1 to 5 business days to settle, while Pix and SPEI (Mexico's interbank transfer system) settle instantly (Lumx coverage docs, read November 1, 2026). Domestic payments between two accounts in the same currency rarely need a stablecoin at all.
Every use case below has the same four steps underneath:
The payer funds in local currency or dollars.
The provider converts to a dollar stablecoin, USDC or USDT.
The provider converts again and pays out over the recipient's local rail, such as Pix or SPEI.
Both sides track the payment by status and webhook, and the person paid sees local currency in a bank account.
On cost, a wire's correspondent fees and FX margin show up only in the amount that arrives. For a sense of scale, BIS Working Paper 1385 (October 2026) reports US-outbound fintech operator medians of 262 basis points for BRL at $200 and 104 at $10,000, and 461 and 189 for COP. Prices by corridor are in cross-border payment costs in 2026, and adoption figures are in stablecoin payment statistics for 2026. Most of these flows are business to business. Remittances and dollar accounts are products that companies build on the same rails.
On Lumx, KYB (know your business, the verification of a company and its owners) or KYC (know your customer, the verification of an individual) approves the customer and creates its wallet before any money moves. An on-ramp with the exact amount announces the deposit, an off-ramp with a locked quote pays out, and the status plus the onramp.success, offramp.success and offramp.failed webhooks report each leg. Lumx deducts no fee from the amount that reaches the recipient on a Pix, SPEI or Bre-B (Colombia's instant payment system, run by the Banco de la República) payout.
The seven use cases, the rail at the receiving end and the settlement time on that rail, against a SWIFT wire at 1 to 5 business days (Lumx coverage docs and product facts, November 1, 2026)
Use case | Who pays whom | Receiving rail and settlement | Against a wire | Read next |
Contractor payroll | A company pays contractors in Brazil, Mexico and Colombia | Pix and SPEI, instant. Colombia by Bre-B or ACH Colombia | Instant instead of 1 to 5 days | |
Seller payouts | A platform pays sellers and creators and keeps a fee | Pix or SPEI in, local payout out, instant | Instant instead of 1 to 5 days | |
Supplier payments | A buyer pays an invoice in the supplier's currency | Local rail where one exists, otherwise SWIFT in USD, 1 to 5 business days | Same as a wire where only SWIFT reaches the supplier | |
USD collections | A company is paid in dollars by clients abroad | ACH 1 to 2 business days, FEDWIRE same day, SWIFT 1 to 5 business days | ACH and FEDWIRE can beat a wire; the gain is the instant local payout | |
Treasury moves | A group moves cash between entities and currencies | Wallet to wallet in seconds, then the local rail when cash leaves | Seconds between wallets instead of 1 to 5 days | |
Remittance-style payouts | An app lets people send money to family abroad | Pix, SPEI or Faster Payments (the UK's real-time bank transfer network), instant | Instant instead of 1 to 5 days | |
Fintech dollar accounts | An app gives its users a dollar balance | USD in by ACH, FEDWIRE or SWIFT, local rail out | Instant payout; inbound is bank-rail time |
Contractor payroll in Brazil, Mexico and Colombia
A company with contractors in three countries sends one dollar transfer and pays each person in local currency, with no crypto wallet on their side. That replaces one wire per person. The Brazilian case is in paying contractors in Brazil.
The same flow can carry salaries, but the stablecoin rail moves only the net amount: payslip, payroll tax and withholding stay with the employer's payroll process.
On Lumx, the employer is a business customer funded by a FEDWIRE (the Federal Reserve's same-day wire system) or ACH deposit that the platform announces in advance with the exact amount. Each payee is a registered destination, verified before first use, with the employee relationship that the docs use for both employees and contractors. Each payout is one off-ramp call with the purpose code for professional services, tracked by status. A Colombian payee receives over Bre-B or ACH Colombia, chosen when the destination is registered.
Seller payouts when a platform takes a fee
A platform that pays sellers in another country has two jobs: collect the fee and move the rest. In a stablecoin flow the buyer pays by Pix or SPEI, the platform adds its fee to what the buyer funds, and the seller then cashes out the stablecoin to a local bank account.
On Lumx, each seller is onboarded as its own customer with its own wallet. The checkout creates the on-ramp on the seller's behalf, the platform's cut is a partner fee set once in basis points that comes on top of what the payer funds, so the seller is credited the quoted amount, and the payout is an off-ramp from the seller's wallet to a destination in the seller's own name. Creators and affiliates take the relationship BUSINESS_PARTNER.
Supplier payments across currencies
A buyer owes an invoice in another currency. The stablecoin route quotes the amount in the supplier's currency, locks the rate while the buyer approves, and pays the supplier's local account.
Two limits matter. A supplier with no local rail receives USD by SWIFT, so the speed gain shrinks. And Bre-B payments in Colombia are capped at 1,000 UVB per payment under Circular Reglamentaria Externa DSP-465 of the Banco de la República (about COP 12.1 million in 2026), so an invoice above the cap needs a destination registered on ACH Colombia from the start, which has no per-payment limit.
On Lumx, the buyer requests a locked rate for 30 seconds, 1 minute or 5 minutes (the 30-second lock carries no fee), and passes its ID on the off-ramp so the payout settles at the quoted price. The destination holder relationship is SUPPLIER and the purpose code is trade transactions. Suppliers outside the local rails are paid in USD over SWIFT with UETR and MT103 confirmations, and euro and pound suppliers are paid over SEPA and Faster Payments.
Collecting USD from clients abroad
A Brazilian or Mexican company that invoices clients in dollars wants an account number that clients can pay by ACH or wire, with no US entity. The collection lands in dollars and converts to a stablecoin. Once the deposit has landed, it can be paid out in reais or pesos over Pix or SPEI, which are instant. Timing depends on the inbound rail: ACH takes 1 to 2 business days, FEDWIRE the same day and SWIFT 1 to 5.
On Lumx, the answer is a named virtual account (a local account number issued in the customer's own name). A USD account takes ACH (credit only), FEDWIRE and SWIFT deposits, and any individual or company in a country on the supported countries list can open one. For each expected deposit the platform creates an on-ramp with the exact amount, and the response carries the payment instructions to give the client. When the deposit matches, it converts and the wallet is credited. A company without a local entity can hold named accounts in BRL and MXN too. The account type itself is on the named virtual accounts page.
Treasury moves between entities
A group has cash in one entity and a bill due in another. A stablecoin balance settles at any hour, weekends included. The limits are the bank legs, which still run on banking schedules, and an accounting policy for holding a stablecoin balance before the first sweep.
On Lumx, deposits in each currency land as stablecoin in the customer's wallet, with no separate per-currency balances. When each subsidiary is its own customer, funds move between their wallets in seconds, with no FX step, and a payout to a subsidiary's bank account carries the purpose LOAN.
Remittance-style payouts and dollar accounts for fintechs
These two use cases are products other companies build: an app that lets a sender pay a relative abroad, and an app that gives users a dollar balance with deposit details and a cash-out.
The builder owns the licences its jurisdiction requires.
On Lumx, senders are individual customers verified before they move funds. The sender funds a wallet by a local rail, the recipient is registered as a destination with the purpose BILLS, or PERSONAL_ACCOUNT when a person sends to their own account, and a locked quote shows the exact amount the recipient will get before the sender confirms. A dollar account app uses the same customer and wallet objects.
Is a stablecoin payment regulated, and what are the risks?
Yes, and the norms aim at the provider that handles the stablecoin, not at USDC itself. The paying company's job is to use a provider inside the local regime and to know its own tax position. The country guides cover stablecoin regulation in Brazil, and in Mexico in depth.
The norm that reaches a stablecoin payment in each country, and the main risk with the control on Lumx (see Methodology for what could be read)
Topic | What applies | On Lumx |
Brazil | Law 14.478 of December 21, 2022 and BCB Resolutions 520 and 521 of November 10, 2025: virtual asset providers need Central Bank authorization, with a transition regime in Article 88 of Resolution 520, and Resolution 521 ties payments and transfers with virtual assets into the FX framework (Article 76A of Resolution 277/2022) | The Brazilian entity applied for authorization and operates under the transition regime |
Mexico | Fintech Law of March 9, 2018 and Banxico Circular 4/2019, published on March 8, 2019: Banxico decides which virtual assets licensed fintechs and banks may operate with | Payouts run over SPEI to a destination verified before first use |
Colombia | As of November 1, 2026, no dedicated stablecoin law; Circular DSP-465 caps Bre-B at 1,000 UVB per payment | The peso leg runs on a banking partner's sponsored program, under the partner's licence, and the reports to the UIAF are the partner's |
Compliance hold | A payment stops until a document arrives | KYB and KYC run first, with KYC through Sumsub and blockchain monitoring through Chainalysis; a hold surfaces as an RFI status and a webhook |
Custody and nesting | Who holds the stablecoin, and money pooled for parties nobody can see | Wallets are custodial, each payout debits the customer's own wallet, and nested payments are refused |
Peg risk falls on whoever holds a balance, so it matters most for treasury. See are stablecoin payments safe.
When a stablecoin payment is the wrong tool, and where to start
Skip the stablecoin when the payment never crosses a currency, such as a Pix payment between two Brazilian accounts.
Skip it when the recipient needs a SWIFT confirmation for customs or a bank file. Pay by SWIFT in USD, which returns the UETR and MT103.
Skip it when the payer collects money for third parties nobody has verified, which compliance screening cannot clear. Lumx refuses these as nested payments.
Skip it as a payroll system when the real need is payslips, tax withholding and local employer filings.
To pick a pilot, list last quarter's cross-border payments by corridor, drop the ones where the payment stays in one currency or the receiving country has no local rail, and price the top corridor both ways: the amount that arrived by wire against a live quote.
<!-- OPERATOR PARAGRAPH --> I would pick the cross-border payment a company already makes most often, as long as the receiving country has an instant rail, and run ten real payments through it before touching anything else. I would leave treasury for last, because treasury needs an accounting policy before the first payment and the other use cases do not.
What the seven use cases look 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.
Pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. Coverage by country is on the Lumx coverage page, and the product overview is on global payments. The sandbox is open for a first corridor.
Methodology and sources
Product behavior comes from the Lumx docs pages read on docs.lumx.io on November 1, 2026. The Bre-B cap comes from Circular Reglamentaria Externa DSP-465 of the Banco de la República, Asunto 18, numeral 3.2, with the 2026 UVB value from the Banco de la República's Bre-B page, read November 1, 2026. The norms in the regulation table come from our regulation guides. The BCB resolutions and Banxico's circular link to the official portals. The statement that Colombia has no dedicated stablecoin law rests on our Colombia regulation guide, which read Superintendencia Financiera Carta Circular 78 of 2016 and Bill 510 of 2025. For the concept behind every use case, start with what a stablecoin is and what a stablecoin corridor is.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Frantisek Duris on Unsplash.
What are the main stablecoin payment use cases for businesses?
Seven recur: contractor payroll, seller payouts, supplier payments, USD collections, treasury moves, remittance-style payouts and fintech dollar accounts. Lumx covers each one through a single API of customers, wallets, named accounts, locked quotes and local payouts.
Can a company pay employees and contractors in stablecoins?
Yes: the company funds in dollars and each person receives local currency in a bank account, with no crypto wallet needed. For employees, payslip, payroll tax and withholding stay with the employer's payroll process. On Lumx, the employer is a business customer, each payee is a verified destination under the employer's customer record, and every payout is an off-ramp transaction tracked by status and webhook.
Are stablecoins good for remittances?
They can be, when the receiving end has a local instant rail and the sending app holds the licences its jurisdiction requires. On Lumx, senders are verified as individual customers and a locked quote shows the exact amount the recipient will get.
Are stablecoin payments legal for a company in Brazil, Mexico or Colombia?
The norms regulate the provider that handles the stablecoin, not USDC or USDT as such. Brazil requires virtual asset providers to hold Central Bank authorization, with a transition regime for those already operating. Mexico limits what licensed fintechs and banks may do with virtual assets, and Colombia has no dedicated stablecoin law as of November 1, 2026. Lumx runs KYB and KYC before any money moves, and its Brazilian entity applied for authorization and operates under the transition regime.
Which stablecoin payment use case should a business start with?
Pick the cross-border payment you already make most often, where the receiving country has an instant rail, and compare a batch of real payments with what the wire delivered. Leave treasury for last, since it needs an accounting policy first. Lumx has a sandbox environment for a dry run before any production payment.
