Real-time
Two-way sync
Changes in Adyen or Odoo instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ ERP
Adyen to Odoo integration — real-time, two-way sync
Keep Adyen and Odoo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Adyen and Odoo
Keep Adyen and Odoo agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.
A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.
Stacksync syncs Stores, Users and API Credentials, Webhook Configurations, Settlement Detail Reports in Adyen with Sales Orders (sale.order), Invoices (account.move), Products (product.template / product.product), CRM Leads (crm.lead) in Odoo in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Provision Stores, Users, and API credentials through the Management API from an internal admin app or IdP so new locations and staff get the right Adyen access automatically.
- 02 Load Settlement Detail Reports into a warehouse to break out fees, interchange, and net payouts by merchant account for finance and treasury reporting.
- 03 Sync employee records from an HR system of record into Odoo for expense and timesheet workflows.
- 04 Sync Odoo contacts and CRM leads with an external CRM when sales runs outside Odoo but invoicing stays in it.
Common sync patterns
One customer and vendor master
Where both systems keep records of the same organizations, corrections made in either propagate to the other.
Subsidiary to headquarters
Where Adyen serves a business unit and Odoo is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Where Adyen handles billing: invoices land in Odoo
Invoices and payment activity from the billing side post through to the enterprise system automatically.
What you can sync between Adyen and Odoo
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Adyen objects | Odoo objects | How this pairing syncs | |
|---|---|---|---|
| Settlement Detail Reports Downloadable reports of settled transactions, fees, and payouts per merchant account; read-only, delivered when a report webhook fires, and loaded for finance reconciliation. | Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. | Settlement Detail Reports is specific to Adyen and Purchase Orders (purchase.order) to Odoo — each maps to any object or custom field on the other side. | |
| Payments Checkout API payment requests and results (/payments); created to authorize a card, wallet, or local payment, and retrieved by pspReference. Final state arrives asynchronously via the AUTHORISATION webhook. | Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. | Payments is specific to Adyen and Inventory Transfers (stock.picking) to Odoo — each maps to any object or custom field on the other side. | |
| Modifications (Captures, Refunds, Cancels) Actions on an authorized payment via /payments/{pspReference}/captures, /refunds, and /cancels; written to settle, return, or void funds, with results confirmed by CAPTURE and REFUND webhooks. | Employees (hr.employee) HR records read for directory and provisioning syncs. | Modifications (Captures, Refunds, Cancels) is specific to Adyen and Employees (hr.employee) to Odoo — each maps to any object or custom field on the other side. | |
| Payment Links Hosted payment link objects created through /paymentLinks; created, retrieved, and expired, with paid or expired status reported back through webhooks for accounts-receivable sync. | Projects and Tasks (project.project / project.task) Work items synced with external project tools. | Payment Links is specific to Adyen and Projects and Tasks (project.project / project.task) to Odoo — each maps to any object or custom field on the other side. | |
| Merchant Accounts Company and merchant account entities in the Management API; read and updated to keep account configuration, payment-method settings, and capabilities aligned with internal systems. | Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | Merchant Accounts is specific to Adyen and Contacts (res.partner) to Odoo — each maps to any object or custom field on the other side. | |
| Stores Physical and online store entities under a merchant account (Management API); full CRUD, so new locations and their payment-method configuration can be provisioned from an internal admin source. | Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. | Stores is specific to Adyen and Sales Orders (sale.order) to Odoo — each maps to any object or custom field on the other side. |
How changes propagate between Adyen and Odoo
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Adyen Odoo Sub-second propagation
DetectionAdyen notifies Stacksync of record changes through webhook events. Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks.
DeliveryEach detected change is written to Odoo through its API, with automatic retries and rate-limit backoff.
Odoo Adyen Sub-second propagation
DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.
DeliveryEach detected change is written to Adyen through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Adyen: Adyen does not publish fixed numeric rate limits; excessive requests return HTTP 429, and the Management API reports 'too many requests' in the error detail. Adyen recommends exponential backoff, and no rate-limit response headers are documented.
- Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
What ships with Adyen ⇄ Odoo
Connect Adyen and Odoo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–Odoo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Adyen or Odoo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Adyen or Odoo record.
Observability
Monitoring
Track your Adyen ⇄ Odoo sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Adyen and Odoo.
How the Adyen and Odoo connectors work
Adyen
- Integration surface
- REST APIs on adyen.com - Checkout (/checkout/v71), Management (/v3), Balance Platform / Configuration, Transfers, Payouts, and Reports, with standard webhooks for events
- Authentication
- API key in the X-API-Key header per web service or Balance Platform user (primary for Checkout, Management, and Balance Platform); Basic auth for classic web-service users; OAuth 2.0 for partner integrations; client keys are client-side only
- Change detection
- Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks; all HMAC-signed and acknowledged with a 2xx within about 10 seconds. No database-style CDC; historical transactions come from Settlement Detail Reports
- Capabilities
- read · write · webhooks
- Rate limits
- Adyen does not publish fixed numeric rate limits; excessive requests return HTTP 429, and the Management API reports 'too many requests' in the error detail. Adyen recommends exponential backoff, and no rate-limit response headers are documented.
Odoo
- Integration surface
- XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink)
- Authentication
- Database user credentials or per-user API keys
- Change detection
- Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
- Capabilities
- read · write · webhooks
- Rate limits
- Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
How it works
How to connect Adyen to Odoo — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Adyen and Odoo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Adyen
connected
Odoo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Adyen and Odoo objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Adyen ⇄ OdooCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Adyen OdooCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Adyen and Odoo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Adyen and Odoo: authenticate both systems, choose the objects to sync (such as Adyen's Settlement Detail Reports and Payments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Adyen: Adyen does not publish fixed numeric API rate limits; excessive requests return HTTP 429 (the Management API surfaces 'too many requests' in the error detail), and clients are expected to apply exponential backoff. Odoo: The external API exposes the ORM generically: any model (res.partner, sale.order, account.move) is accessed with the same execute_kw call pattern rather than per-object endpoints. Stacksync's field mapping accounts for these differences between Adyen and Odoo without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Adyen and Odoo records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Adyen and Odoo connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Adyen–Odoo integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Adyen and Odoo. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Adyen: Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks; all HMAC-signed and acknowledged with a 2xx within about 10 seconds. No database-style CDC; historical transactions come from Settlement Detail Reports. On Odoo: Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 515 integrations available for Adyen and Odoo.
Popular · 6 of 515
No integrations match .
