Redirect Checkout

Overview

Redirect Checkout is a checkout flow that sends the customer from the merchant site or app to another page or application to complete payment or authentication. 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.

It differs from hosted checkout as a concept because a hosted page may be opened in several ways, while redirect specifically describes the navigation pattern. A reliable implementation keeps the customer journey simple while maintaining authoritative server-side amounts, explicit state, and recoverable payment and order records. Related operational concepts include Hosted Checkout, Checkout Session, and Checkout Failure, each of which should retain a separate definition and system owner.

It normally interacts with Hosted Checkout and Checkout Session, although the exact system boundaries vary by merchant and platform. Operationally, teams should bind the redirect to a server-created session, protect state parameters, preserve cart context, handle the back button, and verify results through authoritative server events. A reliable implementation keeps the customer journey simple while maintaining authoritative server-side amounts, explicit state, and recoverable payment and order records.

In merchant checkout and e-commerce operations, it commonly covers redirect URL, session state, return URL, provider page, cancellation path, and asynchronous payment confirmation. The concept commonly includes redirect URL, session state, return URL, provider page, cancellation path, and asynchronous payment confirmation.

Controls for Redirect Checkout 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: is a flow that sends the customer from the merchant.