(Pliant) White-label Mobile App
OVERVIEW

I led the end-to-end redesign of Pliant’s white-label mobile app, used by companies across Europe to manage corporate cards, reimbursements, and receipts. My focus was to turn complex financial rules into predictable, mobile-first experiences that feel clear, fast, and trustworthy.

UI minimalistic widgets

YEAR

2025

ROLE

Product Designer

SERVICES

User Research
Prototyping
Visual/UI Design
Design System Contribution
Delivery & Handoff


I worked closely with a cross-functional team, from early discovery to implementation, making sure the redesigned mobile app was both technically feasible and experience-driven.

About the project

Context

Pliant is a modern B2B credit card platform that combines corporate card issuance with powerful spend-management tools. The company provides everything from ready-to-use payment apps to fully customizable card infrastructure via API, enabling businesses and fintechs to issue cards, control spend policies, automate accounting, and integrate financial operations at scale. Within this ecosystem, I redesigned the white-label mobile app employees use to track transactions, upload receipts, submit reimbursements, and understand their company’s policies, transforming complex financial logic into a clear, mobile-first experience.

The challenge

Pliant's initial mobile app design was not built with whitelabeling in mind, making it difficult to adapt for different clients. My challenge was to completely redesign the app to function as a fully customizable whitelabel solution. This was essential because many of our customers use our Cards-as-a-Service (CaaS) product and require branded, personalized versions of the app. The redesign involved rethinking the UI/UX to allow theming, flexible branding elements, and modular functionality without compromising performance or user experience. The result was a scalable, adaptable mobile app that meets diverse client needs while maintaining Pliant's core features and security standards.

As Pliant expanded into new markets and onboarded larger customers, the mobile experience became essential to daily cardholder workflows. Users needed to quickly understand which expenses required receipts, when an upload was overdue, whether a transaction counted as personal or business, and how specific reimbursement rules applied to their case.

The existing app struggled to support this level of clarity. Patterns were inconsistent across similar actions, policy logic felt hidden or difficult to interpret, and many of the interactions still relied on web-centric behavior that didn’t translate well to mobile.


Our whitelabel app is used by major clients, including Commerzbank, BMW, Check24, Circula, and Decathlon, among others.

image of a smartphone leaning on top of a record player
UI minimalistic widgets

Approach & Process

  1. Mapping the current experience

    • Audited existing mobile flows: receipts, reimbursements, transaction details, policies

    • Identified duplicate patterns, unclear copy, and inconsistent states

    • Mapped dependencies with web flows and back-office tools


  2. Defining mobile-first patterns

    • Reworked navigation to reduce cognitive load

    • Standardized how we present key financial concepts: status, deadlines, policies, and “what happens next”

    • Created reusable patterns for banners, warnings, empty states, and input flows


  3. Prototyping, validating, and refining

    • Built interactive prototypes to test new flows internally

    • Iterated with Product and Engineering on edge cases and error scenarios

    • Documented behaviors and component specs to support implementation

Design System & White-Label Constraints

The app is white-label, which means multiple customers use it under their own branding. That required:

  • Designing using tokens and flexible components rather than hard-coded visuals

  • Ensuring the UI still works with different brand colors, logos, and typography

  • Reusing core patterns across web and mobile to reduce fragmentation

I collaborated with the design system team to:

  • Extend existing components for mobile needs

  • Document variations for different states (default, warning, error, empty)

  • Align on motion, spacing, and hierarchy rules so the experience feels coherent, regardless of the brand using it.

Impact

  • Clearer understanding of receipt and reimbursement tasks

  • Fewer ambiguities around overdue receipts and personal vs. business expenses

  • A more coherent, “mobile-first” feel across the entire app

Internally, the new patterns became a reference for future mobile work, helping the team ship new financial features faster and more consistently.

Reflection
This project strengthened my ability to translate complex, regulated financial logic into mobile experiences that feel simple, predictable, and human. Working on Pliant’s white-label app gave me hands-on experience designing for real money movement, compliance, and trust at scale.

Smooth Scroll
This will hide itself!

Enter Password

(Pliant) White-label Mobile App
OVERVIEW

I led the end-to-end redesign of Pliant’s white-label mobile app, used by companies across Europe to manage corporate cards, reimbursements, and receipts. My focus was to turn complex financial rules into predictable, mobile-first experiences that feel clear, fast, and trustworthy.

UI minimalistic widgets

YEAR

2025

ROLE

Product Designer

SERVICES

User Research
Prototyping
Visual/UI Design
Design System Contribution
Delivery & Handoff


I worked closely with a cross-functional team, from early discovery to implementation, making sure the redesigned mobile app was both technically feasible and experience-driven.

About the project

Context

Pliant is a modern B2B credit card platform that combines corporate card issuance with powerful spend-management tools. The company provides everything from ready-to-use payment apps to fully customizable card infrastructure via API, enabling businesses and fintechs to issue cards, control spend policies, automate accounting, and integrate financial operations at scale. Within this ecosystem, I redesigned the white-label mobile app employees use to track transactions, upload receipts, submit reimbursements, and understand their company’s policies, transforming complex financial logic into a clear, mobile-first experience.

The challenge

Pliant's initial mobile app design was not built with whitelabeling in mind, making it difficult to adapt for different clients. My challenge was to completely redesign the app to function as a fully customizable whitelabel solution. This was essential because many of our customers use our Cards-as-a-Service (CaaS) product and require branded, personalized versions of the app. The redesign involved rethinking the UI/UX to allow theming, flexible branding elements, and modular functionality without compromising performance or user experience. The result was a scalable, adaptable mobile app that meets diverse client needs while maintaining Pliant's core features and security standards.

As Pliant expanded into new markets and onboarded larger customers, the mobile experience became essential to daily cardholder workflows. Users needed to quickly understand which expenses required receipts, when an upload was overdue, whether a transaction counted as personal or business, and how specific reimbursement rules applied to their case.

The existing app struggled to support this level of clarity. Patterns were inconsistent across similar actions, policy logic felt hidden or difficult to interpret, and many of the interactions still relied on web-centric behavior that didn’t translate well to mobile.


Our whitelabel app is used by major clients, including Commerzbank, BMW, Check24, Circula, and Decathlon, among others.

image of a smartphone leaning on top of a record player
UI minimalistic widgets

Approach & Process

  1. Mapping the current experience

    • Audited existing mobile flows: receipts, reimbursements, transaction details, policies

    • Identified duplicate patterns, unclear copy, and inconsistent states

    • Mapped dependencies with web flows and back-office tools


  2. Defining mobile-first patterns

    • Reworked navigation to reduce cognitive load

    • Standardized how we present key financial concepts: status, deadlines, policies, and “what happens next”

    • Created reusable patterns for banners, warnings, empty states, and input flows


  3. Prototyping, validating, and refining

    • Built interactive prototypes to test new flows internally

    • Iterated with Product and Engineering on edge cases and error scenarios

    • Documented behaviors and component specs to support implementation

Design System & White-Label Constraints

The app is white-label, which means multiple customers use it under their own branding. That required:

  • Designing using tokens and flexible components rather than hard-coded visuals

  • Ensuring the UI still works with different brand colors, logos, and typography

  • Reusing core patterns across web and mobile to reduce fragmentation

I collaborated with the design system team to:

  • Extend existing components for mobile needs

  • Document variations for different states (default, warning, error, empty)

  • Align on motion, spacing, and hierarchy rules so the experience feels coherent, regardless of the brand using it.

Impact

  • Clearer understanding of receipt and reimbursement tasks

  • Fewer ambiguities around overdue receipts and personal vs. business expenses

  • A more coherent, “mobile-first” feel across the entire app

Internally, the new patterns became a reference for future mobile work, helping the team ship new financial features faster and more consistently.

Reflection
This project strengthened my ability to translate complex, regulated financial logic into mobile experiences that feel simple, predictable, and human. Working on Pliant’s white-label app gave me hands-on experience designing for real money movement, compliance, and trust at scale.

Smooth Scroll
This will hide itself!

Enter Password

(Pliant) White-label Mobile App
OVERVIEW

I led the end-to-end redesign of Pliant’s white-label mobile app, used by companies across Europe to manage corporate cards, reimbursements, and receipts. My focus was to turn complex financial rules into predictable, mobile-first experiences that feel clear, fast, and trustworthy.

UI minimalistic widgets

YEAR

2025

ROLE

Product Designer

SERVICES

User Research
Prototyping
Visual/UI Design
Design System Contribution
Delivery & Handoff


I worked closely with a cross-functional team, from early discovery to implementation, making sure the redesigned mobile app was both technically feasible and experience-driven.

About the project

Context

Pliant is a modern B2B credit card platform that combines corporate card issuance with powerful spend-management tools. The company provides everything from ready-to-use payment apps to fully customizable card infrastructure via API, enabling businesses and fintechs to issue cards, control spend policies, automate accounting, and integrate financial operations at scale. Within this ecosystem, I redesigned the white-label mobile app employees use to track transactions, upload receipts, submit reimbursements, and understand their company’s policies, transforming complex financial logic into a clear, mobile-first experience.

The challenge

Pliant's initial mobile app design was not built with whitelabeling in mind, making it difficult to adapt for different clients. My challenge was to completely redesign the app to function as a fully customizable whitelabel solution. This was essential because many of our customers use our Cards-as-a-Service (CaaS) product and require branded, personalized versions of the app. The redesign involved rethinking the UI/UX to allow theming, flexible branding elements, and modular functionality without compromising performance or user experience. The result was a scalable, adaptable mobile app that meets diverse client needs while maintaining Pliant's core features and security standards.

As Pliant expanded into new markets and onboarded larger customers, the mobile experience became essential to daily cardholder workflows. Users needed to quickly understand which expenses required receipts, when an upload was overdue, whether a transaction counted as personal or business, and how specific reimbursement rules applied to their case.

The existing app struggled to support this level of clarity. Patterns were inconsistent across similar actions, policy logic felt hidden or difficult to interpret, and many of the interactions still relied on web-centric behavior that didn’t translate well to mobile.


Our whitelabel app is used by major clients, including Commerzbank, BMW, Check24, Circula, and Decathlon, among others.

image of a smartphone leaning on top of a record player
UI minimalistic widgets

Approach & Process

  1. Mapping the current experience

    • Audited existing mobile flows: receipts, reimbursements, transaction details, policies

    • Identified duplicate patterns, unclear copy, and inconsistent states

    • Mapped dependencies with web flows and back-office tools


  2. Defining mobile-first patterns

    • Reworked navigation to reduce cognitive load

    • Standardized how we present key financial concepts: status, deadlines, policies, and “what happens next”

    • Created reusable patterns for banners, warnings, empty states, and input flows


  3. Prototyping, validating, and refining

    • Built interactive prototypes to test new flows internally

    • Iterated with Product and Engineering on edge cases and error scenarios

    • Documented behaviors and component specs to support implementation

Design System & White-Label Constraints

The app is white-label, which means multiple customers use it under their own branding. That required:

  • Designing using tokens and flexible components rather than hard-coded visuals

  • Ensuring the UI still works with different brand colors, logos, and typography

  • Reusing core patterns across web and mobile to reduce fragmentation

I collaborated with the design system team to:

  • Extend existing components for mobile needs

  • Document variations for different states (default, warning, error, empty)

  • Align on motion, spacing, and hierarchy rules so the experience feels coherent, regardless of the brand using it.

Impact

  • Clearer understanding of receipt and reimbursement tasks

  • Fewer ambiguities around overdue receipts and personal vs. business expenses

  • A more coherent, “mobile-first” feel across the entire app

Internally, the new patterns became a reference for future mobile work, helping the team ship new financial features faster and more consistently.

Reflection
This project strengthened my ability to translate complex, regulated financial logic into mobile experiences that feel simple, predictable, and human. Working on Pliant’s white-label app gave me hands-on experience designing for real money movement, compliance, and trust at scale.

Smooth Scroll
This will hide itself!

Enter Password