Two-way sync
Changes in Adyen or SAP Business One instantly reflect in both systems. No stale data, no manual imports.
Keep Adyen and SAP Business One in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Settlement Detail Reports, Payments, Modifications (Captures, Refunds, Cancels), Payment Links in Adyen with Activities, Business Partners, Items, Sales Orders in SAP Business One 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.
Where Adyen serves a business unit and SAP Business One is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Invoices and payment activity from the billing side post through to the enterprise system automatically.
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
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 | SAP Business One objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Journal Entries GL postings replicated for financial reporting. | Stores is specific to Adyen and Journal Entries to SAP Business One — each maps to any object or custom field on the other side. | |
| Users and API Credentials Customer Area users and API-credential objects managed via the Management API; created, updated, and deprovisioned to keep Adyen access aligned with an IdP or HR source. | Warehouses Stock locations that scope inventory quantities in item syncs. | Users and API Credentials is specific to Adyen and Warehouses to SAP Business One — each maps to any object or custom field on the other side. | |
| Webhook Configurations Per-company or per-merchant webhook subscriptions (Management API); created, listed, and updated to control which events Adyen sends and to which endpoint and HMAC key. | Price Lists Pricing data synced to quoting and e-commerce platforms. | Webhook Configurations is specific to Adyen and Price Lists to SAP Business One — each maps to any object or custom field on the other side. | |
| 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. | Activities CRM-style tasks and interactions aligned with external sales tools. | Settlement Detail Reports is specific to Adyen and Activities to SAP Business One — 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. | Business Partners Combined customer, vendor, and lead master records; the anchor object for most syncs. | Payments is specific to Adyen and Business Partners to SAP Business One — 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. | Items Product master data including inventory levels, aligned with e-commerce and warehouse systems. | Modifications (Captures, Refunds, Cancels) is specific to Adyen and Items to SAP Business One — each maps to any object or custom field on the other side. |
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.
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 SAP Business One through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls SAP Business One for changes on an incremental schedule, reading only records changed since the previous pass. Polling on update timestamps.
DeliveryEach detected change is written to Adyen through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–SAP Business One connection.
Changes in Adyen or SAP Business One instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Adyen or SAP Business One data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Adyen or SAP Business One record.
Track your Adyen ⇄ SAP Business One sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Adyen and SAP Business One.
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.
Authenticate Adyen and SAP Business One with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Adyen and SAP Business One 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Adyen and SAP Business One: authenticate both systems, choose the objects to sync (such as Adyen's Stores and Users and API Credentials), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 SAP Business One: Polling on update timestamps; no general-purpose webhook mechanism on the standard surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Adyen side: Settlement Detail Reports, Payments, Modifications (Captures, Refunds, Cancels), Payment Links, plus custom fields where Adyen exposes them. On the SAP Business One side: Activities, Business Partners, Items, Sales Orders. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Adyen and SAP Business One: Subsidiary to headquarters; Where Adyen handles billing: invoices land in SAP Business One; Migration without a hard cutover. Where Adyen serves a business unit and SAP Business One is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Adyen: 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. SAP Business One: Service Layer, a REST API based on OData, plus the legacy COM-based DI API. Authentication: Session-based login with company database, username, and password against the Service Layer. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 509 integrations available for Adyen and SAP Business One.