Stripe

Connect billing and revenue

Stripe gives Health and Engine the billing evidence needed to explain how recurring revenue moved and which subscription or payment changes contributed. Connect it when the question begins with MRR, retention, churn, expansion, contraction, or failed payments.

Go to setup ↓

---

What this connection helps you answer

• What is driving MRR movement?
• Are failed payments creating revenue pressure?
• Which subscriptions, plans, or customer groups contributed most to growth or loss?
• Did product or reliability movement appear before the billing outcome?

Stripe metrics remain useful without another source. Product-to-revenue and reliability-to-revenue claims require enough identity coverage to connect the records safely.

Setup

1. In Stripe, open Developers > API keys.
2. Select Create restricted key.
3. Choose Providing this key to a third-party application.
4. Grant Read access to the resources listed below.
5. Enter the restricted key in Prolytics Connections.

Do not provide your Stripe Secret Key. Prolytics does not require write access to your connected Stripe account.

Required access

Path A: Quick Start (Recommended)

The fastest way to connect Stripe. This grants broad read-only access to your account data so Engine can access the data required for supported revenue analysis. We will never ask for Write access.

Why we need these permissions:

Under Resource type:

• Core: Allows Engine to analyse failed transactions and declined charges, and map Stripe billing entities back to product users or accounts.
• Billing: Allows Engine to calculate MRR, ARR, and churn from active subscriptions and the pricing catalog.

Path B: Strict Compliance (For Custom Security Protocols)

If your organization requires absolute least-privilege scoping, leave all parent categories as None and manually enable Read access for only the following exact endpoints:

Core Resources

• Charges and Refunds: Required at connection time and used by Engine to query payment history and run charge searches.
• Customers: Required at connection time for validation checks and used to look up customer records during investigations.

Billing Resources

• Subscriptions: Used to calculate MRR and ARR by reading your active subscriptions.
• Invoices: Used to pull invoice history for a customer when investigating billing questions.
• Prices: Used during discovery to build your pricing catalog, including product names, price IDs, and billing intervals.
• Products: Required alongside Prices to expand price objects to include the parent product name; without it, your pricing tiers will have no names.

What Happens After Stripe Is Connected

OS begins preparing the revenue, subscription, and payment metrics supported by your Stripe data. Calculations use the account's supported default currency. Amounts from other currencies are not silently combined into the same total, and zero-decimal currencies are handled using their correct units.

Stripe metrics can work independently. Connecting billing outcomes to PostHog behaviour or Sentry impact also depends on whether the same customer or account can be identified across those sources.

Missing identity coverage limits only cross-source comparisons. Stripe revenue, subscription, and payment analysis remain available.

Investigate an MRR decline ->