A digital wallet is no longer a place where digital assets sit still. It is the surface where the customer relationship keeps running. Everyone who issues a ticket, a loyalty card, a gift card, or an ID now operates a channel — the active pass — and inherits the one problem the platforms have not solved.
The Active Pass Makes the Digital Wallet a Customer Channel Beyond the Checkout
The digital wallet has changed jobs: it has become an interface, the screen where the customer relationship keeps running long after the thing in it was issued. For a decade it was the opposite. The wallet used to be a container, a place where cards, tickets, and coupons sat still until a terminal asked for them.
This summer the wallet has become more than accept Apple Pay and Google Pay at checkout. What looked like routine product news from three of the biggest players made the old definition of “digital wallet integration” obsolete.
At I/O in May, Google shipped a top-to-bottom Wallet redesign: a dynamic home screen that surfaces time-sensitive passes, Live Updates that push flight and event changes to the lock screen, and an announced Digital Receipts API.
At WWDC on June 8, Apple unveiled iOS 27’s Featured Actions — interactive tiles that turn a pass into a row of buttons — alongside a full pass-production toolchain: a Pass Designer app for the Mac and a server-side Swift framework for building and signing passes at scale.
And on June 25, Ticketmaster announced customizable Google Wallet tickets: rich hero branding and up to twelve configurable, reorderable action links per ticket, managed from its TM1 platform. Ticketmaster says it is the first ticketing partner to offer the capability.
All of these announcements go beyond the wallet as payment or store of tickets.
The digital wallet as a container era ended because it succeeded
Digital wallets carried 56% of global e-commerce transaction value and 33% of in-store value in 2025, per Worldpay’s Global Payments Report, a flow the prior edition measured at $15.6 trillion in consumer spend in 2024 alone. Juniper Research counts 4.4 billion wallet users in 2025, headed past 6 billion by 2030; that’s more than 3/4 of humanity.
When a technology reaches three-quarters of humanity, the adoption question is settled. So we can turn to the next one: what else would people want a digital wallet to do?
The truth the payments framing hides is that almost everything else in the wallet is dead weight. Roughly half of the 17.9 loyalty memberships the average American holds sit inactive, per Bond’s 2023 Loyalty Report; U.S. adults hold about $27 billion in unused gift cards and store credit, per Bankrate’s 2024 survey; and a ticket’s usefulness expires at the venue door. A credential’s commercial life has historically ended at issuance. The brand pays to get the pass into the wallet, then the relationship goes dark, and re-engagement gets outsourced to email and push, channels customers have trained themselves to ignore.
A pass is no longer a file to save to the wallet. It is a surface in the wallet.
Let’s look closely at what Ticketmaster shipped. The ticket still proves entry. That’s the job it was built for. But before the event it can surface parking, transit options, and gate details… During the event, express-entry lanes, seat upgrades, in-seat food ordering, and merchandise… Afterward, links into the venue or artist app. The ticket became the event’s remote control and with that a companion across the fan’s whole event journey.
Apple is generalizing the same pattern from the platform side: Featured Actions put interactive tiles on passes, and the new Poster Generic template extends that treatment to loyalty, rewards, membership, and gift cards — the cinematic format tickets got — while hotel keys will carry trip details and in-stay services, not just a door credential. Google, meanwhile, has spent two years wiring passes into its distribution machine: auto-linked passes that attach a parking pass to your event ticket, Nearby Passes notifications that surface the right card by location — now inferred automatically from Google Maps data — and, since October 2025, automatic import of loyalty cards, boarding passes, and event tickets straight from Gmail.
If we read that distribution list from the issuer’s chair it turns out that how a pass gets into the wallet is no longer your decision. Between Gmail auto-add, Google’s AI-powered “everything else” pass scanner, and Apple’s new Create a Pass camera import, your credential is going into the wallet whether you put it there or not. Customers can now digitize any card, ticket, or voucher you issue — and if they do it themselves, the result is an unbranded, unmanaged artifact you don’t control and can’t update. When issuance gets cheap and ingestion gets automatic, having a pass stops being a differentiator. Operating one becomes the business.
A wallet pass is persistent, branded real estate on the most-opened screen the customer owns. It is your channel with a lifecycle, an owner, and a P&L.
That is the strategic reframe: a wallet pass is no longer a credential with a barcode. It is persistent, branded real estate on the most-opened screen the customer owns — a channel with a lifecycle, an owner, and a P&L. Industry analysis extended the logic within days: if an event ticket can become a customer interface, what stops loyalty cards, memberships, insurance documents, or stored value from following? Nothing. The mechanics are general; only the imagination has been sector-specific.
The market has named the pieces of this shift but not the thing itself. The martech stack calls its tooling “mobile wallet marketing” and has pitched the wallet as a channel for years. Analysts call the transaction side ambient commerce. Neither names what issuers now own. So name it after what changed: the passive wallet is giving way to the active pass — a credential that acts, verifies, and carries the customer relationship after issuance instead of ending there. The rest of this piece is about what it takes to operate one, and the one thing that makes an active pass safe to run.
A pass in your wallet that can act is useful. A pass that can verify is powerful.
The second shift gives the first one teeth. In November 2025, Apple launched Digital ID, a passport-derived credential accepted, in beta, at TSA checkpoints in more than 250 U.S. airports — and by May 2026 extended it beyond travel, starting with age verification across Apple’s own services. State IDs now sit in both wallets — 14 states plus Puerto Rico on Apple’s side, ten and counting on Google’s — and in Europe, eIDAS 2.0 requires every member state to offer a certified digital identity wallet by the end of 2026, with private-sector acceptance obligations following in 2027. Regulation is pulling from the demand side too: the UK’s Online Safety Act made age checks mandatory for adult-content services, and Google answered with zero-knowledge-proof age verification built into Wallet, proving “over 18” without revealing name, address, or birth date.
For anyone who issues credentials, the implication is direct: the wallet is becoming the default place where “prove it” happens, whether that is age at the self-checkout, membership at the gym door, or entitlement at the event gate. Identity upgrades the pass from marketing surface to trust surface.
And that trust surface just opened to everyone
One structural fact completes the picture: the wallet is no longer the duopoly’s private surface. Pushed by EU regulators, Apple opened iPhone NFC to rival wallets in Europe — Norway’s Vipps, then PayPal in Germany and Curve across the EEA, became the first true tap-to-pay alternatives on iPhone. National account-to-account rails are arriving on the same surface — Brazil’s Pix, at more than six billion transactions a month, now taps to pay inside Google Wallet. Even Visa and Mastercard are building rails for software agents to transact under mandate. While adoption there is jagged, the direction is set — and what happens when checkout itself disappears is its own story.
The consequence is not a payments story. It is a population story: banks, merchants, and fintechs can now build wallet experiences that were architecturally impossible three years ago; and every issuer who does inherits the same unsolved question.
Every action link raises the same question
An action link is a URL. A pass that can order food to your seat, upgrade your ticket, open your hotel room, or release stored value is only as trustworthy as the answer to one question: is the right person actually there? The more capable the pass, the more valuable the fraud.
So before wiring high-value actions to a pass, an issuer needs a presence check that holds up. We’ve argued the infrastructure-level version of this diligence elsewhere; at the turnstile, those questions become five requirements:
- Judge it as a measurement, not a metaphor: how often does it accept someone standing outside the space where the action is valid? An answer with an error radius is an answer that fails at a turnstile.
- It runs on hardware already deployed at the touchpoint, because capital cost is what keeps most venues, stores, and transit systems from instrumenting the moments that matter.
- Alive offline. It works at the moment of validation even when connectivity doesn’t — at the gate, in the basement venue, on the bus.
- Dead on replay. A recording, screenshot, or forward of the credential proves nothing.
- Invisible at throughput. It clears a walking crowd without adding an aim-and-scan step at every moment of value — a check that adds friction taxes exactly the experience the interface era is selling.
Now score the stack honestly. Static QR fails on replay: copied with a screenshot, spoofed with a sticker. Rotating barcodes — the ticketing industry’s real incumbent, and a genuinely good answer to replay — keep the optical ritual: aim, brightness, handoff at the gate; they fail on throughput. GPS fails on boundedness and offline: coarse, slow indoors, fakeable. Bluetooth fails on boundedness: it bleeds through walls, which is why it never became a payment-grade presence signal. Ultra-wideband is precise and hard to spoof, but fails brownfield: it needs chip coverage across the crowd and certified anchors at every touchpoint. NFC is excellent at four centimeters and fails brownfield everywhere else: certified hardware at every touchpoint is the exact bottleneck that keeps passes passive at every moment that isn’t a register.
One requirement sits above the other five: consent. The wallet is the one channel the customer explicitly chose to install and open, and presence must keep that property — sensed only when the customer’s own app invites it, never harvested in the background. A presence layer that customers didn’t opt into is surveillance, and surveillance is how issuers lose the surface they just won.
Run the scorecard and the gap is visible: nothing in the stack clears all five at once. That column is empty.
Where we sit
That empty column is the layer LISNR works on. Picture one fan at one gate. Hands-free entry is a switch she flipped when she added the ticket to her wallet. As she reaches the turnstile, her phone and the validator exchange an encrypted ultrasonic tone over the speakers and microphones that phones and payment terminals already carry. Sound stops at the walls of the room; each tone is unique and expires in seconds, so a recording proves nothing; none of it needs a connection. She never breaks stride and the pass that proved her entry is the same surface that offers the seat upgrade once she is inside. The catch: the check runs inside an app, so it reaches exactly as far as the apps and wallets that integrate it. Bogotá’s TransMilenio — 2.5 million daily riders — already runs presence-verified promotions this way, and fare-collection integrations are underway from Delhi to Jaipur.
Whatever technology wins, the requirement is now legible: as wallets evolve from storage into interface, presence verification stops being a nice-to-have and becomes the trust layer the whole stack rests on. Passes that act need proof of context. Identity that verifies needs proof of proximity.
Before your competitors’ passes wake up
If you issue anything a customer might hold — tickets, loyalty cards, gift cards, memberships, insurance documents, stored value — this summer set your agenda.
Treat the pass as a product, not an export. It needs an owner, a roadmap, and metrics. “We support wallet” is the new “we have an app” — true of everyone, meaningful for no one.
Design the action set around the lifecycle, not launch day. Ticketmaster’s twelve links matter because they change over the asset’s life: transport before, upgrades during, re-engagement after. Map the equivalent arc for a gift card (activate → check balance → top up → re-gift) or a membership (onboard → book → renew) before your first pass ships.
Instrument it like a channel. Google exposes pass analytics and field-change notifications to issuers; Apple’s semantic tags feed Live Activities. If wallet engagement isn’t on a dashboard next to email and push, you’re flying a new channel blind.
Verify presence at the moments of value. Decide, use case by use case, how you’ll know the pass, the person, and the place actually coincide — against all five requirements, with consent designed in — before any pass of yours learns to act.
The digital wallet spent its first decade winning the transaction. It will spend the next one owning everything around the transaction — the proof, the relationship, the moment after issuance when yesterday’s passes went dark. Apple showed the industry what a pass looks like when it wakes up. Is your pass awake when your customer looks at it?