# Checkout Sessions

 - [POST /checkoutsessions/create](https://docs.shift4.com/apis/payments-platform-rest/openapi/checkout-sessions/checkoutsessionscreate.md): Creates a Checkout Session — the server-side configuration for a single payment attempt. The response carries two fields for collecting payment: `clientSecret` for embedding Payment components on your
 - [GET /checkoutsessions/list](https://docs.shift4.com/apis/payments-platform-rest/openapi/checkout-sessions/checkoutsessionslist.md): Returns a paginated list of Checkout Sessions, most recent first. Pagination and time filters are passed as request headers — `Limit`, `StartingAfterId`, `EndingBeforeId`, `DatetimeAfter`, and `Dateti
 - [GET /checkoutsessions/retrieve](https://docs.shift4.com/apis/payments-platform-rest/openapi/checkout-sessions/checkoutsessionsretrieve.md): Retrieves a single Checkout Session by id. The id is passed via the `CheckoutSessionId` request header. Returns the same envelope shape as Create and List — the current `status`, `lastOpened`/`expires
 - [POST checkoutsessions-notification](https://docs.shift4.com/apis/payments-platform-rest/openapi/checkout-sessions/checkoutsessionsnotification.md): This is an outbound HTTP POST message from the Shift4 gateway to the merchant's environment that provides a status of the checkout session. This notification request is sent to the `webhookUrl` set on