S-360 Documentation

Page tree

Versions Compared

Old Version 1

changes.mady.by.user jbo

Saved on

compared with

New Version 2

changes.mady.by.user jbo

Saved on

Key

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

TIXNGO Ticket Status

In TIXNGO, we support 18 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.

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 delivery: 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

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)

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 "cancelled/invalidated" status to TIXNGO and receiving feedback from TIXNGO)
  • DELETED (after successful blockchain deletion and feedback from TIXNGO)

What and how we synchronize ticket details ?

Each mode has a specific mapping.

Last update

Mapping Document

Change log

03 Apr 2023FIFASTX-2770_S360-TNG_Mapping_WIP.xlsx

Work in progress → Final version will be uploaded when developement will be completed.

07 Feb 2023

S360-TNG_Mapping_20230207.xlsx

Fixing nationality  Image AddedSTX-129714 DELIVERED

07 Oct 2022

S360-TNG_Mapping_20221007.xlsx

Lifecycle implementation