Real-time
Two-way sync
Changes in Adyen or Splunk instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Analytics
Adyen to Splunk integration — real-time, two-way sync
Keep Adyen and Splunk 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 Splunk
Feed the customers, invoices, and revenue records in Adyen into Splunk 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. Splunk 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 Search Results, Saved Searches, Fired Alerts, KV Store Collections in Splunk, field by field and in real time. A customer, invoice, or amount created or corrected in Adyen shows up in Splunk within seconds, mapped to the right record. Where Splunk keeps its own accounts or users, the flow runs both ways, so finance attributes can enrich what Splunk 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 Provision and update Saved Searches, alerts, and Dashboards from a Git-backed config repository so detections and reports stay versioned and consistent across search heads.
- 04 Export Users and Roles into an IAM database for periodic access reviews, or provision them from an identity source of truth.
Common sync patterns
Revenue alongside the rest of the data
The amounts Adyen records sit next to product, usage, or operational data in Splunk, so a single view combines what was billed with what actually happened.
Reports refresh as the books change
Instead of waiting for a scheduled load, Splunk updates the moment a figure moves in Adyen, so a dashboard opened at any point in the day is current.
Where Splunk keeps account or user records: finance attributes enrich them
Status, plan, or outstanding balance from Adyen attaches to the matching account or user in Splunk, so segments and cohorts can be cut by real financial standing.
What you can sync between Adyen and Splunk
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 | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Users and Roles Accounts at /services/authentication/users and role/capability definitions at /services/authorization/roles, with full CRUD; exported for access reviews or provisioned from an identity source of truth. | Stores is specific to Adyen and Users and Roles to Splunk — 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. | Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control. | Users and API Credentials is specific to Adyen and Dashboards to Splunk — 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. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Webhook Configurations is specific to Adyen and Search Results to Splunk — 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. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Settlement Detail Reports is specific to Adyen and Saved Searches to Splunk — 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. | Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting. | Payments is specific to Adyen and Fired Alerts to Splunk — 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. | KV Store Collections App-scoped, MongoDB-backed key-value collections at /servicesNS/{owner}/{app}/storage/collections/data/{collection} with full CRUD and batch endpoints. Genuinely bidirectional lookup/state store — read records out or write records in. | Modifications (Captures, Refunds, Cancels) is specific to Adyen and KV Store Collections to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Adyen and Splunk
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 Splunk 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 Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Adyen Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
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.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Adyen ⇄ Splunk
Connect Adyen and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Adyen or Splunk 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 Splunk record.
Observability
Monitoring
Track your Adyen ⇄ Splunk 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 Splunk.
How the Adyen and Splunk 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.
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Adyen to Splunk — 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 Splunk 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
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Adyen and Splunk 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 ⇄ SplunkCustomers 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 SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Adyen and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Adyen and Splunk: authenticate both systems, choose the objects to sync (such as Adyen's Stores and Users and API Credentials), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. Splunk: REST API (management API + HTTP Event Collector). Authentication: HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud). Stacksync manages authentication, retries, and rate limits on both sides.
-
Adyen: Adyen has no generic list-all-payments endpoint; historical transaction data is retrieved from Settlement Detail Reports and reconciled with the pspReference from webhooks, and amounts are expressed in minor units with a currency code. Splunk: Searches are asynchronous: POST /services/search/jobs returns a search ID (SID), and results are fetched from /services/search/jobs/{sid}/results once the job completes; oneshot and export modes return results synchronously. Stacksync's field mapping accounts for these differences between Adyen and Splunk 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 Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Adyen and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Adyen–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Adyen and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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
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 473 integrations available for Adyen and Splunk.
Popular · 5 of 473
No integrations match .
