SealTicket

Each ticket opens on the holder's phone as a QR code that changes every minute. A screenshot, printout or forwarded picture of it is refused within 2 minutes, by the gate scanner and by any phone that scans it. Each ticket gets in once (or as many times as its ticket type allows), and a ticket shown again while its holder is inside is flagged, so one link can't get two people in.

By email. Send tickets to one person (one or several at a time), import a list from a spreadsheet if you sold tickets somewhere else, or open a free sign-up page where people claim their own. Each email has a link per ticket; the holder opens it on their phone at the door. Lost the email? Filling in the sign-up page again with the same address sends the tickets again, and you can resend any ticket from your dashboard.

When one person books several tickets, each guest still gets their own ticket, and the booker gets a group page with all of them: they type each guest's name and send each one their ticket on WhatsApp, by email or as a link, or keep them all on their phone and open each one at the door. Each ticket gets in once, on its own, so guests don't have to arrive together. If you'd rather give one ticket for a whole group (a family or a table), make a ticket type that admits several people: the gate lets that many in on one code, once each. It's easier to misuse, so the dashboard warns you first.

Yes. The live demo shows a full ticket with its changing code, lets you scan it with your phone and try the door scanner, with no sign-up. New accounts get a 14-day trial with everything; after that, a free account keeps a practice event with up to 5 tickets to yourself.

Yes. Untick “Email” and each ticket gets WhatsApp, Share and Copy link buttons, and you can mark it as given. Tickets you share yourself don't use your plan's ticket emails.

Yes. Leave the location empty and tickets say “to be announced”, or keep it off the public sign-up page and show it only on tickets. When you add it, every ticket shows it, and one button emails it to everyone with a ticket.

Yes. Add your event's logo, artwork, an accent colour and up to 8 sponsor logos that take turns at the bottom of every ticket. The code itself can be a QR Studio-style seal, circle or square in your colours, with your logo, and every design is scan-tested before it's saved.

You don't need it: SealTicket works on its own. If you use both, an event can have both: passes with photos for crew and staff, tickets for guests. They share the event's gates, ticket types, zones and analytics, so one scanner at the door checks both.

Not yet. SealTicket is in beta and doesn't take payments: use it for free events, guest lists and invitations, or import the buyers from wherever you sell. We'll look at selling tickets based on what beta users tell us.

Yes, by ticket type. Tick "Tickets of this type need the holder's selfie" (for VIP, season or staff tickets): the ticket only works once the holder adds a photo of themselves through their link, and the gate scanner shows it, so the ticket can't be passed on.

Make a gate link under Gates and open it on a door staff phone, with its 6-digit PIN. The scanner trusts only real tickets on qrcodespot.com, shows the name and ticket type, and marks people in and out. If someone's ticket is for another event, another zone or already used, it says so.

SealTicket is on paid plans, and tickets don't use your editable QR codes: 250 per event on Starter, 1,000 per event on Growth, 5,000 per event on Pro, 20,000 per event on Scale. Cancelled tickets don't count. Ticket emails have a monthly allowance: 500 on Starter, 3,000 on Growth, 15,000 on Pro, 60,000 on Scale (email us for more); tickets you share by WhatsApp or link don't count. Events, gates and ticket types follow your plan's Verified Photo Pass limits. On a free account you can try it on a practice event with up to 5 tickets.

Their name, email address, ticket type and what happened at the gates, plus a photo if their ticket type asks for one. The photo is deleted when the event ends; the rest 90 days later. The organiser sees this in their dashboard; we use it only to deliver and check the tickets.