Illustrative previewEnterprise Adyen acquiring for Odoo 17/18/19: cards, 100+ local methods, 3DS2/SCA, HMAC webhook reconciliation.
Built to order by ECOSIRE.
What is Adyen Unified Gateway for Odoo?
Enterprise Adyen acquiring for Odoo 17/18/19: cards, 100+ local methods, 3DS2/SCA, HMAC webhook reconciliation. Built to order by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Odoo.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
Technical Specifications
- Odoo Compatibility
- Odoo 17, Odoo 18, Odoo 19
- Editions
- Enterprise & Community
- License
- Licence confirmation required
- Python Requirement
- Python 3.10+
- Database
- PostgreSQL 12+
About this Product
Standardize your global checkout on Adyen without leaving Odoo. The Adyen Unified Gateway is a build-to-order payment provider module that ECOSIRE designs, builds, installs and supports for your Odoo 17, 18 or 19 environment (Community or Enterprise). It is not an existing apps.odoo.com download — after purchase our engineers scope your acquiring setup, wire it to your live Adyen merchant account, and hand over production-ready code within a one working week lead time.
The module registers Adyen as a native payment.provider record so it appears wherever Odoo already takes payment: eCommerce checkout, the customer portal for invoices and quotations, subscriptions, and Sales/Invoicing "Pay Now" links. Shoppers pay through Adyen's Drop-in or Components UI, giving them cards plus 100+ local and alternative payment methods (iDEAL, Bancontact, SEPA, Klarna, PayPal, Apple Pay, Google Pay, Alipay, WeChat Pay and more) surfaced dynamically by country and currency — no per-method Odoo code to maintain.
Security and reconciliation are first-class. Every transaction runs through 3DS2 / SCA with Adyen RevenueProtect fraud controls, and asynchronous notification webhooks are verified with HMAC signatures before a single payment.transaction state changes, so a spoofed callback can never mark an order as paid. The full acquiring lifecycle — authorize, capture (immediate or delayed), partial and full refund, and void/cancel — is exposed on the Odoo transaction and its linked invoice through Adyen's API, with automated actions and server logging keeping Accounting in sync.
Under the hood it is clean, upgrade-safe Odoo: a proper __manifest__.py declaring dependencies (payment, account, and website_sale where relevant), Python models extending models.Model with computed fields via @api.depends, access control through ir.model.access.csv plus record rules, backend and portal views in XML/OWL, and configuration split cleanly between test and live Adyen environments. Credentials are stored as Odoo system parameters, never in source. You receive the source code, documentation, admin training and a post-launch support window — a maintainable asset your team owns, not a black box.
What you get
- Complete, commented Odoo module source (Python models, XML/OWL views, ir.model.access.csv, record rules, __manifest__.py) delivered to your Git repository
- Configured and tested integration against your live Adyen merchant account, including API key, merchant account, client key and HMAC webhook secret setup
- Test-environment build with sandbox transactions covering card, a local method, 3DS2 challenge, capture, refund and void paths
- Production deployment assistance and go-live checklist for your Odoo 17/18/19 instance (Community or Enterprise)
- Administrator and finance-team documentation covering configuration, the capture/refund/void workflow, and webhook reconciliation
- Live training session for your operations and accounting users on running and reconciling Adyen payments in Odoo
- Post-launch support window with bug fixes and configuration adjustments (duration set in your quotation)
- Handover notes and architecture summary so your in-house or partner developers can maintain and extend the module
Who this is for
Enterprise merchant standardizing on Adyen
A finance or e-commerce lead consolidating multiple regional acquirers onto a single Adyen contract, who needs Adyen to be the one gateway inside Odoo for web, portal and recurring payments — with clean reconciliation into Accounting.
Cross-border retailer needing local methods
A merchant selling across Europe, the Middle East and Asia who loses conversions at checkout because Odoo core doesn't surface iDEAL, Bancontact, Klarna or local wallets. They want 100+ methods appearing automatically by shopper country and currency.
Odoo administrator / ERP owner
The internal admin or implementation partner responsible for the Odoo instance who wants an upgrade-safe, well-documented module with proper access rules and secure credential handling — not a fragile custom hack they can't maintain across Odoo versions.
Compliance and finance controller
A controller accountable for PSD2/SCA compliance and accurate books, who needs verified HMAC webhooks, auditable transaction lifecycle, and refunds/voids that stay consistent between Adyen and Odoo journals.
How Adyen Unified Gateway for Odoo Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Adyen support in Odoo core | Full native payment.provider for Adyen (Drop-in/Components), built to order | You build it from scratch against Adyen's API | Varies by module; often single-region or card-only | Partial support |
| 100+ local & alternative methods surfaced by country | Yes, dynamic via Adyen Drop-in/Components | Only if you code and maintain each method | Usually a limited fixed subset | Not included |
| 3DS2 / SCA + RevenueProtect fraud handling | Included, mapped onto the Odoo transaction state | Must be implemented and tested by you | Sometimes; depth varies | Partial support |
| HMAC-verified, idempotent webhook reconciliation | Yes, signature checked before any state change | You design and secure the webhook yourself | Often basic or unsigned handling | Not included |
| Capture / partial refund / void lifecycle from Odoo | Full lifecycle on the transaction and linked invoice | Build each API call and UI action yourself | Frequently capture-only or refund-only | Partial support |
| Odoo 17/18/19, Community & Enterprise, upgrade-safe | Yes, clean manifest, access rules, version-tested | Depends on your team's practices | Per-version; upgrades may lag or cost extra | Included |
| Ownership, source code & documentation | Full source, docs, training and support window handed over | You own it but carry all the effort | Often obfuscated or license-restricted | Included |
| Time and effort to production | one working week build-to-order, tested against your account | Months of dev, QA and PCI/SCA work | Fast install but integration gaps to fill | Immediate but no Adyen at all |
Frequently Asked Questions about Adyen Unified Gateway
How long until the module is delivered, and is this an instant download?
This is a build-to-order module, not an instant apps.odoo.com download. After purchase our team scopes your Adyen setup, then builds, tests against your merchant account and installs it — typically within a one working week lead time depending on the number of payment methods, multi-company scope and any recurring/tokenization requirements. You get a firm timeline in your kickoff, plus a test-environment build before go-live.
What support and updates are included after launch?
Every engagement includes a post-launch support window (its length is set in your quotation) covering bug fixes, configuration adjustments and help with reconciliation questions. Because the module is written to be upgrade-safe across Odoo 17, 18 and 19, we can also quote version-upgrade and enhancement work — for example new payment methods or added tokenization — after the initial window. You receive the full source, so your own developers can maintain it too.
Which Odoo versions and editions does it support?
Odoo 17, 18 and 19, on both Community and Enterprise. Adyen is registered as a standard payment.provider, so it works with website eCommerce, the customer portal, Sales/Invoicing Pay-Now links and subscription billing wherever those apps are installed. We confirm your exact edition and installed apps during scoping so dependencies in the __manifest__.py match your instance.
Which payment methods and currencies will my customers see?
Cards plus 100+ Adyen local and alternative methods — iDEAL, Bancontact, SEPA, Klarna, PayPal, Apple Pay, Google Pay, Alipay, WeChat Pay and more — subject to what your Adyen contract enables. Using Adyen's Drop-in/Components, the available methods are surfaced dynamically by the shopper's country and currency, so you don't maintain per-method logic in Odoo. The module is multi-currency and multi-company aware.
How are payment confirmations kept secure and reconciled?
Adyen sends asynchronous notification webhooks, and the module verifies the HMAC signature on every one before it changes a payment.transaction state — a forged callback can never mark an order paid. Webhook handling is idempotent and matched on the Adyen reference, so duplicate or out-of-order notifications don't double-post. Paid, authorized, refunded and voided states sync to the linked invoice and journal entries.
Can we authorize now and capture later, or issue partial refunds?
Yes. The full acquiring lifecycle is exposed on the Odoo transaction: authorize, immediate or delayed/manual capture, partial and full refunds, and void/cancel. This suits fulfilment-then-charge workflows where you authorize at checkout and capture on dispatch. Actions can be triggered from the transaction form and, if needed, exposed over XML-RPC/JSON-RPC for external systems.
Do you store our Adyen API keys in the code?
No. API key, merchant account, client key and the HMAC webhook secret are stored as Odoo system parameters (with separate test and live environments), never committed to source. Access to payment configuration and transactions is governed by ir.model.access.csv and record rules so only authorized roles can view or act on them.
Related Modules
Advanced Web Domain Widget
A build-to-order Odoo widget that lets non-technical users compose dynamic filters across relational (`Many2one`/`Many2many`) fields using simplified, human-readable operators. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 database.
Advance POS View
A build-to-order Odoo Point of Sale extension that gives cashiers switchable product-view layouts and rich sorting and display controls at the register. ECOSIRE scopes, builds, installs, and supports it for your Odoo — it is not an instant download.
Aged Receivable / Payable Analytics
Interactive aged-balance dashboards for Odoo with configurable buckets, customer/vendor drill-down, multi-currency views and collection-priority scoring. Built to order, installed and supported by ECOSIRE on Odoo 17, 18 and 19.
AI Accounting Auto-Categorization
A build-to-order Odoo module that uses AI to suggest the right account for every transaction, match bank-statement lines automatically, and flag anomalies and duplicates so your team closes the books faster. ECOSIRE scopes, builds, installs and supports it on Odoo 17, 18 or 19.
Adyen Unified Gateway
Enterprise Adyen acquiring for Odoo 17/18/19: cards, 100+ local methods, 3DS2/SCA, HMAC webhook reconciliation. Built to order by ECOSIRE.
- Registers Adyen as a native Odoo payment.provider, live across eCommerce, customer portal, subscriptions and Sales/Invoicing Pay-Now links
- Drop-in and Components checkout embedded via OWL/JS so shoppers stay on your Odoo storefront with a PCI-friendly hosted card field
- Cards plus 100+ local and alternative methods (iDEAL, Bancontact, SEPA, Klarna, PayPal, Apple Pay, Google Pay, Alipay, WeChat Pay) surfaced dynamically by country and currency
- 3DS2 / SCA authentication with challenge and frictionless flows to meet PSD2 and reduce declines