Product design for regulated fintech and banking
Banking and fintech app design: mobile and web banking, payment and lending apps, super apps and internal tools. We design the moments that decide trust: the block, the refusal, the limit, the re-verification and the recovery.
Digital banking apps have converged. Transfers, templates and mobile wallets are excellent almost everywhere - in our study they scored full marks across the board. That parity is exactly why the product is no longer won on the happy path.
The gaps that decide trust open on the failure path: a declined transfer, an exceeded limit, a blocked card, a forgotten password. An app can feel great in daily use and still carry trust debt that surfaces the instant something is refused - and a refusal the customer cannot understand, or cannot recover from without a phone call, is where products lose people.
We design mobile and web banking apps around the journeys a bank is judged on: opening an account, getting a card, moving money, changing a limit and getting back in after a block. Each journey is designed to finish in the app, the failure path included.
Account opening that runs end to end in the app, with identity checks that say what they need and why.
Virtual and physical cards, limits the customer sets, and a block they lift in the app, without the phone call our scoring model penalises most.
Transfers and templates, with a payment status that says why a payment is held or declined and what the customer can do next.
A home screen built around what each customer checks most, with navigation measured by the steps each everyday task takes.
For a bank with 700,000+ customers we built a mobile banking app where everything from registration to payments is done online, with virtual cards and a drag-and-drop widget home screen. The first release took six months. View case
Fintech apps face the same trust moments as banking apps: an identity check, a declined payment, a credit decision. We design payment apps, lending apps and super apps with those moments inside the flow, so the customer finishes them in the app.
Checkout with the methods customers already use, such as BLIK or Pay by Account, and a payment status that says what happened and what to do next.
Application and repayment screens, and a credit decision explained in plain language, a refusal included.
Several products in one app, with balances and the everyday actions on the first screen.
For $lana (Monetech), a credit PWA for the Mexican market, our team did the UI/UX design as well as the front end and the back-end integration, and delivery took five months. View the $lana case
For GlobalTips, a restaurant payments platform, we rebuilt the staff onboarding flow in the live app, and GlobalTips measured onboarding around 30% more efficient. View the GlobalTips case
In a pilot study of seven retail mobile banking apps, kept anonymous, we scored each on the three axes. The pattern was consistent: maturity outran experience, and experience outran security - the weakest axis, and the real market gap.
One transparent formula, three weighted axes. We score whether the app creates a calm, understandable, controllable experience. Every weight, criterion and penalty is on the table, so the ranking rests on observable behaviour: steps taken, blocks explained, journeys finished without a call.
Navigation and search, the core scenarios (steps, speed and clarity), design and readability, error and status clarity, and consistency - averaged into one experience score.
Function coverage, genuinely end-to-end digital processes with no office or paper, automation and self-service, and integrations that help rather than clutter.
Security that protects the customer, not one that shifts liability - checks that fire only on real risk, user control of limits, devices and sessions, plain explanations, and low friction.
TOTAL = 0.40 × experience + 0.35 × maturity + 0.25 × smart security
Every app runs the identical set of scenarios on one fixed platform, so the comparison is genuinely like-for-like. Each sub-score uses a behavioural 0-5 scale - 5 is best on the market, 3 is tolerable but the pain is felt, 0 is unsafe to use. Then, and this is the part that matters for a regulated product, security penalties are applied after the average:
A declined action or blocked card with no clear reason costs a full point. A refusal the customer cannot understand is a trust failure.
If the only way back in is a phone call or a branch visit, with no real self-service, the score drops by one and a half - the heaviest penalty in the model.
Making the customer prove the same thing twice in one session costs half a point. Security should not make people pay for the bank's caution.
The evaluation shows where trust breaks. UX research, prototypes, UI and a shared design system close those gaps, and we test the options before a design is kept.
A shared set of standards, rules and components that keeps every screen consistent and makes the product easier to use, maintain and scale.
A standing peer-review step: our designers review each other's work and give feedback, so quality and consistency are held to a team standard.
Interactive prototypes to present, test and refine the experience before a line of production code is written.
We test many options and keep the one that communicates most clearly - for example, evaluating many chart types before choosing the one that best shows a currency's share of a whole portfolio.
For each scenario we record the steps taken, the pain point and the reason for the score, and log critical incidents separately - so a rating can be defended.
We build around what people actually do. For customers who monitor results rather than manage day to day, the interface is made for fast, clear oversight - multi-currency balances recalculated in real time.
A design and usability engagement is sequenced and buyable, and we own the outcome.
Pick one platform and hold it constant, choose a MINI or FULL scope, and declare the weights up front - so every score is comparable and auditable.
The identical set of journeys runs on every app: access and recovery, daily banking, the digital office, and security and data - the failure path included.
Score the three axes on the behavioural 0-5 scale, then apply the security penalties so one serious trust-failure cannot hide inside a comfortable average.
We show where the product loses trust, control and digital continuity, with per-axis leaders and a per-scenario evidence pack - critical incidents kept separate from the average.
Refusals become plain-language messages with a real next step, controls move into self-service, and journeys finish online without a call. We design it, and we own the outcome.
What does banking and fintech app design include?
UX research, a structured usability evaluation, interactive prototyping and UI design, backed by a shared design system. We focus on the moments that decide trust: the block, the refusal, the limit, the re-verification and the recovery.
Do you design fintech apps as well as banking apps?
Yes. Besides mobile and web banking apps we design payment apps, lending apps and super apps. For $lana (Monetech), a credit PWA for the Mexican market, our team did the UI/UX design, and for GlobalTips, a restaurant payments platform, we rebuilt the staff onboarding flow, which GlobalTips measured around 30% more efficient.
How do you measure a banking app's usability?
With one transparent formula over three weighted axes: experience (0.40), digital maturity (0.35) and smart security (0.25). Each sub-criterion is scored on a behavioural 0-5 scale on a single fixed platform, then security penalties are applied after the average, so one serious trust-failure cannot hide inside a comfortable score.
What is the difference between a usability audit and product design?
The audit diagnoses where a product loses trust, control and digital continuity, with per-axis leaders and a per-scenario evidence pack. Design closes those gaps - refusals become plain-language messages with a real next step, controls move into self-service, and journeys finish online without a call.
Do you design for regulated environments like FINMA, DORA and PSD2?
Yes. We design for banks and financial institutions and treat security, control and recovery as product requirements from the start - security that protects the customer rather than shifting liability, with checks that fire only on real risk and user control of limits, devices and sessions.
How long does a design and usability engagement take?
It is sequenced and buyable. You pick a MINI or FULL scope and one platform to hold constant; the identical set of scenarios then runs on every app, is scored and penalised, and the trust debt is diagnosed and designed out. We give you an honest timeline against the scope after a short review.
Can you work with our existing design system and team?
Yes. We embed with your product and engineering team, or augment an existing one, and work within (or help establish) a design system - a shared set of standards and components - so the work stays consistent and easy to maintain and scale. A standing design-check step holds quality to a team standard.
What do we get at the end of a usability evaluation?
A defensible score on each axis, a per-scenario evidence pack recording the steps taken, the pain point and the reason for each score, and critical incidents logged separately from the average - so a rating can be defended. From there we design the fix and own the outcome.
No account managers in between - a working conversation about where your product loses trust and how we would fix it.