Short answer: Dynamics 365 cannot process OXXO, SPEI or CoDi through native card connectors, because none of them is a card. You either integrate a Mexican PSP yourself, or you connect Dynamics 365 once to a payment connector that already supports all three. The second route also covers the rest of Latin America without another project.

Mexico is the clearest example of a market where a card-only checkout quietly loses sales. So it deserves a proper look.

Why Mexico works differently

A large share of Mexican consumers either hold no credit card or prefer not to use one online. Instead, three local rails carry an enormous amount of commerce.

OXXO is a convenience store chain with thousands of locations. Shoppers check out on your site, receive a voucher with a reference number, then walk to an OXXO store and pay in cash. The store confirms the payment, and your order proceeds. For many Mexican buyers, this is simply how online shopping works.

SPEI is Mexico’s interbank electronic transfer system. It moves money between bank accounts directly, without touching a card network.

CoDi is the central bank’s QR-based payment system, built on top of SPEI. The customer scans a code and pays from their bank app.

None of these run on card rails. Therefore your existing acquirer cannot reach them.

The methods that matter in Mexico

All five sit inside the SensePass network of 112 payment methods.

What OXXO actually changes in your order flow

OXXO is not just another tender. It changes timing, so plan for it in Dynamics 365.

The customer completes checkout and receives a voucher. However, no money has moved yet. They then travel to a store, sometimes the same day and sometimes several days later. Only after they pay does confirmation reach you.

Consequently you need three decisions before launch. First, decide whether to reserve stock while the voucher is open. Second, set a voucher expiry and a rule for what happens when it lapses. Third, define an order status that clearly means “awaiting payment,” so warehouse teams do not ship early.

Our guide to cash and voucher payments walks through that flow in full, including how it appears in your ERP.

How SensePass adds Mexican methods to Dynamics 365

SensePass connects your existing Dynamics 365 environment to 112 payment methods and 50+ processors through one integration. OXXO, SPEI, CoDi, Pay Cash and MercadoPago are already included.

Configuration, not development. You connect once. Then you switch Mexican methods on. Nothing changes inside Business Central, Finance & Operations, or Commerce, and no per-country build applies.

One connector across the region. The same integration that gives you OXXO also gives you PIX and Boleto in Brazil, PSE in Colombia, and Yape in Peru. Therefore expanding into a new Latin American market becomes a settings change rather than a project.

Reconciled in your ERP. Voucher confirmations and transfer settlements post back into Dynamics 365 automatically. As a result, finance works from one ledger rather than a separate Mexican feed.

In-store as well. For physical retail, tap-and-pay lets customers tap their phone at the register and pay with a local method — with no app download and no dedicated terminal.

Practical notes for a Mexican launch

Price and settle in Mexican pesos. Use the transaction-date rate for the sale and the settlement-date rate for the payout. Then post any difference to realised gain or loss.

Expect a mixed tender profile. Cards, OXXO and SPEI will all appear. So report by tender to see what your customers actually prefer, rather than assuming.

Handle refunds by rail. You cannot reverse a cash payment made at a convenience store. Therefore refunds route through a bank transfer or another method, and your policy should say so plainly.

Watch your order-release rules. Cash vouchers are the single most common source of confusion for teams new to the market. Get the “awaiting payment” status right before you go live, not after.

Frequently asked questions

Can Dynamics 365 accept OXXO payments? Not natively. OXXO is a cash voucher rail rather than a card, so it requires a Mexican PSP integration or a payment connector such as SensePass that already supports it.

How does an OXXO payment work? The customer checks out, receives a voucher with a reference number, pays in cash at an OXXO store, and the store confirms the payment. Your order then proceeds.

What is SPEI? SPEI is Mexico’s interbank electronic transfer system. It moves funds between bank accounts directly, so it bypasses card networks entirely.

What is CoDi? CoDi is the central bank’s QR-based payment method, built on SPEI. Customers scan a code and pay from their banking app.

How long can an OXXO voucher stay open? It depends on the expiry you configure. Because of that gap, set a clear stock-reservation and expiry policy before launch.

Will Mexican methods reconcile automatically in Dynamics 365? Yes. Confirmations and settlements post back into your ERP, so you avoid importing a separate country-specific settlement feed.

Can I add other Latin American markets with the same setup? Yes. See the Latin America country guide for what each market expects.

Reach the Mexican buyers cards cannot

A card-only checkout in Mexico does not reach a smaller audience. It reaches a different one — and misses a very large group entirely. One connector adds OXXO, SPEI and CoDi to Dynamics 365, then covers the next market when you are ready.

Request a demo, or start with the Dynamics 365 payments overview.