Skip to content
Accounting and finance ⇄ Database

Recurly to VoltDB integration — real-time, two-way sync

Keep Recurly and VoltDB 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 Recurly and VoltDB

Work with Recurly's financial data straight from VoltDB: 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 Accounts, Subscriptions, Plans, Invoices from Recurly into Partitioned Tables, Replicated Tables, Stored Procedures, Materialized Views in VoltDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against VoltDB, 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 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 03 Sync customer or account reference data from a CRM into VoltDB replicated tables for in-transaction lookups such as fraud or policy checks.
  • 04 Stream committed VoltDB results out through export targets into a warehouse for historical analysis.

Common sync patterns

Query finance data like any other data

Customers, invoices, and payments from Recurly live in VoltDB 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 VoltDB; Stacksync handles the API calls, rate limits, and retries against Recurly.

Write back safely

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

What you can sync between Recurly and VoltDB

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.

Recurly objects VoltDB objects How this pairing syncs
Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Partitioned Tables Tables sharded across partitions by a partitioning column; the primary transactional store and sync target. Invoices is specific to Recurly and Partitioned Tables to VoltDB — each maps to any object or custom field on the other side.
Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Replicated Tables Small reference tables copied to every partition, a common landing spot for synced lookup data. Transactions is specific to Recurly and Replicated Tables to VoltDB — each maps to any object or custom field on the other side.
Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Stored Procedures Precompiled transactional units that serve as the primary write interface. Line Items is specific to Recurly and Stored Procedures to VoltDB — each maps to any object or custom field on the other side.
Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Materialized Views Synchronously maintained aggregates over tables, useful as pre-computed read sources. Coupons and Redemptions is specific to Recurly and Materialized Views to VoltDB — each maps to any object or custom field on the other side.
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). Streams Insert-only constructs that feed the export subsystem with committed rows. Billing Info is specific to Recurly and Streams to VoltDB — each maps to any object or custom field on the other side.
Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Export Targets and Topics Connectors that push committed data to external systems such as Kafka or JDBC sinks. Measured Units and Usage is specific to Recurly and Export Targets and Topics to VoltDB — each maps to any object or custom field on the other side.

How changes propagate between Recurly and VoltDB

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.

Recurly VoltDB 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 VoltDB as a row-level write, with types converted between the two schemas.

VoltDB Recurly Interval-based propagation

DetectionStacksync polls VoltDB for changes on an incremental schedule, reading only records changed since the previous pass. Export streams and topics push committed changes to configured targets.

DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • 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.
  • VoltDB: No API rate limits; throughput is bounded by partition count and cluster sizing.
What ships with Recurly ⇄ VoltDB

Connect Recurly and VoltDB for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Recurly or VoltDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Recurly or VoltDB 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 Recurly or VoltDB record.

Observability

Monitoring

Track your Recurly ⇄ VoltDB sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Recurly and VoltDB.

How the Recurly and VoltDB connectors work

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.

VoltDB

Integration surface
SQL over JDBC plus native client libraries and an HTTP/JSON interface
Authentication
Database credentials
Change detection
Export streams and topics push committed changes to configured targets; otherwise polling
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by partition count and cluster sizing.
How it works

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

    Choose tables

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

Recurly and VoltDB 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 440 integrations available for Recurly and VoltDB.

Popular · 6 of 440
All Recurly integrations All VoltDB 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