UX Case Study
Paze Transaction History
Designing a unified transaction history interface for the Paze digital wallet — across multiple enrolled credit cards, for every type of user.
US Bank Paze Wallet Design Thinking Lead UX Designer
Client
US Bank
Major US financial institution launching the Paze digital wallet ecosystem
Product
Paze Wallet
Multi-card digital wallet enabling seamless online checkout experiences
My Role
Lead UX Designer
Facilitation + UI design
Method
Design Thinking
Mural-based ideation sprint
Output
Figma Prototype
High-fidelity UI ready for review
02 — Challenge
The Problem We Were Solving
Users enrolled multiple credit cards in Paze but had no unified way to see where, when, and how much they'd spent through the wallet.
Pain point
No visibility
Users couldn't see Paze-specific transactions separate from regular card activity
Pain point
Multi-card confusion
Switching between enrolled cards to find transactions was disjointed and slow
Pain point
No filtering or insight
Without filters by date, merchant, or amount — users had no way to make sense of their Paze spending patterns
Problem framing — How Might We
"How might we show users transactions made with Paze wallet?"
03 — Process
How We Worked
A structured design thinking sprint in Mural, designed to move from ambiguity to clarity fast.
Mural brainstorming board
Mural board — brainstorming & Crazy 4s session
1
Problem framing
Defined the HMW statement as a team anchor before any idea generation.
2
Crazy 4s sketch exercise
4 sketches in 4 minutes each — I facilitated to force divergent thinking and keep momentum high.
3
Team voting in Mural
Voting surfaced shared values: clarity, speed, minimal navigation overhead.
4
Concept refinement → Figma
Three directions evolved from raw sketch into high-fidelity UI.
04 — Concepts
Three Paths Explored
Each concept prioritised a different navigation mental model. We evaluated on discoverability, cognitive load, and implementation complexity.
Concept 1
Card-first navigation
Tap a card → swipe between cards → see transaction history in context.
Swipe navCard-centric
Concept 1
Manage wallet view
Concept 1 modal
Transaction history modal
★ Selected
Concept 2
Toggle-based view
A toggle switches between payment mode and transaction history — all cards visible simultaneously.
ToggleAll-card view
Concept 2
Toggle transaction history
Concept 3
Horizontal tabs
Main and Transaction History tabs at top. Familiar pattern, but adds a navigation layer.
TabsFamiliar pattern
Concept 3
Tab-based navigation
Concept 2 won because it kept all enrolled cards in view while making transaction history a single toggle away — no extra navigation, no card-by-card drilling.
Team rationale after voting session
05 — Solution
What We Designed
A unified Paze transaction dashboard built to US Bank's design system — intuitive, filterable, and visually informative.
✓
Dashboard overview
All Paze-enrolled cards with at-a-glance indicators and quick links to activity
✓
Vertical card tabs
Persistent sidebar tabs let users switch cards without losing context
✓
Transaction filters
Filter by card, date range, merchant, or amount — all in one toolbar
✓
Merchant graph view
Visual chart of spending by merchant helps users spot patterns
✓
Paze identifier
Paze logo marks wallet transactions, differentiating from regular card purchases
✓
Incentive bar
Visual progress bar for loyalty or cashback incentives tied to Paze usage
06 — My Contribution
What I Owned
I played a dual role — facilitating the team's creative process and then leading the translation of ideas into a production-ready UI.
🧭
Facilitation lead
Ran the Crazy 4s session, defined the HMW statement, structured the voting process — keeping the team aligned and moving.
✏️
Ideation contributor
Contributed my own sketches in the Crazy 4s exercise alongside the team — ideas that informed the toggle concept direction.
🎨
UI design ownership
Designed the complete high-fidelity Figma prototype: vertical card tabs, transaction toggle, graph view, and incentive bar — all within US Bank's design system.
🤝
Cross-team coordination
Worked with the enterprise UX group throughout to validate decisions against system standards and real user expectations.
07 — Outcome & Learnings
Results & Reflections
The design sprint delivered a validated direction aligned with user needs and US Bank's product standards — ready for development handoff.
3
Concepts ideated and evaluated
1
Toggle concept selected by vote
6
Key features in the final UI
2
Teams aligned through the process
Key learning
Structure unlocks speed
The HMW framing stopped the team from jumping to solutions. A small ritual with outsized effect on output quality.
Key learning
Navigation model is the product
All three concepts had the same data. The winner was about how few steps it took to see it — that trade-off is the real UX decision.
If I did it again
Prototype earlier, test sooner
The toggle vs. tab vs. card-swipe debate could have been resolved faster with even 5 users in a quick usability test before high-fidelity investment.
1 / 7