Skip to content
Accounting and finance ⇄ Data warehouse

Adyen to Apache Druid integration — real-time, two-way sync

Keep Adyen and Apache Druid 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 Apache Druid

Land the financial records from Adyen in Apache Druid continuously, and write results back, without building or maintaining a pipeline.

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 Payment Links, Merchant Accounts, Stores, Users and API Credentials from Adyen into tables in Apache Druid in real time, and the connection works in both directions: values computed in Apache Druid 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.

Common use cases

  • 01 Create Adyen Payment Links from an invoicing or billing system and sync each link's paid or expired status back so accounts receivable sees payment without opening the Customer Area.
  • 02 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.
  • 03 Keep lookup tables in Druid refreshed from a CRM or database so query-time joins use current reference data.
  • 04 Expose product telemetry stored in Druid to business tools without granting direct cluster access.

Common sync patterns

Write-back of computed fields

Scores or segments computed in Apache Druid, like payment-risk flags or customer tiers, sync back onto records in Adyen where the finance team can act on them.

Queryable history for audit and reconciliation

A continuously synced copy in Apache Druid gives you a durable, queryable record of financial data for month-end and audit questions.

Finance analytics without ETL

Invoices, payments, and customer records from Adyen arrive in Apache Druid as queryable tables, current within seconds instead of a day behind.

What you can sync between Adyen and Apache Druid

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 Apache Druid objects How this pairing syncs
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. Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Settlement Detail Reports is specific to Adyen and Metrics to Apache Druid — 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. Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Payments is specific to Adyen and Ingestion Supervisors to Apache Druid — 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. Lookups Key-value mappings joined at query time, refreshable from external systems. Modifications (Captures, Refunds, Cancels) is specific to Adyen and Lookups to Apache Druid — 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. Tasks Batch ingestion and compaction jobs monitored during data loads. Payment Links is specific to Adyen and Tasks to Apache Druid — 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. Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Merchant Accounts is specific to Adyen and Datasources to Apache Druid — 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. Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Stores is specific to Adyen and Segments to Apache Druid — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Apache Druid

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 Apache Druid 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 applied to Apache Druid as a row-level write, with types converted between the two schemas.

Apache Druid Adyen Interval-based propagation

DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.

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.
  • Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
What ships with Adyen ⇄ Apache Druid

Connect Adyen and Apache Druid for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–Apache Druid connection.

Real-time

Two-way sync

Changes in Adyen or Apache Druid instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Adyen or Apache Druid 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 Apache Druid record.

Observability

Monitoring

Track your Adyen ⇄ Apache Druid 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 Apache Druid.

How the Adyen and Apache Druid 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.

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity
How it works

How to connect Adyen to Apache Druid — 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 Apache Druid 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
    Apache Druid connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Adyen and Apache Druid 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 ⇄ Apache Druid
    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 Apache Druid
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Adyen and Apache Druid 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 435 integrations available for Adyen and Apache Druid.

Popular · 7 of 435
All Adyen integrations All Apache Druid integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own