Wallet push notifications: talk to customers without an app or spam
A channel your customers didn't have to install
When a customer saves your card to Apple Wallet or Google Wallet, you get something rare: a direct line to their lock screen. No app, no email inbox full of promotions and no SMS costs.
That channel is only valuable as long as the customer trusts it. One needless message too many, and the card gets deleted. This guide shows how Wallet notifications work, what to send and when, and how to keep it all GDPR-compliant.
How Wallet notifications actually work
A Wallet notification isn't a classic app push. It's the result of a change to the card: you update a detail, and Wallet lets the customer know.
Apple Wallet. A lock-screen notification appears when the value of a field on the card changes, e.g. the points balance or the offer text. You define a message for each field in advance, and the system inserts the new value into it. Example: "You now have 50 points!" When the customer taps the notification, the card opens with the change highlighted. Apple's Wallet guidelines ask that change notifications be used only for information that matters to the customer at that moment, and never for marketing.
Google Wallet. You add a message to the back of the card and flag it to trigger a notification. The customer taps to open the card and sees the new message on its back. According to Google's documentation, Google Wallet sets the text of the actual lock-screen notification, and each card can receive at most three notifications in 24 hours.
| Apple Wallet | Google Wallet | |
|---|---|---|
| What triggers a notification | A change to a field value on the card | A new message flagged for notification |
| Who writes the notification text | You, with the new value in the message | Google (your message is on the card) |
| Sending limit | No publicly stated number | At most 3 notifications per card in 24 hours |
| Links | On the back of the card | In the message, only to content related to the card |
For you as a merchant, that means one thing: you don't "send" a message, you change the card. So every notification needs a reason on the card itself: new points, a new reward or new information.
Six rules against spam
A customer can delete your card with a single swipe. These rules protect their trust.
- Every message has to be useful to the customer. Ask yourself: would the customer want to know this even if they didn't buy anything? A new stamp, a reward that's ready, points about to expire: yes. A generic ad: rarely.
- Less is more. For marketing messages, one or two a month is enough, with a notification only on Google Wallet. On Apple Wallet, put the offer on the card without a notification. Send transactional ones (stamps, points) when something actually happens.
- Keep it short. The Apple Wallet lock screen shows one sentence, and on Google Wallet, too, customers read the message at a glance. Put the important information first: "Your coffee is waiting. 1 more stamp to a free one."
- Mind the timing. Don't send at night or early in the morning. Send a lunch offer around 11 am, not at 3 pm.
- Personalize as much as you can. "You have 8 of 10 stamps" works better than "Visit us". The card already knows where the customer stands, so use that.
- Always explain how to opt out. On the back of the card, say how to turn off notifications or delete the card. Customers who know they can leave are less likely to.
Example messages customers want to get
The best messages follow a real event on the card. You can adapt these examples to your own tone.
| Industry | Situation | Message text | Type |
|---|---|---|---|
| Café | Stamp added | You have 8 of 10 stamps. Two more coffees to a free one! | Transactional |
| Café | Reward ready | Your free coffee is waiting. Show your card at the counter. | Transactional |
| Café | Quiet hours | It's quiet here this afternoon. Double stamps from 2 to 4 pm. | Marketing |
| Gym | Membership expiring | Your membership expires in 5 days. Renew at the front desk or online. | Transactional |
| Gym | Schedule change | Thursday's group class starts at 7 pm instead of 6 pm. | Transactional |
| Gym | Inactivity | We miss you! Bring a friend for free this week. | Marketing |
| Salon | Points | You have 120 points on your card, enough for a free facial. | Transactional |
| Salon | Birthday | Happy birthday! Enjoy 20% off all treatments this month. | Marketing |
| Events | Day before | See you tomorrow! Doors open at 7 pm, entrance B. | Transactional |
| Events | Change | The concert has moved to Hall 2. Your ticket is still valid. | Transactional |
Notice the difference. Transactional messages tell customers something about their status or a service they already use. Marketing messages nudge them toward a new purchase. That difference matters under the GDPR, too.
GDPR: what European merchants need to know
The GDPR doesn't ban Wallet notifications, but it does distinguish service messages from marketing. The key is knowing which category each message falls into.
Service messages (a new stamp, a points balance, a membership about to expire, a rescheduled appointment) relate to the relationship the customer already has with you. They can usually be based on performance of a contract or legitimate interest, backed by an assessment that justifies it.
Marketing messages (discounts, new offers, invitations to buy) as a rule require consent. An overview from GDPR Register notes that the ePrivacy Directive (2002/58/EC) generally requires prior consent for direct electronic marketing, even when a company relies on legitimate interest. The same source points out that under Article 21 of the GDPR, customers always have the right to object to marketing.
What this means in practice:
- Keep consents separate at sign-up. Ask for marketing consent separately from accepting the terms, and make it optional, e.g. with a separate, unchecked box: "I'd like to receive offers and news." Without it, send only service messages.
- Don't mix message types. A new-stamp message that also advertises a promotion becomes marketing. If the customer hasn't given consent, keep it purely informational.
- Collect only what you need. For a stamp card, a name and an email address or phone number are enough. Ask for a date of birth only if you actually use it, e.g. for a birthday reward.
- Make leaving easy. On the back of the card, explain how to turn off notifications, withdraw consent or ask for their data to be deleted.
- Check your service provider. You need a data processing agreement (DPA) with the platform that issues your cards, and you need to know where the data is stored.
- Keep records. Note when and how each customer gave consent. That's your proof if anyone asks.
This is not legal advice. Member states implement the ePrivacy rules differently, so check your case with a lawyer or against your national data protection authority's guidance.
A checklist before every message
Before you send, answer these seven questions.
- Is this a service message or a marketing message?
- If it's marketing, have all recipients given consent?
- Is the most important information visible in the first sentence?
- Is the message personalized (name, points, stamps)?
- Am I sending at a reasonable time of day?
- Have I already messaged this customer recently?
- Does the back of the card say how to opt out?
The bottom line
Wallet notifications are the most direct channel you have to your customers, but only as long as customers find them useful. Send less, keep it relevant, and draw a clear line between service messages and marketing.
In Walletap, you set up messages for stamps, points and memberships once, and the system sends them automatically whenever something changes on the card. Send marketing campaigns only to customers who have agreed to receive them.
Want to set up notifications for your program? Get in touch and we'll help you write the first messages for your card.