Product design · Fintech

ZenPay: a mobile wallet app for payments, budgets and spending

A fintech app for payments, expense tracking and budgets, with its research, user flow and UI design.

ZenPay fintech app design case study cover: the home screen with balance, quick send and transaction history
Project
Designed by Maniruzzaman Jubayer
Industry
Fintech, payments, Fintech work
Topics
Fintech case studies, Mobile app case studies
Year
2025
Tools
XD, Illustrator, Photoshop, Figma
Featured on
Development, Amsterdam, Mobile app design, Dubai, Mobile app design, Riyadh, Product design, New York, Mobile app design, Abu Dhabi

Overview

This fintech app design case study covers ZenPay, a mobile wallet for sending and receiving payments, tracking expenses and setting budgets in one place. I designed the mobile app, from personas and user flow to the final screens, and a landing page that sells it.

The challenge

Money apps run on trust, and the deck set out what that meant.

  • Earn trust in a crowded fintech market while meeting data security rules.
  • Keep balances and activity consistent across devices.
  • Let a busy user send money and check spending quickly.
  • Give a freelancer paid by several clients one clean record.

The process

  1. Research, 1 week: personas for a busy professional and a freelancer.
  2. User flow: from onboarding and log in to home, then out to scan QR, analytics, cards, add money and a profile with its settings.
  3. A moodboard, then wireframes, 2 weeks: greyscale layouts for withdraw, send money, transfer receipt, cards, notifications, analytics and profile.
  4. Visual design, 2 weeks: Switzer type from a 36 px headline down to 16 px buttons and tags, a monochrome palette of near black, white and light grey, and a 4 column grid on a 390 px screen with 12 px gutters.
  5. A design system of reusable components: the bottom bar in each active state, card faces, notification rows and buttons.
ZenPay fintech app user flow from onboarding and log in to home, cards, analytics and profile settings
ZenPay fintech app user flow from onboarding and log in to home, cards, analytics and profile settings

The solution

Every screen that moves money follows the same order: who, how much, what it costs, then confirm.

Home and balance

Home opens with a greeting, then Top Up, Send Money and Withdraw as chips across the top, because that's why people open the app. The available balance sits in the centre in large type. Below come a quick send row of recent contacts and the transaction history, each line marked Paid or Added. The bottom bar puts a round scan button in the middle, within reach of the thumb.

Send money, top up and withdraw

Each flow starts with the person or account, shown as a card you can edit. Top up offers a grid of preset amounts plus a custom option; send and withdraw use a large keypad. Before the button, the screen lists the value, the charge and the total, and top up strikes through the fee when a free charge applies. Nobody meets a surprise fee after tapping.

Verification and receipts

Paying needs a PIN on a calm verification screen with one line of reassurance and four dots. After it, a success screen shows the amount and a receipt with payment status, transaction ID, date, time and type. Every payment leaves a record the freelancer persona can find later.

Cards and payment methods

The cards screen stacks a light and a black card with the last four digits and expiry, and an Add New Card button underneath. Adding a card is one form: number, expiry, CVC, cardholder name, address and email, then Save Card. A separate screen lists the payment methods, each with a radio button, before Next.

Analytics and notifications

Analytics splits earning and spending into two tabs, with a weekly filter and a bar chart that darkens the selected day. The transaction history repeats underneath, so a spike in the chart can be checked against the payments behind it. Notifications are grouped into Today and Yesterday: money received, subscriptions, offers, top ups and newly connected cards.

Landing page

The landing page leads with one promise, Get Started and Watch Demo buttons, and the home screen in a phone. Four feature cards follow (payments, budgeting, expense tracking and insights), each illustrated with a piece of the app's interface, then four reasons to choose ZenPay beside the send money screen. A plan section with a monthly and yearly toggle, user quotes, an FAQ and a closing call to action finish it.

ZenPay mobile app screens: home, top up, withdraw, verification, cards, notifications and transfer receipt
ZenPay mobile app screens: home, top up, withdraw, verification, cards, notifications and transfer receipt

The result

  • The mobile app, listed in the project summary as 50+ screens across 20 flows.
  • A design system: Switzer type scale, monochrome palette, grid and components.
  • A landing page with feature cards, an FAQ and a closing call to action.

How it helps the client

ZenPay can ask for trust one step at a time: users see the charge before they pay, confirm with a PIN and get a receipt after. Busy users and freelancers get balance, history and spending in one place, and the shared grid and components mean new flows can be added without the app drifting. For more work like this, see my fintech case studies. Building something similar? See how I approach product design for fintech apps.

Frequently asked questions

  • On ZenPay: a home screen led by the balance, send money, top up and withdraw flows, QR scan, saved cards, analytics with weekly spending, notifications, and profile settings for security, payments and support. Onboarding with sign up, log in and password recovery comes before all of it.

  • Make every cost and step visible. On ZenPay I started with personas and a full user flow, then gave every money screen the same order: recipient, amount, charges, confirm. A PIN step confirms the payment, and a receipt with a transaction ID follows it.

  • Keep it to one screen of decisions and one of confirmation. On ZenPay the recipient comes first, picked from recent contacts or edited in a card, then the amount on a large keypad, then the charge and total, then one Transfer button. A PIN step stops accidental payments, and the success screen doubles as a receipt. I wireframed it in greyscale first to settle the order of steps.

  • On ZenPay it covered type, colour, grid and components. Switzer runs from a 36 px headline to 16 px buttons and tags, the palette is near black, white and one light grey, and the grid is 4 columns on a 390 px screen with 12 px gutters. The components include the bottom bar in each active state, card faces, notification rows and primary buttons. With those in place, a new flow is assembled from parts that already work, and the developer handoff stays short.

  • The ZenPay timeline set 1 week for research, 2 weeks for wireframes and 2 weeks for visual design. Every project starts with a free 30 minute intro call, then a written scope and one fixed quote, and runs in weekly design sprints with a written update every 48 hours.

  • Yes. I build iOS and Android apps in React Native or Flutter, and web front ends in React and Next.js. This case study covers the design. Either way you get a documented design system and developer handoff, so the build follows the screens.

More case studies

Fintus banking website design case study: the Smarter Money, Simpler Life homepage hero on a desktop monitor

Fintech · 2024

Fintus

A website for a banking and saving platform

FundFlo finance SaaS landing page design: the title above a laptop showing the dark hero and proof cards

Fintech · 2024

FundFlo

A landing page for a finance SaaS

Planning a product like ZenPay?

A free 30 minute call. You leave with a clear next step, whether we work together or not.

Book a free intro call