Payouts to Mexico

This guide covers Mexico-specific requirements for MXN payouts. For the general cross-border payment flow, see Sending Cross-Border Payments.

Supported configurations

Mexico payouts support the following participant types:

• C2C (consumer-to-consumer)
• B2C (business-to-consumer)
• B2B (business-to-business)

Both individual and business customers can originate payouts, and both individual and business counterparties can receive them.

All participant types and source account assets support the bank_account route. MXN-USD payouts also support the mobile_wallet route.

Trading account requirement

Mexico payouts require a USDC_SOL trading account as the source. Other trading account types (such as USDC or USDC_NPL) do not support MXN payouts.

Verify MXN payout availability

Confirm your bank supports MXN payouts for your participant type and route.

ℹ️

Bank configuration required

Contact Cybrid support to enable MXN payouts and configure Mexico as a supported corridor for your bank.

GET /api/banks/{bank_guid}
Authorization: Bearer YOUR_TOKEN

Look for an entry in supported_payout_symbols where:

• symbol: MXN-USD or MXN-USDC_SOL
• country_code: MX
• participants_type: C2C, B2C, or B2B
• route: bank_account

You can also query prices for Mexico:

GET /api/prices?payout_country_code=MX
Authorization: Bearer YOUR_TOKEN

Recipient requirements

Mexico payouts require minimal recipient information. The platform validates required fields when you create a plan.

Individual counterparty

Required fields:

• name.first, name.last

Business counterparty

Required fields:

• name.full

The counterparty must be in verified state (watchlist screening passed) before you can create the external bank account and plan.

ℹ️

No originator KYC required

Mexico payouts do not require additional KYC fields on the originator (customer). The customer must be verified, but no specific PII fields are validated at plan creation.

Purpose of transaction

For Mexico payouts, purpose_of_transaction is optional. All standard purpose values are accepted if provided. See the API reference for the complete list.

External bank account setup

Mexico payouts use SPEI (Sistema de Pagos Electrónicos Interbancarios), Mexico's electronic interbank payment system, with CLABE routing.

Requirements:

• CLABE: 18-digit bank account identifier
• Bank Code: First 3 digits of the CLABE

Send a POST request to /api/external_bank_accounts:

{
  "account_kind": "raw_routing_details",
  "name": "Mexican beneficiary account",
  "counterparty_bank_account_details": [{
    "bank_code_type": "CLABE",
    "bank_code": "032",
    "account_identifier": "032180000118359719",
    "account_identifier_type": "CLABE",
    "payment_rail": "SPEI"
  }],
  "counterparty_guid": "counterparty_guid",
  "customer_guid": "customer_guid",
  "asset": "MXN"
}

ℹ️

API versioning

Creating external bank accounts with foreign raw routing details requires Accept-Version: 2025-10-01 or later.

For the full account model and field reference, see Create Foreign Fiat External Bank Accounts.

Common validation errors

Related resources

• Sending Cross-Border Payments
• Create Foreign Fiat External Bank Accounts
• Creating a Counterparty
• Verifying a Counterparty
• Create Plan API Reference