# Yurplan

### Why connect Yurplan to The Wallet Crew

Yurplan is a ticketing platform for event sales and attendee management. The Wallet Crew adds the wallet layer on top, so Yurplan tickets can be distributed as **Apple Wallet** and **Google Wallet** passes.

This integration makes it possible to expose an **Add to Wallet** button directly in the Yurplan confirmation page and in the confirmation email. This keeps distribution close to the purchase flow and removes the need for a separate app-specific journey.

Yurplan remains the source of truth. Ticket data stays in Yurplan, and wallet passes stay synchronized with it over time. When ticket information changes in Yurplan, the installed pass is updated automatically.

{% hint style="info" %}
Yurplan controls ticket data and ticket state. The Wallet Crew handles pass creation, distribution, and wallet-side updates.
{% endhint %}

<details>

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

* **Confirmation page distribution**: after checkout, attendees add their ticket to Apple Wallet or Google Wallet directly from the Yurplan confirmation page.
* **Confirmation email fallback**: the same order can also expose an **Add to Wallet** entry point in the confirmation email.
* **Ticket change after purchase**: if event or ticket data changes in Yurplan, the wallet pass refreshes automatically.
* **Ticket cancellation**: when a ticket is cancelled in Yurplan, the matching pass is updated to stay aligned with the ticket status.
* **Entry control follow-up**: when a ticket is checked at the venue, the corresponding pass metadata can be updated from the Yurplan event flow.

</details>

### What this integration unlocks

This connector turns Yurplan tickets into live wallet credentials. Each confirmed ticket can become one wallet pass, ready to be stored on the phone and presented at the entrance.

The operational value is immediate. Wallet passes are easy to retrieve, offline-ready at the gate, and kept current without asking attendees to search for PDFs or old emails. For event teams, this reduces delivery friction and makes ticket updates more reliable.

Because distribution happens from the confirmation page and confirmation email, the integration fits naturally into the existing Yurplan purchase journey. No duplicate ticket database is needed in The Wallet Crew.

### How the connector works

The connector listens to Yurplan lifecycle events and converts them into wallet actions.

1. **Order confirmed**: The Wallet Crew creates one wallet pass per ticket.
2. **Ticket identification**: each ticket is stored with a unique identifier in the format `eventId|ticketToken`.
3. **Ticket canceled or checked**: the connector receives the Yurplan event, finds the matching pass through `yurplan.ticketId`, and updates the pass metadata.
4. **Data enrichment**: customer and pass data are retrieved from Yurplan APIs, including attendee name, barcode token, ticket type, price, event information, venue information, images, and scan count.

The connector uses a tenant-level default pass type when creating Yurplan wallet passes. This keeps issuance consistent across events unless a more specific setup is added later.

### Distribution in Yurplan

This integration supports the two key ticketing touchpoints already present in Yurplan.

The first touchpoint is the **confirmation page**. It supports a direct **Add to Wallet** action immediately after purchase, when intent is highest and the ticket is still top of mind.

The second touchpoint is the **confirmation email**. It acts as both the standard distribution channel and a recovery path when the confirmation page is closed or the purchase was completed on desktop.

Together, these two touchpoints cover most ticket delivery journeys without adding extra operational complexity.

### Data synchronization and ticket lifecycle

The core principle is simple: Yurplan remains authoritative for ticket data. The Wallet Crew does not become the primary ticketing system. It reads ticket information from Yurplan and mirrors it in wallet format.

The connector receives Yurplan webhooks for key lifecycle events:

* `order confirmed`
* `ticket canceled`
* `ticket checked`

This event-driven model keeps passes aligned with the current state of the ticket. It is especially useful for event operations, where a ticket can change after purchase and still needs to remain trustworthy at the entrance.

### FAQ

<details>

<summary><strong>Can The Wallet Crew be connected to Yurplan?</strong></summary>

Yes. The Wallet Crew can connect to Yurplan and transform Yurplan tickets into Apple Wallet and Google Wallet passes.

</details>

<details>

<summary><strong>Where can the “Add to Wallet” button be displayed?</strong></summary>

The integration supports the Yurplan confirmation page and the Yurplan confirmation email. These are the two standard post-purchase touchpoints for ticket delivery.

</details>

<details>

<summary><strong>Where is ticket data managed after the integration is enabled?</strong></summary>

Ticket data remains managed in Yurplan. The Wallet Crew reads Yurplan data and keeps the wallet pass synchronized with it.

</details>

<details>

<summary><strong>How many wallet passes are created for one order?</strong></summary>

The connector creates one wallet pass per ticket when the order is confirmed.

</details>

<details>

<summary><strong>What happens when a ticket is cancelled or checked in Yurplan?</strong></summary>

The Yurplan event is received by the connector. The matching pass is found through the Yurplan ticket identifier, then the pass metadata is updated so wallet data stays aligned with Yurplan.

</details>

<details>

<summary><strong>Are ticket changes reflected automatically in the wallet pass?</strong></summary>

Yes. When ticket information changes in Yurplan, the wallet pass is updated automatically.

</details>