How to pay US suppliers from Brazil and Mexico with stablecoins

Paying a US supplier from Brazil or Mexico with stablecoins means converting the company's local currency into USDC and paying out dollars to the supplier's US bank account over ACH or wire. The supplier receives an ordinary domestic dollar transfer and never handles a stablecoin. The stablecoin only carries the value across the border.

The opposite direction, a US company paying suppliers in Brazil or Mexico, is a different route and is not covered here.

The route, from the local transfer to the supplier's bank

The payment has three legs. The first is local: the company pays reais over Pix (Brazil's instant payment system, run by the Central Bank) or pesos over SPEI (Mexico's interbank transfer system, run by Banxico). The second is the conversion into the dollar stablecoin USDC, which can sit in a wallet until the company decides to pay. The third is a dollar payout to the supplier's US bank account over ACH or FEDWIRE (the Federal Reserve's same-day wire system).

A bank remittance does the same job through a foreign exchange contract and a correspondent chain whose status the sender cannot see until the money arrives. Stablecoins versus SWIFT payments sets the two designs side by side, and the stablecoin corridor explainer shows how the legs connect. The same structure toward China is in our guide to paying suppliers in China from Brazil, where the supplier's country decides whether a stablecoin can be used at all. A US supplier never touches one.

1. Onboard the paying company. KYB (know your business, the verification of a company and its owners) on the company, identified in Brazil by its CNPJ (the Brazilian company taxpayer ID).

2. Fund in local currency. Reais over Pix or pesos over SPEI, from the company's business bank account. Both rails run around the clock, so funding never waits for a US cut-off.

3. Hold or convert at once. The money becomes USDC in the company's wallet. A company that pays several US suppliers a month can fund once, when the rate suits, and pay from that balance (see natural FX hedge in Brazil on holding it), as in our guide to converting BRL to USDC for treasury.

4. Register the supplier, then pay out. The supplier's US bank details go in once, with the relationship declared as a supplier. The USDC then converts to dollars and leaves over ACH or FEDWIRE.

On Lumx the legs are an on-ramp that credits the customer's wallet and an off-ramp to a registered destination. The BRL and MXN accounts are created with the customer and go active right after approval, per the Lumx accounts documentation, and the API returns the Pix code or the SPEI CLABE (the 18-digit Mexican bank account number) for each deposit. Lumx targets one business day for KYB.

What Brazil and Mexico each ask of the payer

Brazil regulates the company that handles the stablecoin, not the stablecoin. Law 14.478/2022 requires virtual asset service providers to be authorized by the Central Bank of Brazil (BCB). Resolution 521/2025 introduced Article 76A into Resolution 277/2022, which defines payments and transfers with virtual assets as an activity of a PSAV (Prestadora de Serviços de Ativos Virtuais, Brazil's virtual asset service provider authorization), and Resolution 520/2025 sets the transition regime in its Article 88. Resolution 561/2026, published April 30, 2026, bars virtual assets from the eFX cycle, the foreign exchange route for payment institutions, but not Article 76A. Our guide to stablecoin regulation in Brazil walks through each norm.

For the payer, that means an authorized provider, a payment declared as an invoice for goods, and the invoice kept, because purpose is the first question any reviewer asks.

Mexico has no stablecoin law. Under the Fintech Law of March 9, 2018, banks and licensed fintechs may operate with a virtual asset only if Banxico has determined that asset and authorized the operation (Articles 30 and 88), and the CNBV (Mexico's banking and securities regulator) supervises the fintechs. A company paying its own supplier through a provider is that provider's client, not someone offering exchange or custody to others, which is what Article 17 section XVI of the anti-money-laundering statute reaches. The Mexico regulation guide has the articles.

Lumx is not a bank. In Brazil it operates as a virtual asset service provider under the Article 88 transition regime of Resolution 520/2025, and in the United States it is registered with FinCEN as an MSB (money services business, the FinCEN registration category). A purpose that does not match the underlying activity can put a payment on hold for an RFI (request for information, a compliance hold that asks for a document before a transaction clears), so keep the supplier invoice at hand.

What the US supplier has to give you

A US bank account is described by a short list: the supplier's legal name exactly as the bank holds it, its tax ID and address, the receiving bank's name and address, the ABA routing number, the account number, and whether the account is checking or savings. It has to be a dollar account, and the supplier's finance team should send it in writing.

The name on the invoice and the name on the bank account must be the same entity, so a supplier that invoices through a parent company is paid as that company. ACH reaches nearly any US account and is the default; FEDWIRE is for an invoice due today at a bank that takes wires.

On Lumx, an ACH or FEDWIRE destination takes the account type (CHECKING or SAVINGS), account number, ABA routing number, bank name and address, and the holder's legal name, tax ID and address. The holder relationship is SUPPLIER and the off-ramp carries the purpose TRADE_TRANSACTIONS, which the purpose codes page defines as payments for goods or services. The supplier's statement shows the paying company's legal name as sender, not Lumx, per the sender of record page.

How long does a payment to a US supplier take?

The dollar leg has a clock, and the clock is Eastern time.

Rail times and cut-offs for each leg, from the Lumx documentation read on November 1, 2026.

A payout requested after the cut-off, on a weekend or on a US federal holiday is processed on the next US business day.

Cut-offs in local time. US standard time runs from November 1, 2026 to March 14, 2027, and US daylight time outside that period.

Take an invoice due Friday, paid from USDC already held. A FEDWIRE payout requested in São Paulo on Tuesday before 5:00 PM lands that day. An ACH payout requested before 4:00 PM lands Wednesday or Thursday, and one requested at 6:00 PM lands Thursday or Friday, with no slack left. A Mexico City team has three hours less on ACH.

An RFI hold, a US bank holiday, extra review on large transfers (typically up to two business hours) and the supplier's own bank review all add time.

On Lumx, a payout moves through TRANSFERRING_STABLECOIN, TRADING and TRANSFERRING_FIAT to SUCCESS, and each change arrives as a webhook such as offramp.success. Per the cut-off times page, an off-ramp is complete once the funds leave Lumx's banking partner.

What size of invoice fits in one payment

An on-ramp and an off-ramp each have their own per-transaction, daily and monthly caps, and a supplier payment uses both: the on-ramp that funds the wallet and the off-ramp that pays the supplier.

At standard KYB the defaults are US$50,000 per transaction and US$100,000 per day and per month. An invoice of US$60,000 does not fit in one payment at standard KYB. Three US$40,000 invoices on the same day pass the daily cap on the third, at US$120,000 against US$100,000. And because the monthly cap equals the daily cap, a company that expects to send more than US$100,000 a month should ask for a higher limit before the first invoice.

On Lumx, a payment that would pass a limit is rejected with a 422 and the code TRANSACTION_LIMIT_EXCEEDED, and reading the customer with includeTransactionLimits=true returns the amount used and remaining. A limit increase goes through the dashboard or the API with a supporting document such as a bank statement, and the documented review target is one business day. The transaction limits documentation has the table.

What the payment costs and what to measure it against

A supplier payment has three costs: the spread on the conversion into the stablecoin, which is the number worth comparing between providers; a per-payment fee on each rail; and what intermediary banks deduct from an international wire, which ACH and FEDWIRE to a US account avoid because they are domestic transfers.

The comparison that decides the question is not the transit time of the dollar leg, which is a bank transfer either way. It is everything before it: the bank's foreign exchange contract, the spread inside its rate, and the days before the payment leaves. Take one recent invoice and get two numbers for the same dollars delivered. The live rate for the first leg is on the BRL to USDC page and the MXN to USDC page, and the dollar leg is on the USDC to USD page.

Lumx's pricing model is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. A locked rate holds the quote for 30 seconds, one minute or five minutes. The 30-second lock carries no fee, and the longer locks include one to cover volatility.

Start with one invoice, and keep three records

I recommend that the first payment on this route be a mid-sized invoice with a full business day of slack, not the largest invoice of the quarter. A first payment tests the supplier's bank details, the declared purpose and the paying company's limits at once, and nobody on the paying side can speed up the supplier's bank. I would rather the test be a payment that can be late than one that cannot.

Keep three records for each payment: the supplier's invoice, the confirmation of the local deposit (the Pix receipt or the SPEI tracking key), and the payout reference. They answer any reviewer.

When a stablecoin route is the wrong tool for a US supplier

When the payment is on behalf of someone else. Paying the supplier of a sister company that has not been onboarded is nesting, and a provider that must see every payer and payee will refuse it. The test is one question: whose money is it, and whose business does it pay for? The nested payments rule applies it.

When the invoice names a different entity from the bank account. That mismatch holds payments for review, and no rail fixes it.

When the payment may need to be recalled. Once a dollar payout leaves the provider, getting it back depends on the supplier agreeing to return it.

When the company's tax or accounting policy requires a bank foreign exchange contract. The stablecoin route does not produce one.

What a US supplier payment 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.

On the global payments API, the paying company is a business customer, created with a BRL account in Brazil or an MXN account in Mexico, in the company's own name. A foreign company can hold the same named accounts without a local entity in Brazil or Mexico. After KYB, the customer receives a custodial wallet on each supported blockchain, and dollar payouts to a US supplier work from USDC on Ethereum, Polygon and Base.

Funding is an on-ramp. For one known amount it returns a Pix code in Brazil or a CLABE with a reference in Mexico. For a supplier paid on a schedule, a standing autoconversion rule returns a static Pix code or a CLABE with a memo, and every deposit made with it converts to USDC. A floating on-ramp not paid within a day expires.

The payout is an off-ramp from the wallet to the supplier's destination. If a transaction is held for review, the RFI is resolved with the compliance team by email or Slack, and a transaction left unanswered for 24 hours may be refunded. The coverage page lists the rails and pairs available.

Methodology and sources

Everything said about what Lumx does was read in the Lumx documentation on November 1, 2026: Coverage, Accounts, Destinations, Transactions, Exchange Rates, Wallets, Autoconversion Rules, Transaction Limits, cut-off times, Sender of Record, Purpose Codes, Request for Information and Nested Payments. The pricing model, the KYB timing and the Brazilian entity's status are stated as in Lumx's own fact sheet.

Brazilian norms are cited by number and year, without links: Law 14.478/2022 and BCB Resolutions 277/2022, 520/2025, 521/2025 and 561/2026. The article references come from our Brazil guide, which records that bcb.gov.br did not serve a text body to our checker on September 24, 2026. The local-time cut-offs are our own arithmetic from the Eastern time cut-offs, with São Paulo at UTC-3 and Mexico City at UTC-6 all year, since neither follows daylight saving time.

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

Cover photo: Eric Prouzet on Unsplash.