# Updates, lifecycle, and installation status

This integration is built for change. Event tickets get reprinted, exchanged, moved, and cancelled. The Wallet Crew keeps the wallet ticket aligned with Secutix. Sometimes that means updating a pass. Sometimes it means invalidating it.

## How integration works

Secutix stays the source of truth for ticket and contact data, and The Wallet Crew only adds the wallet layer. The Wallet Crew doesn’t store your full ticket dataset. Each pass stays linked to Secutix through external identifiers: `secutix.movementId` for event tickets and `secutix.contactNumber` for member cards. When a pass is created or updated, The Wallet Crew calls Secutix web services to fetch the latest data, then rebuilds the pass payload and pushes the update to devices.

<div data-with-frame="true"><figure><img src="https://3566051324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWLc8AHXW4tdrAXUBfrYF%2Fuploads%2F3504hifkqVrJQtA32wK3%2Fimage.png?alt=media&#x26;token=1e9d022e-31f5-4951-8c9e-743eccaea3b7" alt="Integration schema showing Secutix as the source of truth, The Wallet Crew syncing ticket changes, and Apple Wallet / Google Wallet passes being updated."><figcaption><p>Integration schema: The Wallet Crew fetches changes and pushes Secutix ticket to Apple &#x26; Google Wallet .</p></figcaption></figure></div>

## How updates work

Secutix can change tickets in several ways, like the **ticket shop** (self-service) or the **back office** (agent actions). When a change happens, Secutix notifies The Wallet Crew via webhook. Then the connector updates the existing pass or invalidates the old one.

<details>

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

* Start time changes in Secutix back office. The wallet pass updates within seconds.
* Buyer reprints. Barcode changes. The wallet pass refreshes.
* Exchange creates a new ticket. Old pass is invalidated. New pass becomes valid.
* Refund deactivates the pass so it can’t be scanned.

</details>

## Update pass scenarios matrix

Use this matrix to predict what wallet users will experience. It also helps support teams answer “why did my ticket change?” quickly.

| Use Cases                                   | Possible from the Ticket Shop | Possible in Back Office | New Secutix Transaction | New Ticket Generated | New Movement ID | New Order ID | New File ID | Secutix Transactional Email Sent | Ticket to be Updated in Wallet | Old Ticket to be Deactivated in Wallet |
| ------------------------------------------- | ----------------------------- | ----------------------- | ----------------------- | -------------------- | --------------- | ------------ | ----------- | -------------------------------- | ------------------------------ | -------------------------------------- |
| Change of the title or schedule of an event |                               | Yes                     |                         |                      |                 |              |             |                                  | Yes                            |                                        |
| Reprinting of a ticket                      | Yes                           | Yes                     |                         | Yes                  |                 |              |             |                                  | Yes                            |                                        |
| Change of ticket holder's name              | Yes                           | Yes                     |                         | Yes                  |                 |              |             |                                  | Yes                            |                                        |
| Change of cultural contact                  |                               | Yes                     |                         |                      |                 |              |             |                                  | Yes                            |                                        |
| Replacement of a spectator                  |                               | Yes                     | Yes                     | Yes                  | Yes             | Yes          |             | Yes                              |                                | Yes                                    |
| Ticket exchange                             |                               | Yes                     | Yes                     | Yes                  | Yes             | Yes          |             | Yes                              |                                | Yes                                    |
| Cancellation of a ticket                    |                               | Yes                     | Yes                     |                      |                 |              | Yes         |                                  |                                | Yes                                    |

## Installation status update

### Movement external references

Installation status is useful for reporting and post-purchase automation. The Wallet Crew writes wallet installation signals back into Secutix by default.

Ticket installation status is persisted into the Secutix **movement external references**.

This data is kept up to date over time. If a user uninstalls the pass, the status is updated accordingly. If they reinstall later, the same fields are overwritten with the latest status and device.

These keys are added:

* `twc.passId`: The Wallet Crew pass identifier
* `twc.passType`: template name used for the ticket
* `twc.status`: `installed` or `uninstalled`
* `twc.device`: `apple`, `google`, `apple+google` or `-` after pass has been uninstalled.

### Printing status

On first add to Apple Wallet or Google Wallet, The Wallet Crew sets the Secutix ticket status to **PRINTED**. In Secutix, **PRINTED** means the buyer retrieved the ticket.

Use this when you need Secutix-native retrieval tracking. It helps with compliance reporting. It can also enable resale flows (depending on your Secutix resale setup) that require **PRINTED**.

This is one-way. The Wallet Crew does not revert **PRINTED** if the pass is removed. Removal does not mean the ticket is unusable.

<div data-with-frame="true"><figure><img src="https://3566051324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWLc8AHXW4tdrAXUBfrYF%2Fuploads%2FqqlvDUo6R4Gf5v356iNX%2Fimage.png?alt=media&#x26;token=85671df1-1c27-44ca-aca0-2c50c8a4f595" alt="Update printing status option in the Secutix connector settings." width="443"><figcaption><p>Update printing status option in the Secutix connector settings.</p></figcaption></figure></div>

### FAQ

<details>

<summary><strong>How fast do Secutix tickets update in Apple Wallet and Google Wallet?</strong></summary>

By default, Secutix change webhooks run every **\~10 minutes**.

After The Wallet Crew receives the webhook, the wallet update is usually pushed in **seconds**.

</details>

<details>

<summary><strong>What triggers a wallet ticket update vs an invalidated (void) ticket?</strong></summary>

Simple edits usually **update** the existing pass.

Actions that generate a new ticket (exchange, replacement) usually **invalidate** the old pass and activate the new one.

</details>

<details>

<summary><strong>Do attendees need to re-add the ticket after a change?</strong></summary>

No. The pass is automatically updated or invalidated.

</details>

<details>

<summary><strong>My ticket looks outdated. What should I do?</strong></summary>

This is usually a device refresh issue.

Ask the attendee to:

* Check connectivity.
* Close and reopen the wallet app.

If needed, remove and re-add from the original link.

</details>

<details>

<summary><strong>Can I send a wallet notification for last-minute changes?</strong></summary>

Yes. Use wallet notifications for urgent, event-day updates.

Suggested copy:

* **"Update: your ticket details changed. Please open your Wallet ticket."**
* **"Update: your entry information has changed. Your Wallet ticket is up to date."**

</details>

<details>

<summary><strong>Geolocated notifications: can we notify users when they are near the venue?</strong></summary>

Yes. You can trigger a notification when attendees are near the venue. This works for Apple Wallet and Google Wallet.

Recommended starting radius: **50 meters**. Increase it for large venues or multi-entrance sites.

<figure><img src="https://3566051324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWLc8AHXW4tdrAXUBfrYF%2Fuploads%2F9fqkSb1VX3G0R4gPHJT7%2Fimage.png?alt=media&#x26;token=eba175ae-3339-443c-a512-6333dbb7f78d" alt="Example of geolocated notification"><figcaption><p>Example of geolocated notification.</p></figcaption></figure>

<figure><img src="https://3566051324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWLc8AHXW4tdrAXUBfrYF%2Fuploads%2FlbMbKHaPAj36hfE2NxRB%2Fimage.png?alt=media&#x26;token=f43e1037-9103-42b1-aa85-402430275c08" alt="Max distance setting for geolocated notifications"><figcaption><p>Max distance setting for geolocated notifications.</p></figcaption></figure>

</details>

If you need to double-check how tickets are delivered to users, go to [Distribution](https://docs.thewalletcrew.io/connect/ticketing/secutix/distribution).