Home›Apple & Google Wallet Development
Wallet Pass Development
I build the passes your customers keep in their phone — loyalty cards, memberships, coupons and tickets — and the platforms that issue, update and track them. Nine wallet platforms shipped across three continents, from single-brand loyalty programs to white-label SaaS used by agencies.
Most projects are one of these, or a platform that combines several of them behind a dashboard your team controls.
Points, stamps and tiers that live in Apple Wallet and Google Wallet, updating on the customer's phone as they earn — no app to install, no plastic to reprint.
Gym, clinic, club and staff passes with scannable barcodes, expiry handling and tier changes pushed straight to the phone.
Time-limited offers and event tickets with redemption tracking, so you can see what a campaign actually returned rather than how many people opened an email.
The certificate handling, signing pipeline and .pkpass file generation that sits underneath all of it, built to survive Apple's certificate renewals.
The dashboard your team lives in: designing passes, issuing them in bulk, scanning at the counter, and reporting on redemption. Multi-tenant and white-label when agencies need to resell it.
Wallet passes wired into the tools you already run — GoHighLevel, ManyChat, WhatsApp flows and custom CRMs — so issuing and scanning triggers your existing automations.
Nine production wallet platforms, each live for a real business rather than a demo.
What the pass shows, how a customer gets it, what updates it, and who scans it. Most of the risk in a wallet project is in the flow around the pass, not the pass itself.
Apple Pass Type ID certificate and Google Wallet issuer account, set up in your name so you keep ownership. This is the step teams most often get stuck on.
Pass design, signing, generation and delivery — link, QR, email or WhatsApp — with a staging environment you can test on your own phone.
The admin side: issuing, updating, scanning at point of sale, and hooks into your CRM so the passes feed the systems you already use.
Deployment, documentation and a walkthrough for your team. Certificates expire annually, so I make sure someone on your side knows how to renew them.
A single pass type with a working issuing flow typically takes 2 to 3 weeks. A full pass management platform — dashboard, customer sign-up, scanning and analytics — usually runs 6 to 12 weeks depending on how much of the flow already exists.
No. Apple Wallet and Google Wallet are already on the phone. Customers add a pass from a link, a QR code or a WhatsApp message, and it lives in the wallet app they already use. Removing the app install is usually the single biggest lift in sign-up rates.
Yes. Apple Wallet passes must be signed with a Pass Type ID certificate from an Apple Developer account, which costs $99 a year. Google Wallet needs a Google Cloud project and issuer account, which is free. I can set both up on your behalf, or guide your team through it so the certificates stay under your control.
Yes. Point balances, tier changes, expiry dates and offers can be pushed to a pass already sitting in someone's wallet, and the phone shows the update on the lock screen. That is what makes wallet passes a marketing channel rather than a static card.
Yes. I have built wallet pass integrations with GoHighLevel, ManyChat and custom CRMs, so issuing a pass, scanning it and updating points can trigger and respond to your existing automations.
Tell me what you are trying to put in your customers' phones and I will tell you what it takes — scope, timeline and what you need on your side before development starts.