/
4.1 Which TIXNGO ticket data is synced back to S-360 ?

4.1 Which TIXNGO ticket data is synced back to S-360 ?

Jul 02, 2024

Understanding Ticket Statuses

In TIXNGO, we support different statuses to ensure that at any time (before, during, and after an event), an organizer is able to know where a ticket is and who is its owner.

S360 Ticket Status

TIXNGO Ticket Status

S360 Ticket Status

TIXNGO Ticket Status

Not printed

NA. The ticket does not exist in TIXNGO

Printed

  • (after injection) INJECTED

  • (after download) DOWNLOADED

  • (after assignment) ASSIGNED

  • (after transfer initiated) PENDING_TRANFER

  • (after transfer cancelled by sender) FAILURE_TRANSFER

  • (after transfer rejected by receiver) FAILURE_TRANSFER

  • (after transfer accepted) TRANSFERRED

  • (after ticket activation) XXX_ACTIVATED (OFFLINE_ACTIVATED, ONLINE_ACTIVATED, MANUAL_ACTIVATED, BT_ACTIVATED)

Controlled
External Access Control or S-360 Ticket Check

  • (after control before feedback from TIXNGO) XYZ_ACTIVATED where XYZ is the activation method used

  • (after control and feedback from TIXNGO) CONTROLLED

Invalidated
Ticket Invalidation,
Reprint from the back-office,
Post ticket on resale

Cancelled
Cancel ticket (manually or by batch)


If the ticket was never sent to TIXNGO → NA .

But if the ticket was already existing in TIXNGO ...

  • DELETION_PENDING (after sending the "invalidated status to TIXNGO and receiving feedback from TIXNGO)

  • DELETED (after successful blockchain deletion and feedback from TIXNGO)

Understanding Ticket details synchronization

Since the lifecycle introduction and the additional adjustments, the mapping is fixed and predictable, meaning that S-360 receives only what is necessary for its functioning and what is visible in the back-office screens.