Skip to Content

Integrating Odoo POS with Transbank, Getnet, Banchile Pagos and Mercado Pago

Compare architecture, devices, certification, statuses, refunds and support.
Blog SYSTCOM · Odoo y gestión empresarial
Blog SYSTCOM · Gestión empresarial y Odoo
October 30, 2026 by
Equipo SYSTCOM

Two providers may accept the same cards and still require very different integration projects. One may communicate with the register through a cable and SDK; another may receive orders through an API and return status changes through webhooks. That difference affects networking, testing, contingency procedures and support.

When integrating payments with Odoo POS in Chile, asking whether it “works” is not enough. The useful question is: which flow works, with which device, contract, version, operations and recovery conditions?

What official sources show

ProviderRelevant public modelWhat must be confirmed
TransbankUSB terminals through SDK, plus an API and webhook option. All operations except tipping.Operational and certified; validate terminal, contract and environment per project.
GetnetUSB terminals through SDK. All operations except tipping.Operational and currently undergoing certification.
Mercado PagoPoint Smart 2 through API and webhooks. All operations except tipping.Operational and certified; validate credentials, account and terminal per project.
Banchile PagosUSB terminals through SDK. All operations except tipping.Operational and certified; scope confirmed internally by SYSTCOM.

This table summarizes public information; it does not certify compatibility for a specific installation. Odoo 19 also has no documented standard connectors for Transbank, Getnet or Banchile Pagos, so they require specific development. Odoo’s documented standard Mercado Pago terminal integration does not list Chile among its supported countries.

SYSTCOM has developed integrations for Getnet, Banchile Pagos, Transbank and Mercado Pago connected to Odoo POS. They have been tested on Odoo 17, 18, 19 and 20. Selection and activation depend on the technical scope validated for each merchant.

Ten criteria for comparing an integration

  1. Odoo version and edition. The connector should state its exact version, dependencies and update path. “Odoo compatible” without a version is not an acceptable criterion.
  2. Hosting model. Odoo Online restricts custom modules, while Odoo.sh and on-premise deployments allow different options. A local connection may need a bridge service or network access that hosting must support.
  3. Device and firmware. Record the model, terminal number, firmware and operating mode. Replacing hardware may change the protocol or require renewed certification.
  4. Supported operations. A sale alone is not a complete integration. Review declines, cancellations, last-sale recovery, voids, full or partial refunds, closing, totals and tipping where relevant.
  5. Correlation and idempotency. Every attempt needs a unique reference. After a timeout, the system must distinguish a retry from a second charge.
  6. Status and recovery. Define how pending states, late responses and charges approved without local confirmation are handled. The register needs a way to query or rebuild the state.
  7. Reconciliation. Align the Odoo order, provider reference, amount, payment method, fee, deposit and any refund. Operational closing and bank reconciliation are not the same process.
  8. Security. Credentials must not be exposed in the browser or repository. Apply least privilege, rotation, logs without sensitive data and notification verification.
  9. Certification and rollout. Confirm test environments, required scenarios, ownership of certification, pilot stages and conditions for production credentials.
  10. Support and change. Define who supports the terminal, network, connector and Odoo; how issues are diagnosed; and what happens when an API, firmware or ERP version changes.

A minimum maintainable architecture

Checkout layerStarts payment, blocks incompatible actions and displays understandable statuses.
Integration layerTranslates Odoo flows into SDK/API calls and applies references, timeouts and controlled retries.
Control layerRecords events, supports diagnostics and feeds closing and reconciliation without exposing secrets.

The integration should keep the order state separate from each payment-attempt state. An order can have more than one attempt, but only one should ultimately be applied as the valid charge. Preserving that history makes it easier to investigate declines, duplicates and refunds.

Questions for an evaluation meeting

  • Which Odoo versions and terminal models have been tested?
  • Which operations are implemented, and which are outside scope?
  • How is an approved payment recovered if Odoo missed the response?
  • Which identifier links the order, payment, receipt and deposit?
  • How does contingency work without internet or a local service?
  • Which tests does the provider require before production?
  • Who maintains the integration after Odoo or terminal updates?

If you first need to clarify the concept, return to what an integrated POS actually solves. To turn these criteria into a project, continue with the implementation roadmap.

Turn a provider list into a technical decision

We review compatibility, operations, contingency, certification and support before committing to an architecture.

Review compatibility
Integrated Odoo POS: automating in-person payments in Chile
Connect the sale, terminal and reconciliation without hiding exceptions.