How NitePass Worked
An attempt at a safer alternative to selling tickets through social-media DMs.
Students listed or requested tickets
Sellers posted the tickets they had. Buyers could post what they were looking for on the wanted board.
Listings entered a review queue
New listings were held for approval rather than published straight away, with moderation tooling built to work through them.
Buyers contacted the seller
Approved listings were browsable, and buyers could message the seller or make an offer through the site.
What Was Built for Trust
These mechanisms were built. None of them were ever tested at scale — no listing was ever posted by a real user.
University email confirmation
An opt-in flow that emailed a one-hour token to a .ac.uk address. It was never made a requirement to sign up.
Listing review queue
Listings were held for approval rather than auto-published, with a moderation queue built to action them.
Reporting
Any listing could be flagged, and reports landed in the same moderation queue.
Duplicate-image detection
Uploaded tickets were read with OCR and fingerprinted, to catch the same ticket being listed twice.
Built for Students
NitePass was designed around the way students actually buy and sell tickets — last-minute, in group chats, and between people who go to the same events. The aim was to keep that ease while adding the accountability that DMs never have.
- A university email confirmation flow for sellers
- Designed for real student events and nights out
- Fair, transparent pricing — no silent markups