Fintech Mobile UX Behavioral Design Payment Systems

Due
Notice

A mobile-first billing redesign that cut call center volume by 62% and transformed a punitive payment experience into one users actually trusted.

62%
Fewer support calls
40%
Faster transactions
5wk
Concept to shipped
JM
Dashboard
Total Loan Balance
$94,700.00
Paid $398 on Aug 27 Autopay Sep 27
Pay $398.00
Pay by
Transactions · PAST 30 DAYS
PNC PNC Bank
−$398.00
Discover Discover Debit
−$100.00
Goals
You're on a 21 payment streak!
Home
$
Payments
Loans
Account
Make Payment
Step 2 of 3
Payment Amount
$398.00
Pay From
PNC Checking ••2232
Payment Date
Today, Aug 27
Biometric Verification
Touch ID to continue
🔒 Encrypted · Single-session · Auto-cleared
Home
$
Payments
Loans
Account
$398.00
Review before confirming
From PNC Checking ••2232
To Student Loan ••4821
Date Today, Aug 27
Autopay Active — Sep 27
Streak after 🔥 22 on time
Confirm Payment
Home
$
Payments
Loans
Account
JM
Dashboard
Total Loan Balance
$94,700.00
Paid $398 on Aug 27 Autopay Sep 27
Pay $398.00
Pay by
Transactions · PAST 30 DAYS
PNC PNC Bank
−$398.00
Discover Discover Debit
−$100.00
Goals
You're on a 21 payment streak!
Home
$
Payments
Loans
Account
Make Payment
Step 2 of 3
Payment Amount
$398.00
Pay From
PNC Checking ••2232
Payment Date
Today, Aug 27
Biometric Verification
Touch ID to continue
🔒 Encrypted · Single-session · Auto-cleared
Home
$
Payments
Loans
Account
$398.00
Review before confirming
From PNC Checking ••2232
To Student Loan ••4821
Date Today, Aug 27
Autopay Active — Sep 27
Streak after 🔥 22 on time
Confirm Payment
Home
$
Payments
Loans
Account
Project Context
Role
Lead Product Designer
End-to-end UX, research, interaction design, field testing
Timeline
5 Weeks
Brief to shipped, cross-functional sprints
Platform
Mobile-first Web
Dark mode by default, biometric auth, offline-tolerant
Team
PM · Dev · Call Center
Validated in the field, not just the lab
The Problem
What the system looked like

200+ calls a day. Every one a design failure.

An eight-step payment flow was generating over 200 daily support calls. Users forgot account numbers, lost progress after single errors, struggled to read in low light, and abandoned payments entirely.

The result: late fees, eroded trust, and a call center absorbing the cost of a broken interface. Every call was a symptom. The system itself was the problem.

What we designed toward

Three steps. Under a minute. No reason to call.

The north star was simple: make payments so seamless that users never need help. Smart onboarding captures account details once. Every subsequent payment is pre-filled, verified, and ready.

We didn't just reduce calls. We eliminated the failure points that caused them.

“The eight steps weren’t a payment flow. They were a call center generator.”

Design reframe · Call center analysis
The Redesign
Interactive Demo

Three steps.
Under a minute.

Every design decision traced back to one question: what would make it so seamless that users never need to call?

01
Dashboard — Total clarity
Balance, next payment, autopay status, and on-time streak visible at a glance. No hunting, no confusion.
02
Payment — Pre-filled, verified
Account details stored securely from onboarding. Users confirm, not re-enter. Errors caught in real time.
03
Confirm — One tap, done
Full summary before commitment. Confirmation receipt stored automatically. Streak updated.
JM
Dashboard
Total Loan Balance
$94,700.00
Paid $398 on Aug 27 Autopay Sep 27
Pay $398.00
Pay by
Transactions · PAST 30 DAYS
PNC Bank
−$398.00
Discover Debit
−$100.00
Goals
You're on a 21 payment streak!
Home
$
Payments
Loans
Account
Make Payment
Step 2 of 3
Payment Amount
$398.00
Pay From
PNCChecking ••2232
Payment Date
Today, Aug 27
Biometric Verification
Touch ID to continue
🔒 Encrypted · Single-session · Auto-cleared
Home
$
Payments
Loans
Account
$398.00
Review before confirming
FromPNC Checking ••2232
ToStudent Loan ••4821
DateToday, Aug 27
AutopayActive — Sep 27
Streak after🔥 22 on time
Confirm Payment
Home
$
Payments
Loans
Account
Design Decisions

Four choices that changed the outcome — each one traceable back to a specific failure point in the original flow.

01 · Flow
Eight steps collapsed to three

Smart onboarding captures account details once. Every subsequent payment is pre-filled, verified, and ready. Users confirm, they don't re-enter. Front-loading setup is not friction — it's the opposite of friction downstream.

Progressive disclosure
02 · Trust
Transparency at every stage

Progress indicators, pending payment dates, and on-time streak tracking transformed the experience from punitive to rewarding. The streak feature reduced late payments — not because we nagged, but because we celebrated.

Behavioral motivation
03 · Security
Biometric login, zero friction

Two-factor authentication and Touch ID balanced strong security with fast access. Encrypted session data cleared automatically. Security UX is still UX.

Security UX
04 · Recovery
Errors that don't punish

Dynamic error highlighting, auto-scroll to problem fields, and real-time correction without clearing data. Dark mode by default came from watching real people struggle in low light, not from WCAG checklists alone.

Error prevention · Accessibility
Outcomes
62%
Fewer support calls

From 200+ daily calls to a fraction, driven by eliminating the failure points that sent users to the phone in the first place.

40%
Faster transactions

Three steps, pre-filled fields, and biometric login cut time-on-task dramatically across all user segments.

5wk
Concept to shipped

Cross-functional sprints with Dev, Accounts, and Call Center. Validated in the field, not just the lab.

What This Work Demonstrates
How do you reduce support calls without adding a chatbot?

You eliminate the failure points that generate them. Every call was a symptom. The flow was the disease. Fixing the experience at the source is cheaper, faster, and more durable than any support layer built on top of it.

What does "validated in the field" actually change?

Dark mode by default wasn't in the brief. It came from watching real people struggle in poor lighting, something a lab test never surfaces. Real context reveals failure modes that controlled environments conceal.

Why does onboarding deserve more design attention than the core flow?

Because what you capture at the start determines how much friction lives in every session that follows. Front-loading is not friction. It's the architecture of a frictionless future.