Checkout Session

Overview

A checkout session is a temporary stateful record that groups the customer, cart or line items, amounts, currency, configuration, progress, and payment context for one checkout attempt. For operational use in checkout and order conversion, teams should identify the object being described, the system of record, the event that creates it, and the outcome it is allowed to influence.

Asynchronous methods may leave the session complete from an interface perspective while the payment remains pending, requiring a separate payment state. A checkout session differs from a cart and from a Customer Order. For clearer boundaries, compare Presentment Currency with Customer Order; they may share identifiers while representing different stages or responsibilities.

The cart represents selections, the session coordinates the checkout attempt, and the order records the committed commercial outcome. One cart can create several sessions, but duplicate completion should not create several orders. Operational records should preserve session ID, client reference, cart, customer, line-item snapshot, amount, currency, status history, payment attempts, order, timestamps, and expiration.

One cart can create several sessions, but duplicate completion should not create several orders. Risks include session reuse after price changes, exposing secret identifiers, duplicate sessions, accepting client-modified amounts, and losing the order link after redirect.

Controls for Checkout Session should bind every customer-visible instruction to server-side state, verify asynchronous payment evidence independently, make order creation idempotent, monitor abandonment and failures, and route uncertain results to a documented recovery queue. Support staff should be able to explain the status without creating a second order or payment action. The audit scope should also preserve its distinguishing context: A is a temporary stateful record that groups the customer.