FinTech UX design for lending and payments, with each status explained

In lending, payments and business finance, our FinTech UX design gives every decline a reason and every failed payment a way forward.

Book a call

  • 2017

    Founded

  • 90+

    Projects

  • 19

    Countries with clients

What we design in FinTech

For founders and product teams in finance, from a first app to one already live with customers.

FinTech and related UX design work

FinTech app design for approvals, statuses and money in motion

Every status tells someone about their money, several people act on one application, and the rules limit what each screen says. So we map every state a loan, payment or claim can reach before drawing any screen.

One status, read the same way by customer and staff

MomentWhat the customer is wondering
Signing up
"Why do you need all this, and how long will it take?"
Applying
"Will I qualify, and what exactly am I agreeing to?"
Waiting
"Is it pending, approved or stuck?"
Paying
"Did that go through, and when will it arrive?"
Approving a payment at work
"Can I sign this off, or does it need someone else?"

Pending, approved, funded, failed and reversed each get a plain label, a short explanation and a next step. When a customer and an operations agent read the same record, they should reach the same answer. Where they differ, the gap becomes a support call.

Approvals with a limit and a name on them

A spend request in a business finance tool, and a credit approval or fraud case in a lender's back office, both wait on someone with the right authority. Their screens answer the same questions: who may approve, up to what amount, what they are looking at and what changes when they act.

When a model helps approve an application or flags a payment, the reviewer sees what the result rests on and can overrule it with a reason. The customer gets the main reasons in plain words, within the limits your compliance team sets.

Loans and payouts that arrive in stages

A loan may fund in stages, a payout lands days after the sale, and a lender may fund some invoices in a request and not others. A bare declined on half a request sends a business owner straight to the phone.

We give each part its own status: what was funded, what wasn't, the reason where your compliance team allows one, and something the customer can do now. That might be adding a document, waiting for their own customer to pay or asking for a review.

Every reason has to make sense on a phone at nine in the evening.

Declines, checks and holds with a way forward

Identity checks required by know-your-customer and anti-money-laundering rules say why they ask, and progress is saved for people who stop halfway. A declined application, a failed payment or a missing document shows what happened and what to do next.

The rules shape the words. Most online card payments in Europe and the UK need strong customer authentication, and credit offers must show their true cost before anyone agrees.

Explanations are becoming a duty as well. US lenders must give the main reasons for refusing credit. The FCA's Consumer Duty expects UK firms to check that customers understand what they are told, and the EU AI Act treats AI credit scoring of individuals as high-risk.

Your compliance team decides what each rule requires. We design how a customer meets it: the wording, the order, the moment it appears and what a staff member sees when the customer calls.

Insurance quotes, claims and underwriter screens

Policyholders meet an insurance product when they buy cover, sometimes at another product's checkout, renew or claim. Underwriters, brokers and claims handlers use it all day.

We design quotes that make cover, cost and terms clear before anyone pays, and claims that show one status at a time and ask plainly for a photo or document.

Underwriter and broker screens sort submissions by what needs a person first. An AI recommendation shows what it rests on, so a professional can check, change or overrule it. Our piece on how a review step hands control back to the reviewer works through an example. Your underwriting and claims specialists set the rules.

What you get when Tcules designs your FinTech product

We take on the customer journeys and the staff screens behind them, for a new product or a live app.

Who does the work

One senior product designer leads it and designs the screens, and an account lead keeps it moving. A researcher joins when a concept needs testing with customers, and design engineers or developers when the work moves into code.

What we need from you

Your compliance or risk lead's time on wording and decline reasons, and the policy rules behind each status. We also need the support calls each status causes, time with customers and with the staff who review cases, and the person on your side who makes product decisions.

Where our part stops

Lending policy, credit models, fraud rules and regulatory sign-off stay with your compliance, risk and legal teams; our designs present their rules clearly. Payment integrations stay with your engineers unless Software Development builds with you.

A concept that needs testing with real users first can start with UX Research or Prototyping & Usability Testing.

What clients say

  • “They deliver the works required on time. They deliberate sufficiently and outline clear thought processes in the flows.”

    Amin NordinHead of Growth, OctiFi

  • “Tcules told us what was really wrong, including the things we didn't want to hear, and then fixed them with us.”

    Akshay VyasCreative Head, Knovos

  • “It was simply the most successful long-distance 3rd party collaboration I have seen. The company is on eye-level or above for the services they offer. Their staff were really good.”

    Roland SailerDirector of Product, Ringier Media Switzerland

Three ways to work with us

Not sure which suits you?

Tell us about the product, and we'll suggest one.

Book a callSee how we work

Tell us what you’re working on

Book a call

Why founders and product teams choose Tcules

See why teams choose Tcules

  • Fluent in SaaS

    Roles, permissions and data-heavy screens need no explaining to us.

  • Idea to launch

    Bring an idea or your own prototype. Designers lead it through to launch.

  • Craft people notice

    Your product stands out from lookalike software and feels effortless to use.

  • Evidence before screens

    We test your assumptions with real users before they become expensive mistakes.

  • Seen your problem before

    Senior designers who've solved problems like yours lead your product and do the work.

  • Start small

    An optional fixed-price pilot lets you try us first, and ongoing work has no minimum term.

See why teams choose Tcules

Other industries

See all industries
See all industries

Tell us which status sends customers to support

Share the product, the step and roughly how often it happens.

Questions about FinTech UX design

Do you make sure our product is compliant?

Your compliance and legal specialists decide what the rules require, and Tcules designs every screen to those requirements: what to ask for, when to explain it and how to show the result. The design makes their rules clear to the customer and to your staff.

How should an app explain AI credit decisions and agent payments?

Give the main reasons in plain words, what the customer can do about each and a route to a person, within limits your compliance team sets. When an agent pays for someone, show what they allowed, a receipt naming the agent and a way to dispute it.

Do you design banking and money management apps?

Yes. Balances, transfers, cards and savings goals need what lending and payments need: one meaning per status, a reason for every block and a clear next step. We design the customer app and the staff tools behind it together.

Can a designer work inside our FinTech team?

Yes, as an ongoing partnership: a senior Tcules designer works in your tools and channels next to your product and engineering people. OctiFi's first design assignment grew into continuing design work on its app. See how ongoing work is set up