Payment Route
Mexico to United States Payment Methods
A Mexico-to-US payment can enter the United States through several different routes: direct card checkout, American Express, PayPal, Apple Pay or Google Wallet, a regulated transfer, closed platform balance, or an explicitly offered Mexico-facing account-payment flow. SPEI is Mexico’s domestic interbank transfer system; CoDi and DiMo are Mexico-side payment or addressing layers. None becomes a universal US checkout button simply because it works at home. This guide identifies the live route before comparing approval, MXN/USD cost, renewals, payment state, refunds, and recovery.
Route: payer in Mexico → US merchant or verified recipient; often a Mexico-issued card, PayPal account, wallet-backed card, Mexican bank account, or regulated transfer route with USD billing or conversion. Treat ordinary merchant checkout separately from a verified invoice or bank-recipient transfer.
First Read
Start With the US Checkout, Not Mexico’s Domestic Payment Menu
The US merchant or recipient decides which doors exist. If card checkout is shown, inspect the exact Mexico-issued card profile and issuer. If PayPal is shown, inspect the Mexican PayPal account and funding layer. Apple Pay and Google Wallet add wallet handoffs above eligible cards. SPEI, CoDi, or DiMo matter only when a merchant or regulated provider explicitly exposes a compatible Mexico-facing account or recipient route. Compare MXN/USD conversion, recurring billing, authentication, payment state, and refunds only after the route is identified.
Route Read
Which Mexico-to-US Route Fits the Job?
Read this as a route map, not a ranking. The US merchant or recipient chooses the entry point; the Mexican account, card, wallet, bank, or provider then decides whether that exact route is eligible.
| Route | Route Read | Best Job | What Still Decides |
|---|---|---|---|
| Direct Visa / Mastercard card checkout | First Check | US merchant checkout, subscriptions, software, stores, travel, apps, and digital services | The US merchant must accept the exact Mexico-issued card profile. The issuer still controls available funds or credit, card status, online and international use, merchant country or category, billing profile, authentication, recurring authorization, limits, MXN/USD posting, risk, and refunds. |
| American Express card checkout | Separate Card Route | US merchants that explicitly accept the exact Mexican Amex product | Check merchant Amex acceptance, exact card product, account controls, available credit, merchant country and category, currency, recurring support, authentication, limits, posting, and refunds. Do not infer Amex acceptance from Visa or Mastercard support. |
| PayPal checkout | Merchant Checkout Layer | US merchants that explicitly offer PayPal, including supported one-time or automatic-payment flows | The merchant must expose PayPal. Then check the Mexican PayPal account, account status, transaction type, selected or backup funding, underlying card decision, billing agreement, currency conversion, PayPal transaction state, and refund destination. |
| Apple Pay wallet handoff | Service-specific | US web or app checkout where the merchant explicitly supports Apple Pay | Mexico is an Apple Pay-supported market, but the exact Wallet card and issuer must still be eligible. Check merchant integration, compatible device or browser, selected card, issuer, country, currency, recurring support, device confirmation, final authorization, and refund to the original card route. |
| Google Wallet / Google Pay handoff | Service-specific | US checkout where the merchant explicitly supports a compatible Google payment flow | Google Wallet supports selected institutions and cards in Mexico. Check merchant integration, Google Account, app or browser flow, eligible saved method, underlying issuer, country, currency, recurring support, authorization, and refund. Wallet availability is not proof of this US merchant route. |
| Regulated transfer to a verified US recipient | Alternative | Invoices, business payments, family or account recipients, and other non-checkout jobs | Verify the legal provider and recipient, identity and account requirements, send and receive currencies, rate and fees at the time of transfer, payment method, delivery route, timing, transaction state, recipient reconciliation, cancellation or recall options, and refund or return process. |
| SPEI-funded or Mexico-facing account collection | Explicit Only | A US merchant or provider that explicitly supplies compatible Mexican account instructions | SPEI is a domestic Mexican interbank rail, not generic US checkout. Verify the merchant or regulated provider, Mexican recipient or collection account, financial institution, reference, MXN amount, any later conversion, payment state, reconciliation, and recovery before sending. |
| CoDi payment request | Explicit Only | A merchant or collection provider that explicitly presents a compatible CoDi request | CoDi requires a supported payment request and participating financial institutions. Verify who generated the QR, NFC, or mobile request, displayed recipient, amount, account, customer authorization, transaction state, and reconciliation. Do not scan a code simply because it is labeled as a payment option. |
| DiMo mobile-number transfer | Recipient Route | An explicit Mexican recipient or collection route where the intended account is linked to DiMo | DiMo uses a mobile number linked to an eligible account. Verify the intended recipient, participating institution, linked mobile-number route, amount, transfer state, limits, and any institution-level charges. A US merchant needs an explicit Mexico-facing recipient setup before DiMo is relevant. |
| Prepaid / Virtual Card program | Limited | Selected one-time purchases or merchant-specific credential flows | Check the exact program, activation or verification, underlying account, balance or spending limit, merchant or category restrictions, recurring and trial support, country, currency, billing profile, authentication, deposits or holds, credential lifetime, and refund behavior. |
| US platform gift card or store balance | Limited | Gaming, app stores, streaming, and platform-specific purchases | The issuer, authorized seller, code status, US account or store region, currency, product, subscription, backup-payment rule, remaining balance, redemption, and refund destination must match. Closed balance does not become general USD cash or repair an unresolved authorization. |
Route by Route
Six Route Families, Six Different Control Points
The destination is the same, but the route owner changes. Direct cards depend on merchant and issuer approval; PayPal adds an account and funding layer; Apple Pay and Google Wallet add a wallet handoff above an eligible card; regulated transfers use recipient and provider rules; SPEI, CoDi, and DiMo remain Mexico-side account layers unless explicitly connected to the foreign payment; store balance stays closed-loop.
1. Direct Card: Merchant + Issuer
This is the cleanest first route to inspect when the US checkout shows the card network. The merchant must accept the exact Mexico-issued card profile; the issuer then decides available funds or credit, card status, country, currency, online and international use, merchant category, authentication, recurring authorization, limits, risk, and final approval. A network logo alone is not approval.
2. PayPal: Merchant Lane + Account + Funding
PayPal is a separate US merchant lane. The merchant must expose it, then the Mexican PayPal account, account status, transaction type, currency, billing agreement, and displayed funding must fit. The selected card can still be declined underneath PayPal. Record the PayPal transaction state, conversion choice, funding-side entry, and refund destination separately.
3. Apple Pay / Google Wallet: Handoff Layers
Wallets change how an eligible card reaches the US merchant without replacing the funding decision. Check merchant integration, device or browser or app flow, Wallet or Google Account profile, selected funding method, issuer, card country, currency, recurring support, authorization, conversion, and refund. The same declined card can fail again inside a wallet.
4. Regulated Transfer: Provider + Recipient
A verified transfer is a different payment job from merchant checkout. Identify the regulated provider, legal recipient, account details, sender and recipient verification, send and receive currencies, fees and rate at the moment of transfer, funding method, timing, payment state, reconciliation, return or recall options, and refund process. Do not copy bank details from an unverified message.
5. SPEI / CoDi / DiMo: Mexico-Side Account Layers
SPEI moves domestic interbank transfers; CoDi helps create and authorize supported payment requests; DiMo helps address an eligible recipient account with a mobile number. A US merchant can use one of these only through an explicit compatible Mexico-facing collection or recipient route. Verify the actual provider, recipient, account or request, amount, currency, state, and recovery.
6. Store Balance: Closed-Loop Route
A US gift card or platform balance creates value inside one platform. Check the issuer, seller, code state, US account or store region, currency, eligible product, subscription, remaining balance, backup-payment requirement, redemption, and refund destination. It does not become general USD cash and does not cancel a pending card, PayPal, wallet, or transfer attempt.
Domestic Rail ≠ Foreign Checkout
SPEI, CoDi, and DiMo Need an Explicit US-Facing Connection
Banco de México describes SPEI as a real-time transfer system between accounts at different financial institutions in Mexican pesos within Mexico. CoDi is a payment-and-collection platform for electronic transfers, and DiMo links a mobile number to an eligible account for supported transfers. Those capabilities are useful home-ground infrastructure, but they do not by themselves prove that a US merchant accepts the route.
SPEI Stops at the Domestic Rail
For a US payment, ask who provides the Mexico-facing collection account or recipient instruction. If a regulated provider gives valid Mexican bank details and a reference, SPEI can fund that Mexico-side leg. The provider then owns the conversion, onward delivery, reconciliation, and return path. Without that explicit bridge, the US merchant does not receive SPEI simply because the payer can send SPEI at home.
CoDi Needs a Real Payment Request
A CoDi QR or mobile request should be tied to the actual merchant or recipient and displayed through a compatible participating flow. Verify the recipient, amount, institution, authorization screen, and final state before approving. A QR image sent in a chat or copied from another transaction is not a substitute for verified merchant instructions.
DiMo Needs the Intended Linked Recipient
DiMo simplifies recipient addressing with a mobile number, but the number must be linked to the intended eligible account. Verify the recipient and participating institution before sending. For a US-facing payment, a provider must explicitly establish the Mexico-side recipient route; a random phone number is not an international payment rail.
Follow the Failed Gate
Which Part of the Mexico-to-US Route Broke?
Use the screen and payment state to locate the owner. Card authorization, authentication, billing or country profile, the cross-border route, MXN/USD conversion, PayPal or wallet eligibility, and recipient-transfer state are different failure layers. Check the US merchant order and any pending authorization or transfer before opening another route.
Card Authorization Gate
Open the card-decline guide when the US 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, USD charge, recurring setup, authentication result, and whether the issuer received the authorization request.
Authentication Gate
Open the 3D Secure guide when the card route stops before or during authentication. Record whether no challenge appeared, an OTP or issuer app failed, the session expired, or authentication succeeded and the later authorization was declined. Those stages have different owners.
Money Trail Gate
Open the money-trail guide when the problem is the amount rather than approval. Reconcile the US merchant’s original USD or other currency, any merchant or PayPal conversion, authorization, posted MXN amount, separate issuer or provider charges, transaction date, and refund credit. Do not compare a checkout quote with a statement amount from a different stage.
Cross-Border Gate
Open the international-payment guide when the same Mexico-issued card or account works domestically but fails for the US merchant. Compare countries, card or account profile, billing region, merchant category, currency, international controls, authentication, issuer or provider risk, and route-specific restrictions.
Payment State Gate
Open the payment-state guide when the merchant, PayPal, wallet, bank, or transfer record does not agree. Verify whether the first attempt is declined, pending, completed, reversed, returned, refunded, or awaiting recipient reconciliation before sending again.
PayPal Layer
Open the PayPal issue guide when the US merchant never offers PayPal, the Mexican account cannot continue, a funding card cannot be linked or selected, currency changes the route, the selected funding is declined, or an automatic-payment agreement fails.
Before You Press Pay
Read the Route Before Creating an Authorization or Transfer
Confirm the live US route first, then check the exact Mexican card or account, authentication stage, billing and country profile, MXN/USD money trail, renewal capability, recipient-transfer eligibility, and any existing payment state before creating another authorization.
| Check | Why It Matters |
|---|---|
| Live route: The US checkout or recipient exposes this door | Confirm the exact direct card, Amex, PayPal, Apple Pay, Google Wallet, prepaid or virtual, store-balance, regulated transfer, or explicit Mexico-facing account route. A method that works in Mexico but is absent here is not available for this payment. |
| Authentication: The current issuer or institution challenge can complete | For cards, record whether 3D Secure is frictionless or challenged. For an account route, use only the financial institution or regulated provider’s genuine authorization flow. Passing authentication confirms that stage only; final authorization or transfer processing is separate. |
| Profile: Genuine country and billing data fit | Compare the issuer billing record, card country, PayPal or wallet account country, store region, shipping country, postal code, and merchant-supported countries. Correct only genuinely outdated information; a profile match is not final authorization. |
| Money trail: MXN/USD is clear end to end | Record the US merchant’s original currency, any MXN or DCC offer, PayPal or provider conversion, authorization, posted MXN amount, separate issuer or provider charges, transaction date, and refund conversion. Compare the same stage, not one headline rate. |
| Second charge: The route survives renewal | For subscriptions, record the billing agreement, next charge date, card or funding status, expiry or replacement, available funds or credit, country, currency, recurring support, and later authorization. A one-time transfer or CoDi request is not the same mechanism as card or PayPal recurring billing. |
| Recipient: Account instructions are verified | For SPEI-funded, regulated transfer, CoDi, or DiMo routes, verify the legal recipient or provider, institution, account or linked identifier, request, reference, amount, currency, payment state, reconciliation, and recovery. Do not send to copied instructions without independent verification. |
| Recovery: Refund, dispute, and transfer recovery are understood | Refunds normally return through the original route and can convert at a different rate. Card disputes, PayPal cases, bank-transfer recovery, provider procedures, and closed store balance follow different rules. Preserve the original route, transaction state, merchant order, timing, and provider. |
Payment Jobs
Three US Payment Jobs That Change the Route
Mexico-to-US payments often appear when users pay for global online services, commerce, or verified recipients.
AI Tools and Software
A US software or AI service may use card, PayPal automatic payment, wallet, or another recurring route. Confirm the initial charge, billing agreement, later renewals, currency, authentication, payment state, and refund route.
Streaming and Subscriptions
A subscription may require an eligible Mexico-issued card or account, recurring agreement, billing and country compatibility, available funds or credit, authentication, expiry, and renewal support. A one-time bank transfer does not automatically satisfy later recurring charges.
Online Shopping or Invoice
For shopping, use only methods displayed by the US store and compare card or account profile, shipping and billing countries, currency, conversion, authorization, fees, returns, and refund route. For an invoice, use only independently verified recipient instructions from the merchant or regulated provider.
Straight Answers
Questions About the Mexico → US Route
The useful question is not which Mexican method is best in general. It is which route the live US merchant or recipient offers, which Mexican account or card sits underneath it, and how that route handles approval, MXN/USD conversion, renewals, payment state, refunds, and recovery.
How should I choose a payment method from Mexico to a US online service?
Start with the live US checkout or recipient instructions, then identify the route rather than the brand. A direct Mexico-issued card, PayPal, Apple Pay or Google Wallet handoff, regulated transfer, explicit SPEI-funded collection, CoDi request, DiMo recipient route, prepaid or virtual card, and store balance have different account owners, authorization, MXN/USD conversion, recurring behavior, payment states, refund paths, and recovery rules.
Can I use SPEI to pay a US website?
Not as a generic US checkout method. Banco de México describes SPEI as an interbank transfer system for transfers between participating financial institutions in Mexican pesos within Mexico. A US merchant or provider can use a Mexico-facing SPEI-funded route only when it explicitly supplies compatible Mexican recipient or collection instructions. Verify the provider, account, reference, currency, payment state, reconciliation, and recovery before sending.
Can I use CoDi or DiMo for a US merchant?
Only through an explicit compatible Mexico-facing flow. CoDi requires a supported payment request and customer authorization; DiMo requires an intended recipient account linked to a mobile number through a participating institution. Neither one becomes a universal international checkout option simply because it is available in Mexico.
Can I use PayPal from Mexico to pay US services?
PayPal can work only when the US merchant offers the PayPal lane and the Mexican account remains eligible. Check account status, transaction type, billing agreement, currency, selected or backup funding, underlying card decision, PayPal transaction state, conversion, and refund destination. One-time checkout and automatic payments are separate billing routes.
Can Apple Pay or Google Wallet fix a declined Mexican card?
Not necessarily. A wallet changes the handoff but often leaves the same underlying issuer and card decision in place. Check merchant wallet integration, eligible Mexico-issued card, issuer, country, currency, device or browser, authentication, recurring support, and final authorization. The same card can fail again inside a wallet if the underlying gate is unchanged.
Do currency conversion fees apply?
They can, but the amount depends on the live route. Rebuild the money trail before comparing rates. Record the US merchant’s original currency, any MXN or DCC offer, PayPal or provider conversion, card authorization, posted MXN amount, separate issuer or provider charges, transaction date, taxes, transfer delivery where relevant, and refund credit. Verify current fee and rate information at the time of payment.
What We Checked
What We Checked: Mexico → United States
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 a domestic real-time interbank transfer system in Mexican pesos, describes CoDi as a mobile payment-and-collection platform for electronic transfers, and provides transfer-verification context. DiMo explains mobile-number-to-account linking through participating institutions. PayPal Mexico governs a separate merchant-payment account and funding layer. Apple and Google list Mexico among supported wallet markets subject to participating issuers, cards, devices, and merchant flows. None of these sources guarantees that a specific US merchant exposes a particular Mexican card, PayPal lane, wallet handoff, SPEI-funded collection, CoDi request, DiMo recipient, currency, recurring route, or refund path.
- Banco de México: Información sobre SPEI — describes SPEI as a Banco de México-operated real-time system for electronic transfers between accounts at different participating financial institutions in Mexican pesos within Mexico.
- Banco de México: CoDi — explains the CoDi payment-and-collection platform, electronic transfers, mobile authorization, and QR/NFC technologies.
- DiMo: Official service site — explains mobile-number linking to eligible accounts and supported electronic transfers through participating institutions.
- Banco de México: MI SPEI — provides transfer-verification context and identifies CoDi and DiMo as ways to initiate or address certain electronic transfers.
- PayPal Mexico: User Agreement — current terms governing Mexico-resident PayPal accounts, payments, linked funding methods, account status, and restrictions.
- PayPal Mexico: Consumer Fees — provides current fee categories and currency-conversion information; verify the live page before relying on a rate.
- Apple Support: Countries and regions that support Apple Pay — lists Mexico as an Apple Pay-supported market, subject to participating banks, issuers, and eligible cards.
- Google Wallet Help: Supported payment methods in Mexico — lists selected Mexican institutions and card types supported by Google Wallet.
Our read: The live US checkout or verified recipient instructions define the route. A Mexico-issued card, PayPal lane, Apple Pay or Google Wallet handoff, regulated transfer, SPEI-funded collection, CoDi request, DiMo mobile-number route, and store balance are not interchangeable. Authentication is not authorization, a Mexico domestic account rail is not automatically a US checkout rail, and a new method does not erase an unresolved authorization or transfer. Compare the route state, MXN/USD money trail, and refund or recovery path before switching.
Freshness Check
How Current Is This Mexico → US Route?
We last checked this Mexico → United States route on August 16, 2026, and scheduled the next review for November 16, 2026. US merchant checkout options, Mexican card and wallet products, PayPal funding, SPEI participation, CoDi and DiMo availability, regulated transfer routes, MXN/USD conversion, authentication, recurring billing, payment states, fees, refunds, disputes, and recovery procedures can change before then. Use the live US checkout or verified recipient instructions plus the current Mexican provider account for the final decision.
Last checked: August 16, 2026
Mexico-side map: Open the Mexico Payment Guide to review SPEI, CoDi, DiMo, cards, PayPal, wallets, MXN money trail, and the domestic-versus-foreign route boundary.