For the 80+ ticketing companies that have integrated with our service, we’ve received requests for the ability to validate specific ticket types stored in a single database on-the-fly. The difference between what they can currently do with CodeREADr and their request is ‘on-the-fly’. For our validation service type, if you want to validate a VIP pass, you would need a VIP service associated with a VIP database. You would need another service and database for early-bird attendees, voucher holders, parking passes, etc.
Now with sessions, instead of creating a different service and database for each type of ticket, you can create sessions to accomplish that. Currently, this only applies to online services deploying Direct Scan to URL (DSU) or Postback URL services. With those service types, the validation occurs on their servers. Now that we can submit both the ticket ID and the ticket type to their server, they will know which type to validate against.
For example, the session options could include:
- VIP Ticket
- Earlybird Ticket
- General Admission
The app user would select the option(s) to save for the session. You will see the options with the Ticket ID for every subsequent scan until you need to scan for another ticket type. They would then edit or clear the previously selected options and then choose another option(s).
Also, clients can use ‘Custom Validation’ to create their own scripts to run offline. Those scripts could validate the Ticket ID and selected session option(s) offline against a single database.