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 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 :
...
...
TIXNGO Ticket Status
...
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 ?
...
In the custom parameters, to enable the lifecycle mode, you can use TIXNGO_LIFECYCLE_MODE=lifecycle.
By default, if not specified, the history mode will be used.
...
| title | DEPRECATED |
|---|
DEPRECATED : History Mode
...
be used
...
- 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 Blockchain Status (history)
...
Printed
...
(after injection) INJECTED
No Action/Status as long as the user does not have a wallet
...
(after download) RECEIVED
Action/Status : Inject/Confirmed
...
(after assignment) RECEIVED 
Holder/Assignee fields are set
Action/Status : Inject/Confirmed
...
(after transfer initiated) TRANSFER_PENDING
Action/Status : Inject/Confirmed
...
.
...
(after ticket activation) ACTIVATED
No specific Action/Status
...
Controlled
→ ACS control
→ Ticket check (BO)
...
(after control BUT before feedback from TIXNGO) ACTIVATED
(after control and feedback from TIXNGO) CONTROLLED
No specific Action/Status
...
Invalidated
→ Reprint ticket
→ Post ticket on resale
...
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)
If the ticket was never sent to TIXNGO → NA
...
Cancelled
→ Cancel ticket (manually or by batch)
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)
...