How to Blur the Stripe Dashboard During Screen Sharing (Hide Customer Data, Revenue & API Keys)

The reliable way to demo or record the Stripe Dashboard is to blur the customer and revenue data directly in the page before you start sharing — so payment amounts, customer emails, payout totals and your live API keys are frosted out as real pixels the moment your feed goes live. Stripe has no built-in presenter mode, and switching to Test mode still leaves your account's structure and secret keys exposed. An in-page blur lets you walk through a real charge or a live report without putting a single customer or number on the call.

Because the blur is painted into the web page (not laid over your monitor), it survives Zoom, Google Meet, Microsoft Teams, Loom, OBS and even a screenshot someone takes of the shared feed. Nothing you blur ever leaves your browser. Here's exactly what to hide in Stripe, and how.

What's sensitive in the Stripe Dashboard

Almost every Stripe screen carries something you wouldn't hand to the room. The highest-risk areas:

• Payments list & the charge detail — each row shows the customer name and email, the payment amount, the card brand and last-4 digits, and the payment method. Opening a charge exposes the full timeline and billing details.
• Home & Balances — the top cards show gross volume, net volume, and often MRR; the balance panel shows your available and pending balance and your next payout amount and date.
• Customers directory — names, emails, total spend and saved payment methods, one search away.
• Disputes & Radar — dispute reasons, amounts and evidence, plus fraud flags, usually naming the customer.
• Developers → API keys — your publishable key, the Secret key (sk_live_…), any restricted keys, and webhook signing secrets. A live secret key on a recording is a credential leak.
• Reports & Payouts — payout totals, per-day settlement figures and your bank account last-4.

How to blur the Stripe Dashboard before you share

The whole flow with BlurFirst takes under a minute:

1. 1

   Share a single browser tab

   Present only the Stripe tab — keep your email, Slack and your terminal (where the Stripe CLI prints keys) out of frame.

2. 2

   Start BlurFirst on the page

   Open the Dashboard and press Ctrl/⌘ ⇧ Y (or click the toolbar icon) to bring up the control bar.

3. 3

   Box-blur the revenue and balance cards

   Drag a rectangle over the Home page's gross-volume and balance cards, and over the payout summary. The box stays anchored to that region as you scroll.

4. 4

   Element-blur customer rows and keys

   On the Payments list, click a customer email or an amount to frost just that cell. On Developers → API keys, click the Secret key value to hide it before the panel is on screen. Click again to reveal.

5. 5

   Let Scan sweep for PII (Pro)

   One click runs a local Scan that finds and blurs emails, card numbers, phone numbers and API-key patterns on the current page — useful before a Payments export or the keys panel is visible.

6. 6

   Keep the panic shortcut ready

   If you click into the wrong charge, press Ctrl/⌘ ⇧ H to blur the entire page instantly, fix the view, then reveal.

Isn't switching to Test mode enough?

Test mode helps, but it doesn't cover everything. Toggling to Test mode swaps live transactions for fake ones, so the Payments list is safe — but the Developers panel still shows your live secret and restricted keys, and your real business name, statement descriptor, bank last-4 and account settings persist across both modes. On top of that, most useful demos and support sessions need to show a *real* workflow — a genuine charge, a real payout, an actual dispute — which is exactly the data Test mode hides. Blurring covers what Test mode leaves exposed, and lets you present live data selectively.

Save a reusable Stripe blur profile

If you present from Stripe regularly, set the structural blurs once. BlurFirst Pro's per-site auto-apply re-applies your saved region blurs — the balance cards, the payout summary, the API-keys area — automatically each time you open the Dashboard, and they survive Stripe's single-page re-renders as you navigate. You only blur the record-specific cells per session. BlurFirst stores a CSS selector for each saved blur, never the content inside it.

One honest limitation

BlurFirst only affects content inside a browser tab — it can't blur your terminal, the Stripe CLI, or another window. That's why step one is sharing a single tab rather than your whole screen. Scan detects patterns (emails, card numbers, API keys), not free-text names — so for a customer's name, use element or box blur. A desktop app that covers native windows is in development.