Banxico SPEI: Developer’s Guide to Mexico’s Real-Time Payments

Banxico SPEI (Sistema de Pagos Electrónicos Interbancarios) is Mexico’s real-time gross settlement system operated by the central bank, Banco de México. It enables instant, irrevocable interbank transfers available 24/7/365. For developers building payment flows in Mexico—whether for payroll, supplier payments, or consumer transfers—understanding SPEI is essential. This guide explains how SPEI works, how to integrate with it, and how complementary APIs like API Pull’s Banxico API and AML API fit into a complete payment workflow.

What is Banxico SPEI?

SPEI stands for Sistema de Pagos Electrónicos Interbancarios, the backbone of electronic payments in Mexico. It is a real-time gross settlement (RTGS) system where each transaction is settled individually and immediately in central bank money. Unlike batch systems, SPEI transfers are final once confirmed—no reversals or chargebacks.

Key Features of SPEI

SPEI is used for a wide range of transactions: payroll disbursements, supplier payments, government social programs, and even consumer peer-to-peer transfers. The system processes millions of transactions daily, with a total value exceeding trillions of pesos annually.

How SPEI Works: From Transaction to Settlement

Participants and Roles

SPEI involves three main participants:

• Banxico: Operates the central platform and manages settlement accounts.
• Banks and financial entities: Each holds a settlement account at Banxico and sends/receives payment orders.
• End users: Individuals and businesses that initiate transfers through their bank.

When a user initiates a transfer, their bank sends a payment order to Banxico via the SPEI network. Banxico validates the message, debits the sending bank’s settlement account, and credits the receiving bank’s account. The receiving bank then credits the beneficiary’s account.

Message Formats and Standards

Payment orders follow the SPEI standard. Historically, the format was defined by the CNAB (Comité Nacional de Autoridades Bancarias). Modern implementations use ISO 20022, a global XML-based standard that provides richer data fields (e.g., purpose codes, remittance information).

The Settlement Process

1. Initiation: The sender’s bank submits a payment order with beneficiary account (CLABE), amount, and concept.
2. Validation: Banxico checks the format, sufficiency of funds in the sending bank’s settlement account, and beneficiary existence.
3. Settlement: Banxico debits the sending bank’s account and credits the receiving bank’s account in real time.
4. Confirmation: Both banks receive a confirmation message. The receiving bank credits the beneficiary’s account.

Settlement is final and irrevocable. Daily reconciliation reports are provided to participants.

Integrating with Banxico SPEI: Developer Options

Direct Connection via Banxico’s API

Becoming a direct participant requires a banking license or authorization from Banxico. This involves significant infrastructure, legal agreements, and compliance with technical standards. Most developers do not pursue this route.

Using a Financial Institution’s API

The most common approach is to use a partner bank’s API. Many Mexican banks offer REST APIs that allow you to initiate SPEI transfers, query balances, and receive webhooks for transaction status. These APIs abstract the complexity of the SPEI protocol. You send a JSON payload with the beneficiary’s CLABE, amount, and concept; the bank handles the rest.

Third-Party API Providers for Complementary Data

While you integrate with a bank for transfer initiation, you often need auxiliary data. For example, if you are processing cross-border payments (e.g., converting USD to MXN before sending via SPEI), you need real-time exchange rates. API Pull’s Banxico API provides live USD/MXN rates, TIIE, and UDI values sourced from Banxico’s SIE system. This allows you to compute the exact MXN amount to send.

Additionally, for compliance, you may need to screen beneficiaries against sanctions lists. API Pull’s AML API Mexico checks against SAT 69-B, OFAC, UN, and PEP databases—critical for regulated entities.

Sandbox environments are available for testing. Most banks and API providers offer a test environment with synthetic CLABEs and balances.

Use Cases for SPEI in Business Applications

Payroll Disbursement

Companies use SPEI to pay employees in real time. Instead of waiting for the next business day, funds arrive instantly. Batch endpoints allow submitting multiple transfers in a single request. For example, a staffing agency can process hundreds of payroll payments via a single API call to their bank.

Supplier Payments (AP)

Accounts payable teams automate supplier payments by scheduling SPEI transfers. The real-time settlement ensures suppliers are paid immediately, improving relationships. For recurring payments, webhooks can notify both parties of successful settlement.

Cross-Border Payments and Currency Conversion

When a US-based company needs to pay a Mexican supplier, the workflow often involves:

1. Convert USD to MXN using a live exchange rate (e.g., via API Pull’s Banxico API).
2. Initiate a SPEI transfer in MXN to the supplier’s CLABE.

This combination eliminates the need for slow wire transfers and provides full visibility into the exchange rate used.

Afore and Pension Payments

Mexican retirement fund administrators (Afores) use SPEI to disburse pension payments to workers. The government also uses SPEI for social program transfers. These high-volume, time-sensitive payments rely on SPEI’s reliability.

Compliance and AML for SPEI Transactions

AML Screening Requirements

Financial institutions and fintechs must comply with CNBV (Comisión Nacional Bancaria y de Valores) anti-money laundering regulations. Any payment initiation—especially to new beneficiaries—requires screening against official lists: SAT 69-B (fake invoice issuers), OFAC sanctions, UN consolidated list, and domestic PEP databases.

Using API Pull’s AML API for SPEI Beneficiaries

Before initiating a SPEI transfer, integrate API Pull’s AML API to screen the beneficiary’s name, RFC, or CURP. The API returns a risk score and alerts if the individual or entity appears on any watchlist. This can be done in real time, adding only milliseconds to the payment flow.

For example, a lending platform disbursing a loan via SPEI would first verify the borrower’s identity (using CURP API), then screen the beneficiary via AML API, and finally initiate the transfer through their bank’s API.

When SPEI is the Wrong Tool

SPEI is excellent for most real-time payments, but it has limitations:

• Microtransactions: For very small amounts (e.g., under 10 MXN), transaction fees from banks may eat into the value. ACH or cash alternatives might be cheaper.
• Delayed settlement: If you need to hold funds or delay settlement (e.g., for escrow), SPEI’s real-time finality is a drawback. Consider using a digital wallet or prepaid card instead.
• International transfers: SPEI only works in Mexican pesos (MXN). For multi-currency payments, you need a different system like SWIFT or a crypto stablecoin. However, you can use SPEI after converting to MXN.

Next Steps: Get Started with Banxico Data via API Pull

To build a robust payment flow in Mexico, you need reliable data alongside your bank integration. API Pull provides:

• Banxico API: Real-time exchange rates, TIIE, and UDI for currency conversion and financial computations.
• AML API: Compliance screening for SPEI beneficiaries.
• CURP and RFC APIs: Identity verification to ensure you’re sending money to the right person.

Access sandbox environments and detailed documentation at apipull.com. Start by testing the Banxico API to fetch live rates, then combine with AML screening for a compliant, automated payment pipeline.