Six steps from browsing to the gate. The interesting part is step two — a seat hold is a lock, not a flag.
Every event has a real venue plan. Rows, tiers and prices are shown before you commit, so there is no guesswork about what you are paying for.
Up to 6 seats in a single order.
Choosing a seat takes a distributed lock rather than a plain database flag. Two people cannot hold the same seat, even if they click at the same instant.
10 minutes to complete payment.
Seats taken by other customers appear greyed out on your map immediately, without refreshing. If someone tries to take a seat you hold, you are told before you pay.
Updates arrive over a WebSocket channel.
Card, UPI and net banking all run against sandbox instruments. Nothing is charged and no real card details are ever handled by this frontend.
Test card 4242 4242 4242 4242.
Payment success turns the hold into a confirmed booking and prints one ticket per seat, each with its own barcode and price tier.
Re-open them any time from My bookings.
Each ticket carries a unique token. Scanning validates that exact seat for that exact booking, so a duplicated or voided ticket fails at the door.
Used tickets are marked, not deleted.
Seat holds use an atomic compare-and-set with an optimistic concurrency version. If the version moved underneath you, the hold is refused rather than silently overwriting someone else.
The booking commits only after the payment gateway reports success. If the commit fails, the hold is released and the seat returns to the pool.
Cancelled and expired holds return their seats to the live map immediately, so the next customer sees them as available.
Live availability, real venue plans and no payment required until you pick a seat.