top of page

Projects

Designing Trust in a Multi-Wallet Fintech Experience

A scalable wallet system that balances usability, trust, and compliance.

This case study presents an end-to-end product design approach focused on progressive onboarding, wallet and account creation, and system scalability in a fintech context.

Built on accumulated UX practice and real-world product experience, this work extends a scalable design system approach based on my previous Design System.

Overview

This project explores how users can manage multiple wallets within a single fintech application without increasing complexity.


The focus is on designing a clear, secure, and scalable experience that supports different user needs while respecting regulatory requirements.

Role & Scope:

  • Role: Senior Product Designer

  • Scope: UX Design, Product Thinking, Service Design, System Design

Intro.png

The Challenge

Users want to separate their money across different purposes such as travel, savings, or shared expenses.
However, research identified four key friction points in existing fintech experiences:

  • Low comprehension of multi-wallet structures

  • Limited sense of control during setup

  • Lack of transparency in balances and actions

  • Trust concerns related to security and compliance

Product Thinking Approach

The solution was approached from a product design perspective rather than isolated UI screens.

Key principles included:

  • Aligning with users’ natural mental model of money

  • Reducing cognitive load through progressive disclosure

  • Keeping onboarding lightweight while maintaining compliance

  • Designing flows that scale with additional wallet types

This ensured a balance between usability, business needs, and regulatory constraints.

Understanding the System

User Mental Model

Users already categorize their money mentally.
Instead of introducing new behavior, the experience mirrors this habit digitally through purpose-based wallets.

This mental model helped define wallet types, hierarchy, and navigation before moving into interface design.

Mind Map.png

Understanding the System

Service Design Perspective

A service design approach was used to align user interactions with backend processes and compliance requirements.

End-to-End Experience Flow

The experience was designed as a continuous journey:

  • Entry and orientation

  • Wallet setup

  • Optional funding

  • Review and confirmation

  • Activation and dashboard access

Flow.png

Soft Onboarding Strategy

To reduce drop-off and build trust gradually, the experience supports soft onboarding.

Users can explore the app and understand its value before completing identity verification. Money-moving actions remain restricted until verification is complete, ensuring safety without blocking discovery.

Soft-onboarding.png

Wallet Creation Experience

Wallet creation is intentionally lightweight:

  • Core information is collected in a single screen

  • Optional actions such as funding are revealed only when needed

  • All decisions remain editable, reducing commitment anxiety
     

This supports both first-time users and experienced fintech customers.

Setup-awallet.png

Scaling with Multiple Wallets

Once onboarded, users can create additional wallets through a faster, simplified flow.

The wallet switcher acts as a central control point, allowing seamless expansion without repeating onboarding steps.

This structure supports long-term growth and advanced use cases.

Dashboard.png

Key Design Decisions

Clarity

Simple Setup

Control

Inline Options & Review

Trust

Transparency & Compliance

Outcome & Learnings

The final solution delivers a multi-wallet fintech experience that is intuitive, secure, and scalable.

Key outcomes include:

  • Reduced onboarding friction

  • Improved sense of control and transparency

  • Strong alignment between UX and compliance

  • A system ready to scale with future features

Image.png

Design Files & Prototype

The full design flow, including user flows, service design artifacts, and key screens, is available in the Figma file below for further exploration.

This case focuses on structure and flow rather than visual polish.

bottom of page