How to Send Wallet Pass Push Notifications: A Step-by-Step Guide

Wallet pass push notifications achieve a 69% open rate. Marketing email averages roughly 20%. That gap — nearly 3.5× — exists because a wallet push lands directly on the lock screen, bypassing every inbox, spam filter and promotional tab that email has to navigate. And unlike a native app push notification, it requires no app download. The moment a customer adds your pass to their wallet, you have a direct communication channel to their device. This guide explains exactly how to use it.

How Apple Wallet push works

Apple Wallet push notifications operate through Apple Push Notification Service (APNS). Understanding the mechanism helps you design your system correctly.

When a customer adds your pass to their wallet, their device registers a push token with Apple and then calls the webServiceURL you defined in your pass bundle. This registration call tells your server: “This device has this pass, and here is its push token.” You store that token alongside the pass record.

To send a push notification, you do not send a message directly to the device. Instead, you take two steps. First, you update the pass data on your server — change the points balance, tier name, or any other field. Second, you send a lightweight payload to APNS that contains only the push token and an empty aps dictionary. This signals to the device that the pass has changed. The device then calls your webServiceURL again to fetch the updated pass bundle, and the new data appears on screen.

The lock screen notification Apple displays says something like “[Your pass name] has been updated” — you cannot customise this text directly through APNS. The notification appears automatically whenever a pass update is delivered.

You need two things to use APNS: a Pass Type ID certificate from your Apple Developer account and a webServiceURL endpoint that handles registration, update and deregistration requests. The certificate signs your APNS requests; the endpoint serves updated pass bundles on demand.

How Google Wallet push works

Google Wallet push is considerably simpler. There is no separate push certificate and no push token to manage.

To update a pass and trigger a notification, you make a single authenticated PATCH request to the Google Wallet REST API, targeting the pass object by its ID. Google automatically detects that the object has changed and syncs it to any device that has saved it.

To display an explicit notification on the device — rather than just a silent data sync — include an addMessageRequest body alongside your PATCH. This adds a message to the pass that appears as a notification. The message has a header field (short title) and a body field (one to two sentences of context). Both are plain text; no HTML or markdown is supported.

Google Wallet notifications appear on the device within a few minutes of the API call in most cases. There is no SLA guarantee on delivery speed, but in practice notifications arrive quickly under normal network conditions.

When to send push notifications

Push notifications are powerful precisely because they interrupt. Use that interruption deliberately — not constantly. Here are the scenarios where a wallet push is clearly justified:

• Loyalty point balance updates. When a customer earns points after a purchase, push the new balance immediately. The instant feedback reinforces the behaviour you want to encourage.
• Tier upgrades. Reaching Gold or Platinum status is a milestone. A push notification at the moment of upgrade makes it feel like an event rather than a quiet data change.
• Expiry reminders. Thirty days before a membership or voucher expires, send a reminder. A second reminder seven days out catches anyone who missed the first.
• Event-day reminders. For event tickets, send a push on the morning of the event. Include the venue address in the back fields so the customer can tap straight through to Maps.
• Flash sale alerts. If you have a limited-time offer relevant to the customer, a wallet push reaches them faster than email and feels more urgent. Use this sparingly — no more than once or twice per month.

Best practices for wallet push notifications

Keep messages under 100 characters. Lock screen notifications truncate at around 100 characters on most devices. Write the most important information first. “You've earned 50 points. Balance: 1,240 points” is better than a sentence that buries the number at the end.

Do not push more than once per week under normal circumstances. Customers who receive daily pushes from a loyalty card quickly associate your brand with interruption. Wallet passes stay in the wallet as long as they feel useful — push too often and the customer removes the pass.

Personalise where possible. Include the customer's name or their current balance in the notification text. “Hi Emma, your Gold membership renews in 30 days” outperforms “Your membership renews soon” in every retention metric.

Time notifications sensibly. Sending a push at 2 am achieves nothing useful and may cause the customer to remove the pass. For non-urgent messages, schedule delivery between 9 am and 6 pm in the customer's local timezone.

Update the pass data alongside the notification. A notification that announces “You've been upgraded to Gold” but opens to a pass still showing Silver is a frustrating experience. Always update the pass fields before or simultaneously with sending the push.

What you cannot do with wallet push notifications

Wallet passes are not a replacement for a native app push channel. There are meaningful restrictions to understand before building your system around them.

No URLs in notification text. The notification displayed on the lock screen is plain text only. You cannot include a clickable URL in the notification message itself. You can, however, update the back fields of the pass to include a relevant URL — the customer taps the notification, opens the pass and taps the link in the back fields.

No images or rich media. Unlike native app push notifications, wallet pass notifications cannot include images, action buttons or expandable content.

On Apple, you cannot set custom notification text. Apple generates the notification text from the pass update event. You have no control over the exact wording of the lock screen message for Apple Wallet passes. Google Wallet's addMessageRequestgives you full control over the notification copy.

Delivery is not guaranteed. Both APNS and Google Wallet push are best-effort delivery systems. If a device is offline, the notification may be delivered when it comes back online, or it may be dropped. Do not use wallet push for time-critical communications where guaranteed delivery is required.

How Issuepass makes push trivial

Managing APNS certificates, building a registration endpoint and handling Google Wallet PATCH requests from scratch takes days of engineering time. Issuepass handles all of it.

From the dashboard, you can send a push notification to a single pass, a segment or your entire pass list in three clicks: select the passes, write the message and click Send. We handle the APNS delivery for Apple Wallet passes and the Google Wallet addMessageRequest for Android simultaneously.

From the API, sending a push notification is a single POST request with the pass ID and the updated field values. We take care of the push token lookup, the APNS payload construction and the Google Wallet PATCH — returning a 200 when both have been dispatched.

You can also trigger pushes automatically from your CRM or automation platform using our webhooks and HubSpot integration — so a tier upgrade in your CRM fires a push notification without any manual step.

Start free and send your first wallet push notification today.