Two-way sync
Changes in Acumatica or Adyen instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica and Adyen in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Merchant Accounts, Stores, Users and API Credentials, Webhook Configurations in Adyen with Customers, Vendors, Sales Orders, Invoices in Acumatica 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.
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
Where both systems keep records of the same organizations, corrections made in either propagate to the other.
Where Adyen serves a business unit and Acumatica is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
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.
| Acumatica objects | Adyen objects | How this pairing syncs | |
|---|---|---|---|
| Payments Customer payment records reconciled against invoices from payment platforms. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Journal Transactions GL entries replicated into reporting databases. | 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. | Journal Transactions is specific to Acumatica and Users and API Credentials to Adyen — each maps to any object or custom field on the other side. | |
| Projects Project cost and billing structures synced with delivery tools. | 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. | Projects is specific to Acumatica and Webhook Configurations to Adyen — each maps to any object or custom field on the other side. | |
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | 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. | Opportunities and Cases is specific to Acumatica and Settlement Detail Reports to Adyen — each maps to any object or custom field on the other side. | |
| Customers AR master data synced with CRMs and billing tools. | 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. | Customers is specific to Acumatica and Modifications (Captures, Refunds, Cancels) to Adyen — each maps to any object or custom field on the other side. | |
| Vendors Supplier records aligned with procurement and AP automation. | 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. | Vendors is specific to Acumatica and Payment Links to Adyen — 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.
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
DeliveryEach detected change is written to Adyen through its API, with automatic retries and rate-limit backoff.
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 Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Adyen connection.
Changes in Acumatica or Adyen instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or Adyen data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Acumatica or Adyen record.
Track your Acumatica ⇄ Adyen sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and Adyen.
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 Acumatica and Adyen 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 Acumatica and Adyen 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 Acumatica and Adyen: authenticate both systems, choose the objects to sync (such as Acumatica's Payments and Journal Transactions), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Acumatica and Adyen: Migration without a hard cutover; One customer and vendor master; Subsidiary to headquarters. When one system is replacing the other, run both in parallel with records matching until the switch is complete.
Acumatica: Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries. Authentication: OAuth 2.0 or cookie-based session login with Acumatica credentials. 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. 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. Acumatica: The contract-based REST API uses versioned endpoints with a defined entity contract, so integrations pin an endpoint version and remain stable across upgrades. Stacksync's field mapping accounts for these differences between Acumatica and Adyen 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 Acumatica and Adyen records are not retained after a sync operation.
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 511 integrations available for Acumatica and Adyen.