Connect Odoo to payment workflows built around your business. Paying.co develops custom payment integrations for supported Odoo environments, connecting checkout, payment devices, providers, and backend processes where standard connectors do not meet your requirements. What is possible depends on your Odoo version, edition, and hosting.
This page explains fit, deliverables, and engagement. For Odoo-specific background, read Is Your Payment Gateway or Platform Connected to Odoo? It Should Be.
Businesses whose Odoo checkout or POS needs payment behavior the standard connectors do not cover.
Groups that need consistent payment behavior across stores or sites.
Partners who need payment engineering alongside their implementation work.
Providers that need a custom Odoo integration for their service.
No single connector covers every Odoo application. Support for one path does not establish support for another, and we confirm the offered scope for each before committing.
Which device or payment integration is needed, which flows are supported, and how order and payment states stay aligned.
Which checkout and provider integration fits, where sensitive data is handled, and how callbacks, confirmations, and refunds are represented.
Which records must be matched, how fees, refunds, and settlements appear, and what is custom versus existing Odoo functionality. Offered only within confirmed capabilities.
We do not assume every Odoo edition, hosting model, or version allows the same customization. Before drafting scope we verify the following against current Odoo and provider documentation, and we assess whether an existing supported integration fits before proposing new development. Provider-module work and terminal-integration work are different, and we explain which applies.
We separate combinations that have been delivered from proposed custom work, and we do not promise unrestricted provider or hardware choice. Each offered flow gets its business and payment behavior defined for the selected application and provider.
Payment on an order, in store or at checkout.
According to provider semantics, where supported.
Only where the application and provider support them.
Defined in scope, not assumed.
We identify who supplies and operates each component and explain the actual sensitive-data flow and responsibility boundaries. A custom integration does not eliminate PCI obligations. See Embedded Payments where an embedded payment experience is relevant.
Depending on the path, we address order and transaction references, provider callbacks and webhooks with verification, duplicate protection and idempotency where supported, lost responses and pending or unknown outcomes, refunds and cancellations, and reconciliation with exception handling. A browser redirect alone does not prove a payment completed, automatic retries are not always safe, and offline behavior is described only where it is actually supported. For testing, see the Payment Application Testing Checklist.
Odoo version, hosting, modules, and access.
Deliverables, dependencies, and the split between you, your Odoo partner, and Paying.co.
The module or service and its configuration.
Testing, and approvals that apply. External schedules are dependencies.
A pilot first, then wider rollout.
We confirm account and access provision, credentials, deployment permissions, existing module conflicts, test environments, and acceptance criteria up front. Timelines depend on those external dependencies, so we do not promise universal schedules. For scope and prerequisites, read Payment Gateway Integration: Scope, Timeline, and Hidden Dependencies.
Ownership of custom code versus third-party or licensed modules, documentation, handoff, support, and upgrades are confirmed in the agreement, not assumed. We assess and test the impact of Odoo version changes, installed-module changes, and provider or API changes, and we do not promise perpetual compatibility or maintenance without contractual support. See also Platform Integrations and Custom Development.
Share your Odoo version, edition, hosting model, and applications, whether you need POS, eCommerce, accounting, or a combination, your existing or custom modules and current payment setup, your intended provider and terminals, the transaction and reconciliation workflows you need, your countries, locations, and deployment size, your available API or module access, documentation, and sandbox, your Odoo implementation partner if any, and your target timing. Please do not include credentials in this form.
Tell us about your project — we route you to the right specialist.