Should a car wash prioritize Apple Wallet or Google Wallet cards?

Neither — support both, and know the one real difference between them

A car wash shouldn't prioritize one wallet over the other, because Waya issues the same stamp, points, balance, or discount card to both Apple Wallet and Google Wallet from a single enrollment form — the customer's phone decides which wallet the card lands in, and you don't build or design anything twice.

The one fact worth knowing, because it changes what you can promise a customer: geofence — the lock-screen message that appears automatically when a customer's phone gets near your branch — is Apple Wallet only, with a radius of 50 to 500 meters (150 m default) and up to 10 branch locations per card. Google Wallet decides its own proximity trigger; Waya doesn't control or guarantee it for Android customers.

Everything else — the card design, the welcome and win-back triggers, campaign messages, stamps and points — works identically on both wallets. Only the automatic proximity nudge is asymmetric.

What this means for a car wash specifically

A car wash relies more on geofence than most verticals, because "driving past the branch" is a genuinely common event for regular customers — far more common than, say, walking past a barbershop on foot. Losing that automatic nudge on Android customers means roughly half your customer base (Android holds a large share of the Saudi market) won't get the same drive-by reminder Apple customers get for free.

That's not a reason to skip Android customers or push them toward buying an iPhone — it's a reason to lean more heavily on Waya's other triggers for them: the welcome message on enrollment, the stamp-added confirmation, the reward-redeemed message, and the 14-day win-back trigger, all of which work identically regardless of wallet.

• Card design and enrollment: identical on both wallets
• Automatic triggers (welcome, stamp, reward, win-back): identical on both wallets
• Scheduled and one-off campaigns: identical on both wallets
• Geofence proximity messages: Apple Wallet only, Google Wallet uses its own logic

The limitation, stated honestly: don't promise geofence to every customer

The mistake to avoid is telling every customer "you'll get a message when you drive by" without knowing which wallet they're on. An Android customer who never gets that drive-by nudge, after being told they would, reads as a broken promise even though nothing is actually broken — Waya simply doesn't control Google Wallet's proximity behavior the same way.

State it plainly at enrollment or in your card description if geofence is a selling point you mention out loud: "Apple Wallet customers get an automatic nearby-branch reminder; Android customers get the same welcome, stamp, and reward messages, just without the drive-by nudge."

A side-by-side comparison for a car wash owner

The table below lists what's identical and what differs, so there's no ambiguity when setting expectations with staff or customers.

Setting up a wallet-agnostic launch in practice

Design the card once in the dashboard, print one QR poster, and let the customer's phone pick the wallet — there's nothing to configure per platform. If a customer's device has neither wallet installed, the same enrollment link opens a web card instead, with no lock-screen messages or geofence at all, which is worth knowing if a customer asks why a friend on an older Android phone doesn't get any push notifications.

Enrollment and stamping both run the same way regardless of wallet: staff scan the customer's card on an ordinary phone, since Waya has no POS or till integration and there's no SMS channel either — every message, wallet or geofence, lands on the lock screen through the wallet app itself.

The next step: build the loyalty program itself

Wallet choice is a detail underneath the actual loyalty design — stamp threshold, staff scanning discipline, and trigger messages matter far more to your return rate than which wallet a customer happens to carry. Start from the full car wash loyalty guide for the mechanic decision and launch plan, and treat this page as the footnote about wallet behavior, not the main event.

Confirming wallet coverage before you launch

A short checklist keeps expectations accurate for both wallets before you print the first QR poster.

1. Step 1: design one card, not two

   Build a single stamp or points card in the dashboard — it renders correctly on both wallets automatically.

2. Step 2: set geofence only if on Growth or above

   Configure the radius from the Branches screen, knowing it will only fire for Apple Wallet customers.

3. Step 3: write trigger messages that don't assume geofence

   Make welcome, stamp, reward, and win-back messages useful on their own, since they're the only automatic nudge Android customers get.

4. Step 4: brief staff on the one real gap

   Make sure whoever answers customer questions knows geofence is Apple Wallet only, so nobody overpromises to an Android customer.