BookRevs

A rider wants to find and book a track day, and to get their money back if it is cancelled. An organizer wants to fill an event, control capacity and be paid. The platform has to hold both positions at once, take its cut, and stay correct when they conflict — because a booking is a financial commitment on both sides.

That is what separates a marketplace from a booking form. Money moves between two parties who do not trust each other, mediated by a platform that has to be able to explain every movement afterwards.

A rider pays the platform; an organizer is paid by the platform. Those are not the same transaction, and treating them as one is how marketplaces end up unable to explain their own balances. Payments run through Stripe with connected accounts for organizers and payment intents for riders, so the money has an owner at every point.

Payment state is decided by the payment provider, not by the application, and it arrives as webhooks. Webhooks retry, arrive out of order, and can be delivered more than once for the same event. A handler that assumes otherwise will double-confirm a booking or double-count a payment.

Received events are recorded, so a redelivered webhook is recognised as one already processed rather than applied a second time.

A track day has hard physical capacity — a finite number of riders can be on a circuit safely. Selling one place twice is not a bug that can be smoothed over afterwards. When capacity is reached, riders join a waitlist rather than being turned away.

Events carry schedules, images, links and optional add-ons that riders select alongside the booking itself, so an add-on is priced and recorded as part of the same commercial transaction rather than bolted on beside it.

Track days are cancelled — weather, circuit availability, an organizer withdrawing. Cancellation is where a marketplace either keeps its riders or loses them, and it is a request with a decision and a financial consequence rather than a button that deletes a row.

Riders self-register and verify with a one-time code. Organizers cannot: an organizer can take other people’s money, so they arrive by invitation with a single-use token rather than by signing up. The two paths are deliberately different because the trust required is different.

European track days are not a single-language market. The application is internationalised across five languages from the routing layer down, rather than having translation retrofitted, which is the difference between adding a market and rebuilding for one.