How does a Mercado Pago payment work?
In the hosted flow, Checkout Pro, the shopper is redirected to Mercado Pago’s payment page. They can log in to pay with a method saved in their account or continue as a guest, and then return to the merchant’s site. Merchants that keep the shopper on their own page use Checkout API, where Mercado Pago recommends its Orders API for new integrations.
In Argentina the same integration offers account money, Cuotas sin Tarjeta, credit cards including Visa, Mastercard, American Express, Naranja and Cabal, debit and prepaid cards, and Rapipago and Pago Fácil cash slips. Checkout Pro uses 3DS 2.0 to authenticate card payments.
Cuotas sin Tarjeta, formerly Mercado Crédito, is a credit line run by Mercado Pago. The shopper signs in, chooses Cuotas sin Tarjeta and pays in up to 12 fixed monthly instalments in the app, without a card. The seller is credited the full amount.
Cash slips work asynchronously. The shopper pays the slip at a Rapipago or Pago Fácil counter. By default it expires after 3 business days, and crediting can take up to 2 business hours after payment. Until then the order waits for payment.
Why does Mercado Pago matter for merchants?
Reach is the first reason. MercadoLibre reported 88 million fintech monthly active users across Latin America in the second quarter of 2026, up 30% on a year earlier. Mercado Pago’s Checkout Pro is available in Argentina, Brazil, Chile, Colombia, Mexico, Peru and Uruguay, and MercadoLibre named Brazil and Mexico as its fastest growing fintech markets in that quarter. This page describes the Argentine checkout in most detail, because the methods on offer differ by country. Many Argentine shoppers keep a balance in a Mercado Pago payment account, and the central bank reported that 76.9% of push transfers in August 2026 had a payment account (CVU) at one end.
Instalments are the second reason. Cuotas sin Tarjeta spreads a purchase over up to 12 months without a credit card, and card instalments sit in the same checkout.
Mercado Pago operates as a payment service provider today. It announced in May 2025 that it would apply for a banking licence, and a central bank director said in September 2026 that it would receive one before the end of the year.
Mercado Pago also covers payouts. Its Payouts API sends one or many transfers, up to 1,000 in one request, from the merchant’s Mercado Pago account to Mercado Pago accounts or external bank accounts, provided the origin account holds enough funds.
What can go wrong?
Cash slips are the slowest part of the flow. A shopper who pays after the due date is refunded to their Mercado Pago account rather than completing the order, and Mercado Pago treats an unpaid slip as expired 30 days after its due date. Merchants should cancel unpaid slips past their due date to keep reconciliation clean.
Refunds depend on balance. A payment can be refunded in full or in part within 180 days of approval, but the merchant must have enough available balance in the Mercado Pago account. Card refunds go back to the card statement.
Card payments made through Mercado Pago can still be disputed. Mercado Pago sends a chargeback notification, and the merchant reviews the case through the chargebacks API and submits documentation before the deadline.
How would Omno handle Mercado Pago?
Omno would treat Mercado Pago as one route among several, shown in the hosted checkout next to cards and transfers or through Direct Links on the merchant’s own checkout. Each payment would move from pending to final, and the webhook would be the source of truth for confirming an order, which matters most for cash slips that stay pending for days. Routing rules set by the merchant could send card payments either through Mercado Pago or through another provider by card number range, and in the hosted checkout, if a provider is unavailable or rejects the request, the payment would move to the next provider in the rule until one accepts. Eligibility rules could limit which customer groups and order amounts see Mercado Pago, and the routing-decision log would record which provider handled each payment.