Stripe's payment management console for developers and businesses

How to Record Stripe Dashboard

Record Stripe Dashboard in test mode without exposing real transactions. Guide for payment integration tutorials and webhook debugging recordings.

When you’d need to record Stripe Dashboard

Payment integration tutorials for developers

Record Stripe Dashboard alongside your code — show the checkout flow in test mode, verify the payment appears in the dashboard, check webhook delivery. The dashboard side of integration is half the tutorial.

Stripe setup walkthroughs for non-technical founders

Record how to configure Stripe — products, pricing, subscription plans, customer portal settings. Founders who set up Stripe for the first time need visual guidance through the 50+ settings pages.

Webhook debugging recordings for support

Record a webhook delivery failure — show the event, the endpoint, the response code, the payload. Share with your team or Stripe support instead of copy-pasting logs into a ticket.

Financial reporting walkthroughs

Record Stripe's Revenue, Balance, and Payout reports for your accounting team. Show where to find specific metrics, how to filter by date range, how to export CSV. Record once, reuse every month-end.

Recommended settings

Resolution

1920x1080

Frame rate

30fps

Audio

Microphone only

Capture mode

Custom Area

Things to know

•Stripe Dashboard shows real transaction amounts, customer emails, and payment method details (last 4 digits of cards)
•The sidebar shows test/live mode toggle — accidentally recording in live mode exposes real financial data
•API keys page shows publishable keys in full and secret keys partially — both are sensitive
•Webhook logs show endpoint URLs that reveal your server infrastructure

Step-by-step

1
In Screenify Studio, select Custom Area and drag the region over Stripe Dashboard.
Use Custom Area capture to exclude the sidebar — it shows account name, mode toggle, and links to every section.
2
Open Stripe Dashboard in Chrome. IMMEDIATELY check the test/live mode toggle (top left or sidebar). Switch to TEST MODE for any recording you'll share. Live mode shows real customer data, real transaction amounts, and real payment methods.
3
In test mode, create sample data if needed: Payments > + Create test payment. Stripe provides test card numbers (4242 4242 4242 4242) for this purpose. Demonstrate with test data, never live transactions.
4
Check the URL bar — it shows dashboard.stripe.com/test/... (test mode) or dashboard.stripe.com/... (live mode). The URL confirms your mode. If you see /payments without /test/, you're in live mode.
5
When navigating to Developers > API Keys, NEVER record this page in live mode. Even in test mode, be aware that test API keys are shown in full. If your tutorial is public, blur or crop the API key values.

Pro tips

Always record in test mode. This is not a tip, it's a rule. Stripe's test mode has identical UI to live mode with fake data. Toggle the switch before opening any page. Live mode exposes customer emails, card details, transaction amounts, and refund histories.

Auto-zoom on webhook event logs. Stripe's webhook log shows event type, endpoint URL, response code, and JSON payload in a compact list. When you click an event to inspect it, auto-zoom zooms in so viewers can read the `payment_intent.succeeded` payload structure — crucial for integration tutorials.

Custom area crop the sidebar. Stripe's sidebar shows your account name (potentially your company name), the test/live toggle state, and navigation to every section including Payouts, Balance, and Tax. Crop to the main content area to avoid exposing account context.

Create test data that tells a story. Don't record with empty test mode. Create 5-10 test payments, a test subscription, and a test refund before recording. Tutorials with realistic-looking (but fake) data are more educational than empty dashboards.

Common mistakes

Recording in live mode. You forgot to switch to test mode. Your recording shows 'Jane Smith, jane@company.com, $149.00, Visa ending 4242' — real customer PII and transaction data. Always verify test mode toggle before recording. The dashboard background color changes slightly between modes.

Showing API keys on screen. Developers > API Keys shows your publishable key in full and reveals the first/last characters of your secret key. In test mode this is lower risk, but in live mode it's a security incident. Navigate away from this page or blur it.

Showing webhook endpoint URLs. Developers > Webhooks lists your endpoint URLs: 'https://api.yourcompany.com/webhooks/stripe'. This reveals your server domain, API path structure, and that you use Stripe. Use custom area capture to exclude the endpoint column if sensitive.

Not explaining test mode to viewers. You record in test mode (correct!) but don't tell viewers that the data is fake. They think your startup made $0.50 in test transactions and wonder why you're making a tutorial. Verbally note: 'I'm in test mode — this is sample data.'