Skip to content
Accounting and finance

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

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

Keep the customer, invoice, and payment records that Pigment and Recurly share consistent in real time, whether the two systems split your finance stack or one is replacing the other.

Two finance systems in one company usually means one of two setups. Either the systems divide the work, with one issuing invoices or serving a business unit while the other holds the books, or one is on its way out and both must stay accurate during the transition. In both cases, the customer, invoice, and payment records the two systems share start to drift the moment updates are keyed twice or moved by hand.

Stacksync syncs Data imports, Users and permissions, Applications, Metrics in Pigment with Subscriptions, Plans, Invoices, Transactions in Recurly bi-directionally and in real time. A record created or corrected in either system appears in the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most at close. When both systems agree on who was billed, what was paid, and what is outstanding, reconciliation stops being a hunt for which copy of the truth is current.

Common use cases

  • 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • 03 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.
  • 04 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.

Common sync patterns

Payment status everywhere

A payment applied in one system updates the matching invoice in the other, so no one chases a balance that was already settled.

Entity or business-unit roll-up

Where each system serves a different entity or unit, sync the shared records so group-level reporting starts from consistent data.

Where Pigment issues invoices and Recurly holds the books

Invoices and payments recorded on the billing side land in the system of record automatically, so revenue is captured once and correctly.

What you can sync between Pigment 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.

Pigment objects Recurly objects How this pairing syncs
Applications Planning models organized by domain such as finance, sales, or workforce Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Applications is specific to Pigment and Transactions to Recurly — each maps to any object or custom field on the other side.
Metrics Multidimensional values holding plans and actuals; the main target for inbound data Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Metrics is specific to Pigment and Line Items to Recurly — each maps to any object or custom field on the other side.
Dimension lists Master data like accounts, products, or employees that metrics are sliced by Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Dimension lists is specific to Pigment and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.
Tables Row-based transactional data loaded into models from source systems 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). Tables is specific to Pigment and Billing Info to Recurly — each maps to any object or custom field on the other side.
Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Scenarios is specific to Pigment and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.
Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model 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. Data imports is specific to Pigment and Accounts to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Pigment 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.

Pigment Recurly Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

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

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

Rate-limit considerations

  • Pigment: Subject to the platform's API rate limits.
  • 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 Pigment ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Pigment and Recurly connectors work

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits

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 Pigment 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 Pigment 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
    Pigment connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Pigment 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 406 integrations available for Pigment and Recurly.

Popular · 8 of 406
All Pigment 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