A Stripe dashboard for MRR, churn and sources
Paste a restricted, read-only Stripe key and Sumly reads every subscription and payment on the account: MRR, churn, refunds, fees and what reaches your bank.
What Sumly reads
- Subscriptions with their plans, trials, discounts and scheduled cancellations
- Every balance movement: charges, refunds, disputes and the fee Stripe kept
- The buyer's name and country on each payment
- The balance waiting to be paid out
Good to know
- A full secret key is refused; only a restricted key with read access is taken.
- The first read goes back three years and can take a few minutes on a busy account.
Connect Stripe in a few minutes
- 1In that project's Stripe: Developers → API keys → Create restricted key.
- 2Give it Read on Subscriptions, Balance and Charges (Products too, for plan names). Everything else: None.
- 3Paste the
rk_live_…key below. The first read takes up to three years of payments.
Trace each payment to its visit
Pass the sumly_vid cookie into Checkout as metadata named sumly_visitor_id, on subscription_data for plans and on payment_intent_data for one-off sales. Each payment then counts for the source, campaign and country of the visit that started it. How attribution works.
Questions
Can Sumly change anything in Stripe?
No. The key you give it can only read, and Sumly never asks for more.
Does it match Stripe's own MRR?
It follows the same rule: a subscription stops counting the moment its cancellation is scheduled, and discounts that are still running come off. Small gaps come from currency conversion, done at the European Central Bank's daily rate.
Other integrations
Try it with your own projects
Sumly opens to a few founders at a time. Leave your address and what you would connect; we write when your place is ready.
Or look around first: open the live demo.