> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fast Checkout

> Speed up large group bookings by collecting only the booker’s contact and payment details at checkout, with participant details completed after purchase.

Fast Checkout shortens checkout for group bookings. When a participant buys at or above a minimum number of tickets you set, they pay with just their **contact and payment details** instead of completing a form for every participant — the per-participant race-day details are filled in after purchase. This removes the biggest drop-off point for groups: filling in many forms before paying, which is why it lifts conversion on larger bookings.

## Fast Checkout use cases

Fast Checkout helps most where someone books several entries at once — a running club captain entering their members, a company booking a team, a group of friends signing up together.

* **Set the minimum where a booking becomes a "group."** Five tickets is the common threshold, but choose what fits your event.
* **Use it on tickets people buy in bulk.** There's little benefit on a ticket almost always bought one at a time.
* **Have a plan to collect participant details later** (see [Collecting participant details after purchase](#collecting-participant-details-after-purchase)).

## Setting up Fast Checkout

Fast Checkout is configured per ticket, in the ticket's **Fast checkout** section.

**1. Open the ticket's Fast checkout section**

Edit the ticket and find the **Fast checkout** section.

**2. Turn on Enable Fast Checkout**

Switch on **Enable Fast Checkout** for this ticket.

**3. Set the minimum ticket quantity**

Set the **Minimum ticket quantity** — the number of this ticket a participant must select to use Fast Checkout.

**4. Save**

Save the ticket.

## Participant experience

When a booking meets the minimum, the booker enters their own contact and payment details, pays, and the booking is confirmed — with no per-participant form first. Below the minimum, the same ticket falls back to normal checkout, with a details form for each entry. So how a ticket behaves depends on how many a person buys.

## Collecting participant details after purchase

Because participant details are gathered after purchase, plan how you'll collect them. Entries are paid and confirmed, but race-day details may be blank until someone completes them.

Let bookers know they (or their participants) need to finish each entry's details, and set a deadline that leaves you time before the event. If you rely on those details for fulfillment — start lists, waves, merchandise sizing — chase any that are still incomplete as the event approaches.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.