This function retrieves information from TIXnGO about the ticket (status, holder) and stores it inside SecuTix.
With the lifecycle implementation, we aligned the statuses and the screens between TIXNGO and S-360 and synchronize the tickets from a "business" perspective
...
Batch size
Recommended value: 1000
TIXNGO Ticket
...
History mode (legacy behaviour)
- Possible Statuses (tixngo.legacyStatus) : INJECTED, RECEIVED, ACTIVATED, TRANSFER_PENDING, TRANSFERRED, CONTROLLED, DELETION_PENDING, DELETED
- Possible Actions : INJECT, TRANSFER, DELETE, BURN
- Possible States : PENDING, CONFIRMED, KO, DELETION_PENDING, DELETED, REGISTRATION_PENDING, CANCELLED, FAILED
Lifecycle mode (new behaviour)
...
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.
| Info | ||
|---|---|---|
| ||
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 | S360 Blockchain Status (lifecycle)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 → ACS control | (after control before feedback from TIXNGO) XYZ_ACTIVATED where XYZ is the activation method used (after control and feedback from TIXNGO) CONTROLLED |
Invalidated → Reprint ticket → Post ticket on resale | If the ticket was already existing in TIXNGO ...
If the ticket was never sent to TIXNGO → NA |
Cancelled → Cancel ticket (manually or by batch) | If the ticket was already existing in TIXNGO ...
If the ticket was never sent to TIXNGO → NA |
...
With the history mode (legacy behaviour), we synchronize the tickets from a "blockchain transaction" perspective
History mode (legacy behaviour)
- Possible Statuses (tixngo.legacyStatus) : INJECTED, RECEIVED, ACTIVATED, TRANSFER_PENDING, TRANSFERRED, CONTROLLED, DELETION_PENDING, DELETED
- Possible Actions : INJECT, TRANSFER, DELETE, BURN
- Possible States : PENDING, CONFIRMED, KO, DELETION_PENDING, DELETED, REGISTRATION_PENDING, CANCELLED, FAILED
| S360 Ticket Status | S360 Blockchain Status (history) |
|---|---|
| Not printed | NA |
Printed | (after injection) INJECTED |
(after download) RECEIVED | |
(after assignment) RECEIVED | |
(after transfer initiated) TRANSFER_PENDING | |
(after transfer cancelled by sender) RECEIVED ... or ... (after transfer rejected by receiver) RECEIVED | |
| (after transfer accepted) TRANSFERRED Action/Status : Transfer/Confirmed | |
(after ticket activation) ACTIVATED | |
Controlled → ACS control | (after control BUT before feedback from TIXNGO) ACTIVATED |
Invalidated → Reprint ticket → Post ticket on resale | If the ticket was already existing in TIXNGO ...
If the ticket was never sent to TIXNGO → NA |
Cancelled → Cancel ticket (manually or by batch) | If the ticket was already existing in TIXNGO ...
If the ticket was never sent to TIXNGO → NA |
