18.1 General Requirements
18.1.1 The Backend System must require player interaction to call a bingo.
18.1.2 The Backend System must detect a failure or loss of communication with any participating Player Terminal during session Play and notify the Operator.
18.2 Bingo Cards
18.2.1 If there is a data corruption or modification in the Bingo Card database, the Backend Sys- tem must have a method to detect and notify the Operator of any discrepancy and mark the cards unplayable.
18.2.2 Any changes to, or removal of card Perms from the database must not impact the log of card faces from previously played session bingo Games.
18.2.3 The Backend System must have a secure and reliable method of validating called bingos for all bingo paper products. This validation requires manual Operator acceptance for payout of paper products.
18.2.4 The Backend System must track paper products inventory and sales for reconciliation of sales values and to match inventory values, when paper products are used in electronic Game. The system must reasonably ensure that sufficient information is provided to the Op- erator to identify missing paper products prior to a session starting.
18.2.5 If the Bingo Cards used are pulled from a Perm, the data storage mechanism of the Perm must have integrity check. If the Bingo Card is generated at the time of Play by using RNG, the RNG must satisfy requirements set out in 21.1.1 and 21.1.2 of this document.
18.3 Session Bingo Game
18.3.1 Session bingo Game results may be generated by either electronic or physical RNG, which must satisfy section 21.1 or 21.2 respectively.
18.3.2 The Backend System must provide functionality to recall a drawn ball. All instances of ball re-calls must be logged. Ball recalls must be communicated to all paper and electronic bingo players.
18.3.3 All Game results must be logged.
18.4 Single-Player Bingo Game
18.4.1 All Game results generated must adhere to section 21.1 of this document
18.4.2 If the Game uses traditional 5x5 Bingo Cards with a results set of 75 balls, the odds of achieving a pattern must be the same as session bingo unless otherwise communicated to the player.
18.4.3 The Game may allow player to re-select their Bingo Card face prior to retrieving Game results.
18.4.4 Paytables must be protected from modifications and must also have integrity check.
18.5 Flashboard Display
18.5.1 Flashboard display is required if the system supports paper Play.
18.5.2 Estimated Prizes advertised on the flashboard display must be disclosed immediately when modified.
18.5.3 Results must be displayed on both Player Terminals and flashboard displays in real time.
18.5.4 Flashboard display must contain all information required for paper players to participate in the Game. This includes:
- Called balls;
- Graphical representation of winning pattern;
- Prize of current Game;
- Game and session name;
- Ordinal number, if used;
- Pre-called balls for outstanding Games for which sales are open; and
- Any other non-standard information required for Play.
18.5.5 The Backend System must automatically detect any failure in the flashboard display, e.g. communication failure or any other that can be detected, and halt session Play until the fail- ure is resolved.
18.6 Prizing
18.6.1 Prize adjustments may only be performed through restricted means.
18.6.2 Any Prize adjustments made, or other changes to Prize structure must be logged sufficiently for audit purposes, including: user making the change, date/time and details on the change.
18.6.3 Session bingo Prizes must pay out according to the advertised Game rules.
18.6.4 Progressive Prize contributions and Ordinal balls must increment as designed and be accu- rately communicated.
18.6.5 The changes of Progressive pools and Ordinal ball values must be tracked by the Backend System to show the details of the change including: time of change, associated session, val- ue of contribution or increment change and when the value is reset to the default value.
18.6.6 The Backend System must provide functionality to either enable a “must-go” situation for Progressive Prizes to force the Prize to be paid out, or to transfer contributions to a new Prize pool. If used, this function must be logged in reports.
18.7 Reporting
18.7.1 Where the Backend System is used to track asset inventory, the following paper inventory information must be available in the reporting interface:
- Inventory delivered to the hall;
- Inventory assigned to cashiers or runners;
- Inventory returned by cashiers or runners;
- Inventory reported as damaged;
- Sold inventory;
- Inventory Price;
- Date/time of the above actions; and
- User responsible for initiating the above actions.
18.7.2 The following information must be available for each session played by the Backend System, including both electronic and paper sales for a minimum of 1 year:
- Card face information for all participating players;
- Ball call order including ball recalls;
- Winning card(s);
- User name of the caller;
- Prizes won;
- Sales; and
- Progressive Prize contributions.