Apple Wallet & Google Wallet passes
Tickets, vouchers and memberships that live on the customer's phone, not in their inbox.
63Digital issues Apple Wallet and Google Wallet passes from your platform: signed Apple passes, Google save links, grouped per event, and in the organiser's timezone, with the same QR codes your door scanners already read. We built wallet tickets for Rebll Tickets, switched on per promoter.
What we build
Apple Wallet passes
Signed .pkpass files, bundles for multi-ticket orders, and event artwork on the pass.
Google Wallet passes
Signed save links with the event and ticket inline, grouped per event.
Secure credential handling
Certificates and keys kept in a vault and a pipeline's secure files, never in the repository.
Rollout controls
Per-organiser switches and a diagnostics page to verify passes before customers see them.
How to, from jobs we've done
Our work on Apple & Google Wallet
Is this for you?
A good fit when
- ✓You issue tickets, vouchers or memberships that people show on arrival
- ✓Your customers dig through emails for PDFs at the door
Probably not when
- –You need passes to update live with seat changes or push notifications (that's a larger build)
Related: System integration
Common questions
Do Wallet passes work with my existing ticket scanners?
They can. Keep the QR payload identical to your current tickets, and scanners don't need to change.
Do I need an Apple developer account for Wallet passes?
Yes. Apple passes are signed with a Pass Type ID certificate from your Apple developer account, plus Apple's WWDR certificate.
Is Google Wallet harder than Apple Wallet?
Different, not harder. Google passes can be added from a signed JWT link with the event and ticket inline; the catch is that event classes, once created, only change when you bump their version.
Want tickets in Apple and Google Wallet?
Tell us what you issue and how it's scanned. We'll add wallet passes without changing your door process.