Connect Stripe to Rig

    Sync your Stripe customers, subscriptions, invoices, charges and payment intents into Rig, so revenue questions run on your own billing data. Stripe connects with a restricted API key that can only read.

    Before you start

    • You need a Stripe user who can create API keys. Stripe asks for two-factor verification when the key is created.
    • Decide whether you want payouts and invoice payments. Those streams are off by default and need their own read permission.

    Step 1: Create a restricted Stripe key

    1. Open the API keys page in the Stripe Dashboard.
    2. Click Create restricted key.
    3. Enter a name in the Key name field, for example Rig.
    4. Set Read on each resource Rig syncs, which are customers, subscriptions, invoices, charges, payment intents, products and prices. Leave every other resource at None.
    5. Also set Read on events if you want deleted customers and invoices marked in your warehouse. Add payouts and balance transactions if you plan to turn those streams on.
    6. Click Create key, complete the two-factor check and copy the key. Stripe does not show it again.

    Use a restricted key
    A restricted key starts with rk_live_. Stripe recommends it over a secret key because it can only do what you allow, and a leaked key cannot create charges or trigger payouts.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Stripe, open the card and click Connect.
    3. Restricted API key: paste the rk_live_ key you created.
    4. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    5. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Stripe lands in its own stripe schema in your warehouse:

    • Customers: your customer records.
    • Subscriptions: subscriptions and their items.
    • Invoices: invoices and their lines.
    • Charges and payment intents: card and other payment attempts with their outcomes.
    • Products and prices: your catalogue.

    Payouts, payout balance transactions and invoice payments are off by default. Switch them on when you pick streams if you want cash-out and reconciliation data.

    Good to know

    • Rig reads Stripe's deletion events for customers and invoices. Deleted ones stay in your warehouse with their full data and a deleted marker, so history does not disappear.
    • A key created in a sandbox sees sandbox data only. Create the key in live mode for real revenue.
    • Write permission includes read, so a key set to Write on something works but gives Rig more than it needs.
    • To disconnect Stripe, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Track MRR and ARR from live subscription data
    • Analyse revenue retention and churn
    • Recover failed payments and reduce dunning loss
    • Monitor refunds and disputes

    More ideas for using Stripe

    Stripe documentation

    Was this guide helpful?