Push Notifications Without an App: How Wallet Passes Fill the Gap

The conventional wisdom says that if you want to send push notifications, you need a mobile app. Build it, submit it to the App Store, wait for approval, convince customers to download it and then ask them to opt in to notifications. The reality is that most businesses cannot afford this — and even those that can face a significant drop-off at every step.

Wallet passes change this equation entirely. A customer adds a pass to Apple Wallet or Google Wallet with a single tap. No download, no App Store review, no permission dialogue beyond the initial "Add" button. And adding the pass implicitly enables the pass holder to receive lock screen notifications whenever the pass is updated. This is push without an app.

The Real Cost of a Native App

Building a native iOS and Android app for a small or mid-sized business costs between £50,000 and £200,000 in development — and that is before ongoing maintenance, OS updates and the engineering time needed each time a feature changes. App Store submission takes days to weeks, with no guarantee of approval on the first attempt.

Even after all that investment, you face a conversion problem. Push permission opt-in rates for native apps average around 60% on iOS — meaning 40% of your users who went to the trouble of downloading your app will never receive a push notification. On Android, the numbers are better, but push fatigue is real across both platforms. Users who download apps but disable notifications are a sunk cost.

Web push notifications are an alternative some businesses explore. Browser-based push has its own friction: users must opt in through a browser permission dialogue that most people dismiss. Web push does not work on iOS Safari in the same way. Deliverability varies significantly by browser and device.

How Wallet Pass Push Works

Apple Wallet. When a customer adds a .pkpass file to Apple Wallet, the Wallet app registers a push token with Apple's Push Notification Service (APNs). It then sends that token — along with the pass type identifier — to your pass server. When you want to notify the pass holder, you send a lightweight push payload to APNs. This tells the device that an updated version of the pass is available. Apple Wallet fetches the updated pass from your server and displays the new information. The customer sees a lock screen notification.

Google Wallet. The mechanism is different but the outcome is similar. You make a REST API call to update the pass object in Google's systems. Google Wallet reflects the update and, depending on the update type, shows a notification to the pass holder. There is no separate push registration step — the update is triggered entirely server-side.

The practical result is the same from the customer's perspective: they add a pass once, and from that point forward they can receive relevant, timely updates on their lock screen without installing anything.

Why the Open Rate Numbers Matter

Push notifications from wallet passes achieve an open rate of approximately 69% — compared to roughly 20% for marketing emails and around 35% for SMS (already accounting for opt-outs and carrier filtering). This is not a subtle difference. For a loyalty programme with 10,000 active members, the difference between a 20% email open rate and a 69% wallet push open rate is 4,900 additional people seeing your message.

Email inboxes are saturated. Spam filters are aggressive. Many businesses find that even well-crafted campaigns see open rates drop below 20% as their list ages. SMS is expensive per-message and opt-out rates are climbing as customers grow more protective of their phone numbers. Wallet push sits in a genuinely different category: it feels less intrusive than SMS, is not subject to spam filtering and is read in the context of the customer already using their phone.

Use Cases Where App-Less Push Excels

Loyalty balance updates. When a customer earns points or their tier changes, push a pass update showing the new balance. The customer sees their updated points on the lock screen without opening anything. This drives re-engagement at the exact moment they are most likely to act.

Expiry reminders. Push a notification 30 days, 7 days and 1 day before a voucher or membership expires. The visual countdown on the pass face creates urgency without requiring a customer to check their email.

Flash sale alerts. Update a loyalty card with a time-limited offer. The push notification fires at the moment you want attention. Because the pass is already in the customer's wallet, there is no re-engagement barrier — they are already opted in.

Event day communications. Update an event ticket with the door open time, gate assignments or last-minute schedule changes. Push the update on the morning of the event when the customer will actually act on it.

Appointment confirmations and reminders. Issue a pass for an upcoming appointment. Push a reminder 24 hours and 1 hour before. The pass shows the address, time and any preparation instructions.

Channel Comparison

The Honest Limitations

Wallet push is not a replacement for every channel. It has real constraints that you should understand before building a strategy around it.

No rich media. You cannot include images in a wallet push notification. The notification is text-only, drawing from the pass fields you update. This makes wallet push unsuitable for campaigns where visual design is the primary vehicle — product launches with hero images, for instance.

No deep links into an app. If your engagement goal requires the customer to land on a specific screen in your app or website, wallet push can only link to a URL. There is no native deep-link mechanism to a specific section of an app.

Message length is limited. The notification text that appears on the lock screen is drawn from the pass field values — typically around 100 characters before truncation. You are writing update copy, not marketing copy.

Wallet push works best as a contextual, transactional notification channel — informing customers about changes to something they already have in their wallet. Pair it with email for rich content delivery and SMS for genuinely urgent messages.

How Issuepass Makes Wallet Push Trivial

Sending a wallet push with Issuepass requires a single API call to update a pass field. Set the push flag to true and every holder of that pass receives a lock screen notification. For automated programmes — loyalty balance updates, expiry reminders — you can set up rules that fire push updates based on data changes without writing additional code.

If your team uses HubSpot, the native Issuepass card in the contact sidebar lets you trigger a pass update — and the associated push — directly from the contact record. No API call needed, no developer involvement.

There is no app to build, no App Store review to wait for and no per-message cost. Start free and send your first wallet push in minutes.