Checkout is the stage of a purchase where a buyer confirms an order, supplies the details needed to pay and receive it, and authorizes the payment. Strictly it runs from leaving the cart to the issuer's approval or refusal, though teams often stretch the word to the whole funnel tail. A checkout must collect a final total with shipping, tax and duties resolved, a contact address, a delivery address where goods ship, a payment method and a credential; anything more serves the merchant. Pressing pay sends the credential through a payment gateway to the issuer, while capture and settlement follow days later. Most consumer jurisdictions require price, seller identity and withdrawal rights before the payment button.
What is checkout, and where does it end?
The strict checkout definition covers one span only: the shopper leaves the cart, and the shopper gets an approval or a refusal. Everything before that is browsing, and everything after it is fulfillment.
The everyday checkout meaning is looser. Teams use the word for the whole tail of the funnel, cart page and confirmation email included, which is why two people comparing checkout numbers are often measuring different things.
Five things a checkout has to collect
A final order total, with shipping, tax and duties already resolved. A contact address, because the receipt and any dispute correspondence go there. A delivery address, if something physical is moving. A choice of payment method. And a credential — card, bank login, wallet token — that a provider can turn into an authorization request.
Anything asked for beyond that list is collected for the merchant's benefit rather than the transaction's. That distinction is where most checkout optimization work begins.
The moment the buyer stops being involved
Pressing pay hands the credential to a payment gateway, which requests authorization from the issuing bank. The answer comes back in a second or two, and the buyer sees a confirmation.
Everything after that — capture, clearing, settlement of the money into the merchant's account — happens days later and without them. Buyers judge a checkout on the two seconds they can see; merchants live with the week that follows.
Where the checkout actually lives
The same five inputs can be gathered on the provider's domain through a hosted payment page, inside the merchant's own layout through an embedded checkout, or skipped almost entirely for a recognized buyer through one-click checkout. Those pages carry the trade-offs in detail; the choice comes down to how much compliance scope and engineering the merchant wants to hold.
Whether an account is required is a separate decision, and guest checkout exists because forcing one costs orders.
Checkout as a legal record
The screen is also where a contract forms. In most consumer jurisdictions the buyer must see the total price, the identity of the seller, delivery terms and any right of withdrawal before the payment button, not after it. Tax has to be displayed the way local rules require, inclusive or exclusive.
Getting that wrong is not a design flaw. It makes the order challengeable and can attract a regulator, which is why cross-border sellers treat a localized checkout as a compliance job as much as a commercial one.