Two-way sync
Changes in Adyen or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Keep Adyen and Salesforce 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 and sales describe the same customers in different systems. Salesforce 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 Payment Links, Merchant Accounts, Stores, Users and API Credentials in Adyen to Opportunities, Cases, Campaigns, Tasks and Events in Salesforce 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.
When a contact or address is corrected in Salesforce, Adyen gets the update before the next invoice goes out.
Finance sees the account owner and relationship history from Salesforce when chasing a balance, and sales sees that the chase is happening.
A won opportunity creates or updates the customer in Adyen with the right billing details, so invoicing starts without re-keying.
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Modifications (Captures, Refunds, Cancels) is specific to Adyen and Leads to Salesforce — 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. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Payment Links is specific to Adyen and Opportunities to Salesforce — 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. | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Merchant Accounts is specific to Adyen and Cases to Salesforce — 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. | Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Stores is specific to Adyen and Campaigns to Salesforce — 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. | Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | Users and API Credentials is specific to Adyen and Tasks and Events to Salesforce — 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. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | Webhook Configurations is specific to Adyen and Products and Price Books to Salesforce — 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 written to Salesforce through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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–Salesforce connection.
Changes in Adyen or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Adyen or Salesforce 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 Salesforce record.
Track your Adyen ⇄ Salesforce sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Adyen and Salesforce.
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 Salesforce 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 Salesforce 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 Salesforce: authenticate both systems, choose the objects to sync (such as Adyen's Modifications (Captures, Refunds, Cancels) and Payment Links), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Adyen: 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. On Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Adyen side: Payment Links, Merchant Accounts, Stores, Users and API Credentials, plus custom fields where Adyen exposes them. On the Salesforce side: Opportunities, Cases, Campaigns, Tasks and Events. Stacksync auto-detects both schemas and converts types between the two systems.
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 Salesforce: Billing detail changes flow back; Collections with context; Where Salesforce tracks deals: closed-won creates the finance record. When a contact or address is corrected in Salesforce, Adyen gets the update before the next invoice goes out.
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. Salesforce: REST, SOAP, and Bulk APIs. Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode. Stacksync manages authentication, retries, and rate limits on both sides.
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 532 integrations available for Adyen and Salesforce.