Skip to content
Accounting and finance ⇄ E-commerce

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

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

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

Shipwire 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 Webhook Configurations, Settlement Detail Reports, Payments, Modifications (Captures, Refunds, Cancels) in Adyen with Products, Stock, Receivings, Returns in Shipwire field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Shipwire, 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 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.
  • 02 Provision Stores, Users, and API credentials through the Management API from an internal admin app or IdP so new locations and staff get the right Adyen access automatically.
  • 03 Sync Receivings (advance ship notices) and reconcile them against Purchase Orders so inbound supplier shipments are visible as they land.
  • 04 Pull Returns and tracking.delivered events into a support or analytics database for reverse-logistics and delivery-SLA reporting.

Common sync patterns

Where Shipwire originates orders: sales flow into the books

A new or updated order in Shipwire 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 Shipwire, 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 Shipwire

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 Shipwire 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. Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. Payments is specific to Adyen and Returns to Shipwire — 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. Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. Modifications (Captures, Refunds, Cancels) is specific to Adyen and Purchase Orders to Shipwire — each maps to any object or custom field on the other side.
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. Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. Payment Links is specific to Adyen and Trackings to Shipwire — 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. Rates Shipping cost quotes for a cart or order; read-only, called at checkout time to estimate carrier costs rather than synced as stored records. Merchant Accounts is specific to Adyen and Rates to Shipwire — 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. Orders B2C fulfillment orders (create, update, cancel, get) with item, hold, routing, and tracking subresources; typically written from a storefront or ERP and synced back with status and trackings. Stores is specific to Adyen and Orders to Shipwire — 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 Catalog SKUs including kits, virtual kits, and marketplace products; created and edited via API, commonly mastered in a PIM or ERP and pushed into Shipwire with dimensions and pricing. Users and API Credentials is specific to Adyen and Products to Shipwire — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Shipwire

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

Shipwire Adyen Sub-second propagation

DetectionShipwire notifies Stacksync of record changes through webhook events. Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics.

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.
  • Shipwire: No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
What ships with Adyen ⇄ Shipwire

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Shipwire

Integration surface
REST API (v3)
Authentication
Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com)
Change detection
Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream)
Capabilities
read · write · webhooks
Rate limits
No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
How it works

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

    Choose tables

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

Adyen and Shipwire 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 459 integrations available for Adyen and Shipwire.

Popular · 8 of 459
All Adyen integrations All Shipwire 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