2026 Dent Blanche V1
Objectives & high level scope
The objectives of this release are:
Powering up for the major summer events, and this year is definitely world class!
Getting even better, one feature at a time, always.
Powering up for the major summer events
Improve BackOffice
Looking for smoother operations in BackOffice? We are bringing enhanced ticket search, improved filtering, better contingent support, and a new "Open in Excel" export—making troubleshooting and daily tasks faster and more efficient for operators.
Expanding the reporting domain
Are you missing some data in the new V4 reporting domain? We are improving it based on past experience to have all the needed data to support major summer events.
Ticket Check: port NFC POC to V4
Interested to test NFC cards to perform a ticket check at outer perimeter? We are making the Proof of Concept of this feature available for TIXNGO V4 so it can be further tested in 2026.
Getting even better, one feature at a time
Curiosity layout & Match semantics improvements to boost adoption
You think the new Curiosity layout or Match event semantics are promising? We are improving those two features and integrating them for tickets looking better than ever, and in more contexts!
Other Miscellaneous improvements
As always, we also plan a list of small yet impactful improvements to the mobile app and Backoffice that will simplify everyone's work. Follow the detailed release notes to find these hidden gems.
True Ticket Preview in BackOffice
Are you injecting test tickets to configure your design rule and verify the result? We are introducing a true ticket preview displayed side-by-side with the design rule, showing the final look immediately. We are also including this preview in the ticket support screen to help troubleshoot injection and ticket configuration.
Transfer by link
Looking for a faster, more intuitive way to transfer tickets? You can now share a ticket via a secure link using your device’s native sharing options, offering a modern alternative to email transfers and fully configurable per usage rule.
While introducing this new capability, we will review and improve the full transfer experience!
Unfortunately, Transfer by link and True Ticket Preview had to be postponed in order to keep the focus on the refinement of existing features and the stabilization of the platform before the major summer operations.
Release planning
Here are the planned installation dates of every iteration of this version.
| PRE-PROD | PROD |
|---|---|---|
DBV1.1 | 28.01 | 03.02 |
DBV1.2 | 03.031 | 05.031 |
DBV1.3 | 03.03 | 05.03 |
DBV1.4 | 11.03 | 17.03 |
DBV1.5 | 25.03 | 31.03 |
DBV1.6 | 08.04 | 14.04 |
1 Release V1.2 & 1.3 are merged due to Tet holidays in Vietnam.
Exact deployment date per slot can vary by a few days for operational reasons.
Detailed release notes
Here will be unveiled, one increment at a time, the new features available in the next deployment.
Multi‑factor authentication (MFA) is mandatory for all TIXNGO Backoffice accounts since March 1, 2026. Backoffice users can set up MFA and generate access codes using either mobile or desktop tools that support the open, vendor-neutral TOTP standard.
DBV1.6
Apply seating flow configuration consistently in mobile (visibility labels & custom flow)
Mobile now applies the organizer’s seating display configuration consistently across the entire app—not only on the Ticket details screen. Whenever a ticket is configured with a custom flow (venue-specific seating flow) and/or custom labels / visibility rules, the same seating presentation is used everywhere seating information appears, reducing confusion when spectators switch between screens.
 Blue ribbon displays | Ticket selection for transfer displays the custom flow | Ticket resale shows the custom flow |
|---|
More details: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/337609375
This change requires a new mobile app build.
Reporting
We extend Ticket V4 reporting to give a clearer view on ticket usage and to simplify large‑scale analytics:
External Wallet statistics – Apple / Google Wallet usage now included in Event statistics (add/remove, control, transfer, current status split) for better adoption tracking.
Incremental data retrieval – Ticket, Spectator V4 and Device V4 reporting APIs support incremental loads via last‑updated filters, optimized for BI/ETL refresh scenarios.
More details: https://go.confluence.secutix.com/wiki/x/dYANE
Spectator support: transfers easier to review (Pending moved to Past transfers)
To simplify investigations, Pending transfers are now under the Tran with past transfers, giving support a single view to resolve requests faster.
More details: https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/195692627
Miscellaneous
Backoffice navigation – The side menu has been refined so operators can focus on what they use most: Event stats now sit directly under Events, and Create event is available as a clear primary action inside the Events screen.
Backoffice mobile logs (spectator V4 only) - When a backoffice user forces a logout or resets devices, the mobile log entry includes the acting operator's email, for example: Spectator device session removed from backoffice by abc@gmail.com.
DBV1.5
New additional placeholder
It’s now possible to display additional icons on the top of specific tickets by setting a special metadata. This can be used when stewards need to visually check particular conditions, for instance some special access right given only to some tickets.
More details:https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/202867749/V4+Ticket+Layout+Classic#Top-icon-display
Improved communication search in Backoffice
Backoffice communications screens have been improved so that operators can:
Search communication logs using multiple templates at once:
Communications logs filtering with multiple templates selectionFilter email & notification communication templates by setting key and audience to simplify configuration and maintenance:
Communication template filtering with multiple keys & audiences selection
Miscellaneous
Starting from this release, the MFA option cannot be switched off anymore.
Columns order in the mobile logs tables (global and on spectator screen) has been changed to show the most useful information first, leading with the system date.
DBV1.4
Better looking team logos on ticket
When using match event semantics, the team logos are now displayed significantly bigger and without borders or background for best visual impact with semi-transparent logos.
More information in: https://go.confluence.secutix.com/wiki/x/hAAjDw
Improved contingent filtering in Backoffice
If you are leveraging contingents in S-360, it is now easier to filter on them in TIXNGO Backoffice: the contingent related to each ticket is displayed in the ticket list, and the contingent filter supports multi-selection but more importantly is not dependent anymore of the event filter. This also applies to transfers lists (pending & past) in the spectator support screen.
The contingent visibility is managed by the Organizer setting enable.contingent.feature. Set it to “true” if you need this feature and don’t see it, and false otherwise.
Miscellaneous
A new ticket deletion reason (with corresponding notification) has been added: ONSITE_TROUBLESHOOTING. This deletion reason is dedicated to “local” TIXNGO deletions and will never be used for tickets deleted from S-360, and it is exactly the point of this addition.
NFC tickets: logs of interactions with the external wallets systems are now available in the Ticket Support Screen for troubleshooting
SDK & branded app telemetry can now record events as well towards Adobe Analytics, in addition to the standard Firebase
When using Spectator V4 and ticket assignment, a change in the spectator profile will now correctly update the ticket holder information for future tickets.
Transfer/assign/resale/exchange after ticket check configuration is now working again.
DBV1.3
This includes in a single the release V1.2 & V1.3
Backoffice Improvements
This release brings again a bunch of improvements to the Backoffice user interface, for more efficient operations, every day.
Ticket list
On the central ticket list screen, it’s now possible to:
Search a ticket
Select multiple statuses, for instance to exclude the Deletion pending and Deleted tickets;
See the total number of tickets matching the current filter criteria, with full precision, on the top left of the ticket list table with label “Filtered results”.
Ticket support screen
Ticket status history UI has been improved by:
Adding a copy button for additional information fields.
Removing the duplicate technical IDs in the additional information section of Detailed view.
Improving the default columns width so all columns are visible by default in the ticket history view on a standard full HD laptop screen (no horizontal scroll bars).
And also:
In the header, you can now click on the event name to open the event list to quickly navigate to other tickets of this event or change something in the event configuration.
On the metadata tab, the Purchase details box now shows the names sent by S-360 instead of the technical IDs
Purchase details are now displayed like on the mobile (incl. translations)
Miscellaneous
It’s now also possible to search a campaign by a part of it’s name, especially useful if you use naming conventions for your campaigns.
Tightening security
Starting from this version, the newly introduced Reporting API Key must be used for all reporting domain queries. Existing API keys (now renamed “Ticketing” for clarity) are not allowed anymore on the reporting endpoints. You will find the organizer’s Reporting API Key in the “My Account” section of the Backoffice just below the Ticketing API key (note you must have ADMIN role to see this).
We are improving our capabilities to detect and block illegitimate usage of the TIXNGO mobile app in order to protect our systems and ensure the fans are not affected.
Finally we added an extra layer of protection to the Manuel ticket activation from the mobile: after 10 attempts with invalid PIN, a 5 minutes ban will be enforced (same limits as for the deactivation).
DBV1.1
Open in Excel
On key Backoffice screens, a new Open in Excel function allows operators to export the currently downloaded data to an Excel file. This enables quick troubleshooting and sharing outside the Backoffice, once the operators selected the relevant data using the filters.
This function is available on the following screens:
Ticket list
Mobile Logs
Communication
Currently downloaded data means all data already downloaded by the Backoffice to display in the table. The amount of data downloaded depends on the screen:
For the ticket list, data is downloaded by chunks of 1’000
For other screens, data is download by visible page of 50
If you need to open more data in excel than the current page, use the pagination function to load more data.
Ticket small display improvements
On Classic
We made the “badges” icons bigger better visibility to make onsite visual checks easier and, when wristband is used, easier tap to mark the wristband as “given”.
The custom at_icon is now displayed in a 38x38px to fit nicely in the gray circle.
On Curiosity
Add “Ticket x of y” on top for clearer overview of the wallet
Now, the “main” metadata are displayed in a dedicated section higher on the ticket, just before the “Purchase details” section.
Curiosity layout is designed to switch automatically to Classic on event day to focus on operational information for smooth onsite operations. As a failsafe in case this doesn’t work for whatever reason, it is now possible to manually activate a ticket still displayed in Curiosity by long-pressing the text in green:
Miscellaneous changes
Mobile
The assignment reminder pop-up now appears whenever Assignment is enabled in the Usage Rule, and not only when mandatory.
It’s now possible to disable resale/exchange after ticket check.
Accessibility of the mobile app, and especially screen reader support, has been improved.
NFC ticket check POC is now available in TIXNGO V4, so it can be further tested in 2026. Contact TIXNGO team if you want to test this POC.
Additional fields collected using the per-event spectator data collection (see https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/195691608 ) are now displayed before the opt-ins on the Profile screen of the mobile App
TIXNGO SDK is now more stable when embedded into React Native apps
Interfaces
Feedback interface to S-360 is now also triggered when spectator is anonymized on TIXNGO for all tickets owned by this spectator. This will make sure the ticket owner information is anonymized on S-360 as well. Anonymized ticket will have owner email similar to ANONYMIZED_16630215@anonymized.anonymized.