Showing your revenue without showing your customers.

The four ways people do this

Screen-share the dashboard on a call. Send a screenshot. Export a CSV. Add the person to your Stripe account as a team member. All four are in daily use and all four have the same two problems: they show much more than the question asked for, and they only work on the person looking at them right now.

That second one is the expensive part. The person on the call is rarely the person who decides. Whatever convinced them has to survive being described second-hand to a boss, a partner, or a procurement form — and “I saw his dashboard and it looked fine” does not survive that trip.

What a screen-share actually exposes

Open Stripe to make one point about MRR and the default views also carry individual customer names and email addresses, what each of them pays, who failed a payment this month, who disputed a charge, and who you refunded.

For most businesses that is other people’s data, held under terms that did not anticipate it being shown to a prospective customer. It is also, frequently, a competitor’s logo sitting in your customer list in front of someone who will recognise it.

If you do share a screen, open a single aggregate report first, put the browser in a clean window, and never scroll the payments or customers tabs. That reduces the exposure. It does not fix the second problem at all.

Stripe’s own read-only access, and why it fits badly

You can add someone to your Stripe account with a limited role, and for an accountant or a contractor that is exactly right. For an outsider asking a single question it is the wrong tool in three ways: they need a Stripe login, they get a view of the whole account rather than the one figure, and access persists until you remember to remove it. Most people do not remember.

It also still fails the forwarding test. Access granted to one person convinces one person.

Restricted keys: the right primitive

Stripe lets you create a restricted key scoped to read specific resources and nothing else. It cannot create charges, cannot issue refunds, cannot move money, and can be revoked from your dashboard without disturbing the live keys your product runs on.

That is what you give a service that turns billing into a published figure — not something you hand to a prospect. The distinction worth holding onto: a restricted key is how a tool reads your revenue, and the page it produces is what the outsider sees. What each kind of Stripe key can and cannot do, including how to scope one and how to revoke it.

The option that survives forwarding

A page. One link, readable by anyone you send it to, showing totals only — recurring revenue and active accounts — measured from your processor under a published counting rule and labelled with which processor it came from and when it was last read.

No customer names, because individual identities are never stored or published. No login for the reader. No access to revoke afterwards. And it keeps working when the person you sent it to pastes it into Slack for someone more senior, which is where the decision usually actually happens.

If the absolute number is the sticking point, it can stay private: figures can be turned off and the timeline still publishes the decisions, their dates, and what revenue did afterwards as a percentage. Growth stays checkable; the amount stays yours.

Which to use, plainly

An accountant or a new hire: a limited Stripe role. It is what it is for. A one-off conversation with someone you trust: a clean screen-share of a single aggregate view, nothing else open. Anyone evaluating you — a prospect, a partner, an investor, a journalist, a candidate — a link, every time. They will forward it, and it needs to work when they do.

Why the screenshot stopped working · the eight processors that can be read directly

Questions founders ask

Can I give someone read-only access to my Stripe account?

Stripe supports team members with limited roles, including view-only ones. It works, but it is the wrong shape for this job: it requires the other person to have or create a Stripe login, it grants a view of your whole account rather than one figure, and you have to remember to remove them afterwards. It is built for accountants and staff, not for a prospect who wants one question answered.

What does someone see if I screen-share my Stripe dashboard?

Far more than the revenue figure. The default views include individual customer names and email addresses, individual payment amounts, failed payments, disputes and refunds. For most businesses that is customer data you have a duty to protect, being shown to a third party to make a point that did not require it.

Is exporting a CSV from Stripe better?

It is worse for trust and often worse for privacy. A spreadsheet is editable by definition, so it proves less than a screenshot, and raw exports usually carry per-customer rows that you then have to strip by hand. If you send one, send an aggregate you have built deliberately — never the default export.

What about a restricted API key?

That is the right primitive, and it is what a verification service should ask for. A restricted key can be scoped to read one or two resources and nothing else, cannot move money, and can be revoked from your dashboard at any time without touching your live keys. It is not something to hand to a prospect directly — it is what you give a tool that turns it into a page.

Does Thonest see my customers?

No. Individual customer identities are never stored or published. What is read is what is needed to compute totals — recurring revenue and how many active accounts — and what is published is those totals. Your customer list is not in the page and could not be extracted from it.

Can I revoke access later?

Yes, from your own processor, without asking us. Revoking stops future readings. Measurements already taken stay on the record rather than disappearing, because a timeline that can be silently emptied is not evidence of anything — but nothing new is read once you have revoked.