Every merchant we talked to had the same problem. They wanted a loyalty program, but the last thing their customers wanted was another app to download, another login to forget, another icon buried three screens deep. So we asked a simple question: what if the loyalty card just lived in the wallet the customer already opens every day?
The best app is often no app at all — just a pass that shows up when it's needed.
01The wallet is the platform
Apple Wallet and Google Wallet already solve distribution, storage, and notifications. A .pkpass bundle is signed, versioned, and updatable over the air. Once a customer adds a passly pass, we can push a new stamp or a fresh offer straight to their lock screen — no push-notification permission dance, no app update, no friction.
- One tap to add — no account, no download
- Server-driven updates land on the lock screen instantly
- Location and time triggers surface the pass at the right moment
02GDPR by default, hosted in Frankfurt
Because most of our partners are in Germany and the wider DACH region, compliance couldn't be an afterthought. passly runs entirely on AWS Frankfurt, stores only what a loyalty program actually needs, and treats data minimisation as a design constraint rather than a checkbox. The result is a product our WEU clients can hand to their own legal teams without a fight.
03Why not just build an app?
We could have. But an app means install funnels, store reviews, two native codebases, and a permanent maintenance tax — all to solve a problem the wallet already solved. Building on the wallet let a small senior team ship something people actually keep, instead of something they delete after one visit.
That's the whole thesis behind passly, and behind how we build in general: reach for the boring, proven path, and spend the creativity on the part that actually matters to the customer.