At that time, the bank didn’t have a native mobile payments solution. Clients could initiate some transfers on desktop, but for security reasons, certain transactions required co-signing by a second account owner — something that couldn’t be done on mobile. When one client made a large transfer, the other had to log in from a computer to confirm it within a limited time window. This caused frustration and repeated failed attempts.

Business stakeholders wanted to bring this flow to mobile, balancing convenience and compliance while ensuring users could complete tasks securely without timeouts or technical issues.
‍

MY ROLE:

In this project, I worked closely with data, stakeholders, and development teams. I collaborated with both the Payments Product Owner and Mobile Product Owner to understand technical and security constraints as well as client pain points. This knowledge helped me design a mobile experience aligned with the web process while optimizing it for on-the-go usage.

I built the information architecture, created prototypes, and designed the final UI for both iOS and Android platforms.

‍

The timeline for this project was short, so I began by aligning closely with both product owners to clarify technical limitations, legal requirements, and user expectations. Understanding the strict structure of banking payments was critical to balance security with task simplicity.

I mapped the full process in a detailed information architecture diagram, which helped surface potential edge cases early and guided our MVP planning. We decided to start with the “Scan Orange Payment” feature — a high-frequency task that allowed users to scan invoices and test the end-to-end experience quickly.

I created prototypes that were validated by the product owners and the security team to ensure both compliance and usability. The first version was designed for iOS, since 55% of active users were on that platform, followed by Android adaptation.

1. Conducted an audit of web and adaptive mobile flows, identifying user friction points.
2. Prioritized most-used payment types for mobile optimization.
3. Designed iOS-first flows, iterated based on feedback, then adapted for Android.
4. Created the bank's initial mobile visual system (color palette, dark theme adaptations, typography guidelines).
5. Delivered detailed specs, design tokens, and flow diagrams to development teams.

The final mobile payments design allowed users to initiate, review, and confirm transactions directly on their phones — including multi-owner approvals.

KEY IMPROVEMENT:

• Simplified step-by-step flow aligned with regulatory rules.
  
• Clear confirmation screens with real-time transaction feedback.
  
• Added visual cues for co-signing and authentication states.
• Unified design system components for iOS and Android.

• Enabled full payment functionality on mobile for the first time.
  
• Increased mobile payment completion rate by 36% within the first release.
  
• Reduced CRO support requests related to failed confirmations by 18%.
  
• Achieved positive internal feedback from both compliance and development teams.
• Set foundation for further mobile feature expansion (QR payments, quick transfers).
  ‍

REFLECTIONS:


This project strengthened my ability to design within strict technical and regulatory boundaries. It taught me how early collaboration with product and security stakeholders helps transform complex, rule-heavy processes into smooth user experiences — while maintaining trust and compliance.