Skip to content
Database ⇄ Accounting and finance

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

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

Work with Recurly'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 Plans, Invoices, Transactions, Line Items from Recurly 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 Recurly with validation, so the finance system stays the system of record.

Common use cases

  • 01 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 02 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 03 Use journal-based change capture to replicate IBM i data into a cloud warehouse for reporting.
  • 04 Keep customer and item files aligned with an ecommerce platform or modern ERP during phased modernization.

Common sync patterns

Query finance data like any other data

Customers, invoices, and payments from Recurly 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 Recurly.

Write back safely

Updates written to the synced tables in IBM AS/400 propagate into Recurly, so automations can create or correct finance records without custom integration code.

What you can sync between IBM AS/400 and Recurly

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.

IBM AS/400 objects Recurly objects How this pairing syncs
Libraries The schema-equivalent containers that scope which files a sync reads. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Libraries is specific to IBM AS/400 and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.
Physical files (tables) The Db2 for i tables mapped directly to sync targets. Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Physical files (tables) is specific to IBM AS/400 and Billing Info to Recurly — each maps to any object or custom field on the other side.
Logical files (views) Indexed or filtered views over physical files, usable as read sources. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Logical files (views) is specific to IBM AS/400 and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.
Members Sub-partitions of files in legacy applications, flattened or selected during syncs. Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. Members is specific to IBM AS/400 and Accounts to Recurly — each maps to any object or custom field on the other side.
Rows / records The unit of read and write, accessed via SQL or record-level access. Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. Rows / records is specific to IBM AS/400 and Subscriptions to Recurly — each maps to any object or custom field on the other side.
Journals and journal receivers The change log that enables log-based CDC on journaled files. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Journals and journal receivers is specific to IBM AS/400 and Plans to Recurly — each maps to any object or custom field on the other side.

How changes propagate between IBM AS/400 and Recurly

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.

IBM AS/400 Recurly 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 Recurly through its API, with automatic retries and rate-limit backoff.

Recurly IBM AS/400 Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

DeliveryEach detected change is applied to IBM AS/400 as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • IBM AS/400: Bounded by system resources and subsystem configuration rather than an API quota.
  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with IBM AS/400 ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your IBM AS/400 ⇄ Recurly sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between IBM AS/400 and Recurly.

How the IBM AS/400 and Recurly connectors work

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.

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

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

    Choose tables

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

IBM AS/400 and Recurly 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 IBM AS/400 and Recurly.

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