Payment page UX UI Design, mockup of two floating iPhones

From Brief to Brand:
Designing a Checkout Experience People Actually Want to Use

Case study no. 02 — the second in an ongoing series where I take a fictional brief and build it like it's real.

Share:

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.

Where it started: the wireframe

Before a single colour was chosen for the project, I started thinking about the wireframes. Structure first.

This stage is less glamorous but arguably the most important. It's where you figure out the logic: how many steps does the user actually need? Where does cognitive load spike? What's the hierarchy of information when someone is about to commit £125.50?
The before/after splits you can see in the project imagery show exactly this process — raw wireframe on the left, finished UI on the right. The bones are identical. Good design scales from greyscale to full colour without losing its shape.
Payment UX Ui Page design - iPhone Frame 1 Payment UX Ui Page design - iPhone Frame 12Payment UX Ui Page design - iPhone Frame 13Payment UX Ui Page design - iPhone Frame 4
Testing it on a real device

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:

  • Touch target sizing.
    Form fields and CTAs need to be large enough to tap accurately under pressure, not just look proportionate on a design canvas.
  • Keyboard behaviour.
    When the numeric keypad triggers for the card number and CVV fields, does the layout still hold? Does the user lose context of where they are in the form?
  • Progress feedback.
    The numbered step indicators with their green validation ticks aren't decorative. They're functional reassurance — they tell the user they're moving forward, one field at a time.
The design decisions worth talking about

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.

The green progress thread. A vertical connecting line runs through the numbered form steps, activating in green as each field is validated. It's a subtle affordance that transforms a long form into a journey with a clear destination. Borrowed from onboarding flows, applied here to reduce abandonment.
The lime CTA. The Pay Now and Add Card buttons use a high-contrast lime green — a deliberate departure from the soft purple gradient of the UI above the fold. In conversion design, your primary action button needs to be impossible to miss without being offensive. Lime against white does exactly that.
HTTPS/SSL confirmation. A small line of text at the bottom of the form: HTTPS/SSL secured connection. Users who notice it feel safer.
Payment UX Ui Page design, mockup of iPhone in use
What this project reinforced

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:

  • Wireframe first.
  • Test on a real device before you call anything finished.
  • Every visual decision should have a functional reason.
  • Trust is earned in small, quiet moments — a tick, a label, a line of security text.
This is post no. 02 in the From Brief to Brand series — a regular look at the projects I'm working on, the decisions behind them, and the occasional thing learned the hard way. There's more coming.