By Nick Babich
These eight fintech app design examples show KYC, transfer, card, investing and spend-insight flows screen by screen, noting what each gets right.
Key Takeaways
- Answer four questions before confirm: every money-moving flow below says how much in total, to whom or where, when it lands, and what happens if something is wrong.
- Dates beat ranges: the strongest flows show a calendar date or a time, such as “Arrives Tue, Nov 17,” and explain any shift caused by a weekend, a cutoff or a market holiday.
- Repeat the amount on the button: a button that says “Send $42.50” is a last check the person can’t skip past by habit.
- Show the name the system found: a contact’s payment history or a name returned by the recipient’s bank is stronger reassurance than the text the person typed.
- Insights are sentences first: a spend insight leads with one sentence and one number, then uses a chart only as evidence.
Each example covers one money task in three screens, from the first tap to the confirmation or receipt, and the numbered callouts mark the details that make the flow safe to finish. All eight products are fictional, with invented names and data, and each was drawn for this article in its own visual style. These are design patterns, not legal or compliance advice. If you are planning a product in this space, fintech UX design teams we compare for banking and payments apps are listed separately; this page stays on the screens.
On November 14, 2026, I read the eight organic results Google showed me on the first page for “fintech app design examples” in the US. Six were galleries or template libraries (two Dribbble tag pages, Mobbin, Behance, Pinterest and Figma Community), and two were agency listicles organized by brand. The galleries are good for mood and visual direction. None of the pages I could load is organized by flow, from the first screen of a money task to its confirmation, so that is how this page is organized.
How to Read a Fintech Flow Example
Look past the colors and the card art, and check whether the screen before confirm answers four questions. They are the same questions worth asking of products designed by the UX teams we review for money and banking products, and they work on any screen you save from a gallery or your own app.
- 01 How much, in total: the amount, every fee and any exchange rate, in the currency the person thinks in. Quaylet shows 500.00 USD going in and 8,613.17 MXN coming out on the same screen.
- 02 To whom, or where: a name the person recognizes, ideally one the system checked. Orlomo shows the contact’s name and the number of past payments.
- 03 When it lands: a date or a time instead of a vague range. Saltreef shows two dates: when the money leaves the bank and when it can be used.
- 04 What if it’s wrong: how to cancel, change or report a problem, and until when. Several examples state a cancel window with a time attached.
Identity checks and spend insights don’t move money, so for those two the questions shift a little: what happens to my data, how long will this take, and what can I do right now.
Fintech App Design Examples at a Glance
Use the table to jump to the flow closest to your product. Each row records the answers the flow gives to the four questions, taken from the screens shown below.
8 Annotated Fintech Flows
| # | Product (fictional) | Flow | Screens | How much | To whom or where | When | If it’s wrong |
|---|---|---|---|---|---|---|---|
| 1 | Ostlin (bank account, iOS) | Identity check (KYC) | 3 | No money moves yet | The person: ID, then selfie | “Most checks finish in a few minutes,” plus a notification | Upload a photo when the camera fails |
| 2 | Saltreef (savings, Android) | Bank link and first deposit | 3 | $250.00 from Checking ••4821 | Saltreef Savings | Leaves Mon, Nov 16; usable Tue, Nov 17 | Cancel until 5:00 PM ET, Sat, Nov 14 |
| 3 | Orlomo (payment app, Android, dark) | Send money to a contact | 3 | $42.50, fee $0 | Marcus Bell, 4 past payments | In seconds; receipt says 7:42 PM | “Report a problem” on the receipt |
| 4 | Quaylet (money transfer, web) | International transfer | 3 | 500.00 USD in, 8,613.17 MXN out, fee 4.99 USD | Ana Lucía Ortega, name confirmed by her bank | Arrives Tue, Nov 17 | Free cancel until paid out |
| 5 | Plinthwise (spend management, web) | Issue a virtual card | 3 | $1,500 a month | Elena Marsh; software and cloud hosting only | Expires Mar 31, 2027 | Freeze or edit limits on the card |
| 6 | Furrowly (budgeting, Android) | Monthly spend insight | 3 | $186 over a usual $274 | Eating out, by merchant | October against May to September | “Not now” on the suggested limit |
| 7 | Tabbury (bill split, iOS) | Split a bill, request money | 3 | $134.16 bill; $91.81 requested | Sam Whitley and Lena Park, by item | Reminder Tue, Nov 17 | Edit or cancel before it’s paid |
| 8 | Nestmoor (investing, iOS, dark) | Recurring investment | 3 | $200 a month; $0 trading fee; 0.25% a year | Broad Market Portfolio, from Checking ••0952 | First buy Fri, Nov 27 | Pause anytime; pausing sells nothing |
1. Ostlin: Identity Check (KYC) on iOS
Flow: A new customer opening a bank account scans an ID, takes a selfie and waits for the check, in three screens on iPhone.
What the screens show: The ID screen asks for a driver’s license or passport and captures the photo automatically once it is sharp, with no glare and all four corners visible. A link to upload a photo instead sits under the frame. The selfie screen gives one instruction and says the photo is used once to match the person to the ID and is not added to the profile. The status screen says most checks finish in a few minutes, promises a notification and lists what is ready now and what unlocks after the check.
Why it works: Each screen has one job and says it in plain words. The status screen turns waiting into something useful: the person can explore the app while the check runs instead of staring at a spinner. The note about the selfie answers the privacy question at the moment it comes up.
Watch for: Don’t promise a time you can’t keep. If some checks take a day, say so on the status screen and in the notification, and give people a clear path when a check fails, not just a generic error. For the regulated side of this flow, such as what has to be disclosed and when, see how identity checks, consent and disclosures are designed in regulated products.
2. Saltreef: Bank Link and First Deposit on Android
Flow: A new savings customer connects a checking account and makes a first deposit of $250.00.
What the screens show: Before any bank login, the first screen lists what Saltreef will see and what it won’t, with an option to enter account and routing numbers instead. The amount screen shows “Arrives Tue, Nov 17” right under $250.00 from Checking ••4821. The confirmation is a short timeline: the money leaves the bank on Mon, Nov 16 and is available, and earning, on Tue, Nov 17. A cancel link says it works until 5:00 PM ET today, Sat, Nov 14.
Why it works: The arrival date is part of the decision, not a surprise on the receipt. Two dates instead of one explain the gap people notice when money leaves one account a day before it shows up in another. The manual option keeps the flow open to people who won’t share a bank login.
Watch for: Weekend and holiday dates are where these screens go wrong. Calculate them, don’t hard-code “1 to 3 business days,” and make sure the cancel time includes a time zone.
3. Orlomo: Send Money to a Contact on Android, Dark Theme
Flow: A person sends $42.50 to a friend by phone number, reviews the payment and gets a receipt.
What the screens show: After the number is typed, the app shows the name it found, Marcus Bell, and that the two have four past payments. The review screen lists the source, the $0 fee, “arrives in seconds” and the amount that arrives, and the main button reads “Send $42.50.” The receipt shows the arrival time, 7:42 PM, a reference number for support, the new balance and a “Report a problem” link.
Why it works: Payment history is a quick check that the money goes to the right person, which matters most when a payment can’t be pulled back. The amount on the button is the last chance to catch a typo. The receipt gives the person what they will need if they ever call support.
Watch for: A dark theme needs the same contrast as a light one. WebAIM’s guide to contrast explains the WCAG AA targets: 4.5:1 for normal text and 3:1 for large text. Small gray labels on dark backgrounds, such as fee and timing lines, are the usual failure.
4. Quaylet: International Transfer with an Exchange Rate on the Web
Flow: A person sends 500.00 USD to a recipient in Mexico who receives Mexican pesos, in three steps in a desktop browser.
What the screens show: The quote screen shows both amounts, 500.00 USD and 8,613.17 MXN, the rate of 17.4000 with a countdown that says how long it is locked (29:41), the 4.99 USD fee and the 495.01 USD that gets converted. The recipient screen shows Ana Lucía Ortega and the last digits of her account, with a note that her bank confirmed the name. The review lists every line with a currency code, the arrival date, Tue, Nov 17, and free cancellation until the money is paid out.
Why it works: The person sees the total cost before typing any recipient details, so there is no surprise at the end. A visible rate lock tells them how long the quote holds. The fee is its own line instead of being hidden in the rate.
Watch for: Put a currency code on every amount, not only a symbol, because the same symbol can stand for more than one currency. Decide in advance what the screen says when the lock runs out, and make the new quote obvious.
5. Plinthwise: Virtual Card for an Employee in a Spend Management Web App
Flow: A finance admin issues a virtual card to an employee, Elena Marsh, for software subscriptions.
What the screens show: The setup form prefills a $1,500 monthly limit and names where it came from, the Design team default. It uses an allowed list (software and cloud hosting) rather than a long block list, sets an expiry of Mar 31, 2027 by default and asks for receipts over $75. Before the card exists, a panel reads the rules back in one plain sentence. The issued card shows Freeze and Edit limits right next to it, and the spend so far is $0 of $1,500, resetting Dec 1.
Why it works: The plain-words summary catches mistakes that a form full of fields hides, such as the wrong limit or a missing category. Defaults that come from a named policy are easy to trust and easy to question. Expiry by default stops forgotten cards from staying open.
Watch for: Dense admin screens drift toward tiny text and many columns. Keep the summary sentence even as the form grows, and make sure the cardholder gets the same rules in their own notification.
6. Furrowly: Monthly Spend Insight on Android
Flow: A budgeting app explains why one category, eating out, ran high in October and suggests one optional change.
What the screens show: The first screen is a sentence: “You spent $186 more on eating out than in a usual month.” Under it, the app defines “usual” as the May to September average, $274, and says October came to $460. The second screen shows six months of bars against a dashed usual line, with October highlighted because it is the month being explained, then three rows that explain the jump: nine delivery orders instead of the usual three, and the two merchants with the largest totals. The third screen suggests a $300 limit, with one alert at $240 and a “Not now” button of the same size.
Why it works: The insight answers “what happened” before showing any chart, which is what people open these screens for. Defining “usual” makes the comparison honest. The suggestion is a single action the person can decline without hunting for the exit.
Watch for: Insights turn into a dashboard quickly. Show one category per insight, keep one chart, and don’t send more alerts than the person agreed to.
7. Tabbury: Split a Bill and Request Money on iOS
Flow: A person who paid a $134.16 dinner bill splits it by item and requests money from two friends.
What the screens show: The first screen is the receipt, with avatars showing who had each item and a hint that shared plates are split evenly. The second screen shows what each person owes, Sam Whitley $41.07 and Lena Park $50.74, and two notes: tax and tip follow what each person ordered, 29 cents on every dollar, and the one cent left over from rounding stays with the person who paid. The last screen confirms both requests and offers one reminder on Tue, Nov 17, only to people who haven’t paid.
Why it works: Friends see a split they can check against the receipt, so the request doesn’t start an argument. Stating the rounding rule keeps the total equal to the bill. A single, dated reminder is easier to accept than open-ended nudges.
Watch for: Splitting by item adds taps. Offer an even split as the fast default for groups who don’t care, and keep the item view one tap away for those who do.
8. Nestmoor: Recurring Investment on iOS, Dark Theme
Flow: A person sets up $200 a month into a diversified portfolio, reviews the plan and sees the next buy dates.
What the screens show: The setup screen has one decision per row: amount, how often, which day and which portfolio. The review shows a $0 trading fee and a 0.25% yearly fee, also written in dollars (about $0.50 a year per $200 invested). A note explains that the first buy is Fri, Nov 27 because Thu, Nov 26 is Thanksgiving and U.S. markets are closed, which matches the NYSE holiday calendar. Another note says the plan can be paused or changed anytime and that pausing doesn’t sell anything. The final screen lists the next three buys, with each date shift explained.
Why it works: Fees in dollars are easier to judge than percentages alone. Explaining a holiday shift before it happens stops a support ticket about a “missed” buy. Saying how to pause before the person commits makes the commitment feel smaller.
Watch for: Date rules for weekends and holidays need tests, because they change every year. Keep the plain statement that investments can lose value close to the review, not only in a footer.
What the Eight Flows Have in Common
Different products, palettes and platforms, and the same few habits keep showing up.
- Trust through specifics: names, dates, reference numbers and exact amounts do more for trust than badges or security illustrations. Seven of the eight flows end on a screen with a date or a time on it.
- Plain-language money facts: fees, rates and limits appear as their own lines, in words people use, with the total in the currency they think in.
- Progressive disclosure: each flow asks for one decision per screen and keeps detail, such as the exchange rate math or the rule behind a split, one line away instead of up front.
- A visible way back: every flow offers a way out or a way back, from uploading a photo instead to cancel, pause, freeze, edit and report links, and several say until when it works.
Patterns that cross into compliance, such as disclosures and consent, are covered in the regulated-product guide linked in the first example. For first-run flows outside finance, see eight annotated onboarding flows from the first screen to first value, and for screens across platforms, annotated mobile app screens for iOS and Android.
How to Use These Examples in a Design Review
Copy the at-a-glance table and fill in one row for each money flow in your product. Write what the screen before confirm actually says for each of the four questions, word for word. Empty cells and vague answers, such as “1 to 3 business days” or “fees may apply,” are the places to start. Then walk the flow on a real phone, in dark mode if you support it, and check that the amount, the name and the date are readable at a glance.
FAQ
How do you design a fintech app?
Start from the money tasks people come to do, such as paying, saving, sending or checking spending, and design each one as a short flow that ends in a clear confirmation. Make sure the screen before confirm answers the four questions above, test the flow with real amounts and dates, and plan the failure states as carefully as the happy path.
What are some examples of fintech apps?
Common types include mobile banking and savings apps, payment and wallet apps for sending money to people, international transfer apps, budgeting apps, investing apps and spend management tools for businesses. The eight examples on this page cover each of those types with fictional products.
What is fintech UX?
Fintech UX is the design of how people use financial products, such as accounts, payments, cards and investments. Compared with most apps, the stakes of a mistake are higher, so the work leans on clarity about amounts, recipients and timing, and on easy ways to undo or report a problem.
Conclusion
The eight flows above look nothing alike, and they agree on the parts that matter: say how much, to whom and when before the person confirms, show the name the system found, repeat the amount where the decision is made, and leave a visible way back.
When you collect fintech screens for your next project, save the whole flow, not only the prettiest screen, and check the screen before confirm against the four questions. That one screen tells you more about a money product than its home tab.