Real-time
Two-way sync
Changes in Adyen or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Business productivity
Adyen to Microsoft Dynamics 365 integration — real-time, two-way sync
Keep Adyen and Microsoft Dynamics 365 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 Microsoft Dynamics 365
Connect the financial records in Adyen with the work happening in Microsoft Dynamics 365, so both stay current without exports or copy-paste.
Adyen holds the financial truth: who the customers are, what they were billed, what they paid. Microsoft Dynamics 365 is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.
Stacksync keeps Modifications (Captures, Refunds, Cancels), Payment Links, Merchant Accounts, Stores in Adyen and Activities, Custom Tables, Accounts, Contacts in Microsoft Dynamics 365 in sync, bi-directionally and in real time. Whatever records Microsoft Dynamics 365 keeps and whatever events it produces, the overlap with Adyen is mapped field by field, and a change on either side shows up on the other within seconds.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.
Common use cases
- 01 Ingest AUTHORISATION, CAPTURE, REFUND, and CHARGEBACK webhooks into Postgres or a warehouse so finance reconciles Adyen settlements against orders in an ERP without manual report exports.
- 02 Trigger a capture, refund, or cancel on an Adyen payment when an order's state changes in a CRM, OMS, or ERP, and write the returned pspReference and status back onto the record.
- 03 Two-way sync of accounts and contacts with a Postgres or SQL database so engineers query SQL while sales works in Dynamics.
- 04 Keep opportunities and orders consistent with the ERP or billing system without manual re-entry.
Common sync patterns
Where Microsoft Dynamics 365 handles customer conversations: billing context in view
Front-line teams see invoice and payment status from Adyen next to the customer they are helping, without logging into the finance system.
Where Microsoft Dynamics 365 collects payments or triggers charges: events land in Adyen
Payment and charge activity flows into Adyen as it happens, so the books reflect reality without manual reconciliation.
Where Microsoft Dynamics 365 tracks people or companies: one identity
A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.
What you can sync between Adyen and Microsoft Dynamics 365
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 | Microsoft Dynamics 365 objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Webhook Configurations is specific to Adyen and Opportunities to Microsoft Dynamics 365 — 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. | Cases (Incidents) Support records shared with ticketing tools and product databases. | Settlement Detail Reports is specific to Adyen and Cases (Incidents) to Microsoft Dynamics 365 — 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. | Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. | Payments is specific to Adyen and Quotes, Orders & Invoices to Microsoft Dynamics 365 — 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. | Products Catalog records aligned with ERP item masters. | Modifications (Captures, Refunds, Cancels) is specific to Adyen and Products to Microsoft Dynamics 365 — 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. | Activities Emails, calls, and tasks captured for engagement analytics. | Payment Links is specific to Adyen and Activities to Microsoft Dynamics 365 — 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. | Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | Merchant Accounts is specific to Adyen and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. |
How changes propagate between Adyen and Microsoft Dynamics 365
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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Adyen Sub-second propagation
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
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 ⇄ Microsoft Dynamics 365
Connect Adyen and Microsoft Dynamics 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–Microsoft Dynamics 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Adyen or Microsoft Dynamics 365 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 Microsoft Dynamics 365 record.
Observability
Monitoring
Track your Adyen ⇄ Microsoft Dynamics 365 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 Microsoft Dynamics 365.
How the Adyen and Microsoft Dynamics 365 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.
Microsoft Dynamics 365
- Integration surface
- REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
- Authentication
- Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
- Change detection
- Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
- Capabilities
- read · write · CDC · webhooks
How it works
How to connect Adyen to Microsoft Dynamics 365 — 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 Microsoft Dynamics 365 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
Microsoft Dynamics 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Adyen and Microsoft Dynamics 365 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 ⇄ Microsoft Dynamics 365Customers 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 Microsoft Dynamics 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Adyen and Microsoft Dynamics 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Adyen and Microsoft Dynamics 365: authenticate both systems, choose the objects to sync (such as Adyen's Webhook Configurations 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 Microsoft Dynamics 365: Where Microsoft Dynamics 365 handles customer conversations: billing context in view; Where Microsoft Dynamics 365 collects payments or triggers charges: events land in Adyen; Where Microsoft Dynamics 365 tracks people or companies: one identity. Front-line teams see invoice and payment status from Adyen next to the customer they are helping, without logging into the finance system.
-
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. Microsoft Dynamics 365: REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface. Authentication: Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities). Stacksync manages authentication, retries, and rate limits on both sides.
-
Adyen: Payment outcomes are asynchronous: a /payments call returns an authorization result, but final states such as captured, refunded, and charged back arrive later as standard webhooks keyed by pspReference and merchantReference. Microsoft Dynamics 365: Authorization may be blocked by a 'Need admin approval for this app' screen requiring a Microsoft directory admin to grant consent to the Stacksync app before syncing can begin. Stacksync's field mapping accounts for these differences between Adyen and Microsoft Dynamics 365 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 Microsoft Dynamics 365 records are not retained after a sync operation.
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 508 integrations available for Adyen and Microsoft Dynamics 365.
Popular · 7 of 508
-
Adyen ⇄ Campfire -
Adyen ⇄ Front -
Adyen ⇄ SendGrid -
Microsoft Dynamics 365 ⇄ Anaplan -
Microsoft Dynamics 365 ⇄ Chargebee -
Microsoft Dynamics 365 ⇄ Hyperline -
Microsoft Dynamics 365 ⇄ Pigment
No integrations match .
