Managing limitation rules for wagering accounts

Abstract

A wagering game account management system and its operations are described herein. In some embodiments, the operations include assigning one or more money values to a graphical user interface control and linking the graphical user interface control to a credit account. The credit account is a third-party financial account from which a player account is authorized to borrow funds up to a credit limit. In some embodiments, the operations further include providing the graphical user interface control for presentation during a wagering game session associated with the player account.

Description

LIMITED COPYRIGHT WAIVER

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. Copyright 2008, WMS Gaming, Inc.

FIELD

Embodiments of the inventive subject matter relate generally to wagering game systems, and more particularly to managing and enforcing limitation rules for wagering accounts.

BACKGROUND

Wagering game machines, such as slot machines, video poker machines and the like, have been a cornerstone of the gaming industry for several years. Generally, the popularity of such machines depends on the likelihood (or perceived likelihood) of winning money at the machine and the intrinsic entertainment value of the machine relative to other available gaming options. Where the available gaming options include a number of competing wagering game machines and the expectation of winning at each machine is roughly the same (or believed to be the same), players are likely to be attracted to the most entertaining and exciting machines. Shrewd operators consequently strive to employ the most entertaining and exciting machines, features, and enhancements available because such machines attract frequent play and hence increase profitability to the operator. Therefore, there is a continuing need for wagering game machine manufacturers to continuously develop new games and gaming enhancements that will attract frequent play.

BRIEF DESCRIPTION OF THE FIGURES

The present invention is illustrated by way of example and not limitation in the Figures of the accompanying drawings in which:

FIG. 1 is a block diagram illustrating account transactions, according to example embodiments of the invention;

FIG. 2 is a block diagram illustrating a wagering game machine architecture, according to example embodiments of the invention;

FIG. 3 is a block diagram illustrating a wagering game network 300, according to example embodiments of the invention;

FIG. 4 is a flow diagram illustrating operations for facilitating account transactions on a wagering game machine through a user interface, according to example embodiments of the invention;

FIG. 5A is a block diagram illustrating a graphical user interface through which players can request account transactions from a wagering game machine, according to example embodiments of the invention;

FIG. 5B is a block diagram illustrating account information in a wagering game machine's graphical user interface, according to example embodiments of the invention;

FIG. 6 is a flow diagram illustrating operations for processing account transactions made at a wagering game machine, according to example embodiments of the invention;

FIG. 7 is a flow diagram illustrating operations for presenting an account rule interface, according to example embodiments of the invention;

FIG. 8 is a block diagram illustrating an account rules interface, according to example embodiments of the invention;

FIG. 9 is a block diagram illustrating an interface for configuring account rules, according to example embodiments of the invention;

FIG. 10 is a flow diagram illustrating operations for processing and storing account rules, according to example embodiments of the invention;

FIG. 11 is a flow diagram illustrating operations for enforcing account rules in a wagering game system, according to example embodiments of the invention;

FIG. 12 is a perspective view of a wagering game machine, according to example embodiments of the invention;

FIG. 13 is an illustration of managing account transactions and determining use limitations, according to some embodiments;

FIG. 14 is an illustration of managing use limitations in connection with credit accounts, according to some embodiments;

FIG. 15 is a flow diagram 1500 illustrating determining limitations on credit accounts for augmenting a wagering game session account, according to some embodiments; and

FIG. 16 is a flow diagram 1600 illustrating controlling use limitations, according to some embodiments.

DESCRIPTION OF THE EMBODIMENTS

This description of the embodiments is divided into six sections. The first section provides an introduction to embodiments of the invention, while the second section describes wagering game machine architectures and wagering game networks. The third section describes interfaces and operations of some embodiments and the fourth section describes example wagering game machines in more detail. The fifth section describes some additional embodiments and the sixth section presents some general comments.

Introduction

This section provides an introduction to some embodiments of the invention.

Wagering game machines typically offer a limited number of ways for players to provide monetary value for use in wagering games. Some wagering game machines allow players to insert cash and cashless vouchers or to draw from casino accounts. However, wagering game machines typically do not offer many other ways to procure funds. As a result, when players run out of cash, cashless vouchers, and/or casino account funds, they often leave the casino floor to acquire additional funds. For example, players may go to automated teller machines, banks, or other institutions from which they can procure funds. Some embodiments of the invention enable players to acquire funds from a variety of sources without leaving a wagering game machine. Additionally, some embodiments enable players to specify conditions under which various account transactions will take place. For example, players can create account rules that automatically replenish depleted accounts, limit losses, donate a portion of winnings to charity, etc. The discussion of FIG. 1 describes some of these embodiments in more detail.

FIG. 1 is a block diagram illustrating account transactions, according to example embodiments of the invention. In FIG. 1, a wagering game machine 102 is connected to an account controller 104, which is connected to a financial institution computer 106. The wagering game machine 102 provides a graphical user interface 108 through which players request account transactions and create account rules. The account server 104 facilitates the account transactions and enforces the account rules, while the financial institution computer 106 also facilitates account transactions.

FIG. 1 shows two transactions. In the first transaction (see “1^ST” in FIG. 1) a player (not shown) uses the interface 114 to request transfer of $500 from a checking account 114 to a game session account 110. After the wagering game machine 102 receives the player's request, the machine 102 notifies the account controller 104 about the request. As a result, the account controller 104 contacts the financial institution computer 106, which transfers $500 from the player's checking account 114 to the player's game session account 110. Funds in the game session account 110 appear on the wagering game machine's credit meter 118 and are available for use in wagering games presented on the wagering game machine 102.

In the second transaction (see “2^ND” in FIG. 1), the player configures an account rule in the user interface 108. The account rule prompts transfer of $20 from the player's game session account 110 to his §529 account 116 for every $100 won playing wagering games. For information about §529 accounts, see section 529 of the United States Code, which governs Qualified State Tuition Programs. The wagering game machine 102 notifies the account controller 104 about the account rule. The wagering game machine 102 also notifies the account controller 104 whenever the player wins money playing wagering games. When the player's winnings reach $100, the account controller 104 transfers $20 from the game session account 110 to the §529 account 116. The account controller 104 can support other account rules. In some embodiments, account rules can transfer a percentage of winnings from the game session account 110 to the §529 account 116. For example, if a player win ten cents in a single game, twenty percent (two cents) is transferred into the §529 account 116.

Although FIG. 1 describes some embodiments, the following sections describe many other features and embodiments.

Example Operating Environment

This section describes an example operating environment and provides structural aspects of some embodiments. This section includes discussion about wagering game machine architectures and wagering game networks.

Wagering Game Machine Architecture

FIG. 2 is a block diagram illustrating a wagering game machine architecture, according to example embodiments of the invention. As shown in FIG. 2, the wagering game machine architecture 200 includes a wagering game machine cabinet 206, which includes a central processing unit (CPU) 226 connected to main memory 228. The CPU 226 can include any suitable processor, such as an Intel® Pentium III processor, Intel® Core 2 Duo processor, AMD Opteron™ processor, UltraSPARC processor, etc. The main memory 228 includes a wagering game unit 232 and an account manager 236. In some embodiments, the wagering game unit 232 can present wagering games, such as video poker, video black jack, video slots, video lottery, etc., in whole or part. In some embodiments, the account manager 236 provides a user interface through which players can request account transactions and configure account rules. For example, players can request funds transfers between various accounts, such as game session accounts, checking accounts, savings accounts, §529 accounts, charity accounts, etc. The account rules can cause transfers and other transactions to occur when specific conditions are met. For example, account rules can initiate funds transfers when players wager specific amounts, win specific amounts, play a specific number of wagering games, etc.

The CPU 226 is also connected to an input/output (I/O) bus 222, which can include any suitable bus technologies, such as an AGTL+frontside bus and a PCI backside bus. The I/O bus 222 is connected to a payout mechanism 208, primary display 210, secondary display 212, value input device 214, player input device 216, information reader 218, and storage unit 230. The player input device 216 can include the value input device 214 to the extent the player input device 216 is used to place wagers. The I/O bus 222 is also connected to an external system interface 224, which is connected to external systems 204 (e.g., wagering game networks).

In one embodiment, the wagering game machine 206 can include additional peripheral devices and/or more than one of each component shown in FIG. 2. For example, in one embodiment, the wagering game machine 206 can include multiple external system interfaces 224 and/or multiple CPUs 226. In one embodiment, any of the components can be integrated or subdivided.

Any component of the architecture 200 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein. Machine-readable media includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a wagering game machine, computer, etc.). For example, tangible machine-readable media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory machines, etc. Machine-readable media also includes any media suitable for transmitting software over a network.

While FIG. 2 describes example embodiments of a wagering game machine architecture, FIG. 3 shows how a plurality of wagering game machines can be connected in a wagering game network.

Wagering Game Network

FIG. 3 is a block diagram illustrating a wagering game network 300, according to example embodiments of the invention. As shown in FIG. 3, the wagering game network 300 includes a plurality of casinos 312 connected to a communications network 314.

Each of the plurality of casinos 312 includes a local area network 316, which may include a wireless access point 304, wagering game machines 302, and a wagering game server 306 that can serve wagering games over the local area network 316. The wagering game server 306 includes an account controller 318, which can facilitate account transactions and enforce account rules. The account controller 318 can communicate with other network components, such as the financial institution computer 324, when enforcing account rules and processing transactions. Also, the account controller 318 can record, modify, and use account information in the account store 320 and rule store 322. In some embodiments, the account controller 318, account store 320, and the rule store 322 can be located outside the casino 312.

The local area network 316 includes wireless communication links 310 and wired communication links 308. The wired and wireless communication links can employ any suitable connection technology, such as Bluetooth, 802.11, Ethernet, public switched telephone networks, SONET, USB, arcnet, current loop, etc. In one embodiment, the wagering game server 306 can serve wagering games and/or distribute content to devices located in other casinos 312 or at other locations on the communications network 314.

Any of the wagering game network components (e.g., the wagering game machines 302) can include hardware and machine-readable media including instructions for performing the operations described herein.

The wagering game machines 302 described herein can take any suitable form, such as floor standing models, handheld mobile units, bartop models, workstation-type console models, etc. Further, the wagering game machines 302 can be primarily dedicated for use in conducting wagering games, or can include non-dedicated devices, such as mobile phones, personal digital assistants, personal computers, etc. In one embodiment, the wagering game network 300 can include other network devices, such as accounting servers, wide area progressive servers, player tracking servers, and/or other devices suitable for use in connection with embodiments of the invention.

In various embodiments, wagering game machines 302 and wagering game servers 306 work together such that a wagering game machine 302 may be operated as a thin, thick, or intermediate client. For example, one or more elements of game play may be controlled by the wagering game machine 302 (client) or the wagering game server 306 (server). Game play elements may include executable game code, lookup tables, configuration files, game outcome, audio or visual representations of the game, game assets or the like. In a thin-client example, the wagering game server 306 may perform functions such as determining game outcome or managing assets, while the wagering game machine 302 may be used merely to present the graphical representation of such outcome or asset modification to the user (e.g., player). In a thick-client example, game outcome may be determined locally (e.g., at the wagering game machine 302) and then communicated to the wagering game server 306 for recording or managing a player's account.

Similarly, functionality not directly related to game play may be controlled by the wagering game machine 302 (client) or the wagering game server 306 (server) in embodiments. For example, account transactions and account rules may be managed centrally (e.g., by the wagering game server 306) or locally (e.g., by the wagering game machine 302). Other functionality not directly related to game play may include power management, presentation of advertising, software or firmware updates, system quality or security checks, etc.

Operations and Interfaces

This section describes operations and interfaces associated with some embodiments of the invention. In the discussion below, the flow diagrams will be described with reference to the block diagrams presented above. In certain embodiments, the operations are performed by executing instructions residing on machine-readable media (e.g., software), while in other embodiments, the operations are performed by hardware and/or other logic (e.g., firmware). In some embodiments, the operations are performed in series, while in other embodiments, one or more of the operations can be performed in parallel. Furthermore, the discussion below describes communications between wagering game network components. In some embodiments, the communications can include HyperText Transport Protocol (HTTP) requests for Hypertext Markup Language (HTML) documents. However, in other embodiments, the communications can be formatted according to different communication protocols.

The section will discuss FIGS. 4-11. FIGS. 4-6 will describe operations and interfaces for performing account transactions in response to player input. The discussion of FIGS. 7-11 will describe operations and interfaces for configuring account rules and performing account transactions based on the account rules.

Account Transactions

FIG. 4 is a flow diagram illustrating operations for facilitating account transactions on a wagering game machine through a user interface, according to example embodiments of the invention. The flow diagram 400 will be described with reference to the FIG. 3's wagering game network and FIG. 2's wagering game architecture. The flow begins at block 402.

At block 402, a wagering game machine 302 detects a player identifier. The wagering game machine 302 may detect the player identifier as a result of a player swiping a player account card, manually entering the identifier, or providing some other device that indicates the player identifier (e.g., an RFID tag). The flow continues at block 404.

At block 404, the wagering game machine 302 receives a list of wagering game accounts and other accounts associated with the player identifier. In some embodiments, the wagering game machine's account manager 236 requests and receives the list from the account controller 318. The flow continues at block 406.

At block 406, the wagering game machine 302 presents a graphical representation of the wagering game accounts and/or other accounts enumerated in the list. For example, the wagering game machine's account manager 236 presents, on the primary display 210, a user interface including graphics that represent financial accounts associated with the player identifier. FIG. 5A shows one such user interface.

FIG. 5A is a block diagram illustrating a graphical user interface through which players can request account transactions from a wagering game machine, according to example embodiments of the invention. In FIG. 5A, the graphical user interface 500 appears on a wagering game machine's touchscreen 502. As shown, the user interface 500 includes graphics representing accounts associated with a player identifier. The graphics include a game session account icon 504, savings account icon 506, casino account icon 508, §529 account icon 510, and money market account icon 512. The GUI 500 can show icons for any number of financial accounts. The accounts can include a game session account, casino debit/credit accounts, checking accounts, savings accounts, educational savings accounts (e.g., a §529 account), charity accounts (e.g., accounts that aid responsible gaming programs), holiday savings accounts, etc. According to embodiments, players can request account transactions by interacting with the icons.

Referring back to FIG. 4, the flow continues at block 408.

At block 408, the wagering game machine 302 detects a request for information about the wagering game account and/or other accounts. For example, the account manager 236 detects that a player has activated an icon in the user interface. The flow continues at block 410.

At block 410, the wagering game machine 302 receives account information associated with the account access request. The account information can include an account balance, transaction options associated with the account, and other information related to the account. In some embodiments, the account manager 236 requests and receives the account information from the account controller 318. Flow continues at block 412.

At block 412, the wagering game machine presents a graphical representation of the account information. To illustrate this concept, FIG. 5B shows how some embodiments can present account information including transaction options in a GUI.

FIG. 5B is a block diagram illustrating account information in a wagering game machine's graphical user interface, according to example embodiments of the invention. Players can activate the account icons by pressing the touchscreen 502. After an account icon is activated, the interface 500 presents additional account transaction options, which are represented by additional icons. In FIG. 5B, the player 518 has activated the savings account icon 506. As a result, the interface 500 has presented a savings account balance 520 and currency icons 514, which allow the player 518 to transfer different denominations between a savings account and other accounts. As shown, the player 518 is dragging a $20 currency icon 516 into the game session account icon 504. This drag-and-drop operation constitutes a request to transfer $20 from the player's savings account into the player's game session account. The GUI 500 supports similar drag-and-drop operations to request other transfers.

Referring back to FIG. 4, the flow continues at block 414.

At block 414, the wagering game machine 302 detects a transaction associated with the account options. For example, the account manager 236 detects a drag-and-drop operation that signifies an account transaction request. The drag-and-drop operations can indicate all parameters needed to request an account transaction. For example, drag-and-drop operations can indicate a transaction type, source account, destination account, currency amount, etc. The flow continues at block 416.

At block 416, the wagering game machine 302 transmits an indication of the transaction request, so the wagering game account and/or other accounts can be adjusted. For example, the account unit 236 transmits, to the account controller 318, an indication of the transactions that the player requested via the user interface. From block 416, the flow ends.

Thus far, this section has described account operations typically performed by wagering game machines. This section will continue with a discussion about account operations that are typically performed by account controllers.

FIG. 6 is a flow diagram illustrating operations for processing account transactions made at a wagering game machine, according to example embodiments of the invention. The flow 600 describes operations by which an account controller transmits information to wagering game machines. In some embodiments, the wagering game machines include logic for presenting the information (e.g., see discussion of FIG. 4). In other embodiments (e.g., where the wagering game machine includes a thin client) the account controller can control presentation of the information on the wagering game machines. The flow 600 begins at block 602.

At block 602, the account controller 318 receives (from a wagering game machine 302) a request for a list of wagering game accounts and other financial accounts associated with a player. The flow continues at block 604.

At block 604, the account controller 318 transmits the account list to the wagering game machine 302. As noted above, in some embodiments, the account controller 318 may control presentation of the account list on the wagering game machine 302. The flow continues at block 606.

At block 606, the account controller 318 receives a request for information about the wagering game account and other accounts. For example, the request may ask for account balances, transaction options, information about recent transactions, etc. The flow continues at block 608.

At block 608, the account controller 318 transmits the account information to the wagering game machine 302. The flow continues at block 610.

At block 610, the account controller 318 receives an account transaction request from the wagering game machine 302. For example, the account controller 318 receives a request to transfer funds from the player's savings account to the player's game session account. The flow continues at block 612.

At block 612, the account controller 318 adjusts the accounts based on the transaction request. For example, the account controller 318 instructs the financial institution computer 324 to deliver funds from a savings account to a game session account. In some embodiments, the account controller 318 does not transfer funds directly into game session accounts. Instead, the account controller 318 deposits funds into other wagering game accounts. Later, the account controller 318 can transfer funds from the wagering game accounts to game session accounts, if needed. The flow continues at block 614.

At block 614, the account controller 318 provides account information indicating the results of the requested transactions. For example, the account controller 318 notifies the player that funds have been transferred between the player's savings account and game session account. The account controller 318 can notify the player by sending a message to the wagering game machine 302. In some embodiments, the wagering game machine 302 will update its credit meter or other related balances accordingly. From block 614, the flow ends.

Account Rules

This section continues with a discussion of account rules. Some embodiments enable players to submit rules that automatically initiate account transactions when certain conditions are met. In some embodiments, the account rules specify account transactions, source and destination accounts, amounts, and trigger conditions. The account transactions can include transfers, deposits, withdrawals credits, debits, etc. When appropriate, source and destination accounts are identified (e.g., for transfers). Trigger conditions indicate when rules should be enforced. Trigger conditions can relate to time, account balances, wagering game results, wagers placed, and any other statistic associated with wagering game accounts, other financial accounts, and wagering games.

In some embodiments, players can use account rules to limit losses. For example, a player can create account rules that limit how much money can be transferred from a checking account into a game session account. Alternatively, players can move a portion of each winning jackpot from a game session account into savings account, where the savings account does not support wagering-game-related withdrawals. Players can also create account rules that transfer percentages of winnings to fund savings plans, charities, and other programs (e.g., responsible gambling programs). Furthermore, in some embodiments, players can create account rules that, at the conclusion of a gaming session, automatically transfer the entire game session account balance to another account, such as a casino debit account, checking account, or the like. As a result, embodiments eliminate the need for wagering game machines to return cash or cashless vouchers at the end of gaming sessions.

The following discussion will describe account rules in more details. In particular, the discussion of FIG. 7 will describe operations for presenting an account rule interface, while the discussion of FIGS. 8 & 9 will describe account rule interfaces. The discussion of FIGS. 10 & 11 will cover operations for creating and enforcing account rules.

FIG. 7 is a flow diagram illustrating operations for presenting an account rule interface, according to example embodiments of the invention. The flow 700 begins at block 702.

At block 702, a wagering game machine 302 presents an interface through which players can view and configure account rules. In some embodiments, the account manager 236 and/or other components create the account rule interface and populate it with account information received from the account controller 318. In other embodiments, the machine 302 renders the account interface in a web browser, using information received from the account controller 318 or other network devices. FIG. 8 shows one embodiment of an account rules interface.

FIG. 8 is a block diagram illustrating an account rules interface, according to example embodiments of the invention. In FIG. 8, the account rules interface 802 shows account rules currently affecting a player's financial accounts. The account rules interface 802 is divided into rows, where the rows show parameters for each account rule. The parameters for each account rule (shown in row 806) include “ACTION”, “AMOUNT”, “SOURCE ACCOUNT”, “DESTINATION ACCOUNT”, and “TRIGGER”. For example, the row 808 shows an account rule that transfers $200 from the player's checking account to the player's casino account every day at 12:00 am. Another rule, shown in row 812, transfers $100 from the player's casino account to the player's money market account when the casino account is greater than $200. In addition to showing the account rules, the account rules interface 802 includes a button 804 that can bring-up an interface for adding new rules. Although FIG. 8 shows an account rules interface in which players select from a predetermined parameter values, other embodiments enable players to create account rules by entering text (i.e., without a predetermined parameters) or by any other suitable method.

Referring back to FIG. 7, the flow continues at block 704.

At block 704, the wagering game machine 302 detects a change to the account rules. For example, the wagering game machine 302 detects that a player has attempted to create new rules or modify existing rules. In some embodiments, players can create and modify rules as follows. In the embodiment of FIG. 8, players can modify existing rules by activating a particular row in the interface 802 or by activating the button 804. After the player activates a row or the button 804, the wagering game machine 302 brings-up an interface for creating and modifying account rules. FIG. 9 shows one such interface.

FIG. 9 is a block diagram illustrating an interface for creating and modifying account rules, according to example embodiments of the invention. In FIG. 9, the account rules interface 902 includes drop-down menus for configuring account rule parameters. In particular, the interface 902 includes an ACTION menu 904, AMOUNT menu 906, SOURCE ACCOUNT menu 908, DESTINATION ACCOUNT menu 910, and a TRIGGER menu 912. Players can configure account rule parameters by selecting values from the menus 904-912. In some embodiments, when an existing rule is being modified, the menus 904-912 show the current parameter values.

Referring back to FIG. 7, the flow continues at block 706.

At block 706, the wagering game machine 302 submits the change to the account rules. Referring to FIG. 9, after a player has selected account rule parameters in the menus 904-912, the player can press the button 914 to submit the account rule for inclusion in the player's rule set. In some embodiments, the wagering game machine 302 submits the change by transmitting an indication of the change to the account controller 318. From block 706, the flow ends.

Although wagering game machines can perform the operations of the flow 700, in some embodiments, other devices perform those operations. For example, in a casino, players can use the kiosk 326 to view, create, and modify their account rules. From outside the casino, players can view, create, and modify account rules using the workstation 328, which in some embodiments can communicate with the account controller 318 over the world wide wed and/or the Internet. Account controllers can also play a role in the process with which players view, create, and modify account rules. This section continues with a discussion about how account servers can interact with a wagering game machine, kiosks, and workstations to process and store account rules.

FIG. 10 is a flow diagram illustrating operations for processing and storing account rules, according to example embodiments of the invention. The flow diagram 1000 begins at block 1002.

At block 1002, the account controller 318 detects a request for account rule information. In one embodiment, the account controller 318 receives the request from a wagering game machine 302 that is presenting the account rules interface 802. The account rule information can include account rules associated with a player. The flow continues at block 1004.

At block 1004, the account controller 318 transmits the account rule information to the requester (e.g., a wagering game machine 302). The account rule information can be in a form suitable for populating an account rules interface (e.g., see FIG. 8). The flow continues at block 1006.

At block 1006, the account controller 318 detects a modification to the account rules associated with a player identifier. In some embodiments, the account controller 318 receives, from a wagering game machine 302, a request to modify account rules associated with a player. The request can enumerate account rule parameters for a new account rule or for an existing rule. The flow continues at block 1008.

At block 1008, the account controller 318 revises the account rules accordingly. For example, the account controller 318 modifies a player's account rules using the rule parameters received at block 1006. In some embodiments, the account controller 318 notifies the player that the account rules have been modified successfully or that there was an error updating the account rules. From block 1008, the flow ends.

This section continues with a discussion about operations for enforcing the account rules.

FIG. 11 is a flow diagram illustrating operations for enforcing account rules in a wagering game system, according to example embodiments of the invention. The flow 1100 begins at block 1102.

At block 1102, the account controller 318 determines that a rule associated with a wagering game account should be enforced. As noted above, account rules can be associated with trigger condition. For example, winning jackpots, placing wagers, playing certain games, account balances, time of day, total amount of wagers made, etc. can trigger account rules to perform financial transactions. In some embodiments, the wagering game machines 302 notifies the account controller 318 about any information relevant to a player's account rules. For example, wagering game machines 302 can notify the account controller 318 when a player wins a jackpot, makes a wager, plays a game, begins a game session, ends a game session, etc. In response, the account controller 318 can determine whether any account rules' trigger conditions have been satisfied. In other embodiments, the wagering game machines 302 can acquire a list of account rules and notify the account controller 318 only when a trigger condition has been satisfied.

In some embodiments, account rules are not associated with wagering game events. For example, account rules can be related to time, account balances, account transactions, etc. Thus, the account controller 318 can use time, account balances, account transactions, and other non-event-related information to determine that an account rules should be enforced. The flow continues at block 1104.

At block 1104, the account controller 318 performs transactions specified in the account rules that are being enforced. For example, if an account rule specifies a transfer of funds, the account controller 318 transfers funds between accounts. As another example, if the account rule specifies that an account is to be locked, the account controller 318 locks the account. As yet another example, if the account rule specifies that certain transactions are prohibited (e.g., withdrawals from a retirement account), the account controller 318 marks the account as deposit only. The account controller 318 may enforce some account rules with assistance from the financial institution computer 324. The flow continues at block 1106.

At block 1106, the account controller 318 provides an indication of the financial transactions. In some embodiments, the account controller 318 can transmit a transaction statement for display on the wagering game machine 302 at which the player is present (e.g., in an account interface). Alternatively, the account controller 318 can notify the player via email, instant message, telephone message, etc. From block 1106, the flow ends.

Example Wagering Game Machines

FIG. 12 is a perspective view of a wagering game machine, according to example embodiments of the invention. Referring to FIG. 12, a wagering game machine 1200 is used in gaming establishments, such as casinos. According to embodiments, the wagering game machine 1200 can be any type of wagering game machine and can have varying structures and methods of operation. For example, the wagering game machine 1200 can be an electromechanical wagering game machine configured to play mechanical slots, or it can be an electronic wagering game machine configured to play video casino games, such as blackjack, slots, keno, poker, blackjack, roulette, etc.

The wagering game machine 1200 comprises a housing 1212 and includes input devices, including value input devices 1218 and a player input device 1224. For output, the wagering game machine 1200 includes a primary display 1214 for displaying information about a basic wagering game. The primary display 1214 can also display information about a bonus wagering game and a progressive wagering game. The wagering game machine 1200 also includes a secondary display 1216 for displaying wagering game events, wagering game outcomes, and/or signage information. While some components of the wagering game machine 1200 are described herein, numerous other elements can exist and can be used in any number or combination to create varying forms of the wagering game machine 1200.

The value input devices 1218 can take any suitable form and can be located on the front of the housing 1212. The value input devices 1218 can receive currency and/or credits inserted by a player. The value input devices 1218 can include coin acceptors for receiving coin currency and bill acceptors for receiving paper currency. Furthermore, the value input devices 1218 can include ticket readers or barcode scanners for reading information stored on vouchers, cards, or other tangible portable storage devices. The vouchers or cards can authorize access to central accounts, which can transfer money to the wagering game machine 1200.

The player input device 1224 comprises a plurality of push buttons on a button panel 1226 for operating the wagering game machine 1200. In addition, or alternatively, the player input device 1224 can comprise a touch screen 1228 mounted over the primary display 1214 and/or secondary display 1216.

The various components of the wagering game machine 1200 can be connected directly to, or contained within, the housing 1212. Alternatively, some of the wagering game machine's components can be located outside of the housing 1212, while being communicatively coupled with the wagering game machine 1200 using any suitable wired or wireless communication technology.

The operation of the basic wagering game can be displayed to the player on the primary display 1214. The primary display 1214 can also display a bonus game associated with the basic wagering game. The primary display 1214 can include a cathode ray tube (CRT), a high resolution liquid crystal display (LCD), a plasma display, light emitting diodes (LEDs), or any other type of display suitable for use in the wagering game machine 1200. Alternatively, the primary display 1214 can include a number of mechanical reels to display the outcome. In FIG. 12, the wagering game machine 1200 is an “upright” version in which the primary display 1214 is oriented vertically relative to the player. Alternatively, the wagering game machine can be a “slant-top” version in which the primary display 1214 is slanted at about a thirty-degree angle toward the player of the wagering game machine 1200. In yet another embodiment, the wagering game machine 1200 can exhibit any suitable form factor, such as a free standing model, bartop model, mobile handheld model, or workstation console model.

A player begins playing a basic wagering game by making a wager via the value input device 1218. The player can initiate play by using the player input device's buttons or touch screen 1228. The basic game can include arranging a plurality of symbols along a payline 1232, which indicates one or more outcomes of the basic game. Such outcomes can be randomly selected in response to player input. At least one of the outcomes, which can include any variation or combination of symbols, can trigger a bonus game.

In some embodiments, the wagering game machine 1200 can also include an information reader 1252, which can include a card reader, ticket reader, bar code scanner, RFID transceiver, or computer readable storage medium interface. In some embodiments, the information reader 1252 can be used to award complimentary services, restore game assets, track player habits, etc.

Additional Embodiments

FIG. 13 is an illustration of managing account transactions and determining use limitations, according to some embodiments. In FIG. 13, a wagering game machine 1302 is connected to an account controller 1304, which is connected to a financial institution computer 1306 and a jurisdictional authority computer 1324. The wagering game machine 1302 provides a graphical user interface (GUI) 1308 through which players request account transactions, create account rules, etc. The graphical user interface 1308 includes a control button 1328 that is preconfigured to access player account settings 1308. The player account settings 1308 can include information about a financial account, such as a credit account 1314, a checking account, a savings account, etc., that the account controller 1314 can use to quickly, and electronically, augment a balance on a wagering game session account 1310. Herein, the procedure for quickly augmenting funds from a financial account (e.g., a credit account), to a wagering game account (e.g., a wagering game session account), can be referred to as a “quick wagering game account augmentation” (“Quick Add”) procedure or “Quick Add” transaction. A mechanism (e.g., a button, a trigger, etc.) for initiating a Quick Add procedure, such as the control button 1328, can also be referred to herein as a “Quick Add” mechanism (e.g., the control button 1328 may be referred to as a Quick Add button 1328). The account controller 1304 can detect when the Quick Add button 1328 is activated by a player (not shown), obtain information from the player account settings 1308, check for limitations on the use of the credit account, and make decisions based on the limitations. The limitations are restrictions and limits on the use of the credit account 1314 that can help the player to responsibly utilize the credit account 1314 for wagering game purposes. For example, the account controller 1304 can look to limitation rules from various rules sources (e.g., from authority limitation rules 1332, from wagering game session account limitation rules 1322, from credit account limitation rules 1342, and from self-imposed limitations stored in the player account rules 1312). Based on the limitations stored within the rules sources, the account controller 1304 can determine, for instance, (a) if the player is authorized to access the credit account 1314, (b) if the player is restricted from making credit transactions on wagering games, (c) how much money the game session account 1310 is authorized to transact in a specified period, (d) how much money the credit account 1314 is authorized to transact, etc.

FIG. 13 shows four transactions. In the first transaction (see “1” in FIG. 13) a player (not shown) uses the interface 1308 to select the Quick Add button 1328 to request a quick funds augmentation of the wagering game session account 1310. After the wagering game machine 1302 receives the player's request, the machine 1302 notifies the account controller 1304 about the request. As a result, in the second transaction (see “2), the account controller 1304 accesses the player account settings 1308 to determine a transaction amount (e.g., $100) associated with the Quick Add button 1328. The account controller 1304 also determines credit account information, from the player account settings 1308, to be able to access the credit account 1314 and transfer the transaction amount. However, before initiating the transfer of the transaction amount, the account controller 1304 first accesses (see “3) the player account rules 1312, the wagering game session account limitation rules 1322, the credit account limitation rules 1342, and the authority limitation rules 1332. The account controller 1304 determines whether there are any rules that restrict the money transaction between the credit account 1314 and the wagering game session account 1310. If there are no restrictions or use limits, the account controller 1304 can transfer (see “4”) the transaction amount (e.g., $100) from the credit account 1314 to the player's wagering game session account 1310. Funds in the wagering game session account 1310 appear on the wagering game machine's credit meter 1318 and are available for use in wagering games presented on the wagering game machine 1302. If, however, there are limitations, the account controller 1304 can enforce the limitations. FIGS. 14, 15, and 16 illustrate some example embodiments and operations of how a player account can be configured to utilize and enforce limitations in connection with credit accounts.

FIG. 14 is an illustration of managing use limitations in connection with credit accounts, according to some embodiments. In FIG. 14, a wagering game system (“system”) 1400 includes a client computer 1445 connected to an account server 1404. The account server 1404 can include an account controller, or be connected to another device with an account controller, according to some embodiments. The account server 1404 can also include an account manager, for example, account manager 236 in FIG. 2. The account server 1404 can include a player account 1403. In some embodiments, the client computer 1445 can be a home computer which a player can use to access the player account 1403 via the Internet. In some embodiments, the client computer 1445 can be a terminal at a kiosk or a casino cage. In some embodiments, the client computer 1445 can be a wagering game machine. The player account 1403 can include an account settings panel 1419 that a player can use to store account information about one or more credit accounts (e.g., credit card accounts, Internet credit accounts, bank lines of credit, casino lines of credit, etc.) The account information can include account holder information (e.g., name, address, etc.), credit card numbers, personal identification numbers (PINs), account access numbers, passwords, etc. The system 1400 can use the account information to access the one or more credit accounts. FIG. 13 describes some embodiments for accessing a credit account. The account information can also include a default transaction amount 1423 per each credit account that the system 1400 can transact during a Quick Add procedure. The system 1400 can cycle through the credit accounts to use during the Quick Add procedure. In some embodiments, the system 1400 can pre-load a specific amount into a holding account that can be used during the wagering game session. In other words, instead of transacting with a credit account when a Quick Add procedure is processed during a wagering game session, the system 1400 can have a holding account that the player “fills up” from the credit account before beginning a wagering game session. The system 1400 can then access the holding account instead of having to make a transaction with the credit account multiple times during the wagering game session. The system 1400, however, can limit the amount that can be stored in the holding account to prevent the player from preloading a large amount of funds from the credit account. The system 1400, therefore, can have limitations, as described in FIGS. 13, 15, and 16, which can help keep the player's use of the credit account in check.

The system 1400 also includes a wagering game machine 1462. The wagering game machine 1462 has a graphical user interface (“GUI”) 1402 that a player can use to play wagering games. The GUI 1402 can also include a Quick Add button 1420, which can initiate a Quick Add procedure to automatically add money to a wagering game session balance. The Quick Add button 1420 can initiates a series of operations that the system 1400 can perform, similar to the operations described in FIG. 13, 15, and/or 16. For example, the system 1400 can access a wagering game session account on the account server 1404 and search limitation rules sources for limitations rules that have been set on the use of the credit accounts in the account settings panel 1419. FIG. 13 described various sources for the limitation rules. One of the sources can be a player's account rules. For instance, one kind of account rule can include a self-imposed limitation to assist the player to responsibly use credit account(s) for wagering games. For example, referring briefly back to FIG. 9, the source account 908 can list a credit account that the player can select and use to pull money from for quickly augmenting funds in a wagering game account. Returning back to FIG. 14, for example, an account rule can include an instruction (e.g., a trigger) to determine when the player activates the Quick Add button 1420 from the wagering game machine 1462. During the process of transacting money from a source credit account, the account rule can determine whether the player has exceeded a transaction limit amount (“use limit”). The player can set the limitations of the use limit, such as by specifying a limit amount and a limit period (e.g., a daily use limit of $200). The player can set an action to “Lock” transactions from that source credit account, if the player has exceeded the use limit. If the use limit has been exceeded, the system 1400 can select other source credit accounts configured to work with the Quick Add procedure (e.g., if the “Visa” account is restricted or has met its use limit, then the system 1400 can look to the “Pal Pal” account). In some embodiments, the player can also set account rules that initiate a Quick Add procedure automatically, without the need to select a Quick Add button 1420. For example, the player can set an account rule with a trigger that watches when the wagering game session credit balance has dropped below a specified number of credits, or when a wager is placed that exceeds the credit balance. If so, then the trigger initiates an action to initiate an electronic funds transfer from the credit account to the wagering game session account. The system 1400, however, can still check for use limitations on the credit account before performing the electronic funds transfer.

If there are limitations, the system 1400 can generate a message 1412 to notify the player of restraints, use limits, etc. The system 1400 can deactivate the Quick Add procedure and/or controls associated with the wagering game machine 1462 when all accounts are restricted. In some embodiments, the player can set account rules with triggers that warn the player when the credit account is near its use limits (e.g., the system 1400 can generate a warning message that the Visa account is near a daily cash withdrawal limit, or that the wagering game machine 1462 is near a daily funds transfer limit).

In some embodiments, the system 1400 can determine a co-account manager (e.g., a co-account holder who has a credit account profile, a social contact who has a player account, etc.) associated with the account (e.g., that the player has specified in the profile, that the credit lender has on the credit account records, etc.) The co-account manager can also set limitations on the credit account. The system 1400 can detect profile settings for the co-account manager. The co-account manager can also have a player account on the account server 1404. The profile settings can include limitations on the player's use of the credit account(s). For example, if the co-account manager is a co-account holder for one of the credit accounts, the system 1400 can look at the co-account manager's account profile to determine if the co-account manager has set use limits or restraints on using that credit account for wagering game purposes. In another example, the player account 1403 can be associated with a social network account, and the co-account manager can be a social contact (e.g., a trusted friend, a money manager, a social worker, etc.) on the social network. The player can use the system 1400 to designate the social contact (e.g., within the account settings panel 1419), as an authorized agent to help the player to gamble more responsibly by giving the social contact the ability to set limitations for the player. The social contact can have an account (e.g., a social network account, a financial account, a player account, etc.) that the system 1400 can access. The system 1400 can look at the social contact's account for any limitations that the social contact has set on the use of the credit account(s) they are authorized to co-manage. In some embodiments, the co-account manager can set limitations by creating account rules which include actions that limit the use of the credit account.

FIG. 15 is a flow diagram illustrating determining limitations on credit accounts for augmenting a wagering game session account, according to some embodiments. The description for FIG. 15 will refer to some previous illustrations, such as FIGS. 9, 13, and 14. In FIG. 15, the flow 1500 begins at processing block 1502, where a wagering game system (“system”) detects activation of a Quick Add procedure. The Quick Add procedure can be a single-selection Quick Add procedure. A single selection Quick Add procedure can be initiated by a single activity or event (e.g., a single click of a control, a single touch of a button, a single trigger, etc.) The system completes the rest of the operations, without additional player intervention, to transact an electronic account transaction, such as from a credit account, into the wagering game session account. FIG. 13 illustrates one example of a graphical user interface 1308 that can activate a single selection Quick Add procedure with a single touch of the with a Quick Add button 1328. FIG. 5A illustrates another example. In FIG. 5A, the icons 506, 508, 510, 512 can be “single-selection” Quick Add icons that can automatically augment a wagering game session balance with a single a touch. The system can take a default amount of funds from the accounts associated with the icons 506, 508, 510, 512. One of those icons 506, 508, 510, 512, or others not shown, can relate to electronic accounts, such as a credit account, that can be monitored and restricted according to limitation rules.

The flow 1500 continues at processing block 1504, where the system determines a credit account, and credit account access information, associated with the Quick Add procedure. The system can determine the credit account, in one embodiment, as described in FIG. 13, by utilizing an account controller. In other embodiments, the system can utilize wagering game servers (e.g., see FIG. 3), account servers (e.g., see FIG. 14), and other devices in conjunction with an account controller. The system can determine the credit account access information by reading from a player account on a wagering game network (e.g., see FIG. 14). In some embodiments, the system is configured to store the credit account access information in the player account so that the player can avoid having to input credit card information at a wagering game machine and enter account information while playing a wagering game. Nevertheless, in some embodiments, the system can obtain the credit account access information from a card swipe at a wagering game machine, or other similar ways. For example, a wagering game machine can be configured with a Quick Add reader (e.g., magnetic card reader, a touch pad, etc.) to which a player can touch or couple a personal storage device (e.g., an RFID card, a laptop, a cell phone, etc.) that can remotely transfer information to the Quick Add reader. The Quick Add reader can pull the credit account access information from the personal storage device. The Quick Add reader can have a default transaction amount associated within it, which the system can use, as described in processing block 1506.

The flow 1500 continues at processing block 1506, where the system determines a transaction amount to transfer from the credit account to the wagering game session account. The system can determine a transaction amount to transfer by searching a player profile to determine a default transaction amount, as illustrated in FIG. 14. In other embodiments, the system can use a default system amount, not a player indicated amount. For instance, a wagering game machine can store a default transaction amount associated with a Quick Add mechanism. When the Quick Add mechanism is initiated, the system can look at the stored default transaction amount on the wagering game machine. In other embodiments, the player can indicate the transaction amount as part of an interview at the beginning of a wagering game session. In other embodiments, the system can prompt the player to select a specific transaction amount after the player initiates the Quick Add procedure. For example, in FIG. 5B, any of the icons 506, 508, 510, 512 can be Quick Add icons that initiate a Quick Add procedure when selected, but then prompt the player for a specific transaction amount. When the player first selects one of the icons 506, 508, 510, 512, the system can display the denomination icons 514. Each denomination icon 514 can be associated with a pre-determined money value equivalent in value to the denomination amount show on the icons 514. When the player selects a specific denomination icon 514, the system can use the denomination amount to deduct from the accounts associated with the icons 506, 508, 510, 512, or from other accounts, such as from a credit account.

The flow 1500 continues at processing block 1508, where the system determines limitations on use of the credit account to augment the wagering game session account. The system can access rules stores as illustrated in FIG. 13. In some embodiments, the system can access private and public databases over a communications network, like the Internet, to determine whether the wagering game player is restrained, or prohibited, from using the credit account for wagering game purposes. The limitations can also be use limits set by the player, by the casino, by third parties, or others, that have been authorized to limit the amount of funds that can be transacted from the credit account during a specified period of time, by a specific player, etc.

The flow 1500 continues at decisional block 1510, where the system determines whether there are use limitations. If there are use limitations, the flow 400 continues at block 1602 in FIG. 16, to determine how to enforce the use limitations. If there are no use limitations, the flow 1500 continues at processing block 1512, where the system transfers the transaction amount from the credit account to the wagering game session account. In some embodiments, the system can access the credit account for the transfer, as illustrated in FIG. 13. In other embodiments, the system can transfer funds from the credit account to a wagering account that is separate from the wagering game session account, and then subsequently transfer the funds to the wagering game session account, or vice versa. In yet other embodiments, instead of accessing the credit account after a Quick Add procedure is activated, the system can access a holding account that has been pre-loaded with funds from the credit account, like described in some embodiments of FIG. 14 above.

FIG. 16 is a flow diagram illustrating controlling use limitations, according to some embodiments. In FIG. 16, the flow 1600 begins at processing block 1602, where a wagering game system (“system”) determines whether there are use restrictions on a credit account. The system can determine various types of limitations. Some limitations can be restrictions, or prohibitions, that stop, or prevent the use of the credit account. The restrictions can be set by the player, social contacts (e.g., friends, family, financial managers, etc.), social groups (e.g., Gamblers Anonymous), jurisdictional bodies (e.g., a gaming commission), business groups (e.g., a casino, a credit card company, etc.), governing bodies (e.g., courts, law enforcement, Immigration Department, etc.), or any other individual, organization, or entity, that has an interest in keeping the player from using a credit account for wagering games. For example, some groups may know of the player's problems with gambling, money management, criminal background, debts, erratic financial status, arrears in child support, warrants, illegal immigration status, under age status, bankruptcy status, etc. Those third parties may have an interest in helping the player control spending on wagering games. Since credit accounts can be monitored and restricted electronically, the system can check for restrictions by the third parties by (a) looking at accounts, online watch lists, membership lists, court records, law enforcement databases, etc., that belong to the third parties to find the player's name and/or other identifying information (e.g., social security number, aliases, etc.), and (b) looking for limitation rules associated with the player

In processing block 1603, after finding the player's name and/or other identifying information from potential sources, the system can stop the transaction, and provide a message explaining the reason(s) for the use restriction(s). The system can present the message through a GUI as a pop-up message (e.g., see message 1412 in FIG. 14). For future reference, the system can store the player's name and any discovered restrictions on the player in a database record related to the player's account. In some embodiments, the system can periodically scan through sources to find the player's restricted status. For example, when a player first registers for a player account with a casino, the system can run a check to see if the player is listed on any sort of list restricting the use of credit accounts. The system can store that information for quick access, and run periodic updates to see if the restrictions have been removed.

In addition to use restrictions, or prohibitions, some limitations can be use limits, which limit, but don't automatically restrict, the player from using the credit account unless the player has reached a spending limit. At processing block 1604 the system determines if the player has reached, or exhausted, a spending limit set by the system. The limit can be a “session” limit, or in other words, a system imposed limit on credit account spending during any given wagering game session. The session limit can include an amount that can be utilized by any or all credit accounts for any wagering game session. To prevent the player from circumventing the limit by repeatedly starting game sessions, the session limit can also have a periodic time limitation, like a daily limit, wherein the player is restricted from utilizing any or all of the credit accounts for quick balance augmentation until the next day. The session balance can be stored and associated with an account server, with a wagering game machine, as a stand-alone background routine, etc. The player can use the credit account until the limit has been reached. Once reached, the system can provide a message, in processing block 1610, that notifies the player that the session limit is exhausted.

If there is no session limit, or if the session limit has not been exhausted, the system, at processing block 1606, can check for another type of limitation, a credit limit. A credit limit is a limit set on the credit account itself. The credit limit can be set by the player, as a self-imposed spending limit, by a social contact, by the credit account, or by other individuals, groups, third parties, and mechanisms. The system can look for money limits, time period limits, or a combination of the two like a daily spending limit. As mentioned previously, some use limitations can be self-imposed limits stored by the player as account rules in a player profile and/or player account settings. At processing block 1606, the system can check to see if the credit limit has been exhausted. For instance, the system can store a credit transfer balance to determine how many credit transfers have been made by the player, what the total amount of the credit transfers have been, and what times periods have transpired between credit transfers.

If the system determines that a credit limit has been exhausted, then, at processing block 1608, the system can check to see if there are other credit account(s) associated with the player account. If so, the flow 1500 can return to block 1602 and the system can check for limitations on the other credit account(s).

If, however, there are no other credit accounts, and the credit limit is exhausted, the flow 1500 continues at processing block 1610, where the system can provide a message that the credit limit is exhausted.

Returning now to processing block 1606, if the session limit and/or the credit limit have not been exhausted, the flow 1500 continues at processing block 1612, where the system determines whether the player account has not yet exceeded a use limit, but that the request for the transaction amount would exceed the use limits. For example, the system may determine that a default transaction amount, such as $100, would exceed the dollar amount of the limit, but the limit still has some balance left, such as $25. At processing block 1614, the system can provide a message that the limit would be exceeded if the default transaction amount were transferred (e.g., if the system were to transfer $100), but the system can still transfer up to the use limit (i.e., the $25 amount up to the limit). In some embodiments, the system can provide a message and prompt the player whether the player wants to transfer the remainder (i.e., the $25 amount). In some embodiments, the system can transfer the remainder automatically.

Returning now to processing block 1612, if there are no use restrictions, and if the use limits are not exhausted, or would not be exceeded with the transaction, the flow returns to block 1512 in FIG. 15, where the system transfers the transaction amount from the credit account to the wagering game session account. The system can then store the transaction amount in a memory store (e.g., in the credit transfer balance) that the system uses to track how much money has been transferred within the use limit. The system can coordinate any transaction fees, or other costs associated with the credit account transaction, as well as the wagering game session balance, the player account balance, or other balances necessary to track the funds transfers.

General

In this detailed description, reference is made to specific examples by way of drawings and illustrations. These examples are described in sufficient detail to enable those skilled in the art to practice the inventive subject matter, and serve to illustrate how the inventive subject matter can be applied to various purposes or embodiments. Other embodiments are included within the inventive subject matter, as logical, mechanical, electrical, and other changes can be made to the example embodiments described herein. Features or limitations of various embodiments described herein, however essential to the example embodiments in which they are incorporated, do not limit the inventive subject matter as a whole, and any reference to the invention, its elements, operation, and application are not limiting as a whole, but serve only to define these example embodiments. This detailed description does not, therefore, limit embodiments of the invention, which are defined only by the appended claims.

Each of the embodiments described herein are contemplated as falling within the inventive subject matter, which is set forth in the following claims.

Claims

1. A method comprising: assigning one or more money values to a graphical user interface control;linking the graphical user interface control to a credit account, wherein the credit account is a third-party financial account from which a player account is authorized to borrow funds up to a credit limit; andproviding, via at least one of one or more processors, the graphical user interface control for presentation during a wagering game session associated with the player account.

2. The method of claim 1 further comprising: detecting an activation of the graphical user interface control via user input during the wagering game session; andin response to the detecting the activation of the graphical user interface control, requesting a transfer, from the credit account to the player account, of an amount of money equal to at least one of the one or more money values.

3. The method of claim 2, wherein the one or more money values are less than an amount of the credit limit.

4. The method of claim 1 further comprising: detecting an additional activation of the graphical user interface control via additional user input during the wagering game session; andin response to the detecting the additional activation of the graphical user interface control, requesting a transfer, from the player account to the credit account, of an amount of money equal to at least one of the one or more money values.

5. The method of claim 4 further comprising: detecting that an amount of losses during the wagering game session exceeds a loss limit; andautomatically restricting the transfer, between the credit account and the player account, of the amount of money equal to the at least one of the one or more money values.

6. The method of claim 4, wherein the one or more values are assigned to one or more graphics, and further comprising detecting a drag and drop of one of the one or more graphics to a credit meter for the wagering game session.

7. The method of claim 1 further comprising: transferring, from the player account to the credit account, a percentage of winnings attained from the wagering game session.

8. The method of claim 1 further comprising: detecting a user input indicating the one or more money values to assign to the graphical user interface control.

9. A system comprising: one or more processors;one or more memory units configured to store instructions, which when executed by at least one of the one or more processors, cause the system to perform operations to assign one or more money values to a graphical user interface control,link the graphical user interface control to a credit account, wherein the credit account is a third-party financial account from which a player account is authorized to borrow funds up to a credit limit, andprovide the graphical user interface control for presentation during a wagering game session associated with the player account.

10. The system of claim 9, wherein the one or more memory units are configured to store instructions, which when executed by at least one of the one or more processors, cause the system to further perform operations to: detect an activation of the graphical user interface control via user input during the wagering game session; andin response to the activation of the graphical user interface control, request a transfer, from the credit account to the player account, of an amount of money equal to at least one of the one or more money values.

11. The system of claim 10, wherein the one or more memory units are configured to store instructions, which when executed by at least one of the one or more processors, cause the system to further perform operations to: detect that an amount of losses during the wagering game session exceeds a loss limit; andautomatically restrict the transfer, between the credit account and the player account, of the amount of money equal to the at least one of the one or more money values.

12. The system of claim 9, wherein the one or more money values are less than an amount of the credit limit.

13. The system of claim 9, wherein the one or more memory units are configured to store instructions, which when executed by at least one of the one or more processors, cause the system to further perform operations to: detect an activation of the graphical user interface control via user input during the wagering game session; andin response to the activation of the graphical user interface control, request a transfer, from the player account to the credit account, of an amount of money equal to at least one of the one or more money values.

14. The system of claim 9, wherein the one or more memory units are configured to store instructions, which when executed by at least one of the one or more processors, cause the system to further perform operations to: transfer, from the player account to the credit account, a percentage of winnings attained from the wagering game session.

15. The system of claim 9, wherein the one or more memory units are configured to store instructions, which when executed by at least one of the one or more processors, cause the system to further perform operations to: detect a user input indicating the one or more money values to assign to the graphical user interface control.

16. One or more non-transitory, machine-readable storage media having instructions stored thereon, which when executed by a set of one or more processors cause the set of one or more processors to perform operations comprising: assigning one or more money values to a graphical user interface control;linking the graphical user interface control to a credit account, wherein the credit account is a third-party financial account from which a player account is authorized to borrow funds up to a credit limit;providing the graphical user interface control for presentation during a wagering game session associated with the player account;detecting an activation of the graphical user interface control via user input during the wagering game session; andin response to the activation of the graphical user interface control, requesting a transfer, between the credit account and the player account, of an amount of money equal to at least one of the one or more money values.

17. The one or more non-transitory, machine-readable storage media of claim 16, wherein the one or more money values are less than an amount of the credit limit.

18. The one or more non-transitory, machine-readable storage media of claim 16, wherein the operations further include: transferring, from the player account to the credit account, a percentage of winnings attained from the wagering game session.

19. The one or more non-transitory, machine-readable storage media of claim 16, wherein the operations further include: detecting a user input indicating the one or more money values to assign to the graphical user interface control.

20. The one or more non-transitory, machine-readable storage media of claim 16, wherein the operations further include: detecting that an amount of losses during the wagering game session exceeds a loss limit; andautomatically restricting the transfer, between the credit account and the player account, of the amount of money equal to the at least one of the one or more money values.