DameTicket: ticketing with real payments

DameTicket is our own product: a SaaS that lets an organiser create paid events, sell tickets and manage attendees without depending on a marketplace that takes 8 to 10% of every transaction.

The interesting part is not the interface

It is the ordering of side effects. When someone hits pay, the system has to confirm with Stripe, reserve the seat, persist the order, send the email and update inventory, and recover cleanly if any one of those steps fails or is retried.

That is where the decisions holding the product up come from: Stripe Checkout with server-side payment intents, webhook signature verification and idempotent order processing, so a webhook firing twice does not charge twice.

Inventory

The Prisma and MySQL schema is designed for concurrent purchases: seat allocation is wrapped in a transaction, so a high-demand event does not oversell.

The rest

Authentication and authorisation for organisers and buyers, session-aware order history and email ticket delivery. Multi-step event creation with image upload, ticket tier configuration and capacity limits. Deployment with isolated environments, automated migrations, and the Stripe test-versus-live switch tied to the environment.