Odoo 19 online payments: choose, test and reconcile

For an Odoo business in Belgium or France, taking payment online is more than placing a logo on a checkout page. In Odoo 19 Enterprise, the chosen provider, available methods, availability limits and accounting reconciliation need to tell the same story.

Separate online collection from the bank

A payment provider lets a customer pay a sales order, invoice or subscription through the portal or eCommerce website. It is not a bank account: provider settlements and fees still need to be reconciled. Decide who owns configuration, API credentials, payment callbacks and finance review.

Choose for the journey you actually sell

Before enabling a provider, list the countries, currencies, payment methods and use cases involved. Check the capabilities that are actually available: tokenisation for later payments, manual capture, refunds, express checkout or direct debit. A capability shown by Odoo depends on the provider and contract; do not infer it from another connector.

Configure availability instead of hiding risk

Countries, currencies and maximum amount in Odoo filter which payment methods are shown. Use them to avoid displaying an unsuitable method, but test the complete path: they do not guarantee the provider will ultimately accept payment. In developer mode, the availability report helps explain why a method is absent.

Test the full cycle before go-live

Odoo recommends test mode on a duplicate or test database. Use the provider’s sandbox credentials, then verify an authorisation, capture where the flow requires it, void, refund and the return to Odoo. Do not use real payments to discover a setup or invoice-numbering issue.

Design reconciliation during scoping

For online payments, an In payment status does not always mean the cash is reconciled on the bank statement. The payment journal and, where appropriate, outstanding account govern the accounting follow-up. Finance should validate entries, fees and settlement differences with its accountant before launch.

A useful acceptance test for Odoo Belgium and France

Underside’s fictional scenario: a Belgian distributor sells in euros to Belgian and French customers through its Odoo website. Marketing wants quick checkout; finance needs net settlements and fees without ambiguous manual reconciliation. The team keeps the provider in test mode until standard and exception paths are traceable.

• Test an accepted, declined, cancelled and refunded payment using sandbox data.
• Check countries, currencies, taxes, fees and displayed amount before confirmation.
• Test the customer portal, invoice link and eCommerce checkout on desktop and mobile.
• Test manual capture only where the provider and business process justify it.
• Reconcile Odoo entries, provider settlements and the bank statement, then document exception handling.

Official sources and scope

References: Odoo 19 documentation on online payments and payments in Accounting. Availability, fees and obligations depend on the provider, contract and organisation; have them confirmed before go-live. The governance recommendations are Underside analysis.