Stripe Connect Setup

Connect customer billing data with Stripe Connect and verify monitored revenue context.

Stripe gives Prevenue billing truth for customer subscriptions, invoices, plans, trials, payment state, MRR, and billing events.

Open Settings > Integrations > Stripe to connect and manage Stripe.

What Stripe powers

Stripe can support:

Customer billing events in the Events pipeline.
Account MRR and plan context.
Metrics such as MRR, ARR, NRR, GRR, expansion MRR, contraction MRR, churned MRR, new MRR, active customers, and churn.
Payment-risk and billing-related account intelligence.
Historical revenue trend coverage.
Prediction-readiness improvements when billing context was missing.

Setup requirements

You need workspace admin access and permission to authorize Stripe Connect.

Prevenue uses Stripe Connect OAuth to create a per-workspace managed billing webhook. Stripe webhook secrets and OAuth credentials are stored server-side.

Customer Stripe integration is separate from Prevenue workspace billing. Connecting Stripe for customer data does not manage the Prevenue subscription for your workspace.

Connect Stripe

Open Settings > Integrations > Stripe.
Select Connect Stripe.
Complete the Stripe OAuth flow.
Return to Prevenue.
Open the setup guide and review the managed webhook endpoint.
Confirm the integration status moves to ready or connected.
Send or wait for a supported Stripe test event.
Review recent activity and Events.

Add account metadata

Billing events are most useful when Stripe objects can attach to a Prevenue account. Add account identity to checkout, invoice, customer, and subscription metadata where possible.

Recommended metadata keys:

metadata.account_id
metadata.account_key

Use the same stable account identifier you use in product events.

When Stripe is connected, Prevenue treats Stripe as authoritative for billing and trial facts such as subscription status, trial start/end, current billing period, cancel-at-period-end, MRR, ARR, currency, and payment risk.

Product sources such as Direct API, Web SDK, PostHog, or Segment can still send fallback account traits like signup date, plan labels, user counts, active users, and seat counts. If a product source and Stripe disagree on billing or trial state, fix the Stripe metadata/matching first rather than overriding billing state from browser or product events.

Historical import

Stripe setup can include historical billing import status. The integration page shows whether history is queued, running, imported, finalizing, completed, failed, or waiting.

Use retry for recoverable sync failures. Use resync when you intentionally want a fresh 12-month historical import and the action is available.

Verify Stripe data

After setup:

Open Settings > Integrations > Stripe and review status, last activity, issues, historical import status, and endpoint metadata.
Open Events and filter source by Stripe.
Open Accounts and confirm plan and MRR fields are populated for known accounts.
Open Results and confirm verified Funnel revenue can use Stripe-backed outcomes.
Review Stripe match, identity, and data-quality warnings in Setup, Events, and Accounts.

Common problems

If Stripe is connected but accounts do not show billing context, check metadata and identity matching first.

If metrics are locked, empty, or syncing, open Metrics and read the availability label on each card.

If historical sync failed, review the Stripe integration status and retry or resync only when the UI allows it.