Guides
Accepting payments in Mexico and LATAM
Most payment tutorials assume a US card and stop there. In Mexico and LATAM a big share of customers pay with cash at OXXO, a SPEI transfer, monthly installments, or a wallet — and the gateway you pick decides which of those you can even offer. These are the guides for getting paid here.
The first decision is not "Stripe or not" — it is which local methods you must support, because that ranks your gateways for you. If a real slice of your buyers pay cash, a checkout that only takes cards quietly loses them. So these guides stay vendor-neutral: Mercado Pago, Conekta and Stripe each win for different method mixes, payout needs and countries, and the right answer is whichever covers your customers with the least integration debt.
The engineering underneath is the same discipline as anywhere else, with two local wrinkles. First, asynchronous methods: an OXXO voucher or SPEI transfer can confirm hours later, so you confirm fulfillment off the verified webhook, never the synchronous API response. Second, reconciliation: store every charge indexed by the gateway's id and reconcile it against your order, because cash and transfer flows are exactly where silent mismatches hide. Get those two right and split payments, subscriptions, stablecoins and the emerging agent rails all become the same pattern with a different rail.
The guides
Payment Gateways in Mexico 2026: Stripe vs Mercado Pago vs Conekta
A practitioner's 2026 guide to choosing a payment gateway in Mexico: MSI, OXXO, SPEI, fees with IVA, payout timing, and which provider fits your business.
Read →
Integrating Clip Payments in Node: Transparent vs Redirected Checkout & Card Token Charges (2026)
Engineer's guide to Clip's online payments API in Node: pick between Transparent, Redirected and Embedded checkout, run the Transparent Card Token to Payments flow, handle the webhook and reconcile — and why there's no sandbox so you test with real MXN$0.01 charges.
Read →
Does Clip Have a Sandbox? Test Cards, Test Credentials, and the Production-Charge Playbook (2026)
Clip's docs contradict each other on sandbox. Here's the verified 2026 answer: which APIs get test credentials + test cards, which don't, and the safe MXN$1 production-charge + refund + idempotency ritual for the rest. Node examples.
Read →
Charge Meses Sin Intereses by API: Stripe, Mercado Pago & Conekta (2026)
Enable meses sin intereses (MSI) by API across Stripe, Mercado Pago and Conekta in Node. The exact params, per-plan minimums, the "MSI don't show up" trap, and who eats the financing fee (you).
Read →
Stripe Installments (MSI) Not Showing in Mexico? The Automatic Payment Methods Trap and the Fix
You enabled meses sin intereses in the Dashboard but the Payment Element shows nothing. The #1 cause is dynamic/Automatic Payment Methods (stripe-js #454). The fix: set payment_method_options[card][installments][enabled]=true on the PaymentIntent. Node.
Read →
Banxico Circular 9/2026: An Engineer's Deadline-Prep Guide to Homologating Your SPEI/DiMo/CoDi Transfer UX by Dec 14, 2026
Banxico's Circular 9/2026 adds UX Guías that force a standardized mobile transfer experience for SPEI, DiMo, CoDi and QR by Dec 14, 2026. Engineer's audit-and-gap-analysis guide — plus where the binding spec actually lives.
Read →
3DS2 in Mexico Is Not PSD2: An Engineer's Guide to 3-D Secure Without the EU SCA Rules
Wire 3DS2 into a Mexican checkout without copying EU PSD2/SCA rules. Why Mexico has no SCA mandate and no EEA exemptions, why you still use 3DS2 for the liability shift, and how to trigger it per-PaymentIntent on Stripe/Conekta/MP with pseudo-code. Engineering guidance, not legal advice.
Read →
Multi-Rail Payment Reconciliation in Mexico: Squaring Stripe, Mercado Pago, SPEI and OXXO Against One Ledger You Control
A Spanish-first engineer's how-to for reconciling Stripe, Mercado Pago, SPEI and OXXO against one ledger you own — so you can answer: did we get every peso?
Read →
How to Accept CoDi (and the Truth About DiMo) in Your App: A Mexican Engineer's Integration Guide
The operational how-to bank pages skip: accept CoDi via an aggregator, verify the RSA-SHA512 signed webhook, reconcile by clave de rastreo, and the honest truth about DiMo.
Read →
How to Integrate Mercado Pago Into Your App (2026): Checkout Pro, Bricks, and Webhooks That Don't Lie
Integrate Mercado Pago the right way in 2026: pick Checkout Pro, Bricks or the Checkout API, wire the preference-to-webhook flow, support OXXO/SPEI/MSI, and verify before granting.
Read →
Mercado Pago Subscriptions Done Right: Preapproval, Webhooks & Failed Payments (2026)
End-to-end Mercado Pago recurring billing: plan vs /preapproval, card-token subscriptions, the two webhook topics, and the failed-payment + cancel-sync handling the docs skip.
Read →
Mercado Pago Split Payments: Build a LATAM Marketplace with Seller Payouts (the Stripe Connect Most People Can't Use)
Stripe Connect can't pay out sellers in much of LATAM. Here's the end-to-end production guide to Mercado Pago Split Payments: OAuth, tokens, application_fee, fee traps.
Read →
Charge In-Person with Mercado Pago Point from Your Own System: The Orders API (Node, 2026)
Drive a Mercado Pago Point terminal from your backend with the Orders API: put the terminal in PDV mode, POST /v1/orders with type point, terminal_id and a mandatory idempotency key, then trust the order.processed webhook. Node, code-complete, with the Payment Intents migration note.
Read →
Mercado Pago Point webhooks not arriving? The 3 real causes and how to debug them (Node, 2026)
Mercado Pago Point webhooks not showing up? It is almost always one of three things: the terminal is not in PDV mode, your endpoint did not return 200/201 within 22 seconds, or your x-signature validation is wrong. How to debug each one in Node.
Read →
Conekta Integration in Node: Cards, OXXO & SPEI With Webhooks That Don't Lie (2026)
End-to-end Conekta guide for Node: Orders & charges for cards, OXXO and SPEI, plus async confirmation via webhooks with RSA signature verification and the raw-body gotcha.
Read →
Winning Chargebacks in Mexico: Build the Reason-to-Evidence Pipeline for Conekta and Mercado Pago
Build the engineer's pipeline to fight contracargos in Mexico: map each dispute reason to evidence, log it at checkout, and submit per rail (MP, Conekta) before the deadline.
Read →
Conekta Subscriptions: Recurring Payments Done Right — Plans, Webhooks & Dunning
Build recurring billing with Conekta end to end: create a Plan, subscribe a Customer with a card source, handle pause/resume/cancel, RSA-verify webhooks, and survive dunning.
Read →
Comply with Mexico's new LFPDPPP 2025 in your SaaS: hash-chained audit log, ARCO as a state machine, and verifiable deletion (an engineer's guide, with code)
The new LFPDPPP (DOF March 20, 2025) is enforced by the Secretaría de Anticorrupción, not INAI. Skip the law-firm summaries: build a hash-chained audit log, an ARCO state machine with the 20-business-day SLA, and verifiable deletion with mandatory bloqueo. Code-heavy (SQL/pseudo). And no, there's no data-localization mandate.
Read →
What Brazil's Pix Automático Teaches Mexican Recurring-Billing Builders (2026)
Brazil's Pix Automático (live June 2025) is LATAM's cleanest recurring-payment mandate. What MX builders can copy — and why it's "learn from Brazil," not "use Pix here."
Read →
Stripe Stablecoins Are Coming to LATAM: What Mexican SaaS Builders Should Prepare in 2026
Stripe pushed stablecoin infra at Sessions 2026 with Privy and Bridge, and LATAM is next. The engineer's guide to what a Mexican freelancer or SaaS can actually build today.
Read →
Visa Intelligent Commerce vs Mastercard Agent Pay vs Stripe ACP: Which Agent-Payment Layer Do You Actually Integrate?
Three agent-payment launches hit in June 2026. They're not competing rails — they're different layers. Here's what each is and the one primitive you actually integrate.
Read →
Stripe Shared Payment Tokens: How a Seller Accepts an Agent-Made Payment (2026)
Stripe expanded Shared Payment Tokens in 2026 so AI agents pay on a customer's behalf without seeing the card. Here's what you, the seller, actually build.
Read →
Work with me on this
FAQ
- Which payment gateway is best in Mexico — Stripe, Mercado Pago or Conekta?
- It depends on your method mix. Conekta and Mercado Pago have the strongest native OXXO (cash) and SPEI (transfer) support, which matters because a large share of Mexican buyers do not pay by card. Stripe is excellent for cards and international reach. Many teams run Stripe for cards plus a local gateway for cash/transfer — pick by which methods your customers actually use, not by brand.
- How do I handle OXXO and SPEI payments that confirm later?
- Treat them as asynchronous. You create the charge and show the customer a voucher or CLABE; the actual payment lands hours or days later. Never mark an order paid on the API response — wait for the verified webhook that confirms settlement, make that handler idempotent, and reconcile by the gateway payment id.
- Can I run a marketplace with split payments in Mexico?
- Yes — Mercado Pago supports marketplace splits and Stripe Connect works for cross-border. The hard part is not the split, it is onboarding sellers (KYC), holding funds, and getting payouts and the fiscal trail right. Decide who is the merchant of record for each transaction before you write a line of code.