The best stablecoin payment provider for Mexico is the one that runs SPEI (the interbank transfer system run by Banxico) in the direction your money moves, issues a CLABE (the 18-digit account number) in your customer's name if you collect, and names the licensed entity behind the peso leg. As of November 2026, eight providers list SPEI.
Quick answer by need, from the table below:
SPEI for both collection and payout: Lumx, Bridge, Due and Avenia, with Rain through its own account product.
A CLABE in the customer's own name: Lumx and Rain.
A payout only, with no collection side: UnblockPay and Crossmint.
SPEI listed in the API but with no published route: Conduit.
Pix in and SPEI out from one call: UnblockPay.
This post sorts the providers by what runs in production today and by how each answers the licence question. The regional map is in the best stablecoin APIs for LATAM, and the Brazilian equivalent is best stablecoin payment providers in Brazil.
What a business buys when it adds stablecoins to a Mexican flow
Three different things, and a provider that suits one is often a poor fit for the others.
The first is a collection: a Mexican business or a foreign company that sells into Mexico receives pesos over SPEI and wants them in USDC or USDT. What matters is the account that receives: a CLABE that identifies your customer and stays valid next month, or a payment instruction that lives for one transaction. A named virtual account is the product for the first case.
The second is a payout: paying a supplier, contractor or parent company in pesos from a dollar balance. The rail is SPEI, and the destination is the recipient's CLABE. SPEI runs around the clock, so the variable is who the recipient sees as the sender. The steps are in sending USDC to Mexico, the rail itself in the SPEI guide, and the cost of a BRL-to-MXN payout in the pricing breakdown.
The third is a product built on a stablecoin balance, such as a card or a wallet. Issuers and card platforms do better here than payments infrastructure.
The providers that run SPEI for Mexico today
Rails and account types as published on the lumx.io compare pages, checked between September and November 2026. The Lumx row comes from our own documentation, read November 16, 2026.
Provider | SPEI collection | SPEI payout | MXN account | Verified comparison |
Lumx | Yes, to a CLABE with a memo reference | Yes, 24/7/365 | Named, in the customer's name; active right after approval | |
Bridge | Yes, MXN virtual account with a CLABE | Yes | Virtual account; the compare page does not record whose name it is in | |
Due | Yes, CLABE in | Yes | In Due's name, not the customer's | |
Avenia | Yes, a CLABE per payment | Yes | No standing account; a new CLABE on each ticket | |
Rain | Yes, virtual account funding from first or third parties | Yes, from the virtual account | Named, in the end user's legal name | |
UnblockPay | No | Yes, plus Pix in to SPEI out | No; per-payment instruction | |
Crossmint | No, card and wallet onramp | Yes, offramp | No | |
Conduit | A CLABE deposit block is listed | Listed as a rail value | No named MXN account; route opened rail by rail |
Circle is not in the table (its comparison page has the detail). It issues USDC and funds or redeems a Circle Mint account in Mexico through a rail it calls CUBIX, and its Payments Network lists SPEI in a sandbox example, with partner institutions running the peso leg. It sits upstream of this list, as the issuer. Bloquo documents Pix (Brazil's instant payment system) with worked examples and no SPEI; see its comparison page. BVNK ships no Latin American rail. Trace Finance and Transfero are Brazil-first, and SPEI shows up only on a product page or a calculator. Rain's documentation is gated, so its row comes from the public site.
Conduit's row is the one most likely to change as routes open.
Who operates each leg of a peso payment in Mexico?
Mexican law splits the work between two kinds of institution, and the split explains why "we work with licensed partners" is not an answer.
SPEI is administered and operated by Banxico as a real-time settlement system that runs 24/7. Its participants are entities regulated at federal level in financial matters, and a company that is not one reaches SPEI through a participant, according to Banxico's SPEI information page, read November 16, 2026.
The Ley Fintech (the 2018 fintech law, published in the Diario Oficial de la Federación on March 9, 2018) creates the institution that holds customer money in this setting. Article 22 reserves to companies authorized by the CNBV (the banking and securities regulator) the habitual, professional business of issuing and redeeming electronic payment funds and moving them between clients, and calls them IFPEs (instituciones de fondos de pago electrónico). Article 23 says those funds are referenced to pesos or, with Banxico's authorization, to foreign currency or to a virtual asset Banxico has determined. Article 26 repeats that foreign currency and virtual assets need Banxico's prior authorization. The CNBV's fintech sector page describes these activities as reserved and requiring express CNBV authorization.
The stablecoin side is where Mexico is unusual. Article 30 of the same law defines a virtual asset and excludes foreign currency and any asset denominated in it. Banxico's Circular 4/2019 (published March 8, 2019, amended by Circular 37/2020) lets banks and fintech institutions carry out only operations with virtual assets that are internal operations, with Banxico's prior authorization, and says operations through which an institution would offer its own clients exchange, transmission or custody of virtual assets are not eligible. How the anti-money-laundering statute reaches everyone else, and why a dollar stablecoin has no licence of its own, is in stablecoin regulation in Mexico.
Read together, the texts treat a licensed peso institution and a stablecoin service as different things, and the one holding pesos is not meant to custody or exchange the token for its clients. That is a reading of the norms as written, and whether a given structure fits is a question for Mexican counsel. For an evaluation, it becomes one question per provider: which entity holds the pesos and executes SPEI, under which Mexican authorization, and which entity performs the stablecoin service. The compare pages do not record the peso-leg entity for each provider, so ask for it in writing.
Named CLABE or payment instruction, the decision that sorts Mexico
Every provider with SPEI can receive a transfer. What differs is what the payer is paying to.
A named CLABE is a standing account in your customer's name. A counterparty pays it from any bank, the details go on an invoice, and they are still valid next quarter. A per-payment instruction is a CLABE generated for one transaction: fine for a checkout or a top-up, awkward for an invoice that a payer's accounts-payable team settles on day 45. A provider-named account sits in between, and it matters when the payer's bank checks the beneficiary name.
On the payout side the same question is about the sender. A SPEI payment arrives with a sender's name on it, and an unfamiliar name invites questions at the recipient's bank. A named account means the recipient sees your customer. Whether a foreign company needs a Mexican entity is in local entities in Brazil and Mexico, and the account type in named virtual accounts. Paying a US supplier from Mexico is in paying US suppliers, and how the Mexican rail sits next to the others is in Latin America payout rails compared.
I would start any Mexico evaluation by asking each provider to name the entity that executes the peso leg, before looking at rails or price. A rail list is easy to copy from a competitor's page, and the entity behind it is not. When the answer is a type of licence, such as an IFPE, the follow-up is whose licence it is.
What do the specialists and the multi-country providers each do better?
Most providers that reach Mexico do it as one country in a list, and the useful differences are narrow.
UnblockPay has the cleanest answer for one corridor: a single fiat-to-fiat call that takes Pix in and pays SPEI out, with one quote covering both legs. A Brazilian importer paying a Mexican supplier fits that, and it fits a payout-only product. It documents named accounts in USD and EUR only, so there is no standing CLABE for the Mexican side to collect on. Crossmint sells wallet infrastructure and an offramp that pays SPEI, which suits a wallet whose users cash out to a Mexican bank. Avenia is stablecoin-native, with subaccounts and a CLABE on each ticket, which suits a product that thinks in balances.
Rain is a card issuer whose MXN virtual account exists to fund card spend: a serious option for a card, a different layer for collections and payouts. Bridge and Due cover Mexico alongside many other currencies. Due holds the MXN account in its own name, and Bridge's compare page does not record whose name the CLABE is in, which is the question to put to them.
Lumx is a multi-country provider, so the case that a second currency changes the choice favours us, and you should weigh it that way. For a product that only pays Mexican suppliers from Brazil, UnblockPay's single call is worth a trial. The multi-country case is for businesses whose users keep a CLABE in their own name and also pay or collect in other currencies, which is most B2B fintechs and few consumer ones.
The questions to ask before a pilot
Five, in the order they eliminate providers:
Which entity holds the pesos and executes SPEI, under which Mexican authorization, and is it the entity that signs your contract?
Is the CLABE a standing account in your customer's name, a shared account, or a new instruction per payment?
What does the recipient's bank statement show as the sender on a SPEI payout?
What happens to a deposit that arrives without the reference, from a third-party payer, or above a limit?
What are the limits at standard verification, and is there an enhanced path for companies?
The fourth is the one most often skipped. A SPEI deposit that matches nothing is the support ticket that eats the first month.
When a stablecoin provider is the wrong tool for Mexico
A flow that is pesos on both ends does not need a stablecoin. A Mexican company paying a Mexican supplier uses SPEI through its own bank. The stablecoin earns its place when a second currency enters, usually dollars.
A business that only needs an occasional dollar wire converted may do better at its bank's foreign exchange desk than under a provider contract. And a consumer wallet or a card starts with the specialists above, not a payments API.
What this looks like on SPEI with 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 Mexico, the answers to the five questions run as follows. Lumx is not a bank, and MXN payments run through a partner licensed as an IFPE, under the partner's licence; the stablecoin is held in custodial wallets segregated per customer. The MXN account is a named account in the customer's name, and you request it in the accounts array when you create the customer. It becomes active right after the customer is approved, with no waiting period, and a foreign company can hold it without a Mexican entity.
To collect, an autoconversion rule on the MXN account returns a CLABE and a memo to use as the payment reference, and every deposit paid with that reference converts to USDC or USDT at the market rate. A third-party payer is allowed, and an unusual one can trigger an RFI (request for information, a compliance hold that asks for a document before a transaction clears). For a one-off collection, an on-ramp turns a single payment into stablecoin.
To pay, you register the recipient's CLABE as a destination, with the holder's RFC (the Mexican tax ID) and the relationship to your customer, such as supplier. After the destination is approved, one off-ramp request moves USDT from the customer's wallet through conversion to the SPEI payment. SPEI has no cut-off on Lumx and runs 24/7/365; the Coverage page lists settlement as instant. On a SPEI payout the recipient sees the customer as sender, and Lumx deducts nothing from the pesos that arrive, so only the recipient's bank can take a fee. Each step sends a webhook, and a payout that fails returns a failure event. Limits attach to the customer, and the API shows what is left against them. The Coverage page lists the rails by country.
Methodology and sources
Providers were included if a comparison page on lumx.io/compare, verified against the provider's public site and API documentation between September and November 2026, shows SPEI live or listed. Where a page and this post disagree, the page is current. No provider was contacted and no pricing was compared. The year in the title looks ahead: every fact here is as of November 16, 2026.
Mexican sources read on November 16, 2026: the Ley Fintech as published on March 9, 2018 (Articles 22, 23, 26 and 30); Banxico Circular 4/2019 as published on March 8, 2019 (provision 3.a); Banxico's SPEI information page; and the CNBV page on the fintech sector. Lumx facts come from docs.lumx.io pages read the same day: Coverage, Payment rail cut-off times, Accounts, Destinations, Autoconversion rules, Sender of record and the guide to converting USDT to MXN and paying out over SPEI.
Verified on November 16, 2026. Operational context, not legal, tax, or investment advice. Ley Fintech (Articles 22, 23, 26, 30) checked against dof.gob.mx on November 16, 2026. Banxico Circular 4/2019 checked against banxico.org.mx on November 16, 2026.
What are the best stablecoin payment providers for Mexico?
It depends on whether the flow is a collection, a payout or both. As of November 2026, eight providers list SPEI: Lumx, Bridge, Due, Avenia, Rain, UnblockPay, Crossmint and Conduit. Lumx runs SPEI in both directions on a named MXN account in the customer's name, active right after approval.
Which stablecoin providers can pay a CLABE in Mexico?
Lumx, Bridge, Due, Avenia, Rain, UnblockPay and Crossmint document SPEI payouts, and Conduit lists SPEI as a rail value without a published route. A payout needs the recipient's 18-digit CLABE. On Lumx you register it as a destination, with the holder's RFC, and the recipient sees your customer as the sender.
Does a stablecoin provider need a Mexican licence?
The peso leg has to run through an institution authorized under Mexican law, such as an IFPE authorized by the CNBV under Article 22 of the Ley Fintech, and the Banxico circular does not let such institutions custody or exchange virtual assets for their clients. Ask each provider which entity executes each leg. On Lumx, MXN payments run through a partner licensed as an IFPE, under the partner's licence.
What is the difference between a named CLABE and a per-payment CLABE?
A named CLABE is a standing account in your customer's name that you can put on an invoice and reuse. A per-payment CLABE is generated for one transaction and expires with it. Business collections usually need the first, and a checkout works with the second.
Can a foreign company collect pesos over SPEI without a Mexican entity?
On Lumx, yes. A foreign company can hold a named MXN account with a CLABE in its own name and collect over SPEI without a Mexican entity. Ask other providers whose name the CLABE is in before relying on it.





