Skip to content
Accounting and finance ⇄ ERP

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

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

Keep Adyen and Cin7 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 Stores, Users and API Credentials, Webhook Configurations, Settlement Detail Reports in Adyen with Sales orders, Purchase orders, Contacts, Branches / locations in Cin7 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 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 Keep customer records aligned between Cin7 and the CRM to remove duplicate account entry.
  • 04 Write purchase orders created in a planning tool back into Cin7 for receiving.

Common sync patterns

Where Adyen handles billing: invoices land in Cin7

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

Migration without a hard cutover

When one system is replacing the other, run both in parallel with records matching until the switch is complete.

One customer and vendor master

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

What you can sync between Adyen and Cin7

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 Cin7 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. Branches / locations Warehouse entities that scope every stock movement and order allocation. Payment Links is specific to Adyen and Branches / locations to Cin7 — 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. Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. Merchant Accounts is specific to Adyen and Stock adjustments and transfers to Cin7 — 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. Credit notes / returns Return documents synced so finance and support see the same refund state. Stores is specific to Adyen and Credit notes / returns to Cin7 — 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. Products SKU records with options and pricing, synced with storefront and marketplace catalogs. Users and API Credentials is specific to Adyen and Products to Cin7 — 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. Inventory levels Stock on hand by branch or location, published outward for availability. Webhook Configurations is specific to Adyen and Inventory levels to Cin7 — 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. Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. Settlement Detail Reports is specific to Adyen and Sales orders to Cin7 — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Cin7

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

Cin7 Adyen Sub-second propagation

DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.

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.
  • Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
What ships with Adyen ⇄ Cin7

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Cin7

Integration surface
REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
Authentication
API key credentials (paired with a username or account ID, depending on the product)
Change detection
Polling on modified-date filters; webhook support exists on some editions for order and stock events
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
How it works

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

    Choose tables

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

Adyen and Cin7 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 495 integrations available for Adyen and Cin7.

Popular · 7 of 495
All Adyen integrations All Cin7 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