Saving the card
The join page shows Google's Save to Google Wallet button on Android. One tap opens a preview, a second tap saves it. The business is told the card was saved through a callback, so your dashboard counts the member within seconds. No app is installed; Google Wallet is already there.
Updating it
A stamp at the till updates the card through Google's API. The change is pushed to the phone and the card shows the new count. A message can be attached to an update and shown as a notification, within a limit of a few notified messages per day so cards do not become noisy.
Nearby on Android
Google Wallet shows a card as a notification when the phone is near one of the card's locations. The card appears on its own: Google does not display a custom text line the way the iPhone lock screen does. We say so on our pages because owners should know what each customer will see. As on iPhone, the check happens on the phone and is not reported to the business.
Differences at a glance
| Apple Wallet | Google Wallet | |
|---|---|---|
| Add button | Add to Apple Wallet | Save to Google Wallet |
| Business learns it was saved | Device registers for updates | Save callback |
| Nearby text line | Yes | Card only, no line |
| Watch | Apple Watch | Wear OS |
| Removal | Customer deletes the pass | Customer removes the card; business notified |
One card, both platforms
The same card, the same stamps, whichever phone the customer carries.
Questions
What about Android phones without Google Play?+
Some phones sold without Google services cannot run Google Wallet. Those customers can keep the card as a web page from the join link, with the same barcode.
Is there a test mode?+
Yes. Until a business is approved for publishing, Google marks its cards TEST ONLY. We complete the approval for you before launch.