Banks should modernise legacy banking UX when outdated interfaces create measurable customer friction, accessibility or compliance gaps, limit the launch of new digital capabilities, or make it harder to meet changing customer expectations. A full core banking replacement is not a prerequisite. Banks can modernise the digital experience layer while legacy systems remain in place.
Often, banking modernisation is treated as a technology problem. However, the customer experience can become outdated long before a bank is ready to replace its core. Legacy systems can constrain how quickly banks introduce new products and digital capabilities, while modernisation approaches increasingly allow legacy and modern components to coexist during a phased transformation.
The decision, therefore, hinges on whether your current digital experience is creating enough customer, business, technology, or regulatory friction to justify modernisation.
In this guide, we will break down the conditions indicating it may be time to modernise legacy banking UX. If customers are struggling with critical journeys or teams cannot efficiently introduce needed improvements, UX modernisation can be considered independently, or as part of a broader banking transformation programme.
What Legacy Banking UX Actually Means
Legacy banking UX is a digital banking experience that no longer meets users’ needs or expectations and is difficult for the bank to improve efficiently because of underlying technology, process, or system constraints. It can show up as slow or fragmented journeys, unnecessarily long forms, confusing navigation, inconsistent experiences across channels, limited self-service capabilities, or interfaces that make routine banking tasks harder than they need to be.
The term “legacy” can refer to different parts of a banking technology stack, so it is important to distinguish between legacy banking infrastructure and legacy digital experience. A bank can have an ageing core system, an outdated customer-facing experience, or both.
Also Read: How Do You Modernise Enterprise UX Without Rebuilding?
Legacy Core vs. Legacy Banking Experience
A legacy core banking system is the underlying technology responsible for functions such as maintaining customer and account records, processing transactions, calculating balances and interest, and supporting other core banking operations. Many banks still operate technology built or significantly developed decades ago, although the age and architecture of these systems vary widely across institutions.
A legacy banking experience, by contrast, is what customers interact with:
- The mobile app
- Website
- Account-opening flows
- Forms
- Alerts
- Transaction journeys
- Help interfaces
- Other digital touchpoints
These experiences typically connect to underlying banking systems through APIs, integration layers, and other services.
The two problems are related, but they are not the same.
A legacy core can constrain what a bank can deliver, while a legacy UX can make existing capabilities difficult, confusing, or inefficient for customers to use. A bank can therefore have a relatively modern core and still provide a dated digital experience. Conversely, a bank can improve significant parts of its customer experience without replacing its entire core banking platform.
Core banking modernisation and UX modernisation can be related programmes, but they do not necessarily have to happen at the same time. Banks can use phased approaches to modernise customer-facing experiences while legacy systems continue to operate underneath them.
What Does a Modern Banking Experience Look Like in 2026?
There is no single definition of a “modern” banking experience. However, current digital banking research points to several recurring expectations. These include simple navigation, convenient journeys, accessibility, personalisation, cross-channel consistency and easier completion of everyday banking tasks. Deloitte’s 2025 Digital Banking Maturity research specifically identifies navigation, ease of use, accessibility, customisation and channel intuitiveness as important UX focus areas.
Customers also increasingly compare digital banking experiences with the broader digital products they use every day. Further, Deloitte's research has found that banks are taking inspiration from familiar non-banking applications.
In practical terms, a modern banking experience should make common tasks clear, accessible and efficient. Depending on the product and market, this can include:
- Simple navigation: Customers can quickly find balances, transactions, payments, cards, support and other frequently used functions.
- Efficient journeys: Routine tasks such as transferring money, managing cards or updating account information do not involve unnecessary steps or repeated data entry.
- Consistent experiences: Journeys remain coherent across mobile, web and other relevant banking channels.
- Accessible interfaces: Digital banking services can be used by people with different abilities and assistive technologies, subject to the accessibility requirements applicable in the relevant market.
- Clear communication: Transaction statuses, fees, warnings, errors and next steps are explained in language customers can understand.
- Useful personalisation: Relevant information, recommendations and controls are surfaced based on the customer's context and needs.
- Effective error recovery: When something goes wrong, the interface explains what happened and provides a clear path forward.
Modernisation, therefore, is about reducing unnecessary friction and creating a digital experience that is easier to understand, more accessible, and better aligned with how customers actually use banking services.
| Dimension |
Legacy banking UX |
Modern banking UX |
| Entry point |
Product- or category-led |
Task- and context-oriented |
| Navigation |
Organisation- or product-led |
Task-oriented and intuitive |
| Forms |
Long and repetitive |
Shorter, pre-filled and progressive |
| Errors |
Technical or unclear messages |
Plain-language guidance with a recovery path |
| Consistency |
Inconsistent across channels |
Consistent cross-channel patterns |
| Accessibility |
Addressed late or retrospectively |
Considered throughout the design process |
| Change speed |
Slow and dependency-heavy |
More modular and easier to iterate |
Signs Your Banking UX Has Aged Out
A banking UX may need modernisation when customers struggle to complete important tasks, digital journeys show persistent friction, accessibility gaps remain unresolved, or product teams find it increasingly difficult to improve the experience. Dated visual design can be a symptom, but it is rarely enough on its own to justify a redesign.
The stronger evidence sits in three places, you see. That is, your analytics, your interface, and your organisation.
What Are the Signs of Legacy Banking UX?
The most useful signals include rising abandonment, inefficient customer journeys, inconsistent interfaces, accessibility issues, excessive form completion effort, repeated customer-support contacts, and a growing dependency on legacy systems or processes.
The important point is to look for patterns across multiple signals, rather than treating one metric as proof that your banking UX is outdated.
1. Behavioural Signals in Your Banking Analytics
Your existing product analytics can reveal where customers are experiencing friction.
Application and onboarding abandonment is one important signal. Track completion and abandonment rates by product, device, acquisition source, and step in the journey. Fenergo's 2025 Financial Crime Industry Trends Report shows 70% of firms lost clients to inefficient onboarding even as AI adoption doubles year-on-year.
Time to complete a critical task can reveal friction that conversion rates alone miss. Track how long customers take to complete journeys such as account opening, making a payment, transferring money, managing a card or finding a statement.
In-app search behaviour can expose information-architecture problems. Look for frequently searched terms, repeated searches, searches that return no useful results, and searches for functions that should already be easy to find through navigation.
Authentication and recovery metrics can reveal friction around login, authentication, and account recovery. Rather than looking only at failed login attempts, measure the complete journey. Look at failed attempts, successful recovery, abandonment, and repeat attempts.
Customer-support contacts can provide another signal. If customers contact support shortly after attempting a digital task, analyse the journey they were completing and the reason for contact. This does not prove that the interface caused the contact, but recurring patterns can identify journeys that warrant investigation.
2. Signals in the Banking Interface Itself
You can also identify legacy UX without waiting for analytics to tell you where the problems are.
Start with your account-opening and onboarding flows. Count the number of fields, steps, and screens. Then identify how much information the bank already holds and whether customers are being asked to provide information repeatedly.
Next, measure the number of interactions required to complete your most important customer journeys. There is no universal “correct” number of taps, but unnecessarily long or fragmented journeys are useful signals for a UX review.
Look at your information architecture. As banking products and services expand, navigation can become increasingly product- or organisation-led. A modernisation review should test whether customers can find what they need based on their goals and tasks rather than having to understand the bank's internal structure.
Then examine error states and recovery paths. Technical error codes, unclear messages, missing explanations, and dead ends can turn an otherwise functional journey into a frustrating one. A modern banking experience should explain what happened in plain language and, where possible, provide an appropriate next step.
Finally, check component and interaction consistency across mobile, web, and other relevant channels. If the same control behaves differently or uses different terminology across journeys, the problem may extend beyond an individual screen and indicate a broader design-system or governance issue.
3. Accessibility Signals
Accessibility should be treated as a measurable part of banking UX rather than a final visual check.
Evaluate critical journeys against the accessibility requirements applicable to your market and product. For web experiences, WCAG 2.2 provides testable accessibility success criteria covering areas such as contrast, keyboard accessibility, input purpose, and target size. W3C also recommends combining automated or functional testing with human evaluation and usability testing, including testing with people with disabilities.
Useful checks include:
- Keyboard accessibility
- Screen-reader compatibility
- Text and non-text contrast
- Form-label and input-purpose support
- Focus visibility and order
- Touch and pointer target sizes
- Error identification and recovery
- Zoom and text resizing
- Accessible authentication and identification flows
Rather than reporting a generic “screen-reader pass rate,” assess conformance against the relevant WCAG success criteria and supplement automated testing with manual and user testing.
4. Signals in the Organisation
Some of the strongest legacy-UX signals appear outside the interface itself. So, it is important to assess how difficult it is to make a relatively small change to a critical customer journey.
If changing a label, validation rule, component or interaction requires extensive coordination across legacy systems, teams or release processes, investigate the underlying dependency.
Other useful questions include:
- Does the organisation have a design system that teams actively use?
- Are the same components being recreated across products?
- Do teams have to redesign established patterns for every new feature?
- Are there critical journeys that teams are reluctant to modify because ownership or implementation knowledge is unclear?
- How many systems need to change before a relatively simple UX improvement can go live?
- How long does it take to move a validated design change from design to production?
A slow change process does not automatically mean the UX is legacy. Banking products operate within security, risk, compliance, technology, and governance constraints. But persistent dependency-heavy change can be a signal that the experience layer and the underlying technology or operating model need closer examination.
Also Read: How Can a Fintech UX Audit Improve Your Product?
A 12-Point Legacy Banking UX Audit
You can use these checks as a starting point for a quarterly UX review:
- Application completion rate, segmented by device, product, and journey
- Abandonment points in your longest or highest-value journeys
- Field count and repetition in onboarding and account-opening flows
- Interactions required to complete the five most common customer tasks
- Authentication failure and recovery rates
- In-app search queries, including failed and repeated searches
- Support contacts following digital sessions, analysed by journey and reason
- Accessibility conformance across five critical customer journeys
- Contrast, keyboard, focus and target-size compliance where applicable
- Design-system adoption and component reuse across digital products
- Time from approved design change to production, including major dependencies
- Customer feedback and app-store reviews, categorised by recurring UX issues and competitor comparisons
Taken together, these signals can help you determine whether you are dealing primarily with a screen-level usability issue, a journey-level experience problem, or a broader platform and operating-model constraint.
If you are preparing a larger transformation programme, a formal UX audit or CX audit can extend this assessment across products, journeys and channels and turn the findings into a prioritised roadmap.
Should Banks Modernise UX or Core Banking First?
Banks do not always need to replace their core banking system before modernising the customer experience. UX modernisation can often happen first when the existing systems can provide the required data and capabilities through reliable integration layers. Core or backend changes become necessary when the underlying technology prevents the bank from delivering the functionality the new experience requires.
When Can Banks Modernise UX Before the Core?
Banks can consider modernising the experience first when the primary problems are related to navigation, usability, accessibility, content, interaction design, or journey structure, rather than missing backend capabilities.
This approach is particularly viable when:
- The core can provide the data the customer journey requires.
- Existing APIs or integration layers can reliably expose required services.
- The underlying transaction and product logic does not need to change.
- Customer-facing improvements can be delivered without modifying core systems.
In these situations, banks can modernise the digital experience while continuing to operate their existing core infrastructure.
When Does UX Modernisation Require Core Changes?
A redesigned interface cannot compensate for an underlying system that lacks the required capability.
Core or backend changes may be necessary when:
- The required data is unavailable or cannot be accessed reliably.
- Critical product or business logic is tightly coupled to legacy systems.
- Customer data is fragmented across systems, limiting the experience the bank can provide.
- The required transaction or product capability does not exist in the underlying platform.
How Can Banks Modernise UX Without Replacing the Core?
Banks can use integration and architectural layers to create more separation between the customer experience and legacy systems.
An API layer can expose legacy capabilities through consistent interfaces, while a backend-for-frontend (BFF) can aggregate and transform the data required by a specific digital channel. Incremental modernisation approaches such as the Strangler Fig pattern can also allow functionality to move progressively from legacy systems to newer services rather than requiring an immediate full replacement.
The specific approach depends on the bank's architecture, integration capabilities, security requirements, data environment, and regulatory obligations.
Ultimately, the idea is to identify which customer problems can be solved at the experience layer, which require deeper technology changes, and where the two need to be modernised together.
What Should Banks Modernise First in Legacy Banking UX?
Banks should prioritise legacy UX modernisation by customer journey rather than redesigning screens one at a time. Start with journeys that have high usage, significant customer friction, measurable business impact, or important accessibility and service implications. This aids in improving outcomes such as completion, conversion, engagement, and support demand rather than simply updating the visual interface.
A screen-by-screen redesign can improve visual consistency without addressing the underlying journey. A journey-led approach looks at the complete task:
- Where customers enter
- What information they need
- How they move through the flow
- Where they encounter friction
- What happens when something goes wrong
Which Banking Journeys Should Banks Modernise First?
There is no universal priority order for every bank. However, five journey categories are often worth assessing early because they combine frequent use, customer impact and measurable business outcomes:
1. Sign-in and Account Access
Sign-in is one of the most frequently repeated digital banking interactions. Authentication, recovery and security checks should be easy to understand while still providing the controls and verification the bank requires.
2. Balance, Transactions and Statements
Customers frequently use digital banking to check balances, review transactions and understand their financial position. These journeys should make important information easy to scan, search and interpret without forcing users to understand internal banking terminology.
3. Payments and Transfers
Payments and transfers are high-consequence journeys. The experience needs clear confirmation, understandable transaction states, meaningful error messages, and appropriate recovery paths so customers know what happened and what to do next.
4. Onboarding and Identity Verification
Account opening, loan applications, and other onboarding journeys directly connect digital experience with acquisition and activation. Review where users abandon the journey, repeat information, encounter verification problems, or lack clarity about what happens next.
5. Servicing and Dispute Resolution
Customers turn to digital channels not only to transact but also to resolve problems. Card issues, disputed transactions, failed payments, account questions, and service requests are opportunities to reduce unnecessary effort while maintaining appropriate security and escalation paths.
The right starting point should ultimately come from the bank's own analytics, customer research, and service data. Prioritise the journeys where customer friction and business impact overlap, rather than assuming every bank has the same UX priorities.
Should Banks Fix Information Architecture Before Redesigning the Interface?
It is recommended to fix information architecture before redesigning the interface when the underlying problem is difficulty finding the right product, task or information. A visual redesign cannot compensate for an information architecture that mirrors internal product structures rather than customer needs.
This is particularly important for banks and NBFCs with large product portfolios. Customers may know what they want to achieve without knowing the financial product's internal name.
For example, our work with Capri Loans involved redesigning the experience around a portfolio of more than 100 loan products. Audience-led research covered borrowers, investors, and partners, while the information architecture was restructured to make product discovery easier. The experience also incorporated Hinglish-oriented content architecture and interactive calculators to help users understand and explore loan options. The redesign reported a 20% increase in lead-form conversions and a 25% reduction in bounce rate.
When users cannot find the right product or understand where to go next, fix the information architecture before adding more interface elements.
When Should Banks Introduce a Design System?
Banks modernising multiple journeys should establish or strengthen their design system early enough to create consistency across those journeys. A design system brings together reusable components, interaction patterns, content rules and accessibility considerations so teams do not solve the same interface problem repeatedly.
This becomes particularly important when a bank is modernising several products or channels at once. Without shared patterns, different teams can create different versions of forms, navigation, alerts, buttons and transaction states.
A design system also makes accessibility easier to manage systematically. Accessibility requirements can be incorporated into reusable components and patterns rather than being treated as a separate check at the end of every individual screen.
Our work on HDFC Invest Right illustrates how this can work alongside information architecture. The experience was designed around portfolio visibility for HNIs managing diverse, multi-asset portfolios, supported by a premium design system aligned with HDFC Securities' existing brand language. The project reported a 30% increase in portfolio engagement and a 22% increase in feature adoption.
When is Personalisation Worth Adding to Banking UX?
Personalisation is most useful when it helps customers understand information or take an action that is relevant to their circumstances. It should solve a recognised customer problem rather than exist simply because the technology makes it possible.
Useful applications can include:
- Personalised financial summaries
- Relevant spending insights
- Contextual reminders
- Savings or financial-goal prompts
- Product recommendations based on relevant customer context
- Portfolio or account information prioritised around user needs
The key is relevance and control, you see. Financial products operate in a high-trust environment, so recommendations and nudges should be understandable, appropriately timed and transparent about why they are being shown.
While working on HDFC Tru, we focused on making everyday banking more personal through financial-clarity dashboards, contextual nudges and integrated product discovery. The project reported a 32% increase in daily app engagement and a 22% increase in product cross-sell rate.
What Should Banks Avoid Redesigning?
Banks should avoid redesigning a journey simply because it looks old. A high-performing journey may not need a wholesale redesign if customers complete it successfully and there is no evidence of significant usability, accessibility, compliance, or operational problems.
Before changing a stable journey, check:
- Task completion and abandonment
- Error and recovery rates
- Customer feedback and support contacts
- Accessibility performance
- Changes in regulatory or security requirements
- Underlying technology dependencies
- Upcoming product or core-system changes
- Whether customers have already learned and rely on the existing interaction pattern
There are also cases where an apparently successful journey still needs targeted modernisation. For example, an accessibility gap, security requirement or new product capability can justify changing an established flow even when its existing completion rate is strong.
The objective is therefore not to redesign everything. Instead, it is better to modernise where the evidence shows that change will improve the customer experience, business outcome, or ability to evolve the product.
How Should Banks Prioritise UX Modernisation?
A practical approach is to score each journey against four dimensions:
| Dimension |
Questions to ask |
| Usage |
How frequently do customers use this journey? |
| Friction |
Where do users abandon, fail, repeat or seek help? |
| Business impact |
Does the journey affect acquisition, activation, engagement, retention or cost to serve? |
| Change dependency |
Can the experience be improved independently, or does it depend on core/backend changes? |
This creates a more defensible modernisation roadmap than starting with whichever screens look the most dated.
For example, a bank may discover that its account dashboard is visually dated but performs well, while its onboarding flow has high abandonment and repeated support contacts. In that case, the onboarding journey may warrant earlier attention even if the dashboard is the more obvious visual problem.
Modernise What Matters. Keep What Works.
Legacy banking UX does not need to be replaced simply because it looks dated. The stronger signal is whether it is creating friction for customers, slowing teams down, limiting accessibility, or making it harder to deliver the experiences customers now expect.
The answer is not always a new core or a complete redesign. Sometimes it is a clearer journey, better information architecture, a more scalable design system, or a smarter experience layer. The solution lies in knowing what needs to change, what can stay, and where modernisation will have the greatest impact.
That’s the thinking behind the banking and financial experiences we design at Onething Design. From simplifying 100+ loan products for Capri Loans to creating portfolio-first experiences for HDFC Invest Right and more personalised banking journeys for HDFC Tru, we focus on solving the experience problem.
If you’re wondering what to modernise first, let’s talk. We’d love to help you figure it out.