Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Possible status : INJECTED, DOWNLOADED, ASSIGNED, CONTROLLED, PENDING_TRANSFER, FAILURE_TRANSFER, TRANSFERRED, BT_ACTIVATED, MANUAL_ACTIVATED, OFFLINE_ACTIVATED, ONLINE_ACTIVATED, DELETION_PENDING, DELETED, ACTIVATED, DEACTIVATED, DEFAULT, INVALID, PENDING, FAILURE

We can regroup these 18 statuses into 5 families :

  • Initial deivery: the ticket is inserted into TIXNGO and/or into the spectator's wallet.
  • Transfer: the ticket is moving from one wallet to another.
  • Activation: the ticket is activated by one of the supported methods allowing the display of the QR code in the app.
  • Control: the ticket has been used to enter event's premises.
  • Deletion: the ticket has been deleted and cannot be used by a spectator.
S360 Ticket Status

TIXNGO Ticket Status

Not printedNA. 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)

...