Skip to content
Accounting and finance ⇄ ERP

Adyen to Dynamics 365 Business Central integration — real-time, two-way sync

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.

  • 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 Dynamics 365 Business Central

Keep Adyen and Dynamics 365 Business Central 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 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.

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 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.
  • 04 Sync vendor and purchase order data with procurement or AP automation tools.

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 Dynamics 365 Business Central is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

Where Adyen handles billing: invoices land in Dynamics 365 Business Central

Invoices and payment activity from the billing side post through to the enterprise system automatically.

What you can sync between Adyen and Dynamics 365 Business Central

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.

How changes propagate between Adyen and Dynamics 365 Business Central

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 Dynamics 365 Business Central 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 Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Dynamics 365 Business Central Adyen Sub-second propagation

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.

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.
What ships with Adyen ⇄ Dynamics 365 Business Central

Connect Adyen and Dynamics 365 Business Central for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–Dynamics 365 Business Central connection.

Real-time

Two-way sync

Changes in Adyen or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Adyen or Dynamics 365 Business Central 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 Dynamics 365 Business Central record.

Observability

Monitoring

Track your Adyen ⇄ Dynamics 365 Business Central 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 Dynamics 365 Business Central.

How the Adyen and Dynamics 365 Business Central 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.

Dynamics 365 Business Central

Integration surface
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
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks
How it works

How to connect Adyen to Dynamics 365 Business Central — 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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Adyen connected
    Dynamics 365 Business Central connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Adyen ⇄ Dynamics 365 Business Central
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Adyen Dynamics 365 Business Central
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Adyen and Dynamics 365 Business Central integration FAQ

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 504 integrations available for Adyen and Dynamics 365 Business Central.

Popular · 7 of 504
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.