31.0 Redemption Terminal (Kiosk) Standards 

Kiosks are only to be used for the purpose of accepting, validating and providing payment for tickets inserted. Kiosks may incorporate other functions that would not have any effect on the integrity of gaming, with the exception of Automated Teller Machine functionality. Kiosks must use a Communication Protocol that will not permit the Kiosk to write directly to the system Database and only process payments based on commands from the system. Redemption Kiosks shall meet the EGS Hardware Requirements for Security and Player Safety, as previously outlined.

31.1 Error Conditions
Kiosks must be capable of detecting and displaying the following Error Conditions. The Error Condition must illuminate the tower light or sound an audible alarm. This requirement may be substituted for a notification system that alerts staff of Error Conditions. The Kiosk shall be able to recover to the state it was in immediately prior to any interruption that occurred, including during payment. Error Conditions requiring Attendant intervention are denoted by ‘*’:

(a) Power loss or power reset;

(b) System and kiosk not communicating (this may be detected upon ticket insertion only)

(c) RAM error (critical memory)*;

(d) Low RAM battery (if battery external to the RAM itself used)*;

(e) Ticket voucher-in jam*;

(f) Door open (all external doors);

(g) Bill Acceptor stacker full (this condition should cause the Bill Acceptor to disable itself to no longer accept anything);

(h) Bill Acceptor door open;

(i) Bill Stacker door open or Bill Stacker removed; and

(j) Printer errors (If internal printer is supported)*.

If the Redemption Kiosk uses error codes instead of a text explanation of the Error Conditions, a description of error codes and their meanings must be affixed on the inside of the Redemption Kiosk.

If any of the above Error Conditions occur during the acceptance and/or escrowing of a ticket voucher, the ticket voucher must be returned to the patron without a status change on the Validation System or, once the Error Condition is cleared, proceed to pay the patron and have a status of ‘Redeemed’ on the system.

31.2 Maximum Redeemable Value
There shall be a maximum ticket value that can be paid by a kiosk or have available the ability to select the maximum amount.

31.3 Metering
Metering information is maintained in critical memory at the Redemption Kiosk. The Redemption Kiosk must maintain the following Meters, which can be by Denomination:

(a) A “Total In” Meter that accumulates the total value of all bills and ticket vouchers accepted by the device. Separate In meters shall report the value of all tickets redeemed and the value of all bills redeemed; and

(b) A “Total Out” Meter(s) for payments issued by the machine. Separate ‘Out Meters’ shall report the value of all tickets or other notes.

31.4 Clearing Meters
The Redemption Kiosk must not have a mechanism whereby an unauthorized user can cause the loss of stored accounting Meter information.

31.5 Required Logs
Logs must be maintained in critical memory or on a paper log (see NOTE, below within this section) housed within the Redemption Kiosk that consists of the following:
(a) Voucher In Event Log which must properly log the following information about the voucher redeemed:

i. Date/Time of redemption;

ii. Amount of voucher; and

iii. At least last 4-digits of validation number.

(b) The Redemption Kiosk must maintain at least 35 events in the “Voucher In” event log.

If the device utilizes a printer to record the information required within this section, the printer must be capable of monitoring any Printer Fault (i.e., ‘Printer Disconnected’, ‘Paper Jam’, ‘Out of Paper’, etc.)

31.6 Ticket Acceptance
Tickets may only be accepted when the Kiosk is communicating with the system. Tickets inserted into a kiosk must be rejected when the system link is down and Payment shall only be made when the ticket is ‘Stacked’ within the Bill Stacker.

31.7 Wireless Networks
This section shall address security precautions and minimum recommendations that govern Wireless Networks.

31.8 Wireless Ethernet Connections
Should a wireless Ethernet Communication solution be adopted, then additional security precautions must be taken. The current wireless Ethernet technology (Wi-Fi) is vulnerable and should not be considered secure. If Wi-Fi is chosen as the Communication method for your system, the following recommendations are to be considered minimum recommendations and not restrictions:

a) The wireless access point must be physically positioned in the building so that it is not easily accessible by unauthorized individuals.

b) Wireless Network traffic must be secured with additional encryption to compensate for the weaknesses in Wi-Fi.

i. The keys used to encrypt the Communication through the wireless Network must be stored in a secure location.

31.9 Security Considerations for WLAN used with a Wired LAN
The wired LAN (Local Area Network) must be isolated from the wireless (WLAN) Network through the layering of additional Network security methods.