Skip to content
Accounting and finance ⇄ Analytics

Adyen to Treasuredata integration — real-time, two-way sync

Keep Adyen and Treasuredata 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 Treasuredata

Feed the customers, invoices, and revenue records in Adyen into Treasuredata in real time, so dashboards and reports run on current numbers instead of last night's export.

Adyen holds the financial truth: who the customers are, what they were invoiced, what they paid, and what revenue landed. Treasuredata is where that data is turned into dashboards, reports, and metrics, but it only reflects the world as of its last load. When the connection between them is a scheduled extract or a hand-built pipeline, analysis runs a step behind the books, and the numbers on a chart rarely match the numbers in the finance system.

Stacksync keeps Payments, Modifications (Captures, Refunds, Cancels), Payment Links, Merchant Accounts in Adyen in sync with Tables, Master (Parent) Segments, Segments, Journeys in Treasuredata, field by field and in real time. A customer, invoice, or amount created or corrected in Adyen shows up in Treasuredata within seconds, mapped to the right record. Where Treasuredata keeps its own accounts or users, the flow runs both ways, so finance attributes can enrich what Treasuredata already tracks.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning's reporting running on yesterday's figures.

Common use cases

  • 01 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.
  • 02 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.
  • 03 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
  • 04 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.

Common sync patterns

Where Treasuredata keeps account or user records: finance attributes enrich them

Status, plan, or outstanding balance from Adyen attaches to the matching account or user in Treasuredata, so segments and cohorts can be cut by real financial standing.

Financial records land in Treasuredata for reporting

Invoices, payments, and revenue from Adyen flow into Treasuredata as they change, so dashboards are built on live figures rather than a periodic extract.

One customer key across both

A customer or account in Adyen is matched to the corresponding record in Treasuredata, so financial numbers join cleanly to whatever Treasuredata already reports on.

What you can sync between Adyen and Treasuredata

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 Treasuredata 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. Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. Webhook Configurations is specific to Adyen and Query Jobs to Treasuredata — 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. Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. Settlement Detail Reports is specific to Adyen and Databases to Treasuredata — 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. Tables Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables. Payments is specific to Adyen and Tables to Treasuredata — 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. Master (Parent) Segments Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records. Modifications (Captures, Refunds, Cancels) is specific to Adyen and Master (Parent) Segments to Treasuredata — 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. Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. Payment Links is specific to Adyen and Segments to Treasuredata — 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. Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. Merchant Accounts is specific to Adyen and Journeys to Treasuredata — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Treasuredata

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

Treasuredata Adyen Interval-based propagation

DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.

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.
  • Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Adyen ⇄ Treasuredata

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Treasuredata

Integration surface
TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
Authentication
API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
Change detection
Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
Capabilities
read · write
Rate limits
TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works

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

    Choose tables

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

Adyen and Treasuredata 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
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 375 integrations available for Adyen and Treasuredata.

Popular · 3 of 375
All Adyen integrations All Treasuredata 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