In this article (14 sections)
In short: integrating Mercado Pago into your system for selling in Latin America means the customer pays and your system finds out on its own, without anyone checking a bank statement. A charge is created, the customer pays in the Mercado Pago environment, and an automatic notice confirms to your system that the payment came through, so the order or installment can be marked as paid. What gets underestimated is not the payment button, but that notice and what your system does when it arrives late, arrives twice or doesn't arrive at all.
This article explains the ways to charge, what happens at each step, the cases you need to plan for and how much work the integration involves.
The most common ways to charge
Method | How it works | When it fits |
|---|---|---|
Payment link | You generate a link per charge and send it by WhatsApp or email | One-off charges, installments, quotes |
Checkout on your site or system | The customer chooses to pay and is taken to the Mercado Pago form | Shops, bookings, orders |
Subscriptions | Automatic recurring charges | Monthly installments, memberships |
QR code | Charge at the counter or on delivery | Physical stores |
The most used option in management systems is checkout with redirect. According to the Checkout Pro documentation, the customer decides to pay on your site, is sent to the Mercado Pago form, pays with saved or new payment methods, and returns to your site or to an address you define. Available payment methods depend on each country and are detailed in the documentation for the country where you operate. Mercado Pago operates in several countries in the region, and each one has its own documentation and payment methods.
How a charge flows, step by step
- Your system creates the charge with the amount, a description and your own reference (for example, the order number).
- The customer is taken to Mercado Pago and pays.
- They return to your system, which shows a result screen.
- Mercado Pago separately notifies your system that the payment's status changed.
- Your system confirms by querying the payment, and only then marks it as collected.
Steps 3 and 4 are separate, and that's the source of many errors. The customer can return to your site before the payment is confirmed (for example, a pending payment), or can close the window before returning and pay anyway. That's why the real status should never come from the return screen: it comes from the notice.
The automatic notice: what to get right
Mercado Pago calls it a webhook: an automatic message sent to an address in your system every time something happens. According to its notifications documentation:
- It's configured in your application's panel, or when creating each charge. If it's defined on the charge, it takes priority over the panel.
- Each notice includes a signature that lets you verify it came from Mercado Pago and not a third party. If it doesn't match, it must be rejected.
- Your system has to acknowledge receipt within 22 seconds at most. Otherwise, Mercado Pago retries every 15 minutes and then with increasing gaps.
- The notice only says that something changed; the details are fetched afterward from Mercado Pago.
- The panel shows the notices sent and their status, which helps recover what failed.
For a business owner, the translation is this: your system has to be able to receive the same notice twice without charging twice, and to receive a late notice without overwriting a more recent status.
The cases to plan for
Case | What should happen |
|---|---|
Payment approved | It's marked as collected, and the next step fires (delivery, receipt, confirmation) |
Payment pending | The order waits; nothing is delivered yet |
Payment rejected | The customer is notified and allowed to retry |
Duplicate notice | The duplicate is ignored |
Notice that never arrives | A scheduled process checks pending payments and reconciles them |
Refund | It's recorded, the balance is adjusted and the customer is informed |
Chargeback or dispute | It's flagged for a person to review |
Customer pays too much or too little | The difference is detected and routed to a person |
The last three usually aren't in the first version of a cheap quote, and they're the ones that create manual work months later.
Reconciliation
Even when everything works, the system should compare each day what it marked as collected with what Mercado Pago reports as credited. That reconciliation is the safety net: if a notice was lost, it shows up the next day, not at month-end.
Costs that aren't development costs
Mercado Pago charges a fee per transaction, which varies by country, payment method and settlement period. Before setting your prices, check the current terms in your country, because they change and can be a significant part of your margin, especially with cards and installments. One way to avoid fees on large payments is to also offer bank transfer and reconcile it in the system. If you operate in several countries or sell to customers abroad, consider a global gateway such as Stripe as well.
How much work it involves
It depends on what surrounds the charge:
Scope | What it includes | Effort reference |
|---|---|---|
Simple charge | Link or checkout, notice, payment status | A few days |
Charge with reconciliation and refunds | The above, plus periodic checks, retries and refund handling | A few weeks |
Recurring charges | Subscriptions, retries after failure, customer notices | More, because of the number of cases |
When it's part of a larger project, the payment integration is usually included in the scope and not priced separately. Atomix's price for a project with integrated payments is USD 5,000 to 10,000, with a free working demo in 24 to 48 hours before we quote. To understand how the cost of connecting systems is built, see how much it costs to integrate two systems.
Before you start, define this
- What gets charged and when: full payment, deposit, installments, recurring.
- What happens on approval: which process starts in your operation.
- Who holds the account: your company's, not the developer's.
- Who reconciles, and how often.
- Which country or countries, and therefore which payment methods will be available.
One good practice: test the whole flow with test credentials before charging a single real payment. The documentation provides a notification address for testing, separate from production, for exactly that purpose.
If the charge sits inside a management system, the article how to choose a management system helps organize what else you need. And if you want the system to connect with other services, see Atomix's custom software development service.
Frequently asked questions
Can I charge without the customer leaving my system?
There are ways to embed the payment form in your own page, but the redirect option is the simplest and carries the least risk. For most management systems, it's enough.
What if the customer pays and the system doesn't find out?
That's what the periodic check and the daily reconciliation are for: the system reviews pending payments and updates them. It's part of a well-built integration, not an extra.
Can I charge in installments or with a subscription?
Yes. Recurring charges have their own rules and more cases to plan for, such as a failed card or a change in amount, so they're quoted separately.
Do I need a special account to integrate?
You need a verified Mercado Pago account and an application created in its developer panel, which gives you the credentials. It's best if that account belongs to your company.
Is Mercado Pago the only option?
No. It depends on your country and your customers. In some cases it makes sense to offer several payment methods and have the system reconcile all of them in one place.
If you want to review how to integrate payments into your operation, you can book a call.