Most banks have nailed the basics. Transfers work. Apple Pay is standard. Card controls exist. But customers still lose trust at the moments that actually matter: a failed transaction, a blocked account, an app that offers no clear next step. We audited seven retail banking apps used in Poland to find where digital journeys still break and what that costs the organisation. This is for product leads, CTOs, and banking operations managers ready to move past feature checklists.
The usual way to evaluate a banking app starts with screens. Is the home screen clean? Is navigation logical? Are icons consistent? Fair questions, but they miss the layer where trust is won or lost.
A journey-based mobile banking UX audit works differently. It follows a real person through a complete task. Not “can the user find the transfer button” but “can they finish the transfer, understand what happens if it fails, and recover without calling anyone.”
We tested thirteen scenarios across every app. First login, daily banking, product opening, failed payments, security settings, recovery paths. Each app was scored on three dimensions: core UX, digital maturity, and security UX.
Basic banking scored well everywhere. The real separation showed up when things got difficult.
Banks look almost identical on the happy path. They diverge the moment something breaks.
Rejected transactions, interrupted transfers, blocked access, repeated authentication loops. These moments expose the product’s real structure faster than any walkthrough. In our sample, the ability to complete a transfer end-to-end without restarting averaged 3.33 out of 5 among incumbent banks. Handling an error without collapsing the flow scored the same.
For a category built on trust, that is mediocre.
The strongest performer stood out precisely here. Recovery was faster. Key information appeared earlier. The next action was obvious. The product stayed calm when the user had the least patience.
What made the difference was not a single feature. It was a product decision: maintain session context after failure, offer a contextual next step, avoid forcing the user back to the start. None of this is complex engineering. Most banks simply have not prioritised it.
Banking app error recovery is where the real gap opens between institutions that treat mobile as a product and those that treat it as a display layer over legacy systems.
Security UX scored lowest across incumbent banks in the audit: 3.13 out of 5, against 3.67 for core UX and 3.83 for digital maturity.
The issue was not missing controls. Controls were there but unexplained and unmanageable from the customer’s side.
Clarity of rejection reason averaged 2.50. User control over limits averaged 2.67. Clarity of next steps averaged 2.67.
When a bank blocks an action without a plain explanation, the customer does not feel protected. They feel locked out. When limits, trusted devices, and recovery paths sit outside self-service, the digital channel feels incomplete no matter how polished the surface.
This goes beyond usability. PSD2 requires Strong Customer Authentication, but it says nothing about how that authentication should feel. The gap between formal compliance and usable clarity is exactly where trust quietly erodes.
Let's start the conversation and develop a solution for your bank that allows you to grow and scale your customer experience.
Poor explainability is not just a UX issue. It is an operating cost problem.
Every journey that ends with “please contact support” or “please visit a branch” means the bank pays twice. Once for the digital product. Then for the manual workaround. The app attracts intent. Another channel absorbs the cost.
In our audit, fully online product opening averaged 3.00 among incumbents. Completing a journey without branch involvement averaged 3.17. Roughly a third of supposedly digital flows still leak into assisted channels.
| Metric | Incumbent average (out of 5) | What it signals |
|---|---|---|
| Refusal clarity | 2.50 | Customers cannot understand why an action was blocked |
| Next-step clarity | 2.67 | The app fails to guide users after an error |
| Self-service limit control | 2.67 | Key settings require a call or branch visit |
| End-to-end journey completion | 3.33 | One in three journeys still needs a channel switch |
| Fully online product opening | 3.00 | Digital onboarding remains partly manual |
The cost of poor explainability in banking is not theoretical. It shows up in support call volume, journey abandonment, repeat contacts, and declining trust in the channel itself.
Routine success is forgettable. A transfer that works as expected creates no memory, no conversation, no loyalty signal. A confusing failure does the opposite.
Customers vividly remember being blocked without understanding why. They remember downloading a PDF to decode a single fact: there was not enough money in the account. They remember the moment the app stopped helping and became a wall.
This perception asymmetry means failure-path clarity carries disproportionate weight. One poorly explained refusal can undo the goodwill of dozens of smooth transactions. Banks that only measure conversion and task completion miss this entirely.
The audit points to three fixes with the highest impact relative to effort.
Explain refusals in plain language. Say what happened, why, and what the customer can do next. Replace compliance-first wording with product-first wording.
Move more control into self-service. Limits, trusted devices, active sessions, card settings, and recovery options should be visible and manageable inside the app.
Measure journey cost, not just journey existence. Track steps to completion, confirmations required, restarts after error, and whether the user can continue or must switch channels. Most banks measure conversion. Far fewer measure composure: the ability of a product to stay understandable under stress.
These are not surface-level interface changes. They typically sit across mobile flows, backend states, identity checks, and the handover between product, operations, and security. That is why isolated screen fixes often disappoint. The visible friction is the symptom. The cause is usually how the system manages state, ownership, and explanation when the journey leaves the happy path.
At WislaCode, this is the territory we work in. We redesign and build the flows that connect mobile, backend, and operational handoff for banks and fintech products, focusing on the moments where digital self-service stops too early.
If your product looks modern but still pushes customers into support queues when something goes wrong, the question worth asking is simple. Where does your digital journey stop being self-sufficient and start borrowing trust from a human?
Thanks to the authors for their support in creating this article.
Viacheslav Kostin is the CEO of WislaCode. Former C-level banker with 20+ years in fintech, digital strategy and IT. He led transformation at major banks across Europe and Asia, building super apps, launching online lending, and scaling mobile platforms to millions of users.
Executive MBA from IMD Business School (Switzerland). Now helps banks and lenders go fully digital - faster, safer, smarter.
