---
title: "Wallet pass push notifications and live updates"
url: https://getstell.com/platform/updates-and-push
description: "Wallet pass push notifications and field updates reach Apple Wallet and Google Wallet lock screens in seconds, with no app. See the documented limits."
---

# Wallet pass push notifications and live updates

# Updates And Push

Wallet pass push notifications and field updates reach Apple Wallet and Google Wallet lock screens in seconds, with no app. See the documented limits. /platform/updates-and-push Fields, in seconds Points after each purchase, tier upgrades the moment they are earned, a new offer replacing an expired one. On Apple Wallet the pass is re-signed and pushed; on Google Wallet the object is written server-side. Either way, the wallet shows the new state in seconds. Design, without reissuing The design lives in a template. Change it in the portal and every issued pass follows: a rebrand rolls out to every wallet at once, with nothing for the customer to re-add. Where a single pass needs to look different, a pass override lets it. A change on the pass can carry a message to the lock screen. It arrives through the pass the customer already chose to carry, with no app to install and no separate messaging vendor in the path. Build audiences from what the program already knows: points balance, stamps collected, tier, last visit, wallet type, birthday month. A rule like “under two stamps from a reward, no visit in the last 30 days” takes a minute in Engage, and the builder shows the estimated reach before you send. Messages that send themselves when something happens: a pass installed, a birthday, a points milestone, a tier change, a member gone quiet. Each automation can carry conditions, so only the customers it is meant for hear from it. Personal, without mail merge Messages can carry the customer's own numbers: first name, points balance, stamps, tier. Placeholders appear as friendly chips in the editor, and the preview shows the message exactly as it lands on the lock screen, sample values filled in. A pass can carry up to ten locations where it is useful. When the customer approaches one, the wallet surfaces the pass on the lock screen: no buzz, no interruption, a suggestion that appears when the pass is relevant and disappears when it is not. Where GPS is too blunt, iBeacons draw the boundary in meters: the membership desk, the gate, the counter where the pass is actually used. They work indoors, and they are private by default; beacons transmit, they do not listen. A relevant date surfaces the pass before an event or booking, so the ticket is on the lock screen when the customer reaches the door instead of buried in the wallet. How do push notifications reach the customer? Through the pass itself. Notifications ride on the pass's own update channel in Apple Wallet and Google Wallet, so there is no app to install, no phone number or email address to collect and no separate messaging vendor in the path. How many push notifications can a wallet pass send per day? Google documents a maximum of three notification-triggering messages or field updates per pass in 24 hours, and may throttle delivery beyond that. Apple's Wallet pass update documentation publishes no daily number; its update push is an empty notification that tells the device to fetch the changed pass. Whatever the ceiling, plan for a few messages a week per customer, not a few a day. Does every change to a pass send a notification? No. On Apple Wallet a lock-screen alert appears only when the field that changed carries a change message, so a silent update is the default. On Google Wallet a notification needs a message or an update set to notify, and the holder must have Wallet notifications on for that pass. Everything else updates the pass quietly. Is location surfacing the same as a push notification? No, and that is why it works. A geofenced or beacon-triggered pass appears quietly on the lock screen when the customer is nearby; it does not buzz or land in the notification list. Customers experience it as the phone being helpful, not as a brand being loud. Can we change the design of passes already in wallets? Yes. Passes are issued from a template, so a design change in the portal reaches every issued pass without reissuing: Apple Wallet passes are re-signed and pushed, Google Wallet passes follow the template edit. Can we target who gets a message? Yes. Campaigns go to every pass holder or to segments you build in Engage, Stell's messaging module, from loyalty state: points balance, stamps, tier, last visit, wallet type, birthday month. The builder shows the estimated reach before you send, and messages can be scheduled or set to recur, timezone-aware. Do we have to send every message by hand? No. Automations send on triggers: a pass installed, a birthday, a points milestone, a tier change, or a member inactive for a number of days you choose. Conditions narrow who qualifies, and a frequency cap limits how often any one customer can be messaged by automations. How fast do field updates land? Seconds, not overnight batches. Stell syncs with your CRM continuously, so a points balance can change on the pass while the customer is still at the till, and the receipt in their pocket agrees with the pass on their lock screen. / /platform /platform/updates-and-push #updates #campaigns #relevance #flow #faq / /platform Passes that follow your business . /contact /articles/category/engagement Message when it matters A reward unlocked, a tier reached, a booking about to start: the notification arrives on an object the customer chose to carry, about a relationship they opted into. Send with restraint Every change on a pass can carry a message, and most should not. Message when you have something worth saying; the channel stays respected, and the pass stays in the wallet. Relevance features vary by wallet; Stell configures each pass for what its wallet supports, today and as new wallets are introduced. How location relevance works Why it works The passes already in wallets just change. Nobody re-adds anything. You send the change once, from the portal or the API. Stell delivers it to every wallet in the form that wallet expects, and decides with you whether it deserves the lock screen. A purchase, a tier rule, a template edit in the portal Re-signed and pushed on Apple Wallet, written server-side on Google Wallet The lock screen, if it matters Wallet pass push notifications and live updates Push to the lock screen Segments from loyalty state Automations on real moments Near your store At the exact spot Ahead of the moment Updates and push Live updates How a change lands Passes stay in wallets for years; businesses change weekly. Stell reconciles the two: point balances, tiers, offers and even the design change on passes already in wallets, and every change can carry a message to the lock screen. Book a demo Read about engagement A connected pass can change. A static one is a liability. A points balance that updates overnight is a report. A balance that updates while the customer is still at the till is an experience. Stell syncs with your systems continuously, so the pass is never the stale copy of the relationship. Campaigns and automations A channel is only half the product. The other half is aim. Engage, Stell's messaging module, is a full campaign tool: compose a message, pick who hears it, schedule the send, and watch delivery land. Or set an automation once and let the moment do the sending. Location and time relevance The pass shows up before anyone asks for it. Wallets can surface a pass when it becomes relevant: near a store, at a specific counter, or ahead of an event. Not a notification, a suggestion, which is exactly why customers tolerate it. Questions about updates and push What teams ask before switching on push. See it live Watch a pass follow your business. Bring a real scenario: a points change, a tier change, a rebrand. Forty-five minutes with a specialist, and you see the change land on a pass in your own wallet.