How to Record Stripe Dashboard Walkthroughs

A developer who publishes a clean five-minute Stripe Checkout integration video gets ranked above the official Stripe docs in YouTube search. The companies that sponsor those videos pay 1,000-plus dollars per slot because the audience is high-intent: a developer searching "Stripe Checkout tutorial" is shipping a payment feature this week. Recording the Stripe Dashboard walkthrough that drives that signup, that ad slot, or that consulting lead is craft worth getting right.

This guide is for the developer, indie hacker, founder, or technical content creator who needs to record Stripe Dashboard tutorials that protect API keys, stay in Test mode end-to-end, and ship the production value the developer audience expects.

Quick Comparison

---

Use Cases Where Recording the Dashboard Beats a Live Walkthrough

Recording Stripe Dashboard work makes sense in specific situations. The cases below benefit because the deliverable persists past one conversation, the audience is global and asynchronous, or the recording becomes a reusable asset across many tutorials, prospects, or team members.

Developer payment integration tutorials

The Stripe developer audience is the largest payment-integration developer audience on the internet. YouTube tutorials covering "Stripe Checkout in Next.js," "Subscription billing in Rails," or "Stripe Connect onboarding for marketplaces" pull six-figure annual view counts. A tutorial creator who publishes weekly builds inbound consulting leads, course sales, or sponsorship revenue.

Stripe Apps demos

The Stripe Apps platform (launched in 2022 and expanded through 2025) lets developers build embedded apps that run inside the Dashboard itself. Recording a Stripe Apps demo — install the app, walk through the embedded UI, narrate the value prop — is the marketing motion for app builders trying to get listed on the Stripe App Marketplace.

Billing setup tutorials for SaaS founders

A founder who just wired Stripe into their SaaS needs to set up products, prices, tax collection, and customer portal access. A 12-minute recorded tutorial covering the Billing tab end-to-end answers the question better than the docs because the docs do not show the Dashboard navigation in motion. This is the most common search-driven Stripe content on YouTube.

Stripe Connect platform demos

Connect powers marketplaces — Lyft, Instacart, Substack, Shopify. Recording the Connect onboarding flow, the platform Dashboard, the connected-account view, and the Express versus Standard versus Custom account-type tradeoffs is content for the marketplace-builder audience and consultants pitching Connect implementations.

Stripe Atlas tutorials for founders

Stripe Atlas helps non-US founders incorporate a Delaware C-Corp, set up a US bank account, and configure tax compliance for 500 dollars one-time. The audience is international founders bootstrapping into the US payment ecosystem. Recording the Atlas onboarding workflow is high-intent content with a narrow audience, and consulting and recruiting opportunities follow from publishing.

Internal team training on Stripe operations

Larger SaaS teams running Stripe at scale need finance and customer support trained on Dashboard workflows. Refunds, subscription pauses, dispute handling, payout schedules. A library of recordings replaces 15 hours of repeated training calls per new hire.

Method 1: macOS Screenshot Toolbar

The Stripe Dashboard runs entirely in the browser. The simplest Mac recorder is built into the OS. Press Command Shift 5, click "Record Selected Portion," draw a box around the Chrome window, and start.

For a 90-second internal demo or a quick capture of a specific Dashboard behavior to send to Stripe support, the built-in toolbar is enough. The output is a .mov file on the Desktop. Audio comes through whichever input macOS has set as default. The mouse pointer is captured visually unless you toggle the option off in the Options menu.

The constraints repeat from any browser-based Mac recording. No webcam, no auto-zoom on Dashboard's dense product/billing tabs, no captions, no editing beyond QuickTime trim, no sharing infrastructure. Files land on Desktop and you upload to Drive, GitHub Gists, Notion, or wherever the deliverable lives.

When to use the Screenshot Toolbar

Quick captures of a specific Dashboard issue. Internal demos for your own team. Throwaway recordings before a polished version.

When to skip the Screenshot Toolbar

Anything customer-facing where production value matters. Anything where you need viewer analytics. Anything that needs captions for an international developer audience.

Method 2: Screenify Studio

Screenify Studio is a Mac-native recorder built for cinematic captures without an editing pass. For the Stripe Dashboard, two features earn their place.

Auto-zoom on dense Dashboard tabs. The Products tab, the Customers tab, and especially the Subscription detail view stack 15-plus fields vertically with small labels and tightly packed metadata. On a 1080p compressed video, the metadata becomes illegible. Auto-zoom smoothly zooms to the field you click on and zooms back out, so the developer or founder watching on a 13-inch laptop sees what you are pointing at.

AI-generated captions in multiple languages. Useful for international developer audiences. Stripe ships in 50-plus countries; the developers consuming Stripe tutorials are global. Record once in English, generate Spanish, Portuguese, German, or Hindi captions, and ship the recording as multi-locale content. The captions are auto-generated and editable for Stripe-specific terms (webhook, idempotency, SetupIntent, PaymentMethod) that auto-transcription often mangles.

Pricing follows a freemium structure: the Free tier records without limits and exports 1080p with a watermark, up to five minutes per video. Pro (from 19 dollars per month, or 149 dollars one-time) removes the watermark and the export cap, and adds share-page branding — your own logo and name on the player, plus a custom domain for share links.

The tradeoff: Mac only. If the team or solo developer works on Windows or Linux, Screenify is not the answer. Loom and OBS are the cross-platform options.

When to use Screenify

Developer tutorials where production value matters. Consultant deliverables where brand matters. Mac-based content creators producing tutorial series for a Stripe-adjacent audience.

When to skip Screenify

Windows or Linux developers. Recordings done from a non-Mac shared workstation.

Method 3: Loom

The Stripe community uses Loom for asynchronous question replies, code review walkthroughs, and team-internal Dashboard demos. The pattern is well-established in the developer ecosystem and the friction-to-record is low enough that it competes with typing a response.

For Stripe-specific workflows, Loom shines in two places. First, the question-reply on Stripe Discord or Slack — a developer asks "why is my subscription not creating an invoice?", you record a three-minute Loom walking through Test mode and the subscription details panel, and the question is answered with the actual Dashboard on screen. Second, the team-internal Dashboard demo — the engineering team needs to understand a new billing flow, you record once and post in the team Slack channel.

The free plan caps recording length and library size, which is enough for ad-hoc replies but not for a full tutorial production workflow. The paid Business plan lifts those caps and adds viewer analytics.

Loom does not produce the cinematic look of Screenify or the multi-source flexibility of OBS. It produces the speed of one click to record, one click to share. For developer Q-and-A and team-internal communication, that speed is the feature.

When to use Loom

Cross-platform developer teams. Quick Q-and-A replies on Stripe Discord, GitHub issues, or community forums. Team-internal demos where speed beats polish.

When to skip Loom

YouTube tutorial production where production value matters. Long-form integration tutorials where a code editor and terminal need to be in frame alongside the Dashboard.

Method 4: OBS Studio (Multi-Source Integration Tutorials)

OBS Studio is free, open source, and built for streamers and broadcasters. For Stripe recordings, OBS earns its place when the tutorial requires the Dashboard, a code editor, and a terminal in frame at the same time — which is required for any full payment-integration tutorial.

The multi-source setup that works for integration tutorials:

• Source 1. Browser window with the Stripe Dashboard in Test mode
• Source 2. Code editor (VS Code, Cursor, Vim) with the Stripe SDK code being written
• Source 3. Terminal running stripe listen --forward-to localhost:3000/webhook for webhook testing
• Source 4. Browser tab with the application's checkout page, where the test payment will be made
• Source 5. Webcam in the corner for face-to-camera narration

OBS lets you switch between layouts, fade between sources, and apply chroma-key on the webcam. The output is a clean broadcast-style video showing the developer writing the integration code, watching the webhook fire in the terminal, seeing the event appear in the Stripe Dashboard, and confirming the payment succeeded — all in one frame.

The downside is setup time. The first OBS recording takes 30-plus minutes to configure. The hundredth takes two minutes. If you publish weekly Stripe tutorials to YouTube or run a developer livestream, OBS pays off. If you record one tutorial per quarter, the configuration time outweighs the polish gain.

When to use OBS

Full payment integration tutorials with Dashboard, code, and terminal on screen. Live streams covering Stripe development. Long-form tutorial series for developers and indie hackers.

When to skip OBS

Single-source Dashboard walkthroughs. Quick team-internal demos. Anywhere the recording is one-off and the OBS configuration time outweighs the polish gain.

Pre-Record Checklist: Test Mode On, Sample Data Ready, Keys Hidden

A recording of the Stripe Dashboard with live API keys visible or real customer data on screen is one of the worst privacy failures possible in a developer tutorial. Treat any Stripe recording as semi-public from day one and run the pre-record checklist before hitting record.

Toggle Test mode ON. Confirm the toggle. Confirm again. This is the single most important step. The Test mode toggle lives in the upper right of the Dashboard. When Test mode is active, every page shows an orange banner reading "Test mode" and the URLs include /test/ as a path segment. Real customer data, real charges, and real bank transfers cannot appear in Test mode by definition. Record exclusively in Test mode unless you have a specific reason not to and have triple-checked that no real data is on screen.

Create test products and prices. A fresh Test mode is empty. Before recording, create a few test products (Premium Plan, Starter Plan, Add-On) and the prices attached to them. Use realistic but obviously-fake names. Avoid product names that match real merchants you have worked with.

Generate test customers and payment flows. Use Stripe's test card numbers — 4242 4242 4242 4242 for the standard success card, 4000 0027 6000 3184 for 3D Secure required, 4000 0000 0000 9995 for insufficient funds. Run through a full payment flow in Test mode before recording so the Customers and Payments pages have realistic test data populated.

Redact API keys completely. API keys live in the Developers, API Keys section. Test keys start with sk_test_ (secret) and pk_test_ (publishable). Live keys start with sk_live_ and pk_live_. The sk_test_ prefix should never show in a recording — even Test secret keys can be used to create test data on the recorder's account, which other developers could exploit. In tutorials, reveal Test publishable keys only (the pk_test_ prefix) and use environment variable references for everything else.

Use environment variables in code. When recording integration tutorials, never paste raw API keys into the code editor. Use .env files with STRIPE_SECRET_KEY=sk_test_... and reference them as process.env.STRIPE_SECRET_KEY. The .env file content can be hidden from the recording, and the code shows only the variable reference.

Hide notification panels and developer tools. The Dashboard has a notification dropdown in the upper right and a Developers menu with logs and webhooks. Close any open panels before recording. The cleaner the canvas, the more the viewer focuses on the workflow.

Set browser zoom to 100 percent. The Dashboard renders at the browser zoom level. Recording at 90 or 110 percent produces inconsistent rendering. 100 percent is the standard.

Sign out of personal Stripe accounts. If the recording is for a tutorial channel and your Dashboard shows your real account name, your real business name, or your real merchant categorization, switch to a dedicated tutorial Stripe account before recording.

Common Recording Scenarios

The Stripe scenarios that warrant recording, ranked by frequency in tutorial and consultant workflows.

Checkout integration tutorial

The most common Stripe tutorial topic. Open the Dashboard, create a product and price in Test mode, copy the Price ID, switch to the code editor, write the Checkout Session creation code, deploy to a local development server, run a test payment with the 4242 card, and watch the payment land in the Dashboard. Total recording time is 8 to 15 minutes for a complete walkthrough.

Subscription billing setup

Open the Billing section, click Products, create a recurring product with a monthly price, navigate to the Customer portal, configure the portal settings, and walk through a test subscription creation in the Dashboard plus the customer-facing checkout. The recording is high-value for SaaS founders setting up their first subscription billing.

Webhook configuration

Open the Developers, Webhooks section, click Add endpoint, paste the local development URL (or the deployed production URL), select the events to subscribe to (payment_intent.succeeded, customer.subscription.created, invoice.paid), narrate the signing secret usage, and run a test event from the Dashboard. The recording is a developer staple and ranks well in YouTube search for "Stripe webhook tutorial."

Stripe Connect onboarding

Open the Connect section, navigate to the platform Dashboard, choose Express, Custom, or Standard account types, walk through the connected-account onboarding flow with a test account, and show the platform-side view of payouts and commissions. Marketplace builders search for this content heavily.

Stripe Apps installation demo

Open the Stripe App Marketplace, find an app (or your own app being demoed), click Install, walk through the OAuth permission grant, and show the embedded app rendering inside the Dashboard. App developers ship this recording as part of the listing.

Tax setup walkthrough

Open the Tax section, configure tax registrations for the relevant jurisdictions, narrate the difference between Stripe Tax (calculation and collection) and the merchant's responsibility to file. Useful for SaaS founders dealing with EU VAT or US sales tax for the first time.

Sigma SQL queries

Sigma is Stripe's SQL data platform for power users. Open Sigma, write a query against charges or subscriptions, run the query, and walk through the results. The audience is data analysts and ops teams running Stripe at scale.

Atlas company formation demo for international founders

Open the Atlas application, walk through the C-Corp formation steps, the EIN application, and the bank account opening flow. Atlas costs 500 dollars one-time. The recording is high-intent content for the international founder audience and consultants helping non-US founders incorporate.

Privacy: Test Mode is Non-Negotiable, API Keys Are Sacred

The Stripe Dashboard recording rule that prevents 95 percent of privacy incidents is binary: Test mode toggle ON, every recording, no exceptions.

The reasons go beyond customer data leaks. Live mode contains real charges, real customer payment methods, real bank account numbers (in the form of last-4 digits and bank names), and real transaction amounts that, taken together, tell a story about merchant revenue that the merchant probably has not consented to share. A tutorial creator who records on live mode "just for screenshots" is one accidental click away from publishing actual customer data on YouTube.

The API key rule is similarly binary: test publishable keys (pk_test_) are recordable; everything else is not. Even Test secret keys (sk_test_) should not appear in a recording. The reasoning:

• A pk_test_ key is meant to be in client-side code and is publicly distributable by design. Recording it is fine.
• A sk_test_ key gives anyone with access the ability to create test charges, customers, and webhooks on your account. Other developers using your account for test data is annoying; the reputational damage from "tutorial creator leaks API keys" is significant.
• A pk_live_ or sk_live_ key is a critical security incident if leaked. Live secret keys can drain real money from connected accounts and create real charges. Live publishable keys are less catastrophic but still let attackers craft phishing flows that look legitimate.

The rotation procedure if a key leaks:

1. Open Developers, API Keys.
2. Roll the leaked key immediately.
3. Update every deployment that referenced the old key.
4. Audit recent activity on the Dashboard for unauthorized usage.
5. Document the incident in your team's security log.

The discipline is small. The downside of getting it wrong is large. Always Test mode, always environment variables, always pk_test_ only in frame.

Stripe's Developer Focus and the Tutorial Economy

Stripe's growth has been a developer-focus case study since the company's earliest YC days. The Stripe docs are the gold standard in API documentation. The Stripe blog publishes deep technical content. The company sponsors developer YouTube channels, conferences, and open-source maintainers. The downstream effect is a tutorial economy where independent creators producing high-quality Stripe content can build sustainable businesses.

The economics that work for Stripe tutorial creators:

Sponsorship slots. Channels covering payments, fintech, and indie SaaS pull sponsorship dollars from Stripe alternatives, payment processors, billing tools, and developer platforms. Mid-sized channels (50,000 to 200,000 subscribers) get 1,000 to 5,000-dollar sponsorship slots regularly.

Course sales. Tutorial creators with audience build paid courses covering full integrations — Stripe Checkout in Next.js, Subscription billing in Rails, Connect for marketplaces. Courses priced at 100 to 500 dollars sell to indie hackers and bootstrappers who need the deeper walkthrough beyond a YouTube tutorial.

Consulting leads. Inbound consulting work from founders who watched a tutorial and need help shipping their integration. Consultants converting at 200 to 400 dollars per hour close engagements that pay back the tutorial production time many times over.

Stripe partnerships. Stripe runs a Verified Partners program that includes implementation consultants. High-output tutorial creators get visibility with the Stripe partnerships team and earn referral pipelines from Stripe sales.

Indie hacker forum and dev Twitter visibility. The Stripe-adjacent technical Twitter audience is small but high-conversion. A tutorial that lands on Hacker News drives 10,000-plus views in a day. The downstream impact on consulting inbound, course sales, and audience building is significant.

The pattern that works: niche down to a specific stack (Next.js plus Stripe, Rails plus Stripe, Django plus Stripe), publish weekly, and build the library that ranks for the long-tail searches. Generic "Stripe tutorial" videos compete with the official Stripe docs. Specific "Stripe Checkout in Next.js 15 with App Router and Server Actions" videos win the niche.

For the broader developer-content production framework, see best screen recorder for product demos and the SaaS-specific framing in screen recording for SaaS onboarding.

Sharing: Where Stripe Recordings Go

The distribution channels that work for Stripe-related recordings differ by audience.

Stripe community forums and Discord. The unofficial Stripe Discord has thousands of active developers asking integration questions in real time. A recording answering a question with the actual Dashboard on screen, instead of a paragraph, gets the answer marked as solved more often.

YouTube payment integration niche. The dedicated channel for tutorial content. Subscribers compound. Sponsorships and course sales follow.

Dev Twitter and indie hacker forum. A 60-second highlight clipped from a longer tutorial drives inbound. Indie Hackers as a forum surfaces tutorials with the right framing into the front-page feed.

GitHub issues and open-source maintainership. Recording a Loom showing exactly how to reproduce a bug attached to a GitHub issue moves the issue toward resolution faster than text descriptions.

Internal team docs in Notion or Linear. Engineering teams running Stripe at scale build internal libraries of recordings covering refund procedures, dispute handling, and webhook debugging. Replaces 10-plus hours per new hire of repeated training.

Sales decks for B2B platforms built on Stripe. Recorded Connect demos go in proposals to enterprise prospects. Static screenshots do not communicate the embedded onboarding flow; recordings do. For more on the sales motion see sales demo recording.

Step-by-Step: Record Your First Stripe Dashboard Tutorial

Concrete workflow you can run today if you have a Stripe account and a tutorial topic.

Step 1. Sign in to the Stripe Dashboard. Toggle Test mode ON in the upper right. Confirm the orange Test mode banner is showing. Confirm the URL contains /test/.

Step 2. Populate test data. Create a few test products and prices, run a test payment with the 4242 card, create a test customer, and trigger a test webhook event so the Dashboard tabs are not empty.

Step 3. Open the Dashboard in a clean Chrome profile. Set browser zoom to 100 percent. Close other tabs. Mute Slack and email notifications.

Step 4. Sketch the three to five points you want to make. Sticky note, text doc, anywhere. The note is the script.

Step 5. Open your recorder. macOS Screenshot Toolbar for quick captures, Screenify for polish, Loom for community Q-and-A speed, OBS for multi-source integration tutorials.

Step 6. Hit record. Open with the headline. "In this walkthrough, I will configure a Stripe Checkout session in Test mode and run an end-to-end payment."

Step 7. Walk through the steps on the sticky note. Click on the Dashboard section. Narrate the action. Show the result.

Step 8. Run a live test. Trigger the actual payment, the actual webhook, the actual customer creation. Show the event landing in the Dashboard.

Step 9. End with the next step or recommendation. "After confirming the test flow, switch to Live mode and run the same flow with a real customer. The integration code does not change between Test and Live."

Step 10. Stop the recording. Skip the editing session. Trim only the silent dead air at the head of the file.

Step 11. Generate captions if your audience includes non-English developers or if the recording will live on YouTube. Edit the auto-generated transcript for Stripe-specific terminology.

Step 12. Upload to Loom, Screenify, YouTube, or your community channel depending on the deliverable. Embed in the project documentation or post in the relevant Discord, Slack, or forum thread.

The whole loop takes 15 to 30 minutes for a workflow you have run before. Faster than typing the answer, more thorough than a paragraph in a forum reply, and the recording becomes a reusable asset across many future questions and tutorial series.

Troubleshooting

Common problems Stripe recorders hit and the fixes that work.

The Dashboard is laggy during recording. Accounts with large transaction histories or many connected accounts render slowly. Pre-load the page, let the network requests finish, then start recording. For unavoidable lag, take a screenshot-based approach for the worst-offending tabs — record the static image and narrate over it.

Test mode banner is not visible in the recording. Check the Test mode toggle is ON before every recording session. The orange banner is the only visual confirmation. If the banner is missing, you are recording on Live mode and must stop immediately.

API keys accidentally appear in the frame. Stop recording immediately. Roll the affected key in the Developers, API Keys section. Re-record after confirming the new key is referenced via environment variables. Document the incident.

Captions miss Stripe terminology. Webhook, idempotency, SetupIntent, PaymentMethod, PaymentIntent, SubscriptionSchedule — auto-transcription mangles all of these. Edit the transcript before sharing. Five minutes of cleanup turns unreadable captions into searchable, accessible content.

The Stripe CLI terminal output is too small to read. Increase the terminal font size before recording, or use auto-zoom in Screenify to magnify the output during the moments it matters. A 14-point font in Terminal renders unreadable in a 1080p compressed video.

Webhook test events do not appear in the Dashboard during the recording. Stripe CLI webhook forwarding has a few-second latency. Wait for the event to land before narrating "and here is the event." Practice the timing before hitting record.

Connect onboarding flow shows real bank account fields. Use Stripe's test bank account numbers documented at stripe.com/docs/testing for the Connect onboarding demo. Test routing number 110000000 and test account number 000123456789 produce a valid test connection.

The recording shows a personal account name in the Dashboard header. Switch to a dedicated tutorial Stripe account, or use the in-Dashboard team workspace switcher to record from a generic test workspace. Personal account names should not appear in a published tutorial.

Atlas demo shows real personal information. If recording an Atlas demo, use anonymized form data — fake founder name, fake company, fake address. Atlas validates real submissions, so the recording shows the form-fill flow without actually completing the incorporation. Stop the recording before clicking Submit.

Audio quality is poor. The MacBook's internal mic captures laptop fan noise and keyboard taps. Use AirPods Pro, a Shure USB mic, or any wired headset. Acoustically dampened rooms beat the open kitchen table.

The recording is too long. Most Stripe tutorials benefit from being five to twelve minutes, not twenty. If a draft runs eighteen minutes, find the seven minutes that carry the integration insight and re-record that segment.

FAQ

Can I record in Live mode if I redact carefully?

Strongly discouraged. Live mode contains real customer data, real bank information, and real transaction amounts. Test mode covers every workflow you would record in a tutorial, including subscription billing, webhooks, Connect onboarding, and Stripe Apps. There is no good reason to record on Live mode for a tutorial.

Are test API keys safe to show on screen?

Test publishable keys (the pk_test_ prefix) are designed to be public and are safe to show. Test secret keys (sk_test_) should not appear in recordings — they grant API access to your test account. Use environment variables for any secret key reference.

Can I record the Stripe Dashboard on Windows?

Yes. The Dashboard runs in any modern browser, so Windows recorders (OBS Studio, Loom, Snagit, Camtasia) work fine. The Mac-specific recommendations in this guide do not apply to Windows users; Loom and OBS are the cross-platform options.

How long should a Stripe tutorial be?

Three to six minutes for community Q-and-A replies. Eight to fifteen minutes for single-topic tutorials (Checkout, webhooks, subscriptions). Twenty-plus minutes for full-stack integration tutorials, ideally split into chapters.

What is Stripe Atlas and why record demos of it?

Atlas is Stripe's incorporation product for non-US founders, costing 500 dollars one-time for Delaware C-Corp formation. International founder audiences search heavily for Atlas walkthrough content because the product handles a high-stakes, one-time decision (incorporation), and seeing the workflow before purchasing reduces anxiety.

Can I publish recordings of past Stripe consulting work to win new clients?

Yes, with full anonymization. Replace any client identifiers, use a Test mode demo workspace instead of the client's actual account, and lead with the recording in your proposal. Recorded walkthroughs of past integrations outperform static screenshots in B2B sales materials.

Loom or Screenify for Stripe tutorials?

Loom for cross-platform speed and community Q-and-A. Screenify for Mac-only creators who want polished output and auto-zoom on Dashboard tabs. Many creators use both — Loom for ad-hoc replies in Discord and forums, Screenify or OBS for the polished YouTube tutorial.

What is Stripe Sigma and is it worth recording demos of?

Sigma is Stripe's SQL data platform, available as a paid add-on starting at 12 dollars per month per active subscriber-hour. The audience for Sigma tutorials is data analysts and finance teams running Stripe at scale, which is a smaller but high-intent audience than the developer tutorial niche.

How do I record a Connect onboarding flow without real bank info?

Use Stripe's documented test routing and account numbers (routing 110000000, account 000123456789). The test numbers produce a valid test connection without exposing real banking data.

Can I monetize Stripe tutorial content?

Yes. The most common revenue streams are YouTube ad revenue, sponsorship slots from payments-adjacent companies, course sales (100 to 500 dollars per course), and consulting leads from indie hackers and SaaS founders. Tutorial creators publishing weekly build sustainable businesses on the back of the Stripe developer audience.

Should I record Stripe Apps demos differently from Dashboard demos?

Stripe Apps render inside the Dashboard as embedded UIs, so the recording approach is the same. Capture the Dashboard window, narrate the embedded app, and call out the difference between the standard Dashboard navigation and the app's UI when relevant. For SaaS onboarding flows in general, the same pattern applies.