Skip to content
Accounting and finance ⇄ ERP

Adyen to Epicor ERP integration — real-time, two-way sync

Keep Adyen and Epicor ERP 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 Epicor ERP

Keep Adyen and Epicor ERP agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.

A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.

Stacksync syncs Modifications (Captures, Refunds, Cancels), Payment Links, Merchant Accounts, Stores in Adyen with Jobs, Quotes, AR invoices, Shipments in Epicor ERP in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 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.
  • 02 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.
  • 03 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
  • 04 Push won opportunities from the CRM into Epicor as sales orders and sync order status back.

Common sync patterns

One customer and vendor master

Where both systems keep records of the same organizations, corrections made in either propagate to the other.

Subsidiary to headquarters

Where Adyen serves a business unit and Epicor ERP is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

Where Adyen handles billing: invoices land in Epicor ERP

Invoices and payment activity from the billing side post through to the enterprise system automatically.

What you can sync between Adyen and Epicor ERP

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 Epicor ERP 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. Suppliers Vendor masters kept aligned with procurement and AP automation tools. Merchant Accounts is specific to Adyen and Suppliers to Epicor ERP — 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. Parts Item masters that anchor inventory, BOM, and order line syncs. Stores is specific to Adyen and Parts to Epicor ERP — 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. Sales orders Created from won CRM opportunities; status and line changes sync back out. Users and API Credentials is specific to Adyen and Sales orders to Epicor ERP — 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. Purchase orders Synced with procurement systems and matched against receipts. Webhook Configurations is specific to Adyen and Purchase orders to Epicor ERP — 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. Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. Settlement Detail Reports is specific to Adyen and Jobs to Epicor ERP — 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. Quotes Estimates that pair with CRM opportunities during the sales cycle. Payments is specific to Adyen and Quotes to Epicor ERP — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Epicor ERP

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

Epicor ERP Adyen Interval-based propagation

DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.

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.
  • Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
What ships with Adyen ⇄ Epicor ERP

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Epicor ERP

Integration surface
REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
Authentication
API key combined with basic or token authentication, depending on version and deployment
Change detection
Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments
How it works

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

    Choose tables

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

Adyen and Epicor ERP 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 505 integrations available for Adyen and Epicor ERP.

Popular · 8 of 505
All Adyen integrations All Epicor ERP 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