Share |

27.0 Ticket Validation System Requirements 

A Ticket Validation System may be entirely integrated into an On-Line Monitoring System or exist as an entirely separate entity. Payment by ticket printer as a method of credit redemption on an EGS is only permissible when the EGS is linked to an approved Ticket Validation System. Validation information shall be communicated from the system to the EGS using a secure Communication Protocol. This section concerns bi-directional Ticket Validation System specific requirements where a Ticket Validation System that is independent of an On-Line Monitoring System would also require the Security and Integrity standards previously outlined within this document, would also apply.

27.1 Loss of Communication
In the event there is a loss of communication between the EGS and the Ticket Validation System, an alternate method of payment must be provided either by the validation system possessing unique features (e.g., validity checking of ticket information in conjunction with a local Database storage) to identify duplicate tickets and prevent fraud by reprinting and redeeming a ticket that was previously issued by the EGS; or by use of an approved alternative method that will accomplish the same. Where EGS ticket generation is to be supported while not connected to the validation system, a ticket system must generate two different types of tickets at minimum. On-line and off-line types are denoted respectively by ticket generation either when the validation system and EGS are properly communicating or the validation system and EGS are not communicating properly. When a patron cashes out of an EGS that has lost Communication with the validation system, the EGS must lock up and, after reset, may print an off-line ticket or handpay receipt. The ticket or handpay receipt must be visually distinct from an on-line ticket either in format or content while still maintaining all information required.

27.2 Ticket Issuance
A ticket can be generated at an EGS through an internal document printer, at a player’s request, by redeeming all credits. Tickets that reflect partial credits may be issued automatically from an EGS. Additionally, cashier/change booth issuance is allowed if supported by the validation system.

27.3 Ticket Redemption
Tickets may be inserted in any EGS participating in the validation system providing that no credits are issued to the EGS prior to confirmation of ticket validity. The customer may also redeem a ticket at a validation terminal (i.e., cashier/change booth, Redemption Terminal or other approved methods.) All validation terminals shall be user and password-controlled with the exception of a Redemption Terminal that does not require human interaction. Where the Validation is to take place at a Cashier/Change Booth, the cashier shall:

(a) Scan the bar code via an optical reader or equivalent; or

(b) Input the ticket validation number manually; and

(c) May print a validation receipt, after the ticket is electronically validated, if applicable. The validation receipt, at a minimum, shall contain the following printed information:

i. Machine number;

ii. Validation number;

iii. Date and Time paid;

iv. Amount; and

v. Cashier/Change Booth identifier.

27.4 Invalid Ticket Notification
The Ticket Validation System must have the ability to identify duplicate tickets invalid tickets and notify the EGS to ‘Reject’ the ticket or advise the cashier that one of the following conditions exists:

(a) Ticket cannot be found on file (stale date, forgery, etc.);

(b) Ticket has already been paid; or

(c) Amount of ticket differs from amount on file (requirement can be met by display of ticket amount for confirmation by cashier during the redemption process).

27.5 Required Reports
The following reports shall be generated at a minimum and reconciled with all validated/redeemed tickets:

(a) Ticket Issuance Report;

(b) Ticket Redemption Report;

(c) Ticket Liability Report;

(d) Ticket Drop Variance Report;

(e) Transaction Detail Report must be available from the validation system that shows all tickets generated by an EGS and all tickets redeemed by the validation terminal or other EGS; and

(f) Cashier Report, which is to detail individual tickets, the sum of the tickets paid by Cashier/Change Booth or Redemption Terminal.

The requirements for ‘b’ & ‘d’ are waived where two-part tickets exist for the EGS , and where the first part is dispensed as an original ticket to the patron and the second part remains attached to the printer mechanism as a copy (on a continuous roll) in the EGS .

27.6 Security of Ticket Information
Once the validation information is stored in the Database, the data may not be altered in any way. The validation system Database must be encrypted or password-protected and should possess a non-alterable user audit trail to prevent unauthorized access. Further, the normal operation of any device that holds ticket information shall not have any options or methods that may compromise ticket information. Any device that holds ticket information in its memory shall not allow removing of the information unless it has first transferred that information to the Database or other secured component(s) of the validation system.