Wallet · Merchant guide
Pick one of your events, release a set number of free seats, and hand out tickets that land straight in a guest’s wallet. Then watch the honest numbers: who was invited, who claimed a seat, and who actually turned up.
A ticket in the wallet
Each ticket is a real, scannable admission that lives in the guest’s digital wallet. Nothing to print, nothing to install.
You cap the free seats
Set Max Seats to Claim and the system enforces it for you. Invite a thousand, release twenty, and it stops taking claims at twenty.
The honest measure
Claimed and turned up are not the same. This page keeps both, so you finally know how many invitations became bodies in seats.
How a complimentary ticket works
You choose
Choose an event to work on
This page always works on one event at a time. Start with Choose an Event in the top-right corner. The events themselves are built on your Events page, so create the event there first if it does not exist yet.
You set the rules
Set the Ticket Settings for that event
Ticket Settings apply to every ticket for the chosen event: when tickets expire, the design ticket holders see, how many seats you are releasing, and any redemption instructions you want shown to the guest.
You issue
Issue the tickets
Add tickets one at a time with Create New Ticket, or Upload a whole guest list from the CSV template. Each ticket can be tied to a mobile number, an email address or a Member ID, or left open for anyone.
A guest claims
A guest claims a seat
The guest opens their ticket and claims one of your released seats, first come, first served. Once your cap is reached, the system stops accepting claims automatically.
Ticket Settings
Ticket Settings apply to every ticket for the event you have open. Set them, then click Save Ticket Settings.
| Setting | What it does |
|---|---|
| Ticket Expiration | The date and time every ticket for this event stops working. It defaults to four hours after the event’s start time, which suits most events. |
| Ticket Design | The look every ticket holder sees in their wallet. Pick one of your saved designs so tickets match the rest of your brand, or create a new design. |
| Max Seats to Claim | The cap on complimentary seats, first come, first served. You can invite far more people than you have seats, for example notify a thousand recipients while releasing only twenty. Once the cap is reached, the system stops accepting claims for you. |
| Redemption Instructions | Free text shown to the guest with their ticket, for anything they need to know to redeem it (which door, what to bring, when to arrive). |
Issuing tickets
You have two ways to hand tickets out, and you can mix them.
Create New Ticket adds one ticket at a time. Mark it complimentary, set a quantity (one recipient can hold more than one ticket), and optionally attach a mobile number, an email address or a Member ID so you know who it went to.
Upload imports a whole guest list at once. Download the CSV template, fill it in, and upload it back. The template columns are quantity, phone number, email, member ID and comp.
Reading the Ticket List
The Ticket List shows every ticket for the event: who each one went to, whether it has been claimed, who claimed it, and whether it has been redeemed. The counters on the left keep the running totals (tickets created, seats claimed, and redemptions) so you can read the whole event at a glance.
Every row can be acted on:
- View previews the ticket exactly as the guest sees it in their wallet.
- Edit changes the recipient details or quantity on that ticket.
- Redeem marks the ticket redeemed by hand, for when someone arrives without a scannable code.
- Archive hides a ticket from the list without deleting it.
Download exports the event’s ticket list to a CSV for your records.
Claimed is not redeemed
This is the distinction the whole page is built around. Keep the two apart and your numbers tell the truth.
Claimed
A guest accepted the invitation and reserved one of your released seats. It counts against Max Seats to Claim. A claim is a promise, not an arrival.
Redeemed
The guest actually turned up and their ticket was scanned. This is attendance, the honest measure of an invitation.
Click Show Analysis to see the three numbers side by side: how many people you reached, how many claimed a seat, and how many arrived. The gap between them is where the real story of an event lives.
Good to know
Pick an event first. Nothing on this page does anything until you use Choose an Event in the top-right. Tickets belong to an event, and events are created on your Events page.
The cap enforces itself. Once claimed seats reach your Max Seats to Claim, the system stops accepting new claims automatically. Raise the cap in Ticket Settings if you want to release more.
Redeeming by hand cannot be undone. A manual Redeem is final, because the guest is treated as admitted. Use it only when someone is genuinely in front of you without a scannable code.
Large guest lists upload in batches. A single CSV import handles up to 10,000 rows. For a bigger list, split it into files of 10,000 or fewer and upload each in turn.
Archiving hides, it does not delete. Archive a ticket to clear it from the list, and use the Archive toggle above the list to show archived tickets again.
Why it matters
Comps are only worth what shows up. Releasing free seats is easy; knowing which invitations became attendance is the hard part, and it is exactly what this page gives you. Cap the seats so a comp run never costs you more than you meant, then use Claimed against Redeemed to see the honest return on every event you fill.
Merchant guide. A plain-language explanation of how Tickets work, not a substitute for the terms in your agreement.