| Table of Contents | ||
|---|---|---|
|
Overview
Interface role
While S-360 handles ticket sales and issuing, TIXNGO, as a Secure Mobile Ticket Delivery solution, functions as an External Printing System. Once tickets are injected into TIXNGO:
- They are marked as PRINTED in S-360.
- They can be assigned, transferred, posted for resale, and more via TIXNGO.
- TIXNGO will keep a track record of all actions performed on the mobile tickets.
The primary role of the S-360 TIXNGO interface is to ensure that once tickets are issued and injected into TIXNGO, their status and details are synchronized between S-360 and TIXNGO.
Supported S-360 products
| Tickets | Digital Privileges |
|---|---|
|
|
Interface functions & data streams
| Function | Objectives | Outcome in TIXNGO | Outcome in S-360 |
|---|---|---|---|
Tickets (Event / Performance, Match / Competition, Open Passes, Services) | |||
| Tickets external printing aka Tickets injection | Create an Event (if does not exist yet) and add the designated NOT_PRINTED S-360 tickets into TIXNGO |
|
|
Retrieve ticket status from TIXNGO | Retrieve TIXNGO tickets details (status, wallet owner, ticket holder) | NA |
|
Push cancelled and invalidated tickets | Invalidate tickets in TIXNGO |
|
|
Push controlled tickets | Mark as Controlled tickets in TIXNGO | Ticket status updated to CONTROLLED |
|
| Digital Privileges (Memberships Cards, Season Tickets – Cards Only) | |||
Inject digital privileges | Create a Privilege Definition (if does not exist yet) and add the designated NOT_PRINTED S-360 membership and season cards into TIXNGO as Digital Privileges instance |
|
|
To learn more about the TIXNGO interfaces (functions, parameters, ...) :
| Children Display |
|---|
TIXnGO is the leading secure mobile wallet solution provided by the SecuTix company.
Please refer to this page for the functionalities of the product.
To set up product that can use this interface, please refer this page
The document describes the features and the setup steps of the interface between SecuTix 360 and TIXnGO
| Table of Contents |
|---|
Data streams
Ticket Injection: External printing. When executing this function, the ticket will pass to "printed" status on Secutix, and it will be injected on TIXnGO
Cancelled ticket: Push that has been cancelled in Secutix into TIXnGO. So the new status of the processed ticket will be cancelled on TIXnGO
Controlled ticket:
Global setup of the interface
As for SecuTix 360, the TixNGo system is perceived as an external printing system. Tickets injected into TIXnGO are considered as printed.
To set it up:
1.) In Organization/Tools/Interfaces create a new External Printing Interface of type "TIXnGO" or "TixnGO with ticket template" (If you want to use the Ticket Template Editor to custom the data send to TIXNGO TIXnGO Customization of the data injected by SecuTix)
2.) Fill in the API URL provided by TIXnGO in the URL field. It must end by organizer/tickets
3.) Fill in the username provided by TIXnGO (I guess the value does not matter)
4.) In the password field, fill in the API key provided by TIXnGO
5.) Inject some test tickets.
The field "Email notification...." allows you to receive emails when one of the asynchronous processes described below is failing.
Should we set up different interfaces for given organization to speed the things up?
No. Else the push cancelled tickets and push will not work.
Don't.
Custom parameters
...
This custom parameter is used for the Tickets external printing/ Push cancelled and validate tickets/ Push controlled tickets. To support larger batch sizes, split them into smaller calls to blockchain to send smaller batches, one after the other inside the same execution. The default split size is 50
Note: The TIXnGO side supported only 50 tickets/times, so that should be kept as default.
...
This custom parameter is used for the Retrieve tickets status from TIXnGO batch. To support larger batch sizes, split them into smaller calls to blockchain to retrieve smaller batches, one after the other inside the same execution. The default split size is 1000
Example: Batch size in the Retrieve tickets status from TIXnGO = 5000, batchSplitSize = 1000. It will split 5000 to 5 calls in the same execution with 1000 per call
...
This custom parameter is used for the Tickets external printing to allow injecting mobile tickets to the latest ticket holder contact or cultural contact based on the invalidation reason, i.e., reseating
Example: After injecting ticket into TnG for contact A (cultural contact) then contact A open mobile app and transfer the ticket to contact B (latest mobile owner). On the STX side, the operator reprinted that ticket with invalidation reason THEFT and reinject it into TnG, this ticket will reinject back to contact A. If there is no invalidation reason here, the new ticket will be reinjected back to contact B
Note: All the cancellation reasons are those which appear on the list of values in the BO [Institution > Initialisation > List of values > Ticket (Cancellation cause)]. With validation reason Theft , rESEATING will work too because the invalidation causes will be modified in order to remove the spaces and to be all set in upper cases
...
Both custom parameters are used for putting blockchain tickets into the resale platform and specified for Push cancelled and validate ticket batch. The purpose of those parameters is to update the invalidation reason to TnG after putting the ticket on the resale platform or tickets is resold.
Example: excludeTicketResale=true, overrideVisibilityFlagForInvalidationReason=RESALE_PENDING, RESOLD
After putting the ticket on the resale platform, the old ticket is invalidated and the validation reason will be updated into TnG side by the Push cancelled and validate ticket with invalidation set at overrideVisibilityFlagForInvalidationReason
For more information, please refer to the US STX-110559
...
overlaySpectatirDetailsWithLastOwner...
Only possible value lifecycle. Activates ticket status feature related to
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
To inject tickets to TIXNGO from S360 or by CSV with multilingual support
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Force/Skip Ticket numbers and tax numbers
To force ticket by ticket id :
To force ticket by tax number :
To skip ticket by ticket number id :
...