
Case study no. 02 — the second in an ongoing series where I take a fictional brief and build it like it's real.
Nobody opens an e-commerce app hoping the checkout will be memorable. They just want it to work — fast, clearly, without friction. So when DailyUI dropped prompt 002 (design a credit card checkout), I didn't treat it as a UI exercise. I treated it as a trust problem.
Because that's what payment design really is. You're asking someone to hand over their card details. Every decision you make — the colour of a button, the placement of a field, the moment a green tick appears — either builds that trust or erodes it.
Before a single colour was chosen for the project, I started thinking about the wireframes. Structure first.




Here's where a lot of designers skip a step: they design for a screen, not in a hand.
Before I polished a single frame, I loaded the prototype onto my phone and used it. Properly used it — one thumb, real keyboard, real scroll behaviour. And that's where the UX principles moved from theory into practice.
A few things surfaced immediately:
The card visualiser. The credit card component at the top of the screen isn't just a nice touch — it's a UX anchor. As the user fills in their details, the card populates in real time. It converts abstract number strings into something recognisable and familiar.

Checkout UI sits at the intersection of visual design, UX psychology, and conversion optimisation. It's one of the most scrutinised screens in any digital product — and one of the most commonly under-designed.
The principles that kept this project tight: