Illustrative previewBuild-to-order Mercado Pago payment acquirer for Odoo 17/18/19:
cards, Pix, boleto, installments, webhooks & refunds across LatAm.
What is Mercado Pago Gateway for Odoo (LatAm)?
Build-to-order Mercado Pago payment acquirer for Odoo 17/18/19: cards, Pix, boleto, installments, webhooks & refunds across LatAm. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Odoo.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
Technical Specifications
- Odoo Compatibility
- Odoo 17, Odoo 18, Odoo 19
- Editions
- Enterprise & Community
- License
- Licence confirmation required
- Python Requirement
- Python 3.10+
- Database
- PostgreSQL 12+
About this Product
Mercado Pago is the default way Latin American shoppers pay — yet Odoo ships no native connector for it, so most merchants fall back to manual bank transfers, lose sales to installment-hungry buyers, or stitch together brittle scripts. This is a build-to-order Odoo payment acquirer that ECOSIRE designs, codes, installs and supports for your specific store. It is not an instant apps.odoo.com download; we build it around your business, your Mercado Pago country account (Argentina, Brazil, Mexico, Chile, Colombia, Uruguay, Peru), your currency and your checkout flow, then hand over the full source.
Under the hood we extend Odoo's standard payment framework: a new payment.provider (Mercado Pago) with server-side credential fields (public key, access token, webhook secret) stored on a dedicated models.Model, secured by ir.model.access.csv plus record rules so only accounting and admin roles can view live tokens. Transactions flow through Odoo's payment.transaction model, so orders, invoices and the customer portal reconcile exactly the way native acquirers do — no parallel bookkeeping. We wire both Checkout Pro (hosted, PCI-lightest) and transparent/Bricks checkout (on-site card capture) so you choose the balance of conversion and control that fits your risk profile.
The gateway speaks Mercado Pago's REST API for payment creation, status polling and refunds, and consumes IPN/webhook notifications to reconcile asynchronous methods like Pix and boleto. Installments (cuotas) are fully configurable — you decide which card issuers, how many installments, and whether interest is merchant- or buyer-borne — and the choices render live at checkout. Every state transition (pending, authorized, done, cancelled, refunded) maps cleanly onto Odoo's transaction states and fires the standard confirmation and dunning logic. Refunds are one click from the Odoo transaction: total or partial, pushed to Mercado Pago and written back on the linked invoice.
Because it is real Odoo code — clean models, XML/OWL views, QWeb-friendly transaction reports, and automated actions for stuck-payment retries — it upgrades with your database and stays inspectable by any Odoo developer. Works on Community and Enterprise, on Odoo 17, 18 and 19. ECOSIRE handles the module, the sandbox-to-production credential setup, a documented handover and a support window; you get a maintainable connector, not a black box.
What you get
- Complete Odoo module source (own addon with `__manifest__.py`, models, views, security CSV, static assets) targeting your chosen version — 17, 18 or 19 — delivered to your Git or as a zip you own outright
- Mercado Pago account wiring: sandbox validation first, then production credentials configured on the `payment.provider`, webhook URL registered, and a documented go-live checklist
- Installment (cuotas) and checkout-mode configuration (Checkout Pro and/or transparent) tuned to your country, issuers and margin policy
- Refund and reconciliation workflow set up against your accounting journals, tested with real sandbox refunds (full and partial)
- Written technical + admin documentation: architecture notes, credential rotation steps, webhook troubleshooting, and how to add issuers or change installment rules later
- A live training/handover session for your team (checkout ops, refunds, reading transaction states) with a recording
- A defined post-launch support and bug-fix window covering the delivered scope, plus paid options to extend
- Deployment support to your environment (Odoo.sh, ECOSIRE-managed, or self-hosted) with a sandbox-to-production migration path
Who this is for
LatAm eCommerce merchant on Mercado Pago
Runs an Odoo website/eShop in Argentina, Brazil or Mexico and needs shoppers to pay the way they already do — cards, Pix, boleto and, above all, installments — instead of dropping off at a bank-transfer wall.
Finance / accounting lead
Wants every Mercado Pago charge, installment and refund reconciled inside Odoo against the right journal automatically, with no spreadsheet re-keying and a clear audit trail for chargebacks.
Odoo partner or in-house developer
Needs a clean, upgrade-safe acquirer built on Odoo's standard `payment.provider`/`payment.transaction` framework — real code they can read, extend and maintain — not an opaque third-party binary.
Operations manager scaling across countries
Manages checkout for multiple LatAm markets and needs one consistent Odoo flow that swaps per-country Mercado Pago credentials, currencies and installment rules without re-architecting the store.
How Mercado Pago Gateway for Odoo (LatAm) Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Mercado Pago cards, Pix, boleto & account money in Odoo checkout | Included | Partial support | Partial support | Not included |
| Installment (cuotas) configuration with live per-plan totals at checkout | Included | Partial support | Partial support | Not included |
| Built on standard `payment.provider`/`payment.transaction` — upgrade-safe, no parallel bookkeeping | Included | Partial support | Partial support | Included |
| Webhook/IPN reconciliation for async Pix & boleto + `ir.cron` re-poll fallback | Included | Partial support | Partial support | Not included |
| Full & partial refunds pushed from Odoo and written back to the invoice | Included | Partial support | Partial support | Not included |
| Full source ownership, documentation, training & support window | Included | Partial support | Not included | Not included |
| Both Checkout Pro (hosted) and transparent/Bricks on-site checkout | Included | Partial support | Partial support | Not included |
| Tailored to your country account, currency, issuers & margin policy | Included | Included | Not included | Not included |
Frequently Asked Questions about Mercado Pago Gateway
How long until the Mercado Pago gateway is live, and is this an instant download?
This is a build-to-order module, not an instant apps.odoo.com download. Typical delivery is one working week depending on which checkout modes you need (Checkout Pro, transparent, or both), how many payment methods and installment rules apply, and your target Odoo version. We start in Mercado Pago sandbox, validate every method and refund path, then cut over to production credentials on your environment. You receive a go-live date after a short scoping call.
What kind of support and updates do I get after launch?
Every build includes a defined post-launch support and bug-fix window covering the delivered scope — if a webhook, refund or checkout path misbehaves, we fix it. Because it's genuine Odoo code using the standard payment framework, the module upgrades cleanly with your database; we also offer paid retainers for new methods, added installment issuers, Mercado Pago API changes, or upgrades across Odoo 17, 18 and 19.
Which Odoo versions and editions does this support?
Odoo 17, 18 and 19, on both Community and Enterprise. It extends the same `payment.provider` and `payment.transaction` models the core acquirers use, so it fits Odoo Website/eCommerce checkout and the customer portal natively. Tell us your version and edition during scoping and we build to match.
Which payment methods and installments are covered?
Credit and debit cards, Pix, boleto bancário, and Mercado Pago account money, depending on your country account (Argentina, Brazil, Mexico, Chile, Colombia, Uruguay, Peru). Installments (cuotas) are fully configurable — you choose the eligible issuers, the maximum number of installments, and whether interest is absorbed by you or the buyer. The installment picker and per-plan totals render live at checkout.
How are asynchronous payments like Pix and boleto reconciled?
The module exposes a signature-verified webhook/IPN endpoint that Mercado Pago calls when a payment's status changes. We map Mercado Pago statuses (approved, pending, in_process, rejected, refunded, charged_back) onto Odoo transaction states so orders confirm automatically once payment clears. As a safety net, a scheduled `ir.cron` job re-polls any transaction still pending in case a webhook is missed.
Is it secure, and do raw card numbers touch my server?
No raw card data is stored on your Odoo server. Card tokenization is handled by Mercado Pago; with Checkout Pro the card entry happens on Mercado Pago's hosted page, and with transparent/Bricks checkout the sensitive fields are tokenized client-side. Live API credentials are stored on a dedicated model protected by `ir.model.access.csv` and record rules so only accounting and admin roles can read them, and webhook notifications are signature-verified to reject spoofed calls.
Can I use one build across multiple LatAm countries?
Yes. The acquirer is currency- and country-aware, so you can run per-country Mercado Pago credentials, currencies (ARS, BRL, MXN, CLP, COP, UYU, PEN) and installment rules through the same Odoo checkout flow. Multi-country scope is part of the scoping conversation and may extend the build timeline slightly.
Related Modules
MCP Server for Odoo
A build-to-order Odoo module that exposes your models and business actions to AI agents over the Model Context Protocol (MCP), with per-tool scoped permissions enforced by Odoo's own access rights and record rules. ECOSIRE scopes, builds, installs, and supports it for you.
MCP Studio - AI-Assisted React App, Module & Chart Builder for Odoo
A build-to-order Odoo companion that connects AI agents to your database over Remote MCP so teams can scaffold modules, generate React app views, and assemble interactive EChart dashboards from natural-language intent. ECOSIRE designs, builds, installs and supports it after a scoping call — it is not an off-the-shelf download.
Merge Sales Orders
A build-to-order Odoo module that consolidates multiple quotations and sales orders for the same customer into one clean document, with configurable line-merge rules and full audit traceability. ECOSIRE scopes, builds, installs, and supports it on your instance.
Message Templates Everywhere
A build-to-order Odoo extension that lets your team fire pre-approved WhatsApp, Instagram, and Messenger messages straight from sales orders, invoices, and CRM records — with dynamic field merging and a full audit trail in the chatter. ECOSIRE scopes, builds, installs, and supports it for you.
Mercado Pago Gateway
Build-to-order Mercado Pago payment acquirer for Odoo 17/18/19: cards, Pix, boleto, installments, webhooks & refunds across LatAm.
- New `payment.provider` record for Mercado Pago with sandbox/production toggle, per-country account support (AR, BR, MX, CL, CO, UY, PE) and encrypted credential fields (public key, access token, webhook secret) exposed only to accounting/admin via record rules
- Checkout Pro (hosted, redirect) flow — lowest PCI burden, fastest to launch, mobile-optimized Mercado Pago wallet login and saved cards
- Transparent / Bricks checkout — on-site card capture inside your Odoo eCommerce so buyers never leave your storefront
- Card payments (credit and debit) with tokenization handled by Mercado Pago, so raw PAN never touches your Odoo server