---
title: "Checkout"
description: "What a buyer sees from choosing seats to receiving tickets, and where to send them after payment."
---

Checkout opens from the seat picker on your website or the hosted event page.
It works the same on both and reads the same live inventory.

## What the buyer sees

<Steps>
  <Step title="Seats held">
    After **Continue to checkout**, the seats are held for the buyer. The
    **Checkout** card shows **Seats held for** a countdown, which turns amber
    under two minutes. If time runs out, the seats are released and the buyer
    can choose again.
  </Step>
  <Step title="Order and details">
    **Your order** lists every seat with its section, row, ticket type and
    price, and the total stays in view. The buyer enters an **Email**, which is
    where the tickets go, and optionally a **Name**. Events can ask for a name
    on each ticket or a few questions. On a phone the card opens as a bottom
    sheet.
  </Step>
  <Step title="Pay on your gateway">
    **Continue to payment** takes the buyer to your gateway's payment page. A
    free event shows **Confirm booking** instead and skips payment.
  </Step>
  <Step title="Tickets">
    The buyer sees **Your tickets are confirmed**. The tickets and QR codes go
    to their email with a printable PDF, and a link opens them at any time
    without logging in.
  </Step>
</Steps>

## Test mode

On a test event, the button reads **Continue to test payment** and the card
shows **No real charge · tickets not valid for entry**. Use your gateway's test
cards.

## After payment

Choose where buyers land in **Setup → After payment**: the SeatLayer
confirmation page, or back on your own page. Buyers are only sent back to a
website you have saved for your organization.

## Languages and themes

Checkout follows the buyer's language in 37 languages and supports light and
dark themes.