Skip to content
Clearcurrent — Consumer fintech project preview

Case Study

Clearcurrent

Consumer fintech · United Kingdom

+24%

Comprehension (moderated)

-33%

Mis-tap rate on transfers

94%

Pattern library coverage

Embedded

Compliance design QA

The Challenge

Feature announcements outpaced education screens — users missed safeguards around transfers, and compliance copy felt bolted on rather than designed.

Full write-up

Explainability-first UX for consumer fintech

Clearcurrent needed education surfaces that kept pace with shipping features — especially around transfers, limits, and confirmations — without burying users in compliance walls.

Fintech teams ship fast; regulation and risk teams insist on clarity. When education UI lags, users tap through confirmations they do not understand — generating incidents and churn disguised as "user error".

Pattern library for limits and holds

We built repeatable components for explaining holds, pending states, and retry windows. Language stayed plain; hierarchy carried legal nuance without shouting.

Moderated testing loop

Each pattern shipped with rubric-based comprehension scoring so iterations were comparable sprint-to-sprint. Designers and compliance reviewed recordings together to kill ambiguity early.

Dark mode and trust

Critical flows received contrast passes in dark mode because many users bank at night. Micro animations signalled state changes without gimmicks.

Reporting

Mis-tap indexes on transfers and comprehension deltas are published directionally; revenue stays out of scope for this narrative.

Timeline & outcomes

Live — iterative complianceOct 2023 – Dec 2025

Engagement timeline

  1. Phase 1

    Audit & component gaps

    Oct – Dec 2023

  2. Phase 2

    Explainability library

    Jan – Sep 2024

  3. Phase 3

    Ship & regression testing cadence

    Oct 2024 – Dec 2025

Indexed outcome curve (baseline = early sprint, 100 = latest measurement)
Indexed performance trend

Values are normalised indices for communication only — not revenue or confidential KPIs.

Before / after index — key UX and delivery signals

Task comprehension index

Baseline
56
Outcome
86

Error-prevention score

Baseline
49
Outcome
84

Design QA throughput

Baseline
38
Outcome
78

What We Built

  • Explainability components for limits, holds, and confirmations
  • Pattern library harmonising regulatory language with UI rhythm
  • Moderated testing loops with documented rubric scores
  • Dark-mode polish for trust-critical flows

Tools Used

React NativeStorybookFigmaHotjarLookback

Related case studies

Safety UX is product UX — we treated audits as design inputs, not late-stage stickers.

Engagement charter · Risk-aware delivery

Timeline

Oct 2023 – Dec 2025

Investment

£14,000 – £24,000

Want similar results?

Send Enquiry
WhatsAppBook a Call