Stripe Connect Setup

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

Start with Setup → Connect Stripe. Use Settings → Integrations → Stripe later to manage the connection and its history.

What Stripe powersCopy Anchor Link

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 requirementsCopy Anchor Link

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

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

Authorizing Stripe connects billing data; it does not install payment actions in your app. After Install and deploy, complete Setup → Payment connection with your developer or coding agent. They can reuse or extend your existing payment webhook; create a new endpoint only if no suitable one exists. See Verify Payments.

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

Connect StripeCopy Anchor Link

1. Open Setup → Connect Stripe and select Connect Stripe.
2. Authorize the Stripe account that sells your app's plans.
3. Return to Setup and check the merchant shown is correct.
4. Wait for the products and prices import to finish. Progress updates automatically; you can work on App address and Environment values while it runs.
5. If the import fails, select Retry catalog import. Customer and activity history can continue importing in the background.

This step is complete when Stripe is connected and its required catalog import is verified. Authorization alone is not completion. If an import finishes without the products or prices your app needs, check the connected merchant and its catalog before proceeding.

Use Change account only when you intend to replace the merchant. Replacing the connection can require catalog and payment verification again. Do not reconnect just to dismiss an import error.

Add account metadataCopy Anchor Link

Billing events are most useful when Stripe objects can attach to a SaaSFunnels 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.

Billing and trial factsCopy Anchor Link

When Stripe is connected, SaaSFunnels 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 importCopy Anchor Link

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 dataCopy Anchor Link

After setup:

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

Common problemsCopy Anchor Link

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.

Related articlesCopy Anchor Link

• Billing
• Results
• Event Log and Payload Review
• Troubleshooting