Wild Society

Ticket and table system with Stripe payments and automatic WhatsApp confirmations, live on wildsociety.space.

Role

Product and development

Year

2026

Context

Venues and nightlife

Context

Table and ticket bookings for club nights, handled the way they almost always are: messages, lists, and whoever remembers who showed up.
Problem

Taking money and confirming a booking were two separate manual jobs, both done at night while everything else was happening.

No certainty about who had actually paid.
Confirmations written out one by one.
Idea

Make the payment the event that triggers everything else, instead of something to reconcile afterwards.
What I built

A FastAPI app with Stripe checkout and a webhook on completed payments that creates the booking and sends the WhatsApp message through Evolution API.

Dashboard showing the real state of the night.
SQLite as the database: small, sufficient, no infrastructure to maintain.
Running in production behind Caddy on port 8100.
Result

The flow closes itself: whoever pays gets confirmed, and the guest list is the real one rather than a reconstruction.
What I learned

The payment webhook is where a product becomes reliable or doesn't. Treating it as the source of truth rather than as a notification simplified everything around it.

Stack

FastAPI · SQLite · Stripe · Evolution API · Caddy