Skip to content
UXE Award

Fintech UX design awards: what we look for in financial products

Entering a fintech product for a UX design award? What editors test in banking, payments and investment interfaces — clarity about money, honest risk, recovery from mistakes, and the accessibility bar finance can't dodge.

The UXE editors5 min read

Financial products are judged by a harder standard than most, and not because the standard is unfair. It's that the cost of a confusing interface is different when the thing being moved is someone's rent. If you're entering a banking, payments, lending or investing product for a fintech UX design award, this is what we go looking for.

1. Can someone tell what just happened to their money?

The single most revealing test in a finance app is the transaction list. It is the screen people open most, usually to answer one question — what was that? — and it's where most products quietly fail.

The transaction list, two ways
Compared onScoresCosts
MerchantThe name people recognise, with the legal name beneathSQ *4417 LTD LONDON GB
StatusPending, cleared, refunded — in words, with datesA colour with no legend
AmountOriginal currency and converted amount, with the rate usedConverted only
FeesShown as their own line, namedFolded into the total
BalanceAvailable vs. total, both explainedOne number that quietly means neither

2. Is risk communicated before the decision, not after?

Investment and credit products live or die on this. We look for whether the cost, the risk and the alternative are visible at the moment of choosing — not in a confirmation screen after intent has formed, and certainly not in a linked PDF.

  • APR, total repayable and the monthly figure together, before the application starts.
  • Losses shown with the same prominence as gains. A portfolio screen that only animates upward is a designed bias.
  • Currency conversion rate and fee shown before confirming, not on the receipt.
  • Any "buy now, pay later" option presented with what happens if a payment is missed, in the same type size as the offer.
If the only place the true cost appears is a document nobody opens, the interface has made a decision on the customer's behalf. That is scored under ethics, not only usability.
Inclusive & Ethical Design criteria brief

3. What happens when someone makes a mistake?

Payments are irreversible in a way almost nothing else in software is. Products that score well are designed around that: they make the risky action slow, the recoverable action fast, and they never rely on a single confirmation dialog nobody reads.

Designing around irreversibility
  1. 01

    Prevent

    Check the account name, flag a first-time payee, warn on an unusual amount.

  2. 02

    Confirm meaningfully

    Restate the amount and recipient in plain words — not "Are you sure?"

  3. 03

    Give a window

    A short cancel period where the rails allow it.

  4. 04

    Explain recovery

    If it can't be undone, say exactly who to contact and how fast.

4. Does it work for the people finance usually fails?

Accessibility in fintech is not a nice-to-have; in many markets it is a legal requirement, and in all markets it is the difference between a product a person can use independently and one that forces them to hand their bank details to someone else. Editors test it directly.

  • Screen reader through an entire payment, including the amount field and the confirmation.
  • Largest text size on the transaction list — do amounts clip or wrap into nonsense?
  • Contrast on green/red status indicators, and whether colour is the only signal.
  • Timeouts: security sessions that expire are reasonable; expiring mid-form with no warning and no draft is not.
  • Authentication alternatives for someone who can't use biometrics or receive an SMS quickly.

5. Is security explained, or just imposed?

Strong authentication is non-negotiable and almost always annoying. The entries that score well don't remove the friction — they explain it, place it well, and never make the user pay it twice. Telling someone why they're being asked to re-authenticate, and returning them exactly where they were afterwards, moves two criteria at once.

Where fintech entries belong

Most financial products enter Product Experience or Mobile Experience with the Fintech subcategory, and the strongest add one specialist category:

Second categories that suit financial products
  • Inclusive & Ethical Design3If you have an audit and an honest position on dark patterns.
  • UX Writing & Content Design3If you rewrote the language of money in your product.
  • Service Experience2If the product spans app, web, phone and branch.
  • Interaction Design2If the payment flow itself is the achievement.

What to send

A test account with realistic data — not three tidy transactions. The transaction detail view. A payment confirmation. An error from a declined or failed transfer. Your accessibility statement with its gaps disclosed. And one measured outcome: support contacts about a specific flow, completion on an application, or failed-payment recovery rate.

Finance is a field where an independent, published score does real work in procurement and compliance conversations — which is a second reason to enter beyond the badge. Submit your product.

Onboarding under regulation

Identity checks, proof of address, source of funds — financial onboarding is the most constrained flow in consumer software, and the constraints are not an excuse for a bad experience. Editors look for whether the design did the work the regulation didn't require.

Four moves in a regulated sign-up
  1. 01

    Say what's coming

    The whole list, up front, with a realistic time — not a surprise per screen.

  2. 02

    Ask in a sane order

    Cheap questions first; documents when the user is committed.

  3. 03

    Fail gracefully

    A rejected document should say what was wrong with it, specifically.

  4. 04

    Hold the state

    Someone who has to find a passport should return to exactly where they left.

Money in more than one currency

Multi-currency is where finance products most often show whether they were designed or assembled. The score-lifting details are unglamorous: the currency symbol never ambiguous, the rate and the fee shown separately, the conversion timestamped, and historical transactions displayed in the currency they happened in with today's equivalent alongside.

Trust signals that are actually signals

Padlock icons and "bank-level security" copy do very little. What does: naming the protection scheme that covers the money, showing the last sign-in and the devices connected, letting someone freeze a card in one tap, and making the route to a human findable in under ten seconds when something has gone wrong.

Questions we get asked

  • Can a bank enter if the product is only available to customers?

    Yes — tick reviewer access and we'll arrange a test account. It's the norm for financial entries, and a sandbox with realistic transactions is ideal.

  • How are dark patterns judged in fintech?

    Strictly. Pre-ticked insurance, obscured fees, urgency on a credit decision and buried cancellation are scored under ethics, and they pull down the whole entry rather than one criterion.

  • Does compliance with regulation count as accessibility evidence?

    No. Regulatory conformance and WCAG conformance are different things. Send your accessibility statement and audit separately.

  • What's the most common reason fintech entries lose points?

    The transaction list. It's the most-used screen, it's usually inherited from the core banking system, and it rarely gets the design attention the onboarding flow does.

Assessed work in finance

Chosen by score from the work the editors have assessed, not by hand.

  • fintech
  • banking
  • industry

Written by

The UXE editors

The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.