Updates, lifecycle, and installation status

Understand update vs deactivate behaviors, common ticket change scenarios, and how installation status is persisted back to Secutix.

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.

Integration schema: The Wallet Crew fetches changes and pushes Secutix ticket to Apple & Google Wallet .

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.

Real-world examples

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

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. When enabled, it writes wallet installation signals back into Secutix.

If you enable Persist installation status, The Wallet Crew persists ticket installation status 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.

Persist installation status option in the Secutix connector settings.

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.

Update printing status option in the Secutix connector settings.

FAQ

How fast do Secutix tickets update in Apple Wallet and Google Wallet?

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

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

What triggers a wallet ticket update vs an invalidated (void) ticket?

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.

Do attendees need to re-add the ticket after a change?

No. The pass is automatically updated or invalidated.

My ticket looks outdated. What should I do?

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.

Can I send a wallet notification for last-minute changes?

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

Geolocated notifications: can we notify users when they are near the venue?

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.

Example of geolocated notification.

Max distance setting for geolocated notifications.

If you need to double-check how tickets are delivered to users, go to Distribution.