Skip to content

Digital wallet | Shipped product

UniPay: Unified Payments & Financial Management

I designed UniPay's wallet journey: account entry, identity-document choices, wallet home, funding methods, services and confirmation.

Wallet interfaceAccount entry · Document choices · Wallet home
UniPay mobile app screens

PROJECT AT A GLANCE

The essentials.

Design scope
Wallet interface
Available views
Service choices · Confirmation state
Screen focus
Shipped interface
Covered here
Onboarding, identity and wallet screens
Skip to project details

KEY DESIGN DECISIONS

Account, document and funding choices.

Each step asks for one kind of decision: who you are, which document you hold, and where the money comes from.

01

Connected wallet flows

I designed account entry, document choice, the wallet home and funding choices as one connected set of screens.

02

Document choices

The document screen presents identity-document types as clear, selectable options before the user continues.

03

Funding categories

I grouped funding sources into cards and bank accounts, so the choice starts with the type of source.

Each of these decisions shipped in UniPay.

Design
Question

How are document choices and funding choices separated from the wallet overview?

Design
Scope

I designed these core areas:

  • Account entry
  • Document choices
  • Wallet home

Flow
structure

  • Account entry is a separate step from document selection.
  • The document step asks for an identity-document choice before the user continues.
  • Wallet home groups balance, payment shortcuts and services.

Screen
Coverage

How the shipped screens connect.

OnboardingVerify identityFinancial dashboardChoose servicePay or transferConfirmation

Pattern
decisions

Key structures in the shipped product:

  • Document selection and funding selection ask for different kinds of choices.
  • Wallet home presents service shortcuts, while funding groups account types.

What I’d Change
Next

Looking back, I'd design the feedback after a document choice more explicitly: a visible verification state, plus clear rejection and retry paths, before the wallet opens.