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.

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.