[ 1 New ownership-related ticket properties: Initial & Previous Owners ] [ 2 New Ticketing Business-oriented tickets ] [ 3 New ticket statuses and attributes ] [ 4 New Ticket Deletion Reasons ]

New ownership-related ticket properties: Initial & Previous Owners

TIXNGO tickets v4 now include standardized ownership properties:

current owner (improved since V3)
initial owner (improved since V3)
previous owner (in case of ticket transfer)

These new Ownership fields will be visible from the V4-version of the Support Ticket screen.

New Ticketing Business-oriented tickets

TIXNGO tickets v4 now include business-focused data by default. Alongside the classical ticket identification (ticket number, ticket external id, barcode, ….) we promoted the following properties:

Purchase Details	Seating Details	Advanced Seating Details

Purchase Details	Seating Details	Advanced Seating Details
purchaseDate fileNumber purchasePrice purchaseCurrency seatCategoryId contingentId tariffId	seated (Y/N) numbered (Y/N) externalEntrance gate level area block row seat	physicalSeatId companionSeatId salesSeatId leftSeatId & rightSeatId frontSeatId & backSeatId seatQuality & temperature xcoord & ycoord

Please note:

These “business-oriented” properties
- are automatically injected by S-360, removing the need for custom mapping in the template.
- will be visible from the V4-version of the Support Ticket screen.
While you can still use the standard MAIN, EXTRA, and HIDDEN key-value pairs to exten

New ticket statuses and attributes

With Ticket V4, status will reflect where the ticket is (on the phone, not on the phone, in transit). Other pertinent info previously existing as individual status are managed as attributes.

Ticket Status

The ticket status reflects where the ticket is now from the perspective of the secure wallet.

New TIXNGO Tickets statuses

Status	Description

Status	Description
`NOT_DOWNLOADED`	The ticket is currently not downloaded on any phone. This typically happens when: the ticket has just been injected (via S-360, CSV, or API) but not yet downloaded to any device; the spectator has logged out from all devices; a transfer was rejected or cancelled, but the sender has not yet re-downloaded the ticket;
`DOWNLOADED`	The ticket is currently downloaded and present on a spectator's device.
`PENDING_TRANSFER`	A transfer has been initiated but not yet accepted by the recipient.
`DELETION_PENDING`	The ticket has been deleted by the issuer, but some devices still have it (including offline ones).
`DELETED`	The ticket is deleted and not present on ANY device anymore (even offline ones)

Ticket Attributes

The attributes are tracking the major business milestones of the ticket. For each attribute, the timestamp at which it has been set to true is stored & displayed in the ticket support screen.

Attribute	Type	Description

Attribute	Type	Description
`Injected`	Boolean	Track the timestamp at which the ticket has been received by the system.
`Delivered`	Boolean	`TRUE` when the ticket has been downloaded at least once. This attribute is never reset so it will always store the timestamp of the first download.
`Assigned`	Boolean	`TRUE` when the ticket has been assigned and includes ticket holder details.
`KeptByOwner`	Boolean	`TRUE` when the ticket has been assigned and the wallet owner kept it for himself.
`Activated`	Boolean	`TRUE` when the ticket has been activated at least once (since the most recent deactivation). When activated, the QR code becomes visible in the mobile app. The ticket will be deactivated only if any of the following occurs: The ticket is manually deactivated on the mobile (operational feature protected by code) The ticket is deleted
`Checked`	Boolean	`TRUE` when the ticket has been checked (outer-perimeter check).
`Controlled`	Boolean	`TRUE` when the ticket has been scanned by Access Control.
`Deleted`	Boolean	`TRUE` once the ticket reached the final DELETED status

Ticket Actions

Ticket actions are recorded in the Ticket Status Log and drive status and/or attributes.

Action	Triggered by (Actor)	Effect on ticket

Action	Triggered by (Actor)	Effect on ticket
`Inject`	S-360 / API / CSV	Creates the ticket and initial log entry (`NOT_DOWNLOADED`)
`Download`	Mobile	Downloads the ticket to a device → usually `DOWNLOADED`. Also sets Delivered = TRUE.
`StartTransfer`	Mobile / Back-office	Sets status to `PENDING_TRANSFER`. If activated, deactivates first.
`EndTransfer`	Mobile / Back-office / System	Cancels an ongoing transfer and returns the ticket to its previous state. Or transfer accepted → owner changes.
`Activate`	Mobile	Sets Activated = TRUE and makes QR visible in the app.
`Deactivate`	Mobile	Sets Activated = FALSE (manual or system-driven before sensitive operations such as transfer).
`Assign / Unassign`	Mobile	Sets/clears holder info (Assigned, KeptByOwner).
`Check`	Mobile	Sets Checked = TRUE (outer-perimeter check).
`Delete`	Back-office / TicketingSystem	Sets status to `DELETION_PENDING` (cancels transfer first if any).
`Unlink`	Mobile / System	Confirms tic`DELETED`
`Control`	TicketingSystem	Marks control and sets Controlled = TRUE.
`UserLogoff`	Mobile / Back-office / System	Removes the ticket from the device and clears device association; may result in status `NOT_DOWNLOADED` when logged out from all devices.

"Triggered by (Actor)" indicates the system or component initiating the action.

Mobile: spectator’s device or app initiates the action (stores mobile timestamp).
Back-office: operator performs the action in TIXNGO BO (no mobile timestamp).
TicketingSystem: issuer-side systems (e.g., S-360).
System: TIXNGO internal automated processes.
Some actions trigger multiple actors depending on context (manual vs. automatic).

New Ticket Deletion Reasons

To simplify the invalidation logic inherited from S-360, TIXNGO V4 introduces its own set of 10 dedicated ticket deletion reasons, rather than retrofitting those from S-360.
This change streamlines both notification customization and manual ticket deletion from the TIXNGO back-office, offering a clearer, more consistent approach to managing deleted tickets.

Deletion Reason	Notification Template Key	Comment

Deletion Reason	Notification Template Key	Comment
`REFUND`	`push.ticket.deleted.refund`
`REPRINT`	`push.ticket.deleted.reprint`
`RESEAT`	`push.ticket.deleted.reseat`
`RESALE_CANCELLED`	`push.ticket.deleted.resale.cancelled`
`RESALE_PENDING`	`push.ticket.deleted.resale.pending`
`RESOLD`	`push.ticket.deleted.resold`
`DISTRIBUTION`	`push.ticket.deleted.distribution`
`THEFT_LOSS`	`push.ticket.deleted.theft_loss`
`BLACKLIST`	`push.ticket.deleted.blacklist`
`ONSITE_TROUBLESHOOTING`	`push.ticket.deleted.onsite_troubleshooting`	Dedicated to local TIXNGO deletions; never used for deletions coming from S‑360
`OTHER`	`push.ticket.deleted`

Deleted tickets can be visible from the More menu of the mobile app depending on the Application Settings if:

The corresponding screen are enabled (deleted-tickets-visibility, enable-resale-ticket-shop-s360)
The reason is selected in ticket.deleted.hidden-reasons

Tickets deleted with reasons RESALE_PENDING, RESALE_CANCELLED, RESOLD are anyway displayed in separate Resale screens.