Create ticket sales — sell events directly via forms

For ticket sales, the capacity logic decides on success and frustration. You must prevent more tickets being sold than seats available — especially with sought-after events, hundreds of buyers can sign up in seconds. Therefore define a hard upper limit per category and reserve seats atomically during the checkout process. Stripe itself does not offer inventory management; that lies in your backend responsibility.

For small to medium events, a simple mechanism suffices: on clicking "Buy", the seat is reserved for 10 minutes, during which the buyer must complete the Stripe checkout. If nothing arrives in that time, the seat falls back into the pool. For large events with a run on the sales start, queues are worthwhile — such as a virtual queue that serves buyers in the order of their arrival. Show the remaining capacity live ("12 tickets remaining"). This transparency increases conversion and avoids frustration from sold-out categories at the checkout click.

Stripe Checkout is an almost perfect match for ticket sales. You define a product per ticket category, the buyer chooses quantity and category in the form, the backend creates a Stripe checkout session and redirects to the Stripe-hosted page. There Stripe takes over all PCI-DSS requirements, including credit card, SEPA direct debit and common wallets like Apple Pay or Google Pay.

Rely on the Stripe webhook for the success confirmation, not on the browser redirect. Browsers can crash, connections can drop, buyers accidentally close the tab — the webhook is the reliable source of truth that money has flowed and the ticket may be issued. Build idempotent handlers: when a webhook comes twice, the ticket must not be created twice. Store per Stripe event ID that you have already processed it and ignore repetitions. This small precaution prevents embarrassing double bookings.

After successful payment, the buyer gets the ticket — most practically as PDF with QR code, embedded in a confirmation email. The QR code contains a unique ticket ID that is scanned at the entrance and validated in a small database. This way you avoid forgeries and double uses. Generate the PDF server-side directly after Stripe webhook receipt and send it via email trigger.

Design the ticket PDF readable and mobile-friendly. Organizers often scan QR codes directly from guest smartphone displays, so the code should be large and high-contrast. Add the most important info in plain text: event name, date, time, venue, category, ticket ID. For events with personalized tickets, add the buyer name — this hampers ticket touts and enables personal reception. Additionally offer an ICS file for download or as attachment so that the appointment moves directly into the calendar. These small convenience features noticeably differentiate you from mass platforms.

Despite all care, cancellations occur — illness, weather, conflict with other appointments. Define a clear cancellation policy and communicate it transparently before purchase: up to 14 days before the event 100 percent refund, up to 7 days 50 percent, after that nothing. This staggering is market-standard and protects you from short-term cancellations without seeming unfair.

The technical handling runs cleanly via the Stripe API. Per cancellation, you initiate a refund object with the corresponding share, Stripe processes the chargeback automatically. Mark the ticket in your own system as cancelled so that it no longer works at the entrance, and release the seat in the inventory again. Send a confirmation email with the refund amount and the expected processing time (Stripe needs 5 to 10 business days depending on the card). For full events, you can automatically offer freed seats to waiting list interested parties — a short trigger email with click-to-buy link suffices. This mechanism fills events significantly better than manual rebooking.