Fintech UX — Design for Money

When users trust a screen with their money, every pixel carries weight. A misalignment that reads as "a little off" in a social app reads as "I don't trust this" in a banking app. Financial stress changes how people use software: they check balances at 2am, they abandon KYC flows at the first confusing step, they read a failed payment as "where is my money?" — and the interface either answers or loses them.

This skill applies whether you're building money UI, auditing it, or designing a flow. It's judgment, not a checklist: every rule below exists because violating it costs trust, money, or both.

The Seven Laws of Money UI

1. Trust is the product. Features are why users arrive; trust is why they stay. Every decision either deposits or withdraws from the trust account — and trust is built in drops, lost in buckets.
2. Calm is functional. Financial anxiety is a usability bug, not a mood. Muted palettes, generous space, deliberate motion, and no alarm styling on ordinary events.
3. Numbers are sacred. Tabular figures, explicit signs, honest precision, visible "as of" freshness. Never rounding theater, never a jumping digit.
4. Say if money moved. Every error, timeout, and ambiguous state answers the user's only real question first: did money leave my account?
5. Irreversible actions get explicit confirmation. The CTA names the action and the amount ("Send $250.00 to Alex Rivera"), never "Confirm."
6. Compliance is a design material. KYC, disclosures, and consent are moments to design — explained steps convert; walls of forms abandon (Signicat's Battle to Onboard research measured 63–68% abandonment of badly-designed financial onboarding).
7. Accessibility is law, not polish. ADA / Section 508 / WCAG 2.2 AA are legal obligations for financial services. 48px targets for money actions, announced amounts, 200% zoom, no color-only status.

Modes — each has a contract, not just a posture