Ankit Mandli
WorkChallengesRedesignsAboutExperienceArtContact
mandliankit2001@gmail.com
WorkChallengesRedesignsAboutExperienceArtContactmandliankit2001@gmail.com
Ankit MandliUI & UX Designer Lead
Based inBhopal, India
Elsewhere
LinkedIn
© 2026 Ankit MandliBack to top ↑
← All challenges

Daily UI #002 · Mobile app

Credit Card Checkout

Luma Store

A checkout that feels familiar, secure and effortless. Review your order and pay with confidence.

Product
Luma Store
Role
UI/UX Designer
Platform
iOS & Android
Challenge
Daily UI #002
Credit Card Checkout: Payment
Credit Card Checkout: Review order

Hover the screens to scroll through them.

On this page

  1. 01The brief
  2. 02Concept
  3. 03The problem
  4. 04Target user
  5. 05UX goals
  6. 06Information architecture
  7. 07User flow
  8. 08Wireframes
  9. 09Payment form
  10. 10Design system
  11. 11Final UI
  12. 12Trust & security
  13. 13Responsive & accessible
  14. 14Key decisions
  15. 15Reflection
01

The brief

Create a simple, trustworthy checkout that lets people pay confidently, with minimal friction.

Daily UI #002

“Design a credit card checkout form or page. Don't forget the important elements such as the numbers, dates, security numbers, etc.”

02

Concept

Luma is a modern store selling premium creative products. A customer has picked a UI Design Kit and is ready to pay: they review the order, choose a payment method, enter card details and confirm the final amount.

Platform
Mobile app, designed at 390 × 844.
Why mobile
Touch-friendly controls, a concise hierarchy, readable fields and one clear payment action.

Core user goal

“I want to pay quickly and know exactly what I'm being charged.”

03

The problem

Checkout is a high-intent but sensitive moment. People abandon when forms are complicated, totals are unclear, security feels uncertain or errors are hard to recover from.

How might we

Make credit-card checkout simple, while giving people enough confidence to complete the payment?

04

Target user

Persona
Arjun, 28 · Product Designer
Goal
Complete an online purchase quickly and confidently.
Needs
A clear total, familiar card fields, secure payment, easy recovery.
Frustrations
Unexpected fees, long forms, unclear errors, failed payments.
05

UX goals

  • Cut unnecessary fields and decisions.
  • Keep the total price obvious.
  • Use familiar payment patterns.
  • Validate details before submission.
  • Offer subtle security reassurance.
  • Communicate processing, success and failure clearly.
06

Information architecture

SectionContent
HeaderBack navigation, Luma brand, “Secure checkout”
ProgressPayment → Review → Complete
OrderProduct, quantity, promo code, subtotal, tax, total
PaymentCard or PayPal, card number, name, expiry, CVV
BillingBilling address, or same as shipping
TrustEncryption and secure-payment reassurance
CTAReview Order · $53.90, then Pay $53.90
07

User flow

  1. Product
  2. Cart
  3. Checkout
  4. Review order
  5. Payment method
  6. Card details
  7. Validate
  8. Pay
  9. Processing
  10. Success or failed
08

Wireframes

Three mobile directions explored before any visual styling.

Three checkout wireframes: A single column, B two section (chosen), C card style
Three checkout wireframes: A single column, B two section (chosen), C card style
A single column · B two section, chosen for its clearer grouping · C card style.
A single column · B two section, chosen for its clearer grouping · C card style.

Selected direction

A structured mobile flow built on the grouped layout, combining the strongest usability ideas from all three.

09

Payment form

Familiar fields in a familiar order, each formatted and validated as it's filled.

Card number
Readable, grouped formatting.
Cardholder
A clear, visible label.
Expiry
MM / YY.
CVV
A security field with contextual help.
Billing
Kept separate from the payment credentials.

The amount is in the button

Product, quantity, subtotal, tax and total are shown before paying, and the button says “Pay $53.90” instead of a vague “Continue”.

10

Design system

Modern, premium, calm and trustworthy. Inter with a strong hierarchy, generous spacing, rounded controls and restrained shadows.

Luma design system: colour palette, Inter type scale, icons, payment marks and component states
Luma design system: colour palette, Inter type scale, icons, payment marks and component states
Colour palette, Inter type scale, icons, payment marks, and buttons, fields and selection in every state.
Colour palette, Inter type scale, icons, payment marks, and buttons, fields and selection in every state.
11

Final UI

Order summary, payment method, familiar card fields, billing, security reassurance and an explicit payment button: premium but restrained, so usability stays first. Hover a screen to scroll it.

  • Payment screen
    Payment screen
    Payment

    Payment

    Order, payment method, validated card fields and billing.

  • Review screen
    Review screen
    Review

    Review

    Everything confirmed in one place before “Pay $53.90”.

12

Trust & security

Subtle cues like “Secure checkout”, encryption messaging and short reassurance that card details are processed securely. Less uncertainty, without the clutter.

Interaction states

StateBehaviour
DefaultEmpty fields with clear labels.
FilledValues are formatted and validated.
ValidA subtle confirmation on each valid field.
ErrorA specific, field-level recovery message.
ProcessingThe button shows progress and prevents a duplicate payment.
SuccessPayment confirmation and the next action.
FailedWhat went wrong, plus recovery or another payment method.
13

Responsive & accessible

Mobile first. On larger screens the same structure expands into payment and order-summary columns without changing the hierarchy.

Treated as core requirements

  • Visible labels and sufficient contrast.
  • A logical focus order.
  • Descriptive error messages.
  • Comfortable touch targets.
  • A clear payment call to action.
14

Key decisions

  • 01

    Mobile first

    For focused, one-handed interaction.

  • 02

    Clear total

    So there's no uncertainty about the charge.

  • 03

    Amount in the CTA

    An explicit action, not “Continue”.

  • 04

    Familiar fields

    Nothing new to learn at the payment step.

  • 05

    Inline validation

    Prevents avoidable payment failures.

  • 06

    Subtle security

    Builds trust without clutter.

  • 07

    Recovery-first errors

    Keeps people moving when something fails.

15

Reflection

Success means people understand the total, find the payment fields, enter details without confusion, recognise valid and invalid input, understand the payment status and recover from common errors.

The main learning: checkout design is about reducing uncertainty. Clear totals, familiar patterns, useful validation, transparent states and a confident call to action make paying feel safer and easier.

The full story

Read the full case study

The complete write-up: brief, user, flow, wireframes, design system, states and reflection.

Download PDF ↓Open in browser

PDF · 4 pages · 409 KB

Next challenge · #003Landing Page →