Google Wallet at I/O 2026 and Apple Wallet in iOS 27: Everything Announced and What It Means
Every Google Wallet feature announced at I/O 2026 (May 22), every iOS 27 Wallet rumor going into WWDC, and what each change means for the businesses that issue passes.
In eighteen days, Apple and Google both moved on Wallet. Bloomberg reported on May 4 that iOS 27 will add a consumer “Create a Pass” button to Apple Wallet. On May 22 at I/O 2026 Google previewed a Digital Receipts API, contactless loyalty enrollment, Auto-linked Passes, Live Updates for travel, Cross-device Payment Verification, an Android-wide Wallet redesign, and several smaller features. WWDC opens June 8 with the full iOS 27 preview.
Most press has covered each story in isolation. Read together they describe a category that’s getting more capable in both directions at once: for the consumer carrying passes and for the business issuing them. The middle of that sandwich, the signed, server-updatable, branded pass program, is unchanged. This is the practical run-down.
At a glance: every update in this cycle
Google Wallet, announced at I/O 2026 (May 22, 2026):
- Android Wallet app redesign. Two-per-row passes, full-screen live items, searchable “View more” hub. Shipping.
- Live Updates for tickets and flights on lock screen and always-on display. Shipping.
- Digital Receipts API. Retailers push receipts directly into Wallet. Preview, no partners or date.
- Contactless loyalty enrollment. Post-tap-to-pay prompt to join a retailer’s program. Rolling out.
- Auto-linked Passes. Boarding passes installed automatically post check-in. Launch partner: Azul Airlines.
- Inline frequent-flyer signup from a boarding pass. Announced, no date.
- Cross-device Payment Verification. NFC tap plus biometric, alternative to SMS OTP under EU/UK SCA. Announced, no date.
- Digital ID verification expanded to Uber and Intuit TurboTax. Shipping by partner.
- Nearby Passes via Google Maps. The 10-location geofence cap is removed.
- Chrome autofill expands to pull passport, driver’s license, loyalty cards and boarding passes out of Wallet for desktop and iOS forms.
Apple Wallet, iOS 27 (WWDC June 8, public release around September):
- Create a Pass. Consumer pass authoring from a QR scan or from scratch, three color templates (orange, blue, purple). Bloomberg, May 4. WWDC-pending.
- Apple Intelligence integration in Wallet, alongside Safari and Shortcuts. MacRumors code-leak rumor (Nicolás Álvarez), April 16. No specifics.
- Plausible continued expansion of the Verify with Wallet API (introduced iOS 16.5, then iOS 26 added web verification, then iOS 26.1 added US passport credentials).
- Already shipping on iOS 26 and unchanged: Add to Wallet API, Multi-Event Tickets, redesigned boarding-pass templates with Live Activities and AirTag tracking, Apple Intelligence order extraction from Mail.
The rest of this post takes those one at a time.
Google’s I/O 2026 Wallet batch, in detail
Wallet app redesign (shipping)
The Android Wallet homepage is restructured around time-sensitivity. Boarding passes and live items render full-screen. Other passes lay out two-per-row, with the option to pin or drag-reorder which ones live on the home view. A searchable “View more” hub holds everything else and exposes transaction details.
For issuers the layout itself doesn’t change the pass payload. What does change is the position of a static loyalty card. It now sits behind the live items in the Wallet UI. Passes that update, push, or surface contextually are the ones that win the home screen.
Live Updates for tickets and flights (shipping)
Time-sensitive events and flights can post Live Updates that surface on the lock screen and always-on display, in addition to standard Wallet field updates. Apple shipped a comparable Wallet-native mechanism for boarding passes in iOS 26 (September 2025), with United, Delta, and Southwest as launch carriers. This is genuine feature parity.
Digital Receipts API (preview)
The most consequential developer-side announcement: a dedicated API for retailers to push receipts directly into Wallet at checkout. Launch partners and ship date weren’t disclosed.
The receipt is a wedge. Once it’s in Wallet, attaching a return barcode, a points-earned line, or a follow-up coupon is a smaller step. POS vendors and payment processors will likely intermediate. Small retailers will get this through Square, Toast, Lightspeed and similar before building to it directly.
Contactless loyalty enrollment (rolling out)
After a tap-to-pay transaction at a participating retailer, the user gets a notification inviting them to join that retailer’s loyalty program if they haven’t already. Accepting creates the Wallet pass.
The front door changed. The program didn’t. The loyalty card, the points logic, the tier rules, the redemption flow, the design of the pass are all still owned by the retailer. What changed is the acquisition funnel: a customer who would never have signed up at the counter now might.
Auto-linked Passes: automatic boarding pass syncing (shipping)
After airline check-in (online, mobile, or at the airport), the boarding pass is pushed into Wallet automatically. No “Add to Google Wallet” button to find. Google’s reference launch partner is Azul Airlines (Brazil), with broader rollout to follow.
The pattern matters more than the feature: operator-issues, then platform-auto-installs. If it works for airlines, ticketing and event partners are the next plausible candidates.
Inline frequent-flyer signup from a boarding pass (announced)
When a boarding pass lands in Wallet, the user will see a prompt to join the airline’s frequent flyer program. Airline-first, no ship date.
Cross-device Payment Verification (announced)
Buying on a desktop browser? Tap your Android phone to the laptop via NFC and confirm with face, fingerprint, or PIN. Google positions it as an alternative to SMS OTPs for EU/UK Strong Customer Authentication. Launch date not specified.
This is a payment-processor-level change. For non-payment issuers (loyalty, ticketing, IDs) the direct effect is zero. For businesses taking card-not-present payments through Google Pay, conversion lifts are plausible once it ships broadly.
Digital ID verification expansion (partial)
Google Wallet’s digital ID verification lets a user selectively share attributes from a digital ID without handing over the whole document. It extended to Uber and Intuit TurboTax. Rollout is partner-by-partner. The mDL credentials are state-issued in the US, so geographic reach is gated on DMV cooperation.
Nearby Passes via Maps, plus Chrome autofill expansion
Two smaller things. Nearby Passes now uses Google Maps for store identification, removing the historical 10-location cap on per-pass geofences. Store networks that previously truncated to 10 can now expose all of them. Separately, Chrome autofill can now pull out of Wallet (passport, driver’s license, booking confirmations, loyalty cards, boarding passes) to fill forms on desktop and iOS.
Apple’s iOS 27 Wallet: Create a Pass and the rumors around it
Apple’s June 8 keynote will preview iOS 27. The headline Wallet item Bloomberg has reported is Create a Pass.
Create a Pass: what Bloomberg has confirmed
A new ”+” entry in the Wallet app (the same menu where credit cards get added) lets the user create a pass by hand. Two flows: scan a QR code from any existing pass or ticket and let Wallet build a pass around it, or build from scratch with the camera and a template.
Customization covers images, colors, style, and text fields. Three color-coded templates: orange (Standard / other), blue (Membership), purple (Event). Bloomberg’s framing: this addresses venues that hand out QR codes (gyms, concerts, small businesses) without offering a native Wallet pass.
WWDC will likely fill in detail. The current reporting confirms the consumer flow and the templates. It does not describe signing, server updates, push notifications, branded design at scale, or any developer-facing API. That absence is the story for issuers.
What Create a Pass actually does
It is the largest expansion of who can put a pass in Apple Wallet since Wallet shipped. Until now every Apple Wallet pass came from a signed certificate held by an issuer (directly or via a vendor). After iOS 27, the consumer can issue to themselves.
A user-created pass is a fundamentally different object from an issuer pass:
| Capability | Issuer pass (.pkpass signed) | Create a Pass (consumer) |
|---|---|---|
| Updates after install (server push) | Yes, APNs to every device with the pass | No |
| Brand design at scale (logo, strip, color, fields) | Full | User picks from templates |
| Bulk issuance (10,000 cards in one job) | Yes | No, one device, one pass |
| Cross-device parity (issued once, on every iPhone) | Yes | No, lives on the device that created it |
| Server-side state (points, balance, expiry, tier) | Yes | No |
| APNs lock-screen notification when balance changes | Yes | No |
| Geofenced lock-screen surfacing on visit | Yes (issuer controls) | Limited (only what the user typed in) |
| Analytics, revocation, trusted certificate | Yes | No |
A branded membership card that updates when a member upgrades, a stamp card that pushes a banner when a stamp lands, a season ticket whose seat changes when the team moves the user: all untouched by Create a Pass. iOS 27 grew the floor of what end users can do without lowering the ceiling of what a business pass program needs.
A fairer framing than “Apple killed the pass-API category”: Apple is educating the market about wallet passes at scale, and for free. Every consumer who hand-makes a pass for their gym is one consumer more likely to expect their real loyalty card to push a notification when their points change.
The rest of the iOS 27 Wallet rumor pile
Beyond Create a Pass, only one other Wallet item is in the rumor pile, and it’s weaker.
Apple Intelligence inside Wallet. A code leak surfaced by MacRumors on April 16, based on backend code found by developer Nicolás Álvarez: Wallet is one of the apps getting deeper Apple Intelligence integration in iOS 27, alongside Safari and Shortcuts. No specifics on the surface. Plausibly an extension of the iOS 26 Apple Intelligence work that already auto-extracts order tracking from Mail.
Plausible but unleaked: continued expansion of the Verify with Wallet API (introduced iOS 16.5 for US state IDs, web verification added in iOS 26, US passport credentials added in iOS 26.1). This is Apple’s counterpart to Google’s Uber and TurboTax expansion.
PassKit changes have accelerated rather than slowed. iOS 26 (September 2025) was the largest PassKit wave since the early Wallet years: Add to Wallet API, Multi-Event Tickets, redesigned boarding-pass templates with Live Activities and AirTag tracking, Verify with Wallet, Apple Intelligence order extraction. iOS 27 will land on top of that.
Side by side: iOS 27 Wallet (rumored) vs Google Wallet I/O 2026 (shipped / announced)
| Wallet area | iOS 27 (rumored / leaked) | Google Wallet I/O 2026 |
|---|---|---|
| Pass authoring | Create a Pass. Consumer, QR-scan or scratch-built (Bloomberg, May 4) | None new. User-add-from-photo predates this cycle |
| AI inside Wallet | Apple Intelligence integration (code leak, no specifics) | None. Gemini features inside Wallet UI were not announced at I/O |
| Receipts | No rumored Apple effort | Digital Receipts API (preview) |
| Loyalty acquisition | No rumored Apple effort | Contactless loyalty enrollment post-tap |
| Boarding passes | Wallet-native Live Activities already shipped in iOS 26 | Auto-linked Passes (Azul launch partner), inline FF signup |
| Live updates | Already in iOS 26 (boarding passes) | Live Updates for flights and tickets |
| Identity / verification | Verify with Wallet expansion plausible | Digital ID expanded to Uber, Intuit TurboTax |
| Geofencing | No change | 10-location cap removed via Maps |
| Wallet app UI | No iOS 27 Wallet-UI redesign rumored | Android Wallet redesign |
| Cross-platform payment auth | Tap-to-Pay-on-iPhone iteration plausible | Cross-device Payment Verification |
| Issuer-side APIs | iOS 26’s Add to Wallet API and Multi-Event Tickets still the latest | New API surface across receipts, loyalty, auto-link |
The honest read: in this cycle Google is building commercial pipes (push a receipt, install a loyalty card, auto-install a boarding pass). Apple is mostly investing in the consumer-side authoring surface plus a possible AI hook. They aren’t doing the same kind of work this round.
How this lands for different kinds of business
The practical impact splits by business type. The cohorts below are the ones we see most often at WalletWallet. The named examples are illustrative shapes.
Multi-location retailer with its own loyalty program
What lands hardest: contactless loyalty enrollment is the highest-leverage feature in the batch. A one-screen prompt at the moment of payment beats every other acquisition channel a retailer has. It requires a live Google Wallet loyalty class. The Digital Receipts API is the longer game on the same surface. Create a Pass raises the visual bar your own pass is measured against. Strip image, brand color, server-updating fields, and lock-screen notifications when balances change become the differentiators against any self-made card. Our own pass-shape data backs the design point: across the passes generated through WalletWallet in the last 30 days, 33% carry a custom brand color and around 1.2 secondary fields on average. The field is settling on simple, branded designs, and live behavior is what distinguishes a real loyalty pass from a placeholder.
What to do now: if you don’t issue native Google Wallet loyalty (only .pkpass), the cost of not doing so just rose. Audit your Apple Wallet design against what a hand-built pass will look like in September.
Membership or discount-card operator (where the card scheme is the product)
What lands hardest: Create a Pass has the longest tail here. The wallet card is the product. The differentiator post-September is the live behavior of an issued pass: updates when a member’s status changes, surfaces on the lock screen near partner venues, redesigns when you refresh the program. Verify with Wallet (Apple) and Google’s Digital ID expansion are the longer-term shape change for any scheme that grants access to physical or digital benefits. Geofence cap removal (Google) is operationally useful for any scheme with more than 10 partner venues.
What to do now: lean on the differences between an issued pass and a hand-made one in customer-facing language. Members are about to learn what a wallet pass is. They should learn it from your card.
Single-site venue, gym, or hospitality business
What lands hardest: contactless loyalty enrollment is the obvious win for any venue that does tap-to-pay and runs even a basic membership or stamp scheme. Create a Pass is the trap. If your gym hands out a QR code but doesn’t issue a real wallet pass, members will make their own, and that copy won’t update when class times change. Live Updates are useful for anything time-bound (a class moving, a venue closing early, a season-ticket schedule change).
What to do now: if you’re not issuing wallet membership passes, the cost of not doing so just went up. The free version a member makes themselves will be wrong by next week.
Event and live-marketing agency
What lands hardest: Live Updates for tickets is the pro-grade ticketing experience that PDFs and basic passes can’t match. A wallet ticket whose seat updates and whose lock screen surfaces a “doors at 7pm” reminder is operationally distinct. Create a Pass raises the floor for low-budget organizers, which makes a polished agency-produced VIP, sponsor, or speaker credential more distinguishable from the DIY alternative. Auto-linked Passes is the pattern to watch. When post-purchase auto-install extends from airlines to ticketing, agencies issuing through APIs that map cleanly to Google’s class model will inherit it without code changes.
What to do now: if “digital event ticketing” is on your service catalog, the wallet-pass version is now the credible premium option.
Web or dev agency adding wallet passes to client stacks
What lands hardest: the May 2026 cycle made wallet passes more visible to your clients. “Can we add an Apple Wallet pass to the checkout?” becomes a normal client question, which means a pre-built wallet-pass module is a small, repeatable line item. Create a Pass does the educational work that used to be your job. Clients will arrive understanding what a pass is and why a self-made one isn’t a loyalty program. Digital Receipts API is worth tracking for an upsell on top of any e-commerce build.
What to do now: pick one client to ship a real wallet program for during the WWDC content cycle. Use the traffic to publish the case study.
Indie dev or small SaaS adding wallet as a feature
What lands hardest: market signal. Two major platforms moved on Wallet in the same month. Wallet passes have moved from a niche side feature to a serious distribution surface for any product that benefits from a phone-resident credential. Create a Pass removes a chunk of explanation from your onboarding. iOS 26’s Add to Wallet API is the developer-side primitive that pairs naturally with a one-API-call provider.
What to do now: the window where adding wallet passes is novel but not saturated is open. Ship a minimum version this quarter and iterate after WWDC.
What stays true regardless of cohort
The pass your business issues remains the source of truth. A self-created pass (Apple Create a Pass) or a user-added-from-photo pass (Google) is a personal shortcut. It doesn’t get updates from the operator. If your cafe replaces its stamp card, a hand-made copy will be wrong the next day. Both platforms made the surrounding context (receipts, enrollment, lock-screen presence) richer. The center, which is the signed, server-updatable, branded program, is unchanged and more valuable than it was six weeks ago.
How WalletWallet fits
Disclosure, since this is our blog. WalletWallet is a one-call API for issuing and updating Apple Wallet passes. We sign with our certificate (no Apple Developer account required). POST /api/pkpass returns a signed .pkpass. PUT /api/pkpass/{serial} updates installed passes and fans out APNs push to every device that holds one. Native Google Wallet lifecycle (the API surface Google grew on May 22) is on our roadmap. Today a .pkpass opens on Android via Google’s import path.
iOS 27 Create a Pass is consumer flow. It doesn’t collide with .pkpass issuance from a backend. Google’s I/O batch raises the value of native Google Wallet for issuers and is a fair input into our roadmap. What changed for us, and for every issuer-side pass vendor, is the surrounding story. The case for a real branded pass program is sharper than it was six weeks ago.
Dates to remember
- May 4, 2026. Bloomberg breaks iOS 27 Create a Pass.
- May 22, 2026. Google I/O Wallet session.
- June 8, 2026, 10am PT. WWDC keynote, iOS 27 preview.
- June 8, 2026, 1pm PT. Platforms State of the Union. “What’s new in Wallet” follows during the week.
- September 2026 (est.). iOS 27 public release.
This article will be updated after WWDC with whatever Apple confirms.
Image and source credits: Google Wallet press images via Android Authority, 9to5Google, and Android Police. Apple Wallet reporting from Bloomberg, MacRumors, and CNET (Getty Images).
Build your first wallet pass
Generate a signed .pkpass from JSON, test it in Apple Wallet, and keep the integration simple.