Wallet pass notifications are often reported to have an approximately 90% open rate, but Apple Wallet and Google Wallet don’t report notification opens or pass views. That figure comes from wallet pass operators’ lock-screen interaction data, so it isn’t a platform-reported open rate. For push notifications for wallet passes, understanding what the metric measures matters as much as the headline number.
It’s reasonable to want a clear way to judge whether customers saw a message and whether it brought them back. Push notifications for wallet passes work differently from app push alerts, and results depend on delivery, customer settings, and what happens after a tap.
This guide explains how to interpret reported open rates, manage message frequency, and add relevant URLs. You’ll also learn how Apple Wallet and Google Wallet notifications reach customers, and how wallet passes can share timely updates without requiring a separate mobile app.
Key Takeaways
- Set a sustainable sending rhythm: platform limits are ceilings, not a target for routine campaigns.
- Make each update useful and easy to act on, since Apple Wallet and Google Wallet handle pass changes differently.
- Use links that clearly relate to the pass, so customers know where a tap will take them.
- Reach customers through the wallet already on their phone, without requiring a separate mobile app.
- Connect digital loyalty tools to your customer communication plan when you’re ready to manage rewards and pass updates in one experience.
What are wallet pass push notification open rates?
-
Interpret the reported rate before comparing channels.
Some wallet pass operators report an approximately 90% open rate, based on lock-screen interaction data. Apple Wallet and Google Wallet don’t report notification opens or pass views themselves. Treat the figure as an operator-reported estimate, not a platform analytics metric. A customer seeing a lock-screen alert is not necessarily the same as tapping it or redeeming rewards.
Standard app push benchmarks use different measurements. Reported averages are 5-11% on iOS and 4-8% on Android. Compare these figures carefully: app opens, lock-screen visibility, wallet taps, and purchases describe different actions. For example, a customer might see a loyalty update, ignore it, then use the pass at checkout.
-
Track outcomes beyond the notification.
Give each message a clear next step that connects it with a customer action. A loyalty update might point to a reward threshold, while a ticket update might explain a schedule change. Track observable campaign actions, such as visits or redemptions, separately from opens. This gives you a more useful view than treating every delivered alert as engagement.
Wallet pass fields can trigger an alert when a change message is configured. Only front and back fields trigger these notifications, and simultaneous field changes are combined into one notification. For example, updating a points balance and reward status together can produce one alert, not separate messages for each field.
-
Choose campaign features that fit the pass.
Pass updates can change personalized fields on one wallet pass or add information to a field across passes. Keep the message brief and relevant to the pass holder. A points balance crossing a reward threshold is a useful example; unrelated promotional copy is less suited to an update triggered by a pass change.
Plan campaign costs around the sending platform, provider arrangements, and the work required to prepare updates. Don’t use an open-rate estimate to calculate a campaign budget or assume every provider charges the same way. Before sending, define the audience, the pass field that will change, and the action customers should take.
-
Separate Google Wallet boarding-pass alerts from campaign reporting.
Google Wallet can send nearby notifications for passes that include merchant locations, and tapping one opens the pass. That doesn’t establish that a business campaign message was opened. For a boarding pass, distinguish pass-related notices from a campaign deliberately sent through a pass update.
For any Google Wallet alert, identify its trigger first: a nearby location, a changed pass field, or a message associated with the pass. Then measure a customer action your campaign can observe, such as a redemption. This prevents automatic pass interactions from being mistaken for campaign opens.
Notification frequency limits
Google Wallet currently allows three notifications per day per pass; Apple Wallet currently allows twenty notifications per day per pass. Apple Wallet alerts accompany pass updates and are intended for critical changes, not unsolicited marketing.
-
Balance frequency with customer trust
Set a useful cadence before sending loyalty card updates. For most consumer brands, a practical starting point is about once a month to once every six weeks. Sending more often can make alerts feel less valuable and encourage customers to remove the pass. Reserve each message for a meaningful change, such as a new reward or an important service update.
-
Check Apple Wallet sending requirements
Use Apple Wallet notifications for genuine pass changes, and make the message explain what changed. The alert accompanies a pass update, so don’t treat it like an independent marketing blast. Apple Wallet users can control or disable pass notifications. Separate app-based promotional push notifications require explicit user permission and a clear opt-out.
-
Keep Google Wallet below its technical ceiling.
Google Wallet’s current limit is three notifications per day per pass. That’s a maximum, not a recommended campaign schedule. Google may throttle delivery if it determines that an issuer is spamming users. Consolidate related information into one clear update instead of triggering repeated alerts for small pass changes.
For example, combine a loyalty balance change and a newly available reward when both belong in the same update. One useful message is easier to understand than multiple alerts competing for attention. Check the message trigger and pass field before sending, especially when updates are automated.
-
Choose timing around the customer’s next action.
Schedule campaign messages for a moment when customers can respond. Suggested windows are 11 AM to 1 PM and 6 PM to 8 PM. Match timing to the offer: a lunch reward makes sense before lunch, while an evening promotion should arrive before customers decide where to go. Avoid sending merely because a pass field changed.
-
Build a simple frequency plan.
Record the reason for each notification, its audience, and its trigger. Then check the calendar for overlapping sends before scheduling. A monthly loyalty update can share a meaningful reward, while an urgent pass correction may need separate treatment. Review customer responses and pass removals, then adjust the schedule to keep messages relevant.
A structured loyalty program can help connect reward activity with purposeful customer communication.
How wallet push notifications appear on Apple and Android devices
Apple Wallet and Google Wallet create alerts through their native wallet apps. Check each platform’s triggers and device settings before planning pass messages.
-
Review platform differences
Plan separately for Apple Wallet and Google Wallet because their notification triggers differ. Both can surface a pass based on a customer’s location, while pass-field changes can also prompt alerts. On Android, Google Wallet users need notifications enabled for their passes. A lock-screen banner comes from the wallet app, not a separate business app.
Google Wallet users can swipe away nearby pass notifications; alerts also disappear when they leave the location. For boarding passes or loyalty cards, explain the relevant update clearly. Don’t assume every member has the same device settings or sees an alert at the same moment.
-
Use location-based notifications
Choose locations that give a pass a clear reason to surface. Apple Wallet passes can include up to 10 relevant locations for contextual notifications. Google Wallet pass classes and objects can each contain up to 10 merchant locations. A customer’s phone can trigger a location-based alert when the customer is near a saved location.
Tie each saved location to the pass experience, such as a store connected to a loyalty offer. Location-based reminders using GPS proximity work with Apple Wallet and Google Wallet. Apple Wallet also supports Bluetooth beacon reminders; Google Wallet does not. Account for that difference when planning a store reminder.
-
Set meaningful value-change triggers.
Use a pass value that gives members a useful reason to look again. Apple Wallet can surface a notification when a value changes, such as a points balance or expiration date. Google Wallet can trigger alerts when specified pass fields change. A points balance crossing a reward threshold is one practical example.
Before updating a field, decide what the customer should understand from the alert. A new balance may matter because it unlocks a reward; a routine correction may not need attention. Tie the changed value to a clear benefit or action, so the update makes sense on a phone’s lock screen.
-
Check the customer’s device experience.
Preview the pass in Apple Wallet and Google Wallet before distributing it. Confirm that the relevant field or saved location supports the intended trigger, then test how the notification reads as a banner. A concise message helps customers recognize whether an alert concerns boarding details, a points change, or a nearby store.
For Android users, account for disabled Google Wallet notifications in your delivery expectations. For Apple Wallet, check that the pass value or location matches the intended alert. These checks help distinguish a platform trigger from a customer action, such as opening the pass or visiting a location.
Including relevant URLs in notification messages
Choose a destination that supports the pass message. Apple Wallet and Google Wallet handle links differently, so test the format before sending a campaign.
-
Match each link to the pass-holder’s next step.
Use a URL that directly supports the wallet pass experience. A loyalty message about points could lead to relevant reward details; a ticket update could lead to event information. Apple Wallet and Google Wallet require links in pass messages to relate to the pass. Don’t send customers to an unrelated homepage or a general promotion that doesn’t explain the alert.
Keep the on-screen experience in mind. A notification should explain why its link matters, rather than show a bare address without context. For example, “View your updated points balance” sets a clearer expectation than a shortened link alone. Focus the message on one action, so customers can decide whether to open it.
-
Format Google Wallet links deliberately.
Google Wallet doesn’t automatically turn URLs in notification messages into clickable links. An HTML anchor tag can make a URL clickable, so use that format when the message needs a tap-through destination. Preview the message as it will appear in Google Wallet, then confirm the anchor text describes the page customers will reach.
For marketing or promotional messages, Google Wallet generally requires direct interaction with its API. Plan the sending method before building a campaign around a message. A field update and a promotional message aren’t interchangeable: choose the one that matches the purpose and content of the communication.
-
Make Apple Wallet destinations easy to find.
Apple Wallet automatically converts URLs on the back of a pass into links. Put helpful destinations there, such as a page explaining reward terms or ticket details. Don’t assume a URL inside a notification message will behave the same way. Keep the notification clear, and place pass-related links where customers can find them.
Test the full customer journey on an Apple device: read the alert, open the pass, and tap the relevant back-of-pass link. A short label such as “Reward details” tells customers what the destination contains. Make sure the alert’s promise matches the page it opens.
-
Separate promotional consent from device settings.
Promotional messages generally require explicit marketing consent, separate from phone notification settings. A customer enabling Apple Wallet or Google Wallet alerts hasn’t necessarily consented to marketing. Tie consent to the promotional purpose, and clearly identify a message as an offer when it includes one.
-
Vary repeated campaign messages.
Before sending, compare the new copy with the previous message. Identical back-to-back text can make a points offer feel like a duplicate rather than a useful update. Change the wording only when the underlying information or next action changes. For example, distinguish a newly available reward from a reminder about the same reward.
Notification delivery without a mobile app
Apple Wallet and Google Wallet deliver pass notifications through their native wallet apps, so customers don’t need to download a separate business app. Alerts may not arrive if pass notifications are disabled or an update lacks a valid trigger. Check wallet settings, pass fields, message settings, and certificate configuration.
-
Confirm the customer’s wallet settings.
Start by checking whether notifications are enabled for the pass. Google Wallet users must allow pass notifications to receive message alerts. Customers can also control or disable notifications for their passes. For example, an Android customer with Google Wallet notifications turned off won’t receive that pass’s alert through the usual channel.
Explain where the alert should appear, such as on the device’s lock screen, and remind customers that opening the wallet pass is separate from seeing a notification. Dismissing a notification doesn’t remove an alert already delivered, although deleting it removes the pass’s “Last Notification” field.
-
Check that the update can trigger an alert.
Review the changed pass field before troubleshooting delivery. Only changes to front and back fields trigger wallet push notifications, and the field needs a specified change message. If an update changes a hidden or ineligible field, it won’t create the expected notification. Combine related changes into one clear customer message.
For example, updating a points balance without setting its change message won’t provide the trigger needed for an alert. Add a concise message explaining the balance change, then test the update on the intended pass type before relying on it to engage members.
-
Validate Apple Wallet certificate settings.
For existing Apple Wallet passes, use the same certificate used to create the pass. The certificate for push notifications must also be valid. A mismatched or invalid certificate can prevent delivery, even when the pass update and message appear correctly configured.
Check these settings together: the certificate matches the original pass, remains valid, and the update includes a change message on an eligible field. This gives you a practical troubleshooting sequence before changing the campaign or asking customers to download anything.
-
Test the full delivery path.
Send a controlled test update to a pass, then check whether its message appears on the device. Verify the specific wallet app, notification setting, eligible field, and certificate configuration. If the alert is missing, change one setting at a time so you can identify whether the trigger or delivery setup caused the issue.
After delivery, open the wallet pass and review its “Last Notification” field. It displays the latest message on the back of the pass, giving you another way to inspect what customers can see beyond the lock screen.
BonusQR: Loyalty application
BonusQR offers a digital loyalty application and platform for businesses building customer rewards. For wallet-based loyalty communication, its loyalty software and Digital Stamp Card help organize the rewards experience alongside your customer engagement strategy.
Turn to BonusQR when you’re ready to move beyond individual pass updates and build a structured loyalty program. A Digital Stamp Card suits businesses that reward repeat visits, while the loyalty application supports a branded digital experience for customers. Choose an approach that fits how your business rewards members and shares useful updates.
Explore BonusQR’s loyalty options and choose a suitable next step for your business.
Make your next wallet update part of a loyalty plan
Make your next pass message a deliberate customer touchpoint. Decide what action you want customers to take, then connect it to a loyalty experience they can keep using. This shifts attention from a single notification to the ongoing relationship built around rewards and repeat visits.
For businesses building that experience, BonusQR offers a loyalty application, loyalty platform, and loyalty software. Digital stamp cards and points systems can support a broader customer rewards strategy alongside push notifications for wallet passes, helping you plan how pass communication fits your loyalty program.
Choose one practical next step: map a customer action to a reward, then decide how your loyalty experience will support it. Contact BonusQR about wallet passes and explore how to shape your next step with confidence.
Frequently Asked Questions
How do push notifications work for Apple Wallet passes?
Apple Wallet alerts customers when an eligible pass field changes and includes a change message. The pass must already be on the customer’s device, and notifications must be enabled. For example, a business can update a loyalty balance and explain the change in the alert. When several pass fields change together, the updates are combined, giving customers one clear notice rather than separate alerts.
How do push notifications work for Google Wallet passes?
Google Wallet can show a notification when a pass field changes or when a customer is near a saved merchant location. Tapping a nearby-pass alert opens that pass in Google Wallet. For a local loyalty offer, connect the saved location and message to the pass’s purpose. Customers also need notifications enabled for the pass, so a silent device setting can affect what they see.
Can businesses send push notifications to wallet passes without a dedicated app?
Yes. Notifications reach customers through Apple Wallet or Google Wallet, so they don’t need to download the business’s separate app. They do need the relevant wallet pass installed. For example, a café can share a digital loyalty pass, then use a relevant pass update to reach members through their phone’s wallet. Wallet messaging is one channel alongside, not a replacement for, other customer communications.
What types of updates can wallet pass notifications deliver?
Wallet notifications can highlight a meaningful pass change, such as a points balance, reward status, or expiration detail. A nearby-location alert can also surface a relevant pass for a customer. Choose an update based on what the holder needs to know next. For example, explain that a changed balance has unlocked a reward, rather than sending a vague message that doesn’t connect the change to a useful action.
How do users enable or disable notifications for wallet passes?
Users manage pass notifications through their wallet or device notification controls and can turn them off. Google Wallet requires notifications to be enabled for the pass to receive message alerts. If someone stops seeing alerts, first check the pass-specific setting and the device’s notification controls. Customers can still open a saved pass manually, but may not see a new alert on the lock screen.
What are the costs of wallet pass notification platforms?
There isn’t one standard cost for wallet pass notification platforms. Pricing can depend on the platform’s plan, the number of passes or messages, and features such as campaign management or integrations. Compare what each plan includes with the tasks you need to perform. For a small loyalty program, focus on pass creation, update tools, and the communication features you’ll actually use.
What are the limits and requirements for sending notifications to Google Wallet passes?
Google Wallet currently allows a maximum of three notifications per day per pass. The pass needs an eligible field update with a change message for this type of alert, and users must have notifications enabled. Google may throttle delivery if it identifies issuer spam. Promotional Wallet messages generally require direct interaction with the Google Wallet API, so plan that method separately from ordinary pass updates.
How do businesses create, update, and distribute a wallet pass with notifications?
Start by creating a pass with fields suited to its purpose, such as loyalty points or ticket details. Configure the message for an eligible field, then test the pass update in Apple Wallet and Google Wallet. Distribute the pass through a customer-facing channel, such as a QR code or business website. Before launch, review the customer’s full journey from saving the pass to receiving and understanding an update.
