Two-way sync
Changes in Adyen or Azure Synapse Analytics instantly reflect in both systems. No stale data, no manual imports.
Keep Adyen and Azure Synapse Analytics in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Finance data belongs in the warehouse: revenue, invoices, payments, and customers joined with everything else the business measures. Getting it there usually means an extraction pipeline that breaks quietly and delivers yesterday's numbers.
Stacksync syncs Settlement Detail Reports, Payments, Modifications (Captures, Refunds, Cancels), Payment Links from Adyen into tables in Azure Synapse Analytics in real time, and the connection works in both directions: values computed in Azure Synapse Analytics can be written back to fields in Adyen where you want them operational. Schema changes are handled, API limits are managed, and the sync is something you configure rather than code you maintain.
Scores or segments computed in Azure Synapse Analytics, like payment-risk flags or customer tiers, sync back onto records in Adyen where the finance team can act on them.
A continuously synced copy in Azure Synapse Analytics gives you a durable, queryable record of financial data for month-end and audit questions.
Invoices, payments, and customer records from Adyen arrive in Azure Synapse Analytics as queryable tables, current within seconds instead of a day behind.
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 | Azure Synapse Analytics 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. | SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | Merchant Accounts is specific to Adyen and SQL pools to Azure Synapse Analytics — 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. | Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | Stores is specific to Adyen and Tables (dedicated SQL pool) to Azure Synapse Analytics — 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. | External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | Users and API Credentials is specific to Adyen and External tables to Azure Synapse Analytics — 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. | Views Curated projections used when downstream tools should not read base tables directly. | Webhook Configurations is specific to Adyen and Views to Azure Synapse Analytics — 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. | Schemas Namespaces that separate staging, integration, and presentation layers. | Settlement Detail Reports is specific to Adyen and Schemas to Azure Synapse Analytics — 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. | Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | Payments is specific to Adyen and Materialized views to Azure Synapse Analytics — 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 applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
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–Azure Synapse Analytics connection.
Changes in Adyen or Azure Synapse Analytics instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Adyen or Azure Synapse Analytics 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 Azure Synapse Analytics record.
Track your Adyen ⇄ Azure Synapse Analytics sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Adyen and Azure Synapse Analytics.
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 Azure Synapse Analytics 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 Azure Synapse Analytics 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 Azure Synapse Analytics: 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.
Common patterns for Adyen and Azure Synapse Analytics: Write-back of computed fields; Queryable history for audit and reconciliation; Finance analytics without ETL. Scores or segments computed in Azure Synapse Analytics, like payment-risk flags or customer tiers, sync back onto records in Adyen where the finance team can act on them.
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. Azure Synapse Analytics: SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint. Authentication: SQL authentication or Microsoft Entra ID. 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. Azure Synapse Analytics: The serverless SQL pool queries files in the data lake directly, so some 'tables' a sync sees are projections over Parquet or CSV rather than managed storage. Stacksync's field mapping accounts for these differences between Adyen and Azure Synapse Analytics 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 Azure Synapse Analytics records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Adyen and Azure Synapse Analytics connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Adyen–Azure Synapse Analytics integration in-house.
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 536 integrations available for Adyen and Azure Synapse Analytics.