All work

Case study 05 · PayME · Fintech

Finance for people who don’t trust apps with money.

Leading a team of 6 to turn a basic e-wallet into an embedded finance app with salary advance, loans, savings and insurance, built with bank partners.

Role
Lead Product Designer
Company
PayME Technology Corp
Timeline
Apr 2022 to Apr 2023
Team and tools
Design team of 6 · Figma, Miro, Useberry
PayME version 2.0, embedded finance. A hand holds a phone showing the new finance home with buy now pay later, salary advance, quick loan, insurance and savings.

Problem

Users paid at stores with PayME and did little else. Financial services faced a bigger wall: people didn’t trust an app with their money.

What I did

Led research, set the design roadmap, built a design system, and designed the finance flows, including salary advance with CIMB bank.

Outcome

Shipped a new e-wallet, PayME POS and bank-partnered loan flows, plus the design workflow and brand guidelines with Marketing.

0

designers led and mentored

0/10

interviewees feared losing money to an app

0/10

ran out of salary by mid-month

0

usability findings fixed before release

01Context

From a wallet to a whole financial life.

COVID-19 pushed Vietnamese consumers toward online payments. PayME launched an e-wallet to ride that shift. Then the company set a bigger goal: become an all-in-one financial app for both personal and business needs.

The business goal was clear. Integrate every financial service into one app, with an interface simple enough for every customer segment. The open question was whether users wanted that, and what would stop them.

02My role

Lead, mentor, and the link between business and design.

I led a multidisciplinary design team of 6, including UI/UX designers and a UX writer. My job covered four areas.

Direction

Product roadmap

Turned research into priorities, and priorities into a roadmap the team could follow.

Alignment

Stakeholder requirements

Gathered requirements from business, partners and engineering, and translated them into design scope.

Quality

Output and documentation

Set the design workflow, reviewed output quality, and kept documentation current for engineering.

People

Team management

Mentored junior designers and ran the team’s day-to-day delivery.

03Research

Ten interviews, one loud signal: trust.

We interviewed 10 active users aged 18 to 35 who had made a transaction in the last three months. Each session ran 45 to 60 minutes. We asked about their need for financial services like investing and lending, and their pain points with the current app.

The answers were blunt. Here is how many of the 10 said each thing.

Afraid of losing money to an app or fraud, trust banks more10/10
Felt there were no promotions worth using10/10
Found the first eKYC step hard, with long approval waits9/10
Want quick loans but fear complex steps and unclear interest9/10
Found nothing else to explore, and the UI boring9/10
Use up their salary by mid-month and want an advance7/10
Prefer installments for high-value purchases7/10
Had trouble linking banks and wallets6/10

We also collected user stories to hear the need in their own words.

  • “I’m a taxi driver with a low income. I want to get paid in advance every mid-month to cover my family’s living expenses.”
  • “I want to borrow less than 10 million VND to open a small business, but the bank’s procedures are complicated.”
  • “I want to invest safely with a small amount, 50,000 to 100,000 VND, to learn how investing works.”

A competitor review completed the picture. The market leaders had scale, partners and incentives, but their apps buried services and confused users. Investment apps won trust with audits and big-name backers. The opening was clear: simple to use, and visibly trustworthy.

04Define

Two people, two money problems.

Persona A18 to 50

People who need money

Income of 5 to 10 million VND a month. Needs are higher than income. Want fast disbursement, a trusted sponsor, clear information and a simple interface. Like vouchers. Fear losing money.

Persona B18 to 35

People with money

Income of 10 to 40 million VND a month. Care about customer service and complete information. Prefer safe investments. Fear being cheated.

We mapped one journey for the whole app, from awareness to loyalty, then a detailed journey per feature. Four problems rose to the top.

  1. Brand trust. Users didn’t know PayME well enough to trust it with money.
  2. Onboarding friction. eKYC and bank linking were hard for new users.
  3. Nothing to explore. The app had no standout features beyond payment.
  4. Low financial habit. Few users invested or saved, and educating the market takes time.
PayME user journey map across awareness, consideration, decision, use, explore and loyalty, with thoughts, actions, touchpoints, feelings, opportunities and teams involved.
User journey map. Feelings dip at decision and first use, where trust and errors matter most. Select to enlarge.
Product roadmap in Miro showing design system, onboarding, investment, top-up and profile work across releases.
Design roadmap. I turned the research into a release plan the team could follow. Select to enlarge.

05Ideate

Ideas for the product, and a face for the brand.

Trust isn’t only built in flows. We ran product ideation on whiteboards, and in parallel explored a mascot with Marketing to give the brand warmth and make it easier to remember.

Whiteboard sketches and sticky notes from product ideation sessions.
Product ideation on whiteboards.
Pencil sketches of mascot concepts, including robots, animals and a unicorn.
Mascot exploration with Marketing.

06Design

One structure for many services.

With many services entering one app, information architecture was the first design decision, not the last. I restructured the app so finance services had a clear home next to the wallet.

PayME information architecture tree.
Information architecture for the new app. Select to enlarge.

Salary advance, with three actors

Salary advance answered the clearest need from research: 7 in 10 people ran out of money by mid-month. It was also the most complex flow, because three parties were involved. The user requests, PayME checks, and CIMB bank approves and disburses. I mapped it as a swimlane so business, bank and engineering could agree on every handoff.

Swimlane user flow for salary advance across three lanes: user, PayME and CIMB bank.
Salary advance flow across user, PayME and CIMB. Select to enlarge.

A design system to move fast

To save implementation time, we built the design system from existing app layouts, then refreshed it with new type and a younger color palette. The system followed the roadmap, so each release added the components it needed.

PayME user interface showcase with several app screens on a bright green background.
Four home screen variants: buy now pay later offer, active balance, linked bank accounts, and an empty state.
Home states for new, active, bank-linked and empty accounts. Product UI is in Vietnamese, the market language.

07Test

Five users found three problems we couldn’t see.

Before each release we built a task list and ran usability tests. For salary advance, we recruited 5 participants aged 18 to 35 with low incomes, who needed an advance or a loan for living costs and had never used PayME. Each session ran 45 to 60 minutes.

Five screens of the salary advance happy path: home, amount entry, employer details, confirmation and success.
The happy path participants were asked to complete.

Finding 1

Even with a free amount field, users didn’t know how much was enough to ask for.

Solution

Suggest preset advance amounts, so users can compare options instead of guessing.

Finding 2

Users wanted to see the fee right away. An extra step to view fees made comparing amounts slow.

Solution

Show the fee on the same screen as the amount, and update it live as the amount changes.

Before and after of the amount screen. After adds three preset amounts and a fee breakdown on the same screen.
Before and after. Preset amounts and a live fee breakdown on one screen.

Finding 3

After tapping the entry point, users wanted to see their past advances.

Solution

We weighed two options: show the latest advance on the entry screen, or add a separate management screen. We chose the separate screen, so each screen does one job.

Before: home and amount screens with no history.
Before. No way to see past advances.
After: home, a salary advance management screen listing past advances, then the amount screen.
After. A dedicated screen for advance history.
Showing the fee next to the amount helped users and the business at once. Users could borrow with confidence, and clear pricing is how a new brand earns trust.

08Reflection

The hardest part wasn’t the screens.

We measured on production, but the release took longer than planned. Engineering had to change parts of the implementation. Agreeing on business processes and rules with partner banks took time too.

What I took away as a lead:

  • Bring partners in early. In fintech, the bank’s rules shape the flow. A swimlane reviewed with the bank on day one saves weeks later.
  • Design for trust, not just ease. For money, clarity about fees and status beats a shorter flow.
  • Systems pay off. A roadmap-aligned design system let a team of 6 ship a new wallet, a POS product and loan flows in one year.