Back to BlogGeneral

Apple Wallet and Google Wallet loyalty passes: 20 questions

A wallet loyalty pass is a file the customer keeps in Apple Wallet or Google Wallet and a business updates from its own server. Apple calls the loyalty style a store card; Google models it as a class and an object. The twenty answers below come from Apple’s and Google’s own developer documentation

Twenty questions about Apple Wallet and Google Wallet loyalty passes, each answered from Apple’s and Google’s own developer documentation, with the page cited.

By Zakaria Fahim · September 5, 2026 · 9 min read

Wallet loyalty passes are documented in public, by the two companies that built them, and most of the questions businesses ask have a published answer. The twenty below are taken from Apple’s Wallet Developer Guide and Google’s Wallet documentation, fetched on 5 September 2026, with the exact page named for each in the source note on this article.

Two answers are about Fideliya rather than about the platforms, and they say so. Everything else is the platform’s own statement about itself.

QuestionApple WalletGoogle Wallet
Loyalty stylestoreCardLoyalty class plus loyalty object
How a customer adds itMail or Safari, application/vnd.apple.pkpassA signed JWT link
How it updatesYour web service plus a push over HTTPSClass or object update through the API
Message limitNot stated as a count3 push-triggering messages in 24 hours
Delivery promisePushes are not guaranteed to be deliveredThe user must have notifications enabled
Companion appPasses should not require oneLinks work on the web, in email and in SMS

What is a wallet loyalty pass?

Apple describes passes as a digital representation of information that might otherwise be printed on small pieces of paper or plastic, and says they can contain images and a barcode and be updated using push notifications. The technology has three parts: a package format, a web service API for updates, and an API for apps to read the pass library.

Which Apple pass type is a loyalty card?

The store card. Apple states that the storeCard key is appropriate for store loyalty cards, discount cards, points cards and gift cards. The other four styles are boarding passes, coupons, event tickets and generic passes, and Apple gives gym membership cards and metro passes carrying a balance as generic examples.

Does a customer need an app?

No. Apple states that users do not need to have your app installed to add your passes to Wallet, and adds that passes should not require a companion app. That is the platform’s own position, not a vendor’s marketing line, and it is the reason a wallet loyalty card can be joined at a counter in one tap.

How does a customer add a pass on an iPhone?

Through Mail or Safari. Apple states both have supported passes since iOS 6 and macOS v10.8.2, that on iOS they add passes to the pass library directly, and that on macOS they use iCloud to add them to the user’s iOS devices. Both expect the application/vnd.apple.pkpass MIME type.

How does a customer add a pass on Android?

Through an Add to Google Wallet link. Google states the link is a dynamically generated URL containing an encoded and signed JSON Web Token, in the form pay.google.com/gp/v/save followed by that token, and that it works anywhere hyperlinks work, including websites, email and SMS.

A signed JWT describing the pass. Google states that the safe length of an encoded JWT is 1800 characters, recommends presenting the link as an Add to Google Wallet button on surfaces that support hyperlinked images, and notes that saving can only be initiated in the context of a logged-in Google identity.

Does the customer have to approve the pass?

Yes. Apple states that adding passes to Wallet requires explicit permission and that the user must always see and approve the pass before it is added. There is no silent install path on either platform, which also means a pass cannot be pushed onto a phone that never asked for it.

How does a pass update after it is issued?

Apple describes a web service on the issuer’s server, reached over HTTPS, that devices register with after a pass is installed. When the pass changes, the server sends a push notification to the registered devices, and the device fetches the new version and compares it against the one it held.

Are wallet notifications guaranteed to arrive?

No, and this is the most useful sentence in either document. Apple states that push notifications are not guaranteed to be delivered and that multiple push notifications from the same source are coalesced into a single notification. Google states that users must have notifications enabled for their passes to receive them.

How many messages can a Google Wallet pass send?

Google states a maximum of 3 messages that trigger a push notification in a 24 hour period, and describes TEXT_AND_NOTIFY as the message type that adds a message to the pass details and triggers the notification. Update notifications on specific fields are subject to the same ceiling.

What is a change message on an Apple pass?

A per-field string shown when that field’s value changes. Apple states that if the value of a field has changed and the field specifies a change message, the device shows the message, and warns that change messages interrupt the user and are typically appropriate only for time-sensitive information.

What can never change on a pass?

Two things. Apple states that any field on a pass can be updated except for the authentication token and the serial number, and warns specifically against changing the authentication token in an update, because passes are not guaranteed to update and some devices may still hold the old token.

What identifies a pass uniquely?

Apple states that the combination of pass type identifier and serial number is used throughout PassKit to uniquely identify a pass, and that two passes of the same type with the same serial number are understood to be the same pass even if other information on them differs. The serial number is opaque to PassKit.

Which barcode formats can an Apple pass use?

Apple names PKBarcodeFormatQR, PKBarcodeFormatPDF417, PKBarcodeFormatAztec and PKBarcodeFormatCode128 as valid on iOS 9 and later, so none of them needs a fallback. It also notes that watchOS does not support Code128, and that a pass carrying only a Code128 barcode displays no barcode there at all.

How many fields fit on the front?

Apple states that a pass can generally have up to three header fields, a single primary field, up to four secondary fields and up to four auxiliary fields. Coupons, store cards and generic passes with a square barcode carry up to four secondary and auxiliary fields combined. The back of the pass can have as many fields as needed.

Which images does a store card use?

Apple lists logo, icon and strip for the store card style. The logo image sits in the top left corner beside the logo text with 160 by 50 points allotted, and Apple notes it should usually be narrower. The icon, shown on the lock screen and in Mail, measures 29 by 29 points.

Can one pass be shown in more than one language?

Yes. Apple states a pass can be localized in three ways: by displaying numbers and dates in the localized format, by providing localized strings, and by providing localized images. Each localization needs its own .lproj directory, and images that do not need localizing sit at the top level of the pass.

Can a loyalty pass appear near the shop?

Within limits Apple publishes. A pass can carry up to ten relevant locations, each with longitude, latitude and optional altitude, and up to ten unique beacon UUIDs. Apple also states that a store card does not support a relevant date, so a loyalty card cannot claim relevance by time the way an event ticket can.

What is a Google Wallet class and object?

Google states that passes issued to users are created by combining a passes class with a passes object. The class is the template that every holder of that pass shares; the object is one person’s card. Google offers a REST API and an Android SDK for issuing and managing both.

What does a business need before issuing passes?

Five things, four from Apple and one from Google.

  1. A pass type identifier that matches the signing certificate.
  2. A team identifier matching that certificate’s Team ID.
  3. A PKCS #7 signature including the WWDR intermediate certificate.
  4. An HTTPS web service, which Apple requires for all pass communication.
  5. A Google Wallet issuer account, and a signed JWT per save link.

Sources

Fideliya holds all five of those centrally, which is the practical difference between issuing passes and buying a platform that issues them: a business supplies a logo, a goal and a reward. The comparison with the app-based alternative is on loyalty app or wallet pass, the design choices sit on fifteen punch card ideas, and what to send once the card is live is on twenty loyalty campaign ideas.

Every answer above comes from one of seven primary pages, all fetched on 5 September 2026: Apple’s Wallet Developer Guide chapters on About Wallet, Pass Design and Creation, Distributing Passes and Updating a Pass, and Google’s Loyalty card overview, its Add to Google Wallet web guide and its Trigger Push Notifications guide. The source note above this article maps each question to the page it was answered from. No statistic, price or percentage appears on this page, and nothing here is inferred from a vendor’s marketing material.

Fideliya is wallet-native loyalty program software for small businesses. Customers add a stamp or points card to Apple Wallet or Google Wallet in one tap, with no app to download and no account to create. Fideliya runs stamps, points, gift cards and referrals on one platform in English, French, Spanish and Arabic with full right-to-left support, and the free plan issues a real wallet pass for up to 20 customers. The Apple side is described on Apple Wallet loyalty cards, and the plans are on the pricing page.

Frequently asked questions

What is a wallet loyalty pass?

Apple describes passes as a digital representation of information that might otherwise be printed on paper or plastic, containing images and a barcode and updatable by push notification. A Fideliya loyalty card is exactly that: a pass the customer keeps in Apple Wallet or Google Wallet and the business updates from its own server.

Which Apple pass type is a loyalty card?

The store card. Apple states that the storeCard style is appropriate for store loyalty cards, discount cards, points cards and gift cards. Fideliya issues its loyalty pass as an Apple storeCard, which is why the card sits in Wallet under the same style as a shop card rather than a ticket.

Does a customer need an app to use a wallet loyalty pass?

No. Apple states plainly that users do not need your app installed to add passes to Wallet, and that passes should not require a companion app. Fideliya is built on that: the customer adds the card to the wallet already on their phone and nothing is installed.

How does a customer add a pass on an iPhone?

Through Mail or Safari, which Apple says add passes to the pass library directly on iOS and expect the application/vnd.apple.pkpass MIME type. Fideliya serves its Apple pass with that MIME type from the join page, so the card opens and can be added without any intermediate step.

How does a customer add a pass on Android?

Through an Add to Google Wallet link, which Google describes as a dynamically generated URL containing an encoded and signed JSON Web Token. Fideliya builds that link at pay.google.com/gp/v/save for every customer, so the same join page works on Android and iPhone.

What is the Add to Google Wallet link?

A signed JWT in a URL. Google states the safe length of an encoded JWT is 1800 characters and that saving can only be initiated in the context of a logged-in Google identity. Fideliya signs that token server-side, so the customer only ever taps a button.

Does the customer have to approve adding a pass?

Yes. Apple requires explicit permission and states that the user must always see and approve the pass before it is added to Wallet. A Fideliya card therefore cannot appear in a wallet without the customer looking at it first and choosing to keep it.

How does a wallet pass update after it is issued?

Apple describes a web service on your server plus a push notification sent to the devices registered for that pass, over HTTPS. Fideliya runs that service, so a scan at the counter updates the stamp count on the card the customer is holding without anyone reopening anything.

Are wallet push notifications guaranteed to arrive?

No, and both platforms say so. Apple states that push notifications are not guaranteed to be delivered and that multiple pushes from the same source are coalesced. Google requires the user to have notifications enabled. Fideliya reports that Apple and Google accepted a broadcast, and never that a customer saw it.

How many messages can a Google Wallet pass send?

Google states a maximum of 3 messages that trigger a push notification in a 24 hour period. Fideliya sits well inside that: the plan allowance is one broadcast a month on Free, three on Pro and ten on Enterprise, counted per month rather than per day.

What is a change message on an Apple pass?

Apple states that if a field value changes and the field specifies a change message, the device shows it, and warns that change messages interrupt the user and are typically appropriate only for time-sensitive information. Fideliya follows that restraint rather than attaching a message to every field.

Can a pass serial number or authentication token change?

No. Apple states that any field on a pass can be updated except the authentication token and the serial number, and warns against changing the token because devices may still hold the old one. Fideliya keeps both fixed for the life of a customer’s card.

What identifies a wallet pass uniquely?

Apple states that the combination of pass type identifier and serial number uniquely identifies a pass, and that two passes of the same type with the same serial number are understood to be the same pass. Fideliya assigns one serial per enrolled customer, which is what lets a scan find the right card.

Which barcode formats can an Apple Wallet pass use?

Apple names QR, PDF417, Aztec and Code128 as valid on iOS 9 and later, and notes that watchOS does not support Code128. Fideliya uses PKBarcodeFormatQR, which is the format with the widest reader support and the one its own browser scanner reads.

How many fields fit on the front of a loyalty pass?

Apple states a pass can generally have up to three header fields, a single primary field, up to four secondary and up to four auxiliary fields, and that store cards with a square barcode carry up to four secondary and auxiliary fields combined. Fideliya designs its store card inside those limits.

Which images does a store card use?

Apple lists logo, icon and strip for the store card style, with the logo allotted 160 by 50 points and the icon 29 by 29. Fideliya maps a business logo and cover image onto exactly those slots, which is why a wide logo is cropped rather than shrunk.

Can one pass be shown in more than one language?

Yes. Apple describes localizing a pass through localized number and date formats, localized strings and localized images, each language in its own .lproj directory. Fideliya ships English, French, Spanish and Arabic, with right-to-left support, so the card reads correctly for the customer holding it.

Can a loyalty pass appear on the lock screen near a shop?

Apple states a pass can carry up to ten relevant locations and up to ten beacon UUIDs, and that a store card does not support a relevant date. Fideliya works within that: location relevance is available to a pass, and a date-based appearance is not something a store card can claim.

What is the difference between a Google Wallet class and an object?

Google states that passes are created by combining a passes class with a passes object: the class is the template shared by every holder and the object is one customer’s card. Fideliya creates one loyalty class per business pass and one loyalty object per enrolled customer.

What does a business need before it can issue passes?

Apple requires a pass type identifier matching the signing certificate, a team identifier, a PKCS #7 signature including the WWDR intermediate certificate, and an HTTPS web service. Google requires an issuer account and a signed JWT. Fideliya holds all of that centrally, so a business supplies a logo and a reward rather than certificates.

Ready to create your own loyalty pass?

Set up in under 5 minutes. No app for your customers to download.

Start free
Compare Fideliya with alternativesCalculate your ROI
Apple Wallet and Google Wallet loyalty passes: 20 questions — Fideliya Blog