Your manufacturer in Monterrey wants pesos on its CLABE before it ships. Your treasury holds USDC, and an exchange sale plus a bank wire puts the shipment at risk.
Converting USDC to MXN through Yativo is one payout. You lock a quote, and your recipient gets Mexican pesos over SPEI in under 30 minutes.
Mexico received US$61.79 billion in remittances in 2025, per Banco de México. Its SPEI rail handled 7,308.1 million transfers in 2025, worth 591.8 trillion pesos.
This guide shows how USDC to MXN conversion works on Yativo, which local rails you can use, and what to collect from recipients. It ends with dashboard steps and a full API example.
What It Means to Convert USDC to MXN and Pay Out Locally
Converting USDC to MXN means turning a dollar-backed stablecoin balance into Mexican pesos that lands in a real local account. People call this an off-ramp. The hard part is not the conversion itself. It is getting the money to the right bank account (CLABE) quickly and at a known rate.
Most businesses that hold USDC want one of two outcomes. They want to pay someone in Mexico, such as a supplier, a contractor or an employee. Or they want to move their own treasury into MXN for local costs.
Yativo handles both with one flow. You hold USDC or USD in your float balance. When you send a payout, Yativo converts the value and a licensed local payout partner credits MXN over a local rail such as SPEI and bank transfer.
Why Converting USDC to MXN Through an Exchange Is Harder Than It Looks
Selling USDC on an exchange looks simple on screen. In practice it adds steps between your balance and your recipient.
Two hops instead of one. You sell on the exchange, withdraw MXN to your own bank, then send a second transfer to the recipient. Each hop adds time, limits and another point of failure.
Spreads and withdrawal fees stack up. The quoted price on an order book is rarely what you net after spreads and withdrawal charges. Sending small amounts across borders already costs an average of 6.36% of the amount sent, according to the World Bank.
Banks may question the funds. Some banks ask for extra documents when money arrives from a crypto exchange. That review can freeze the payment you needed to make today.
New accounts often need a waiting period. Banco de México notes that online banking often asks you to register a new account first before you can pay it. An exchange cash-out plus a new payee can add days.
We break down more of these costs in the hidden costs of international payments.
How USDC to MXN Conversion Works with Yativo
Yativo is payment infrastructure, not a bank or an exchange. We use stablecoins as the settlement layer, and a licensed local payout partner delivers the MXN on a domestic rail.
- You fund your Yativo float balance with a fiat or stablecoin deposit, such as USDC.
- You request a quote that shows the rate, the fees and the exact MXN amount.
- Yativo settles the payout value on-chain with a licensed local payout partner in Mexico.
- The partner converts the stablecoin to MXN and sends a local payment to the recipient’s bank account (CLABE).
- Your recipient sees Mexican pesos in their account like any other domestic credit.
Your recipient does not need a crypto wallet. They never see or touch stablecoins. On their side, the payment looks like a normal local MXN transfer.
On the local side, SPEI is run by Banco de México and operates 24/7 as a real-time settlement system. For the wider picture, read our overview of the on-ramp and off-ramp API for businesses and how to receive international payments in stablecoins.
Local Rails for USDC to MXN Payouts
SPEI is the featured rail for USDC to MXN. Mexico also has a bank transfer gateway, POBO and SWIFT options. See our Mexico SPEI guide and Mexico local bank transfer guide.
SPEI (gateway ID 1)
Gateway 1 pays pesos to any CLABE over SPEI. Gateway 759 is a second SPEI option in our catalog. SPEI is the default way to turn USDC into MXN.
Required details: the fields returned by the form for gateway 1. Expect the beneficiary name and the 18-digit CLABE.
Settlement time: Under 30 minutes.
Limits: 1 MXN minimum and 100,000,000 MXN maximum per payout in our catalog.
Best for: supplier invoices, payroll and marketplace seller payouts.
Bank Transfer (MXN) (gateway ID 767)
Gateway 767 is a bank transfer option for MXN accounts. Use it when your account manager recommends it for a specific bank or volume.
Settlement time: Under 30 minutes.
Limits: 1 MXN minimum and 100,000,000 MXN maximum per payout in our catalog.
POBO (Local)
POBO (Local), gateway 1059, pays MXN on behalf of your business. Use it when next-day timing works for you. Any gateway with POBO in its name requires a POBO endorsement on your account.
Settlement time: T+1 (next business day).
Limits: 20 MXN minimum and 5,000,000 MXN maximum per payout in our catalog.
SWIFT (POBO) and SWIFT
SWIFT (POBO), gateway 1148, delivers MXN through SWIFT on behalf of your business. SWIFT, gateway 656, delivers USD instead. Any gateway with POBO in its name requires a POBO endorsement on your account.
Settlement time: T+1 (next business day) for both.
What You Need Before Your First USDC to MXN Payout
The form in your dashboard, or the authenticated GET /beneficiary/form/show/1 call, is the authoritative field list. For field details, see API documentation. Collect the items below before you send.
- A verified Yativo business account. KYB must be complete before you can pay out.
- A funded balance. Deposit USDC or fiat into your float balance. USDC deposits credit your balance once confirmed on-chain.
- The customer record, if you are a fintech. Payouts made on behalf of a customer need that customer’s ID.
- The 18-digit CLABE. It identifies one account at one institution, per Banco de México.
- The beneficiary name and RFC, if the form asks for it. Use the exact name registered with the bank.
- A payment reference. An invoice number or payroll period helps the recipient reconcile the credit.
Validate the CLABE check digit in your onboarding form. A wrong digit sends the payout back.
How to Convert USDC to MXN and Pay Out via Yativo
Option 1: Dashboard (for manual payouts)
- Fund your Yativo float balance with either a fiat or a stablecoin deposit, such as USDC.
- 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 and SPEI as the payout method.
- Enter the recipient details the payout form asks for, such as the beneficiary name and 18-digit CLABE.
- 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 keys replaced bearer tokens, as covered in our October update. Every POST also needs a unique Idempotency-Key header.
Step 1. Generate a USDC deposit address on Solana to fund your 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: adcc9f3e-78c9-4eb6-bf0d-fbf68b2e9f87
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 carries gateway ID 1. 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_SECRETThe response lists every required field and its accepted values. Build your payment_data object from it.
Step 4. Create the beneficiary. Replace the placeholder with the fields the form returned:
POST https://api.yativo.com/api/v1/beneficiaries/payment-methods/
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: b8ecd388-8eea-448b-99f4-b77b630018e0
Content-Type: application/json
{
"gateway_id": 1,
"nickname": "Manufacturas Regias SA de CV",
"currency": "MXN",
"customer_id": "e8caa491-57b6-4c39-9e3a-d2c97e47fbf0",
"payment_data": {
"{field_from_form}": "{value}"
}
}Step 5. Lock your MXN 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: 6cc1864d-68d8-4edc-b919-a1492b7c5bb9
Content-Type: application/json
{
"from_currency": "USD",
"to_currency": "MXN",
"method_id": 1,
"method_type": "payout",
"amount": 3000
}Step 6. Initiate the payout from your balance:
POST https://api.yativo.com/api/v1/wallet/payout
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: 76901722-3ce7-4f30-b2bd-ef54a42556bc
Content-Type: application/json
{
"debit_wallet": "USD",
"amount": 3000,
"payment_method_id": 9980,
"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. For bulk runs, repeat the call per beneficiary, as described on our payouts page.
Yativo vs an Exchange vs a SWIFT Wire for USDC to MXN
| Yativo off-ramp | Exchange sale + bank withdrawal | SWIFT wire | |
| Steps to reach the recipient | One payout | Sell, withdraw, then transfer again | One wire through correspondent banks |
| Settlement | Under 30 minutes | Depends on the exchange and your bank | T+1 or longer |
| MXN amount known upfront | Yes, in the quote | Only after the trade and fees | Often not, intermediaries may deduct fees |
| Recipient needs crypto | No | No, but you need an exchange account | No |
| Best for | Paying people in Mexico from USDC | Occasional personal conversions | Large payments with no local rail |
Best Practices for Converting USDC to MXN
Lock the rate on large payouts. Quotes hold for 5 minutes, so request one right before you approve a big MXN payment.
Validate details at onboarding. Check account formats in your own form before you save a beneficiary. Most failed payouts start with a typo.
Match the name to the account. Use the exact legal name the bank account (CLABE) is registered under. Mismatches can trigger compliance holds.
Keep a USDC buffer. Hold enough balance for your next payout cycle so on-chain confirmation time never delays a payment run.
Keep the CEP. Banco de México issues an electronic payment receipt (CEP) for SPEI transfers, which suppliers often ask for as proof.
Use idempotency keys everywhere. A unique Idempotency-Key on every POST stops a retry from sending the same payout twice.
Frequently Asked Questions
Does my recipient need a crypto wallet to receive MXN?
No. Your recipient gets Mexican pesos in their normal bank account (CLABE). They never touch USDC, and the credit looks like any other domestic payment.
Is converting USDC to MXN this way legal and compliant?
Yes, when it runs through regulated infrastructure. Yativo is registered with FinCEN as a Money Services Business, registration number 31000270723339. A licensed local payout partner handles the MXN leg. Your own tax and reporting duties still apply, so confirm them with your advisor.
How long does a USDC to MXN payout take?
SPEI and bank transfer payouts to Mexico settle in under 30 minutes. POBO (Local), SWIFT and SWIFT (POBO) settle T+1.
What exchange rate do I get when I convert USDC to MXN?
You see the rate, the fees and the exact MXN amount before you confirm. Quotes from the exchange-rate endpoint hold for 5 minutes, so you can lock a rate before you approve a large payout.
Do I need an exchange account to convert USDC to MXN?
No. You deposit USDC into your Yativo balance and pay out directly on a local rail. There is no separate exchange order, withdrawal request or bank transfer to manage.
Can I pay a debit card number instead of a CLABE?
Collect the CLABE. It is the standard account identifier for SPEI and avoids card-specific limits.
Start Converting USDC to MXN with Yativo
SPEI moved 7,308.1 million transfers in 2025, so Mexican suppliers expect pesos fast. Yativo turns your USDC into MXN on any CLABE through a licensed local payout partner in under 30 minutes. Book a demo to set up your first MXN payout, or contact sales if you already know your monthly volume.
Sources
- Banco de México: Ingresos y Egresos por Remesas, diciembre de 2025
- Banco de México: Informe Anual sobre las Infraestructuras de los Mercados Financieros 2025
- Banco de México: SPEI, información
- Banco de México: MI SPEI, transferencias
- Banco de México: Information for SPEI users
- World Bank: Remittance Prices Worldwide
- Yativo: Yativo API Documentation
- Yativo: Safer API access, three new virtual accounts and new payment links