Objectives & high level scope

Spectator V4 refactoring

Full refactoring of spectator-centric data management, focused on the SSO-only future

We modernized the Spectator data model for superior performance, scalability, GDPR compliance, and maintainability, centered on 100% SSO-based identity.

New and improved mobile devices & sessions management

We rebuilt spectator devices and sessions management as well to improve performance while maintaining our strong focus on security and control.

New reporting domain for spectators & their devices

Following the V4 design, all data of spectators & their devices are published in a dedicated reporting domain to empower organizer to leverage those data without impacting the operational system.

Tickets V4 improvements

Clarify ticket statuses & history

Are you puzzled by the new ticket statuses? We adjusted them to clarify and simplify the ticket history and align better with what syncs to S-360. Troubleshooting and spectator support, especially in complex cases, will benefit from these improvements.

Better support venues specificities in seating details flow

Does your complex venue signage not fit the S-360 physical configuration? First, you can configure seating detail labels in the Ticket Design rule.

Need more flexibility? Second, define a custom flow to display on the ticket screen using the S-360 injection template when the physical configuration can't model the venue signage.

Full bulk ticket update

Need to rename a gate or fix a typo in your TIXNGO tickets? We are bringing back the ability to bulk edit seating details and ticket metadata directly from the TIXNGO Backoffice screen!

Better support spectators with lots of tickets & transfers

Managing spectators with dozens, hundreds, or thousands of tickets for multiple competition events? We enhanced the Backoffice spectator support screen with filters and searches to help operators handle these spectators more efficiently.

Other Miscellaneous improvements

We plan a list of small yet impactful improvements to the mobile app and Backoffice UX that will simplify everyone's work. Follow the detailed re

Release planning

Here are the planned installation dates of every iteration of this version.

Detailed release notes

Here will be unveiled, one increment at a time, the new features available in the next deployment.

RIMV4.6

NFC ticket support through Apple & Google Wallet

Do you want to support NFC at Access Control? This is now possible through a dedicated interface of T

For Apple Wallet, we are supporting all the new semantics introduced by Apple with iOS 18.1 for rich ticket display on iOS devices.

Open

Apple Wallet NFC ticket

Moreover, event information will be kept up to date

More information:

• https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/49218147

• https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/535953622

• https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/536314003

Ticket Check at OSP

We ported all the Ticket check features used in Outer Security Perimeter (OSP) context to tickets V4, namely:

• Bluetooth beacons (cards & gates), including generating unique Bluetooth ID per event

• Manual ticket check, with new bigger trigger zones but only enabled when ticket is activated for more security:

Open

Manual ticket check at OSP will be simpler thanks to bigger trigger zone

Per-event spectator data collection

For organizers having to deal with different data collection requirements per event, typically for events happening in different countries, it is now possible to configure a dedicated data collection rule that will be applied to all wallet owners (spectators) of an event. In practice, this means the spectator will have to complete his profile if needed (only once), before being able to view the tickets.

Open

If configured, additional information should be entered before seeing the tickets.

More information: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/195691608

Scan the ticket barcode to open a ticket in BackOffice

Do you have a barcode scanner available at your onsite Ticketing Support Center? It’s now possible to directly scan the ticket barcode from TIXNGO BackOffice home screen to open directly the corresponding ticket!

Open

Support landing page now supports entering the barcode

Miscellaneous small changes

• It’s now possible to configure in the ticket

• It’s now possible to override per event the seating details field to use as condition to show the alert to remind your spectators to transfer tickets if these tickets have a different seating location in the venue.

• Event name can again be translated in all languages supported by the app.

• Event number can now again be defined also for “Standard” events and not only “Match” ones.

• Wristband icon is still displayed if hosp_room metadata is set even if hospitality field is hidden in design rule configuration.

• Anonymization support for Spectator V4 has been added.

• In the reporting domain, the Full Ticket List data set now contains display names in addition to the technical ID for reference data coming from S-360 (e.g. contingent, seat category, etc).

• [Security] OTP validity is now by default reduced to 5 minutes. Validity can be configured by TIXNGO team per organizer.

RIMV4.5

Bulk spectator actions

Add new self-service bulk actions on spectators in the Backoffice. It’s no more required to do a service request to perform the following action for a list of spectators:

1. Anonymize

2. Clear Active Sessions or Devices

3. Lock/Unlock

More details in https://go.confluence.secutix.com/wiki/x/FIDEHw

Put on resale UX improvement

The S-360 Online Sale team is improving the ticket resale process UX. On TIXNGO, we removed the initial hurdle of a confirmation popup before opening the WebView:

Open

The useless confirmed popup we removed

Miscellaneous small changes

• Auto-cancellation of a transfer is now notified to both recipient and sender.

• It’s now possible to duplicate Ticket configuration rule.

• It’s now possible to focus a communication campaign to one specific contingent.

RIMV4.4

This release is packed with both powerful features and small but impactful improvements. Enjoy!

Full bulk ticket update

Need to rename a gate or fix a typo in your TIXNGO tickets? We are bringing back the ability to bulk edit seating details and ticket metadata directly from the TIXNGO Backoffice screen! And yes, we also support updating the new ticket Custom Flow.

Open

Bulk update of seating details, in a brand new bulk update wizard

To make this very powerful tool easy and safe to use, we built a wizard to give you all the information and guide you all the way!

Detailed documentation: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/320274550

Supercharged event selection, and filters persistence in BackOffice

This could be seen as a small UX improvement, but we are confident this will radically change your daily usage of the Backoffice, to the point that you will soon forget how it was before.

Open

Selecting events in Backoffice has never been so efficient!

On a selection of screens, we have made the event selection really efficient with:

• Easy filters: today, next X events

• Improved search on event name, dates & ID

• Easy multiple selection / de-selection

And on top of that, the filters on these screens are now saved on your browser! So when switching screens you will automatically keep the same context.

Spectator V4

We are working on that for months, and it’s finally ready to start rollout. There is not many visible changes, but under the hood this has been a complete overhaul !

Full refactoring of spectator-centric data management, focused on the SSO-only future

We modernized the Spectator data model for superior performance, scalability, GDPR compliance, and maintainability, centered on 100% SSO-based identity.

More information: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/323092481 & https://go.confluence.secutix.com/wiki/s

New and improved mobile devices & sessions management

We rebuilt spectator devices and sessions management as well to improve performance while maintaining our strong focus on security and control.

More information: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/339378993

New reporting domain for spectators & their devices

Following the V4 design, all data of spectators & their devices are published in a dedicated reporting domain to empower organizer to leverage those data without impacting the operational system.

More information: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/235210405 and more specifically:

• https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/378208332

• https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/379060259

• https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/378339407

Miscellaneous small changes

• The Transfer reminder alert to remind spectators to transfer tickets with “incompatible” seating details (like a different gate) can now be customized for each event in the Overwrite settings tab (overriding the existing global Organizer setting).

• [Backoffice] It’s now possible to target only a specific contingent when creating a campaign

• [Backoffice] Before

• [Backoffice] Barcode number is now also displayed in the header of the Ticket support screen.

• [Backoffice] In Spectator support screen, the valid tickets listed are now displayed by default

• [Reporting domain] In the full ticket list, we added display names of contingents, tariffs, seat categories and tickets rules, in addition to IDs.

• [Mobile] TIXNGO app & SDK are now officially compatible with Harmony OS with the following limitations:

  • No push notifications are sent, but the app is fully usable without them.

  • SECUTIX will NOT publish apps in Huawei AppGallery. If needed, organizer can publish the app with their own account.

• [Mobile] TIXNGO SDK is officially compatible with REACT mobile apps.

RIMV4.3

Better support spectators with lots of tickets & transfers

Managing spectators with dozens, hundreds, or thousands of tickets for multiple competition events? We enhanced the Backoffice spectator support screen with filters and searches to help operators handle these spectators more efficiently.

Open

New powerful filters in the Past transfers view in the Spectator Support Screen

More details in https://go.confluence.secutix.com/wiki/x/UwiqCw

Miscellaneous small changes

In the Communications screen, it’s now possible again to list ALL communications sent over a given time period, no other filters required.

RIMV4.2

Better support venues specificities in seating details flow - part 2

Need more flexibility that seating details label overrides? Define a fully custom flow to display on the ticket screen using the S-360 injection template when the physical configuration can't model the venue signage.

Open

Custom flow defined for a ticket, visible in BackOffice & on the Mobile app

More details in https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/337609375

Clarify ticket statuses & history

Are you puzzled by the new ticket statuses? We adjusted them to clarify and simplify the ticket history and align better with what syncs to S-360. Troubleshooting and spectator support, especially in complex cases, will benefit from these improvements.

Smarter Logs & History

Open

New Ticket History Overview simplified screen, matching 1:1 the history synchronized with S-360

Mobile Timestamps: Ticket status logs now include the mobile device’s timestamp, providing precise context for every event—even offline or manual activations.

Ticket History Redesign: The “Status history” section is now “Ticket history,” split into two tabs:

• Overview: Major events at a glance, matching the S-360 summary & using S-360 mobile statuses terminology.

• Detailed: All the granular details, with improved columns and clearer timestamps.

More information in https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/196280443

More accurate ticket deletion tracking

Open

A ticket in DELETION PENDING status

Introducing the DELETION PENDING status! Now, whenever a ticket deletion is requested (via S-360, API, or Backoffice), you’ll see this new status until all devices confirm deletionDELETED.

The DELETION_PENDING status is visible everywhere you need it: main ticket lists (with filtering!), spectator support screens, ticket support screens, and more.

This change brings us back in line with S-360, making troubleshooting easier and statistics clearer.

Enhanced Ticket Attributes

• Delivered Attribute: A new “Delivered” attribute added (with a timestamp!) to record the very first time a ticket is downloaded. This attribute never resets, ensuring you always know when a ticket was first delivered, regardless of the number of times it has been transferred.

• Activated Attribute: Now, the “Activated” timestamp is only reset on manual deactivation, deletion, or specific transfer scenarios—never on logout. This ensures more accurate tracking of ticket activation time.

• Comprehensive Filtering: You can now filter ticket lists by Delivered, Assigned, and Kept by Owner attributes, making it easier than ever to find exactly the tickets you need.

S-360 Feedback Alignment

Statuses in the feedback interface are now fully aligned with S-360. We also improved the additional info field, including for instance recipient email visibility for pending transfers. More information in https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/380338185.

Other changes

In the ticket list screen, it is now possible to filter tickets by Contingent. Please note that the Contingent filter is available only after selecting at least one event.

RIMV4.1

Better support venues specificities in seating details flow - part 1

Does your complex venue signage not fit the S-360 physical configuration? You can override seating detail labels in the Ticket Design rule.

Want to hide some seating details in some cases? The Ticket Design rule now let you configure the visibility of ALL fields.

More information: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/134088452/V4+Design+rules#Ticket-fields-visibility-customization

Other changes

Mobile

Returning a ticket, or transferring it from Backoffice, will not require acceptance anymore, even if transfer accept/reject feature is enabled. More information: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/337215511

It will also be possible to show only some of the deleted tickets in the mobile app depending on the deletion reason. More information: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/49217764

General performance enhancements have been implemented, especially for spectators having lots of tickets.