01
Check the offer before publishing
Open the event page as a visitor and review the date, starting time, venue and ticket description. Check prices, available quantities and sales periods. With several ticket types, review the total admission you are offering rather than each type alone. Ask someone who did not configure the event to read the page: can they explain what they are buying and which conditions apply before checkout?
- Check the mobile layout, logo and visibility of the checkout action.
- Record who verified venue capacity and the published prices.
02
Test payments in the correct environment
A successful test payment does not prove that live payment processing is configured correctly. Before real sales, check which provider account is connected, whether it is approved for live transactions and which methods appear in your checkout. Distinguish an abandoned payment from a definitively failed or expired order. Check the route back to the booking after payment as well as the payment page itself.
- Confirm whether test or live mode is appropriate for your current stage.
- Have only an authorised person carry out and reconcile an agreed real test payment.
03
Check confirmation, language and exceptions
Complete a full test booking and verify that the ticket email arrives, quantities match and the order shows the correct payment status. Check both Dutch and English visitor journeys when you offer both languages. Test reopening the private order link and resending through the available admin function. Use fictional test details where possible and keep real visitor information out of screenshots shared with a large team.
- Test successful, cancelled and failed payments in the test environment.
- Verify the QR ticket, private order link and contact for questions.
04
Agree a go/no-go and follow-up process
Launch only when the critical journey works and the team knows who handles problems. After the first real orders, check that payment status and ticket delivery match; judge an order by its current status, not merely a return page. Prepare admission with the correct event and scanning permissions too. If something fails, record the symptom before changing settings so you do not introduce a second problem while investigating.
- Assign a payment contact and a visitor-support contact.
- Keep the test results and reuse the checklist for your next event.