One successful sale in a demo does not prove that an integration is ready for every register. Real operations include declines, timeouts, shift changes, refunds, network outages, replaced devices and closings that must reconcile.
Payment automation in Odoo POS should be managed as a process, integration and adoption project. This roadmap organizes the work into six stages and defines the evidence worth requiring before production.
Stage 1. Discovery: observe before automating
Document the current flow from the moment a cashier selects Payment until finance reconciles the deposit. Include the people involved, systems used, reference retained and procedure for resolving differences.
- Points of sale, registers, companies, branches and shifts.
- Payment methods, tips, installments and split payments where applicable.
- Electronic sales receipt, invoice, payment voucher and the SII issuance model.
- Operational closing, settlements, fees and bank reconciliation.
- Current issues: duplicate entry, missing references, duplicates or rework.
Stage 2. Scope and architecture
Define the provider, product, terminal, interface and operations. Clearly separate standard Odoo 19 capabilities from specific development. Transbank, Getnet and Banchile Pagos do not appear as standard terminals in Odoo’s documentation, and its standard Mercado Pago page does not list Chile. Local connectors must therefore be assessed as specific integrations.
SYSTCOM has developed integrations for Getnet, Banchile Pagos, Transbank and Mercado Pago as payment gateways connected to Odoo POS. They are tested on Odoo 17, 18, 19 and 20 and cover every operation except tipping. Transbank, Banchile Pagos and Mercado Pago are operational and certified; Getnet is operational and undergoing certification. Before each rollout, the scope should confirm the terminal, contract, environment and support conditions.
Decisions that must be documented
- The system of record for the order, payment attempt and reconciliation.
- Unique references and idempotency.
- Timeouts, retries and last-transaction recovery.
- Permissions for cancellation, forced completion, voids and refunds.
- Secure credential storage and webhook verification.
- Observability, log retention and data protection.
Stage 3. Development and configuration in a controlled environment
Use test or certification credentials and a database that cannot process live sales. Configure payment methods, journals and interim accounts according to the accounting design. Never store secrets in the browser, source code or shared documents.
The connector should record useful events without exposing card data. Each attempt needs correlatable identifiers and statuses that checkout and support teams can understand. If a local bridge service is required, document its installation, updates, ports, restart and monitoring.
Stage 4. End-to-end testing
| Group | Minimum scenarios | Evidence |
|---|---|---|
| Sale | Approved, declined, canceled, boundary amount and split payment when supported. | Order, attempt, reference, receipt and expected accounting entry. |
| Communication | Timeout before/after authorization, internet loss, register or terminal restart and late response. | Recovery without a duplicate charge and a clear operational message. |
| After-sales | Void, full/partial refund, repeated attempt and missing original sale. | Link to the original transaction and enforced permissions. |
| Closing | Shift change, terminal closing, discrepancies, fees and deposits. | Reconcilable report and documented handling of differences. |
| Update | Module update, session reopening and controlled device replacement. | Persistent configuration and tested rollback. |
When the provider requires certification, its scenarios are added to this matrix; they are not replaced by internal tests.
Stage 5. Pilot and phased rollout
Start with a representative but limited set of registers. Train cashiers, supervisors, finance and support teams on normal and contingency scenarios. The guide should state when to wait, query, cancel or escalate; it should never ask staff to repeat a charge “just in case.”
Define the deployment window, backup, device inventory, owners, support channel and rollback threshold. During the pilot, compare Odoo sales, provider records and closings every day. Expand only after acceptance criteria are met.
Stage 6. Operations, reconciliation and maintenance
After launch, monitor pending transactions, discrepancies, terminal-specific errors and API or firmware changes. Maintain a version matrix and an environment where Odoo and connector updates can be tested before production.
Periodically review users with void permissions, credential validity, log quality and support procedures. If the tax issuance model changes, validate the configuration with finance and the appropriate adviser before changing the flow.
Go-live checklist
- Compatibility and certification documented.
- Functional, technical, accounting and contingency tests approved.
- SII issuance model confirmed and receipt delivery defined.
- Production credentials protected and rotatable.
- Training and exception procedures delivered.
- Monitoring, support, rollback and owners active.
If you are still framing the problem, read what an integrated POS solves. To compare alternatives, see the criteria for payment-provider integrations in Chile.