Apple Wallet and Google Wallet Loyalty Pass Updates

Quick Summary: Google Wallet now requires creating a shared class and a customer-specific object, then issuing passes with signed JWTs. Apple Wallet's 2026 updates focus on clearer layouts, featured actions, and better team tools for designing and updating passes. Both updates aim to make loyalty passes more dynamic, scalable, and engaging for users.

Google Wallet Loyalty pass setup in 2026 still starts with a LoyaltyClass and LoyaltyObject, built in the Business Console or REST API, then issued with a signed JWT and Add to Google Wallet link. Apple Wallet Loyalty updates raise the bar too. These Loyalty Pass Updates matter if you need passes that scale, stay simple, and support future changes. We cover the real Google Wallet Loyalty flow and what these Loyalty Pass Updates mean next.

How to Create a Google Wallet Loyalty Pass

Google Wallet loyalty setup has three parts: create a class, create an object, then issue it with a signed JWT. Google’s flow says every pass needs both a shared class and a user-specific object in its loyalty pass guide.

1. Set Up the LoyaltyClass First
   Build the template for all customers. Add your brand name, program name, logo, colors, and shared rules. Use one class per loyalty program, not per customer.

2. Create the LoyaltyObject for Each Customer
   Make one object per member. Add a unique object ID, link it to the class ID, set state to active, and include account name, account ID, points, barcode, or linked offers as needed.

3. Issue the Pass with a Signed JWT
   Put the loyalty object in the JWT payload, then sign it with your authorized service account key. Google requires iss, aud, typ, iat, origins, and the loyalty payload for save flows in its JWT reference.

Also Read: Wallet Passes vs. Standalone Loyalty Apps: Which Is Better?

What Changed in 2026 for Loyalty Pass Design

2026 changed pass design in a practical way: both wallets now push clearer actions, cleaner layouts, and easier team workflows.

1. Why Featured Actions Matter for Loyalty Programs

Apple now supports Featured Actions on all pass styles, with up to two action tiles below the pass face, according to Apple’s 2026 Wallet update. That gives loyalty programs a better spot for offers, perks, or store links without stuffing the main card.

Keep only the top 1 to 2 actions. Too many choices hurt taps.

2. Why Pass Designer and Pass Builder Matter for Teams

Apple’s new Pass Designer and Pass Builder help teams preview, validate, and ship passes faster. This matters for multi-location brands that need cleaner handoffs between design, ops, and dev.

• Fewer layout guess checks
• Faster brand review
• Easier scale across locations

3. How Apple’s New Layout Direction Affects Loyalty UX

Apple’s Poster Generic style puts bold art first, while Google still gives teams strong row-based control through cardTemplateOverride customization. For operators, that means one clear rule:

• put points, tier, and barcode first
• move extras into actions or detail views

Also Read: Loyalty Reward Cards: How They Work and Why Your Business Needs One

How to Keep Loyalty Passes Updated at Scale

Use a simple rule: patch for small edits, update for full replacements. Google says update can clear fields you omit, so fetch the latest version first. Use patch for point balances, links, or labels. Use update only when you mean to replace the whole record, per Google’s update guidance.

Know the split between shared and personal data. A class change updates every pass tied to that template. An object change affects one customer only, as Google explains in its classes vs. objects overview.

Use updates to drive action, not just accuracy:

• Change points or tier at the object level
• Change branding or program text at the class level
• Batch low-risk edits on a schedule
• Reserve notifications for real value

Too many updates create noise. Send fewer, better pass changes.

Also Read: Loyalty Program Cards: The Complete Guide for Businesses

Why These Wallet Updates Matter to Businesses

Static loyalty cards are not enough now. Apple says loyalty passes can show real-time alerts for points, balances, and offers, while Google now supports field update notifications and added nearby geofence notifications in its Wallet release notes. That shifts passes from simple storage to an active retention channel.

For businesses, the win is scale. Google’s model separates a shared class from each user object in its pass creation flow, which makes bulk updates easier across many stores. > If you run multi-location loyalty, clean pass architecture matters as much as creative design.

Keep your loyalty passes easy to update and scale. Use OneCup to launch app-free Apple Wallet and Google Wallet rewards faster, with less setup friction.

Frequently Asked Questions

Q1: How can I create a scalable Google Wallet loyalty pass for my business?

Use one pass class, dynamic fields, clear reward rules, and automated updates. Plan for location groups, barcode fallback, and expiry logic early. Platforms like OneCup can simplify rollout across many stores.

Q2: What are the key design updates in Apple Wallet for loyalty passes in 2026?

Apple Wallet now rewards cleaner layouts, stronger branding, and more timely pass updates. Keep key value visible first, reduce clutter, and make lock screen relevance useful instead of noisy.

Q3: How do Featured Actions enhance user engagement on Google Wallet passes?

Featured Actions give users a clear next step, like checking points, redeeming rewards, or opening an offer. They work best when tied to intent, location, or recent activity, not generic clicks.

Conclusion

Apple and Google both raised the bar in 2026. Apple added richer pass design options and actions in Wallet according to Apple, while Google expanded loyalty updates and notifications in its release notes.