20.1 Wagering Account at POS
20.1.1 Wagering Accounts must use a method of authentication to access or transfer player funds or associated information such as player activity. This authentication requires a Wagering Ac- count identifier, as well as a player supplied authentication method, such as a PIN.
20.1.2 Wagering Accounts must have a unique and non-predictable identifier. Either the player must choose this identifier, or the system will assign it pseudo-randomly. This identifier may be associated with a player, or a specific player session.
20.1.3 At the time a Wagering Account is created, a player receipt must be issued with the following information, at a minimum:
20.1.4 There must be a method of identifying a player in the event that their account PIN is lost.
20.1.5 All Wagering Account activities including transactions, changes to the account and success- ful and unsuccessful logins must be tracked at the Backend System including Wagering Account number, location of activity and activity.
20.2 Vouchers and Coupons
20.2.1 Voucher and Coupon status during transactions and on-demand must be displayed on Player Terminals and Backend System. Once redeemed, they must not be redeemable again.
20.2.2 The Backend System must be equipped to capture and store all Cashless Wagering meters. The following meter information must be captured, as applicable:
20.2.3 The Backend System must have a mechanism in place to record all required meters, as specified above in Section 20.2.2 of this document, at the time a drop box is removed or on demand.
20.2.4 Vouchers and Coupons must contain the following information at a minimum:
20.2.5 In the event of a communication disruption, the Player Terminal may issue a single offline Voucher to clear player’s balance, which must be communicated to the Backend System im- mediately on reconnection, or lockup in hand-pay.
20.2.6 Validation numbers of unredeemed Vouchers must be appropriately masked when viewable through any display to prevent generation of counterfeit vouchers.
20.3 Reporting
20.3.1 Sufficient accounting information must be captured by the Backend System to allow for full reconciliation and audit of all Cashless Wagering transactions.
20.3.2 Reports must be available to provide information on all activities on electronic Wagering Ac- counts including purchases, Wagers and cash-outs:
20.3.3 Reports must be available to track information on all Voucher transactions, including: