Your drivers in Guadalajara expect their weekly payout on Friday. Your dollar wire left on Wednesday, and nobody can tell you when the pesos will land.
SPEI payouts to Mexico with stablecoin settlement close that gap. You fund in USDC or USD, lock a quote, and your recipient gets Mexican pesos (MXN) in their bank account over SPEI, Mexico’s real-time payment system.
Mexicans already live on SPEI. Banco de México reports 7,308.1 million SPEI transfers in 2025, worth 591.8 trillion pesos. That value equals about 16.8 times Mexico’s GDP for the year.
This guide covers why paying into Mexico still breaks, how the stablecoin-funded SPEI flow works and which recipient details you need. It then walks through your first MXN payout by dashboard and by API.
Why Paying Out in Mexico Is Harder Than It Should Be
Mexico has one of the best domestic payment rails in the world. The trouble starts when your money comes from outside the country and has to cross into that rail.
Small cross-border transfers are expensive. Sending small amounts abroad costs an average of 6.36% of the amount sent, according to the World Bank. On a US$40,000 monthly contractor run, that average would cost you US$2,544 every month. We break down more of these costs in the hidden costs of international payments.
The exchange rate moves under you. Banco de México set the FIX rate at 18.1903 pesos per dollar on October 2, 2026. The peso gained 0.71% that day alone, so a rate fixed hours earlier can already be stale.
New payees face waiting periods. Banco de México notes that online banking often asks you to register a new account first and wait before you can pay it. That slows down every new contractor or supplier you onboard.
A wrong CLABE means a return. SPEI rejects or returns transfers with bad data. One mistyped digit can push a payroll line back to you and leave your recipient unpaid.
SPEI Payouts to Mexico with Stablecoin Settlement: How It Works
Yativo is payment infrastructure, not a bank. We use stablecoins as the settlement layer between your balance and Mexico. A licensed local payout partner then delivers the pesos over SPEI.
- You fund your Yativo float balance with a fiat or stablecoin deposit, such as USDC.
- Yativo converts the payout value to USDC and settles it on-chain.
- A licensed local payout partner in Mexico receives the stablecoin settlement.
- The partner converts USDC to MXN and sends a SPEI transfer to the recipient’s CLABE.
- Your recipient receives pesos in their normal bank account.
Your recipient does not need a crypto wallet. They never see or touch stablecoins. On their side, the payment arrives as a SPEI deposit from a local sender.
Mexico’s economy runs on money from abroad. The country received US$61.79 billion in remittances in 2025, and 99.1% of it arrived as electronic transfers. For more on the settlement layer, read how to receive international payments in stablecoins.
Supported Payout Rails for Mexico
Yativo’s Mexico payout list includes SPEI and Bank Transfer for pesos, plus SWIFT for dollars. This guide focuses on SPEI.
SPEI (MXN)
SPEI is run by Banco de México and operates 24/7 as a real-time settlement system. It moves pesos between accounts at different financial institutions inside Mexico.
Your Mexico list can show more than one SPEI entry. Our gateway list carries SPEI as gateway ID 1, which the API documentation uses in its Mexico examples, and as gateway ID 759. Use the ID that the live methods response returns for your account.
Required details: the CLABE and the beneficiary’s full name, per the gateway 1 form in our API documentation.
Settlement time: payouts via SPEI settle in under 30 minutes, end to end.
Best for: contractors, gig and marketplace sellers, refunds and high-frequency payouts that need to land fast.
Bank Transfer (MXN)
Bank Transfer, gateway ID 767, is our second peso payout method for Mexican bank accounts. We cover it in detail in our guide to local bank transfer payouts to Mexico.
USD alternatives
SPEI delivers pesos only. If your recipient wants dollars, use SWIFT, gateway ID 656, which pays USD. Availability depends on your account, so check the live list before you build.
Recipient Details to Collect Before Your First SPEI Payout
The Mexico payout form in our API is the authoritative field list. For gateway 1 it asks for two fields, so collect them cleanly during onboarding.
- CLABE: the 18-digit standardized account code, which identifies one account at one institution. Copy it from the bank’s app or a statement.
- Beneficiary full name: the legal name of the person or the registered name of the company that holds the account.
- Holder type: individual or company, so your records match your invoices and contracts.
- Tax ID (for your records): the RFC, Mexico’s taxpayer registry code, if your accounting needs it.
- Bank name: useful for support, since the first three CLABE digits identify the bank.
Ask for a screenshot of the CLABE from the bank’s app. It removes most typing errors before the first payout.
How to Send a SPEI Payout via Yativo
Option 1: Dashboard (for manual payouts)
- Fund your Yativo float balance with either a fiat or a stablecoin deposit.
- Go to Transfer in your Yativo dashboard.
- Select the float wallet you are paying with, for example USD, EUR, MXN or whichever balance you funded.
- Choose the customer you are paying on behalf of. This step is necessary for fintechs that run payouts on behalf of their customers.
- Choose Mexico as the destination country and the SPEI payout method.
- Enter the recipient details: the 18-digit CLABE and the beneficiary’s full name.
- Enter the amount in USD or MXN.
- Review the quote: exchange rate, fees, delivery time and the exact MXN amount your recipient receives.
- Confirm with your PIN and 2FA.
- Track the payout in real time and download the receipt for your records.
Option 2: API (for automated and bulk payouts)
Every endpoint below is in the Yativo API documentation. Production calls go to https://api.yativo.com/api/v1, and the sandbox runs at https://smtp.yativo.com/api/v1.
Authenticate every request with the X-Api-Key and X-Api-Secret headers. Each key only works from the server IPs listed on it. These API keys replaced bearer tokens, and login tokens stop working from servers on October 15, 2026, as covered in our October update. Every POST request also needs a unique Idempotency-Key header.
Step 1. Generate a USDC funding address on Solana to top up your USD balance:
POST https://api.yativo.com/api/v1/crypto/create-wallet
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: 7b1c2d3e-4f5a-4b6c-9d7e-8f9a0b1c2d3e
Content-Type: application/json
{
"currency": "USDC_SOL"
}
Step 2. List the payout methods available for Mexico:
curl "https://api.yativo.com/api/v1/payment-methods/payout?country=MEX" \
-H "X-Api-Key: $YATIVO_API_KEY" \
-H "X-Api-Secret: $YATIVO_API_SECRET" \
-H "Accept: application/json"
SPEI appears with gateway ID 1 in the documentation examples. Always read the ID from the live response instead of hardcoding it.
Step 3. Fetch the required fields for that gateway:
GET https://api.yativo.com/api/v1/beneficiary/form/show/1
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
For gateway 1, the documented form returns two required fields: clabe and beneficiary. If your account uses gateway 759, run the same call with that ID and build payment_data from the response.
Step 4. Create the beneficiary with the CLABE and full name:
POST https://api.yativo.com/api/v1/beneficiaries/payment-methods/
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: 2c3d4e5f-6a7b-4c8d-8e9f-0a1b2c3d4e5f
Content-Type: application/json
{
"gateway_id": 1,
"nickname": "Norte Logistica SA de CV",
"currency": "MXN",
"customer_id": "e8caa491-57b6-4c39-9e3a-d2c97e47fbf0",
"payment_data": {
"clabe": "012180000000000002",
"beneficiary": "Norte Logistica SA de CV"
}
}
Step 5. Optionally, lock your rate. Quotes hold for 5 minutes:
POST https://api.yativo.com/api/v1/exchange-rate
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: 9d0e1f2a-3b4c-4d5e-8f6a-7b8c9d0e1f2a
Content-Type: application/json
{
"from_currency": "USD",
"to_currency": "MXN",
"method_id": 1,
"method_type": "payout",
"amount": 2500
}
Step 6. Initiate the payout from your USD balance:
POST https://api.yativo.com/api/v1/wallet/payout
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: 4e5f6a7b-8c9d-4e0f-9a1b-2c3d4e5f6a7b
Content-Type: application/json
{
"debit_wallet": "USD",
"amount": 2500,
"payment_method_id": 5120,
"customer_id": "e8caa491-57b6-4c39-9e3a-d2c97e47fbf0",
"quote_id": "4a72ecf8-6c8a-4e38-9971-8aabe9f785ed"
}
Use the id from the beneficiary response as payment_method_id. Leave out quote_id if you did not lock a rate. For bulk runs, repeat the call per beneficiary, as described on our payouts page.
Which Mexico Payout Option Should You Use?
| SPEI (MXN) | Bank transfer (MXN) | USD via SWIFT | |
| Settlement speed | Under 30 minutes | Under 30 minutes | Depends on correspondent banks |
| Required details | CLABE, beneficiary name | See API documentation | See API documentation |
| Best for | Contractors, sellers, refunds | Suppliers, payroll | Recipients who want USD |
| Availability | Active | Active | Active |
| Currency received | MXN | MXN | USD |
Best Practices for SPEI Payouts to Mexico
Validate the CLABE before you save it. The 18th digit is a check digit, so a simple validation in your onboarding form catches most typos. It is cheaper than chasing a returned payout.
Match the name to the account holder. Use the exact legal name on the account, including the company suffix such as SA de CV. Mismatched names are a common reason for returns.
Lock the rate on large runs. Exchange-rate quotes hold for 5 minutes, so lock one before payroll or a large supplier batch. You then know the exact peso amount before you confirm.
Keep the CEP for disputes. Banco de México issues the CEP within 30 minutes of the deposit, and you can look it up for 45 working days. Store the tracking details with each payout so you can resolve questions fast.
Read gateway IDs at runtime. Mexico has more than one SPEI entry and a separate Bank Transfer method. Pull the IDs from the payout methods endpoint instead of hardcoding them.
Run one playbook across LATAM. The same flow works in other markets. See our guide to local payouts to Argentina via bank transfer, our breakdown of LATAM payout rails and our guide to paying Chinese suppliers from Mexico.
Frequently Asked Questions
Does my recipient in Mexico need a crypto wallet?
No. Your recipient gets Mexican pesos in their normal bank account over SPEI. They never interact with stablecoins, and the deposit looks like any domestic transfer.
Is it legal and compliant to pay Mexican recipients this way?
Yes, when the payout runs through regulated infrastructure. Yativo is registered with FinCEN as a Money Services Business, registration number 31000270723339. A licensed local payout partner sends the SPEI transfer, so your recipient sees a normal local payment. Your own tax and invoicing duties still apply, so confirm them with your advisor.
How long does a SPEI payout take?
Payouts via SPEI settle in under 30 minutes, end to end. On the local leg, Banco de México says a SPEI transfer should not take more than 30 seconds once the sending bank approves it.
Can I pay to a debit card or phone number instead of a CLABE?
SPEI itself accepts a CLABE, a 16-digit debit card or a 10-digit phone number linked to an account, according to Banco de México. The Yativo SPEI form in our API documentation asks for the CLABE and the beneficiary’s full name. Collect the CLABE to keep your payouts consistent.
How can my recipient prove they were paid?
Every SPEI transfer can be backed by a CEP, the electronic payment receipt issued by Banco de México. Your recipient can look it up on the CEP site with the date, amount, banks and tracking key. You can also download the Yativo receipt from your dashboard.
Can my recipient receive US dollars instead of pesos?
Not through SPEI, which only moves pesos. For dollars, use SWIFT, gateway ID 656, which pays USD. Check GET /payment-methods/payout?country=MEX for the methods enabled on your account.
Start Sending SPEI Payouts to Mexico
SPEI handled over 7.3 billion transfers in 2025, so your recipients already expect pesos to arrive in seconds. Yativo lets you fund in USDC or USD and deliver MXN to any CLABE through a licensed local payout partner. Your payouts settle in under 30 minutes, and you get one API for every corridor. Book a demo to set up your first SPEI payout.
Sources
- Banco de México: Informe Anual sobre las Infraestructuras de los Mercados Financieros 2025
- Banco de México: Ingresos y Egresos por Remesas, diciembre de 2025
- Banco de México: SPEI, información
- Banco de México: Information for SPEI users
- Banco de México: MI SPEI, transferencias
- Banco de México: Comprobante Electrónico de Pago (CEP)
- Heraldo Binario: Precio dólar: Peso cierra ganando terreno este viernes 2 de octubre
- World Bank: Remittance Prices Worldwide
- Yativo: Yativo API Documentation
- Yativo: Safer API access, three new virtual accounts and new payment links