UX guidance
Screen-by-screen guidance for building your customer-facing lending journey
How to present iwoca's lending flow in your UI. This guide covers what to show, what to hide, and what each user action should trigger.
Customer form
Key decisions
Application form
Key decisions
Offers screen
What to show vs hide
| Show | Hide |
|---|---|
| Offer amount | probability_of_offer |
| Duration | offer_type label (treat all the same visually) |
| Monthly interest rate | Other internal fields |
| Transaction fee | |
| Total repayable (confirmed only) | |
| Monthly repayment (confirmed only) |
normal_repayment_amount and total_repayable are only available when offer_type is confirmed.
For sample and indicative offers, don't show repayment amounts.
Offer hierarchy
Each offer type supersedes the previous as more data becomes available. Your UI should always show the latest offers – earlier ones become irrelevant.
Button behaviour
Decision outcomes
After a customer submits their application, three outcomes are possible. Your UI should handle each clearly.
Offers are ready. Direct the customer to your offers screen or to iwoca via login link to review and draw down.
iwoca is assessing the application. Show a confirmation message and set expectations on timing. The customer can check back via iwoca's platform.
iwoca did not approve the application. Show a clear message with iwoca's contact details. Do not reveal internal decline reasons.
If iwoca declines the customer, do not show reasons from the API. Display a generic message and direct them to iwoca's support if they have questions.