Skip to content
Accounting and finance ⇄ Database

Adyen to IBM AS/400 integration — real-time, two-way sync

Keep Adyen and IBM AS/400 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 IBM AS/400

Work with Adyen's financial data straight from IBM AS/400: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Payments, Modifications (Captures, Refunds, Cancels), Payment Links, Merchant Accounts from Adyen into Libraries, Physical files (tables), Logical files (views), Members in IBM AS/400 and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against IBM AS/400, and rows your code writes or updates flow back into Adyen with validation, so the finance system stays the system of record.

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 Expose AS/400 order, inventory, and item master data to modern SaaS tools without rewriting green-screen applications.
  • 04 Use journal-based change capture to replicate IBM i data into a cloud warehouse for reporting.

Common sync patterns

React to financial events

Changes in Adyen appear in IBM AS/400 as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

Customers, invoices, and payments from Adyen live in IBM AS/400 as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on IBM AS/400; Stacksync handles the API calls, rate limits, and retries against Adyen.

What you can sync between Adyen and IBM AS/400

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 IBM AS/400 objects How this pairing syncs
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. Physical files (tables) The Db2 for i tables mapped directly to sync targets. Users and API Credentials is specific to Adyen and Physical files (tables) to IBM AS/400 — 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. Logical files (views) Indexed or filtered views over physical files, usable as read sources. Webhook Configurations is specific to Adyen and Logical files (views) to IBM AS/400 — 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. Members Sub-partitions of files in legacy applications, flattened or selected during syncs. Settlement Detail Reports is specific to Adyen and Members to IBM AS/400 — 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. Rows / records The unit of read and write, accessed via SQL or record-level access. Payments is specific to Adyen and Rows / records to IBM AS/400 — 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. Journals and journal receivers The change log that enables log-based CDC on journaled files. Modifications (Captures, Refunds, Cancels) is specific to Adyen and Journals and journal receivers to IBM AS/400 — 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. Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. Payment Links is specific to Adyen and Data queues to IBM AS/400 — each maps to any object or custom field on the other side.

How changes propagate between Adyen and IBM AS/400

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 IBM AS/400 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 applied to IBM AS/400 as a row-level write, with types converted between the two schemas.

IBM AS/400 Adyen Sub-second propagation

DetectionChanges in IBM AS/400 are captured at the source via change data capture — no polling loop against its API. Journal-based CDC by reading journal receivers on journaled files.

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.
  • IBM AS/400: Bounded by system resources and subsystem configuration rather than an API quota.
What ships with Adyen ⇄ IBM AS/400

Connect Adyen and IBM AS/400 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–IBM AS/400 connection.

Real-time

Two-way sync

Changes in Adyen or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Adyen or IBM AS/400 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 IBM AS/400 record.

Observability

Monitoring

Track your Adyen ⇄ IBM AS/400 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 IBM AS/400.

How the Adyen and IBM AS/400 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.

IBM AS/400

Integration surface
SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access
Authentication
IBM i user profile credentials (database credentials)
Change detection
Journal-based CDC by reading journal receivers on journaled files; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Bounded by system resources and subsystem configuration rather than an API quota.
How it works

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

    Choose tables

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

Adyen and IBM AS/400 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 428 integrations available for Adyen and IBM AS/400.

Popular · 8 of 428
All Adyen integrations All IBM AS/400 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