Skip to content
Accounting and finance ⇄ Business productivity

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

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

Connect the financial records in Adyen with the work happening in eClinicalWorks, so both stay current without exports or copy-paste.

Adyen holds the financial truth: who the customers are, what they were billed, what they paid. eClinicalWorks is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Users and API Credentials, Webhook Configurations, Settlement Detail Reports, Payments in Adyen and Practitioners, Observations, Medications, Allergies in eClinicalWorks in sync, bi-directionally and in real time. Whatever records eClinicalWorks keeps and whatever events it produces, the overlap with Adyen is mapped field by field, and a change on either side shows up on the other within seconds.

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

Common use cases

  • 01 Load Settlement Detail Reports into a warehouse to break out fees, interchange, and net payouts by merchant account for finance and treasury reporting.
  • 02 Ingest AUTHORISATION, CAPTURE, REFUND, and CHARGEBACK webhooks into Postgres or a warehouse so finance reconciles Adyen settlements against orders in an ERP without manual report exports.
  • 03 Feed appointment events to reminder and messaging platforms to reduce no-shows.
  • 04 Keep provider directories consistent between eClinicalWorks and scheduling or marketing systems.

Common sync patterns

Where eClinicalWorks collects payments or triggers charges: events land in Adyen

Payment and charge activity flows into Adyen as it happens, so the books reflect reality without manual reconciliation.

Where eClinicalWorks tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

Where eClinicalWorks is a docs or knowledge workspace: reference data kept fresh

Figures teams rely on, like customer status or outstanding balances, stay current wherever eClinicalWorks surfaces them instead of going stale after a one-time paste.

What you can sync between Adyen and eClinicalWorks

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 eClinicalWorks objects How this pairing syncs
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. Medications Prescription and medication-list data within the patient record. Payment Links is specific to Adyen and Medications to eClinicalWorks — 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. Allergies Allergy and intolerance entries in the clinical record. Merchant Accounts is specific to Adyen and Allergies to eClinicalWorks — 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. Immunizations Vaccination history exposed for registries and patient apps. Stores is specific to Adyen and Immunizations to eClinicalWorks — 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. Documents Clinical notes and attachments referenced from the chart. Users and API Credentials is specific to Adyen and Documents to eClinicalWorks — 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. Diagnostic reports Structured result reports grouping observations for a study or panel. Webhook Configurations is specific to Adyen and Diagnostic reports to eClinicalWorks — 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. Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. Settlement Detail Reports is specific to Adyen and Patients to eClinicalWorks — each maps to any object or custom field on the other side.

How changes propagate between Adyen and eClinicalWorks

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

eClinicalWorks Adyen Interval-based propagation

DetectionStacksync polls eClinicalWorks for changes on an incremental schedule, reading only records changed since the previous pass. HL7 interface feeds push event messages as they occur.

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.
  • eClinicalWorks: Subject to the platform's API rate limits and interface throughput agreements.
What ships with Adyen ⇄ eClinicalWorks

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

eClinicalWorks

Integration surface
FHIR R4 REST API plus HL7 v2 interfaces (ADT, SIU, ORU) through an interface engine
Authentication
OAuth 2.0 / SMART on FHIR for the FHIR API; site-configured credentials for HL7 interface connections
Change detection
HL7 interface feeds push event messages as they occur; the FHIR API is polled
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits and interface throughput agreements
How it works

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

    Choose tables

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

Adyen and eClinicalWorks 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 434 integrations available for Adyen and eClinicalWorks.

Popular · 8 of 434
All Adyen integrations All eClinicalWorks 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