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.
| Note |
|---|
| In case of multi organization, the organization must be set up in the organization owing the inventory of the tickets (the organization where the catalog is defined) |
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 /wiki/spaces/CF/pages/40576543)
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.
| 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, ...) :
| Child pages (Children Display) |
|---|