Real-time
Two-way sync
Changes in Adyen or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ CRM
Adyen to Microsoft Dynamics 365 Sales integration — real-time, two-way sync
Keep Adyen and Microsoft Dynamics 365 Sales 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 Sales
Sync customers, invoices, and payment status between Adyen and Microsoft Dynamics 365 Sales in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Microsoft Dynamics 365 Sales knows the relationship: who the contacts are and what is in motion with the account. Adyen knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Webhook Configurations, Settlement Detail Reports, Payments, Modifications (Captures, Refunds, Cancels) in Adyen to Quotes, Orders, Invoices, Activities in Microsoft Dynamics 365 Sales with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
Common use cases
- 01 Load Settlement Detail Reports into a warehouse to break out fees, interchange, and net payouts by merchant account for finance and treasury reporting.
- 02 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.
- 03 Feed BI models with continuously updated CRM data instead of scheduled exports.
- 04 Bi-directional sync of accounts, contacts, and opportunities with a SQL database so teams query CRM data without OData or FetchXML.
Common sync patterns
Billing detail changes flow back
When a contact or address is corrected in Microsoft Dynamics 365 Sales, Adyen gets the update before the next invoice goes out.
Collections with context
Finance sees the account owner and relationship history from Microsoft Dynamics 365 Sales when chasing a balance, and sales sees that the chase is happening.
Where Microsoft Dynamics 365 Sales tracks deals: closed-won creates the finance record
A won opportunity creates or updates the customer in Adyen with the right billing details, so invoicing starts without re-keying.
What you can sync between Adyen and Microsoft Dynamics 365 Sales
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 Sales objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Contacts Person records linked to accounts; synced with marketing and support systems. | Merchant Accounts is specific to Adyen and Contacts to Microsoft Dynamics 365 Sales — 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. | Leads Prospect records; written in from enrichment or web forms, read out on qualification. | Stores is specific to Adyen and Leads to Microsoft Dynamics 365 Sales — 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. | Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. | Users and API Credentials is specific to Adyen and Opportunities to Microsoft Dynamics 365 Sales — 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. | Quotes Pricing proposals; often synced with CPQ or ERP pricing data. | Webhook Configurations is specific to Adyen and Quotes to Microsoft Dynamics 365 Sales — 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. | Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. | Settlement Detail Reports is specific to Adyen and Orders to Microsoft Dynamics 365 Sales — 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. | Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. | Payments is specific to Adyen and Invoices to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. |
How changes propagate between Adyen and Microsoft Dynamics 365 Sales
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 Sales 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 Sales through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Sales Adyen Sub-second propagation
DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.
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.
- Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
What ships with Adyen ⇄ Microsoft Dynamics 365 Sales
Connect Adyen and Microsoft Dynamics 365 Sales for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–Microsoft Dynamics 365 Sales connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Adyen or Microsoft Dynamics 365 Sales 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 Sales record.
Observability
Monitoring
Track your Adyen ⇄ Microsoft Dynamics 365 Sales 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 Sales.
How the Adyen and Microsoft Dynamics 365 Sales 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 Sales
- Integration surface
- Dataverse Web API (OData v4 REST)
- Authentication
- OAuth 2.0 via Microsoft Entra ID
- Change detection
- Dataverse change tracking with delta tokens, plus registered webhooks on table events
- Capabilities
- read · write · webhooks
- Rate limits
- Requests are governed by Dataverse service protection limits evaluated per user and time window.
How it works
How to connect Adyen to Microsoft Dynamics 365 Sales — 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 Sales 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 Sales
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Adyen and Microsoft Dynamics 365 Sales 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 365 SalesCustomers 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 365 SalesCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Adyen and Microsoft Dynamics 365 Sales integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Adyen and Microsoft Dynamics 365 Sales: authenticate both systems, choose the objects to sync (such as Adyen's Merchant Accounts and Stores), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Adyen and Microsoft Dynamics 365 Sales connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Adyen–Microsoft Dynamics 365 Sales integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Adyen and Microsoft Dynamics 365 Sales. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
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 Microsoft Dynamics 365 Sales: Dataverse change tracking with delta tokens, plus registered webhooks on table events. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Adyen side: Webhook Configurations, Settlement Detail Reports, Payments, Modifications (Captures, Refunds, Cancels), plus custom fields where Adyen exposes them. On the Microsoft Dynamics 365 Sales side: Quotes, Orders, Invoices, Activities. 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.
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 426 integrations available for Adyen and Microsoft Dynamics 365 Sales.
Popular · 7 of 426
-
Adyen ⇄ Apollo.io -
Adyen ⇄ Close -
Adyen ⇄ Copper CRM -
Microsoft Dynamics 365 Sales ⇄ Bill -
Microsoft Dynamics 365 Sales ⇄ Braintree -
Microsoft Dynamics 365 Sales ⇄ Navan -
Microsoft Dynamics 365 Sales ⇄ Ramp
No integrations match .
