Stripe integration
Settled revenue, not reported revenue. Bring Stripe charges, subscriptions, refunds and churn into the same view as the spend that produced them.
- Setup time
- 2 minutes
- Access
- Read-only restricted API key or OAuth
- Sync
- Every 2 hours
Supported metrics
Standardized against every other connected source so cross-channel comparison is honest.
- Net settled revenue
- MRR and ARR
- Refund and dispute rate
- Trial-to-paid conversion rate
- Churn rate and net revenue retention
- Customer lifetime value
- CAC and CAC payback period
- LTV:CAC ratio by channel
- Profitable ROAS after refunds
Stripe and Paid Lens: product overview
Ad platforms report the revenue they were told about at checkout. Stripe knows what actually settled, what was refunded, what churned in month two, and what a customer is worth over their lifetime. Those are different numbers, and the difference is usually where the margin went.
Paid Lens connects to Stripe with read-only access and imports charges, subscriptions, invoices, refunds, disputes and plan changes. Joined to campaign attribution, this produces revenue figures that survive contact with a finance review.
For subscription businesses this is the connection that makes payback period and LTV:CAC real inputs to budget decisions instead of quarterly estimates.
See how Stripe data feeds the prioritized decision queue, how metrics are reconciled in attribution and metrics, or browse setup documentation.
What data is imported
Read-only, aggregated for analysis, and never written back to Stripe.
Charges and payments
Successful, failed and disputed payments with amounts and currency.
Subscriptions
Plan, MRR, billing interval, trial conversion and cancellation events.
Invoices
Invoice amounts, discounts and collection status.
Refunds and disputes
Refunded and charged-back amounts netted out of reported revenue.
Customers
Customer creation date and attribution metadata passed at checkout.
Products and prices
Plan structure used for cohort and tier-level analysis.
Common use cases
Measure payback period per channel
Paid Lens divides acquisition cost by the settled revenue each cohort actually produces, so you know which channels fund themselves and when.
Strip refunds out of ROAS
Channels with high refund or dispute rates stop looking profitable once the money that went back is netted out.
Compare channels on lifetime value
Cohorts from different sources are tracked over time, exposing channels that acquire cheap customers who churn fast.
Judge trial quality, not trial volume
Trial-to-paid conversion rate by source reveals which campaigns produce signups worth having.
What it looks like with Stripe connected
Product imagery is being finalized — these frames show the views this integration powers.
Why connect Stripe
Every connection raises the quality of the recommendations Paid Lens can make. Read more about how access is scoped and protected on our security page.
Paid Lens cannot change budgets, pause campaigns, or edit records. Tokens are encrypted and can be revoked at any time.
Settled revenue beats reported revenue
It is the only revenue figure that will not be argued with, and it is frequently lower than what the ad platforms claimed.
Subscription economics need time, not clicks
Payback and retention are the metrics that decide whether growth is sustainable, and only billing data contains them.
Read-only access
Paid Lens uses a restricted read key. It cannot create charges, issue refunds, or modify subscriptions.
Stripe integration FAQ
What access does Paid Lens need in Stripe?
A read-only restricted API key, or read-only OAuth. Paid Lens cannot create charges, refund payments, or change subscriptions.
How does Stripe revenue get attributed to a campaign?
Through metadata passed at checkout, matched customer records from your CRM, and UTM attribution captured at signup. Setup covers whichever of these your stack supports.
Is Stripe useful if I already connect a CRM?
Yes. The CRM knows what was booked; Stripe knows what was collected and what stayed. For subscription businesses the two figures diverge meaningfully.
Does Paid Lens store card or payment details?
No. No card data, PAN, or payment credentials are imported. Only aggregated transaction and subscription data is used.
More questions? Read what buyers usually ask or talk to us.
Related integrations
These pair well with Stripe and typically raise decision quality the most.
The connection that changes what gets optimized. Once HubSpot is linked, recommendations target revenue instead of conversions.
View integrationEnterprise pipeline, stage velocity and closed-won revenue by source — joined to media spend so marketing is measured the way finance measures it.
View integrationWhat happens after the click. Join GA4 sessions, channels and conversions to spend so landing pages and journeys become part of the decision.
View integrationImport Search, Shopping, Demand Gen and Performance Max data, then get a ranked queue of the changes worth making this week — each with the reasoning behind it.
View integrationConnect Stripe and get your first recommendations in 2 minutes
No credit card, no sales call, and nothing written back to your account. Connect, wait for the backfill, and read what Paid Lens thinks you should do first.