S-360 Documentation

Page tree

Versions Compared

Old Version 83

changes.mady.by.user jbo

Saved on

compared with

New Version 84

changes.mady.by.user jbo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel3

Overview

While S-360 manages tickets sales & issuing, TIXNGO, as a Secure Mobile Ticket Delivery solution, maintain a track record of all actions performed on 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

Which products can be injected into TIXNGO?

TicketsDigital Privileges
  • Event / Performance
  • Match / Competition
  • Open Passes
  • Services
  • Memberships Cards

  • Season Tickets – Cards Only


Interface functions & data streams


FunctionObjectives Outcome in TIXNGOOutcome 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
  • Event is created (if does not exist yet)
  • Ticket exists in TIXNGO and its status is INJECTED
  • Ticket marked as PRINTED
  • Ticket marked as “Processed” by the function

Retrieve ticket status from TIXNGO
aka Feedback interface

Retrieve TIXNGO tickets details (status, wallet owner, ticket holder)

NA

  • No status change
  • Update the mobile ticket status, details and history

Push cancelled and invalidated tickets
aka Push Cancelled

Invalidate tickets in TIXNGO
  1. Ticket status updated to DELETION_PENDING (until deletion confirmed)
  2. Once confirmed, Ticket status updated to DELETED
  • No status change
  • Ticket marked as “Processed” by the function

Push controlled tickets
aka Push Controlled

Mark as Controlled tickets in TIXNGO

Ticket status updated to CONTROLLED

  • No status change
  • Ticket marked as “Processed” by the function
Digital Privileges (Memberships Cards, Season Tickets – Cards Only)

Inject digital privileges
aka Privileges injection

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
  • Privilege definition is created (if does not exist yet)
  • Privilege instance exists in TIXNGO and its status is INJECTED
  • Card marked as PRINTED
  • Card  marked as “Processed” by the function



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 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.

Info
titleImportant

Please do not set up different interfaces on the same organization, else the push cancelled tickets and push will not work.

For more detailed info, please refer to the specific site:

Children Display