Ticketing for the B Corp Summit
Case study
- My role
- I designed and built the ticketing platform: payments, QR codes, staff portal and back office.
- Duration
- December 2025 to February 2026, for the May 2026 event
The problem
The Summit sold single tickets and bundles of up to 6 people: one payment, but six QR codes, six emails and six separate session profiles. If Stripe retries a webhook nothing may be duplicated, and staff must validate entries from a smartphone.
What I did and why
- Participants as separate records: a dedicated collection for bundle participants instead of a list nested in the order. Admins find a person by name, the check-in CSV export has one row per person and changing a participant doesn't touch the order.
- Stripe embedded checkout: payment stays inside the Summit site, with no redirect.
- Idempotent webhooks: one key per Stripe session; QR codes and emails are generated in background jobs with three attempts, so the webhook answers straight away.
- Refunds without ghost tickets: a refund automatically invalidates the order's QR codes.
- Staff portal: dedicated login, scanner using the browser camera and an entry log with timestamps.
The same problem across three events
I also built the ticketing for Impact Summit (events, tickets with automatic inventory, Stripe checkout) and for Activation Days (persistent cart, coupons, free experiences without going through Stripe, bookings area).
Results
- 300attendees at the May 2026 Summit
- 0duplicate QR codes or double emails
- 3 eventsrunning ticketing I built
Stack highlights
- Next.js 16
- Payload CMS 3
- MongoDB
- Stripe Embedded Checkout
- Payload Jobs
- React Email + Resend
- tRPC
- next-intl
Working on something similar? Let's talk.
Get in touchBeyond ticket sales, the platform runs the two-day programme: parallel sessions, speaker profiles and attendees picking the sessions they want. Confirmation and refund emails go out in Italian or English, with the QR code attached. Event staff have their own login, and the Summit team exports the check-in list from the admin.
What I bring to an agency or a small business from this project
- A payment flow that holds up in the awkward cases: repeated webhooks, refunds, bundles for several people.
- Ticketing already adapted to three different events: I know what staff need on the day.
- An admin the client runs on their own for attendees, orders, programme and exports.
Realized for B Lab Italy in collaboration with Ride On
