Mobile Checkout Design: 11 Patterns That Convert
Mobile checkout design patterns that reduce abandonment: guest checkout, wallet pay, smart forms, clear totals and error handling, with specs and a checklist.

This is for founders, PMs and designers building a shopping, food, ticketing or booking app who want the checkout to stop leaking customers. You will get 11 proven patterns, the field-level specs behind them, and a checklist to audit your current flow screen by screen.
TL;DR: Most checkout losses come from surprise costs, forced account creation, long forms and payment friction. Show the full price early, allow guest checkout, put Apple Pay and Google Pay first, cut fields to the minimum, and validate inline. Keep the flow to as few screens as the order genuinely needs, and make the pay button impossible to miss.
Why mobile checkout design matters so much
Baymard Institute's long-running research puts average documented online cart abandonment at roughly 70%. Some of that is window shopping and price comparison you cannot fix. But Baymard's surveys consistently find a large share of abandonments are caused by the checkout itself: extra costs revealed late, being forced to create an account, a process that feels too long or complicated, and not trusting the site with card details.
On a phone, each problem is amplified: keyboards cover half the screen, card numbers are error-prone, and app-switching for a one-time code can lose the session. Good mobile checkout design is mostly about removing work.
The anatomy of a mobile checkout
A typical flow has four stages. Not every app needs all of them as separate screens.
| Stage | Job | Can it be merged? |
|---|---|---|
| Cart | Review items, change quantities, see costs | Often merged into a bottom sheet in food and quick-commerce apps |
| Shipping or delivery | Address, delivery slot or pickup choice | Pre-filled for returning users |
| Payment | Wallet, saved card or new card | Merged with review in a one-page checkout |
| Review and pay | Final total, terms, place order | Often the same screen as payment |
| Confirmation | Reassure, show order number and next steps | Always its own screen |
Apps like Uber Eats and Deliveroo collapse delivery, payment and review into a single scrollable screen for returning users, because the defaults are already known. Retail apps with variable shipping often keep a separate address step. Both are fine; the rule is that every screen must earn its place.
11 mobile checkout patterns that work
1. Show the real total before checkout starts
Shipping, service fees, taxes and minimum-order charges are the top reason for abandonment in Baymard's surveys. Show an estimated total in the cart, including delivery cost, and repeat it on every later step. If tax depends on address, say "Tax calculated at next step" next to the subtotal rather than leaving it out silently.
2. Offer guest checkout, prominently
Forcing account creation before purchase loses buyers. Put "Continue as guest" at the same visual weight as "Sign in," not as a small link below. You can offer to save details after the order is placed, when the user has the most goodwill and you already have their email.
3. Put express wallets first
Apple Pay and Google Pay replace an entire form with one authentication. Place the wallet button at the top of the payment step, and also in the cart for single-tap checkout. Follow each platform's branding rules: Apple requires its official button artwork and minimum sizes, and Google Pay has equivalent brand guidelines. Do not recolor or redraw them.
4. Cut every field you can
Each field is a chance to give up. Ask yourself whether you need it for this order.
- •One "Full name" field instead of first and last, unless your carrier requires both.
- •Hide "Address line 2" behind an "Add apartment, suite, etc." link.
- •Skip "Company" for consumer apps.
- •Use the billing address = shipping address default, with a checkbox to change it.
- •Ask for phone only if delivery drivers need it, and say so.
5. Use the right keyboard and autofill for every field
This is one of the cheapest conversion fixes in mobile design. Set the correct input type and autofill hints so the OS can do the typing.
| Field | Keyboard | Autofill hint (iOS / Android) |
|---|---|---|
| Email keyboard | emailAddress / emailAddress | |
| Phone | Phone pad | telephoneNumber / phone |
| Card number | Number pad | creditCardNumber / creditCardNumber |
| Expiry | Number pad, auto-insert slash | creditCardExpiration / creditCardExpirationDate |
| CVC | Number pad | creditCardSecurityCode / creditCardSecurityCode |
| Postcode | Numeric or default, by country | postalCode / postalCode |
| One-time code | Number pad | oneTimeCode / smsOTPCode |
Enable card scanning with the camera where your payment SDK supports it, and auto-detect card brand from the first digits so users never pick "Visa" from a dropdown.
6. Use address autocomplete, but allow manual entry
Address lookup turns a five-field form into one search. Always include "Enter address manually," because autocomplete fails on new buildings, rural addresses and some countries' formats.
7. Validate inline, kindly and late
Validate a field when the user leaves it, not on every keystroke, and never wipe what they typed. Put the error message directly under the field, in plain language: "Card number looks one digit short" beats "Invalid input." Keep the error color at sufficient contrast; you can check it with our contrast checker.
8. Make the primary button persistent and specific
Pin the pay button to the bottom of the screen above the home indicator, with the total in the label: "Pay $42.80" or "Place order · $42.80." Keep it at least 44 pt tall on iOS and 48 dp on Android, full width minus side margins. A specific label reduces hesitation because users know exactly what tapping does.
9. Show progress only when there are real steps
A three-step indicator (Delivery, Payment, Review) helps on multi-screen flows. On a single-page checkout it adds clutter. If you use one, let users tap back to completed steps without losing data.
10. Add trust where anxiety peaks
Next to the card fields, not in the footer, show: accepted card logos, a short line on secure payment, the return or cancellation policy in one sentence, and support contact. Keep it brief. Badges everywhere look like a scam; one clear reassurance at the payment field looks professional.
11. Handle failure without losing the order
Declined cards, 3-D Secure challenges and network drops are normal. Design the states:
- •Declined: keep everything filled, explain in plain words, offer another method.
- •3-D Secure or bank app redirect: show a waiting state that explains what is happening and returns the user to the same screen.
- •Network loss: never charge twice; show a "Checking your order" state and confirm before allowing a retry.
- •Out of stock or price change: highlight the changed line in the cart, not as a generic error.
The confirmation screen is part of checkout
Treat confirmation as the first screen of the post-purchase experience. Include the order number, what was bought, the total charged, the delivery estimate, and one next action (track order, add to calendar, view ticket). Offer account creation here for guests with a single password field, since you already have their email.
Platform-specific details
| Detail | iOS | Android |
|---|---|---|
| Wallet | Apple Pay sheet, official button | Google Pay, official button |
| Bottom actions | Respect the home indicator safe area | Respect gesture navigation insets |
| Minimum tap target | 44 × 44 pt | 48 × 48 dp |
| Back behavior | Edge swipe back must not discard the form | System back must not discard the form |
| Keyboard | Use a toolbar with "Next" and "Done" | Use IME actions "Next" and "Done" |
For layout spacing around these elements, see our mobile app spacing system. If you are mapping the whole purchase journey, our e-commerce user flow post covers browse to checkout end to end.
Worked example: a five-screen grocery checkout, reduced to three
Here is how the patterns above simplify a common flow.
Before: Cart → Sign in or register → Address form (8 fields) → Delivery slot → Payment form → Review → Confirmation.
After:
- •Cart sheet: items, quantity steppers, delivery fee, estimated total, express wallet button and "Checkout" button.
- •Checkout screen: email (guest), address search with saved address pre-filled, delivery slot chips, payment method row showing the wallet or saved card, totals block, pinned "Pay $38.20" button.
- •Confirmation: order number, slot, total, "Track order" button, optional "Save details" password field.
Seven screens became three, and returning users can complete the order with two taps and a Face ID scan. You can generate a first draft of a flow like this in floow, then compare variations side by side before committing to one.
Mobile checkout design audit checklist
Run through this on a real phone, with a new account and a returning account.
- • Delivery fees and estimated total visible in the cart
- • Guest checkout offered at equal prominence to sign-in
- • Apple Pay and Google Pay shown first where available
- • No more than the fields needed to fulfil this order
- • Correct keyboard type and autofill on every field
- • Address autocomplete with manual fallback
- • Errors shown inline under the field, input preserved
- • Pay button pinned, specific and showing the total
- • Trust note next to the card fields
- • Declined, 3-D Secure and offline states designed
- • Back navigation never clears entered data
- • Confirmation shows order number, total and next step
- • Works at the largest text size and in dark mode
FAQ
How many steps should a mobile checkout have?
As few as the order requires. Many food and quick-commerce apps manage with a cart plus one checkout screen; retail with variable shipping often uses two or three. Baymard's research suggests the number of form fields matters more than the number of steps, so reduce fields first.
Is a one-page checkout better than a multi-step one?
A one-page checkout works well when most data is pre-filled or short, especially for returning users. Multi-step can be clearer when each step has real decisions, such as shipping speed or gift options. Test with your own users; both can convert well when each screen is short.
Should I force users to create an account before checkout?
No. Forced account creation is one of the most common abandonment reasons in Baymard's surveys. Offer guest checkout and invite people to save their details on the confirmation screen.
Where should the Apple Pay button go?
At the top of the payment options and, ideally, in the cart for express checkout. Use Apple's official button style and keep it at least as prominent as your own pay button.
How do I reduce errors when users enter card details?
Use number pads, auto-format card numbers into groups, detect the card brand automatically, insert the slash in expiry dates, support camera scanning where possible and validate on blur rather than on every keystroke.
Design it with floow
Sketch your checkout in floow and iterate on variations before your developers touch the payment SDK. Paste this prompt to start:
Design a 3-screen mobile checkout for a grocery delivery app: a cart bottom sheet with quantity steppers and delivery fee, a single checkout screen with guest email, address search, delivery slot chips, Apple Pay first and a pinned "Pay $38.20" button, and a confirmation screen with order tracking.
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Insights17 November 2026Recipe App Design: Search, Cook Mode and ListsRecipe app design guide: the core screens, ingredient scaling, hands-free cook mode, smart shopping lists and search filters, with specs and copyable prompts.By floow.design
Insights17 November 2026How to Make an iPhone App: Design, Build, ShipHow to make an iPhone app step by step: scope it, design iOS screens to Apple's rules, pick SwiftUI or cross-platform, test in TestFlight and pass App Review.By floow.design
Guides16 November 2026User Flow Diagram: How to Make One, With App TemplatesHow to make a user flow diagram step by step: notation, happy and unhappy paths, tools, and copy-ready templates for sign-up, checkout and booking.By floow.design