Apple Wallet and Google Wallet loyalty cards: what they can and can't do
What Apple Wallet and Google Wallet loyalty cards can do: lock screen near 10 places, 3 notifying messages in 24 hours, card fields and updates, with sources.

A loyalty card in Apple Wallet or Google Wallet can show a stamp count or balance, update after every visit, appear on the lock screen near up to ten of your addresses and carry short messages. It cannot take orders, run games or promise to show up at a set moment, because the phone decides when. On Google Wallet you also get at most three messages that trigger a notification in 24 hours. Below is each limit with its source, so you know what you can promise customers and your staff.
Every platform fact in this article comes from Apple's and Google's own developer pages, which we read again on 5 November 2026. The links are next to each fact.
The short version
Apple Wallet | Google Wallet | |
|---|---|---|
Pass type for loyalty | Store card: for business loyalty cards, gift cards or point cards | Loyalty card |
Shows balance or points | Yes, a store card can display a balance or point accumulation | Yes, points and rewards are visible on the phone |
Lock screen near a place | Up to 10 locations, the system decides | Up to 10 merchant locations, Google decides |
Notifying messages | No count in the pages cited here | At most 3 in 24 hours |
Card changes after saving | Yes, through an update service | Yes, the card is patched |
The rest of the article explains what each row means for a café, bakery or salon.
Lock screen and location: ten places, and you do not pick the moment
Apple. A pass can be relevant on a date, at a location or both. Apple's page on the lock screen says the system displays the pass when the date and any location match, and that a pass can have only 10 relevant locations. For a chain it advises to "start with the best ones". It also notes that the Simulator does not show passes on the lock screen, so a real phone is the only test.
Google. Since 14 October 2025 Google Wallet can send a notification when a customer enters a merchant location, with up to 10 locations per card design and per card (Google release notes). Google's page on notifications adds three conditions: the customer has notifications on, has given Google Wallet precise, always on location access, and Google decides how close they must be and how long they must stay. Google also writes the notification text.
Two examples, both illustrative:
- Say a bakery has three shops and a market stall. That is 4 of the 10 places, so every address can be on the card.
- Say a chain has 14 shops. Only 10 fit, so you choose the busiest ones. A customer standing outside the other four gets nothing.
The honest promise to a customer is "the card may remind you when you are near us", not "it will pop up when you walk past". For when and why to use location at all, read how geotargeting works in a mobile wallet. In Rewardly, location notifications come with the Advanced plan and above.
Messages: three that notify in 24 hours on Google Wallet
Google's developer page says: "You may send a maximum of 3 messages that trigger a push notification in a 24 hour period." It adds that Google may throttle delivery "if it deems you are spamming your users". A message sent without the notify flag only sits on the card and does not ring the phone. We did not find a message count in Apple's pages, so plan for the stricter Google rule.
Say a café writes to its members once a week. Google allows 3 notifying messages a day, which is 21 a week, so one a week uses under 5% of the room. The limit only bites on a busy day. Say launch day has a welcome message, a first offer, a reminder and an event notice: the fourth is over the limit. Send one.
Frequency should follow your customers, not the limit. In Rewardly's data, a coffee shop member who comes back at all does so after a median of 15 days (how soon loyalty members come back, by industry), so a message every two weeks matches that rhythm. Rewardly measures a 90% read rate on wallet messages, so a few well timed messages do reach people. Push notifications come with the Advanced plan and above, see push notifications.
Card fields: front for the balance, back for the rest
Apple groups the text on a pass into fields: header fields at the top, primary fields for the most important information, secondary and auxiliary fields for supporting information on the front, back fields on the back and an Additional Info section below the pass (Apple, pass fields). You do not edit these by hand in Rewardly. You choose the design and the reward text, and the card shows the stamps or the balance.
Use that to decide what goes into your reward text: one short line a customer reads in two seconds, such as "Free coffee after 10 stamps". Opening hours, long terms and the address belong on your website, not on the card.
A pass with a number of uses works the same way. A 10 visit pass shows the remaining entries on the card, and the number goes down after each use. Passes are a Professional plan feature.
To see how a card looks before you set anything up, design it in the free loyalty card maker.
Updates: when the card changes and when it does not
On Apple, the phone registers the pass with your server. When something changes, the server sends a push, the phone asks for the updated pass and the card refreshes (Apple, update web service). On Google, a change to the card design reaches every card of that design and shows when the phone next syncs. You never have to do this by hand.
In Rewardly, every stamp or purchase rebuilds the card and updates it in both wallets, so the balance is current after the scan. A change to the design or the reward text shows on new cards at once and on existing cards with the customer's next stamp or purchase. When you change the location addresses, the dashboard lets you update cards already in wallets once in 24 hours.
What to do tomorrow: change your reward text on a Monday and tell staff. Regulars see it on their next visit. A customer who never returns never sees the change, so do not count on an edit to reach people who left.
What a wallet card cannot do
- Orders, bookings, a menu with photos, games or chat. Those need an app. Building a loyalty app: costs and 10 questions lists what an app contains and costs, and loyalty app vs wallet helps you decide.
- Appear on demand. The system chooses the moment, on both platforms.
- Work on a phone with neither wallet. The card is saved to Apple Wallet on an iPhone and to Google Wallet on Android. There is no web only version of the card, and a desktop browser only shows a QR code to scan with the phone.
- Make a weak reward interesting. The card ends lost cards and gives you visit counts. The reward still has to be worth the trip. How customers join is covered in the guide to digital loyalty cards.
FAQ
Can a wallet loyalty card send notifications?
Yes. On Google Wallet a message can trigger a notification, up to 3 in 24 hours. On an iPhone the card can also appear on the lock screen near your addresses, and Google Wallet sends a nearby notification. In Rewardly push notifications are included from the Advanced plan.
How many locations can one wallet card use?
Up to 10 on Apple Wallet and up to 10 on Google Wallet. If you have more shops, put the busiest ten on the card.
Do customers need an app for an Apple Wallet or Google Wallet card?
No. They scan a QR code or open a link, fill in a short form and save the card to the wallet that is already on the phone.
Does the card update after it is saved?
Yes. In Rewardly the balance changes after each stamp or purchase. Design edits reach existing cards on their next update.
Should I choose Apple Wallet or Google Wallet?
You do not choose. An iPhone sees the Apple Wallet button and an Android phone sees the Google Wallet button, so one card covers both.
Set up your wallet loyalty card. Try Rewardly for €0
No upfront payment, 14 days free.


