← Back

Payment channel profile

What SPEI is and how merchants accept it

SPEI is Mexico's interbank transfer system operated by Banco de Mexico. For merchants, it can be relevant for ecommerce or B2B account-to-account payments, but pricing, confirmation handling, refund flow, settlement calendar, and provider eligibility must be verified for the exact PSP route. This page covers fit, access routes, and what to ask a provider.

MexicoPrimary marketMain service market
Payment method / bank transferRole / typeInstant payment, Bank transfer
Medium, verify entity and documentsEntity requirementOnboarding conditions
Real-time / T+0SettlementPayout timing

What it is

SPEI, the Sistema de Pagos Electronicos Interbancarios, is an interbank settlement system owned and operated by Banco de Mexico, the country's central bank. It has been running since 2004 and handles both high-value institutional payments and everyday retail transfers. A payer initiates the transfer from a banking app or online banking using the recipient's CLABE, an 18-digit standardised bank account number, or by scanning a QR code. Banks must follow Banco de Mexico timing rules, but merchant-side confirmation, pricing and payout handling depend on the provider route. Confirm those details before treating SPEI as a checkout-ready method.

  • Banco de Mexico owns and operates SPEI as an interbank settlement system.
  • Payments route to an 18-digit CLABE account number or through a QR code.
  • Banks must follow Banco de Mexico timing rules; verify merchant-side confirmation with your provider.
  • Unsettled orders are cancelled at the end of the operating day rather than carried over.

Where it is used

SPEI is domestic to Mexico and settles in Mexican peso. Its users are banked Mexican consumers and businesses of every size, from someone repaying a friend to a corporate treasury moving payroll. Many banks and non-bank financial institutions participate, which means the rail can reach a large banked audience. It does not reach people without a bank account, so a merchant targeting cash-based shoppers needs something else alongside it. Merchant pricing depends on the bank, PSP, account and contract model rather than the rail alone. Everyday retail transfers are an important use case, but the system has always carried large institutional payments as well.

  • SPEI is domestic to Mexico and denominated in MXN.
  • Participating banks, brokerages and non-bank financial institutions connect to the system.
  • Users range from retail banking customers to corporate treasuries.
  • It does not reach shoppers who have no bank account at all.

Which businesses it suits

SPEI suits merchants who want near-instant confirmation at a lower cost than cards, and who sell to customers comfortable with their banking app. Mexican ecommerce, digital content, SaaS, B2B invoicing and supplier payments all fit well, as does any business where a large average order makes card interchange painful. It suits less well when customers expect instalments, because a bank transfer carries no credit. It is also a weaker fit for buyers who rarely use online banking, and for businesses that depend on weekend or holiday settlement behaving identically to a weekday. It suits recurring and invoiced collection too, provided your systems can match an incoming transfer to the right invoice.

  • It suits ecommerce, digital services, SaaS, B2B invoicing and supplier payments.
  • It suits merchants where large average order values make card fees expensive.
  • It does not suit instalment-driven purchases, since a transfer carries no credit.
  • It does not suit customers who rarely use online banking or mobile banking.

How merchants usually connect

Businesses with a Mexican entity and a bank account can receive SPEI transfers directly, simply by publishing a CLABE and reconciling incoming payments. Cross-border merchants cannot realistically do that, so they connect through a payment service provider that holds the local banking relationships and presents SPEI as a checkout method. Providers active in Mexico include dLocal and EBANX, both of which also offer cards and OXXO cash collection. Through a PSP the customer still pays from their own banking app, but your integration sees a standard payment notification rather than a bank statement line. Ask whether the provider issues a reference per order, because that is what makes automated reconciliation possible.

  • Merchants with a Mexican entity can receive SPEI directly using a CLABE account number.
  • Cross-border sellers normally use a PSP such as dLocal or EBANX instead.
  • A PSP turns bank transfers into standard payment notifications your systems can consume.
  • Direct receipt is cheaper per payment but requires local reconciliation capability.

Cross-border merchant notes

Without a Mexican entity you are not a scheme participant; the provider is. That means settlement normally arrives in peso to an account the provider controls, and you repatriate in your own currency, so FX spread and timing are part of your real cost. You also depend on the provider to confirm receipt, since you cannot watch a Mexican bank account you do not hold. Reconciliation deserves attention: transfers carry references of varying quality, so confirm your provider generates a unique reference per order and passes it back with the confirmation. Confirm what happens when a transfer arrives without the expected reference, since manual matching gets expensive at volume.

  • Your provider is the participant, so your access depends on its licence and risk appetite.
  • Settlement is usually in MXN, so currency conversion sits between sale and payout.
  • You rely on the provider for confirmation, because you cannot see the receiving account.
  • Confirm a unique per-order reference is generated and returned with each payment.

Fees, settlement and refunds

Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms, so confirm against the provider's official pricing page or a written quote before you go live. Do not assume SPEI is cheaper than card acceptance for your account until the provider quotes your exact setup. Ask how payment confirmation is surfaced, when funds are paid out, what happens on failed or mistaken transfers, how refunds are initiated, which fees apply, and which reconciliation files you receive.

  • Compare SPEI and cards using a written quote for your real method mix.
  • Ask how provider confirmation differs from bank-level transfer status.
  • Confirm payout timing, settlement currency, reserves, and failed-payout handling.
  • Refunds and mistaken transfers need explicit operating rules.
  • Reconciliation files should identify transfers against your order records.

Alternatives and complements

OXXO is the natural complement for cash-preferred shoppers, since SPEI only reaches banked customers and cannot help someone who pays in notes at a till. Card acceptance is still needed for instalments and for buyers who expect card protections. CoDi, the QR-based collection layer Banxico built on SPEI infrastructure, is worth asking your provider about if you sell in person or want QR checkout. A balanced Mexican setup offers SPEI for instant bank payment, cards for credit, and OXXO for the cash economy. Ask which of these your provider can enable in one integration, because a fragmented Mexican setup creates reconciliation work.

  • Add OXXO to reach cash-preferred or unbanked Mexican shoppers.
  • Keep card acceptance for instalments and for buyers who want card protections.
  • Ask about CoDi if you need a QR collection layer on SPEI infrastructure.
  • Offer SPEI first for banked buyers and the others as supporting methods.

Questions to ask before you integrate

Ask whether SPEI is offered for your category and entity structure, and whether the provider issues a unique reference per order. Confirm settlement currency, payout timing, cut-offs and the FX margin in writing. Ask how payment confirmation reaches your systems and what happens when a customer sends the right amount with a mistyped reference. Ask how refunds are handled and who pays. Finally, ask about operating hours and holiday behaviour, since banks publish a daily window and unsettled orders are cancelled at day end. Ask what evidence the provider can give you for a payment, because you may need proof for accounting or a dispute.

  • Confirm that SPEI is offered for your category and entity structure with a unique reference per order.
  • Get the settlement currency, payout timing, cut-offs and FX margin in writing.
  • Confirm how confirmation is delivered and how mistyped references are resolved.
  • Confirm how refunds are handled, who pays, and how long they take.
  • Confirm how operating hours, weekends and holidays affect confirmation and settlement.

Merchant usage and connection route

SPEI in the payment stack

SPEI is important for Mexico merchants evaluating bank-transfer collection, especially for higher-value orders, B2B invoices, wallet top-ups, or customers who prefer bank-app transfers. Assess automated references, confirmation timing, reconciliation, refunds, fraud controls, and how SPEI fits beside cards, OXXO, wallets, and BNPL.

Connection route

Merchants may access SPEI through Mexican banks, account providers, PSPs, gateways, payment institutions, platforms, or virtual-account style services. Confirm whether the route supports automated payment identification and merchant reporting, or whether operations must manually match incoming transfers.

Verification questions

  • Is SPEI needed for ecommerce checkout, invoices, B2B collection, wallet funding, marketplace flows, or account-to-account payment?
  • Which bank, PSP, gateway, payment institution, account provider, or platform provides the merchant route?
  • How are payment references, confirmation timing, callbacks, reconciliation, refunds, and unmatched transfers handled?
  • What Mexican entity, account, documentation, category, transaction-size, and fraud-review requirements apply?
  • Who resolves wrong amounts, late transfers, duplicate payments, mistaken payments, and customer-service escalations?

Merchant caveats

  • SPEI transfer availability does not guarantee automated merchant reconciliation.
  • Manual transfer matching can create support and fulfillment risk.
  • Refunds and mistaken-payment handling should be defined before high-value order rollout.
  • Provider examples are discovery examples only, not recommendations or support evidence.

Provider examples to verify

STPConektaOpenpayBanwireTonder

Related markets

Mexico

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Sources

Capability verification checklist

Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.

  • Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
  • Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
  • Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.

Official links to open

Commercial terms to confirm

Pricing modelbank transfer or psp priced
Pricing basisofficial public pricing or terms
Fields still to confirm
  • Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.

Integration route to confirm

API / checkout routepsp or bank transfer route
Fields still to confirm
  • SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.

Operational features to confirm

No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.

Fields still to confirm
  • Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.

Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.

Questions merchants ask

Who operates SPEI in Mexico?

Banco de Mexico, the Mexican central bank, owns and operates SPEI as an interbank settlement system that has handled transfers since 2004. Banks, brokerages, insurers and other regulated financial institutions participate directly. Merchants reach it either through their own bank or through a licensed payment provider.

How fast is a SPEI transfer?

Banco de Mexico sets timing rules for participant banks, but merchant-side visibility still depends on the bank, PSP notification and reconciliation setup. Ask your provider how successful, failed and pending SPEI transfers are reported, then test the round trip before releasing orders automatically.

Do I need a Mexican bank account to accept SPEI?

To receive transfers directly, yes, because payments route to a CLABE account at a Mexican bank. Cross-border merchants normally avoid that by using a payment provider that holds the local banking relationship and forwards payment notifications to you. Ask the provider how settlement and repatriation work before you commit.

Can SPEI payments be refunded or charged back?

A completed transfer is final, so there is no chargeback mechanism in the card sense. A refund is a new payment you send back to the customer, which means collecting their bank details and running a separate process. Agree the refund workflow, responsibility for cost and expected turnaround with your provider before go-live.

Is SPEI cheaper than card payments in Mexico?

Usually, yes, because there is no interchange and no card network in the flow. Public pricing is only a first filter, though. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms, so compare a written quote against your real Mexican method mix.

What is a CLABE number?

A CLABE is the 18-digit standardised bank account number used in Mexico to route transfers. It identifies the bank, branch and account. If you receive SPEI directly you publish your CLABE for customers to pay into. If you use a provider, it handles CLABE routing on your behalf and simply notifies you of payment.

Public sources