Google Wallet Loyalty Cards: A Setup Guide for Business Owners

Google Wallet Loyalty Cards: A Setup Guide for Business Owners

A Google Wallet loyalty card is a digital pass that lives in the Google Wallet app on a customer’s Android phone. It replaces the paper stamp card, shows your brand and the customer’s progress, and can nudge people back to your shop. You can launch one in two ways: build it yourself on Google’s developer platform, or use a loyalty platform that issues the passes for you. This guide explains how both work, what customers do to add a card, and where owners go wrong.

TL;DR

• Google Wallet stores loyalty, rewards and membership cards, and customers can add them by scanning a QR code or tapping an Add to Google Wallet link.
• Building directly on Google’s API takes developer work (classes, signed links, verification). A platform like Beepify skips that and issues the card for you.
• Google caps notifications at 3 per pass in 24 hours, so save them for moments that matter, such as one stamp left.
• For a salon, cafe or shop, the card only pays off if staff stamp it at every visit and customers see a clear reward.
• Plans start at €45 per month, and you can test the flow first with a demo.

Table of Contents

• What a Google Wallet loyalty card actually is
• How customers add a loyalty card to Google Wallet
• Two ways to launch your own Google Wallet card
• Static passes versus live passes
• What push notifications can do, and their limits
• What the card needs to work in a real business
• Examples by business type
• Our perspective
• Beepify plans and pricing
• A simple launch plan
• Common mistakes
• FAQ
• Sources

What a Google Wallet loyalty card actually is

Google describes Wallet as the place to keep digital copies of loyalty and gift cards, and loyalty cards also cover rewards and membership cards. For you as a business owner, that means one pass can be a stamp card, a points card or a membership card. The customer never needs to carry plastic or download your own app.

That last point matters more than it sounds. Most small businesses will never get customers to install a dedicated app for a coffee. A wallet pass sits where the customer already looks when paying, next to their cards and tickets.

Google’s developer documentation says the Wallet API reduces clutter and gives customers faster access to their cards, and lets businesses issue passes across Android, web, email and SMS. In practice, that gives you several places to hand out the card: a QR code at the counter, a link in a receipt email, a text message after a booking.

A note on Apple users: Google Wallet is an Android and web experience. If your customers use iPhones, they need an Apple Wallet version of the same card. We cover that on our Apple Wallet stamp card page. One setup that produces both passes saves you from running two programs.

How customers add a loyalty card to Google Wallet

Your customer has two routes, and you should design for both.

Route 1: from the Wallet app

Per Google’s help page, the customer opens the Google Wallet app, taps Loyalty card, and then finds and taps the merchant or program name. This only works if your program is discoverable in Google Wallet, which requires extra enrollment work on the business side. Most small shops will not rely on this route.

Route 2: scanning your QR code or tapping a link

This is the route that works for a salon or cafe. The customer scans a QR code with the phone camera, taps the link that appears, selects Add to Google Wallet and confirms. It takes seconds at the counter.

Technically, an Add to Google Wallet link is a generated URL that contains an encoded, signed JWT. It can be embedded on a website, in an email or in an SMS. You do not need to understand the JWT part if you use a platform. You only need to know that the link is how the card gets onto the phone.

If you want a customer-facing walkthrough you can print or share, our blog has a short guide on how to add a loyalty card to Apple Wallet and Google Wallet.

Two ways to launch your own Google Wallet card

Option A: build on Google’s API

Google’s documentation lays out what this involves. You create a loyalty class that defines the structure and content of your cards, including program details, display and security options. The LoyaltyClass reference also covers Smart Tap redemption and discoverability. Then you issue individual loyalty objects per customer.

If you want customers to find and join your program from inside Google Wallet, the steps grow. According to Google, you need to set up a test class, build enrollment and sign-in pages, push the card back to Wallet after enrollment, and request verification and activation.

That is a real software project. It suits a larger retailer with developers and an existing customer database. It rarely suits a three-chair salon.

Option B: use a loyalty platform

The second option is a service that handles the technical side and gives you a dashboard. You design the card, print or display a QR code, and your staff scan customers to add stamps. This is what we built Beepify for. Our own walkthrough, Google Wallet loyalty card setup step by step, covers the process in more detail, and the Google Wallet card guide for business owners explains what to decide before you start.

Static passes versus live passes

There is a distinction many owners miss. A pass a customer saves by themselves, such as a photographed barcode, is just a static image. You cannot update it, and you cannot message the customer. A pass that you issue through the API is a live object. You can change the stamp count, show a reward tier and send a notification.

Google’s enrollment documentation describes this as upgrading a customer’s card, and the ability to push updates back to Wallet is the reason to prefer an issued pass. The practical rule: if your card cannot update itself after a stamp, it is a paper card in disguise.

What push notifications can do, and their limits

The feature that sets a wallet card apart from a paper card is the notification. A message can appear on the customer’s lock screen without them opening anything. For a salon, that can be a reminder that the customer’s usual six-week cut is due. For a cafe, a note that they are one coffee from a free one.

Google sets rules. A message with the TEXT_AND_NOTIFY type adds a message to the pass and triggers a push. Updating fields such as the points balance can also trigger a notification. But both message and update notifications are limited to 3 per pass in a 24-hour period, and customers must have Wallet notifications switched on to receive them.

Three a day is a ceiling, not a target. A customer who gets a ping every day will archive the card. Better triggers are rare and specific:

• One stamp left before a reward
• A reward that is about to expire
• A birthday treat
• A quiet-day offer, such as a weekday morning slot in a salon
• A short, timed push for a new product in a shop

Our customer engagement tools include push notifications and location-based alerts, so a card can remind customers when they are near your store. Use that sparingly too.

What the card needs to work in a real business

Technology is the easy part. These are the things that decide whether customers keep using the card.

A reward worth walking in for

A free coffee after ten stamps is a common cafe pattern. A salon might reward every fifth visit. The right number depends on your average visit gap and margin. If the reward is too far away, customers give up. If it is too close, you give away margin. Start with something a regular can reach in a month or two, then adjust using your data.

A counter routine staff will actually follow

Stamping must take two seconds. Put the QR code at the till, train every team member to ask at payment, and make sure each person who stamps has the right access. Our platform includes team access controls and extra scanners for busy locations, so a second till or a stylist’s station does not become a bottleneck.

An easy way to join

The first scan is where you lose people. Put the QR code on the counter, on receipts, on the mirror in a salon or on the cup sleeve. Tell customers the card needs no app. That is one of the main objections to loyalty programs, and wallet cards remove it.

A reason to leave a review

A loyalty card also gives you a natural moment to ask for feedback. Automated review requests after a visit can lift your Google profile rating over time, which brings new customers as well as repeat ones.

Examples by business type

Salons. Visits are predictable. A card that tracks the number of visits and reminds the customer when they are due turns a one-off cut into a routine. Our blog also covers how to boost repeat visits with a digital card for a shop.

Cafes. Frequency is everything, and the stamp card is already familiar. The difference is that a digital card cannot be left in another jacket. See our guide to the coffee shop loyalty card for ideas on reward structure.

Retail. Shops depend on impulse and reminders. A push when a customer walks near the store or a limited offer can turn a passing visit into a purchase. We go deeper in retail customer retention.

Our perspective

We talk to owners who have tried a paper card, then a points app, then given up. The pattern is nearly always the same: the program asked too much of the customer. A download, a registration form, a login. Each step costs you a share of the people who would have joined.

We believe the wallet is the right place for a small business loyalty program because the customer already trusts it and already opens it to pay. Our product is built around that idea: the card goes into Apple Wallet or Google Wallet in seconds, stamps are collected by scanning a QR code, and a push notification brings the customer back at the moment it counts.

We also think owners should be sceptical about notification volume. The ability to message customers is powerful, and the temptation is to overuse it. The platform limit of three per pass per day is a guardrail, but the real discipline is yours. One well-timed message beats five generic ones.

Finally, measure. A loyalty card is only worth its monthly fee if more customers return. That is why we offer an analytics dashboard, and why our results guarantee refunds if retention does not measurably increase.

— erenmette

Beepify plans and pricing

If you would rather not build on Google’s API yourself, Beepify gives you customizable reward cards, QR code stamping, Apple Wallet and Google Wallet support, push notifications, review automation and team access in one place. You can look at the flow before committing with our demo.

Plans as published on our pricing page:

Extra scanners cost €5 per month per scanner, and extra locations cost €25 per month per location. Enterprise covers custom POS integration and white-label solutions. See all features before you choose a plan, and read about the QR code stamp card if your main need is fast stamping at the till.

A simple launch plan

1. Pick one reward. Keep the first program simple: a single stamp card with one clear reward.
2. Design the card. Add your logo, colors and the stamp count. A card that looks like your brand feels more trustworthy.
3. Place the QR code. Put it at the till and where customers wait.
4. Train your team. Everyone asks at payment: do you have our card?
5. Test it yourself. Add the card to your own phone, stamp it and check the notification.
6. Send your first push. Use a reason that helps the customer, such as one stamp left.
7. Review after a month. Check how many cards were added, how many returned and adjust the reward.

Common mistakes

• Too many stamps. A reward 15 visits away feels unreachable.
• Notification overload. Customers delete cards that nag.
• No staff routine. If stamping depends on someone remembering, it will not happen.
• Ignoring iPhone users. A program that only works on Android excludes part of your customers.
• No measurement. Without return-rate data you cannot tell whether the card works.

FAQ

How do I add a loyalty card to Google Wallet?

The simplest way is to scan the business’s QR code with your phone camera, tap the link, choose Add to Google Wallet and confirm. You can also open the Wallet app, tap Loyalty card and search for the merchant, if the business has made its program discoverable.

Do customers need to download an app?

No separate app is needed for a wallet card. The customer uses Google Wallet, which is already on most Android phones, and the pass appears next to their other cards. With Beepify, the same card can also be added to Apple Wallet for iPhone users.

How many notifications can I send through Google Wallet?

Google limits message and update notifications to 3 per pass within a 24-hour period, and the customer must have notifications enabled. In practice, you should send far fewer, and only for useful moments such as a nearly complete card or a birthday reward.

Do I need a developer to create a Google Wallet loyalty card?

If you build directly on Google’s API, yes. You must create loyalty classes, generate signed links and, for in-Wallet enrollment, complete a verification process. A loyalty platform handles those steps, so you design the card and start stamping without writing code.

Sources

• Loyalty cards & gift cards, Google Wallet Help
• Loyalty card overview, Google for Developers
• Issuing passes for web, email, SMS, Google for Developers
• REST Resource: loyaltyclass, Google for Developers
• User Loyalty Program enrollment and Pass Upgrades, Google for Developers
• Trigger Push Notifications, Google for Developers

Recommended

• Google Wallet Loyalty Card Setup: Step by Step
• Add a loyalty card to Apple Wallet and Google Wallet
• Apple Wallet Loyalty Cards: Add by QR, Issue Without NFC
• Loyalty card app vs. Apple/Google Wallet: key differences