# Checkout

> Understand how Paystack Checkout works, from initialization to authorization and verification.

Paystack Checkout is Paystack’s hosted payment completion flow for online transactions. Your server creates the transaction, Paystack presents the payment interface, and your system verifies the outcome before you deliver value.

Checkout is useful when you want Paystack to handle payment collection across supported channels without building and maintaining your own card or channel-specific forms. It gives you a single payment surface for cards, transfers, wallets, and other supported methods while keeping the merchant in control of transaction creation and fulfilment.

There are two common variants.

## Popup

Popup keeps the customer on your site. After your backend initializes the transaction, your frontend uses the returned `access_code` to load Checkout in a modal flow. This works well when you want a seamless web experience and do not want the customer to navigate away from the current page.

## Redirect

Redirect sends the customer to the `authorization_url` returned during initialization. The customer completes payment on a Paystack-hosted page and is then returned to your `callback_url`. This works well when you want the simplest server-driven flow or when your application architecture already relies on redirects.

## How authorization works

A Checkout transaction starts on your server when you call the initialize transaction endpoint. The response includes three values that matter most:

- `authorization_url`: the hosted page for redirect flows
- `access_code`: the token used to resume the transaction in Popup or SDK flows
- `reference`: the identifier you use for reconciliation and verification

After Checkout opens, the customer chooses a payment method and completes any authentication their bank or provider requires, such as PIN entry, OTP, 3DS, or wallet authorization. For the full lifecycle from initialization to verification, see [Payment flow](/payments/concepts/payment-flow).

## What Paystack handles and what you handle

Paystack handles the hosted payment UI, the secure payment session, payment-channel switching, redirects to external authorization pages, and the final transaction processing.

The merchant handles transaction initialization, passing the right amount and customer data, exposing the `access_code` or redirecting to `authorization_url`, receiving the customer back on a callback URL, listening for webhook events, verifying transaction status, and deciding when to ship goods or grant access.

## Key concepts

### `access_code`

A short-lived code returned after initialization. Popup and mobile SDK flows use it to load the exact transaction your server created.

### `authorization`

When a payment succeeds, the verified transaction can include an `authorization` object. For reusable card authorizations, that object becomes the basis for recurring charges and other returning-customer flows.

### `webhook`

A server-to-server event sent by Paystack, such as `charge.success`. Webhooks are the most reliable signal for fulfilment because they do not depend on the customer staying on the page or returning to your app.
