Banking UX is Shaped by the Systems Behind the Customer Journey

Natalia Labanava, Head of UX at Velmie, discusses the principles of digital banking experience, the future of customer channels and the difference between production-proven solutions and generic white-label products.

Banks have invested heavily in digital channels, but the quality of the customer experience still varies widely.

A polished interface can make a strong first impression. In production, however, customers judge a banking service by whether they can understand the status of a payment, complete onboarding without unnecessary repetition and resolve a problem without moving between several disconnected channels.

The experience depends on more than interface design. It reflects the quality of the core banking platform, the transaction model, external integrations and the operational processes behind the service.

We spoke with Natalia Labanava, Head of UX at Velmie, about how financial institutions should approach digital-channel design and what they should expect from a production-ready banking solution.

What makes UX in financial services different?

Natalia: Banking interfaces have to make complex and sometimes irreversible actions understandable.

Banking UX is fundamentally about trust. People open a financial application because they want to feel in control of something important: their salary, savings, business cash flow or a payment they cannot afford to get wrong.

Every detail contributes to that sense of control. The wording of a transaction status, the timing of a confirmation and the way the interface responds when something goes wrong all shape whether the customer feels confident or anxious.

A good banking experience does not hide complexity. It translates complexity into something people can understand and act on. When a payment is still being processed, the customer should know why, what is happening next and whether any action is required. When an account is restricted, the product should explain the situation with care rather than display a cold system message. This is the thinking behind the transfer confirmation screen Velmie recently designed for Flot, where every critical action is confirmed clearly before it is submitted, so the customer never has to guess whether the transfer has actually gone through.

This is why banking UX cannot be designed as a visual layer placed over finished technology. Designers need to understand the product rules, transaction lifecycle and operational reality behind the interface. The experience only feels coherent when design, product, engineering and operations are working from the same understanding of the customer journey.

Which principles matter most in digital banking UX?

Natalia: The best banking products become part of a customer’s everyday life. People return because the experience is useful, familiar and rewarding, not simply because they need to complete a transaction.

Good UX helps customers build confidence in the product. It makes important actions feel effortless, brings relevant information forward at the right moment and gives people a reason to explore more of what the institution can offer. Over time, that creates stronger engagement and a deeper relationship with the brand.

Consistency still matters, but it should feel like continuity rather than standardisation. A customer should be able to move between mobile and web channels, notifications and support without feeling that they have entered a different product. The language, behaviour and visual logic should remain recognisable throughout the relationship.

In business banking, the experience must also adapt to the user’s role. A company owner, finance manager and payment approver use the same platform for different reasons. Each should see the information and actions relevant to their work, without having to navigate around functions they do not need.

The objective is not merely to help customers complete a task. It is to create a financial product they enjoy using, trust with important decisions and choose to return to.

How are customer expectations changing?

Natalia: Good banking UX begins with the way people think about money, not with the way a bank organises its products and systems. Customers think about paying someone, managing cash flow, controlling spending or setting money aside. The experience should follow those intentions rather than force people to understand the institution’s internal structure.

The fundamentals are hierarchy, continuity and feedback. The customer should immediately see what matters, understand the result of an action and recognise the same logic wherever they interact with the institution. Complexity should appear only when it is relevant, rather than being exposed simply because it exists in the underlying platform. We applied this principle of clear status communication when designing Flot's transfer-processing status screen, keeping the customer oriented to what stage their payment is at instead of leaving them to interpret a generic loading state.

A strong banking product also develops a sense of familiarity. It understands which information matters to the customer, remembers how they use the service and reduces effort without becoming intrusive. Over time, the experience should feel increasingly natural, not increasingly crowded.

That is what builds preference. Customers may initially choose a bank for its rates, products or convenience, but they continue using its digital channels when the experience feels dependable, considered and easy to return to.

Why should digital channels form part of the core banking program?

Natalia: Digital channels are where the institution’s product and operating model become visible.

The core platform defines accounts, transaction states, limits, fees and permissions. External providers may control card processing, payments or identity verification. The channel has to bring that information together in a form the customer can understand.

When digital channels are delivered as a separate project, the design team may work from API documentation without understanding the complete financial process. This can create gaps between the experience presented to the customer and the way the service actually operates.

For example, the interface may show only “successful” and “failed” payment statuses even though the platform recognises several intermediate states. A card-management journey may be designed before the processor’s operational capabilities are understood. An onboarding flow may overlook what happens when a case is referred for manual review.

At Velmie, the core platform, operational back office and customer-facing channels are developed within the same delivery environment. The channels are not part of the ledger itself, but they are designed around the same product rules, transaction model and operational processes. That alignment reduces the risk of building an attractive interface that does not reflect the service behind it.

What does omnichannel mean in practice?

Natalia: A real omnichannel experience carries the customer’s context from one touchpoint to the next. Someone who starts onboarding on a phone should be able to continue on the web without repeating steps. A payment prepared in online banking should appear immediately in the mobile approval queue, while support and operations teams should see the same status and history in their own tools.

This has less to do with making every screen look alike than with keeping customer data, permissions, product rules and transaction states aligned across the platform. When that foundation is missing, the channels may appear consistent but still feel like separate services.

How will artificial intelligence influence banking UX?

Natalia: AI could change banking UX by removing the need for customers to understand how the product is organised. Instead of searching through menus, choosing a support category or completing a form, a person should be able to describe what they need in their own words.

For designers, the challenge is not to make banking conversational for its own sake. It is to decide when conversation is more natural than navigation, how the system asks for missing information and how it presents the result without hiding important detail.

Trust will depend on restraint. The experience should never sound more certain than the underlying information allows. When the reason for a failed payment is unknown, it should say that clearly. When a request has moved to manual review, the change should be visible rather than disguised behind a reassuring response.

Used well, AI will make the experience feel more attentive. The customer should not have to identify a transaction that is already on screen, repeat information the bank already holds or explain the same issue several times. The product should carry that context forward and respond in a way that feels direct, calm and relevant.

What is the difference between a production-proven channel solution and a white-label product?

Natalia: A white-label solution can provide a useful starting point. It may include standard journeys, reusable components and an established visual structure.

The problem arises when an untested template is presented as a production-ready banking product. A demonstration normally shows the intended journey under controlled conditions. Production introduces interrupted onboarding, delayed provider responses, unusual account states, device changes and customer behaviour that the design team did not anticipate.

Customers may submit the same transaction twice because they did not receive a response quickly enough. They may leave a process midway and return later through another channel. External services may be unavailable or return incomplete information.

A production-proven solution has already been shaped by those conditions. Its transaction states, recovery paths and operational workflows reflect experience from live financial services rather than assumptions made during design.

That does not mean the solution is fixed or that every institution should use the same experience. It means the starting point includes knowledge that cannot be gained from a prototype alone.

How should institutions test whether a channel solution is genuinely proven?

Natalia: A product is proven when its design reflects what has happened after launch, not only what was planned before it. Institutions should ask how the experience has changed in response to real customer behaviour: where people hesitated, which journeys were abandoned, what generated support requests and which assumptions turned out to be wrong.

The most revealing parts of a demonstration are rarely the ideal journeys. It is more useful to see how the product behaves when onboarding is interrupted, a payment remains pending or an external service does not respond. These situations show whether the experience has been designed as a complete service or only as a collection of screens.

The team behind the product matters just as much. A mature channel solution should have an active release process and designers who remain involved after launch, using production feedback to refine journeys rather than treating go-live as the end of the work.

The strongest evidence is visible in the product itself. A genuinely proven solution carries the decisions, corrections and small improvements that come only from being used by real customers.

Does customisation undermine the value of a proven product?

Natalia: Customisation becomes a problem when it breaks the product’s design logic. If every institution receives a different navigation model, set of components and interaction pattern, the solution gradually turns into a collection of unrelated applications. Each change takes longer, improvements cannot be shared, and the experience becomes harder to maintain.

A proven product should provide a coherent foundation rather than a fixed template. The interaction principles, design system and core journeys remain consistent, while the experience adapts to the institution’s products, customer roles and operating model.

That adaptation goes far beyond applying a logo and brand colours. A retail customer, business owner and payment approver may need different information, levels of control and ways of moving through the service. Those variations should feel native to the same product, not like custom screens added around its edges.

Velmie develops its digital channels on a shared product foundation, carrying production experience from one release into the next. Institutions can shape the experience around their proposition without losing the consistency, usability and maintainability of an established product.

What should institutions expect after launch?

Natalia: Digital channels are never finished. Once a product is live, we can see where people hesitate, what they ignore and which parts of a journey make sense only to the team that designed them.

We review the interface in use, not as a set of isolated screens. That means looking at recordings, support conversations, completion rates and the points where customers leave a flow or repeat an action. The important part is understanding why. Sometimes the problem is visual. Sometimes the wording is wrong. Sometimes the interface is exposing a weak process behind it.

Changes are then designed and tested against the original problem. A cleaner screen is not an improvement if customers still cannot complete the task or if the change creates confusion elsewhere in the journey.

At Velmie, UX stays involved after launch because the product keeps changing. New services, updated integrations and new customer behaviour all affect the experience. We use that feedback to refine the digital channels as part of the product, rather than treating each request as another front-end adjustment.

How will digital banking UX evolve in the next 5 years?

Natalia: I think the next generation of banking UX will move from transaction execution to financial guidance. Today, most digital channels wait for the customer to decide what to do. The product displays balances, provides controls and records activity. It is functional, but largely passive.

The opportunity is to make the experience understand the customer’s financial position and help them act before a problem appears. That could mean recognising that upcoming payments will put pressure on cash flow, identifying money that could be used more effectively or bringing an approval to the right person at the moment it becomes relevant. The product should not simply show more information. It should make the next decision easier.

This will change how designers think about banking products. We will spend less time designing isolated features and more time designing the relationship between the customer and their money over time. The experience should become more useful as it learns from behaviour, while remaining transparent and firmly under the customer’s control.

For business customers, the shift will be even more significant. A company does not experience banking as a collection of accounts and payment screens. It experiences it through cash flow, responsibilities, approvals and decisions shared across a team. Digital channels will need to reflect that reality and become part of how the business operates each day.

The institutions that get this right will build products customers actively prefer, rather than channels they use only when they need to move money. That requires the experience, product logic and core platform to evolve together.