Home›Loyalty Program Without an App
Own it, don't rent it
Your customers already have Apple Wallet and Google Wallet on their phones. A pass takes seconds to add and nothing to download. Build that program once, own every part of it, and stop paying a platform every month for the privilege of running your own customers.
They live in a wallet or a car door until the customer forgets them. You have no idea who is close to a reward, and no way to reach them.
Asking someone to download an app for one coffee shop is a wall. Most people say no at the counter, and the ones who install it delete it within a month.
Loyalty platforms charge monthly, often per location or per pass. The fee grows exactly as you succeed, and stops the day you stop paying — taking your program with it.
A wallet pass removes the first two problems outright. Owning the platform removes the third.
The word gets used loosely. Here is precisely what ends up in your name when the project is finished.
Your Apple Developer account holds the Pass Type ID certificate. Your Google Cloud project holds the Wallet issuer ID. Both are registered to your business, not to me and not to a vendor. Nobody can switch your passes off.
Names, points, visits and redemptions sit in a database you control, on hosting you pay for directly. You can export it, query it, or plug it into whatever CRM you use later.
You get the source, the deployment and the documentation at handover. Bring it in-house, hand it to another developer, or come back to me — that stays your decision.
Issue 500 passes or 50,000; open a second branch or a tenth. The running cost does not move, because there is no middleman metering it.
Seven steps from an idea to a program you own outright. Nothing here locks you to me.
Stamps, points, tiers or a simple membership. This is a business decision, not a technical one, and it is where I push back hardest — a program nobody understands at the counter will not get used.
Apple Developer enrolment and a Google Wallet issuer account, set up with your business details. I walk you through it rather than doing it under my own account, because ownership starts here.
Your logo, colours and fields, laid out for both Apple Wallet and Google Wallet so the pass looks deliberate rather than generic on either phone.
How a customer gets the pass — a QR code on the counter, a link, a WhatsApp message — and how your staff scan it to add points or redeem. This is the part customers and staff actually touch, so it gets the most attention.
Where you see who is enrolled, push an offer to everyone holding a pass, and check what a campaign returned. As simple or as detailed as you need.
Your server or cloud account, your domain. I set it up and hand over the keys, so there is no account of mine sitting in the middle of your business.
Source code, documentation, and a walkthrough for whoever maintains it. Including how to renew the Apple certificate each year, because that is the one thing that will otherwise catch you out.
The build is a one-off. After that the running cost is what Apple and your host charge — nobody is metering your customers.
| You own it | Subscription platform | |
|---|---|---|
| Apple Developer Program | $99 / year | Included, but not yours |
| Google Wallet issuer | Free | Included, but not yours |
| Hosting | ~$5–20 / month | Included |
| Per pass issued | Nothing | Often metered |
| Per extra location | Nothing | Usually charged |
| The build | One-off | None upfront |
| If you stop paying | Nothing changes | Program switches off |
| Customer data | Your database | Vendor's database |
If you are still testing whether a loyalty program works for your business at all, rent one first. A subscription costs less to start and you can walk away in a month. Owning it makes sense once those monthly fees have added up past the cost of building, or once you need something the platform simply will not do. I will tell you honestly which side of that line you are on before you commit to anything.
Yes. Apple Wallet and Google Wallet are already on the phone — nothing to download. The customer scans a QR code or taps a link, and the pass is in their wallet in a few seconds. Removing the app install is usually the single biggest lift in sign-up rates.
Hosting, which is typically $5 to $20 a month for a small to mid-sized program, plus the $99 a year Apple Developer fee. There are no per-pass, per-customer or per-location charges, because there is no platform in the middle taking a cut.
No, and it would be dishonest to claim otherwise. A subscription is cheaper to start and makes sense if you are testing whether a loyalty program works at all. Owning it wins once the monthly fees have added up past the one-off build, or once you need something the platform will not do. If you are unsure, start on a subscription and move when the numbers say so.
Nothing breaks. The Apple and Google accounts are registered to your business, the data is in your database, and you hold the source code. Another developer can pick it up, which is the entire point of owning it rather than renting it.
Usually yes. Most platforms let you export customer and points data, which I can import into your own system. Existing passes issued by the old platform cannot be transferred, so customers re-add a new pass — normally handled with a single message campaign before you switch over.
A straightforward stamp or points program with issuing, scanning and a basic dashboard is typically 3 to 6 weeks. More complex programs — tiers, multiple locations, CRM integration — run longer. You will get a specific timeline before anything starts.
Tell me what you sell and how you would like to reward repeat customers. I will come back with a scope, a timeline and a one-off price — and an honest answer about whether building your own is worth it for you yet.