Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 61 Next »

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

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.

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.









  • No labels