Checkout

On this page 7

Checkout is the final stage of an online purchase, in which the buyer confirms the cart, provides delivery and billing details, selects shipping and payment, and places a binding order. In e-commerce checkout and payments, it is the point where browsing turns into revenue and where payment authorization, fraud checks and legal confirmation all happen within a few seconds.

Checkout is also the stage with the highest commercial sensitivity. Every extra field, surprise cost or failed payment at this step loses a buyer who had already decided to purchase, which is why checkout design is a discipline of its own.

How the checkout process works

A checkout runs a fixed sequence of data collection and validation steps, even when the interface shows them on a single page. Each step must succeed before the order can be created.

StepWhat happensKey validation
Cart reviewItems, quantities and discounts confirmedStock availability, coupon rules
Contact and identityEmail or account login, optional guest checkoutValid email format
Delivery detailsAddress and shipping method selectedAddress verification, shipping eligibility
TotalsShipping, taxes and fees calculatedCorrect tax for destination
PaymentCard, wallet, bank transfer or other methodAuthorization, 3D Secure where required
Order placementOrder created, confirmation shown and sentIdempotency to prevent duplicates
Typical checkout steps

Behind the interface, the store passes payment data to a payment gateway, which forwards it to the payment processor and the card networks. Card numbers are usually captured in hosted fields or a redirect controlled by the payment provider and replaced by a token, so the store never handles raw card data. This design reduces the merchant’s PCI DSS scope.

Checkout formats and their trade-offs

Checkout formats differ in how many screens the buyer sees and who hosts the payment step. There is no universally best format; the right one depends on the audience, order complexity and payment methods.

FormatDescriptionAdvantageDrawback
One-page checkoutAll fields on one screenFewer page loads, clear overviewCan look long on mobile
Multi-step checkoutSeparate screens per stageFocused steps, easier error handlingMore points where buyers can leave
Express checkoutWallet buttons that prefill dataVery fast on mobileDepends on wallet adoption
Hosted checkoutProvider-hosted payment pageLower compliance burdenLess design control, redirect
Guest checkoutPurchase without an accountRemoves registration frictionWeaker customer data for retention
Common checkout formats

Most mature stores combine formats: express wallet buttons at the top, a guest option, and a short standard form for everyone else, with an account offered after the order is placed.

Checkout compared with the cart and the payment gateway

Checkout is often confused with neighboring components. The shopping cart holds intent, the checkout collects commitment, and the payment gateway moves money. Each is owned and optimized differently.

ComponentMain jobMain risk
Shopping cartCollect items and show running totalsAbandonment before checkout starts
CheckoutCollect details and confirm the orderFriction, surprise costs, form errors
Payment gatewayTransmit and authorize payment securelyDeclines, downtime, fraud
Order confirmationRecord the contract and inform the buyerMissing or duplicated orders
Checkout and related components

The boundaries matter for measurement. Cart abandonment and checkout abandonment are separate metrics with different causes: the first often reflects comparison shopping, while the second usually signals friction, missing payment methods or surprise costs. Treating them as one number hides where the real problem is.

Payment outcomes also need their own tracking. A buyer who submits the form but receives a soft decline from the issuer has not abandoned anything; the order failed. Monitoring authorization rates by payment method separates design problems from payment problems.

Designing a checkout that converts

Checkout design rests on a few well-established principles: show the total cost early, ask only for necessary data, and make errors easy to fix. Usability research consistently identifies unexpected extra costs, forced account creation and long forms as major reasons for abandonment.

DecisionRecommended practiceReason
Shipping costsShow before checkout, ideally on product pagesPrevents surprise at the last step
Account creationOffer guest checkoutForced registration drives buyers away
Form fieldsRemove optional fields, use address autocompleteLess typing, fewer errors
Payment methodsMatch local preferencesPreferred methods vary strongly by country
Error messagesInline, specific and preserved inputBuyers fix errors instead of leaving
Trust signalsClear return policy and secure payment cuesReduces hesitation at payment
Checkout design decisions

In the European Economic Area, Strong Customer Authentication under PSD2 often requires 3D Secure for card payments. A well-integrated flow uses exemptions and frictionless authentication where the issuer allows them, so that the extra step appears only when it is needed.

Common checkout failures

  • Duplicate orders when buyers click twice and the system lacks idempotency protection.
  • Stale stock that allows payment for items already sold out elsewhere.
  • Tax or shipping miscalculation for foreign addresses, which leads to refunds or losses.
  • Broken mobile layouts where keyboards hide fields or buttons.
  • Silent payment failures that show a generic error without telling the buyer what to do next.

In everyday language

Checkout is the online version of the cash register. The buyer has already picked the products; now the shop asks where to send them and how the buyer wants to pay.

A good checkout is like a short, fast line at the register: no surprises in the price, no unnecessary questions, and a clear receipt at the end. A slow or confusing checkout makes people put their basket down and walk away.

Seen in the real world

An online home goods store sees that about two thirds of carts are abandoned, and its analytics show the largest drop on the shipping step. The checkout required account registration and revealed a shipping charge only after the address was entered.

The team adds guest checkout, shows a shipping estimate in the cart, enables wallet buttons for mobile users and turns on address autocomplete. The form shrinks from fourteen fields to eight. Over the following weeks, the share of buyers who complete checkout rises noticeably, with the clearest gain on phones, and support requests about unexpected costs almost disappear.