Full credit chain on display
The visible information architecture gives a clean story from merchant setup to underwriting decision support.
FinTech and Lending/merchant/overview5 screens
Loan Dating Dashboard
Merchant finance dashboard covering onboarding, KYC, inventory, cashflow, scoring, credit reports, proposals, and underwriting flows.
Screen walkthrough
A fuller gallery for the product story.
This gallery shows progression, not just a single hero frame. Use it to talk through navigation depth, records, analytics, and workflow context during a call.
/merchant/overview
Screen 01
Primary interface capture used for the listing card and story lead.
Overview
This is one of the clearest product demos in the set because the navigation exposes the full lending journey. The interface moves from onboarding and KYC through trading and inventory signals into scoring, loan application, proposal packaging, and bank underwriting surfaces.
Strongest story angle
Frame it as a credit workflow product for SMEs where merchant data, risk analysis, and underwriting are connected instead of fragmented across teams.
Observable modules
OverviewOnboarding and KYCTrading EngineInventoryCashflowScoringCredit ReportLoan ApplicationProposal PackUnderwriting
Why this one works
Three angles worth carrying into the final write-up.
Strong SME narrative
Merchant ops, trading data, and program logic position the product around real business cashflow rather than generic consumer lending.
Good fit for fintech case-study depth
This product can carry a more detailed narrative because the modules already map cleanly to commercial credit operations.
Motion outline
This sequence can still become a short teaser.
- 01
Start on the active merchant and overview dashboard.
- 02
Step through KYC, cashflow, scoring, and proposal modules with guided labels.
- 03
Close on the lending storyline: data-rich underwriting for SME finance.
Next publishing pass
The structure is now cleaner: better screenshots, stronger conversion paths, and shared page chrome that behaves correctly. The next layer is adding repository-backed build notes and verified outcome data.
Still worth adding
- 1. Verified repository context for stack and architecture notes.
- 2. Approved proof points to replace generic performance language.
- 3. Short teaser renders once the repository evidence is in place.