Skip to content
Accounting and finance ⇄ E-commerce

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

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

Turn every Nuorder order into clean revenue: Adyen and Nuorder keep customers, orders, and payment status aligned in real time, in both directions.

Nuorder runs the storefront — the catalog, the orders, and the buyers placing them. Adyen records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.

Stacksync syncs Payment Links, Merchant Accounts, Stores, Users and API Credentials in Adyen with Pricing / Price Lists, Payments, Products, Orders in Nuorder field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Nuorder, its paid-or-overdue state from Adyen — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.

The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.

Common use cases

  • 01 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.
  • 02 Create Adyen Payment Links from an invoicing or billing system and sync each link's paid or expired status back so accounts receivable sees payment without opening the Customer Area.
  • 03 Push a brand's Products with pricing and images from a PIM or ERP into NuORDER via /api/product/new so the wholesale showroom and linesheets stay current each season.
  • 04 Sync Inventory / ATS levels from a warehouse or ERP into NuORDER via /api/inventory/{id} so buyers see accurate available-to-sell quantities and oversell drops.

Common sync patterns

Where Nuorder originates orders: sales flow into the books

A new or updated order in Nuorder creates or updates the matching invoice or revenue record in Adyen, so billing and reporting start without re-entry.

Where Adyen is the money system of record: payment status on the order

Paid, overdue, and refunded state from Adyen lands on the order or account in Nuorder, so the store and support see what has actually been collected.

One customer master

Where both systems keep customer or buyer records, an edit in either propagates to the other, ending duplicate accounts and mismatched contact details.

What you can sync between Adyen and Nuorder

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 Nuorder objects How this pairing syncs
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. Payments Payment status and detail returned alongside Orders (the modified-orders date-range query returns the order plus its payment information); read-oriented in most syncs. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
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. Pricing / Price Lists Wholesale and retail price data attached to products through the product data feeds; read out for margin reporting or written in during catalog loads. Stores is specific to Adyen and Pricing / Price Lists to Nuorder — 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 Fluent-schema catalog records (style, SKU, images, custom fields); brands push them in via /api/product/new (POST) and update via /api/product/{id} (PUT), typically mastered in a PIM or ERP. Users and API Credentials is specific to Adyen and Products to Nuorder — 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. Orders Wholesale sales orders with nested line items and payment info; read via /api/orders/{status}/detail, created via /api/order/new (PUT), and advanced via /api/order/{id}/process and /cancel. Webhook Configurations is specific to Adyen and Orders to Nuorder — 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. Companies Retailer and customer accounts (buyers, doors); enumerated via /api/companies/codes/list and created through the customer-creation API, commonly synced with a CRM or ERP. Settlement Detail Reports is specific to Adyen and Companies to Nuorder — each maps to any object or custom field on the other side.
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. Line Items SKU, quantity, and price rows nested inside each Order; the unit ERPs and fulfillment systems consume when an order is written out. Modifications (Captures, Refunds, Cancels) is specific to Adyen and Line Items to Nuorder — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Nuorder

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

Nuorder Adyen Interval-based propagation

DetectionStacksync polls Nuorder for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified date: a date-range order endpoint returns the IDs of orders changed within a UTC start/end window.

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.
  • Nuorder: Results are cursor-paginated via lastId/lastValue exposed in a 'next' response header (null on the last page); published request-rate limits are not documented and are governed per integration.
What ships with Adyen ⇄ Nuorder

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Nuorder

Integration surface
REST API (JSON), with optional SFTP flat-file data feeds
Authentication
OAuth 1.0 — consumer key/secret plus an access token/secret issued per approved application in the NuORDER Portal (Admin > Settings > API Management > Approved Applications)
Change detection
Polling on modified date: a date-range order endpoint returns the IDs of orders changed within a UTC start/end window; products and customers are pulled by last-modified date. No native webhooks.
Capabilities
read · write
Rate limits
Results are cursor-paginated via lastId/lastValue exposed in a 'next' response header (null on the last page); published request-rate limits are not documented and are governed per integration.
How it works

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

    Choose tables

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

Adyen and Nuorder 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
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 364 integrations available for Adyen and Nuorder.

Popular · 7 of 364
All Adyen integrations All Nuorder 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