Two-way sync
Changes in Adyen or SAP Business ByDesign instantly reflect in both systems. No stale data, no manual imports.
Keep Adyen and SAP Business ByDesign 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 Payment Links, Merchant Accounts, Stores, Users and API Credentials in Adyen with Customer Invoices, Materials / Products, Purchase Orders, Opportunities in SAP Business ByDesign 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 ByDesign 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 ByDesign objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Opportunities Built-in CRM records synced with external sales tools when both are in use. | Payments is specific to Adyen and Opportunities to SAP Business ByDesign — 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. | Projects Project structures and tasks read for time and billing integrations. | Modifications (Captures, Refunds, Cancels) is specific to Adyen and Projects to SAP Business ByDesign — 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. | Employees Worker records referenced by time, expense, and project data. | Payment Links is specific to Adyen and Employees to SAP Business ByDesign — 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. | Business Partners (Accounts) Customer and supplier master data synced with CRMs and procurement tools. | Merchant Accounts is specific to Adyen and Business Partners (Accounts) to SAP Business ByDesign — 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. | Contacts Person records linked to accounts, aligned with CRM contact objects. | Stores is specific to Adyen and Contacts to SAP Business ByDesign — 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. | Sales Orders Order documents created from external channels and read for status. | Users and API Credentials is specific to Adyen and Sales Orders to SAP Business ByDesign — 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 ByDesign through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls SAP Business ByDesign for changes on an incremental schedule, reading only records changed since the previous pass. Polling on last-changed 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 ByDesign connection.
Changes in Adyen or SAP Business ByDesign instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Adyen or SAP Business ByDesign 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 ByDesign record.
Track your Adyen ⇄ SAP Business ByDesign sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Adyen and SAP Business ByDesign.
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 ByDesign 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 ByDesign 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 ByDesign: authenticate both systems, choose the objects to sync (such as Adyen's Payments and Modifications (Captures, Refunds, Cancels)), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Adyen side: Payment Links, Merchant Accounts, Stores, Users and API Credentials, plus custom fields where Adyen exposes them. On the SAP Business ByDesign side: Customer Invoices, Materials / Products, Purchase Orders, Opportunities. 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 ByDesign: Subsidiary to headquarters; Where Adyen handles billing: invoices land in SAP Business ByDesign; Migration without a hard cutover. Where Adyen serves a business unit and SAP Business ByDesign 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 ByDesign: SOAP web services plus OData services for analytical and custom data access. Authentication: Basic authentication over TLS for service users; OAuth-based options exist for certain scenarios. Stacksync manages authentication, retries, and rate limits on both sides.
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. SAP Business ByDesign: The integration surface is primarily SOAP web services organized around ByDesign's business object model, with OData services available for reporting-style access. Stacksync's field mapping accounts for these differences between Adyen and SAP Business ByDesign without custom code.
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 511 integrations available for Adyen and SAP Business ByDesign.