Google is rolling out a feature that sounds almost embarrassingly basic — the ability to hide passes stored in Google Wallet. But for the millions of users who’ve accumulated boarding passes, loyalty cards, event tickets, and transit credentials in the app, this small addition addresses a surprisingly persistent irritation. And a genuine privacy gap.
The update, first spotted and reported by Android Police, introduces a “Hide pass” option accessible through the three-dot overflow menu on individual passes within Google Wallet. Once hidden, a pass disappears from the main view entirely. It doesn’t get deleted. It doesn’t lose functionality. It simply moves out of sight, retrievable through a dedicated “Hidden passes” section buried in the app’s settings.
Simple enough. So why does it matter?
The Clutter Problem Was Always a Privacy Problem
Google Wallet has evolved from a payments-only app into a digital credential hub. It stores government IDs in some states, corporate badges, vaccination records, hotel keys, concert tickets, insurance cards, and airline boarding passes. The sheer volume of items a single user might accumulate creates two distinct problems. First, finding the right pass at the right moment — standing at a TSA checkpoint, fumbling through a stack of expired boarding passes — is genuinely frustrating. Second, and more critically, anyone glancing at your phone while you pull up a pass can see everything else you’ve got stored.
That second problem is the one Google is now tackling. Consider the scenario: you open Wallet to tap your transit card on a bus, and the person standing behind you catches a glimpse of your medical insurance details, your employer’s corporate badge, or an event ticket that reveals where you’ll be this weekend. None of that information is protected by the phone’s lock screen once the app is open.
The hidden passes feature creates a layer of visual separation. It’s not encryption. It’s not biometric gating. But it’s a practical acknowledgment that not every credential in your wallet needs to be front and center every time you open the app.
According to Android Police’s reporting, the feature appears to be arriving via a server-side update, meaning users don’t necessarily need to download a new version of the app to access it. This is consistent with Google’s typical approach to Wallet feature rollouts — gradual, server-controlled, and sometimes maddeningly inconsistent in timing across devices and regions.
The mechanics are straightforward. Tap the three-dot menu on any pass. Select “Hide pass.” The pass vanishes from your main feed. To find it again, you go into Wallet settings and look for the hidden passes section, where you can unhide anything you’ve stashed away. There’s no password protecting the hidden section itself, which means this is more about convenience and casual privacy than serious security. A determined snoop with access to your unlocked phone could still find everything.
But that’s fine. That’s what biometric phone locks are for. What this feature does is prevent the incidental, over-the-shoulder exposure that happens dozens of times a day in public settings.
Google Wallet’s Broader Push to Become Your Everything Holder
This update doesn’t exist in a vacuum. Google has been aggressively expanding what Wallet can hold and do throughout 2024 and into 2025. Digital car keys. State-issued digital driver’s licenses, now available in a growing number of U.S. states. Corporate access badges through partnerships with companies like HID Global. Vaccine cards that stubbornly persist years after most venues stopped checking them.
Each addition increases the app’s utility. Each addition also increases the sensitivity of what’s stored inside. A wallet that holds only credit cards and a Starbucks loyalty pass doesn’t raise many eyebrows when opened in public. A wallet that holds your driver’s license, health insurance card, and office building access badge is a different proposition entirely.
Apple, for its part, has dealt with a similar challenge in Apple Wallet, though its approach has leaned more heavily on automatic organization and pass expiration. Apple Wallet automatically archives expired passes and uses on-device intelligence to surface the most relevant credential based on time and location — showing your boarding pass when you arrive at the airport, for instance. Google Wallet does some of this contextual surfacing too, but the hidden passes feature represents a more manual, user-driven approach to managing what’s visible.
The timing of this rollout is notable. Google I/O 2025 took place in May, and among the announcements were expanded Wallet capabilities including broader ID support and new transit integrations. The hidden passes feature wasn’t a headline announcement — it’s the kind of quality-of-life improvement that ships quietly weeks later. But it reflects a growing awareness inside Google that as Wallet becomes more central to daily life, the user experience around managing sensitive credentials needs to keep pace.
There’s also competitive pressure from fintech apps and specialized credential holders. Apps like Airside Digital Identity and various state-specific digital ID applications offer more granular privacy controls, including the ability to share only specific data fields from an ID rather than the entire document. Google Wallet isn’t there yet. But the hidden passes feature suggests the team is thinking about information exposure in ways it hasn’t before.
One limitation worth flagging: the feature doesn’t appear to support bulk actions. If you’ve got 30 expired boarding passes cluttering your Wallet — and many frequent travelers do — you’ll need to hide them one at a time. That’s tedious. A “hide all expired” option would be an obvious next step, but it’s not available in the current rollout.
And there’s still no way to organize passes into custom folders or categories, a feature users have requested for years. The hidden passes section is binary: visible or not. There’s no middle ground, no “show only when I’m at this location” granularity beyond what Google’s existing contextual suggestions provide.
What This Signals About Digital Wallet Design
The broader industry trend here is unmistakable. Digital wallets are no longer just payment tools. They’re becoming identity containers, and the design principles that govern them need to reflect that shift. A payment app can afford to be simple — show the cards, let the user tap. An identity container needs layers. It needs the ability to compartmentalize. It needs the digital equivalent of the physical wallet’s hidden pocket where you keep things you don’t want casually visible.
Google’s hidden passes feature is a first step in that direction. A modest one. But it signals that the company recognizes the problem, which is more than could be said six months ago.
For enterprise IT administrators who’ve deployed corporate badges through Google Wallet, this is a welcome development. Employees have been reluctant to store work credentials alongside personal items in an app that displays everything in a single scrollable list. The ability to hide personal passes — or work passes, depending on context — reduces that friction.
For everyday users, the value proposition is simpler. Less clutter. Less accidental exposure. More control over what you see and what others might see.
The feature is rolling out now, though as with most Google server-side updates, availability may vary. Check the three-dot menu on any pass in your Wallet. If you see “Hide pass,” you’re in. If not, patience. Google’s rollouts have their own timeline, and it rarely matches anyone’s expectations.
WebProNews is an iEntry Publication