Why Odoo customers add Payment Hub
Use Clarity Payment Hub for Odoo payment processing and run every gateway through one Odoo module instead of one provider module per gateway.
Customers get a branded portal, and receipts post to Odoo in real time with line-level cash application.
Payment Hub fills this gap with a different shape: one Odoo module (clarity_payment_hub) connecting to 19+ gateways behind a single, consistent API surface. The module installs through Odoo's standard module install / upgrade lifecycle. Integration to Odoo's data model uses the standard XML-RPC / JSON-RPC API, no monkey-patching, no source modifications, no PostgreSQL triggers. Studio customizations, App Store community modules, custom Python modules, automated actions, and computed fields all coexist. Switch between gateways without changing modules. Add Level III enrichment, surcharging, multi-MID routing, dunning automation, customer portal payment surface, and real-time cash application, on top of whichever payment providers you use today. Works across Community, Enterprise, Online, and Odoo.sh.
Line-level cash application, posted in real time
AR automationDunning and reminders on open invoices for each Odoo company, alongside Odoo's own follow-up reports.
Cash application and payment reconciliationReal-time, line-level cash application through account.move and account.payment, the records Odoo's accounting already uses.
One payment, reconciled in Odoo
- FOLLOW-UPPay-link on an open invoice
- PAYMENTCaptured on your gateway
- ACCOUNT.MOVE.LINEReconciled line by line
- COMPANYPosted per Odoo company
Batch payments, deposits and milestones
B2B payments for manufacturers and distributorsBatch payment across several invoices, plus deposits and milestone billing on manufacturing orders.
Credit card processing fees and surchargingA surcharging engine with per-state, per-card-brand and per-merchant rules. Debit cards are never surcharged.
A manufacturing order, end to end
- MANUFACTURING ORDERDeposit captured
- MILESTONEBilled as work completes
- BATCH PAYMENTSeveral invoices, one payment
- SURCHARGEDisclosed where rules allow
One portal in place of a payment surface per provider
Customer payment portalOne portal with multi-invoice payment, stored credentials, ACH and multi-currency, in place of a payment surface that changes with each provider.
ACH paymentsACH beside cards on the same portal, posting to Odoo the same way.
Lower card costs on commercial cards
Level 2 and Level 3 interchangeLine-item data from sale.order.line and account.move.line goes with each eligible commercial card payment.
Visa CEDPVisa's Commercial Enhanced Data Program now decides whether that data counts. From its April 18, 2026 schedule, failed data is priced the same as none and the criteria stay private, so the data is built from Odoo's own order and invoice lines, per company.
Card cost controls
- COMMERCIAL CARDLevel III from sale.order.line
- VISA CEDPLine-item data validated
- DEBIT CARDNever surcharged
Payment Hub vs native Odoo payment modules, honest side-by-side
Odoo supports 17 payment providers natively, from Stripe and Adyen to Authorize.Net and Nuvei, each installed as its own module, and their capabilities differ. Here's how Payment Hub compares, measured against the best-of-breed native modules (Stripe and Adyen, generally the most feature-complete).
| Capability | Native Odoo Payment Modules (best case) | Payment Hub on Odoo |
|---|---|---|
| Gateway / processor choice | ~ Per-module install required for each gateway, switching = uninstall / reinstall | ✓ 19+ gateways behind one module, switch via configuration |
| Capability consistency across gateways | ✗ Uneven, Stripe / Adyen full-featured, many others read-only | ✓ Uniform capability matrix across all 19+ gateways |
| Level III interchange enrichment | ✗ Not a standard feature of Odoo's payment providers | ✓ Auto-enriched from sale.order.line / account.move.line, 20+ fields per transaction |
| Customer self-service portal | ~ Generic Odoo portal, payment surface gateway-specific | ✓ Unified portal, multi-invoice batch pay, stored credentials, ACH, multi-currency, L3 |
| Multi-invoice consolidation | ✗ Per-invoice flow | ✓ Batch pay across multiple invoices, single auth, single capture, line-level cash app |
| Surcharging / convenience fees | ✗ Not native | ✓ Compliant surcharging engine (per-state, per-card-brand, per-merchant rules) |
| Multi-company routing (different MIDs) | ~ Per-company config possible, switching MIDs per scenario complex | ✓ Per-company / per-shop / per-scenario routing, different MIDs, gateways, currencies |
| Real-time line-level cash application | ~ Auto-application varies by module | ✓ Real-time line-level cash application via account.move and account.payment |
| Manufacturing deposits / milestone billing | ✗ Not native to MRP module | ✓ Triggered by mrp.production and stock.picking events, auto-bills milestones |
| Dunning automation | ~ Basic via Accounting, not gateway-aware | ✓ Full dunning ladder with auto-retry, gateway-aware, configurable per company |
| Subscriptions module recurring | ~ Works with native Stripe / Adyen, gateway-locked | ✓ Works with all 19+ gateways. Full recurring engine independent of gateway choice |
See it running against your own Odoo instance
A 30-minute walkthrough: one module in place of a provider module per gateway, multi-company routing, manufacturing deposits and real-time line-level cash application.
One module across every provider
Odoo runs companies in nearly every industry on Community, Enterprise, Odoo Online and Odoo.sh, often as several companies in one database. It supports 17 payment providers natively, each installed as its own module. Integrating Payment Hub with Odoo adds one module that sits across all of them:
Every ERP Payment Hub works with is on the ERP payment processing page.
Questions
Does Clarity Payment Hub integrate with Odoo?
Yes. Clarity Payment Hub integrates with Odoo (Community, Enterprise, Online, and Odoo.sh) through Odoo's standard XML-RPC and JSON-RPC API, the same external API surface Odoo and Odoo partners use to extend the platform. Authentication uses Odoo's session-based or API-key model.
Does Payment Hub work across all Odoo editions, Community, Enterprise, Online, Odoo.sh?
Yes. Payment Hub deploys cleanly on all four Odoo flavors. Odoo Community (the free, open-source self-hosted edition), installs as a standard Odoo module, integrates via XML-RPC. Odoo Enterprise (the paid, feature-extended edition with Studio, advanced apps, mobile), same module, additionally integrates with Studio-built custom forms and any Enterprise-only modules (Subscriptions, Field Service, Marketing Automation, etc.).
Does Payment Hub support Odoo's multi-company structure?
Yes. Odoo's multi-company architecture (multiple legal entities sharing one Odoo database) maps directly into Payment Hub's location routing table. Each Odoo company (res.company) can have its own merchant ID, gateway, bank account / journal, currency, tax setup, and country.
Does it require source-code modifications, custom Python, or Odoo module modifications?
No. The integration uses Odoo's published XML-RPC / JSON-RPC API exclusively. No core Odoo source modifications, no monkey-patching of standard modules, no custom Python in your existing codebase, no PostgreSQL triggers are required for the baseline integration.
What's the implementation timeline for Odoo?
A typical Payment Hub + Odoo integration goes live in 48 hours once Clarity receives Odoo test environment access (XML-RPC URL + database name + API key or admin credentials), gateway credentials, and your baseline routing configuration.
Related resources
One unified payment layer for all of Odoo.
Your Studio customizations and App Store modules keep working throughout. Live preview in a few days, production-ready in 48 hours.
Book a Live Demo