Card Sorting for Fintech Apps

Navigation in a banking or investment app isn't just a usability issue — it's a trust issue. A user who can't find "freeze card" in a moment of suspected fraud doesn't think "this app has poor information architecture." They think "I can't trust this app with my money."

The stakes for getting fintech navigation right are higher than most product categories. This guide covers how card sorting specifically applies to financial products and what unique considerations apply.

The Trust Dimension of Fintech Navigation

Most products measure navigation success by task completion rate and time-on-task. Fintech products have an additional dimension: the emotional experience of using a product that holds your money.

When users struggle to find security settings, transaction history, or dispute options, they don't just get frustrated — they get anxious. Financial products require users to extend significant trust. Navigation that feels confusing or disorganized undermines that trust at a fundamental level.

Card sorting helps in three specific ways:

1. Reveals where users expect to find high-stakes features — freeze card, report fraud, change beneficiary — in moments of concern or urgency
2. Surfaces vocabulary mismatches between financial industry terminology and how ordinary users think about money
3. Identifies features users expect to be prominent versus those they're comfortable finding in secondary menus

The Financial Vocabulary Gap

Financial terminology is full of industry-specific language that confuses everyday users. Card sorting makes this visible before it ships.

Industry terms vs. user language:

• "Transfer" vs. "Send money" / "Pay someone"
• "Statement" vs. "Transaction history" / "My activity"
• "Beneficiary" vs. "Who gets my money" / "Emergency contact"
• "Portfolio" vs. "My investments" / "What I own"
• "Yield" vs. "Interest" / "What I'm earning"
• "Recurring" vs. "Automatic" / "Scheduled"
• "ACH" vs. "Bank transfer" (most users have no idea what ACH means)

Write every card in plain language. "Automatic payments" is clearer than "Recurring transactions." If you're testing whether your product's terminology is legible, run that as a separate study — the card sort should focus on structure.

Choosing Cards for a Fintech Card Sort

Organize your card selection around user tasks, not product features.

High-frequency transactional tasks (expect these to be prominent):

• Check account balance
• View transaction history
• Send money / transfer funds
• Pay a bill
• Deposit a check
• Top up / add money

Account management (users expect these accessible but not primary):

• Change PIN or password
• Update personal information
• Link a bank account
• Manage direct deposit
• Set up notifications / alerts
• View statements

Security and protection (must be findable in urgency):

• Freeze / lock my card
• Report unauthorized transaction
• Report lost or stolen card
• Change security settings
• Two-factor authentication

Financial tools (varies by product):

• Spending analysis / budget view
• Savings goals
• Investment performance
• Credit score
• Rewards and cashback

Support and help:

• Contact support
• Dispute a charge
• Help center
• FAQs

Keep the card list to 40–55 items. Fintech users sort more carefully than users of other product types — they read each card twice and place it deliberately. Factor this into your time estimate (allow 20–25 minutes per participant).

Who to Recruit

Financial literacy and product familiarity vary dramatically across user populations. Match your participant pool to your actual user base.

For a consumer banking app:

• Adults who use a bank account as their primary financial product
• Mix of age groups — fintech navigation assumptions from a 28-year-old differ from a 55-year-old
• Include users who are not "tech-forward" — they represent your highest navigation risk

For an investment platform:

• Both experienced investors (who have vocabulary like "portfolio rebalancing") and newer investors (who think in terms of "putting money in stocks")
• Run these as separate segments — their mental models diverge significantly
• Avoid recruiting financial industry professionals unless that's your actual target market

For a B2B fintech product (expense management, payroll, etc.):

• Recruit actual role-holders: the accountant, the finance manager, the employee submitting expenses
• Each role has different primary tasks and different navigation expectations

Running the Study

Open Card Sort (Discover Structure)

Frame your instructions around a realistic use case:

"Imagine you're using a banking app on your phone. Here is a list of things you might want to do or find in the app. Please group these items the way you'd expect them to be organized in the app's menu, and give each group a label."

Use CardSort's open card sorting mode. Participants create their own groups and name them without prompting.

Aim for 15–20 participants for a consumer fintech product. You can start seeing reliable clusters at 12 participants; 15–20 gives you statistical confidence.

Key Things to Watch For

Security features placement: Where do users put "freeze card" and "report fraud"? Do they group them with security settings (expecting them in a dedicated security section) or with account management (expecting them near card details)? The answer tells you how prominent these features need to be in navigation.

Balance and history prominence: Users almost universally expect account balance and transaction history at the top level of navigation — not buried two taps deep. If these appear anywhere except primary navigation in your current structure, that's a findability problem.

"Contact support" placement: Where users put support options reveals their mental model for escalation. Users who sort it under "Help" expect a self-service layer first. Users who sort it near account features expect to reach a human faster.

Dual-placement candidates: Some features get sorted in two different places by different users — "account settings" might go under a profile icon for some users and under a dedicated settings section for others. These need either dual placement or a prominent label that helps users find them from either starting point.

Fintech-Specific Navigation Patterns

Research across financial products reveals consistent navigation expectations:

The "urgent action" layer: Users expect freeze card, report fraud, and lost/stolen card to be reachable in fewer taps than most other features — ideally 1–2 taps from the home screen, not buried in settings menus. In card sorting, these items often get sorted separately from general "Settings" and closer to "Account" or "Cards."

Transaction history is primary, not secondary: Users treat "view my transactions" as a primary navigation task, equivalent to "check my balance." Products that hide transaction history under "Statements" or "History" in a secondary menu create consistent findability problems.

"Settings" splits naturally: Users sort personal settings (notification preferences, privacy settings, contact info) separately from financial settings (payment limits, direct deposit, autopay). Don't force them into a single "Settings" section.

Investment products need progressive disclosure: Experienced investors sort differently from novice investors. A structure that works for experienced users often overwhelms new ones. Consider progressive disclosure — simpler navigation initially that reveals advanced options as users engage more deeply.

After the Card Sort: Validation and Measurement

Tree testing: Before deploying your new navigation, validate it with tree testing. Present the navigation structure (without page designs) and ask users to find specific items. Target 80%+ success rate for high-priority tasks (send money, view balance, freeze card).

Pre-launch baseline: Measure current task success rates for your top 5 user tasks with usability testing. Document them before shipping.

Post-launch tracking:

• Support contact rate for navigation-related issues
• In-app search volume for key features
• Task completion rate for top user flows
• Session dropout rates in critical flows (payments, onboarding)

Well-executed fintech navigation redesigns consistently show 15–25% improvement in new user onboarding completion and measurable reduction in "can't find" support contacts.

Card sorting is free on CardSort — no limits, no credit card required. Start your fintech card sort →