S-360 Documentation

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Understanding Ticket Statuses

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

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

Mobile Tickets
S-360 TIXNGO
TICKET_IDticketId
BLOCKCHAIN_TICKET_STATUSticketStatusLog
TICKET_LAST_UPDATElastUpdateTimestamp
ACTIVATION_DATEactivation.date
ACTIVATION_TYPEactivation.method
ACTIVATION_PHONE_MODELactivation.device
ACTIVATION_DURATIONactivation.duration
ACTIVATION_BEACONactivation.beaconName
OWNER_EMAILspectatorDetails.email
OWNER_TITLEspectatorDetails.title
OWNER_FIRSTNAMEspectatorDetails.firstName
OWNER_LASTNAMEspectatorDetails.lastName
OWNER_PHONE_NUMBERspectatorDetails.phoneNumber
OWNER_ID_NUMBERspectatorDetails.idCardNumber
OWNER_BIRTH_DATEspectatorDetails.dateOfBirth
OWNER_COUNTRY_CODEspectatorDetails.nationality
(failover: spectatorDetails.residenceCountry)
OWNER_LANGUAGEspectatorDetails.language
OWNER_INFO1spectatorDetails.extraInfo1
OWNER_INFO2spectatorDetails.extraInfo2
OWNER_INFO3spectatorDetails.extraInfo3
OWNER_INFO4spectatorDetails.extraInfo4
ASSIGNEE_EMAILspectatorDetails.ticketHolder.identity.email
ASSIGNEE_FIRSTNAMEspectatorDetails.ticketHolder.identity.firstName
ASSIGNEE_LASTNAMEspectatorDetails.ticketHolder.identity.lastName
ASSIGNEE_PHONE_NUMBERspectatorDetails.ticketHolder.identity.phoneNumber
ASSIGNEE_ID_NUMBERspectatorDetails.ticketHolder.identity.idCardNumber
ASSIGNEE_BIRTH_DATEspectatorDetails.ticketHolder.identity.dateOfBirth
ASSIGNEE_LANGUAGENot mapped
ASSIGNEE_NATIONALITYspectatorDetails.ticketHolder.identity.nationality 
(failover: spectatorDetails.ticketHolder.identity.residenceCountry)
ASSIGNEE_INFO1spectatorDetails.ticketHolder.identity.extraInfo1
ASSIGNEE_INFO2spectatorDetails.ticketHolder.identity.extraInfo2
ASSIGNEE_INFO3spectatorDetails.ticketHolder.identity.extraInfo3
ASSIGNEE_INFO4spectatorDetails.ticketHolder.identity.extraInfo4


Mobile Tickets transactions
S-360 TIXNGO
TICKET_IDticketId
TRANSACTION_DATElifecycle[i].createdDate
BLOCKCHAIN_TICKET_STATUSlifecycle[i].status
INFOlifecycle[i].info
ADDITIONAL INFOlifecycle[i].additionalinfo
SENDER_EMAILMapping according to status
SENDER_PHONE_NUMBERMapping according to status. 
RECIPIENT_EMAILMapping according to status. 
RECIPIENT_PHONE_NUMBERMapping according to status. 
RECIPIENT_TITLEMapping according to status.
RECIPIENT_FIRSTNAMEMapping according to status.
RECIPIENT_LASTNAMEMapping according to status.
RECIPIENT_ID_NUMBERMapping according to status. 
RECIPIENT_BIRTH_DATEMapping according to status..
RECIPIENT_COUNTRY_CODEMapping according to status.
RECIPIENT_LANGUAGEMapping according to status.
RECIPIENT_INFO1Mapping according to status.
RECIPIENT_INFO2Mapping according to status.
RECIPIENT_INFO3Mapping according to status.
RECIPIENT_INFO4Mapping according to status.


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  STX-129714 DELIVERED

07 Oct 2022

S360-TNG_Mapping_20221007.xlsx

Lifecycle implementation
  • No labels