Fintech UX
Fintech UX: seven patterns for money flows people trust
In a money app, trust is decided in a few screens: the amount, the review and the moment something goes wrong. The patterns I use, from designing Corridor.
· 5 min read
People do not trust a money app because it looks premium. They trust it when the numbers make sense, when nothing is hidden and when it behaves well on a bad day. Most of that is decided in a handful of screens: the amount, the review, the confirmation and the first time something goes wrong.
I designed Corridor, a concept app for remote freelancers who get paid from abroad and send money home. These are the seven patterns I relied on. They apply to most fintech products: transfers, investing, payroll and wallets.
1. Lead with the number people actually care about
Most banking apps make the amount you send the headline. The question a sender actually has is "what will my family get?" In Corridor, the amount the recipient receives is the largest number on the amount screen, updating live as you type. The amount you send is the input, not the headline. Whatever your product, find the number behind the user's real question and make it the biggest thing on the screen.
2. Put the terms next to the claim
Fee, rate, rate lock window and delivery time sit on the same card as the amount. No asterisks, no footnotes, no "see details". If a claim needs a condition, the condition goes right next to it, in the same size of text. Hidden terms are the fastest way to lose a user who has been burned by a bank before.
3. One primary action per screen
The step that moves money should be the easiest screen in the product to scan. One filled button: Continue, then Confirm and send. Secondary options are labelled text buttons. I cut quick actions like convert, schedule and split from the review card. Power users lose a tap, and everyone else gets a screen they can check in two seconds.
4. Make sending deliberate, but never only by gesture
A hold-to-send control makes the final step deliberate and prevents accidental taps. On its own, a gesture excludes people. Every hold has a plain button alternative for keyboard, switch and screen reader users. Friction should scale with the cost of a mistake, and it should never be the only way through.
5. Track it until it lands, in plain words
After sending, people want to know one thing: where is my money? Four plain-language steps until it arrives beat a single "Processing" label every time. Each status is written as words and read out by screen readers, not shown only as a colour. Good tracking also has a business case: the target I would set is fewer than 5 "where is my money?" support contacts per 1,000 transfers.
6. Design the bad day first
Money apps earn trust in the bad moments. Before polishing the happy path, I list every failure state and design each one as a real screen:
- ID verification needed, inside the send flow, not as a dead end.
- Recipient name does not match the bank's records.
- Compliance hold, with what happens next and roughly when.
- Returned transfer, with where the money is now.
- Rate lock expired, with the new amount shown before anything is charged.
Looking back, I would start with these instead of ending with them. They shape the review card more than the happy path does.
7. Plain words for money
"Settlement", "beneficiary" and "FX margin" belong in the back office. On screen it is "arrives", "who gets it" and "our fee". Numbers use tabular figures so amounts line up and do not jitter while they update. Small details, but they are what makes an app feel calm instead of risky.
How I would measure it
Corridor is a concept, so these are targets, not results: at least 35% of quotes turning into confirmed transfers, under 30 seconds to send to a saved recipient, 40% of users sending again within 30 days and 80% of ID checks finished in the same session. Each one maps to a single product event, so the team can see quickly whether the trust patterns are working.
The short version: show the number people care about, put the terms beside it, make the money step boring to scan, and design the bad day before the good one.
Related work