If you sell in Chile and your operation runs on Odoo, sooner or later you'll face the same question: how do I get every payment from my online store or point of sale to record itself, without keying in invoices by hand or reconciling spreadsheets at month-end? The answer is to integrate Odoo with local payment providers. In this guide, we explain how to connect Odoo with Transbank (Webpay), Mercado Pago, and Getnet, which method fits your business, and how to avoid the mistakes that cost the most time and money.
Why integrate Odoo with a payment gateway in Chile
In Chile, card payments rule ecommerce, and Transbank (with Webpay Plus) is still the most widely used gateway, alongside players that are gaining ground, such as Getnet (from Banco Santander) and Mercado Pago. If your online store or physical location takes payments through these channels but your ERP doesn't find out in real time, you end up with three classic problems:
- Double data entry: someone copies amounts from the acquirer's portal into Odoo.
- Manual reconciliation that eats up days of accounting time and hides discrepancies.
- Stockouts, because a paid sale doesn't deduct inventory instantly.
Connecting your payment gateway to Odoo in Chile solves this: a confirmed payment automatically triggers the sale, the electronic invoice to the SII (Chile's tax authority), and the inventory deduction. It's the difference between an ERP that only records transactions and one that actually runs your operation. If you're still evaluating the platform, start by understanding what Odoo is and how it fits your sales flow.
The three key integrations for the Chilean market
Odoo + Transbank (Webpay): the local standard
The Webpay integration in Odoo works mainly in two ways, and choosing the right one is half the job:
- Webpay Plus (web/redirect): in your Odoo eCommerce store, the customer is redirected to the Transbank gateway, pays, and Webpay sends the confirmation back to Odoo. The order is validated automatically. Ideal for online sales.
- Integrated POS (physical terminal): Odoo sends the amount to the Transbank POS terminal, the terminal handles the payment, and the response goes back to the point of sale to validate the sale without keying in amounts. Ideal for physical stores and omnichannel operations.
To activate it, you need an active Transbank account and Webpay Plus credentials (an integration environment for testing, then production). It's worth checking your Odoo version, since the connector changes from release to release.
Odoo + Mercado Pago: native Latin American coverage
Mercado Pago is available as a payment provider in Odoo's official documentation for Chile (as well as Argentina, Colombia, Peru, and Mexico). This means you can set it up with your credentials (Access Token / Public Key) directly in the payments module, with no custom development in the standard case. It covers credit cards, debit cards, and other payment methods supported by Mercado Pago, which makes it a good option if you already sell within that ecosystem.
Odoo + Getnet: centralized online and in-person payments
Getnet lets you integrate eCommerce and point of sale directly into Odoo (Community, Enterprise, and Odoo.sh), accepting debit and credit cards, and even Google Pay and Apple Pay, both online and in store. Its strength is centralizing physical and digital payments in a single system, with automatic reconciliation and real-time receipts.
Quick comparison: which one should you choose?
| Criteria | Transbank (Webpay) | Mercado Pago | Getnet |
|---|---|---|---|
| Market penetration in Chile | Very high (the standard) | High (ecommerce) | Growing (banking) |
| Main channel | Web + POS | Ecommerce | Web + POS |
| Availability in Odoo | Module/connector | Provider in official docs | eCommerce + POS app |
| Apple/Google Pay | Depends on configuration | Partial | Yes |
| Best for | Local omnichannel operations | Sellers in the MP ecosystem | Unified in-person + online payments |
Practical recommendation: most Chilean retailers start with Webpay (because their customers already know it) and add Mercado Pago or Getnet depending on their channel mix. It's not either/or: Odoo can handle several gateways in parallel.
What the integration process looks like, step by step
Whatever the acquirer, a well-executed integration follows a similar flow:
- Define the scope: ecommerce only, POS only, or both? This determines the connector.
- Enable credentials in the acquirer's portal (test environment first).
- Install and configure the payment module on the right Odoo version.
- Map accounts and journals so each payment lands where it should.
- Test real transactions in the sandbox (approved, declined, and reversed payments).
- Connect SII electronic invoicing to issue the tax document upon confirmation.
- Go live and monitor the first reconciliations.
We follow this same order in every Odoo implementation we deliver at KPB. If you want to estimate timelines and budget before you start, see our guides on how to implement Odoo in Chile and how much it costs to implement Odoo.
Common mistakes (and how to avoid them)
- Not testing the decline and reversal flow: many teams only validate successful payments. Always test the negative cases.
- Skipping the integration environment: going straight to production with real credentials is a recipe for mismatched books.
- Forgetting accounting reconciliation: a technical integration without journal mapping generates entries that still have to be fixed by hand.
- Ignoring SII invoicing: a confirmed payment should trigger the DTE (electronic tax document); otherwise, you're back to manual data entry.
- Using an outdated module: each Odoo version may require a different connector.
Beyond payments: data that works for you
Integrating payments is the first step. The real value shows up when that data feeds your decisions. With sales and payment data consolidated in Odoo, you can turn on Business Intelligence dashboards with Keep BI to see, for example, which gateway has the best approval rate or which channel converts best. And with AI automation and Keep Checking, you can catch pending payments or reconciliation discrepancies before they become a problem.
If you're just moving off spreadsheets, our guide to migrating from Excel to an ERP will help; and if you're still comparing platforms, check out Odoo vs Defontana or Odoo vs Nubox.
Conclusion: a single source of truth for your payments
Integrating Odoo with payment providers isn't a technical whim: it's what turns your ERP into the true center of your operation. Whether it's Transbank, Mercado Pago, or Getnet, the goal is the same: every peso collected gets recorded, invoiced, and reconciled without manual intervention. The key is choosing the right method, testing thoroughly, and connecting electronic invoicing.
Want your payments running on their own in Odoo? At KPB Solutions, an Odoo Gold Partner (top 5% worldwide), we implement it end to end. Book a meeting and let's talk about your case.
