Event ticketing service
A seat is held while the payment goes through, the ticket arrives as a code, and at the door that code is read once.
- Buildfrom $2,850
- Timeline3–5 weeks
- Supportfrom $570/mo
Who this suits: Events where the seat is part of what is sold, and the door is a queue of people whose tickets are somewhere in their messages.
What is in the first version
- hall plan
- seat hold
- single-use code
- scanning at the door
The figures above are the package this sits on: Payments and billing. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
The seat is taken before payment
The seat is held while payment runs, the plan updates for everyone, and an unpaid hold returns itself.
- 02
A code, not a picture
The code is bound to the seat and the buyer, opens the door once, and reissuing kills the previous one.
- 03
Cancelled once at the door
The check runs on the device itself, and a second scan names the point and time of the first.
What decides whether this works or annoys people
The first minutes decide it
The hold is taken at the database level, the plan updates by change, and load is tested against an announcement.
No network at the door
The scanner carries the list and works with no network, and a duplicate found at sync names both scan points.
The date moves for everyone
Mass reissue and mass refund are in the first version, and who carries the refund fee is agreed in advance.
What to measure once it is live
- payments that reach a ticket
- seat holds that expire unpaid
- seconds per person at the door
- second scans of the same code
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- Sales and the hall planTypeScriptReactNext.js
- Seats, holds and moneyNode.jsPostgreSQLPrismaRedisStripePaddle
- The door and operationsFlutterS3DockerGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- payment provider fees, refunds included
- the mail service tickets go out through
- SMS with the ticket or entry code
- hired phones or scanners for the door
Asked before the first call
- Why not a ready-made ticketing platform?
- If one fits, use it, and we say so on the call. This is for a hall plan of your own, your own fee, or money that arrives on the day of sale.
- What happens if the network dies at the door?
- The scanners keep working: each downloads the list before the doors open, cancels tickets locally and syncs later. That is a requirement of the first version.
- Can a ticket be passed to somebody else?
- That is your rule and we build either one: a transfer that reissues the code, or a ticket bound to the buyer. What we will not ship is the middle version.