At a busy checkout, entering an amount in Odoo and typing it again into the payment terminal may look harmless. The problem starts when the figures do not match, communication is interrupted, or the terminal approves the charge but the register never receives the response.
An integrated POS connects the Odoo sale to the payment service: the amount leaves the register, the customer completes the transaction on the terminal, and the result returns linked to the correct order. This can reduce duplicate entry and improve traceability, but only when exceptions, reconciliation and support are designed as part of the same process.
What changes compared with a standalone terminal?
1. The amount starts in Odoo
The register sends the amount and a sales reference. The cashier should not need to enter the figure again on a separate device.
2. The terminal processes it
The provider controls card reading, authentication and authorization according to its service and device.
3. The status returns
Odoo receives a result and links it to the order: approved, rejected, canceled or pending, depending on the connector.
4. The operation is reviewed
References, closures and reports make it possible to compare Odoo sales with the provider’s records.
The benefit does not come from making the payment button faster. It comes from preserving a verifiable relationship between the sale, transaction, receipt and financial record.
Integrated does not mean infallible
Odoo 19 states that connected payment terminals depend on internet access. Each acquirer also defines its supported devices, contracts, SDKs, APIs, certifications and operations. An implementation must therefore answer a difficult question: what should the register do when it cannot determine whether the customer was charged?
Automatically validating every sale after a timeout can create duplicate charges or payments without a consistent order. Canceling without querying the provider can ignore an approved transaction. The design should use the sales reference, retrieve the latest status when the provider allows it, and reserve manual actions for authorized users.
Standard Odoo and Chile-specific development
Odoo 19 includes a standard framework for terminal payment methods and documents several providers. However, a name in global documentation does not prove that the same flow is available in Chile. Odoo’s standard Mercado Pago terminal page, for example, lists Point Smart availability for Argentina, Brazil and Mexico—not Chile.
In Chile, Transbank and Getnet describe integrated POS offerings that require changes to the checkout system and provider certification. Mercado Pago Chile offers a Point integration based on orders, external references and notifications. Banchile Pagos publicly confirms Smart POS and digital payment products, but the specific in-person integration scope must be verified for each project.
SYSTCOM has developed integrations for Getnet, Banchile Pagos, Transbank and Mercado Pago as payment gateways connected to Odoo POS. They have been tested on Odoo 17, 18, 19 and 20. Banchile Pagos, Getnet and Transbank use compatible USB terminals and their SDKs; Transbank also supports an API and webhook flow. Mercado Pago uses Point Smart 2 through API and webhooks. All operations except tipping are implemented. Transbank, Banchile Pagos and Mercado Pago are operational and certified; Getnet is operational and currently undergoing certification.
Payment and tax documentation are related, but they are not the same decision
In Chile, the process must also reflect the receipt issuance model reported to the SII. Under the applicable model, a payment voucher can qualify as an electronic sales receipt. If the taxpayer has declared that an electronic sales receipt is always issued, it must still be produced for electronic payments. Cash and bank transfers follow different rules. The SII states that, from September 30, 2026, the model can be changed once per month and becomes effective the following month.
The integration should not decide this through a technical assumption. Before configuring the POS, confirm the taxpayer’s issuance model, the printed or virtual delivery of the receipt, and the handling of returns or credit notes with the accounting team. This article is educational and does not replace tax advice.
Signs that an integrated POS is worth evaluating
- Cashiers enter the same amount on two devices.
- Differences are discovered only during closing.
- There is no shared reference between the order and the transaction.
- Retries depend on the operator’s memory.
- Refunds or cancellations are not linked to the original sale.
- Each branch handles contingencies differently.
Before selecting a provider
- Map the sale, payment, receipt, closing and reconciliation flows.
- Separate essential capabilities from desirable ones.
- Confirm devices, connectivity, contract and certification.
- Test declines, timeouts, retries and status recovery.
- Define who may force, cancel, void or refund a transaction.
The next guide in this series compares the criteria for integrating Odoo POS with payment providers in Chile. If you are already planning a project, continue with the implementation roadmap.