Should a salon prioritize Apple Wallet or Google Wallet cards?

Neither — the same card reaches both, one feature difference aside

A salon doesn't need to prioritize Apple Wallet or Google Wallet, because the same card enrolls into either one automatically based on the client's phone — an iPhone client taps into Apple Wallet, an Android client into Google Wallet, from the identical QR code and enrollment form. There's no separate setup, no separate design, and no decision the salon has to make upfront.

The one genuine difference worth knowing about is geofence: the feature that puts a message on a client's lock screen when her phone is near your branch is Apple Wallet only. Google Wallet has its own proximity behavior, but Waya doesn't control or guarantee its trigger distance the way it does for Apple's 50–500 meter radius.

Plain-language: what happens after a client scans the QR code

When a client scans the enrollment QR code and fills in a first name and mobile number, Waya automatically detects which wallet her phone supports and offers the right add-to-wallet button — she doesn't choose a wallet type, and the salon doesn't configure two separate cards. On a device with neither wallet, the same link opens a web card fallback instead, so nobody is turned away at enrollment.

From that point on, both wallet types behave the same way for the core loyalty mechanics: stamps or points update automatically when staff scan the card, and both support lock-screen push messages for triggers like welcome, stamp added, and reward redeemed.

The limitation, stated honestly

If a salon is planning a strategy specifically around geofence — say, catching a mall client walking past — it's worth knowing plainly that this only works reliably for Apple Wallet clients. Google Wallet decides its own proximity trigger, and Waya doesn't promise the same 50–500 meter, zero-quota behavior on it. A salon with a largely Android clientele shouldn't build a marketing plan that assumes geofence will reach most of its customers.

• Geofence works reliably on Apple Wallet only — up to 10 branch locations, 50–500 m radius, 150 m default
• Google Wallet's proximity behavior is its own and isn't guaranteed by Waya the same way
• All other core features — enrollment, stamps, points, triggers, campaigns — work the same on both
• Don't build a geofence-dependent campaign assuming it will reach Android clients too

Why this matters less than it sounds like it should

In practice, most salons don't need to make a decision here at all, because the enrollment flow already routes each client to the correct wallet automatically. The only real planning implication is around geofence specifically — everything else (win-back triggers, campaigns, stamp counting) reaches both wallet types identically, so a mixed iPhone-and-Android client base is not a problem for the loyalty mechanics themselves.

What to check if geofence matters to your salon specifically

If your location genuinely benefits from proximity alerts — a mall salon, a street with regular foot traffic — check what share of your clientele carries an iPhone before building marketing plans around geofence reach. For a client base that's mostly Android, invest instead in scheduled campaigns and the win-back trigger, both of which reach every client equally regardless of wallet type. The salon loyalty guide covers picking the right notification mix for a given client base in more detail.

Set up enrollment correctly and this becomes a non-issue

The practical next step for any salon is simply to get the enrollment QR code placed where clients naturally are — the till, the mirror, the waiting area — and let the automatic wallet detection do its job. There's no separate Apple or Google setup step for a salon to complete; the only thing worth deciding deliberately is whether geofence is worth setting up given your actual client mix, since that's the one place the two wallets genuinely diverge.

1. Step 1: place the QR code

   Put it at the till, mirror, or waiting area — the enrollment flow handles wallet detection automatically.

2. Step 2: check your client mix

   Get a rough sense of iPhone versus Android share among your regulars if geofence matters to you.

3. Step 3: set up geofence only if it fits

   If iPhone share is meaningful, set the geofence radius from the Branches screen, not the card's address text.

4. Step 4: rely on universal features for everyone else

   Use the win-back trigger and scheduled campaigns as the backbone, since they reach every client regardless of wallet.