Loan Origination and Lending App UX: Application, Verification and Repayment Flows

The short answer

This is for the product teams who build lending apps and loan origination systems, and for lenders redesigning their own flows. It is not a buyer's guide to lending software.

Design the lending journey as seven stages: pre-qualification, application, identity checks, decision, offer and signature, repayment, and collections. Many teams put their effort on the application form. We think the hardest screens are the two nobody storyboards: the wait for a decision, and the "no". A borrower who understands why they are pending, or why they were declined and what they can do next, may well keep trusting the lender. One left with a spinner or a form letter has little reason to return. That is our argument, not a measured result, so test it on your own funnel.

This page covers lending only. For fintech UX in general, see our overview of fintech UX. Nothing here is legal advice; the rules cited are US federal ones, so check them with counsel for your product and market.

Stage by stage: the question, the decision and the rule

At each stage the borrower is asking one question. Design the screen to answer it, then check which rule constrains the answer.

Application and identity checks

Keep the form to what the decision needs. The Baymard Institute, which publishes form research, found about 11.3 fields in the average checkout in 2024 and argued most sites need only 8, adding that fields drive perceived and real complexity more than step count, and more so on mobile. That study is of retail checkout, not lending, so treat it as a principle to test rather than a lending benchmark. The practical moves carry over: one name field, no address line you do not use, and fields shown only when an earlier answer makes them relevant.

Save and resume is not optional. People apply for loans while finding payslips and bank details. Let them leave and return on another device without losing progress, and say in the screen where they will resume.

Document upload needs a reason beside it. For each request, say what it proves and what a good upload looks like. Show acceptance immediately, or say plainly that it will be reviewed, so the person does not wonder whether it arrived.

Explain identity checks as you go. At each verification step, tell the borrower what is being checked, roughly how long it takes, and what happens if the check cannot complete (a retry, an alternative document, a person). Failure here is common and it is where good applicants drop out, so the failure screen deserves as much design as the success one.

Business borrowers add people. Under 31 CFR 1010.230, covered institutions identify and verify the individuals who own 25 per cent or more of a legal entity customer, plus one individual with significant control. In the interface this becomes a short, guided sub-flow for adding owners, with the reason stated, rather than a surprise form near the end. Exclusions and exemptions exist, so confirm what applies to your product.

The wait: design the pending states

An instant decision is a strength when you can deliver it. When you cannot, the screen after submit becomes the product. A checklist for every pending state:

• Name the state in the borrower's words ("We are checking your income documents"), not the system's ("Processing").
• Say what is happening now and who or what is doing it.
• Give a time expectation, and say what will change it.
• Say whether they need to do anything. If they do, show the action as the primary control; if they do not, say so.
• Say how they will be told the outcome, and let them choose the channel.
• Show the application reference and let them find this screen again.
• Provide a way to reach a person, or a plain statement that none is needed yet.
• When the wait runs past your stated time, change the message. Silence after a promise is the fastest way to lose trust.
• Keep the details they entered visible and correctable where the rules allow.

Instant approval, instant decline, manual review and "we need more information" are four different journeys. Draw all four before you build any of them.

The no: anatomy of an adverse-action screen

Under Regulation B, a creditor must notify an applicant of action taken within 30 days of receiving a completed application. An adverse-action notice must be written and include the action taken, the creditor's name and address, the ECOA anti-discrimination statement and the agency that administers compliance. It must also give either a statement of specific reasons or a disclosure of the right to request them within 60 days. The rule adds that reasons must be specific and state the principal reasons: citing internal standards or a failure to reach a qualifying score is not enough (12 CFR 1002.9). The thresholds differ for business credit, so read paragraph (a)(3) if you lend to businesses.

The legal notice is a floor. The screen is where you decide what the borrower does next. A workable anatomy, top to bottom:

1. The outcome, stated once and plainly. No euphemism, no "we are unable to proceed at this time" without saying it is a decline.
2. The principal reasons, in the borrower's terms. "Your reported income did not cover the repayments on this amount" is usable. "Did not meet our criteria" is the form letter the rule warns against.
3. What would change the answer. A smaller amount, a different term, a co-applicant, a corrected document, a waiting period. Offer a counter only if you can honour it.
4. What you used. If a credit report contributed, say which agency and how to obtain a copy and dispute errors; confirm the exact notice contents with counsel.
5. The required statements, formatted to be read and kept, with a downloadable copy.
6. A next action. Reapply later with a reminder, try a smaller amount, or contact a person. Never leave a dead end.
7. No marketing noise. Do not put a cross-sell on the screen where someone has just been refused.

Offer, disclosures and signature

Regulation Z requires closed-end credit disclosures to be made clearly and conspicuously, in writing, in a form the consumer can keep, and before consummation; electronic delivery is allowed subject to E-SIGN consent (12 CFR 1026.17). Section 1026.18 lists what must be shown, including the amount financed, the finance charge, the annual percentage rate, the total of payments and the payment schedule, each with its prescribed label and brief description (12 CFR 1026.18). "Clear and conspicuous" in the commentary means reasonably understandable and legible without obscuring how the terms relate.

Design consequence: put those figures together on one offer screen, using the required labels, before the signing step. Let the borrower compare amount, term and total cost side by side if you offer choices. Do not make them scroll a legal block to find what they will pay.

The E-SIGN Act adds consumer consent conditions where a law requires information in writing. The consumer must affirmatively consent, after clear statements about paper copies, withdrawal and system requirements, and must consent in a way that reasonably demonstrates they can access the electronic form (15 U.S.C. 7001(c)). Build the consent as its own step with those statements visible, not a pre-ticked box inside the terms.

Repayment: the longest part of the relationship

Origination happens once; repayment can last years. Design for it:

• Schedule. Show each payment, its date, and how much is principal and interest, from the home screen.
• Autopay. Recurring debits from a consumer's account need the consumer's authorisation in a writing signed or similarly authenticated, with a copy supplied, and the consumer can stop a payment by telling the institution at least three business days before it is due (12 CFR 1005.10). Make switching autopay on, off or to another account a visible control, not a support call.
• Early payoff. Show a payoff figure for today and for a chosen date, and say whether anything else applies.
• Hardship. Put a plain "I may struggle to pay" route where people look, before a payment is missed. Say what you can offer and what happens to their record.
• Collections. Treat the first missed payment as a conversation. State the amount, the date, the options and a person to talk to, in a calm tone. Check collection rules with counsel before you write the copy.

Two views, one loan: borrower and loan officer

The borrower's journey is half the product. The other half is the queue the lender's staff work in. A good underwriting view shows the applicant's answers, the documents and the verification results on one screen; marks what is missing and who is waiting on whom; and records why each decision was made, in words that can feed the borrower's reasons screen. For business lending, add the ownership structure as a visual, not a list of names. If the staff view cannot produce a clear reason, the borrower will not receive one.

Keep the two views consistent in language. When the officer sees "income evidence requested" and the borrower sees "We need one more document", the state is the same and the mapping should be deliberate.

Our work on a lending flow

We redesigned onboarding and loan issuance for OctiFi, a Singapore fintech from the Y Combinator 2021 batch that offered instant 0% interest loans when we worked with it, and changed flows to meet regulatory requirements; the details are in the OctiFi case study. More on our fintech work is on our fintech and insurtech page.

Where to start

If you can redesign only one thing, map every state between "submit" and the final outcome, including the declines, and write the screen for each. Then check each against the stage table above. If any state has no screen, a spinner or a generic email, that is your first piece of work.