...
While S-360 manages tickets sales & issuing, TIXNGO, as a Secure Mobile Ticket Delivery solution, is considered as an External Printing System.
Once injected into TIXNGO :
- Tickets are marked as PRINTED in S-360.
- Tickets can be assigned, transferred, post on resale, .... from TIXNGO
- TIXNGO will maintain a track record of all actions performed on the Mobile Tickets.
S-360 TIXNGO interface main role is to ensure that once issued and injected into TIXNGO, tickets (status & details) are aligned between S-360 & TIXNGO
...
| 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 |
|
|
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.
| Info | ||
|---|---|---|
| ||
Please do not set up different interfaces on the same organization, else the push cancelled tickets and push will not work. |
...
To learn more about the TIXNGO interfaces (functions, parameters, ...) :
| Child pages (Children Display) |
|---|
...