Stripe revenue.
Reconciled automatically.
Connect Stripe in 2 minutes. Fairview reads your revenue data — calculates MRR, tracks refunds, detects churn signals, and feeds your margin calculation. Read-only restricted key. No engineering required.
MRR
$342K
+9.3% this month
Churn signals
2
flagged this week
Also connects with
From Stripe exports to reconciled revenue view.
Stripe alone — without Fairview
Total volume
no MRR split
$1.82M
manual export
Refunds
not linked to margin
$4.2K
manual export
Active subs
no churn signal
412
- MRR requires manual calculation from raw Stripe data
- Refunds not visible in your operating view
- Churn signals require manual subscription review
- Revenue not connected to cost or margin data
- Finance reconciliation done in a separate spreadsheet
Stripe + Fairview — auto-reconciled revenue
MRR
$342KRefunds (% MRR)
1.2%Churn signals
2 flagged- MRR calculated automatically from Stripe subscription data
- Refunds surfaced as a percentage of MRR in operating view
- Churn signals flagged weekly — cancellations, failed retries
- Revenue feeds directly into margin calculation (with QuickBooks/Xero)
- Weekly Operating Report includes revenue movement every Monday
Stripe in. Revenue view out.
Add restricted API key
Stripe restricted key
rk_live_••••••••••••••••
Developers → API keys → Restricted keys
STEP 01
Create restricted key — 2 minutes
In Stripe, go to Developers → API keys → Restricted keys. Create a read-only key for charges, subscriptions, and customers. Paste it into Fairview Settings → Integrations → Stripe.
Fairview calculates revenue + margin
STEP 02
Revenue calculated automatically
Fairview normalises Stripe subscription data into MRR, tracks refunds as a percentage, and feeds the revenue side of your margin calculation. Pair with QuickBooks or Xero for full contribution margin.
Churn signals surfaced weekly
Churn signal — 2 cancellations
AlertEstimated MRR impact: -$4.8K. Review retention actions.
Refund rate elevated
Watch1.2% of MRR — above 0.8% threshold. Review this month.
STEP 03
Churn signals in your inbox Monday
Cancellations, failed payment retries, and elevated refund rates — surfaced in your Weekly Operating Report with MRR impact estimates every Monday before 8am.
Read-only. Zero risk to your payments.
Fairview uses a restricted read-only key — it can only read the data types you grant access to. It never initiates charges, refunds, or any write operations. Your Stripe account is untouched.
What Fairview reads from Stripe
- Monthly recurring revenue (MRR)
- One-time charges
- Refunds
- Subscription events (upgrades, downgrades, cancellations)
- Customer churn signals
- Payment metadata
Restricted read-only key — never writes to Stripe
MRR breakdown · April
Net: $342K
Churn signal detection active
2 cancellations · -$4.8K MRR impact · Actions in Weekly Report
Three steps. Two minutes.
Create restricted API key
In Stripe, go to Developers → API keys → Restricted keys. Create a read-only key with access to charges, subscriptions, customers, and refunds.
Read-only — no write permissions required
Paste into Fairview
In Fairview, go to Settings → Integrations → Stripe. Paste your restricted key. Revenue fields are mapped automatically.
Takes under a minute
Revenue synced overnight
Fairview pulls your charge and subscription data. By Monday morning, your revenue view and churn signals are live in the Weekly Report.
First report: next Monday 7am
Four features. One Stripe connection.
Operating Dashboard
$342K
MRR · +9.3% growth
MRR, growth rate, and revenue movement in one operating view.
Margin Intelligence
Revenue
side connected
Pair with QuickBooks or Xero
for full contribution margin
Revenue side of your margin model — connect QuickBooks for costs.
Churn Signals
2
detected this week
Cancellations, downgrades, and failed retries flagged with MRR impact.
Weekly Report
MRR: $342K (+9.3%)
2 churn signals
Refunds: 1.2% MRR
Revenue movement, churn signals, and refund flags — delivered every Monday.
FAQ
Stripe-specific. No fluff.
Does Fairview need my full Stripe API key?
No. Fairview uses a restricted read-only API key. Stripe lets you create keys with only the permissions required — Fairview only needs read access to charges, subscriptions, customers, and refunds. Your full secret key is never required.
Does Fairview read Stripe invoices sent outside Stripe?
No. Fairview only captures revenue processed through Stripe. Invoices sent manually or collected through other payment processors are not included in the revenue view.
How does Fairview calculate MRR from Stripe data?
Fairview reads active subscription amounts from Stripe and normalises them to a monthly value. Annual plans are divided by 12. One-time charges are excluded from MRR and shown separately as non-recurring revenue.
What counts as a churn signal in Fairview?
Fairview flags subscription cancellations, downgrades, and failed payment retries in Stripe as churn signals. These are surfaced in the Weekly Operating Report with subscriber counts and estimated MRR impact.
Does Fairview write anything back to Stripe?
No. Fairview is read-only. It reads your revenue data from Stripe to power the operating dashboard, margin calculation, and churn signal detection. Nothing is ever written back to your Stripe account.
How often does Fairview sync with Stripe?
Daily by default. Fairview pulls the latest charge, subscription, and refund data overnight so your revenue view is current every Monday morning. The Scale plan offers more frequent syncs.
Pairs with the rest of your stack.
Connect Stripe. Revenue reconciled automatically.
MRR calculation, churn signal detection, refund tracking, and margin contribution — all from one restricted read-only key. No engineering.
14-day free trial · No credit card · Restricted key · Read-only