Wallet passes
Passes that keep themselves current.
Design the pass once and it drives both wallets. After a scan, a refund or a renewal, the pass on the customer’s phone changes by itself.
Apple Wallet
Google WalletThe problem
A ticket emailed as a PDF is out of date the moment anything changes, and nobody can tell a used pass from a live one.
What we built
Passes we create and sign ourselves, so a scan, a refund or a renewal updates the card already in the customer’s wallet.
What is actually in it.
The pass studio
Lay a pass out field by field, with a live preview.
- Any number of named templates, with one set as the default
- Icon, logo and banner upload, with a plain warning on wrong formats
- Background, text and label colours from colour pickers
- Two styles: a ticket with a banner, or a photo card
- Fields go where Apple places them, and can be reordered
- One design drives both Apple and Google Wallet
Live data on the pass
What is printed comes from the order, not a template.
- Holder name, order number and pass ID
- Event name, date, venue and gates-open time
- Sessions show their start time, collections a pickup window
- Annual pass number, valid for, expiry and visit count
- Member number, tier and term
- A field with no data is simply left off that pass
Every kind of pass
One pass design per ticket type, product or tier.
- Event tickets, including multi-day passes showing the date range
- Group passes: one pass that admits a whole group
- Product and add-on passes, such as collection codes
- Annual passes with photo, number, expiry and visit count
- Membership cards, including organisation, transferable and guest
- Standard barcodes, or custom codes for existing gate systems
Current after the gate
The pass changes once something happens to it.
- After a scan a single-use ticket shows Used, with the time
- The phone gets a ticket used notification
- Annual passes count visits, and the card shows the number
- A refunded, voided or cancelled pass greys out in the wallet
- A renewal refreshes the same card with its new end date
- Passes show as expired once the event or term has ended
Getting them to customers
The right button for the device, and links that never expire.
- Add to Apple or Google Wallet per ticket on the order page
- On a computer, a QR code adds the pass from their phone
- Add all to wallet takes a whole order, grouped by day
- Wallet links never expire, so old emails keep working
- A PDF ticket per pass, and one combined PDF per order
- Staff can send a fresh wallet link during a support call
Designed field by field
Your colours, your layout, both wallets.
Previewed before it ships
Drawn by the same code that makes the real pass.
A design per ticket type
Or a banner per ticket, overriding the template.
Used, at 10:04 am
The pass updates the moment it is scanned.
Counts the visits
An annual pass shows how many times they have come.
Links that never expire
An old email still adds the pass today.
Wallet passes questions
Does the pass update after it has been issued?
Yes. A scan marks it used with the time, an annual pass counts the visit, a renewal refreshes the same card, and a refund greys it out.
Do we need a third-party pass provider?
No. We create and sign our own Apple and Google Wallet passes, with nobody in the middle.
Can different tickets look different?
Yes. A pass template per ticket type, product or membership tier, with a banner image per ticket that overrides the template.
What if the customer is on a computer?
The order page shows a QR code that adds the pass from their phone, and only ever shows the wallet button that matches their device.
Do old wallet links stop working?
No. Wallet links are made fresh every time, so links in old emails keep working.
See it running for your venue.
Every demo is built around your venue. We base it on your own website, events and prices, so you can see exactly what changes for your guests and your team.
Request a demo
An honest conversation with the people who built it.