Build-to-order Mercado Pago payment acquirer for Odoo 17/18/19: cards, Pix, boleto, installments, webhooks & refunds across LatAm. One-time license from $249.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Mercado Pago payment acquirer for Odoo 17/18/19: cards, Pix, boleto, installments, webhooks & refunds across LatAm.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
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.
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
Pix instant payments with QR code and copy-paste code rendered at checkout, reconciled automatically on webhook confirmation
Boleto bancário support (Brazil) with due-date handling and pending-state tracking until the bank confirms
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.
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.
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.
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.
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.
Buy the license on ecosire.com and download the Mercado Pago Gateway for Odoo (LatAm) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Mercado Pago Gateway for Odoo (LatAm), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Mercado Pago cards, Pix, boleto & account money in Odoo checkout | ||||
| Installment (cuotas) configuration with live per-plan totals at checkout | ||||
| Built on standard `payment.provider`/`payment.transaction` — upgrade-safe, no parallel bookkeeping | ||||
| Webhook/IPN reconciliation for async Pix & boleto + `ir.cron` re-poll fallback | ||||
| Full & partial refunds pushed from Odoo and written back to the invoice | ||||
| Full source ownership, documentation, training & support window | ||||
| Both Checkout Pro (hosted) and transparent/Bricks on-site checkout | ||||
| Tailored to your country account, currency, issuers & margin policy |
This is a build-to-order module, not an instant apps.odoo.com download. Typical delivery is 2 to 4 weeks 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.
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.
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.
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.
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.
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.
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.
Build-to-order Mercado Pago payment acquirer for Odoo 17/18/19: cards, Pix, boleto, installments, webhooks & refunds across LatAm.