Two-way sync
Changes in Adyen or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Keep Adyen and Dynamics 365 Business Central 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 Payments, Modifications (Captures, Refunds, Cancels), Payment Links, Merchant Accounts in Adyen with Journals, Dimensions, Payments, Customers in Dynamics 365 Business Central 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 both systems keep records of the same organizations, corrections made in either propagate to the other.
Where Adyen serves a business unit and Dynamics 365 Business Central 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.
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 | Dynamics 365 Business Central 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. | Payments Customer and vendor payment records reconciled against invoices. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| 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 Procurement documents exchanged with supplier-facing systems. | Settlement Detail Reports is specific to Adyen and Purchase Orders to Dynamics 365 Business Central — 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. | General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Modifications (Captures, Refunds, Cancels) is specific to Adyen and General Ledger Entries to Dynamics 365 Business Central — 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. | Journals Staging records for financial postings created by integrations before posting. | Payment Links is specific to Adyen and Journals to Dynamics 365 Business Central — 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. | Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Merchant Accounts is specific to Adyen and Dimensions to Dynamics 365 Business Central — 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. | Customers Core master data synced with CRMs so sales and finance share one customer list. | Stores is specific to Adyen and Customers to Dynamics 365 Business Central — 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 Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
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–Dynamics 365 Business Central connection.
Changes in Adyen or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Adyen or Dynamics 365 Business Central 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 Dynamics 365 Business Central record.
Track your Adyen ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Adyen and Dynamics 365 Business Central.
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 Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Adyen's Payments and Settlement Detail Reports), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Dynamics 365 Business Central: One customer and vendor master; Subsidiary to headquarters; Where Adyen handles billing: invoices land in Dynamics 365 Business Central. Where both systems keep records of the same organizations, corrections made in either propagate to the other.
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. Dynamics 365 Business Central: REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL. Authentication: OAuth 2.0 via Microsoft Entra ID. 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. Dynamics 365 Business Central: The standard API exposes entities as OData v4 endpoints and supports $filter on lastModifiedDateTime, giving integrations a built-in incremental cursor. Stacksync's field mapping accounts for these differences between Adyen and Dynamics 365 Business Central 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 Dynamics 365 Business Central records are not retained after a sync operation.
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 504 integrations available for Adyen and Dynamics 365 Business Central.