Ledger Interface Study
Designing for the specific complexity of fintech onboarding, KYC and payments.
Context and constraints
Fintech interfaces carry a category of complexity general kits don’t: identity verification flows, compliance-heavy onboarding, portfolio and payment states with real regulatory weight behind them. We set an internal brief to design a complete fintech product surface, partly to test whether Foundry UI Core’s foundation could extend into a genuinely specialised vertical, or whether fintech needed a system of its own. No client brief, no external deadline — the test was whether the result would hold up as a real, shippable fintech UI, not a stylised demo.
Decisions
01
KYC as a first-class flow, not an edge case.
Identity verification is treated as a fully designed flow with its own states, rather than a single generic form screen bolted onto onboarding.
02
State density over decoration.
Portfolio and transaction screens favour information density and clear status states over visual flourish, because in this category clarity is the trust signal.
03
180 screens because fintech doesn't compress.
The screen count reflects how many distinct states — verified, pending, rejected, multi-currency, multiple payment methods — a real fintech product actually needs to cover cleanly.
Artifacts
Onboarding flow map
KYC state diagram
Payment state matrix