Mobile Wallet Loyalty: Apple Wallet, Google Wallet, and the Cardless Future

Mobile wallet loyalty puts a member's loyalty card in Apple Wallet or Google Wallet as a digital pass that shows their balance and status, can be scanned or tapped at checkout, updates when their account changes and can appear on the lock screen near a store, without the member installing a separate app.

A physical card or a portal login keeps the program out of sight between purchases. A wallet pass sits where many members already keep payment cards and tickets. It does not replace a loyalty app, which can do far more, but it gives members who will never download an app a visible, current card. This guide explains how wallet passes work, how Apple and Google differ, what updates and notifications can and cannot do, how passes connect to a loyalty platform, and how to design, distribute and measure them.

Key Takeaways

What is a wallet pass and how does it work?

A wallet pass is a structured, signed data file that Apple Wallet or Google Wallet displays as a branded card and updates when the issuer's system sends new data.

Each pass combines fixed design elements (logo, colors, program name) with member-specific data (name, member ID, balance, tier, a barcode or QR code). The member never sees the file, only the card. When the loyalty platform records a change, such as points earned or a new tier, the pass management system updates the pass and the member sees the new values the next time they look.

The two platforms build passes differently:

• Apple Wallet. Passes are created with Apple's Wallet pass format and must be signed with credentials from Apple's developer program. When a member's data changes, the issuer's server sends a push notification to the device, and the device then requests the updated pass from the issuer's web service.
• Google Wallet. Passes are created through the Google Wallet API using a Class, the template shared by all members of a program, and an Object, the individual member's pass. Updating a member's Object updates their pass without reissuing it.

Loyalty teams can build this in-house or use a pass management platform. Pass management platforms handle certificates, API authentication, templates, issuing and updates, and connect to the loyalty platform through an API or webhooks. The loyalty platform buyer's guide covers how to evaluate the platforms that sit underneath.

How do Apple Wallet and Google Wallet differ for loyalty?

Apple and Google support the same basic loyalty card, but they differ in how updates notify members, how location features work and what NFC requires.

Sources: Apple, Showing a Pass on the Lock Screen; Apple, PassFieldContent; Apple, Loyalty Passes; Google, Trigger Push Notifications (loyalty cards); Google Wallet release notes; Google, Smart Tap.

What can wallet notifications do, and what are the limits?

Wallet notifications can confirm points, tier changes and important updates, and both platforms allow some promotional messages, but each platform limits how and how often they are sent.

On Apple Wallet, an update produces an alert only for fields configured with a change message, and Apple's loyalty pass page describes notifying customers "in thoughtful ways". On Google Wallet, a field update triggers a notification only for supported fields: the points balance on the member's pass, and the tier and program name set for the whole program. A message sent with the TEXT_AND_NOTIFY type also triggers a notification. Google allows a maximum of 3 notifying updates in a 24-hour period, applies the same limit of 3 to notifying messages, and may throttle delivery if it judges that an issuer is spamming users. Members can also turn notifications off.

Apple's loyalty page presents notifications as a way to tell customers about products and services and to broadcast program updates, but the platform limits, and the fact that members must keep notifications on to receive them, make wallet alerts better suited to service messages than to routine campaigns.

Good uses:

• Earn confirmation after a qualifying purchase, showing the new balance.
• Tier changes, with the new benefits.
• Reward expiry reminders a short time before an earned reward lapses.
• Time-limited offers that are relevant to the member, used sparingly.

Poor uses are weekly balance summaries, generic promotions and messages that make the member open the pass to find out what changed. Because members can switch off notifications or remove the pass, over-use can cost the program the channel. Coordinate wallet alerts with email, text and app messages so members are not told the same thing three times; the guide to Next Best Action covers choosing channel and timing per member.

How do location features work?

Both platforms can bring a pass forward near a store, but Apple shows the pass on the lock screen while Google sends a notification it controls, and neither lets a brand cover every store at once.

• Apple Wallet shows a pass on the lock screen when it is relevant. Apple's documentation describes relevant dates for boarding passes, event tickets and generic passes, so loyalty passes rely mainly on locations and beacons. A pass can list only 10 relevant locations, each with optional text such as "Store nearby on 3rd and Main", and up to 10 iBeacon UUIDs for in-store Bluetooth beacons. Apple's guidance is to start with the best locations and update the pass to change them.
• Google Wallet can add up to 10 merchant locations per class and 10 per object. Google decides how close a member needs to be and how long they stay before sending a notification, and Google writes the text. Members must have Wallet notifications on and must have given Google Wallet precise, always-on location access.

For chains with many stores, set each member's locations from their purchase history, such as their most visited stores (on Google, on the member's Object, since Class locations apply to everyone), update them when their pattern changes, and say in the privacy notice that purchase history is used this way. As an illustration, a regional grocery chain with 60 stores cannot list every store on a member's pass, so it fills the pass with that member's most visited stores and the nearest alternatives, up to each platform's limit, and refreshes the list monthly from transaction data. Keep location features to the brand's own stores and events.

How do wallet passes connect to a loyalty platform?

The loyalty platform stays the system of record, and it must send member events to the pass management layer so each pass stays current.

The loyalty platform needs to expose, by API or webhook: enrollments (to issue a pass), balance changes, tier changes, reward expiry and offer changes. The pass management platform turns each event into a pass update and, where allowed, a notification. Check that the loyalty platform's APIs can send these events in near real time, and decide which system owns notification rules so the two do not both send messages.

On Google Wallet, only a balance change on the member's pass triggers a field-update notification; tier, expiry and offer alerts for an individual member are sent as TEXT_AND_NOTIFY messages, within the same limit of 3 in 24 hours. On Apple Wallet, each alert needs a change message on the updated field.

BLOYL™, Brandmovers' loyalty platform, provides the system-of-record side of this: a dynamic rules engine for earning and redemption, real-time dashboards and bidirectional CRM and CDP data flows. A pass management provider would need to receive those member events, so confirm how the two systems connect before building.

How should wallet passes be designed?

Put the member's most useful current information on the front of the pass, translate balances into value, and keep one field for offers that actually change.

• Primary field: the number the member needs now, such as "2,340 points: $23 off available", rather than a member number or join date.
• Secondary fields: tier, expiry date or next reward.
• Offer field: a message that changes when there is something new; a field that never changes stops being read.
• Back of the pass: program terms, customer service contact and a link to the account.
• Barcode or NFC: barcodes and QR codes work with standard scanners; NFC needs the certified terminals and software described above, so programs without that setup can start with barcodes.
• Fallbacks: members whose phones support neither wallet, or who switch phones, still need a way to identify themselves at checkout, such as a phone number lookup, and a link on the account page to add the pass again. A static barcode can be screenshotted and shared, so decide whether redemptions need an extra identity check.

How do members get wallet passes?

Offer the pass at moments when intent is highest: right after enrollment, at checkout and in existing member communications.

• Enrollment confirmation page and email, with an "Add to Apple Wallet" or "Add to Google Wallet" button.
• Text message link, only to members who have consented to texts; under FCC rules, marketing texts sent with automated technology generally require the recipient's prior express written consent.
• QR codes at the register, on receipts or on packaging.
• The program website and account page, and on Google, the wallet.google.com homepage, where loyalty passes can be added from the web.
• Gmail auto-add on Google, for members who have Gmail's Smart features control on.
• Post-tap enrollment on Google, where merchants integrated with Smart Tap can request to join the Bounceback pilot, which prompts members who tap to pay to sign up.
• The brand's app, App Clips and NFC tags on Apple, which Apple lists alongside SMS, email and QR codes.

Follow Apple's and Google's badge guidelines for the add-to-wallet buttons.

How do you measure a wallet pass program?

Measure wallet passes as a channel: how many members add and keep them, and whether pass holders behave differently from comparable members without one.

• Pass adds as a share of members offered the pass, by distribution method.
• Active passes and removals over time.
• Pass removals after each type of alert, where the platform reports them; Google, for example, offers callbacks for saves and deletions on a best-effort basis.
• Redemptions and scans by pass versus other methods.
• Visit frequency and spend of pass holders against comparable members without a pass. Members who add a pass are often more engaged to begin with, so compare against a holdout or a matched group rather than all other members.

What privacy rules apply?

Get consent for each channel used to deliver or promote passes, keep location use to what members expect, and explain in the privacy notice how pass data is used.

On Google, nearby notifications depend on the member granting location access to Google Wallet, and Google controls the timing and text. On Apple, relevance for a loyalty pass is set mainly by the locations and beacons listed in the pass. Keep location features to the brand's own stores, describe pass features in the program terms and privacy notice, and follow text-message consent rules when sending pass links by SMS. Programs for age-restricted products, such as alcohol, tobacco or lottery, should review Apple's and Google's pass content policies and apply the same age checks to pass distribution as to the rest of the program. On Google, links in pass messages must relate to the pass; Google states that linking elsewhere violates its Acceptable Use Policy. This is general information, not legal advice.

Conclusion

A wallet pass gives a loyalty program a visible, current card in a place many members already use every day, without asking them to download an app. The limits matter as much as the features: Google caps notifying updates and controls nearby notifications, Apple shows passes by relevance and alerts only on configured field changes, and NFC needs certified hardware and software. Treat the pass as a channel on top of the loyalty platform, connect it to member events, design it around the member's current value, offer it at high-intent moments and measure pass holders against comparable members. The guide to Millennial and Gen Z loyalty covers designing for younger, mobile-first members.

Sources

• Apple Developer, "Showing a Pass on the Lock Screen"
• Apple Developer, PassFieldContent (changeMessage)
• Apple Developer, Loyalty Passes
• Google for Developers, "Trigger Push Notifications" (loyalty cards)
• Google for Developers, Wallet release notes
• Google for Developers, Smart Tap
• Google for Developers, "Use callbacks for saves and deletions"
• Apple Developer, "Adding a Web Service to Update Passes"
• FCC, "Stop Unwanted Robocalls and Texts"