Fintech Demo Video Guide: What to Show, Say and Disclose
Record in a sandbox with test cards and synthetic customers, then check the script for the words that turn a product walkthrough into a regulated financial ad.
By disha Sharma

A fintech demo video can get you into trouble in two ways a typical SaaS demo can't. The first is what's on screen: a real card number, a real balance, a real customer's name in a transaction feed. The second is what the narration says. One line like "earn 4.5% on your cash" or "your money is FDIC-insured" can turn a product walkthrough into a regulated financial ad.
Most advice covers the first problem only. This guide covers both.
The short answer: record every fintech demo in a sandbox with test card numbers and made-up customers, so there's nothing real to leak. Then go through the script line by line and mark every regulated claim: rates, payment amounts, "free", "insured", "returns". Each of those words comes with rules about what else the video has to say. Send the marked-up script to compliance before you record, not after you render.
| Risk | Example | What to do |
|---|---|---|
| Real card data on screen | A full 16-digit card number in an admin view | Processor test cards, shown masked |
| Real customer data | Names and amounts in a transaction feed | Synthetic customers in a demo account |
| Savings rate claim | "Earn 4.5% on idle cash" | Say "annual percentage yield" and add the required details |
| Loan terms | "Just $49 a month" | Add the down payment, repayment terms and APR |
| Insurance claim | "Your money is FDIC-insured" | Name the insured bank and get the wording approved |
| Investment claim | "Grow your portfolio faster" | Principal approval first if you're a FINRA member firm |
This covers US rules, and it's a product team's workflow, not legal advice. Your compliance team decides what applies to your product. The aim here is to hand them a script they can approve in one pass.
Part 1: What's on screen
Use test data your payment provider already publishes
The safest card number in a fintech demo is one that was never a real card. Payment providers publish test data for exactly this purpose:
- Cards: Stripe's testing docs list
4242 4242 4242 4242as the standard Visa test card, with any future expiry date and any three-digit CVC. - US bank accounts: Stripe's test routing number is
110000000, with account number000123456789. - Linked accounts: Plaid's sandbox signs in with
user_goodandpass_goodand returns simulated accounts.
Stripe's own rule is blunt: "Don't use real card details" when testing. Treat demo recordings the same way.
For people and contact details:
- Generate customers; don't edit a real export. Swapping names isn't enough. Amounts, dates and merchant names can still point to a real person.
- Use reserved phone numbers and domains. In North America, 555-0100 to 555-0199 are set aside for fictional use, and
example.comis reserved for documentation. - Make balances look lived-in. A demo account holding exactly $10,000.00 looks fake. $8,412.37 doesn't.
If no number on screen can pay for anything, there's nothing to leak.
Show card masking the way production does
PCI DSS requirement 3.4.1 says that when a card number is displayed, no more than the BIN (the first six or eight digits) and the last four digits may show, unless there's a documented business need to see more. The PCI Security Standards Council's FAQ confirms this applies to 8-digit BINs too.
That matters for video even when the number is a test card. If your demo shows a full 16-digit number in an admin screen, any viewer who knows PCI will wonder whether your real product does the same. Record screens that show •••• 4242, exactly as a live account would.
Your demo should look like production, masking included.
Lock down everything around the demo
Most leaks don't come from the demo screen. They come from everything around it.
- Use a separate browser profile with no saved logins or history for real customer dashboards. Autocomplete in the address bar is on camera too.
- Turn notifications off. A Slack preview with a customer's name is exactly the frame nobody catches live.
- Record one window, not the whole desktop. Close email, chat and the support inbox.
- Never show an API key, test or live. Crop the developer settings page or use a fresh key you revoke after recording.
Treat the recording computer as part of the sandbox: if it can show something real, assume it eventually will.
Prove security features exist; don't publish a playbook
Security is a selling point, so you'll want to show it. Show that it exists, not how it works under pressure.
- Show the two-factor prompt and a successful sign-in.
- Skip account recovery, how support verifies a caller's identity, and any limits that trigger a manual review ("transfers over $X are held"). Those details help fraudsters more than prospects.
- Narrate what the control does instead of clicking through every step.
A good rule: if a fraud team would redact it from a public help article, keep it out of the video.
Part 2: What the narration says
Once a video is public, it's marketing. Certain words in the script carry rules about what else must be said. Here are the four that come up most in fintech demos.
Savings rates: say "annual percentage yield"
Under Regulation DD, the Truth in Savings rule (12 CFR 1030.8), if an ad for a deposit account states a rate of return, it must state it as an "annual percentage yield", using that term. Any interest rate shown alongside it can't be more prominent than the APY.
Stating an APY then brings in more details, including:
- Whether the rate may change
- How long the APY is offered
- The minimum balance needed to earn it, and any minimum opening deposit
- That fees could reduce earnings
- For time accounts, the term and any early withdrawal penalty
Regulation DD lets TV, radio, billboards and telephone response machines leave some of these out. A demo video on your website or YouTube isn't on that list, so plan for the full set. The rule also bans calling an account "free" or "no cost" if maintenance or activity fees may apply.
Regulation DD applies to depository institutions. If your accounts are held at a partner bank, ask the bank's compliance team to approve the script before you publish.
There's also a practical problem: rates change. A video that says "4.10% APY" in the narration is out of date the day the rate moves. Keep the rate out of the voiceover and put it on one end card you can swap.
Loan and pay-later terms: one number brings three more
Regulation Z (12 CFR 1026.24) lists "triggering terms" for closed-end credit ads, such as installment loans:
- The amount or percentage of any down payment
- The number of payments or the repayment period
- The amount of any payment
- The amount of any finance charge
If your narration or on-screen text uses any of them, the ad must also state the down payment, the repayment terms over the full loan, and the "annual percentage rate", using that term, plus whether the rate can go up. Any rate you mention must be stated as an APR.
So "4 payments of $25" and "just $49 a month for 12 months" are triggers. "Split a purchase into smaller payments" isn't. Credit cards and other open-end credit have their own advertising rules elsewhere in Regulation Z, and whether a pay-later product counts as credit is a question for counsel.
The simplest compliant demo script describes how the product works and leaves specific terms to a disclosure screen your compliance team writes.
"FDIC-insured": the claim regulators act on
Section 18(a)(4) of the Federal Deposit Insurance Act and 12 CFR Part 328 ban presenting an uninsured product as insured, or misrepresenting how and how far a deposit is insured. That covers what you leave out, not only what you say.
The FDIC enforces this publicly. On August 19, 2022, it sent cease-and-desist letters to five companies for claiming that certain crypto-related products, or stocks held in brokerage accounts, were FDIC-insured.
For a demo video, that means:
- Never say your company is FDIC-insured unless it is an insured bank. Name the bank that holds the deposits, in wording compliance has approved.
- Don't let a badge on screen do the talking. An FDIC logo next to a crypto or investing tab implies coverage it doesn't have.
- Match production. The FDIC's January 2026 final rule requires banks to show the official digital sign on their homepage, login page and first account-opening screen, with compliance due by April 1, 2027, per Orrick's summary. Record from a build that already reflects that.
If you can't say exactly who is insured and for what, don't say "insured" at all.
Investing features: approval comes before the upload
If you're a FINRA member firm, Rule 2210 covers your videos. A registered principal must approve each retail communication before it's used or filed, whichever comes first. The content must be fair and balanced, and no communication may make a "false, exaggerated, unwarranted, promissory or misleading statement or claim". It also can't predict or project performance, or imply that past performance will recur, outside a few narrow exceptions.
Registered investment advisers fall under the SEC's marketing rule instead, so ask your chief compliance officer which applies.
Two lines that cause trouble in demos:
- The narration: "grow your money faster" or "beat the market" is a promise.
- The chart: a demo portfolio that only ever goes up implies performance, even with no words attached. Use mixed sample data and label it "Illustrative data, not real performance".
The chart says as much as the script, so it needs approval too.
The 5-step workflow
| Step | What you do | Who signs off |
|---|---|---|
| 1. Claims inventory | Highlight every rate, payment amount, "free", "insured" and performance word in the script | Product marketer |
| 2. Reuse approved wording | Copy disclosure language from materials compliance already approved | Product marketer |
| 3. Script review | Send the marked-up script and a list of screens you'll show | Compliance |
| 4. Record in the sandbox | Test cards, synthetic customers, notifications off, one window | Whoever records |
| 5. Frame review | A second person checks the export against the table below | Reviewer, then compliance |
A script-stage catch is a two-minute edit. A final-cut catch means re-recording and a second review.
Use this checklist for step 5:
| Check | What to look for |
|---|---|
| Card numbers | Only test cards, masked to BIN and last four |
| Bank details | Only test routing and account numbers |
| People | Synthetic names, 555-01XX phone numbers, example.com emails |
| Balances and transactions | Generated amounts, no real merchants tied to real customers |
| Rates and fees | Match the approved script and today's live rate |
| Insurance badges | Correct bank name, nowhere near uninsured products |
| Charts | Labelled as illustrative |
| Around the edges | Notifications, autocomplete, API keys, second screens |
Keep the signed checklist with the video file, and note which rate was live on the day it was approved. When the rate changes, you'll know exactly which videos to update.
Where Poko fits
Poko makes product videos from a source you give it: a screen recording, a PDF, a slide deck or a code repository. That suits this workflow, because the source can be checked before any video exists. Record your scripted sandbox walkthrough, review it, then give Poko only the clean file. Our guide to choosing a source for Poko explains which input gives which result.
Poko renders on your own computer, so finished files don't pass through a third-party render server. See local rendering vs. cloud video tools for the trade-offs. The AI model that writes the script is still a separate service, so give Poko only sandbox data.
When a rate changes, you can edit the video by typing, such as "update the end card to the new APY", instead of re-recording. Then send compliance only the changed part to check.
The tool doesn't replace review. It makes each round of review smaller.
Your next step
Open the script of your current fintech demo video and highlight every number, every "free", every "insured" and every promise about growth. If you find more than two, book 30 minutes with compliance before you record anything new. For a related workflow in another regulated industry, see our guide to healthtech demo videos without patient data.
Questions, answered.
Can I use a real customer account in a fintech demo video?
No. A real account puts card numbers, balances, names and transaction histories on screen, and blurring them afterwards depends on someone catching every frame. Record in a sandbox instead. Payment providers publish test data for this: Stripe's standard Visa test card is 4242 4242 4242 4242, and Plaid's sandbox signs in with user_good and pass_good. Fill the demo account with generated customers rather than an edited copy of real data.
What card number can I show in a demo video?
Show a test card from your payment provider, never a real one. Stripe's standard Visa test card is 4242 4242 4242 4242, with any future expiry date and any three-digit CVC. Even then, show it masked the way your live product does. PCI DSS requirement 3.4.1 says displayed card numbers should show no more than the BIN and last four digits, so a demo showing the full number looks wrong to anyone who knows PCI.
Do fintech demo videos need APY or APR disclosures?
They can. If a video for a deposit account states a rate of return, Regulation DD requires it to be called the annual percentage yield, with details such as minimum balance and whether the rate can change. If a loan video mentions a payment amount, number of payments, down payment or finance charge, Regulation Z requires the down payment, repayment terms and APR as well. A script with no specific rates or terms avoids both.
Can a fintech company say it is FDIC-insured in a video?
Only an insured bank can say that about itself. Federal law and 12 CFR Part 328 ban presenting uninsured products as insured or misrepresenting how far a deposit is insured, including by leaving information out. The FDIC sent cease-and-desist letters to five companies over such claims in August 2022. A fintech should name the bank that holds the deposits, in wording its compliance team approves, and keep FDIC logos away from uninsured products.
Do FINRA rules apply to product demo videos?
Yes, if you're a FINRA member firm and the video reaches retail investors. Under FINRA Rule 2210, a registered principal must approve each retail communication before it's used or filed. The content must be fair and balanced and can't make promissory or exaggerated claims, or predict or project performance outside narrow exceptions. A demo portfolio chart that only goes up can imply performance, so label sample data as illustrative.
Keep reading
Healthtech Demo Videos Without PHI: A HIPAA-Safe Workflow
A healthtech demo video should contain zero real patient data, not blurred data. Here's a 5-step workflow: a synthetic sandbox, a locked-down recording machine, a scripted click path, an 18-identifier review and a separate process for patient stories.
Why Local-First AI Video Tools Matter for Product Security
Cloud-first video tools often require uploading your entire project before work begins. Here's why a local-first workflow gives product teams tighter control over unreleased features, sensitive data, and source files.
Local Rendering vs Cloud Video Tools: Privacy, Speed, and Tradeoffs
Local and cloud video rendering each offer unique advantages. Compare their privacy, performance, cost, collaboration, and scalability to find the right workflow for your team.
Poko Motion · the fastest AI motion video generator
Make your first video
in 5 minutes.
Paste a link, a doc or a deck. A swarm of AI agents builds the video while you watch.
