Apple Wallet Loyalty Cards Without an App: How They Actually Work
"Can you add it to Apple Wallet?" is one of the first questions a merchant hears from a customer setting up a loyalty card, and it usually comes loaded with the wrong assumption — that getting there means downloading something first. It doesn't. There's no Ruffus app for customers to download, nothing in Apple's or Google's app store, nothing to install before a pass can sit next to a boarding ticket or a transit card. It's worth being precise about what actually happens when a stamp card lands in Wallet, because the mechanics are different from a bookmark or a bare notification, and the differences are exactly what make it useful.
What a Wallet pass actually is
A Wallet pass isn't a screenshot, and it isn't a shortcut to a web page. It's a signed file — a .pkpass for Apple, a registered object for Google — that the operating system stores and renders using its own native card UI, the same interface it uses for airline boarding passes and event tickets. That distinction matters because it's what lets the pass do things a bookmarked page can't: live on a system-level lock screen surface, get pushed an update without the customer opening anything, and show up in a search for "loyalty" without the customer remembering which browser tab it was in.
Why there's nothing to install
The same loyalty card actually exists in three forms at once: a normal web page, an installable PWA (add it to a home screen and it behaves like an app without ever going through an app store), and a Wallet pass. A customer can use any one of them, or all three, and none of them requires downloading a Ruffus app — which also means there's no update to push, no storage to free up, and no app to delete six months later out of habit. The paper-punch-card replacement works the same way underneath: the first stamp is what creates the card, and the customer signs in with a phone number, an email address, or an existing Google or Apple account. No password to invent, no profile to fill out.
Getting it into Wallet
Once that first stamp exists, adding it to Wallet is a single tap — "Add to Apple Wallet" or "Save to Google Wallet," sitting right on the card's own page. There's no separate signup for Wallet specifically; it's an option on a card that already exists, not a second onboarding. A customer who never taps it still has a fully working card as a web page or a PWA — Wallet is an upgrade to where the card lives, not a requirement to use it at all.
What Wallet does that a web page can't
A bookmarked page only updates when someone opens it. A Wallet pass updates itself: the moment a stamp is issued at the counter, the already-installed pass gets refreshed in the background, so the count the customer sees is current before they've unlocked their phone to check. And because the pass can carry a set of the merchant's own locations, iOS and Android can both surface it on the lock screen when the customer is physically near the store — not as a notification they have to act on, just a card that's already there when they'd otherwise be reaching for it. That's a real, meaningfully different starting point than a page nobody has a reason to open on their own, whether that's a barbershop a client visits every few weeks or somewhere they pass more often. None of that comes with a promise about exactly when a lock-screen suggestion appears or how quickly an update lands on a given device — both are the operating system's call, not something a merchant configures — but the underlying behavior, a live pass that refreshes itself, is real on both platforms.
Apple and Google, both real
Both platforms are genuinely supported, not one real integration with a second one bolted on as an afterthought — but they don't work identically, and it's more useful to know how than to assume they're the same thing wearing different logos.
An Apple Wallet pass is a signed file pushed to the device; when a stamp changes it, Apple's push service sends the device a quiet signal that tells it to go fetch the updated pass, rather than delivering the new data directly. Google's version works more like a live record: the pass is an object registered with Google's Wallet service, and updating it means changing that object directly — there's no separate push step to relay first. Both let a merchant attach up to ten locations for lock-screen relevance; Apple's pass format has a slot for the line of text that shows up when a customer is nearby, and Ruffus fills it with a fixed line carrying the business's name, while Google's equivalent has no text slot at all, so Android shows its own generic treatment instead. Either way, what the merchant actually controls is whether that nearby reminder is on, not what it says. Neither difference makes one platform's pass more or less "real" than the other — they're just two different ways two different companies chose to keep a stored pass in sync with what's actually happening at the counter.
It looks like your business, not a template
None of this is worth much if the pass that shows up looks like a generic loyalty template with a logo dropped in the corner. It doesn't — the card face carries the merchant's own brand color as the actual background of the pass, not an accent stripe on top of a fixed layout, with the text and stamp markers automatically kept legible against whatever color that is. A barbershop's card and a café's card look like two different businesses because they are two different businesses, not two instances of the same design wearing different logos.
The short version
A Wallet pass isn't an app, and getting a stamp card into one isn't a second product to set up — it's what the same card becomes with one tap, after the first stamp already exists on a page or a PWA. What changes is where it lives afterward: somewhere that updates on its own, that can turn up on a lock screen without anyone opening anything, and that still looks like the actual business behind it rather than a template. Whether that business runs its own point-of-sale system or also runs a Shopify store alongside it, none of that changes — the pass works the same way regardless of what's ringing up the sale.