PocketPass puts your brand in the one app every customer already has open: their wallet. You design a pass template once, then issue a pass for each customer, member, ticket holder or guest. The pass lands in Apple Wallet on iPhone or Google Wallet on Android, and from that moment you can change what it says at any time - the phone picks up the change on its own.
There is no app to build and nothing for your customer to install.
The three things to understand
Almost everything in PocketPass is one of three ideas.
A template is the design. It defines what the pass looks like and which pieces of information it carries - a member name, a tier, an expiry date, a barcode. You typically have a handful of templates, one per kind of pass you issue. See Pass templates: the basics.
A pass is one customer's copy. It comes from a template and fills in that person's actual values. Every pass has its own link, its own barcode and its own history. See Issuing a pass.
A notification is a message you push to passes. Pick who should get it, write it, and it appears on the lock screen of everyone holding a matching pass. See Sending a notification.
Why a wallet pass instead of an app
The honest answer is friction. Getting someone to install an app means an app store, a download, an account and a password - and most people simply don't. Apple Wallet and Google Wallet are already installed, already trusted and already on the home screen.
A customer taps one link and the pass is saved. That's the entire journey.
Once it's there, a pass earns its place in a way an email or SMS can't:
- It stays. It isn't buried under two hundred unread messages.
- It updates. Change a balance or a date and the pass in their pocket changes too.
- It reaches the lock screen, without you needing push permission for an app you don't have.
What you can build with it
PocketPass isn't tied to one industry. The same machinery covers membership cards, event tickets, bookings, gift cards, coupons, staff ID and access passes. The preset gallery gives you a sensible starting point for each.
API-first, dashboard-optional
PocketPass is built API-first. Everything you can do in the dashboard you can also do over the REST API - create templates, issue passes, update them, send notifications - so passes can be driven straight from your CRM, booking system or checkout.
If you'd rather not write code at all, you have two other routes:
- Issue passes by hand from the dashboard.
- Publish an issuance form and let customers claim their own pass from a link.
The fastest way to understand PocketPass is to hold one. The quickstart takes about ten minutes and ends with a real, branded pass in your own phone.
What happens after a pass is issued
This is the part that saves the most work. A pass is not a one-off send - it stays connected to you.
- Update the pass and the change reaches the phone. See Live pass updates.
- Send a message and it lands on the lock screen. See Sending a notification.
- Get told when someone installs or removes a pass, so your own systems can react. See Webhooks.
Where to go next
- New here? Start with the quickstart.
- Want the map of the dashboard? See A tour of the dashboard.
- Ready to integrate? See API quickstart.