SPEI: Mexico real-time payments by CLABE

SPEI, Sistema de Pagos Electrónicos Interbancarios, is Mexico real-time payment system, operated by the Banco de México since 2004, and it lets a payment move between accounts at different banks in seconds, 24 hours a day, 7 days a week. A payment is addressed by CLABE, Clave Bancaria Estandarizada, the 18-digit standardised account number that every Mexican bank account has, and it settles in central bank money, so the beneficiary can use the money within seconds of the payment being sent. SPEI is the backbone of electronic payments in Mexico, used by banks, fintechs and businesses for everything from payroll to supplier payments. Source: Banco de México, SPEI. Why SPEI exists is that Mexico needed a real-time interbank system that every bank and every licensed fintech could use, so that money could move between institutions without waiting for a batch. Before SPEI, interbank payments were slow and expensive, and cash dominated, which is costly and insecure. SPEI answers by settling each payment individually in seconds, with a low fee, and by making participation open to banks and to regulated non-bank institutions, so a customer of a fintech can pay a customer of a large bank instantly, and the competition is on service, not on access to the rail. The system was built by the central bank, which is why it is trusted and why it is used for high-value as well as low-value payments. The parties are the payer and the payee, their banks or payment institutions, which must be SPEI participants, and the Banco de México, which operates SPEI and settles the payments. The addressing is by CLABE, which encodes the bank, the branch and the account, and includes a check digit, so a CLABE with a wrong digit is rejected before the payment is sent, which is a control that prevents many mistaken payments. The payer institution must validate the CLABE, show the beneficiary name where available, and send the payment, and the beneficiary institution must credit the account within seconds of settlement. How it works is shown by a worked example. A company in Mexico City pays a supplier in Guadalajara MXN 850,000 on a Friday at 16:00, using the supplier CLABE. The company bank validates the CLABE, sends the payment through SPEI, the Banco de México settles it in central bank money, and the supplier account is credited MXN 850,000 at 16:00:05, five seconds later. The supplier sees the payment on Friday, not Monday, and can pay its own staff on time. For a smaller payment, an individual sends MXN 2,500 to a family member on a Sunday at 20:00 by SPEI, and the family member receives it in seconds, which would have been impossible under the old batch system, where the payment would have waited until Monday. On success the payment is final in seconds, the receiver can use the money immediately, and the cost is low, so the system is used for payments of every size. On failure the payment can be rejected, for example because the CLABE is invalid, the account is closed, or the amount exceeds a limit, and the rejection is immediate, so the sender knows at once and can correct the details. The failure that matters most is a payment sent to a valid CLABE that belongs to the wrong person, because the CLABE check digit only proves the number is well formed, not that it belongs to the intended payee, so the recovery is a request to the receiver to return the money, and the bank follows its mistaken payment process. The data in a SPEI payment is the payer and payee identification, the CLABE, the amount in Mexican pesos, the payment concept, which is a short description the payer writes, and the reference number. The payment concept is the field that matters for reconciliation, because a business that receives hundreds of SPEI payments a day matches them by concept and reference, and a concept that says only payment, with no invoice number, creates a manual exception. A BA must specify the CLABE validation, the concept field, the reference, the limits, and the return process for a payment that cannot be credited, because each of those is a customer promise. Edge cases show the limits. SPEI operates continuously, but each participant sets its own limits and cut-offs for certain services, so a very large payment may be subject to additional checks, and the customer must be told. A payment sent to a CLABE that was closed after the payer copied it will be rejected, and the payer must obtain the new CLABE, which is a customer service issue, not a system failure. A fintech that participates in SPEI must hold settlement funds at the central bank, and if its balance is insufficient, its payments will be queued or rejected, so liquidity management is part of the service, not an afterthought. The effect on the bank or fintech is a service customers expect, and a reduction in cash and cheque volume. The effect on the customer is instant payments at any hour, addressed by a single standardised number, with a check digit that catches typing errors. The effect on operations is a 24/7 service with fraud screening in milliseconds, because an instant payment cannot wait for a morning review, and a liquidity position that must be monitored continuously, because the central bank settles each payment as it arrives. What a BA, PO or SME must understand is that SPEI is a central bank real-time system addressed by CLABE, and the CLABE is the addressing, the check digit is the first control, and the instant settlement is the value. The requirement must name the CLABE validation, the payment concept, the reference, the limits, the liquidity arrangement and the mistaken payment process. The test is to send one payment by CLABE, check that an invalid CLABE is rejected before sending, that the credit arrived in seconds, and that the concept matched the invoice, because if any of those fails, the service is not working. Further reading: Banco de México, SPEI; Banco de México, payment system reports. Last reviewed 7 November 2026.