Event Registration
An admin creates the event once. From there the public signs up, Stripe takes payment, and a webhook confirms the seat. No human touches the money path.
One setup step, then hands off
The only human step is the first one. Everything between a visitor clicking register and a confirmed seat in the admin hub is automated.
How each step works
Name, date, capacity, price. The event is defined once in the admin hub, and that definition drives everything downstream: the public page, the checkout, and the registration list.
A public signup page is generated from the event record. There is no second copy of the details to keep in sync, so the page can never disagree with the event.
Registration and payment are one motion. The attendee checks out through Stripe, which handles cards, receipts, and compliance. Nobody at Edge8 ever sees or handles card details.
When Stripe confirms the payment, its webhook writes the registration into the system. The seat is only counted when the money is real, so the attendee list and the revenue never diverge.
Every confirmed registration appears in the admin hub as it happens: who registered, when, and capacity remaining. Event day starts with a list that is already correct.
The seven elements
Every workflow we document has the same anatomy: seven elements, each assigned to a human, a machine, or both. This is the Centaur Map from our workflow design method.
An admin creates the event once; from then on, each registration is triggered by an attendee.
The event record: name, date, capacity, price. One definition drives everything downstream.
Is the payment confirmed? Stripe answers, and the answer is the only thing that creates a seat.
The webhook writes confirmed registrations into the system, seconds after checkout.
A confirmed seat tied to a real payment. Attendance and revenue are the same number.
Receipts go out through Stripe; the live registration list updates in the admin hub.
Registrations against capacity and revenue per event, visible as they happen.
The standing rules
- The event record is the single source for page, price, and capacity
- No payment, no seat: registrations exist only after Stripe confirms
- Card details never touch Edge8 systems
- The attendee list is read from the system, never kept in a spreadsheet
Why it works
- One definition drives everything, so nothing goes out of sync
- Webhook confirmation makes revenue and attendance the same number
- Zero manual steps between signup and seat means zero backlog
- Admins spend event week on the event, not on reconciliation