Real-time
Two-way sync
Changes in Adyen or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ CRM
Adyen to Kustomer integration — real-time, two-way sync
Keep Adyen and Kustomer 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 Kustomer
Sync customers, invoices, and payment status between Adyen and Kustomer in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Kustomer 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 Users and API Credentials, Webhook Configurations, Settlement Detail Reports, Payments in Adyen to Conversations, Messages, Companies, Custom Objects (Klasses) in Kustomer 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 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 Keep customer attributes updated from billing systems so routing rules and SLAs reflect account value
- 04 Escalate conversation-derived signals into the CRM as tasks or opportunities
Common sync patterns
Collections with context
Finance sees the account owner and relationship history from Kustomer when chasing a balance, and sales sees that the chase is happening.
Where Kustomer 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.
Payment status on the account
Invoice and payment status from Adyen appears on the account in Kustomer, so reps see overdue balances before they promise the next order.
What you can sync between Adyen and Kustomer
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 | Kustomer 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. | Teams Team assignments support routing parity and reporting. | Merchant Accounts is specific to Adyen and Teams to Kustomer — 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. | Tags Labels on conversations and customers sync for categorization and analytics. | Stores is specific to Adyen and Tags to Kustomer — 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. | Notes Internal annotations carry context alongside synced conversations. | Users and API Credentials is specific to Adyen and Notes to Kustomer — 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. | Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Webhook Configurations is specific to Adyen and Customers to Kustomer — 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. | Conversations Support threads across channels sync outward for analytics and CRM context. | Settlement Detail Reports is specific to Adyen and Conversations to Kustomer — 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. | Messages Individual messages within conversations support full-thread replication. | Payments is specific to Adyen and Messages to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between Adyen and Kustomer
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 Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer Adyen Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
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.
- Kustomer: Subject to the platform's API rate limits.
What ships with Adyen ⇄ Kustomer
Connect Adyen and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Adyen or Kustomer 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 Kustomer record.
Observability
Monitoring
Track your Adyen ⇄ Kustomer 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 Kustomer.
How the Adyen and Kustomer 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.
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Adyen to Kustomer — 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 Kustomer 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
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Adyen and Kustomer 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 ⇄ KustomerCustomers 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 KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Adyen and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Adyen and Kustomer: 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.
-
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 Kustomer: Collections with context; Where Kustomer tracks deals: closed-won creates the finance record; Payment status on the account. Finance sees the account owner and relationship history from Kustomer when chasing a balance, and sales sees that the chase is happening.
-
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. Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. 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. Kustomer: API keys are issued as role-scoped bearer tokens, so integration access can be limited to the specific object types a sync touches. Stacksync's field mapping accounts for these differences between Adyen and Kustomer 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 Kustomer 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 413 integrations available for Adyen and Kustomer.
Popular · 6 of 413
-
Adyen ⇄ Xactly -
Adyen ⇄ Gong -
Adyen ⇄ Salesforce -
Kustomer ⇄ Recurly -
Kustomer ⇄ Rillet -
Kustomer ⇄ Workday
No integrations match .
