A foreign merchant's route into Mexican payments

The three rails you are actually choosing between

SPEI is the interbank electronic payment system developed and operated by Banco de México. It moves pesos between accounts at different banks in seconds, runs around the clock, and identifies accounts using the 18-digit CLABE, a standardized code that encodes the bank, the city, the account number and a check digit. Sender banks typically require the receiving account to be registered in advance, sometimes with a waiting period before it can be used, which is a real checkout friction to design around. A SPEI transfer is a push payment: once it settles it is irrevocable, so there is no card-style chargeback on that rail. OXXO Pay is the cash voucher rail. The buyer selects it at checkout, receives a reference and a barcode, and pays in cash at a store. Cards, mostly Visa and Mastercard, remain the base of online spending, and local wallets and BNPL are growing around them.

• Treat SPEI as a push rail: fast, irrevocable, and unsuitable if you need to reverse a payment unilaterally.
• Expect per-transaction limits and advance beneficiary registration to shape your SPEI checkout flow.
• Treat OXXO as an asynchronous rail where the order is only paid once the cashier scans the voucher.
• Keep cards in the mix for higher ticket sizes and for buyers who expect instalments or rewards.

Merchant of record versus using a local partner

These two ideas get confused constantly and the difference is expensive. A payment facilitator or aggregator holds a master merchant account with an acquirer and onboards you as a sub-merchant beneath it, taking on underwriting and risk monitoring in exchange for fast onboarding and a blended price. It does not make anyone else the legal seller, so tax stays with you. A merchant of record is a legal role rather than a technical layer: that entity is the seller on the transaction, remits the relevant taxes, absorbs chargeback liability, and appears on the customer's statement. Using a local partner in Mexico usually means something narrower again, a licensed Mexican entity through which your collections are processed while you remain the seller. For digital goods and subscriptions, a merchant of record arrangement can remove a large compliance burden. For physical goods shipped into Mexico, the tax and customs position is different and needs local advice before you sign anything.

• Ask the provider to state plainly whether it is a facilitator, an acquirer, or the merchant of record.
• Ask which entity name appears on the buyer's statement and on the tax receipt.
• Check whether the arrangement changes who is liable for a card chargeback.
• Get tax advice in Mexico before assuming that a merchant of record removes your filing obligations.

How a foreign merchant actually gets access

Direct access to these rails is gated by local licensing, which is why most foreign merchants arrive through an aggregator. Mexican-facing cross-border providers such as dLocal, EBANX and similar regional specialists hold the local relationships, expose SPEI, OXXO, local cards and wallets through one integration, and settle to your offshore account. Local gateways such as Conekta, PayU and Mercado Pago sit on the other side of the line and are usually oriented toward businesses with a Mexican presence. The practical test is simple: ask whether the provider will onboard your country of incorporation and your industry, in writing, before your team writes any code. Ask also whether you need an RFC tax ID to be onboarded, because some providers require one for certain products even when they do not require a Mexican company. Onboarding for a foreign entity is a product-by-product question, not a single yes or no.

• Confirm in writing that the provider onboards your country of incorporation and your merchant category.
• Ask whether an RFC is required for the specific products you want, not for the platform in general.
• Ask which of SPEI, OXXO, cards and wallets are live on day one and which need extra approval.
• Ask for the KYC document list up front so you are not surprised mid-integration.

Timing, expiry and the cash voucher problem

OXXO vouchers expire. Depending on the processor, the default window is a few days and it can usually be configured within a range, and the per-voucher cap sits in the region of ten thousand pesos with some processors applying tighter limits. Confirmation does not arrive the moment the buyer leaves the store: providers commonly quote one to two business days for confirmation, and settlement to the merchant can run several business days beyond that. Meanwhile your order sits in a pending state. That creates three operational jobs: reserve stock or release it on a timer, remind the buyer before the voucher lapses, and reconcile vouchers that were generated but never paid. Merchants consistently underestimate the unpaid-voucher rate. The upside is real too: cash buyers cannot file a card chargeback, and for a large segment of Mexican consumers a voucher is the only way to buy online at all.

• Set the voucher expiry deliberately, and test the reminder sequence end to end before launch.
• Track the ratio of vouchers generated to vouchers actually paid as a standing metric.
• Hold inventory against pending vouchers for a defined window, then release automatically.
• Build a manual credit process, because a cash voucher normally cannot be refunded through the rail.

What it costs and what to ask

Each rail prices differently, and the visible percentage is only part of the bill. Ask separately about the transaction fee per method, a fixed per-transaction charge, the FX spread applied when pesos are converted to your settlement currency, a settlement or payout fee, a refund fee, a chargeback fee on cards, a monthly minimum or platform fee, any setup or integration fee, and whether a rolling reserve applies to your category. Ask specifically how failed, expired and abandoned vouchers are billed, because a voucher that is generated and never paid still consumed a reference and often a fee. Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live.

• Ask whether you are billed for OXXO vouchers that are generated but never paid.
• Ask whether the quoted percentage includes the FX margin or excludes it.
• Ask how refunds are executed on each rail, since a cash voucher cannot simply be reversed.
• Ask for the reserve formula, the trigger conditions and the release schedule in writing.

A build order that works

Start with cards plus SPEI. Cards cover the buyers who already shop online and give you instalments and recurring billing; SPEI gives you a low-cost, irrevocable rail for banked buyers and for higher-value orders where card interchange hurts. Add OXXO once you have evidence that a meaningful share of your traffic abandons at the payment step, since that is the segment vouchers recover. Layer wallets and BNPL last. Whatever you build, make the checkout show prices in pesos, show the method's specific instructions clearly, and treat the pending state as a first-class order status rather than an afterthought. Then measure method-level approval rate, time to confirmation, unpaid voucher rate, and the difference between your expected and actual payout, and use those four numbers to decide what to add next. Those four numbers, reviewed monthly, tell you more than any provider comparison table will.

• Launch with cards and SPEI, then add OXXO only when abandonment data justifies it.
• Display prices in pesos and give method-specific instructions at every step.
• Treat pending voucher orders as a real order state with its own expiry and messaging.
• Review method-level approval and payout variance monthly before changing the mix.

Questions merchants ask

Public sources

• Banco de Mexico - information for SPEI users
• Stripe documentation - OXXO payments
• dLocal developer documentation - bank transfer payments
• EBANX - cross-border payment solutions