> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/ticketing.md).

# Ticketing

Apple Wallet and Google Wallet provide a practical ticket delivery channel. An **Add to Wallet** option can complement PDFs and mobile app tickets in confirmation and account flows.

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.

<details>

<summary><strong>Real-world examples</strong></summary>

* **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.

</details>

## 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.

{% hint style="info" %}
In ticketing, the pass is a credential first. Marketing value exists, but operational reliability comes first.
{% endhint %}

## 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.

### Ticketing platforms not listed

An unlisted ticketing platform can become a standard connector. The Wallet Crew and the ticketing-platform partner jointly scope that option when the integration can support multiple Brands.

For proprietary platforms or tenant-specific requirements, use a [custom connector](/connectors/custom-connector.md). Tenant scripting can call APIs, map ticket data, and react to lifecycle signals.

This approach also supports event apps, customer portals, access-control systems, and CRM or loyalty platforms.

## 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

<details>

<summary><strong>What can a wallet ticket contain besides access information?</strong></summary>

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.

</details>

<details>

<summary><strong>Can a wallet ticket be updated after installation?</strong></summary>

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

</details>

<details>

<summary><strong>Can the same wallet experience combine ticketing data and CRM/loyalty data?</strong></summary>

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.

</details>

<details>

<summary><strong>Is Apple Wallet / Google Wallet only useful for marketing messages?</strong></summary>

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

</details>

<details>

<summary><strong>What if the ticketing solution is not listed as a connector?</strong></summary>

The Wallet Crew and the ticketing-platform partner can scope a standard connector. A custom connector can also use tenant scripting and APIs for a proprietary integration.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/connectors/ticketing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.