User research for fintech products: a product manager's guide
Foundational guide for fintech product managers running user research. Methods, recruitment, compliance considerations, and stack recommendations for B2C and B2B fintech.
User research for fintech products is structurally different from research in other industries because fintech sits at the intersection of money, regulation, and trust. PMs at fintech companies have to research users who are risk-averse, behaviors that are sensitive (real money, real consequences), personas that span consumer to enterprise treasury, and compliance constraints (PCI-DSS, SOC 2, GDPR, regional banking regulations) that affect what data you can collect and how. The methods that work best are diary studies for spending behavior, in-product testing for friction at money-flow moments, expert interviews for compliance and treasury personas, and verified-panel recruitment for trust-sensitive segments.
This guide is for product managers at fintech companies, from consumer apps (neobanks, payment apps, robo-advisors) to B2B fintech (treasury, accounts payable, embedded finance, compliance platforms). It covers what makes fintech user research different, the methods that fit best, the personas you’ll research, the compliance overlay, and the realistic research stack.
TL;DR: user research for fintech products
- Trust is the hidden variable. Fintech users behave more risk-averse than consumer or enterprise users in any other industry. Research that ignores trust dimensions misses the actual barrier to adoption.
- B2C and B2B fintech are different worlds. Consumer apps research with verified consumer panels and in-product methods. B2B fintech (treasury, AP, compliance) requires verified senior B2B with specialized panels.
- Compliance overlay matters. PCI-DSS, SOC 2, GDPR, and regional banking regulations affect what user data you can collect, how long you store it, and what you can show participants in studies.
- Diary studies are underused. Financial behavior is contextual (paycheck week vs end-of-month, rent due date, business cash flow cycles). Diary studies surface patterns that interviews miss.
- Specialized panels matter. Generic recruitment panels often fail on financial specialists (treasury, compliance officers, CFOs). Verified B2B panels (CleverX, NewtonX) are usually the right call.
What’s different about fintech user research
Five structural factors make fintech research different from research in other industries:
| Factor | Why it matters |
|---|---|
| Trust as a primary variable | Users actively manage perceived risk. “Will I lose my money?” is the first unspoken question. Methods must surface trust signals. |
| Real money in tasks | Test scenarios involving real account balances or real transactions are constrained. Synthetic data, sandbox environments, or hypothetical scenarios introduce their own bias. |
| Compliance overlay | What data you can collect, how long you can store recordings, and what you can show participants depends on PCI-DSS, SOC 2, GDPR, and regional regulations. |
| Diverse personas | Consumer apps test with general consumers; B2B fintech tests with treasury managers, AP specialists, compliance officers, CFOs ? each with very different research dynamics. |
| Behavioral context | Spending and saving behaviors depend on cycles (paycheck, rent, tax, business close) that are invisible in single-session interviews. |
The PMs who win at fintech research treat these factors as part of the research design from the start. The PMs who struggle treat them as constraints to work around.
Common research questions in fintech
PMs at fintech companies typically face this set of recurring questions:
| Research question | Best method | Common mistake |
|---|---|---|
| Why do users abandon onboarding? | In-product session replay + interviews with abandoners | Interview only completers; you miss the abandonment reasons |
| Will users trust this new feature with their money? | Concept testing with trust-specific probes | Asking generic “would you use this” instead of trust-specific dimensions |
| Why is feature X under-adopted? | In-product micro-surveys + targeted interviews | Survey-only research; misses the “moment of friction” context |
| What’s slowing down the AP workflow? | Diary studies + observation interviews with AP specialists | Single-session interviews miss workflow cycle issues |
| How do CFOs evaluate fintech vendors? | Expert interviews with specialized B2B panel | Generic B2B recruitment misses CFO seniority |
| Will SMB owners pay for premium features? | Pricing research + willingness-to-pay studies | Asking willingness-to-pay directly biases responses |
| What’s the right onboarding for a treasury platform? | Usability testing with verified treasury professionals | Generic UXR participants don’t reflect treasury workflows |
| Are users worried about security? | Trust-specific surveys + qualitative depth | Direct security questions get socially desirable answers |
Methods that fit fintech well
1. Diary studies for behavioral context
Financial behavior is cyclical. Spending changes by paycheck week, rent week, end-of-month, end-of-quarter (for B2B), tax season. Single-session research misses these patterns.
Diary studies (1-4 weeks of participant-recorded financial moments) surface:
- When users actually use the app vs when they say they do.
- Friction points that only emerge in specific cycle moments.
- The emotional context around financial actions.
- Real account balances and transaction patterns (with permission).
For diary study mechanics, see the methodology comparison.
2. In-product micro-research for friction detection
Tools like Sprig, Hotjar, and Pendo Feedback let PMs trigger surveys and AI-driven follow-ups at meaningful moments ? at transaction confirmation, at rejection, at abandonment, after first deposit. For fintech, this is the highest-signal method for friction at the money-flow moment.
3. Expert interviews for B2B fintech
For B2B fintech (treasury, AP, compliance, embedded finance), expert interviews with verified senior B2B participants are usually the right call. These users won’t show up on generic consumer panels and won’t tolerate UXR-style research that wastes their time.
4. Trust-specific concept testing
Concept testing for fintech features should add trust-specific probes:
- “What would have to be true for you to feel safe using this?”
- “What’s the worst-case scenario you imagine when using this?”
- “Who else would you ask before deciding to use this?”
- “If something went wrong, what would you expect to happen?”
These probes surface the trust dimensions that generic concept tests miss.
5. Behavioral observation over self-report
For sensitive financial behaviors (overdraft, missed payments, credit usage), self-report is unreliable. Users underreport stigmatized behaviors and overreport socially-desirable ones. When possible, pair self-report with behavioral data in-product analytics and transaction logs with consent.
Personas you’ll research in fintech
Fintech personas split into B2C and B2B categories with very different research dynamics:
B2C fintech personas
| Persona | Where they’re hard to research |
|---|---|
| Mass-market consumers (neobanks, payments) | Easy to recruit; harder to get them to talk truthfully about money |
| High-net-worth users (wealth platforms) | Hard to recruit; over-cautious in research |
| Underbanked / credit-challenged | Stigma makes self-report unreliable |
| Gen Z (mobile-first, BNPL, crypto) | Easy to recruit; opinions shift fast |
| SMB owners (using consumer-feeling apps) | Mid-difficulty; emotional + practical motivations mixed |
B2B fintech personas
| Persona | Where they’re hard to research |
|---|---|
| Treasury managers (cash management, FX) | Hard to recruit; deep specialized workflow |
| AP/AR specialists | Mid-difficulty; workflow research needs observation |
| CFOs (vendor evaluation, strategy) | Hard to recruit; high incentive cost |
| Compliance officers (KYC, AML, fraud) | Hard to recruit; regulated industries verify carefully |
| Procurement (B2B vendor selection) | Mid-difficulty; structured evaluation processes |
| Developers (embedded finance APIs) | Mid-difficulty; community recruitment via developer-specific channels |
For specialized B2B recruitment, see best B2B participant panels 2026.
The compliance overlay
Compliance affects what fintech PMs can do in research. The realistic constraints:
Data you should not collect from research participants:
- Real account numbers, full PAN (Primary Account Number), full SSN.
- Real bank statements unless you have the legal infrastructure to handle them.
- Behavioral data tied to real transactions without explicit consent.
Data you can collect with proper consent:
- Anonymized spending patterns (% of income on category X, not actual amounts).
- Self-reported financial behaviors.
- Screen recordings of test environments (not production).
- Sandbox transaction data.
Data retention:
- GDPR (EU users): right to deletion, time-limited storage.
- CCPA/CPRA (California): similar rights.
- PCI-DSS (any payment data): strict storage and access controls ? usually means don’t store at all in research.
What to show participants in studies:
- Mock data for hypothetical scenarios.
- Anonymized real data with explicit consent.
- Sandbox environments rather than production for usability testing.
- Avoid showing other users’ data even anonymized for live financial products.
For more on the broader compliance environment, see compliance research considerations and HIPAA-style research considerations applied to financial data.
The fintech research stack
For fintech PMs, the realistic 3-layer stack:
| Layer | B2C fintech tools | B2B fintech tools |
|---|---|---|
| In-product feedback | Sprig, Hotjar, Pendo | Sprig, Pendo |
| User interviews | User Interviews + CleverX (for verified) | CleverX (B2B), NewtonX (executive), SAGO (regulated) |
| Diary / longitudinal | dscout, custom diary tools | dscout, in-product capture |
| Synthesis | Dovetail, native AI tools | Dovetail, native AI tools |
| Compliance / consent | Native consent tooling per platform | Native consent tooling per platform |
For most fintech PMs, the cost of running research badly (insights that lead to features users don’t trust or adopt) is much higher than the cost of the right tools. Fintech is one of the few industries where premium tooling pays back fast.
Common mistakes fintech PMs make
1. Skipping trust-specific probes. Generic concept testing tells you “users like the feature” but misses “users don’t trust putting their money behind it.” Trust is invisible until you probe for it.
2. Single-session research on cyclical behavior. Spending behavior changes week-to-week. Single-session interviews miss patterns. Diary studies are underused but high-signal.
3. Generic B2B panels for fintech B2B. Treasury managers and compliance officers don’t show up on Respondent or User Interviews at meaningful volume. Use specialized B2B panels (CleverX, NewtonX, SAGO).
4. Testing in production. Even with anonymization, showing real user data to research participants is risky. Build a sandbox; the cost is much lower than a compliance incident.
5. Self-report on stigmatized behaviors. Overdraft, missed payments, debt burden, credit issues ? users underreport these by 30-50%. Pair self-report with behavioral data when possible, or use indirect questioning techniques.
6. Ignoring regional regulation differences. Fintech that operates across geographies (EU + US, US + Asia) needs different research designs per region. GDPR-compliant US research workflows often violate EU rules.
7. Treating consumer fintech research like B2B SaaS research. Consumer fintech users are not “consumers.” They’re risk-averse decision-makers operating with their own money. The research design should reflect that understanding about B2B user research vs B2C.
Frequently asked questions
What’s different about user research for fintech vs other industries?
Fintech research has to account for trust as a primary variable, regulated data handling (PCI-DSS, GDPR, banking regulations), cyclical behaviors (paycheck cycles, business cash flow cycles), and personas that span risk-averse consumers to specialized B2B (treasury, compliance, CFOs). Understanding user research in product management provides foundational context that applies, but fintech layers on unique compliance and trust constraints.
How do I recruit financial professionals for research?
For mid-tier B2B fintech personas (AP specialists, mid-level finance managers), verified B2B panels like CleverX or User Interviews Business work. For senior B2B (CFOs, treasury managers, compliance officers), specialized panels (CleverX, NewtonX) or custom recruitment is usually required. Generic consumer or marketplace panels typically fail. See recruit financial professionals for research.
What incentives should I pay fintech research participants?
Consumer fintech: $50-$100 for 30-min interviews. Mid-level B2B fintech: $100-$200. Senior B2B (CFOs, treasury VPs): $300-$500. Compliance officers and regulated-industry experts: $300-$600. Under-paying senior B2B fintech is a common reason studies don’t complete.
Can I show real user data in fintech research?
Generally no. Use anonymized data, sandbox environments, mock scenarios, or get explicit consent for any real-data exposure. PCI-DSS requirements alone make showing payment data in research environments rare. Build a sandbox; the cost is small compared to compliance risk.
What’s the right method for testing trust in a fintech feature?
Trust-specific concept testing with probes about worst-case scenarios, who they’d consult before using, what would need to be true for them to feel safe, and what they’d expect if something went wrong. Pair with behavioral observation when possible ? what users say about trust and what they actually do can differ by 20-40%.
How is B2B fintech research different from B2C fintech research?
B2C is high-volume general consumer research with trust overlays. B2B fintech requires specialized senior-B2B recruitment, longer cycles (multi-stakeholder buying processes), compliance-aware research designs, and methods that fit specialist workflows (treasury, AP, compliance). The recruiting cost is 5-10? higher; the research signal per participant is also higher.
How long should fintech user research take?
Quick-turn studies (24-48 hours): possible for consumer fintech via verified panels. 1-2 weeks: typical for mid-tier B2B fintech. 3-6 weeks: realistic for senior B2B fintech (CFOs, treasury) and regulated industries (compliance research). Diary studies for behavioral patterns: 2-4 weeks minimum.
What’s the biggest mistake fintech PMs make in research?
Treating fintech users as if they were consumer SaaS users. They’re not. Fintech users are risk-averse decision-makers operating with their own money or company money. Research designs that ignore this (generic concept tests, single-session interviews on cyclical behavior, no trust probes) produce findings that don’t predict actual adoption behavior.
The takeaway
User research for fintech products is structurally different from other industries: trust is a primary variable, compliance constrains data collection, behaviors are cyclical, and personas span consumers to specialized B2B. PMs who design research around these factors find adoption barriers competitors miss.
The realistic stack is 3 layers: in-product feedback (Sprig/Hotjar/Pendo), interview platform (CleverX for B2B, User Interviews for B2C), and diary/longitudinal capture (dscout). Add specialized B2B panels (CleverX, NewtonX, SAGO) for senior fintech personas. Match the research design to the persona ? consumer fintech research and B2B fintech research are different practices, not variants of the same thing.