Google Wallet enrollment

On an Android phone, scanning your card's QR code ends with the card saved to Google Wallet.

What the customer does

1. Scan or tap the link

   The customer scans your QR code or opens the enrollment link.

2. Fill out the form

   They fill in the enrollment form fields for the card.

3. Save to Google Wallet

   They tap to save, and the card appears in Google Wallet.

What you get with Google Wallet

• Lock-screen notifications: messages you send reach the customer through Google Wallet's own push.
• Automatic updates: republishing a card queues a class update, so existing holders see design and reward changes.

Everything else works the same

Apart from the geofence, an Android customer's card behaves the same as an Apple Wallet card from your side: staff scan it the same way from the Scan tab, it counts toward the same card cap, and broadcasts and triggers reach it through the same Notifications tab you already use.

Running both wallets on the same card

You don't design or publish separate cards for Apple Wallet and Google Wallet — it is the same card, the same QR code, and the same link. Waya sends a customer to the right wallet based on their device: iPhones go to Apple Wallet, Android phones go to Google Wallet, and a desktop browser shows both buttons so the customer can pick whichever matches their phone. See desktop and devices without a wallet for that last case.

If a customer removes the card

A customer can remove your card from Google Wallet the same way they would remove any pass. There is no separate step on your side — they simply stop receiving updates until they enroll again, and nothing about your other customers or your dashboard is affected. Staff can still look them up by phone number from the Scan tab if they need to re-enroll.

Next steps

• Apple Wallet enrollment to compare the iPhone experience.
• QR code and enrollment link for how the link works.
• Desktop and devices without a wallet for the desktop case.