06 — Checkout
← Handbook · Previous: Themes · Next: Pricing and fees
What it is
The page your buyers pay on. It carries your event's theme, shows exactly what they are buying and what it costs, and takes the payment.
Buyers do not need an account. They enter a name, an email and a card, and their tickets arrive by email and on the confirmation page straight away.
What your buyer sees
- Their tickets and extras, with quantities they can adjust. Anything they picked on your event page is already there.
- A discount code field, if you have any active codes.
- Their details — name, email, and phone if you require one.
- Your required policies, directly above the pay button, with a box to tick.
- Card details, and a pay button showing the exact total.
If something is missing, the pay button tells them what, and takes them to it.
Total price, up front
The price shown is the price paid. Fees are already inside your ticket prices, so there is no surprise line added at the end. See Pricing and fees.
Free orders
If the total is zero — a free RSVP, or a code that covers everything — there is no card step at all.
How it behaves
If something sells out while they are deciding
Nothing is held for a buyer while they fill in the form, so whoever pays first gets the tickets. If a tier sells out in the meantime, their basket is corrected to what is left and they are told what changed.
Nobody is charged for losing a race. The tickets are secured before the card is ever charged, so the buyer who arrives a second too late sees "just sold out" and nothing reaches their card at all.
If a discount stops applying
Codes can expire, run out, or be limited to one use per customer. If a code stops applying between the buyer entering it and pressing pay, they are stopped and told — the code is removed, the new total is shown, and nothing is charged. They decide again with the real price in front of them.
A buyer is never charged a different amount from the one on the button they pressed.
If you change something while they are checking out
- A price — the page refreshes to show the new price before they can pay.
- A required policy's wording — the page refreshes so they can read and agree to the new wording.
Their basket is kept either way.
If their bank asks them to approve the payment
Some cards need approval in the buyer's banking app. Their tickets are held for sixty seconds while they do it, and the page shows them the clock. If they do not finish in time, the tickets go back on sale and nothing is charged.
If their card is declined
They are told straight away, their tickets go back on sale, and any discount code they used is freed up so they can use it on their next attempt.
After they pay
They land on a confirmation page and receive an email with their tickets. Each ticket can be downloaded as a PDF, individually or all together. Add-ons with their own codes can be downloaded too.
The confirmation link is the tickets. Anyone with the link can view the order and download the tickets, which is how a buyer can simply forward the email to a friend. It also means buyers should treat that email like the tickets themselves.
Their tickets also appear in their account. If they bought without one, they can sign in later with the same email address and every order they have made will be there.
Good to know
Their basket is kept while they browse — back to your event page and forward again, or a page refresh. A brand new browser tab starts empty.
Signed-in buyers cannot change their name or email at checkout. Those come from their account, so an order cannot be placed under someone else's name.
Required policies sit right above the pay button on purpose. A rule someone scrolled past is a rule they will say they never saw.
If your payments are not set up, nobody can pay. A paid ticket needs a connected payout account — see Getting paid. Until it is connected, buyers cannot enter a card.