Mexico’s Payment Map

Mexico Payment Guide

Mexico’s payment landscape is easier to understand when the rail is separated from the access layer. SPEI is Banco de México’s real-time interbank transfer system for domestic peso payments between participating financial institutions. CoDi is a mobile payment-and-collection platform that can use QR or NFC to initiate electronic transfers, while DiMo lets a customer link a mobile number to an eligible account so transfers can be addressed with that number. Cards, PayPal, Apple Pay, and Google Wallet belong to different merchant-checkout or wallet layers. This guide maps those routes before comparing foreign merchants, MXN conversion, subscriptions, payment states, refunds, and recovery.

Country Read

SPEI, CoDi, and DiMo Do Different Jobs

For a domestic account transfer, SPEI may be the underlying interbank rail. For a merchant or person-to-person flow, CoDi can create a QR-, NFC-, or notification-based payment request that the customer authorizes through a participating financial institution. DiMo is an addressing layer that lets an eligible recipient associate a mobile number with an account. For ordinary merchant checkout, a card, PayPal, Apple Pay, or Google Wallet can create a separate route. A foreign merchant must explicitly expose a compatible route; the fact that SPEI, CoDi, or DiMo works inside Mexico does not make it a universal international checkout method.

Domestic Rail: SPEI Payment Request: CoDi Mobile Identifier: DiMo

Rail Map

Which Mexican Rail, Payment Request, Wallet, or Card Is Moving the Money?

The useful distinction is the mechanism. SPEI moves domestic account-to-account transfers between participating institutions. CoDi helps a merchant or recipient request an electronic payment using a supported mobile flow. DiMo helps address an eligible recipient account with a mobile number. Cards and wallets belong to merchant checkout, while PayPal adds its own account and funding layer. Bank transfers, prepaid or virtual cards, and store balance have separate rules.

Payment MethodCommon UseWhat Actually Controls It
SPEIDomestic account transfers, invoices, person-to-person and business paymentsSPEI is the interbank transfer infrastructure. The payer institution, recipient institution, account details or supported identifier, MXN amount, transfer instruction, security checks, payment state, reference, and recovery process matter. Banco de México operates the system; the customer initiates the transfer through the participating financial institution.
CoDiMerchant or person payment requests through supported mobile-banking flowsCoDi is a Banco de México payment-and-collection platform that can use QR or NFC and an electronic transfer. The merchant or recipient request, participating institution, customer authorization, amount, account, payment state, and reconciliation matter. It is not a separate stored-value wallet and should not be treated as a universal foreign checkout rail.
DiMoElectronic transfers addressed with a mobile numberDiMo lets an eligible customer link a mobile number to an account through a participating institution. The receiving account must be linked for the mobile-number route, and the financial institution still controls account eligibility, transfer limits, authentication, transaction state, and any institution-specific cost.
Visa / MastercardOnline shopping, subscriptions, apps, software, travel, international checkoutAcceptance depends on the live merchant, exact Mexico-issued card profile, issuer settings, available funds or credit, billing country, currency, authentication, recurring support, merchant category, risk controls, and final authorization.
Debit CardsDomestic shopping, online checkout, wallet funding, selected subscriptionsIssuer support, available balance, card status, online and international use, merchant country, currency, recurring billing, authentication, limits, and payment state matter.
Credit CardsOnline shopping, subscriptions, travel, software, digital services, cross-border purchasesMerchant acceptance, issuer credit availability, card controls, country, currency, installment or recurring terms, authentication, authorization, and fees decide the route.
American ExpressSelected merchants, travel, online servicesDo not infer Amex acceptance from Visa or Mastercard support. The merchant, exact card product, issuer or account, country, currency, recurring setup, authentication, and authorization must all fit.
PayPalOnline checkout, selected subscriptions, cross-border commercial paymentsThe merchant must expose PayPal. Then the Mexico PayPal account, account status, transaction type, linked funding source, currency conversion, automatic-payment agreement where used, transaction state, and refund destination must fit current PayPal terms.
Apple PaySupported stores, apps, and web checkoutMexico is an Apple Pay-supported market, but the exact card and issuing bank must still be eligible. Merchant integration, compatible device or browser, selected Wallet card, issuer, currency, recurring support, and authorization remain separate decisions.
Google Wallet / Google PaySupported contactless, app, and web payment flowsGoogle Wallet is available in Mexico with supported institutions and cards. The merchant flow, Google Account, device or browser, eligible saved method, issuer, country, currency, transaction type, and authorization still determine whether a particular payment works.
Bank TransferInvoices, business payments, domestic account transfers, regulated international transfers“Bank transfer” is too broad to identify the route. Confirm whether the payment uses SPEI, another domestic account flow, a regulated international transfer, or a provider-specific collection route; then verify the legal recipient, account details, reference, send and receive currencies, fees, timing, payment state, cancellation, recovery, and refund process.
Prepaid / Virtual CardsSelected one-time online payments, controlled spending, temporary credentialsEligibility depends on the exact program, activation or verification, balance or underlying account, card profile, merchant acceptance, holds, recurring capability, number lifetime, country, currency, and refund behavior.
Gift Cards / Store BalanceGaming, app stores, retail, streaming, platform purchasesIssuer, authorized seller, code state, account or store region, currency, eligible product, subscription rules, remaining balance, backup-payment requirements, and refund destination must match. Store balance is not general MXN cash.

Home Ground

Domestic Account Rails and Merchant Checkout Are Different Layers

Inside Mexico, identify whether the payment is an account transfer, a payment request, a mobile-number-addressed transfer, or merchant checkout. SPEI can carry interbank transfers; CoDi can create a merchant or recipient payment request; DiMo can simplify recipient addressing; cards and wallets create merchant-checkout routes; PayPal adds an account and funding layer. Name the mechanism before comparing convenience or speed.

SPEI: The Domestic Interbank Rail

SPEI is operated by Banco de México and supports electronic transfers between accounts at different participating financial institutions in Mexican pesos. The customer still works through the institution’s app or official online channel. Verify recipient data, amount, institution, transfer state, reference, and any recovery path rather than treating “SPEI” as a merchant wallet.

CoDi: Payment Request and Authorization

CoDi helps merchants and users request and authorize electronic payments through supported mobile flows using technologies such as QR and NFC. The buyer explicitly authorizes the payment. Check the merchant or recipient request, participating institution, displayed amount, account, authorization, payment state, and reconciliation before retrying or switching routes.

DiMo: Mobile Number as an Address

DiMo lets a recipient link a mobile number to an eligible account through a financial institution. A sender can then use that number for a supported electronic transfer. The receiving customer must have the required link, and participating institutions control enrollment, authentication, limits, transaction state, and any applicable institution-level charges.

Cards: Merchant + Issuer

Cards belong to merchant checkout. The merchant and processor decide which networks and card profiles they accept; the Mexican issuer controls funds or credit, card status, online and international use, merchant country or category, currency, authentication, recurring billing, limits, risk, and final authorization.

PayPal and Wallets

PayPal, Apple Pay, and Google Wallet change the checkout handoff but do not eliminate underlying account or card requirements. Check merchant integration, account or Wallet profile, eligible card or funding method, issuer, device or browser flow, country, currency, transaction type, recurring setup, and final authorization.

Closed Balance and Programs

Prepaid, virtual, and gift-card routes depend on the exact program. Activation, verification, balance, allowed merchant types, recurring support, card-number lifetime, country, currency, store region, and refund behavior can differ even when two products show the same network or platform logo.

Leaving Mexico

What Changes When a Mexican Payment Leaves the Domestic Context?

Leaving Mexico usually means rebuilding the route around the foreign merchant or recipient. A foreign checkout may offer an international card, PayPal, wallet-backed card, invoice, or transfer route, but it does not automatically expose SPEI, CoDi, or DiMo. Then the Mexico-issued card or account, merchant country, billing profile, currency, MXN conversion, authentication, recurring setup, payment state, total cost, and refund or recovery path must still fit.

Foreign Payment JobFirst Route to InspectWhat Changes Outside Mexico
US-based subscriptionA merchant-listed recurring card, PayPal, wallet-backed card, or verified billing routeAdd the US merchant or billing entity, USD pricing, Mexico card or account country, signup authentication, later renewals, issuer or provider approval, MXN/USD conversion, total posted cost, cancellation, payment state, and refund reconversion.
US online shoppingThe card, PayPal, wallet, invoice, or other route actually shown by the US merchantCheck the Mexico-issued card or account profile, merchant and shipping rules, billing country, card-profile acceptance, wallet or PayPal integration, authorization, USD/MXN money trail, taxes, returns, and refund destination.
International software or SaaSA route supported for both signup and renewal, or a verified invoice flowSeparate signup from later renewal. Check billing entity, account or card country, stored credential or PayPal agreement, invoice details, currency, conversion, authentication, retry rules, cancellation, and refund path.
Gaming or app storeThe payment method allowed by the current account and store regionCheck account country, store region, marketplace seller or merchant, payment-method country, currency, gift-card region, subscription, delayed charges, remaining balance, backup-payment rules, and refund destination.
International invoiceThe verified bank, regulated transfer provider, card, PayPal, or other invoice route named by the merchantIdentify the actual rail. Verify legal recipient, account details, reference, send and receive currencies, conversion, fee option, timing, intermediary deductions where relevant, cancellation or recall rules, merchant reconciliation, and refund conditions.
Foreign merchant offering a Mexico-facing account flowThe exact local collection or recipient instructions shown by the merchant or regulated providerSPEI, CoDi, or another Mexico-facing account route matters only when an explicit compatible collection or recipient setup exists. Verify the named provider, legal recipient, Mexican account or payment request, reference, currency, amount, payment state, reconciliation, and recovery before sending.

Mexico → United States

Same Payer, New Merchant Country and USD Money Trail

A Mexican payer reaching a US merchant usually leaves the domestic SPEI, CoDi, and DiMo context. The US checkout may accept the same Mexico-issued card, PayPal account, Apple Pay or Google Wallet handoff, but merchant country, USD pricing, recurring billing, authentication, issuer approval, conversion, payment state, and refunds now belong to a cross-border route.

Start With the US Merchant’s Actual Checkout

Record the methods the US merchant actually shows for the Mexican account and product. Then check the exact card, PayPal or wallet route, Mexico and US countries, recurring support, billing currency, issuer or provider rules, authentication, total posted cost, and refund. A domestic SPEI, CoDi, or DiMo route that is absent from checkout is not available for that purchase.

Trace the MXN/USD Money Trail

Freeze the US merchant’s USD price first. If checkout offers MXN, record who converts and the displayed rate or markup. Otherwise trace the USD authorization into the final MXN posting, separate issuer or provider charges, transaction date, and any later USD refund converted back to MXN. Compare the same payment stage.

PayPal Is a Separate Merchant Lane

PayPal can work only when the US merchant offers the PayPal lane and the Mexican PayPal account remains eligible. Check account status, transaction type, selected funding, currency conversion, any automatic-payment agreement, underlying card decision, PayPal transaction state, and refund destination.

SPEI Needs an Explicit Mexico-Facing Recipient Route

SPEI is a domestic Mexican interbank transfer system, not a generic US checkout button. A US service can use an SPEI-funded or Mexico-facing collection route only when a merchant or regulated provider supplies compatible Mexican recipient instructions. Verify the provider, recipient, account details, reference, amount, currency, payment state, reconciliation, and recovery.

CoDi and DiMo Do Not Automatically Travel

CoDi and DiMo are useful Mexico-side layers, but neither proves a US merchant can accept them. CoDi needs a compatible payment request and participating institutions; DiMo needs the recipient’s mobile number to be linked to an eligible account. For a foreign payment, use them only when the merchant or provider explicitly exposes a supported Mexico-facing flow.

Read the First Payment State Before Switching

Confirm whether the merchant created an order and whether the funding side shows declined, pending, completed, reversed, returned, or refunded. A new card, PayPal lane, wallet, or transfer creates a new state and can duplicate the first attempt while it is unresolved.

Where the Mexico Route Breaks

Find the Failed Rail or Gate Before You Retry

A card decline belongs to card authorization; an address or country rejection belongs to the profile layer; a foreign-only failure belongs to the corridor; a merchant order that disagrees with the funding record belongs to payment state; a changed MXN amount belongs to the money trail; and a missing PayPal flow belongs to the PayPal layer. SPEI, CoDi, and DiMo failures should be traced through the participating institution, recipient data, payment request or mobile-number link, and transfer state.

Card Checkout Gate Declined

Use the card-decline guide when the merchant accepts the card route but authorization fails. Record the exact issuer message, full authorization amount, available funds or credit, pending holds, card status and controls, merchant country or category, billing profile, currency, recurring setup, authentication result, and whether the issuer received the request.

Profile or Country Gate Rejected

Use the profile guide when checkout rejects the genuine billing address, postal code, card country, payment profile, account or store region, shipping country, or supported-country combination. Correct only genuinely outdated data; a profile match does not guarantee later authentication or authorization.

Cross-Border Route Blocked

Use the international-payment guide when the same card, account, or wallet works in Mexico but fails for a foreign merchant. Compare payer and merchant countries, card or account country, currency, authentication, online and international controls, merchant category, issuer or provider risk, and route-specific restrictions.

Order and Payment States Disagree

Use the payment-state guide when the merchant order and funding record disagree. A card can leave a pending authorization, PayPal keeps its own transaction state, and SPEI or a Mexico-facing transfer has a separate transfer and recipient-reconciliation state. Match the route before resending.

MXN Money Trail Changed the Final Amount

Use the money-trail guide when the problem is the amount rather than approval. Reconcile the merchant’s original currency, any merchant or PayPal conversion, authorization, posted MXN amount, separate issuer or provider charges, transaction date, and refund credit instead of comparing only one headline rate.

PayPal Layer Missing or Stopped

Use the PayPal guide when the merchant never offers PayPal, the Mexican account cannot continue, a card cannot be linked or selected, selected funding is declined, currency changes the route, or an automatic-payment agreement fails. Start with the visible PayPal layer rather than treating every symptom as a card problem.

Open the Layer

Inspect the Card, Wallet, Account, or Transfer Layer Separately

Use these guides when one component needs deeper inspection. Then return to the Mexico map and destination corridor, because a method guide cannot decide whether the actual payment is SPEI, CoDi, DiMo, merchant card checkout, PayPal, a wallet handoff, or a separate international transfer.

Mexico-Side Checks

Six Checks That Matter More Than the Payment Logo

Before paying, identify whether you are using SPEI, CoDi, DiMo, direct card checkout, PayPal, a wallet layer, another transfer route, or closed store balance. Then check the exact merchant or recipient, account or card, participating institution, country, currency, payment state, and refund or recovery path.

For SPEI, Verify the Recipient and Transfer State

Confirm the recipient, account or supported identifier, receiving institution, amount, reference, and transfer state before focusing on speed. Use the institution’s official app or online channel and preserve the payment record needed for later verification or recovery.

For CoDi, Verify the Request Before Authorization

Check who generated the payment request, the displayed merchant or recipient, amount, participating institution, and authorization screen. A QR code is only an input to the route; the payment still depends on the account, institution, customer authorization, final state, and recipient reconciliation.

For DiMo, Verify the Mobile-Number Link

A mobile number is useful only when it is linked to the intended eligible recipient account. Check the displayed recipient or institution flow, amount, transfer state, and any institution-specific limits or charges. A phone number by itself is not proof of a foreign recipient route.

Let the Foreign Merchant Define the Available Door

Use only a route the foreign merchant actually exposes. Then check the exact card, PayPal or wallet layer, payer and merchant countries, recurring support, billing currency, MXN conversion, authentication, payment state, total posted cost, and refund. Domestic routes absent from checkout are not available for that purchase.

Trace the MXN Money Trail

Start with the merchant’s original currency, then identify who converts first: merchant, PayPal or another provider, card network and issuer, or transfer route. Compare authorization, posted MXN amount, separate charges, transaction date, and refund credit at the same stage.

Read the State Before Opening a Backup Route

Confirm whether the merchant created an order and whether the payment rail shows declined, pending, completed, reversed, returned, refunded, or awaiting recipient reconciliation. A backup card, PayPal route, wallet, or transfer can duplicate the first attempt while it is unresolved.

Straight Answers

Which Mexican Payment Layer Controls the Answer?

The useful distinction is whether the payment uses SPEI, CoDi, DiMo, direct card or wallet checkout, PayPal, another transfer route, or closed store balance. The answer changes with the mechanism.

What payment methods are important to distinguish in Mexico?

Group them by job. SPEI is the domestic interbank transfer infrastructure. CoDi is a payment-and-collection platform for supported mobile electronic transfers. DiMo lets an eligible recipient link a mobile number to an account for addressed transfers. Visa, Mastercard, Amex, PayPal, Apple Pay, and Google Wallet belong to merchant checkout or wallet layers. Bank transfer, prepaid, virtual, and store-balance routes add separate rules.

Is CoDi the same as SPEI?

No. SPEI is the interbank transfer system. CoDi is a payment-and-collection platform that can help initiate and authorize an electronic transfer through supported mobile flows. The user experience can begin with a QR code, NFC, or another request, but the account, participating institutions, authorization, payment state, and reconciliation still matter.

Is DiMo a wallet?

DiMo is better understood as a mobile-number addressing layer for electronic transfers. An eligible customer links a mobile number to an account through a participating institution. A sender can then use that number in a supported transfer flow. The institution and underlying transfer process still control the payment.

Can I use SPEI, CoDi, or DiMo to pay a foreign online service?

Not as a universal foreign checkout method. A foreign merchant or regulated provider must explicitly expose a compatible Mexico-facing collection or recipient route. Otherwise start with the methods shown by the foreign merchant, such as an eligible card, PayPal, or wallet-backed card. Verify the exact provider, recipient, country, currency, amount, payment state, and recovery path before sending through any account route.

Why did my Mexico-issued card work locally but fail abroad?

First locate the failed gate. The foreign merchant may reject the exact Mexico-issued card profile or billing country; authentication may stop before authorization; or the issuer may reject merchant country, category, amount, currency, recurring setup, international-use conditions, or risk. MXN conversion belongs to the money trail and is not the explanation for every decline.

Does PayPal remove the need to check the underlying funding method?

No. PayPal creates a separate merchant and account layer, but the selected funding source can still be a card or other eligible method with its own issuer or account decision. Check the merchant’s PayPal lane, Mexico account status, funding source, transaction type, currency conversion, automatic-payment agreement, payment state, and refund destination.

Freshness Check

How Current Is Mexico’s Payment Map?

We last checked this Mexico payment map on August 16, 2026, and scheduled the next review for November 16, 2026. SPEI participation, CoDi and DiMo availability, bank-app support, PayPal terms, card and wallet integrations, account and card status, countries, currencies, MXN conversion, recurring billing, authentication, payment states, refunds, disputes, reconciliation, fees, and recovery procedures can change before then. Use the live merchant, recipient, financial institution, and current provider terms for the final decision.

Last checked: August 16, 2026

Continue With the Mexico → United States Route

Paying a US merchant or verified recipient adds a new destination, USD money trail, cross-border acceptance layer, recurring-payment conditions, and recovery path. Open the dedicated corridor to compare Mexico-issued cards, PayPal, wallet handoffs, regulated transfers, and the limited cases where a Mexico-side bank or account route is explicitly supported.

Open Mexico → United States Payment Methods

What We Checked: Mexico’s Payment Rails

We reviewed Banco de México, the official DiMo site, PayPal Mexico, Apple, and Google materials on August 16, 2026. Banco de México identifies SPEI as its real-time domestic interbank transfer system and describes CoDi as a mobile payment-and-collection platform for electronic transfers. The official DiMo service explains mobile-number-to-account linking for eligible transfers. PayPal Mexico governs a separate account and merchant-payment layer, while Apple and Google list Mexico among supported wallet markets subject to participating issuers, cards, devices, and merchant flows. Together these sources support the rail map used here; none guarantees that a particular foreign merchant, recipient, card, account, country, currency, recurring payment, or refund will be eligible.

  • Banco de México: Información sobre SPEI — describes SPEI as a Banco de México-operated real-time payment system for electronic transfers between accounts at different participating financial institutions in Mexican pesos within Mexico.
  • Banco de México: CoDi — describes CoDi as a mobile payment-and-collection platform for electronic transfers and explains its use of QR and NFC technology.
  • DiMo: Official service site — explains how participating customers can link a mobile number to an account and use that number to receive supported electronic transfers.
  • Banco de México: MI SPEI — provides transfer-verification context and identifies CoDi and DiMo as supported ways to initiate or address certain electronic transfers.
  • PayPal Mexico: User Agreement — current terms for Mexico-resident PayPal accounts, linked funding methods, payments, account status, withdrawals, restrictions, and service use.
  • PayPal Mexico: Consumer Fees — lists current Mexico consumer fee categories and explains that currency conversion can add PayPal exchange-rate charges; verify the live page before relying on any rate.
  • Apple Support: Countries and regions that support Apple Pay — lists Mexico as an Apple Pay-supported market and notes that eligible cards come from participating banks and issuers.
  • Google Wallet Help: Supported payment methods in Mexico — lists supported Mexican institutions and card types for Google Wallet, subject to device and product eligibility.