This section contains general Backend System requirements which apply to electronic bingo card and Ticket Games.
17.1.1 User input fields must be validated to prevent any security breaches.
17.1.2 Backend System must have ability to enable/disable Player Terminal.
17.1.3 cGaming System must not have hardcoded passwords.
17.1.4 Management, administration or configuration of the Backend System from Player Terminal must not be allowed.
17.1.5 Backend Systems must record and store complete Game events and accounting data.
17.1.6 Backend Systems must provide reports for complete inventory and status audit of activated Deals, sold and unsold Tickets, Bingo Cards etc. which are used in electronic Games.
17.1.7 The Backend System must at a minimum contain the following information in reports, capable of being generated on-demand, for specific time periods, and for specific activities:
- Cashier Transactions - Information on all cash transactions handled by the system, including: cash-in, cash-out, transaction location, time and user name of the cashier performing the transaction and invalid transactions;
- Game and player (Wagering Account) transactions – Any sales and wagering information must be tracked for full reconciliation including: terminal location of the sale, product details, cashless and currency flow, cost and Game result;
- Security Events – any information on access and attempted authentication including: component accessed, username, success or failure of authentication, time, any changes made; and
- Error Logs – All critical errors, such as terminal or system application crashes, failed software authentication and communication errors.