Ticketing

Why Apple and Google Wallet are standard for ticket delivery, what wallet tickets can include beyond access info, and how The Wallet Crew connects ticketing with other systems.

Ticketing in Apple Wallet and Google Wallet is no longer a “nice to have”. In many event ecosystems, it is a standard distribution format and a must-have distribution channel. Customers are already used to it and expect an Add to Wallet option in confirmation and account flows, alongside PDFs and mobile app tickets.

A ticketing solution that only generates a barcode misses most wallet value. Wallet turns the ticket into a live credential. It stays accurate, scannable, and useful throughout the event lifecycle.

Why wallet is critical for ticketing solutions

Wallet means more than putting a QR code in a pass. It uses wallet as a reliable entry credential and a post‑purchase surface, while keeping the pass consistent with the ticketing source of truth.

Wallet matters because ticketing is time‑sensitive and operational. Late changes are common, and entry lines are unforgiving.

Typical wallet capabilities that become critical at scale:

• Offline-ready access at the gate. The pass remains available without browsing email.

• Always up to date. Gate changes, start time changes, seat moves, and cancellations can sync.

• Clear state. Invalidated tickets can be visibly expired or disabled.

• Lower support load. Fewer “where is my ticket?” cases than PDFs and emails.

• More secure distribution patterns. Wallet providers support controls like pass sharing rules.

Real-world examples

• Last‑minute gate change: update “Gate B” on the pass, then notify attendees.

• Seat change after exchange: refresh row/seat automatically, without re-downloading PDFs.

• Event day operations: add “Doors open” and “Bag policy” on the back of the pass.

• On-site value: attach drink vouchers or merchandise pickup instructions to the ticket.

• VIP experience: show lounge access rules and a fast-lane entry message.

Wallet ticket distribution is becoming the default

Wallet passes match how customers already store credentials on their phone. They are quick to retrieve and hard to lose. They also reduce reliance on printing and PDF handling.

For ticketing solutions, wallet support is increasingly part of basic compatibility. Without it, distribution options look incomplete in mobile-first journeys. With it, ticket delivery becomes one tap, then self-service.

In ticketing, the pass is a credential first. Marketing value exists, but operational reliability comes first.

Wallet can support an event, and more than access control

The Wallet Crew works as a wallet layer across systems. Ticketing stays the source of truth for ticket state. Other systems can enrich the same wallet experience.

Common sources connected around a ticketing program:

• Ticketing system: event, venue, seat, barcode/QR, ticket status, transfers.

• CRM / customer data: profile identifiers, segmentation, eligibility, service flags.

• Loyalty / membership: tier, benefits, entitlement rules, member-only access.

• Marketing automation: controlled messaging and operational notifications.

• On-site tooling: scanning and validation workflows.

This makes wallet more than “a ticket in a phone”. It becomes a support surface for the event, before and during arrival, and sometimes after. A ticket can contain more than access information, such as venue guidance, event policies, entry instructions, perks, or links to related experiences.

Connecting to any system (API and generic connector)

The Wallet Crew is not limited to listed ticketing connectors. Any system that can expose identifiers and ticket lifecycle signals can be connected using The Wallet Crew API and a generic/custom connector approach.

This model is often used to connect proprietary ticketing platforms, event apps and customer portals, access control systems, and existing CRM/loyalty stacks.

The Custom connector section documents extensibility patterns, and the API reference documents issuance and update endpoints. For change-driven updates, Webhook covers event delivery and signature validation.

For pass design specifics, see Event ticket.

What a ticketing solution should expose for a wallet integration

A wallet integration depends on data quality and lifecycle signals. The most important requirements are stability and change tracking.

A ticketing integration usually needs:

• A stable ticket identifier and a barcode/QR value used at entry.

• Event metadata like name, date/time, and venue.

• Seat or zone information when applicable.

• Ticket lifecycle states like active, exchanged, cancelled, or refunded.

• A way to detect changes, typically via webhooks or a scheduled sync.

FAQ

What can a wallet ticket contain besides access information?

Wallet tickets can carry operational and experience information, not only a barcode. Common additions include gate and time, venue details, entry instructions, event policies, messages, perks, and deep links to event or account pages.

Can a wallet ticket be updated after installation?

Yes. Wallet passes are designed to be updated after installation. This is what keeps the ticket trustworthy after exchanges or schedule changes.

Can the same wallet experience combine ticketing data and CRM/loyalty data?

Yes. The Wallet Crew can connect multiple source systems in one program. The ticketing system can stay authoritative for ticket state. CRM and loyalty can enrich fields, links, and entitlements.

Is Apple Wallet / Google Wallet only useful for marketing messages?

No. For ticketing, the primary value is operational. The pass is scannable, offline-ready, and easy to retrieve at entry time.

What if the ticketing solution is not listed as a connector?

A custom integration can be built using The Wallet Crew APIs and webhooks. This keeps the ticketing tool as the source of truth. It also enables the same distribution and update mechanics as built-in connectors.