Enhance the personal banking experience through system thinking
Project Type
Personal Banking UX Redesign
Role
Senior UX Designer
Tools Used
Figma, Miro, Jira
Duration
6 Months
Team
1 Lead Designer, 3 Devs, 2 Stakeholders
Focus Areas
Mobile Banking, Cardless ATM, Security Flow
This project aims to modernize the personal banking experience by introducing cardless ATM withdrawals, enhanced mobile payment security, and inclusive features for both digital-first and traditional users. By implementing tap-to-ATM functionality, biometric/passcode authentication, and ensuring accessibility through user-centered design, the solution addresses common pain points such as forgotten cards, passcodes, or limited ATM access. Backed by service blueprints, user flows, and usability testing, the project delivers a seamless, secure, and accessible banking experience that aligns with evolving customer expectations.
You walk 20 minutes to the bank to withdraw some cash for the weekend, only to realize your wallet is still at home by the time you arrive. For many banking users, simple tasks like these are disrupted by systems that still rely heavily on physical cards. This dependence not only slows people down but also limits accessibility and flexibility across platforms. We set out to reimagine a more seamless and secure way to bank—without needing your wallet at all.
I step into a project already in motion, only to realize no one can tell me what stage it's really in or why certain decisions were made. There’s no research to guide the design, no collaboration between teams, and no clear foundation to build on. It reminded me of projects I’ve seen before: everyone moving, but no one aligned. So I hit pause, rebuilt the workflow around user needs, and brought the design and dev teams back to the same table.
I mapped out a clear workflow to help the design team move forward with purpose. I asked each team member to document what they knew and what had been decided before I joined, so we could validate everything with stakeholders. Once we had clarity and confirmation, we worked to rebuild a shared foundation across teams. That alignment gave everyone a common direction and a reason to move together.
One of the biggest gaps was end-user research. Until then, designs were driven by assumptions which shaped more by stakeholder opinions and designer bias than real user needs. To shift that, we talked to both mobile-first users and those who still rely on cash, observing how they interact with ATM systems and mobile banking. What we uncovered brought clarity: patterns, pain points, and unmet needs that had been invisible until we asked.
We interviewed a mix of participants across varying age groups and banking behaviors:
3 mobile-first users (ages 25–40)
3 traditional users (ages 45–65)
Key Themes Identified:
Convenience vs. Limitations: Mobile-first users appreciate the speed of wallet-based payments but feel frustrated when physical cards are still required for large withdrawals.
Security Perception: Traditional users view physical cards and cash as more secure and remain hesitant about mobile withdrawals and digital authentication.
Device Dependence: Users expressed concern over forgetting passcodes or running out of battery during mobile-based ATM use.
Expectations of ATM Interactions: Most users have a strong mental model of how ATM workflows should proceed and expect confirmation steps, clear feedback, and receipt options.
We also developed a low-fidelity prototype simulating the mobile-initiated ATM withdrawal process. Users were asked to complete the following flow:
Select a bank card from their mobile device.
Tap the device on the NFC-enabled area of the ATM.
Authenticate using a passcode or biometric.
Enter and confirm the withdrawal amount.
Complete the transaction and retrieve cash.
Test Scenarios Included:
Biometric failure and retry.
Attempted withdrawal above the default limit.
Low battery notification during session.
Delay or inactivity timeouts at the ATM.
Observations:
Users find mobile payments highly convenient and prefer storing multiple cards in digital wallets.
Most users can complete routine purchases quickly and efficiently without needing to carry physical cards.
Frustration arises when transactions exceed default limits, requiring a physical card to proceed.
Users rely on seamless, uninterrupted digital experiences and view fallback to physical cards as a step backward.
Insights:
There is a strong opportunity to implement alternative verification methods (e.g., biometric confirmation, in-app passcodes) to maintain the digital flow for high-value transactions.
Users value the autonomy and flexibility of mobile payments and expect consistency across all purchase scenarios.
Enhancing mobile security while preserving convenience could boost user trust and reduce friction during edge cases.
Observations:
Some users, especially those less digitally inclined, continue to rely heavily on cash and physical cards.
These users perceive cash as more secure and tangible, especially for budget control and daily expenses.
Hesitancy toward mobile payments stems from concerns about fraud, technical failure, and lack of familiarity with digital platforms.
Insights:
Digital adoption strategies must address security concerns, provide guided experiences, and deliver step-by-step onboarding for traditional users.
The design should accommodate both digital and traditional behaviors, offering parallel, accessible experiences that build trust over time.
Encouraging adoption requires not only technology but also clear education, reassurance, and simplicity in execution.
With real user insights in hand, the team began to question the assumptions behind earlier design decisions. The belief that a mobile-first approach would naturally lead traditional users to adopt digital payments didn’t hold up. Research showed us what we had missed user habits, accessibility gaps, and very different expectations. It was a turning point that grounded the project in reality, not just optimism.
Frustration when physical card is required for transactions over the mobile payment limit.
Interrupted experience due to lack of alternative digital authentication methods.
Dependency on mobile device battery and connectivity for access to banking functions.
Lack of trust signals during high-value mobile transactions.
Discomfort with mobile wallets due to unfamiliarity or fear of digital fraud.
Reluctance to transition from cash and physical cards, which feel more secure.
Anxiety over forgotten passcodes or biometric setup failures.
Limited understanding of how mobile tap-to-withdraw or digital banking flows work.
Mobile-first users love the ease of tapping to pay—until a purchase goes over the default limit.
That’s when the smooth experience breaks, and they’re forced to reach for a physical card they might not have.
To fix that, we introduced a simple idea: let users verify high-value transactions by entering the same passcode they set up at their bank.
No extra steps, no new logins—just a secure fallback that fits into their existing habits.
It keeps the flow seamless, the payment secure, and the card right where it was: left at home.
For mobile-first users, needing a physical card just to use an ATM feels like a step backward.
So we imagined a simpler way, what if you could just tap your phone at the ATM, the same way you pay at checkout?
With NFC-enabled authentication, users can securely verify their identity using their device and passcode which no card required.
From there, withdrawing or depositing cash becomes just as seamless as a contactless payment.
It’s one more way to make everyday banking meet users where they already are—on their phones.
Some users still trust cash and physical cards and that’s okay.
But even for them, inserting a card into an ATM feels a little outdated (and not always secure).
With tap-to-ATM, they can simply tap their card, enter a passcode, and get on with their transaction with no slot, no swipe.
It’s faster, reduces card wear, and helps prevent skimming, all while keeping the flow familiar.
It’s a quiet upgrade that respects old habits while making room for something better.
More seamless and accessible for mobile-first users
More secure and frictionless for both digital and traditional customers
More efficient and user-friendly, reducing dependency on physical cards while maintaining security
To understand two very different kinds of users, those who tap to pay and those who still carry cash, we mapped out their journeys from start to finish. Each step revealed not just actions but frustrations, emotions, and missed opportunities. While some teams rush into design, we took the time to see the full picture. That’s how we built a solution that works for everyone, not just the digitally fluent.
Note: Due to NDA restrictions, certain sections of the development service blueprint and process flow have been removed from the images to protect confidential information.
One of the first things I pushed for was a service blueprint. It helped us see what users do not see, how design, development, and product teams work together behind the scenes. By mapping internal operations, system triggers, and dependencies, we uncovered gaps that were slowing everything down. It gave the dev team clarity, aligned cross-functional efforts, and turned a scattered process into a shared and scalable workflow.
Note: Due to NDA restrictions, certain sections of the development service blueprint and process flow have been removed from the images to protect confidential information.
Rather than relying on imagined flows from earlier meetings, we built entirely new user flows and status flows grounded in real user needs. The user flows helped us trace every step, from mobile payments to ATM withdrawals, uncovering friction points and opportunities to simplify. The status flows revealed how the system processes and communicates each transaction, which is especially important for security checks and real-time limits. Together, they closed the gap between front-end experience and back-end logic, making the entire journey clear, consistent, and secure.
To respect the organization’s privacy, the original information architecture remains behind the scenes. Instead, we focused on highlighting the new structures built for this innovation sections that introduced payment verification, tap-to-ATM access, and a cleaner status flow. By mapping only the redesigned components, we kept things confidential while showing how each piece fits into the larger system. The result is a structure that feels intuitive to users and scalable for the team behind it.
We started wireframing with the organization’s low-fidelity Figma library as our guide, giving the team a consistent and accessible foundation to build from. Using predefined components helped us move faster, stay visually aligned, and keep every screen rooted in the brand’s existing standards. It also made handoff easier and reduced guesswork across design and development. These wireframes became the blueprint for integrating new features like payment verification, tap-to-ATM access, and stronger security flows—fitting seamlessly into the app while keeping the experience clear and intuitive.
The design team was fortunate to work with a system already built with accessibility in mind. Every UI component in the Figma library was thoughtfully crafted, tested, and ready to meet WCAG standards—making accessibility part of the process, not an afterthought. From buttons to form fields, everything was set up for keyboard navigation, screen readers, and clear visual contrast. With those components, we brought the high-fidelity wireframes to life, confident that the final experience would be both inclusive and easy to use.
While we were refining the experience, the dev team had their hands full too. To make cardless ATM withdrawals even more secure, they added biometric authentication right into the mobile app. Now, instead of reaching for a card, users can tap and verify with a fingerprint which quick, simple, and secure. It’s one more way we’re reducing risk and making everyday banking feel effortless.
Initiating the Transaction - Users open the banking application or digital wallet on their mobile device.They navigate to their linked bank card or credit card and select the withdraw cash option. At the ATM, they tap their mobile device on the designated area (NFC-enabled) to initiate authentication.
Biometric or Passcode Authentication for Security - Once the mobile device is tapped, a confirmation screen appears on the app.Users are prompted to authenticate using biometric verification (such as fingerprint or facial recognition) or enter their secure bank passcode to authorize access. After successful authentication, users enter the cash amount they wish to withdraw.
Confirming & Completing the Withdrawal - Users review and confirm the withdrawal request.The ATM dispenses the cash, and users have the option to manually complete the transaction within the app. For added security, the system includes an automatic logout feature—if no action is taken within 30 seconds of inactivity, the session will auto-close, ensuring user privacy and security.
Prototyping takes time, but it’s the clearest way to bring ideas to life. To test and refine the cardless ATM withdrawal flow, we built interactive prototypes that walked through every step from selecting a card to tapping the ATM and confirming with biometrics. These helped stakeholders, testers, and developers experience the journey in real time, including edge cases and micro-interactions. It became our shared blueprint, making sure the final experience was smooth, secure, and ready to build.
To validate the cardless ATM flow, we watched real users try it for themselves—tapping, authenticating, and withdrawing cash with just their phones. We didn’t just look for success; we paid close attention to where things went wrong. Simulated errors like failed biometrics or exceeded limits helped us see how users reacted, recovered, and navigated the flow. Those moments of confusion became opportunities to fine-tune the interface, improve guidance, and make the entire experience feel simple, secure, and stress-free.
With the workflows, research, and designs fully documented and handed off, my role on this project comes to a close. The handoff was smooth, shaped by tight collaboration, clear communication, and constant testing along the way. One thing this project reinforced is that good design goes beyond the screen—it’s about system thinking, alignment, and questioning assumptions early. While I’ve stepped away, the work lives on in a solution that’s inclusive, secure, and ready to support every kind of user.
