Apple Wallet
On iPhone, customers add a pass from a link, QR code, email, SMS, or web page. The pass then lives in Apple Wallet and can show live fields, barcode details, relevant dates, and updates.
How wallet passes work
A practical customer channel built into Apple Wallet and Google Wallet.
Wallet passes are digital cards a customer can add without installing your app. Businesses use them for loyalty, memberships, coupons, gift cards, tickets, and custom verification or customer workflows.
Google Wallet
On Android, customers add the matching wallet pass to Google Wallet. The business logic can stay the same while the customer sees the native Google Wallet experience.
One business program
Your team manages the template, fields, issuing method, updates, redemption data, and lifecycle events from PassIssuer instead of maintaining separate customer apps.
How it works
Five steps from setup to scan.
Create, issue, add, update, redeem. That's the loop. Every PassIssuer feature is one of those five verbs, or the audit trail of one.
Anatomy of a pass.
Every surface you
get for free.
A wallet pass is a tiny living document. It has a front, a back, a push channel, a geofence, a barcode and a webhook — and PassIssuer gives you a console for all of them.
3
1
2
4
1
Brand header
Logo, brand colors, pass type. Edit once, every pass already issued repaints in seconds.
2
Live fields
Numbers, tiers, balances — values you push from your CRM, POS or webhook. The pass updates itself.
3
Back side
Long copy: terms, locations, contact, support. Customers flip the pass to read it.
4
Barcode
Scannable at the counter, with token strategies available for flows that need extra fraud controls.
Push & geofence
Send a message when stamps hit 9. Surface the pass on the lock screen near a store.
Lifecycle hooks
Webhook on add, update, removal. Wire it to your data warehouse — or your help desk.