Consumer Fintech · Mobile · Payments
iPay Cardholder App
A mobile payments experience designed to simplify onboarding, account access, card management, direct deposit, and everyday cardholder tasks.
Insert a hero shot of the Cardholder App — e.g. the home/account screen — recreated or redacted.
/images/cardholder-app-hero.jpgOverview
Project overview
- Product
- iPay Cardholder App
- Platform
- Mobile (iOS / Android)
- Role
- UX/UI Designer / Product Designer
- Timeline
- 2022 — 2024
- Team
- Product, design, and engineering, with business stakeholders
Responsibilities
- Product discovery
- User research
- UX strategy
- Journey mapping
- Interaction design
- Information architecture
- Prototyping
- Visual design
- Usability testing
- Design systems
- Engineering collaboration
Context
The context
The Cardholder App is the everyday, consumer-facing counterpart to the Client Portal — used directly by cardholders to register, verify their identity, manage their card, and complete routine financial tasks from a mobile device.
Because it handles identity verification, authentication, and financial information, the experience has to earn trust quickly while staying approachable for a broad range of users, in both English and Spanish.
The Problem
New and existing cardholders needed a mobile experience that could take them from registration through everyday account management without friction — while still meeting the identity verification and security requirements inherent to a financial product. The challenge was to make a necessarily multi-step, security-conscious journey feel simple rather than burdensome.
My Role
What I contributed
I led UX/UI design for the Cardholder App's core journeys — registration, identity and contact verification, authentication, and everyday account and card management — from research through high-fidelity design and implementation collaboration.
This work ran in parallel with my Client Portal work, and the two shared underlying design patterns and payment domain logic, which is part of what later informed my move into product management across the broader iPay product line.
Research & Discovery
Research methods
Understanding the cardholder journey meant looking closely at where users dropped off, hesitated, or needed support during onboarding and everyday use.
User Interviews
Conversations with cardholders about their registration, verification, and everyday account management experience.
Workflow Analysis
Mapping the existing registration and verification flow to identify unnecessary steps, ambiguity, or drop-off points.
Competitive Review
Evaluating onboarding and authentication patterns from comparable consumer fintech products.
Usability Testing
Testing registration, verification, and card management flows with representative users before build.
Synthesis & Prioritization
Turning findings into prioritized UX improvements across onboarding, security, and account management.
Research scope: [Add participant count]
User Needs & Insights
What administrators and users needed
Progressive disclosure reduces early drop-off
Asking for identity, contact, and security information in clearly scoped steps — rather than all at once — kept the process approachable.
Clear progress builds trust
Cardholders needed to understand where they were in a multi-step process, especially during identity and phone/email verification.
Security should not feel like friction
MFA, biometric login, and identity verification needed to feel like protection, not an obstacle — through clear explanation and streamlined interaction.
Error prevention matters more than error messaging
Preventing avoidable mistakes (like malformed input or unclear requirements) reduced the need for corrective error states altogether.
Everyday tasks need to be fast
Once onboarded, cardholders needed quick, low-friction access to routine tasks like checking card details or setting up direct deposit.
Information Architecture
Organizing complex functionality
Registration was structured as a clear, linear sequence so cardholders always understood what step they were on and why it was required, before moving into the broader account experience.
- 01Card Information
- 02Identity Information
- 03Email Verification
- 04Password
- 05Phone Verification
- 062FA Setup
- 07Account Home
Design Challenges
What made this hard
Reducing cognitive load in a necessarily multi-step flow
Registration required card, identity, contact, and security information. The challenge was sequencing and framing each step so it felt purposeful rather than like an accumulating checklist.
Security without unnecessary friction
MFA, biometric login, and password recovery all needed to be secure by default while remaining fast for returning users completing routine tasks.
Designing trust into a mobile financial product
As a mobile-first financial product handling identity and card data, the app needed visual and interaction cues that reinforced legitimacy and care at every step, not just at login.
Supporting English and Spanish experiences
Content, layout, and verification flows needed to work cleanly across both languages without compromising clarity or increasing maintenance complexity.
Design Process
Problem → Exploration → Validation → Refinement → Delivery
Registration and authentication flows moved through the same problem-to-delivery arc used across iPay, with extra emphasis on validating step sequencing and security patterns with real users.
Problem framing & early exploration
Low-fidelity concepts exploring how to sequence registration steps and reduce perceived effort.
Insert early wireframes of the registration flow.
/images/cardholder-app-registration-wireframe.jpgFlows & interaction design
Detailed flows covering registration, verification, MFA, and recovery paths, including error and edge cases.
Insert a user flow diagram covering registration through account access.
/images/cardholder-app-flow.jpgValidation
Usability testing of the registration and login prototypes to confirm the flow felt clear and appropriately secure.
Insert a prototype screen used in usability testing.
/images/cardholder-app-prototype.jpgRefinement & high-fidelity design
Refining visual design, microcopy, and states for registration, login, and card/account management screens.
Insert a high-fidelity design of a key screen (e.g. account home or card details).
/images/cardholder-app-hifi.jpgDelivery
Collaborating with engineering through implementation and supporting QA across both English and Spanish experiences.
Insert a final delivered screen with annotations.
/images/cardholder-app-delivery.jpgDesign System
Reusable patterns across the iPay ecosystem
The Cardholder App shared foundational patterns with the Client Portal — particularly around forms, feedback states, and authentication — adapted for a mobile, consumer context.
Form patterns
Consistent input, validation, and helper-text patterns across registration and profile screens.
Verification patterns
Reusable UI for email, phone, and identity verification steps.
Status & feedback states
Consistent success, error, and loading states across financial actions.
Authentication patterns
Shared login, MFA, and biometric authentication UI.
Navigation
A simplified mobile navigation model built for quick access to routine tasks.
Insert a component grid for mobile form, verification, and status patterns.
/images/cardholder-app-design-system.jpgEngineering Collaboration
Designing with technical constraints
Mobile identity verification and authentication carry real technical and security constraints. Working closely with engineering was essential to designing flows that were both usable and implementable.
Partnered with engineers to understand identity verification, OTP, and biometric authentication constraints early in design.
Clarified edge cases together, such as failed verification, expired codes, and unsupported devices for biometric login.
Reviewed feasibility of proposed interaction patterns and adjusted designs where platform or vendor constraints required it.
Supported QA and UAT across English and Spanish versions of the app to confirm consistency before release.
Payment Domain Expertise
Areas of applied fintech knowledge
- Identity verification
- Direct deposit
- Card management
- Authentication
- Secure financial information
- Account administration
Selected Screens
A closer look
Insert a recreated or redacted screenshot of the registration flow.
/images/cardholder-app-registration.jpgInsert a recreated or redacted screenshot of the card details screen.
/images/cardholder-app-card-details.jpgInsert a recreated or redacted screenshot of the direct deposit flow.
/images/cardholder-app-direct-deposit.jpgOutcomes
Where this landed
The registration and account management work contributed to a more modern, trustworthy cardholder experience and a stronger shared foundation with the Client Portal.
A clearer, more approachable registration and verification journey.
More consistent authentication patterns across the cardholder experience.
Shared design patterns that improved consistency across the iPay ecosystem.
A more scalable foundation for English and Spanish experiences.
Quantitative results (add if available)
- [Add adoption metric]
- [Add task completion improvement if available]
- [Add usability result if available]
Note: Certain details and visuals on this page have been modified, simplified, or omitted to protect confidential business and customer information.