Use the supported event ticketing journey to manage admission to your sporting occasion. Keep payment setup, customer orders and entry checks distinct from competition registration and group RSVPs.
Create the event through its existing setup workflow and configure the supported admission options. Publish clear date, venue and ticket information. Event availability alone does not mean an organiser has completed the payment and eligibility steps needed for purchasable tickets.
Use the supported checkout and provider-confirmed order state. A customer returning from checkout is not independent proof of payment. Review orders, refunds and the actual event configuration through authorised management controls rather than reconciling sales from public messages.
Use the supported ticket and QR admission workflow for the event. Assign appropriate entry staff and keep attendee information restricted. A group RSVP or combat athlete registration is not an admission ticket, even when all three relate to the same show.
Fictional demonstration
A fictional club prepares a presentation event, verifies its eligible checkout setup and directs customers to the public event page. Entry staff use the authorised admission tools on the day.
Sign in and use the existing event creation workflow. Check eligibility, dates, venue information and any ticket or payment requirements. Review the public destination before promoting it, and give staff the appropriate access rather than sharing owner credentials.
Check how this fits your club, website or event before getting started.
No. Event eligibility and payment configuration have their own requirements. Review the existing setup before promoting sales.
No. An RSVP records a response, while ticket orders follow the supported event and payment workflow.
Use the existing setup workflow to choose your identity, review eligibility and prepare the information you want to publish.
