Systems and methods for location-based game play on computing devices

Information

  • Patent Grant
  • 11250666
  • Patent Number
    11,250,666
  • Date Filed
    Monday, October 29, 2018
    6 years ago
  • Date Issued
    Tuesday, February 15, 2022
    2 years ago
Abstract
Systems and methods are provided for: receiving, from a terminal, identification information associated with a user, wherein the receipt of the identification information is caused by an identification operation performed at at least one of the terminal or a remote processing system located away from the terminal; determining gaming rules associated with a physical jurisdiction for the terminal, wherein a first portion of the gaming rules is provisioned at the terminal, and wherein a second portion of the gaming rules is provisioned by a remote processing system located away from the terminal; and determining, based on at least one of the first portion of the gaming rules or the second portion of the gaming rules, whether the user associated with the identification information is eligible to participate in a game associated with the physical jurisdiction.
Description
TECHNICAL FIELD

This disclosure generally relates to game play systems relating to location-based game play on computing devices.


BACKGROUND

Various governments around the world allow lottery games to be legalized within their borders. Legalization of lottery games and other game plays is typically driven by the public support for this style of entertainment. Currently, these games are presented through specific manned terminals that connect to lottery operators, or corporations responsible for running the games. The player is provided a paper ticket of the game play or lottery play. The paper ticket is a bearer instrument, in that the holder of the paper ticket—whether the original purchaser or not—is entitled to the winnings associated with that paper ticket.


While these games have proven to be popular, a large segment of the population does not participate. This is due to many factors, including the inconvenience of the manned terminals, the concern over losing a ticket, and, more recently, the lack of cash to play the games as many people prefer using payment cards for their various purchases. In addition, due to regulatory restrictions, the sale of lottery products is restricted to various government-approved entities. These restrictions have created some obstacles in bringing game play sales to a broader spectrum of sale outlets. For example, existing sales solutions used in various sale outlets are not appropriate for the sale of the lottery games (or other game plays) because they lack assurances that the sale outlet is located within the “borders” or restrictions of the government regulating the lottery game.


SUMMARY

In some embodiments, a processing system is provided, which is configured to: receive, from a terminal, identification information associated with a user, wherein the receipt of the identification information is caused by an identification operation performed at at least one of the terminal or the processing system located away from the terminal; determine gaming rules associated with a physical jurisdiction associated with the terminal, wherein the gaming rules are provisioned in response to receiving a game play request at or from the terminal, wherein a first portion of the gaming rules is provisioned at or by the terminal, and wherein a second portion of the gaming rules is provisioned at or by the processing system located away from the terminal; determine, based on at least one of the first portion of the gaming rules or the second portion of the gaming rules, whether the user associated with the identification information is eligible to participate in a game associated with the physical jurisdiction; and in response to determining the user associated with the identification information is eligible to participate in the game associated with the physical jurisdiction, enable participation of the user associated with the identification information in the game associated with the physical jurisdiction, wherein presentation of game content associated with the game at the terminal is controlled by control data associated with at least one of the terminal or the processing system, wherein the presentation of the game content associated with the game at the terminal is further based on an attribute of the terminal, and wherein first game content for the game presented at a first terminal associated with a first location is different from second game content for the game presented at a second terminal at a second location.


In some embodiments, the game is associated with a game play set. In some embodiments, the game is presented on the terminal or on a second terminal. In some embodiments, content associated with the game is presented on a user interface of the terminal and is at least partially directed or controlled by the processing system. In some embodiments, the terminal is associated with or comprised in at least one of a gas or fuel pump, a retail terminal, a kiosk, or a mobile device. In some embodiments, the game comprises a lottery game. In some embodiments, the game comprises a non-lottery game. In some embodiments, the attribute of the terminal further comprises at least one of a display capability of the terminal, or a capability of connecting the terminal to a network. In some embodiments, logic for the presentation of the game content is updated based on the attribute of the terminal or based on a connection between the processing system and the terminal.


In some embodiments, a method is provided comprising: receiving, from a terminal, identification information associated with a user, wherein the receipt of the identification information is caused by an identification operation performed at at least one of the terminal or a remote processing system located away from the terminal; determining gaming rules associated with a physical jurisdiction associated with the terminal, wherein the gaming rules are provisioned in response to receiving a game play request at or from the terminal, wherein a first portion of the gaming rules is provisioned at or by the terminal, and wherein a second portion of the gaming rules is provisioned at or by the remote processing system located away from the terminal; determining, based on at least one of the first portion of the gaming rules or the second portion of the gaming rules, whether the user associated with the identification information is eligible to participate in a game associated with the physical jurisdiction; and in response to determining the user associated with the identification information is eligible to participate in the game associated with the physical jurisdiction, enabling participation of the user associated with the identification information in the game associated with the physical jurisdiction, wherein presentation of game content associated with the game at the terminal is controlled by control data associated with at least one of the terminal or the remote processing system, wherein first game content for a first game presented at a first terminal associated with a first location is different from second game content for a second game presented at a second terminal at a second location.


These and other advantages of the present disclosure will become apparent to those skilled in the art from the following detailed description, the accompanying drawings, and the appended claims.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1A is a schematic diagram illustrating a game play system, in accordance with the present disclosure;



FIG. 1B is a schematic diagram illustrating a game play system, in accordance with the present disclosure;



FIG. 2A is a schematic diagram illustrating a game play system in communication with a fuel payment system, in accordance with the present disclosure;



FIG. 2B is a schematic diagram illustrating a game play system in communication with a fuel pump system, in accordance with the present disclosure;



FIG. 2C is a schematic diagram illustrating a game play system in communication with a fuel pump system, in accordance with the present disclosure;



FIG. 2D is a schematic diagram illustrating a game play system in communication with a fuel pump system, in accordance with the present disclosure;



FIG. 2E is a schematic diagram illustrating a game play system in communication with a fuel pump system, in accordance with the present disclosure;



FIG. 2F is a schematic diagram illustrating a game play system in communication with a fuel pump system, in accordance with the present disclosure;



FIG. 2G is a schematic diagram illustrating a game play system in communication with a fuel pump system, in accordance with the present disclosure;



FIG. 3A is a schematic diagram illustrating a game play system in communication with a grocery payment system, in accordance with the present disclosure;



FIG. 3B is a schematic diagram illustrating a game play system in communication with a grocery payment system, in accordance with the present disclosure;



FIG. 3C is a schematic diagram illustrating a game play system in communication with a grocery payment system, in accordance with the present disclosure;



FIG. 3D is a schematic diagram illustrating a game play system in communication with a grocery payment system, in accordance with the present disclosure;



FIG. 3E is a schematic diagram illustrating a game play system in communication with a grocery payment system, in accordance with the present disclosure;



FIG. 4A is a schematic diagram illustrating a game play system in communication with a self-service grocery payment system, in accordance with the present disclosure;



FIG. 4B is a schematic diagram illustrating a game play system in communication with a self-service grocery payment system, in accordance with the present disclosure;



FIG. 5 is a schematic diagram illustrating a game play system in communication with an electronic tablet payment system, in accordance with the present disclosure;



FIG. 6A is a schematic diagram illustrating a game play system in communication with an electronic tablet payment system, in accordance with the present disclosure;



FIG. 6B is a schematic diagram illustrating a game play system in communication with a cloud-based embodiment of a electronic tablet payment system, in accordance with the present disclosure;



FIG. 7 is a flow diagram illustrating a game play purchase in the game play system, in accordance with the present disclosure; and



FIG. 8 is a flow diagram illustrating automatic redemption of a winning game play purchase in the game play system, in accordance with the present disclosure.





DETAILED DESCRIPTION

The present disclosure provides a game play system and game play methods to allow for game play (e.g., lottery play) purchases at a variety of outlets while complying with various governmental restrictions regulating game plays. Game plays may include various types of games, including, but not limited to lottery wagers, lottery draws, scratch tickets, virtual scratch tickets, branded games, second chance games, etc. Thus, the game play system and game play methods allow access for making game play purchases beyond the traditional manned lottery authority terminals providing paper tickets, although the game play system and game play methods could also be used in the context of manned terminals. Indeed, the game play system and game play methods allow for convenient, every day access to game play purchases at various payment-enabled terminals.


Further, the game play system and game play methods allow for a substantially “ticketless” game play—or, a “ticketless” lottery wager. Specially, the game play system and game play methods provide for storing, managing, and redeeming of game play purchases so that a user is not required to present a paper lottery ticket or lottery bearer instrument to redeem winnings. Instead, a winning game play is associated with the user's payment card number in secure storage within the game play system, and winnings may be automatically directed to an account associated with the user's payment card and/or may be effected based on the user's payment card number. In addition, the game play system and game play methods allow for a user to purchase a game play using a payment card (e.g., a debit or credit card) instead of cash. Similarly, the game play system and game play methods allow for a user to purchase a game play using a device carrying or providing payment card data (e.g., an NFC-enabled user device).


As used herein, payment-enabled terminals may refer to a variety of terminals and payment platforms, including, but not limited to, swipe-enabled terminals, swipe-enabled point of sale (POS) systems, Card Reader in Dispenser terminals (CRIND terminals), payment-enabled “smart” devices (e.g., tablets, netbooks, mobile devices, etc.), payment kiosks, self-service payment terminals, automated teller machines (ATMs), “tap” payment platforms, near-field communication payment platforms, proximity-based communication payment platforms, barcode scan payment platforms, cloud-enabled payment devices and interfaces, and cloud-enabled point of sale platforms.


The game play system and game play methods disclosed herein allow for seamless and integrated game play transactions to a user at a payment-enabled terminal. The game play system and game play methods link gaming partners and financial payment partners together with a user at a payment-enabled terminal. In doing so, the game play system and the game play methods allow for a user to purchase a game play or lottery wager at the payment-enabled terminal by receiving the request from the user, provisioning various game play regulations to determine whether the request is valid, effecting the financial transaction associated with the game play purchase, providing information related to the game play purchase to the user, effecting various automatic redemption processes, notifying the user about winning plays, etc. Various aspects, features, and functionality of the game play system and the game play methods are discussed in further detail in commonly-assigned U.S. patent application Ser. Nos. 11/734,207, 13/280,196, 61/593,762, 61/696,533, Ser. Nos. 13/757,512, and 13/829,776, which are each herein incorporated by reference for all purposes.


Disclosed herein are game play systems and methods for facilitating a game play purchase by a user at a payment-enabled terminal. The game play system may store a plurality of records of game play number sets associated with respective payment card numbers; and receive a payment card number associated with the user. The payment card number may originate at the payment-enabled terminal and may be identified when the user swipes its payment card at the payment-enabled terminal. The game play system may also associate the payment card number with a game play number set received from a gaming operator. The game play system may further communicate to the transaction database the payment card number and game play number set for storage at the transaction database.



FIG. 1A is a schematic diagram illustrating a game play system 100 for facilitating a game play purchase by a user at a payment-enabled terminal 103. The payment-enabled terminal 103 may include a user interface 107, swipe 105, a pin pad (not shown), or various peripherals. In an embodiment, the user interface 107 is a touch screen.


The game play system 100 includes a game play data center 110 having a game play transaction database 112 for storing game play records 114 and one or more game play transaction processing servers 116 in communication with the transaction database 112. The game play data center 110 is in communication with a gaming operator 120 having one or more gaming operator servers 126. The gaming operator servers 126 are operable to generate game play number sets, and the transaction processing server 116 receives a game play number set for a given game play transaction from the gaming operator 120. In an embodiment, the gaming operator is part of the game play system 100, and includes one or more gaming operator servers 126 in communication with the game play transaction processing servers 116 over an intersystem network 117. In another embodiment, the gaming operator is located remotely from the game play system 100 and is in communication with the game play transaction processing servers 116 over a secure network connection 119. In either embodiment, the game play transaction processing servers 116 are operable to receive information from the gaming operator 120 and/or gaming operator servers 126 relating to a game play transaction.


In some embodiments, the game play system 100 further comprises a game play system payment processor 118 in communication with the game play data center 110. The game play system payment processor 118 may conduct a financial transaction associated with the game play purchase independent of a financial payment processor 130, upon receiving communications from the game play transaction processing servers 116 to that effect. In other embodiments, the game play system 100 communicates with the financial payment processor 130 to initiate a financial transaction associated with the game play purchase.


Still referring to FIG. 1A, the game play system 100 may be in communication with a payment-enabled terminal 103, a media server 160, an electronic payment host 140, and/or a financial payment processor 130. The electronic payment host 140 may include a payment host 142 and/or a payment network data center 144. The media server 160 may include a media host 162 and/or a payment host 164.


For example, in an embodiment, the payment-enabled terminal 103 may be a fuel pump payment interface in communication with a local point of sale terminal (not shown), and the electronic payment host 140 may be a point of sale host. In an alternative embodiment, the payment-enabled terminal 103 may be a fuel pump interface in communication with the media server 160. The media server 160 may further be in communication with the electronic payment host 140 and/or may be in communication with the financial payment processor 130. As another example, in an embodiment, the payment-enabled terminal 103 may be an in-lane grocery point of sale terminal, and the electronic payment host 140 may be an electronic payment system host associated with the in-lane grocery point of sale system. As another example, in an embodiment, the payment-enabled terminal 103 may be a self-serve grocery kiosk in connection with a grocery local point of sale terminal, and the electronic payment host 140 may be an electronic payment system host associated with the grocery store local point of sale terminal. As another example, in an embodiment, the payment-enabled terminal 103 may be a swipe-enabled electronic tablet in communication with a local electronic tablet payment system server, and the electronic payment host 140 may be a gateway associated with the local electronic tablet payment system server.


Other interfaces and connectivity with fuel pump systems, grocery payment systems, and electronic tablet payment systems are also further described below, and the game play system may bypass an electronic payment host 140 in certain embodiments. Indeed, any payment-enabled device 103 that includes a user interface 107 and a mechanism for determining a payment card number, that is connected, generally speaking, to a payment network, may communicate with the game play system 100. Game play purchases are, thus, possible through a variety of payment-enabled devices 103.


The game play transaction processing servers 116 may receive a payment card number associated with the user 101. The payment card number originates at the payment-enabled terminal 103 and is identified when the user 101 swipes its payment card at the payment-enabled terminal 103 or when the payment card number is otherwise determined (e.g., through a mobile “tap” or NFC communication) at the payment-enabled terminal 103. The game play transaction processing servers 116 may also associate the payment card number with a game play number set received from a gaming operator 120. The game play transaction processing servers 116 may communicate the payment card number and game play number set to the transaction database 112 for storage in records 114.


Still referring to FIG. 1A, the game play system 100 is operable to effect ticketless game plays by associating the user's payment card number with a game play number set. For example, the game play transaction database 112 may store a plurality of records 114 of game play number sets associated with respective payment card numbers. The game play transaction processing servers 116 may manage ticketless lottery transactions by associating, storing, and referencing the plurality of records 114 of game play number sets and their respective payment card numbers. The game play system 100 is also operable to effect automatic winner redemption by initiating payment to an account tied to a payment card number associated with a winning game play number set. The game play system 100 may also manage second chance game plays based on the plurality of records 114 of game play number sets associated with respective payment card numbers stored at the transaction database 112. For example, the game play system 100 may reference the plurality of records 114 to identify non-winning game play number sets. The game play system 100 may then use a random number generator (or other game play mechanism) to run a second chance play for the users associated with the non-winning game play number sets. The “winnings” for the second chance game play may include, but is not limited to, a game play, a store promotion, or free merchandise. For example, if a user purchased the game play at a payment-enabled terminal associated with a particular store, then the game play system may manage and run second chance game plays for that store, and “winnings” for the second chance game play may include a store promotion for that store.


A user 101 of the game play system 100 may use a credit card or debit card to conduct the game play purchase. Thus, the payment card number may be a credit card number or a debit card number.


Further, the connections between the various system elements may be wired or wireless, and may also be cloud-based communications. For example, in an embodiment shown in FIG. 1B, the game play system 100 is in communication with a cloud media server 160, cloud e-commerce platform 140, and/or a cloud based financial payment processor 130. The game play system 100 may also be cloud-based. A transmitter-receiver 190 associated with the payment-enabled terminal 103 may communicate with the various systems 100, 160, 140, and/or 130. Thus, the payment-enabled terminal 103 may receive communications, instructions, data, content for display at the payment-enabled terminal 103 over the cloud from the game play system 100.


Referring back to FIG. 1A, the transaction database 112 is further operable to store one or more sets of gaming rules associated with respective jurisdictions, and the transaction processing servers 116 are operable to provision the gaming rules for a given game play purchase. The game play transaction processing servers 116 may further lookup a payment card number in the game play transaction database to determine the eligible lottery transactions associated with the payment card number. The transaction processing servers 116 may provision the gaming rules based a user's age, based on payment card limits, based on responsible game play restrictions, draw break buffers, and/or based on other time and day restrictions. In some embodiments, the remote system associated with the payment-enabled terminal 103 (or the payment-enabled terminal itself) may provision all or a portion of the gaming rules for the game play purchase in cooperation with the transaction processing servers 116. The game play system 100 may provide instructions for the provisioning of all or a portion of the gaming rules to the remote system associated with the payment-enabled terminal 103 (or to the payment-enabled terminal itself) substantially in real-time. Thus, gaming rule provisioning may be conducted wholly at the game play system 100, wholly at the remote system associated with the payment-enabled terminal (or the payment-enabled terminal itself) in communication with the game play system 100, or at a combination of the game play system 100 and the remote system, depending on the payment-enabled terminal capability and the connection between the payment-enabled terminal 103 and the game play system 100. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both, depending on the payment-enabled terminal capability and the connection between the payment-enabled terminal 103 and the game play system 100.


The game play system 100 may further direct or control the content displayed at a user interface 107 of the payment-enabled terminal 103. Generally speaking, the presentment of content displayed at the user interface 107 may be all or partially directed by the game play system 100, or may be all or partially directed by the remote system associated with the payment-enabled terminal 103, or may be a combination of remote system presentment of content and game play system 100 presentment of content, depending on the payment-enabled terminal capability and the connection between the payment-enabled terminal 103 and the game play system 100. Further, presenting content to the user at the payment-enabled terminal 103 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both, depending on the payment-enabled terminal capability and the connection between the payment-enabled terminal 103 and the game play system 100.


In an embodiment, the game play system 100 stores user-specific administrative data, including, but not limited to, user preferences for presentment of data at the user interface 107, game play options, etc. In an embodiment, user-specific administrative data is stored in the game play transaction database 112 and is associated with respective payment card numbers, thereby allowing for the game play system 100 to control content at the payment-enabled terminal 103, on a user-specific basis, upon receipt of a payment card number. The game play system 100 may further be operable to manage the display of content at the payment-enabled terminal 103 based on the user-specific administrative data, depending on the payment-enabled terminal capability and the connection between the payment-enabled terminal 103 and the game play system 100.



FIG. 2A is a schematic diagram illustrating a game play system 200 in communication with a fuel payment system 251. The game play system 200 may include a game play data center 210 having a game play transaction database 212 for storing game play records 214 and one or more game play transaction processing servers 216 in communication with the transaction database 212.


The game play data center 210 is in communication with a gaming operator 220 having one or more gaming operator servers (see, e.g., FIG. 1A). The gaming operator servers are operable to generate game play number sets, and the transaction processing server 216 receives a game play number set for a given game play transaction from the gaming operator 220. In an embodiment, the gaming operator is part of the game play system 200, and includes one or more gaming operator servers in communication with the game play transaction processing servers 216 over an intersystem network. In another embodiment, the gaming operator 220 is located remotely from the game play system 200 and is in communication with the game play transaction processing servers 216 over a secure network connection. In either embodiment, the game play transaction processing servers 216 are operable to receive information from the gaming operator 220 and/or gaming operator servers relating to a game play transaction.


In some embodiments, the game play system 200 further comprises a game play system payment processor 218 in communication with the game play data center 210. The game play system payment processor 218 may conduct a financial transaction associated with the game play purchase independent of the financial payment processor 230, upon receiving communications from the game play transaction processing servers 216 to that effect. In other embodiments, the game play system 200 communicates with the financial payment processor 230 to initiate a financial transaction associated with the game play purchase.


The fuel payment system may include a fuel pump 208, a local point of sale terminal 246, a point of sale host network 240, media server 260, and/or a financial payment processor 230. The game play system 200 may be in communication with the fuel pump 208, local point of sale terminal 246, media server 260, point of sale host network 240, and/or financial payment processor 230 directly or indirectly through communication servers, gateways, or other hosts. Thus, the transaction processing server 216 of the game play system 200 may receive the payment card number from a several parts of the fuel pump system 251. The fuel pump 208 may include a payment-enabled terminal 203, which may include a user interface 207 for interacting with a user 201, a swipe 205 for reading a user payment card, and/or a pin pad 209. In alternative embodiments, the payment-enabled terminal may include other kinds of swipe-enabled terminals, swipe-enabled point of sale (POS) systems, Card Reader in Dispenser terminals (CRIND terminals), payment-enabled “smart” devices (e.g., tablets, netbooks, mobile devices, etc.), payment kiosks, self-service payment terminals, automated teller machines (ATMs), “tap” payment platforms, near-field communication payment platforms, proximity-based communication payment platforms, barcode scan payment platforms, cloud-enabled payment devices and interfaces, and cloud-enabled point of sale platforms. Thus, the payment card number may be identified when the user 201 swipes its payment card at the fuel pump payment-enabled terminal 203 or when a payment card number is otherwise determined (e.g., via “tap” of a mobile device or NFC communication) at the payment-enabled terminal 203. In an embodiment, the user interface 207 comprises a media screen. The user interface (media screen) 207 may display media content guiding the user 201 through a game play purchase.


As discussed above in relation to FIGS. 1A and 1B, gaming rule provisioning may be conducted wholly at the game play system 200, wholly at the fuel payment system 251 associated with the payment-enabled terminal 203 (or the payment-enabled terminal 203 itself), or at a combination of the game play system 200 and the fuel payment system 251. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 200 may further direct or control the content displayed at a user interface 207 of the payment-enabled terminal 203. Generally speaking, the presentment of content displayed at the user interface 207 may be all or partially directed by the game play system 200, or may be all or partially directed by the fuel payment system 251 associated with the payment-enabled terminal 203, or may be a combination of fuel payment system 251 presentment of content and game play system 200 presentment of content. Further, presenting content to the user at the payment-enabled terminal 203 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 2B is a schematic diagram illustrating a game play system 200 in communication with an embodiment of a fuel pump system 251. The fuel pump system 251 includes a fuel pump 208, a local point of sale terminal 246, a point of sale host network 240, and a financial payment processor 230. The fuel pump 208 is in communication with the local point of sale terminal 246, which is in communication with the point of sale host network 240, which communicates with the financial payment processor 230 to effect a fuel pump payment transaction. The fuel pump system 251 further includes a media-enabled electronic payment system 261. The media-enabled electronic payment system 261 controls the user interface 207 to conduct a payment transaction and/or to display media content. In this embodiment, the user interface 207 is a media screen. The media-enabled electronic payment system 261 includes a media host 262 in communication with a payment host 264. The media host 262 displays and controls the media content presented to the user 201 and also receives user inputs from the swipe 205, pin pad 209, and the user interface 208, and the payment host 264 effects a payment transaction.


The game play system 200 may communicate with the media server 260 to effect a game play purchase. The game play system 200 is communication with the payment host 264 of the media payment system 260. The payment host 264 is in communication with the transaction processing server 216. Thus, the transaction processing server 216 of the game play system 200 may receive the payment card number from the payment host 264 of the media payment system 260.


Further, gaming rule provisioning may be conducted wholly at the game play system 200, wholly at the media server 260, or at a combination of the game play system 200 and the media server 260. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 200 may further direct or control the content displayed at a user interface 207 of the payment-enabled terminal 203 through the media server 260. Generally speaking, the presentment of content displayed at the user interface 207 may be all or partially directed by the game play system 200, or may be all or partially directed by the media server 260 associated with the payment-enabled terminal 203, or may be a combination of media server 260 presentment of content and game play system 200 presentment of content. Further, presenting content to the user at the payment-enabled terminal 203 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 2C is a schematic diagram illustrating a game play system in communication with another embodiment of a fuel pump system 251. The fuel pump system 251 may include a fuel pump 208, a local point of sale terminal 246, a point of sale data center 248, and a financial payment processor 230 to effect a fuel pump payment transaction. In some embodiments, the point of sale terminal 246 is in direct communication with the financial payment processor 230, bypassing a point of sale data center 248, to effect the transaction. In such an embodiment, the game play system 200 receives the payment card number from the point of sale terminal 246 associated with the fuel pump 208 or the financial payment processor 230. Accordingly, the game play transaction server may receive the payment card number from the point of sale terminal 246 or the financial payment processor 230.


In other embodiments, the fuel pump 208 is in communication with the local point of sale terminal 246, which is in communication with the point of sale data center 248, which communicates with the financial payment processor 230 to effect a fuel pump payment transaction. The point of sale data center 248 may include a point of sale host (not shown) and a communications exchange server 211. In such embodiments, the game play system 200 receives the payment card number from the communications exchange server 211 located at a point of sale data center 248. Accordingly, the game play transaction server may receive the payment card number from the communications exchange server 211.


Thus game play system 200 may communicate with the point of sale terminal 246, the financial payment processor 230, and/or the communications exchange server 211 to effect a game play purchase. The game play system 200 may also communicate with the financial payment processor 230 or the game play system payment processor 218 to effect the game play purchase transaction.


Further, gaming rule provisioning may be conducted wholly at the game play system 200; at one or more of the POS 246, communication exchange server 211, and financial payment processor 230; or at a combination of the game play system 200 and one or more of the POS 246, communication exchange server 211, and financial payment processor 230. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 200 may further direct or control the content displayed at a user interface 207 of the payment-enabled terminal 203 through one or more of the POS 246, communication exchange server 211, and financial payment processor 230. Generally speaking, the presentment of content displayed at the user interface 207 may be all or partially directed by the game play system 200, or may be all or partially directed by one or more of the POS 246, communication exchange server 211, and financial payment processor 230 associated with the payment-enabled terminal 203, or may be a combination of one or more of the POS 246, communication exchange server 211, and financial payment processor 230 presentment of content and game play system 200 presentment of content. Further, presenting content to the user at the payment-enabled terminal 203 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 2D is a schematic diagram illustrating a game play system 200 in communication with another embodiment of a fuel pump system 251. The fuel pump system 251 may include a fuel pump 208, a local point of sale terminal 246, and a financial payment processor 230 to effect a fuel pump payment transaction. The fuel pump may also include a fuel pump server 213 in communication with the user interface 207. In this embodiment, the user interface is a media screen, and the media server 213 is operable to control display of media content at the media screen and to receive user inputs at the screen 207, swipe 205, and/or pin pad 209. The game play system 200 receives the payment card number from the fuel pump server 213 of the gas pump 208. In particular, the game play transaction server 216 may receive the payment card number from the fuel pump server 213.


Thus game play system 200 may communicate with the fuel pump server 213 to effect a game play purchase. The game play system 200 may also communicate with the financial payment processor 230 or the game play system payment processor 218 to effect the game play purchase transaction.


Further, gaming rule provisioning may be conducted wholly at the game play system 200, wholly at the fuel pump server 213, or at a combination of the game play system 200 and the media server 260. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 200 may further direct or control the content displayed at a user interface 207 of the payment-enabled terminal 203 through the fuel pump server 213. Generally speaking, the presentment of content displayed at the user interface 207 may be all or partially directed by the game play system 200, or may be all or partially directed by the media server 260 associated with the payment-enabled terminal 203, or may be a combination of fuel pump server 213 presentment of content and game play system 200 presentment of content. Further, presenting content to the user at the payment-enabled terminal 203 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 2E is a schematic diagram illustrating a game play system 200 in communication with another embodiment of a fuel pump system 251. The fuel pump system 251 may include a fuel pump 208, a local point of sale terminal 246, and a financial payment processor 230 to effect a fuel pump payment transaction. The financial payment processor may include a communications exchange server 215 in communication with the game play system 200. The communications exchange server 215 receives the user's payment card number from the point of sale terminal 246, which receives the user's payment card number from the payment-enabled terminal 203. The game play system 200 receives the payment card number from the communications exchange server 215 of the financial payment processor 230. In particular, the game play transaction server 216 may receive the payment card number from the communications exchange server 215 of the financial payment processor 230.


Thus game play system 200 may communicate with the communications exchange server 215 of the financial payment processor 230 to effect a game play purchase. The game play system 200 may also communicate with the financial payment processor 230 or the game play system payment processor 218 to effect the game play purchase transaction.


Further, gaming rule provisioning may be conducted wholly at the game play system 200, wholly at the communications exchange server 215, or at a combination of the game play system 200 and the media server 260. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 200 may further direct or control the content displayed at a user interface 207 of the payment-enabled terminal 203 through the communications exchange server 215. Generally speaking, the presentment of content displayed at the user interface 207 may be all or partially directed by the game play system 200, or may be all or partially directed by the media server 260 associated with the payment-enabled terminal 203, or may be a combination of communications exchange server 215 presentment of content and game play system 200 presentment of content. Further, presenting content to the user at the payment-enabled terminal 203 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 2F is a schematic diagram illustrating a game play system 200 in communication with another embodiment of a fuel pump system 251. The fuel pump system 251 may include a fuel pump 208, a local point of sale terminal 246, and a centralized payment system 217 to effect a fuel pump payment transaction. The centralized payment system 217 may include a financial payment data center associated with the fuel pump system and a financial payment processor. The centralized payment system 217 is in communication with the game play system 200. The centralized payment system 217 receives the user's payment card number from the point of sale terminal 246, which receives the user's payment card number from the payment-enabled terminal 203. The game play system 200 receives the payment card number from the centralized payment system 217. In particular, the game play transaction server 216 may receive the payment card number from the centralized payment system 217.


Thus game play system 200 may communicate with the centralized payment system 217 of the financial payment processor 230 to effect a game play purchase. The game play system 200 may also communicate with the centralized payment system 217 or the game play system payment processor 218 to effect the game play purchase transaction.


Further, gaming rule provisioning may be conducted wholly at the game play system 200, wholly at the centralized payment system 217, or at a combination of the game play system 200 and the centralized payment system 217. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 200 may further direct or control the content displayed at a user interface 207 of the payment-enabled terminal 203 through the centralized payment system 217. Generally speaking, the presentment of content displayed at the user interface 207 may be all or partially directed by the game play system 200, or may be all or partially directed by the centralized payment system 217 associated with the payment-enabled terminal 203, or may be a combination of centralized payment system 217 presentment of content and game play system 200 presentment of content. Further, presenting content to the user at the payment-enabled terminal 203 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 2G is a schematic diagram illustrating a game play system 200 in communication with a cloud-based embodiment of a fuel pump system 251. The fuel pump system 251 may include a fuel pump 208 and a transmitter-receiver 290. The transmitter-receiver 290 may send and receive communications to and from a cloud-based media server 260, a cloud e-commerce platform 240, and a financial payment processor 230 to effect a fuel pump payment transaction. The transmitter-receiver 290 may further be in communication with the game play system 200. The game play system 200 may also be in communication with the cloud-based media server 260, the cloud e-commerce platform 240, and/or the financial payment processor 230.


The game play system 200 receives the payment card number from the transmitter-receiver 290 either directly or indirectly through one or more of the cloud media server 260, cloud e-commerce platform 240, and financial payment processor 230. Thus game play system 200 may communicate with the payment-enabled terminal 203 via the cloud to effect a game play purchase.



FIG. 3A is a schematic diagram illustrating a game play system 300 in communication with a grocery payment system 352. The game play system 300 may include a game play data center 310 having a game play transaction database 312 for storing game play records 314 and one or more game play transaction processing servers 316 in communication with the transaction database 312.


The game play data center 310 is in communication with a gaming operator 320 having one or more gaming operator servers (see, e.g., FIG. 1A). The gaming operator servers are operable to generate game play number sets, and the transaction processing server 316 receives a game play number set for a given game play transaction from the gaming operator 320. In an embodiment, the gaming operator is part of the game play system 300, and includes one or more gaming operator servers in communication with the game play transaction processing servers 316 over an intersystem network. In another embodiment, the gaming operator 320 is located remotely from the game play system 300 and is in communication with the game play transaction processing servers 316 over a secure network connection. In either embodiment, the game play transaction processing servers 316 are operable to receive information from the gaming operator 320 and/or gaming operator servers relating to a game play transaction.


In some embodiments, the game play system 300 further comprises a game play system payment processor 318 in communication with the game play data center 310. The game play system payment processor 318 may conduct a financial transaction associated with the game play purchase independent of the financial payment processor 330, upon receiving communications from the game play transaction processing servers 316 to that effect. In other embodiments, the game play system 300 communicates with the financial payment processor 330 to initiate a financial transaction associated with the game play purchase.


The grocery payment system may include a networked register 390, payment-enabled terminal 303, an electronic payment system 355, and a financial payment processor 330. The game play system 300 may be in communication with the networked register 390, media server 360, payment-enabled terminal 303, electronic payment system 355, and/or financial payment processor 330 directly or indirectly through communication servers, gateways, or other hosts. The media server 360 may include a media host 362 and/or a payment host 364.


Thus, the transaction processing server 316 of the game play system 300 may receive the payment card number from the grocery payment system 352. The payment-enabled terminal 303 may include a user interface 307 for interacting with a user 301 and swipe 305 for reading a user payment card. Thus, the payment card number may be identified when the user 301 swipes its payment card at the payment-enabled terminal 303, or when a payment card number is otherwise determined (e.g., via “tap” of a mobile device or NFC communication) at the payment-enabled terminal 303. In an embodiment, the payment-enabled terminal 303 is a local point of sale terminal in the grocery store. The point of sale terminal may further include a pin pad 309. In an embodiment, the user interface 307 comprises a media screen. The user interface (media screen) 307 may display media content guiding the user 301 through a game play purchase. The media server 360 may control or direct the display of media content at the user interface 307 and may also receive data and information input by the user 301 at the interface 307, pin pad 309, and/or swipe 305.


As discussed above in relation to FIGS. 1A and 1B, gaming rule provisioning may be conducted wholly at the game play system 300, wholly at the fuel payment system 352 associated with the payment-enabled terminal 303 (or the payment-enabled terminal 303 itself), or at a combination of the game play system 300 and the fuel payment system 352. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 300 may further direct or control the content displayed at a user interface 307 of the payment-enabled terminal 303. Generally speaking, the presentment of content displayed at the user interface 307 may be all or partially directed by the game play system 300, or may be all or partially directed by the fuel payment system 352 associated with the payment-enabled terminal 303, or may be a combination of fuel payment system 352 presentment of content and game play system 300 presentment of content. Further, presenting content to the user at the payment-enabled terminal 303 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 3B is a schematic diagram illustrating a game play system 300 in communication with an embodiment of the grocery payment system 352. In in embodiment, the grocery store payment system 352 is an in-lane grocery payment system.


The grocery payment system 352 includes a networked register 390, payment-enabled terminal 303, an electronic payment system 355, and a financial payment processor 330. The payment-enabled terminal 303 is in communication with an electronic payment system 355, which communicates with a financial payment processor 330. The grocery payment system 352 may further include a payment host 357 associated with the payment-enabled terminal 303. The payment host 357 may direct the display of transaction content on the user interface 307 of the payment-enabled terminal 303. In an embodiment, the user interface 307 is a media screen, and the host 357 directs the display of media transaction content on the media screen.


The game play system 300 may communicate with the payment host 357 to effect a game play purchase by the user 301. The game play system 300 may also communicate with the financial payment processor 330 or the game play system payment processor 318 to effect the game play purchase transaction. The game play system 300 is communication with the payment host 357. The payment host 357 is in communication with the transaction processing server 316. Thus, the transaction processing server 316 receives the payment card number from the payment host 357. The transaction processing server 316 also may provide instructions to the payment host 357 for directing the display of game-related content on the user interface 307.


Further, gaming rule provisioning may be conducted wholly at the game play system 300, wholly at the payment host 357, or at a combination of the game play system 300 and the payment host 357. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 300 may further direct or control the content displayed at a user interface 307 of the payment-enabled terminal 303 through the payment host 357. Generally speaking, the presentment of content displayed at the user interface 307 may be all or partially directed by the game play system 300, or may be all or partially directed by the payment host 357 associated with the payment-enabled terminal 303, or may be a combination of payment host 357 presentment of content and game play system 300 presentment of content. Further, presenting content to the user at the payment-enabled terminal 303 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 3C is a schematic diagram illustrating a game play system 300 in communication with another embodiment of the grocery payment system 352. The grocery payment system 352 includes a networked register 390, payment-enabled terminal 303, a store server 358, an electronic payment system 355, and a financial payment processor 330. The payment-enabled terminal 303 is in communication with the store server 358, which communicates with an external electronic payment system 355, which communicates with a financial payment processor 330.


The game play system 300 may communicate with the in-store server 358 to effect a game play purchase by the user 301. In other embodiments, the game play system 300 may communicate with the electronic payment system 355 or the financial payment processor 330 to effect a game play purchase by the user 301. The game play system 300 may also communicate with the financial payment processor 330 or the game play system payment processor 318 to effect the game play purchase transaction. The game play system 300 is communication with the in-store server 358. The in-store server 358 is in communication with the transaction processing server 316. Thus, the transaction processing server 316 receives the payment card number from the in-store server 358. Alternatively, the game play system 300 may receive the payment card numbers from one or more of the electronic payment system 355 and the financial payment processor 330. The transaction processing server 316 also may provide instructions to the in-store server 358 for directing the display of game-related content on the user interface 307.


Further, gaming rule provisioning may be conducted wholly at the game play system 300, wholly at the in-store server 358, or at a combination of the game play system 300 and one or more of the in-store server 358, the electronic payment system 355, and the financial payment processor 330. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 300 may further direct or control the content displayed at a user interface 307 of the payment-enabled terminal 303 through one or more of the in-store server 358, the electronic payment system 355, and the financial payment processor 330. Generally speaking, the presentment of content displayed at the user interface 307 may be all or partially directed by the game play system 300, or may be all or partially directed by one or more of the in-store server 358, the electronic payment system 355, and the financial payment processor 330 associated with the payment-enabled terminal 303, or may be a combination of one or more of the in-store server 358, the electronic payment system 355, and the financial payment processor 330 presentment of content and game play system 300 presentment of content. Further, presenting content to the user at the payment-enabled terminal 303 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 3D is a schematic diagram illustrating a game play system in communication with another embodiment of the grocery payment system 352. The grocery payment system 352 includes a networked register 390, payment-enabled terminal 303, an electronic payment system 355, an electronic payment system host 356, and a financial payment processor 330. The payment-enabled terminal 303 is in communication with the electronic payment system 355, which communicates with an electronic payment system host 356, which communicates with a financial payment processor 330.


The game play system 300 may communicate with the electronic payment system host 356 or with the electronic payment system 355 to effect a game play purchase by the user 301. Thus, the game play system 300 directs the game play purchase via the electronic payment system host 356 or the electronic payment system 355. The game play system 300 may also communicate with the financial payment processor 330 or the game play system payment processor 318 to effect the game play purchase transaction. The game play system 300 is communication with the electronic payment system host 356 or with the electronic payment system 355. The electronic payment system host 356 is located remotely from and in communication with the electronic payment system 355 associated with the in-lane grocery payment system 352. The electronic payment system host 356 is in communication with the transaction processing server 316. Thus, the transaction processing server 316 receives the payment card number from the electronic payment system host 356 or from the electronic payment system 355. The transaction processing server 316 also may provide instructions to the electronic payment system host 356 or the electronic payment system 355 for directing the display of game-related content on the user interface 307.


Further, gaming rule provisioning may be conducted wholly at the game play system 300, wholly at one or more of the electronic payment system host 356 or the electronic payment system 355, or at a combination of the game play system 300 and one or more of the electronic payment system host 356 or the electronic payment system 355. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 300 may further direct or control the content displayed at a user interface 307 of the payment-enabled terminal 303 through one or more of the electronic payment system host 356 or the electronic payment system 355. Generally speaking, the presentment of content displayed at the user interface 307 may be all or partially directed by the game play system 300, or may be all or partially directed by one or more of the electronic payment system host 356 or the electronic payment system 355 associated with the payment-enabled terminal 303, or may be a combination of one or more of the electronic payment system host 356 or the electronic payment system 355 presentment of content and game play system 300 presentment of content. Further, presenting content to the user at the payment-enabled terminal 303 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 3E is a schematic diagram illustrating a game play system 300 in communication with a cloud-based embodiment of a grocery payment system 352. The grocery payment system 352 may include a register 390, payment enabled terminal 303, and a transmitter-receiver 390. The transmitter-receiver 390 may send and receive communications to and from a cloud-based media server 360, a cloud e-commerce platform 340, and a financial payment processor 330 to effect a grocery payment transaction. The transmitter-receiver 390 may further be in communication with the game play system 300. The game play system 300 may also be in communication with the cloud-based media server 360, the cloud e-commerce platform 340, and/or the financial payment processor 330.


The game play system 300 receives the payment card number from the transmitter-receiver 390 either directly or indirectly through one or more of the cloud media server 360, cloud e-commerce platform 340, and financial payment processor 330. Thus, game play system 300 may communicate with the payment-enabled terminal 303 via the cloud to effect a game play purchase.



FIG. 4A is a schematic diagram illustrating a game play system in communication with a self-service grocery payment system 453. The game play system 400 may include a game play data center 410 having a game play transaction database 412 for storing game play records 414 and one or more game play transaction processing servers 416 in communication with the transaction database 412.


The game play data center 410 is in communication with a gaming operator 420 having one or more gaming operator servers 426. The gaming operator servers (see, e.g., FIG. 1A) are operable to generate game play number sets, and the transaction processing server 416 receives a game play number set for a given game play transaction from the gaming operator 420. In an embodiment, the gaming operator is part of the game play system 400, and includes one or more gaming operator servers in communication with the game play transaction processing servers 416 over an intersystem network. In another embodiment, the gaming operator 420 is located remotely from the game play system 400 and is in communication with the game play transaction processing servers 416 over a secure network connection. In either embodiment, the game play transaction processing servers 416 are operable to receive information from the gaming operator 420 and/or gaming operator servers relating to a game play transaction.


In some embodiments, the game play system 400 further comprises a game play system payment processor 418 in communication with the game play data center 410. The game play system payment processor 418 may conduct a financial transaction associated with the game play purchase independent of the financial payment processor 430, upon receiving communications from the game play transaction processing servers 416 to that effect. In other embodiments, the game play system 400 communicates with the financial payment processor 430 to initiate a financial transaction associated with the game play purchase.


The self-service grocery payment system 453 may include a payment-enabled terminal 403, an in-store point of sale 446, an electronic payment system host 455, and financial payment processor 430. The self-service grocery payment system 453 may further include a kiosk server 459 in communication with the user interface 407. In an embodiment, the user interface 407 is a media screen, and the kiosk server 459 provides media content for display on the media screen.


The payment-enabled terminal may be a self-service kiosk, and the transaction processing server 416 may receive the payment card number from the kiosk server 459 in communication with the self service kiosk. In an embodiment, the kiosk server 459 is connected with the self-service kiosk through a local grocery store network 491, and the transaction processing server 416 communicates with the kiosk server 459 through a firewall 492 associated with the local grocery store network 491.


Thus, the transaction processing server 416 of the game play system 400 may receive the payment card number from the kiosk server 459. The payment-enabled terminal 403 may include a user interface 407 for interacting with a user 401 and swipe 405 for reading a user payment card. Thus, the payment card number may be identified when the user 401 swipes its payment card at the payment-enabled terminal 403, or when a payment card number is otherwise determined (e.g., via “tap” of a mobile device or NFC communication) at the payment-enabled terminal 403. The payment-enabled terminal 403 may further include a pin pad 409. In an embodiment, the user interface 407 comprises a media screen. The media screen may display media content guiding the user 401 through a game play purchase, and the media content may be received from the kiosk server 459 in communication with the transaction processing server 416. The game play system 400 may also be in communication with the POS 446, e-payment system host 455 and/or the financial payment processor 430, and the game play transaction servers 416 may receive the payment card number from any of the POS 446, e-payment system host 455 and/or the financial payment processor 430.


As discussed above in relation to FIGS. 1A and 1B, gaming rule provisioning may be conducted wholly at the game play system 400, wholly at the fuel payment system 453 associated with the payment-enabled terminal 403 (or the payment-enabled terminal 403 itself), or at a combination of the game play system 400 and the fuel payment system 453. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 400 may further direct or control the content displayed at a user interface 407 of the payment-enabled terminal 403. Generally speaking, the presentment of content displayed at the user interface 407 may be all or partially directed by the game play system 400, or may be all or partially directed by the fuel payment system 453 associated with the payment-enabled terminal 403, or may be a combination of fuel payment system 453 presentment of content and game play system 400 presentment of content. Further, presenting content to the user at the payment-enabled terminal 403 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 4B is a schematic diagram illustrating a game play system 300 in communication with a cloud-based embodiment of a kiosk system 453. The kiosk system 453 may include a kiosk with user interface 407, payment enabled terminal 403, store server 459, and/or a transmitter-receiver 490. The transmitter-receiver 490 may send and receive communications to and from a cloud-based media server 460, a cloud e-commerce platform 440, and a financial payment processor 430 to effect a grocery payment transaction. The transmitter-receiver 490 may further be in communication with the game play system 400. The game play system 400 may also be in communication with the cloud-based media server 460, the cloud e-commerce platform 440, and/or the financial payment processor 430.


The game play system 400 receives the payment card number from the transmitter-receiver 490 either directly or indirectly through one or more of the cloud media server 460, cloud e-commerce platform 440, and financial payment processor 430. Thus, game play system 400 may communicate with the payment-enabled terminal 403 via the cloud to effect a game play purchase.



FIG. 5 is a schematic diagram illustrating a game play system in communication with an electronic tablet payment system 570. The game play system 500 may include a game play data center 510 having a game play transaction database 512 for storing game play records 514 and one or more game play transaction processing servers 516 in communication with the transaction database 512.


The game play data center 540 is in communication with a gaming operator 520 having one or more gaming operator servers (see, e.g. FIG. 1A). The gaming operator servers are operable to generate game play number sets, and the transaction processing server 516 receives a game play number set for a given game play transaction from the gaming operator 520. In an embodiment, the gaming operator is part of the game play system 500, and includes one or more gaming operator servers in communication with the game play transaction processing servers 516 over an intersystem network. In another embodiment, the gaming operator 520 is located remotely from the game play system 500 and is in communication with the game play transaction processing servers 516 over a secure network connection. In either embodiment, the game play transaction processing servers 516 are operable to receive information from the gaming operator 520 and/or gaming operator servers relating to a game play transaction.


In some embodiments, the game play system 500 further comprises a game play system payment processor 518 in communication with the game play data center 510. The game play system payment processor 518 may conduct a financial transaction associated with the game play purchase independent of the financial payment processor 530, upon receiving communications from the game play transaction processing servers 516 to that effect. In other embodiments, the game play system 500 communicates with the financial payment processor 530 to initiate a financial transaction associated with the game play purchase.


The electronic tablet payment system 570 may include a payment-enabled terminal 503, local tablet server 572, a gateway 594, and financial payment processor 530. The local tablet server 572 is in communication with the user interface 507 of the payment-enabled terminal 503. In an embodiment, the payment-enabled terminal 503 comprises an electronic tablet 571 and a swipe 505. The payment-enabled terminal 503 may further comprise a pin pad 509. In an embodiment, the user interface 507 is a media screen, and the local tablet server 572 provides media content for display on the media screen.


The transaction processing server 516 may receive the payment card number from the local tablet server 572 in communication with the electronic tablet 571. In an embodiment, the local tablet server 572 is connected with the electronic tablet 571 through a local network, and the transaction processing server 516 communicates with the local tablet server 572. Thus, the transaction processing server 516 may receive the payment card number from the electronic tablet payment system 570. The transaction processing server 516 may receive the payment card number from the swipe enabled terminal 503, the local server 572, the gateway 594, and/or the financial payment processor 530.


Thus, the transaction processing server 516 of the game play system 500 may receive the payment card number from the local tablet server 572. The payment-enabled terminal 503 may include a user interface 507 for interacting with a user 501 and swipe 505 for reading a user payment card. Thus, the payment card number may be identified when the user 501 swipes its payment card at the payment-enabled terminal 503, or when a payment card number is otherwise determined (e.g., via “tap” of a mobile device or NFC communication) at the payment-enabled terminal 503. The media screen may display media content guiding the user 501 through a game play purchase, and the media content may be received from the local tablet server 572 in communication with the transaction processing server 516.


As discussed above in relation to FIGS. 1A and 1B, gaming rule provisioning may be conducted wholly at the game play system 500, wholly at the fuel payment system 570 associated with the payment-enabled terminal 503 (or the payment-enabled terminal 503 itself), or at a combination of the game play system 500 and the fuel payment system 570. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 500 may further direct or control the content displayed at a user interface 507 of the payment-enabled terminal 503. Generally speaking, the presentment of content displayed at the user interface 507 may be all or partially directed by the game play system 500, or may be all or partially directed by the fuel payment system 570 associated with the payment-enabled terminal 503, or may be a combination of fuel payment system 570 presentment of content and game play system 500 presentment of content. Further, presenting content to the user at the payment-enabled terminal 503 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 6A is a schematic diagram illustrating a game play system 600 in communication with an electronic tablet payment system 680. The game play system 600 may include a game play data center 610 having a game play transaction database 612 for storing game play records 614 and one or more game play transaction processing servers 616 in communication with the transaction database 612.


The game play data center 610 is in communication with a gaming operator 620 having one or more gaming operator servers (see, e.g., FIG. 1A). The gaming operator servers are operable to generate game play number sets, and the transaction processing server 616 receives a game play number set for a given game play transaction from the gaming operator 620. In an embodiment, the gaming operator is part of the game play system 600, and includes one or more gaming operator servers in communication with the game play transaction processing servers 616 over an intersystem network. In another embodiment, the gaming operator 620 is located remotely from the game play system 600 and is in communication with the game play transaction processing servers 616 over a secure network connection. In either embodiment, the game play transaction processing servers 616 are operable to receive information from the gaming operator 620 and/or gaming operator servers relating to a game play transaction.


In some embodiments, the game play system 600 further comprises a game play system payment processor 618 in communication with the game play data center 610. The game play system payment processor 618 may conduct a financial transaction associated with the game play purchase independent of the financial payment processor 630, upon receiving communications from the game play transaction processing servers 616 to that effect. In other embodiments, the game play system 600 communicates with the financial payment processor 630 to initiate a financial transaction associated with the game play purchase.


The electronic tablet payment system 680 may include a payment-enabled terminal 603, gateway 694, financial payment processor 630, and local tablet server 682. The local tablet server 682 is in communication with the user interface 607 of the payment-enabled terminal 603. In an embodiment, the payment-enabled terminal 603 comprises an electronic tablet 681 and a swipe 605. In an embodiment, the user interface 607 is a media screen, and the local tablet server 682 provides media content for display on the media screen.


The transaction processing server 616 may receive the payment card number from the electronic tablet 681 in communication with the local tablet server 682. In an embodiment, the local tablet server 682 is connected with the electronic tablet 671 through a local network, and the transaction processing server 616 communicates with the electronic tablet 681. Thus, the transaction processing server 616 may receive the payment card number from the electronic tablet 681. In other embodiments, the transaction processing server 616 may receive the payment card number from the gateway 694 or financial payment processor 630.


Thus, the transaction processing server 616 of the game play system 600 may receive the payment card number from the electronic tablet system 680. The payment-enabled terminal 603 may include a user interface 607 for interacting with a user 601 and swipe 605 for reading a user payment card. Thus, the payment card number may be identified when the user 601 swipes its payment card at the payment-enabled terminal 603, or when a payment card number is otherwise determined (e.g., via “tap” of a mobile device or NFC communication) at the payment-enabled terminal 603. The media screen may display media content guiding the user 601 through a game play purchase, and the media content may be provided to the electronic tablet 681 by the local tablet server 682, the game play transaction processing server 616, or a combination of both.


As discussed above in relation to FIGS. 1A and 1B, gaming rule provisioning may be conducted wholly at the game play system 600, wholly at the fuel payment system 680 associated with the payment-enabled terminal 603 (or the payment-enabled terminal 603 itself), or at a combination of the game play system 600 and the fuel payment system 680. Further, the gaming provisioning may be done substantially in real-time, based on predetermined logic or rules that are regularly updated, or a combination of both. The game play system 600 may further direct or control the content displayed at a user interface 607 of the payment-enabled terminal 603. Generally speaking, the presentment of content displayed at the user interface 607 may be all or partially directed by the game play system 600, or may be all or partially directed by the fuel payment system 680 associated with the payment-enabled terminal 603, or may be a combination of fuel payment system 680 presentment of content and game play system 600 presentment of content. Further, presenting content to the user at the payment-enabled terminal 603 may be done substantially in real-time, based on predetermined logic that is regularly updated, or a combination of both.



FIG. 6B is a schematic diagram illustrating a game play system 600 in communication with a cloud-based embodiment of a electronic tablet payment system 680. The electronic tablet payment system 680 may include a kiosk with user interface 607, payment enabled terminal 603, local server 682, and/or a transmitter-receiver 690. The transmitter-receiver 690 may send and receive communications to and from a cloud-based media server 660, a cloud e-commerce platform 640, and a financial payment processor 630 to effect a grocery payment transaction. The transmitter-receiver 690 may further be in communication with the game play system 600. The game play system 600 may also be in communication with the cloud-based media server 660, the cloud e-commerce platform 640, and/or the financial payment processor 630.


The game play system 600 receives the payment card number from the transmitter-receiver 690 either directly or indirectly through one or more of the cloud media server 460, cloud e-commerce platform 640, and financial payment processor 630. Thus, game play system 600 may communicate with the payment-enabled terminal 603 via the cloud to effect a game play purchase.



FIG. 7 is a flow diagram illustrating a game play purchase process 700 in the game play system. The game play purchase is made by a user at a payment-enabled terminal. The game play purchase process 700 may include receiving, at a game play transaction processing server, a game play purchase request (action 702). The game play purchase request may include a payment card number.


The game play purchase process 700 may also include determining a game play number set in response to the game play purchase request (action 704). The determining may further include requesting a game play number set (action 706) from a gaming operator and receiving the game play number set (action 708) from the gaming operator. Thus, determining the game play number set may include receiving the game play number set from a remote gaming operator. Alternatively, the determining the game play number set may include generating the game play number set at one or more gaming operator servers in communication with the game play transaction processing server over a local network. Thus, the determining may be done locally at a gaming operator server in communication with the game play transaction processing server.


The game play purchase process 700 may also include associating, at the transaction processing server, the payment card number with the game play number set (action 710). The game play purchase process 700 may also include storing, at a game play transaction database, the associated payment card number and game play number set (action 712).


The receiving (action 702) may include receiving the game play purchase request may include receiving the payment card number from a fuel pump system; receiving the payment card number from a grocery payment system; and/or receiving the payment card number from an electronic tablet payment system.


The game play purchase process 700 may further include determining, at the transaction processing server, gaming rules associated with a jurisdiction associated with the payment-enabled terminal by referencing gaming rules stored in the transaction database. The game play purchase 700 process may further include provisioning the gaming rules after receiving the game play purchase request. (Not shown.) The provisioning may include administering age, payment card, responsible game play, and/or time restrictions.


The game play purchase process 700 may allow for effecting ticketless game plays by associating the payment card number with the game play number set. The game play purchase process 700 may also allow for managing ticketless game plays by storing the plurality of records of game play number sets associated with respective payment card numbers at the transaction database. The game play purchase process 700 may also allow for effecting automatic winner redemption by initiating payment to an account associated with a payment card number associated with a winning game play number set. Further, the game play purchase process 700 may allow for managing second chance game plays based on the plurality of records of game play number sets associated with respective payment card numbers stored at the transaction database. Pre-registration is not required for second chance games, as the second chance player may be associated with its payment card number. The payment card number used in the game play purchase process 700 may be a credit or debit card number.


Various aspects, features, and functionality relating to game play purchases in the game play system and/or using the game play methods are discussed in further detail in commonly-assigned U.S. patent application Ser. Nos. 11/734,207, 13/280,196, 61/593,762, 61/696,533, Ser. Nos. 13/757,512, and 13/829,776, which are each herein incorporated by reference for all purposes.



FIG. 8 is a flow diagram illustrating an automatic redemption process 800 for a winning game play purchase in the game play system. The automatic redemption process 800 may include determining, at a game play transaction processing server, one or more winning game play number sets (action 802). The automatic redemption process 800 may further include querying a game play transaction database for the one or more winning game play number sets (action 804). The game play transaction database includes a plurality of records of game play number sets associated with respective payment card numbers.


The automatic redemption process 800 may further include determining whether a winner exists (action 806). For example, if a record in the plurality of records of game play number sets associated with respective payment card numbers matches the one or more winning game play number sets, a winner is determined (YES), and the automatic redemption process 800 may further include determining a payment card number associated with the matching record (action 808), and initiating a redemption payment using the payment card number (action 810). Initiating a redemption payment (action 810) may include initiating payment to an account associated with the payment card number. If a record in the plurality of records of game play number sets associated with respective payment card numbers does not match the one or more winning game play number sets, a winner is not determined (NO), and the process 800 ends for a particular gaming instance. The process 800 may be repeated for other gaming instances—for example, other games in a given jurisdiction, other dates, other jurisdictions, etc.


Various aspects, features, and functionality relating to redemption in the game play system and/or using the game play methods are discussed in further detail in commonly-assigned U.S. patent application Ser. Nos. 11/734,207, 13/280,196, 61/593,762, 61/696,533, Ser. Nos. 13/757,512, and 13/829,776, which are each herein incorporated by reference for all purposes.


While various embodiments in accordance with the disclosed principles have been described above, it should be understood that they have been presented by way of example only, and are not limiting. Thus, the breadth and scope of the invention(s) should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the claims and their equivalents issuing from this disclosure. Furthermore, the above advantages and features are provided in described embodiments, but shall not limit the application of such issued claims to processes and structures accomplishing any or all of the above advantages.


Additionally, the section headings herein are provided for consistency with the suggestions under 37 C.F.R. 1.77 or otherwise to provide organizational cues. These headings shall not limit or characterize the invention(s) set out in any claims that may issue from this disclosure. Specifically and by way of example, although the headings refer to a “Technical Field,” such claims should not be limited by the language chosen under this heading to describe the so-called technical field. Further, a description of a technology in the “Background” is not to be construed as an admission that technology is prior art to any invention(s) in this disclosure. Neither is the “Summary” to be considered as a characterization of the invention(s) set forth in issued claims. Furthermore, any reference in this disclosure to “invention” in the singular should not be used to argue that there is only a single point of novelty in this disclosure. Multiple inventions may be set forth according to the limitations of the multiple claims issuing from this disclosure, and such claims accordingly define the invention(s), and their equivalents, that are protected thereby. In all instances, the scope of such claims shall be considered on their own merits in light of this disclosure, but should not be constrained by the headings herein.

Claims
  • 1. A processing system configured to: receive, from a terminal, identification information associated with a user, wherein the receipt of the identification information is caused by an identification operation performed by at least one of the terminal or the processing system located away from the terminal;determine gaming rules associated with a physical jurisdiction associated with the terminal, wherein the gaming rules are provisioned in response to receiving a game play request at or from the terminal, wherein a first portion of the gaming rules is provisioned at or by the terminal, and wherein a second portion of the gaming rules is provisioned at or by the processing system located away from the terminal;determine, based on at least one of the first portion of the gaming rules or the second portion of the gaming rules, whether the user associated with the identification information is eligible to participate in a game associated with the physical jurisdiction; andin response to determining the user associated with the identification information is eligible to participate in the game associated with the physical jurisdiction, enable participation of the user associated with the identification information in the game associated with the physical jurisdiction, wherein presentation of game content associated with the game at the terminal is controlled by control data associated with at least one of the terminal or the processing system, wherein the presentation of the game content associated with the game at the terminal is further based on an attribute of the terminal, and wherein first game content for the game presented at a first terminal associated with a first location is different from second game content for the game presented at a second terminal at a second location.
  • 2. The processing system of claim 1, wherein the game is associated with a game play set.
  • 3. The processing system of claim 1, wherein the game is presented on the terminal or on a second terminal.
  • 4. The processing system of claim 1, wherein content associated with the game is presented on a user interface of the terminal and is at least partially directed or controlled by the processing system.
  • 5. The processing system of claim 1, wherein the terminal is associated with or comprised in at least one of a gas or fuel pump, a retail terminal, a kiosk, or a mobile device.
  • 6. The processing system of claim 1, wherein the game comprises a lottery game.
  • 7. The processing system of claim 1, wherein the game comprises a non-lottery game.
  • 8. The processing system of claim 1, wherein the attribute of the terminal further comprises at least one of a display capability of the terminal, or a capability of connecting the terminal to a network.
  • 9. The processing system of claim 1, wherein logic for the presentation of the game content is updated based on the attribute of the terminal or based on a connection between the processing system and the terminal.
  • 10. A method comprising: receiving, from a terminal, identification information associated with a user, wherein the receipt of the identification information is caused by an identification operation performed by at least one of the terminal or a remote processing system located away from the terminal;determining gaming rules associated with a physical jurisdiction associated with the terminal, wherein the gaming rules are provisioned in response to receiving a game play request at or from the terminal, wherein a first portion of the gaming rules is provisioned at or by the terminal, and wherein a second portion of the gaming rules is provisioned at or by the remote processing system located away from the terminal;determining, based on at least one of the first portion of the gaming rules or the second portion of the gaming rules, whether the user associated with the identification information is eligible to participate in a game associated with the physical jurisdiction; andin response to determining the user associated with the identification information is eligible to participate in the game associated with the physical jurisdiction, enabling participation of the user associated with the identification information in the game associated with the physical jurisdiction, wherein presentation of game content associated with the game at the terminal is controlled by control data associated with at least one of the terminal or the remote processing system, wherein first game content for a first game presented at a first terminal associated with a first location is different from second game content for a second game presented at a second terminal at a second location.
  • 11. The method of claim 10, wherein the game is presented on the terminal or on a second terminal.
  • 12. The method of claim 10, wherein content associated with the game is presented on a user interface of the terminal and is at least partially directed or controlled by the remote processing system.
  • 13. The method of claim 10, wherein the terminal is associated with or comprised in a at least one of a gas or fuel pump, a retail terminal, a kiosk, or a mobile device.
  • 14. The method of claim 10, wherein the game comprises a lottery game.
  • 15. The method of claim 10, wherein the game comprises a non-lottery game.
  • 16. The method of claim 10, wherein the determination of whether the user associated with the identification information is eligible to participate in the game associated with the physical jurisdiction is performed by at least one of the remote processing system or the terminal.
  • 17. The method of claim 10, further comprising receiving the game play request from the terminal.
  • 18. The method of claim 10, wherein the game is associated with a game play set.
  • 19. The method of claim 10, further comprising initiating the presentation of the game on the terminal or on a second terminal.
  • 20. The method of claim 19, further comprising initiating the presentation of the game on the terminal or the second terminal based on at least one of a display capability of the terminal, or a capability of connecting the terminal to a network.
CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation application of U.S. patent application Ser. No. 13/842,709, which was filed on Mar. 15, 2013, and issued as U.S. Pat. No. 10,115,268 on Oct. 30, 2018, which application is incorporated herein by reference in its entirety for all purposes.

US Referenced Citations (322)
Number Name Date Kind
4669730 Small Jun 1987 A
4815741 Small Mar 1989 A
4833307 Gonzalez-Justiz May 1989 A
5083272 Walker et al. Jan 1992 A
5216595 Protheroe Jun 1993 A
5239165 Novak Aug 1993 A
5330185 Wells Jul 1994 A
5383113 Kight et al. Jan 1995 A
5417424 Snowden et al. May 1995 A
5590038 Pitroda Dec 1996 A
5699528 Hogan Dec 1997 A
5708780 Levergood et al. Jan 1998 A
5873072 Kight et al. Feb 1999 A
5884271 Pitroda Mar 1999 A
5890718 Byon Apr 1999 A
5897625 Gustin et al. Apr 1999 A
5919091 Bell et al. Jul 1999 A
5991413 Arditti et al. Nov 1999 A
5991749 Morrill, Jr. Nov 1999 A
6000608 Dorf Dec 1999 A
6021397 Jones et al. Feb 2000 A
6029151 Nikander Feb 2000 A
6055567 Ganesan et al. Apr 2000 A
6062472 Cheung May 2000 A
6070150 Remington et al. May 2000 A
6085242 Chandra Jul 2000 A
6142369 Jonstromer Nov 2000 A
6169890 Vatanen Jan 2001 B1
6175823 Dusen Jan 2001 B1
6185545 Resnick et al. Feb 2001 B1
6240397 Sachs May 2001 B1
6267670 Walker et al. Jul 2001 B1
6277026 Archer Aug 2001 B1
6289322 Kitchen et al. Sep 2001 B1
6304860 Martin, Jr. et al. Oct 2001 B1
6322446 Yacenda Nov 2001 B1
6324525 Kramer et al. Nov 2001 B1
6327577 Garrison et al. Dec 2001 B1
6334116 Ganesan et al. Dec 2001 B1
6360254 Linden et al. Mar 2002 B1
6363362 Burfield et al. Mar 2002 B1
6363364 Nel Mar 2002 B1
6364206 Keohane Apr 2002 B1
6366893 Hannula et al. Apr 2002 B2
6442532 Kawan Aug 2002 B1
6507823 Nel Jan 2003 B1
6529956 Smith et al. Mar 2003 B1
6585589 Okuniewicz Jul 2003 B2
6594644 Dusen Jul 2003 B1
6609113 O'Leary et al. Aug 2003 B1
6622015 Himmel et al. Sep 2003 B1
6678664 Ganesan Jan 2004 B1
6684269 Wagner Jan 2004 B2
6705520 Pitroda et al. Mar 2004 B1
6769607 Pitroda et al. Aug 2004 B1
6805289 Noriega et al. Oct 2004 B2
6807410 Pailles et al. Oct 2004 B1
6819219 Bolle et al. Nov 2004 B1
6836765 Sussman Dec 2004 B1
6839692 Carrott et al. Jan 2005 B2
6839744 Kloba et al. Jan 2005 B1
6848613 Nielsen et al. Feb 2005 B2
6856974 Ganesan et al. Feb 2005 B1
6868391 Hultgren Mar 2005 B1
6869358 Yacenda Mar 2005 B2
6899621 Behm et al. May 2005 B2
6918537 Graves et al. Jul 2005 B2
6925439 Pitroda Aug 2005 B1
6932268 McCoy et al. Aug 2005 B1
6934529 Bagoren et al. Aug 2005 B2
6934689 Ritter et al. Aug 2005 B1
6941270 Hannula Sep 2005 B1
6948063 Ganesan et al. Sep 2005 B1
6988657 Singer et al. Jan 2006 B1
7014107 Singer et al. Mar 2006 B2
7024396 Woodward Apr 2006 B2
7054842 James et al. May 2006 B2
7072854 Loeser Jul 2006 B2
7083084 Graves et al. Aug 2006 B2
7085931 Smith et al. Aug 2006 B1
7086584 Stoutenburg et al. Aug 2006 B2
7093761 Smith et al. Aug 2006 B2
7128274 Kelley et al. Oct 2006 B2
7130817 Karas et al. Oct 2006 B2
7165052 Diveley et al. Jan 2007 B2
7166616 Carnation Jan 2007 B2
7168616 Carnation Jan 2007 B2
7177428 Gordon et al. Feb 2007 B2
7182252 Cooper et al. Feb 2007 B1
7209889 Whitfield Apr 2007 B1
7216092 Weber et al. May 2007 B1
7222101 Bishop et al. May 2007 B2
7229006 Babbi et al. Jun 2007 B2
7229014 Snyder Jun 2007 B1
7249097 Hutchison et al. Jul 2007 B2
7316350 Algiene Jan 2008 B2
7328190 Smith et al. Feb 2008 B2
7356327 Cai et al. Apr 2008 B2
7383226 Kight et al. Jun 2008 B2
7494417 Walker et al. Feb 2009 B2
7547251 Walker et al. Jun 2009 B2
7690580 Shoemaker Apr 2010 B2
7702542 Aslanian, Jr. Apr 2010 B2
7774209 James et al. Aug 2010 B2
7899706 Stone et al. Mar 2011 B1
7905399 Barnes et al. Mar 2011 B2
8103520 Mueller et al. Jan 2012 B2
8396758 Paradise et al. Mar 2013 B2
8509814 Parker Aug 2013 B1
20010001856 Gould et al. May 2001 A1
20010005840 Verkama Jun 2001 A1
20010007983 Lee Jul 2001 A1
20010011248 Himmel et al. Aug 2001 A1
20010042785 Walker et al. Nov 2001 A1
20010044776 Kight et al. Nov 2001 A1
20020002535 Kitchen et al. Jan 2002 A1
20020010627 Lerat Jan 2002 A1
20020010677 Kitchen et al. Jan 2002 A1
20020013768 Ganesan Jan 2002 A1
20020019809 Kitchen et al. Feb 2002 A1
20020022472 Watler et al. Feb 2002 A1
20020046165 Kitchen et al. Apr 2002 A1
20020046166 Kitchen et al. Apr 2002 A1
20020046167 Kitchen et al. Apr 2002 A1
20020046168 Kitchen et al. Apr 2002 A1
20020049672 Kitchen et al. Apr 2002 A1
20020052840 Kitchen et al. May 2002 A1
20020052841 Guthrie et al. May 2002 A1
20020060243 Janiak et al. May 2002 A1
20020062282 Kight et al. May 2002 A1
20020065773 Kight et al. May 2002 A1
20020065774 Young et al. May 2002 A1
20020077993 Immonen et al. Jun 2002 A1
20020094858 Yacenda Jul 2002 A1
20020095387 Sosa et al. Jul 2002 A1
20020111906 Garrison et al. Aug 2002 A1
20020116329 Serbetcioglu et al. Aug 2002 A1
20020116531 Chu Aug 2002 A1
20020120571 Maung et al. Aug 2002 A1
20020128968 Kitchen et al. Sep 2002 A1
20020138450 Kremer Sep 2002 A1
20020145039 Carroll Oct 2002 A1
20020152123 Giordano et al. Oct 2002 A1
20020152160 Allen-Rouman et al. Oct 2002 A1
20020152179 Racov Oct 2002 A1
20020153414 Stoutenburg et al. Oct 2002 A1
20020169713 Chang et al. Nov 2002 A1
20020178062 Wright et al. Nov 2002 A1
20020190123 Anvekar et al. Dec 2002 A1
20030004802 Callegari Jan 2003 A1
20030004891 Rensburg et al. Jan 2003 A1
20030023552 Kight et al. Jan 2003 A1
20030055735 Cameron et al. Mar 2003 A1
20030074328 Schiff et al. Apr 2003 A1
20030115126 Pitroda Jun 2003 A1
20030162565 Al-Khaja Aug 2003 A1
20030191711 Jamison et al. Oct 2003 A1
20030200184 Dominguez et al. Oct 2003 A1
20030212601 Silva et al. Nov 2003 A1
20030218062 Noriega et al. Nov 2003 A1
20030218066 Fernandes et al. Nov 2003 A1
20030220884 Choi et al. Nov 2003 A1
20030226042 Fukushima Dec 2003 A1
20030229590 Byrne et al. Dec 2003 A1
20030233317 Judd Dec 2003 A1
20030233318 King et al. Dec 2003 A1
20030234819 Daly et al. Dec 2003 A1
20030236749 Shergalis Dec 2003 A1
20040010462 Moon et al. Jan 2004 A1
20040019564 Goldthwaite et al. Jan 2004 A1
20040019568 Moenickheim et al. Jan 2004 A1
20040029569 Khan et al. Feb 2004 A1
20040049456 Dreyer Mar 2004 A1
20040049458 Kunugi et al. Mar 2004 A1
20040059671 Nozaki et al. Mar 2004 A1
20040064409 Kight et al. Apr 2004 A1
20040068446 Do et al. Apr 2004 A1
20040068448 Kim Apr 2004 A1
20040078327 Frazier et al. Apr 2004 A1
20040083170 Bam et al. Apr 2004 A1
20040083171 Kight et al. Apr 2004 A1
20040093305 Kight et al. May 2004 A1
20040094624 Fernandes et al. May 2004 A1
20040107170 Labrou et al. Jun 2004 A1
20040117302 Weichert et al. Jun 2004 A1
20040118914 Smith et al. Jun 2004 A1
20040128197 Bam et al. Jul 2004 A1
20040139005 Ganesan Jul 2004 A1
20040159700 Khan et al. Aug 2004 A1
20040162058 Mottes Aug 2004 A1
20040167853 Sharma Aug 2004 A1
20040181463 Goldthwaite et al. Sep 2004 A1
20040193464 Szrek et al. Sep 2004 A1
20040199431 Ganesan et al. Oct 2004 A1
20040199474 Ritter Oct 2004 A1
20040215560 Amalraj et al. Oct 2004 A1
20040215564 Lawlor et al. Oct 2004 A1
20040225560 Lewis et al. Nov 2004 A1
20040230489 Goldthwaite et al. Nov 2004 A1
20040242208 Teicher Dec 2004 A1
20040243490 Murto et al. Dec 2004 A1
20040249766 Ganesan et al. Dec 2004 A1
20040259626 Akram Dec 2004 A1
20040267664 Nam et al. Dec 2004 A1
20040267665 Nam et al. Dec 2004 A1
20050015388 Dasgupta et al. Jan 2005 A1
20050054438 Rothschild et al. Mar 2005 A1
20050060261 Remington et al. Mar 2005 A1
20050065876 Kumar Mar 2005 A1
20050071179 Peters et al. Mar 2005 A1
20050071269 Peters Mar 2005 A1
20050075958 Gonzalez Apr 2005 A1
20050075975 Rosner et al. Apr 2005 A1
20050080634 Kanniainen et al. Apr 2005 A1
20050086164 Kim et al. Apr 2005 A1
20050097038 Yu et al. May 2005 A1
20050103839 Hewel May 2005 A1
20050108096 Burger et al. May 2005 A1
20050109835 Jacoby et al. May 2005 A1
20050125343 Mendelovich Jun 2005 A1
20050125348 Fulton et al. Jun 2005 A1
20050137978 Ganesan et al. Jun 2005 A1
20050143163 Yacenda Jun 2005 A1
20050153779 Ziegler Jul 2005 A1
20050167488 Higgins et al. Aug 2005 A1
20050174975 Mgrdechian et al. Aug 2005 A1
20050177437 Ferrier Aug 2005 A1
20050182714 Nel Aug 2005 A1
20050184145 Law et al. Aug 2005 A1
20050187873 Labrou et al. Aug 2005 A1
20050203844 Ferguson et al. Sep 2005 A1
20050209965 Ganesan Sep 2005 A1
20050211764 Barcelou Sep 2005 A1
20050216583 Cole et al. Sep 2005 A1
20050222925 Jamieson Oct 2005 A1
20050222961 Staib et al. Oct 2005 A1
20050233797 Gilmore et al. Oct 2005 A1
20050247777 Pitroda Nov 2005 A1
20050262017 Kawase et al. Nov 2005 A1
20050269401 Spitzer et al. Dec 2005 A1
20050269402 Spitzer et al. Dec 2005 A1
20050274793 Cantini et al. Dec 2005 A1
20060000900 Fernandes et al. Jan 2006 A1
20060004656 Lee Jan 2006 A1
20060006226 Fitzgerald et al. Jan 2006 A1
20060026070 Sun Feb 2006 A1
20060058011 Vanska et al. Mar 2006 A1
20060074767 Fortney et al. Apr 2006 A1
20060080232 Epps Apr 2006 A1
20060085310 Mylet et al. Apr 2006 A1
20060089160 Othmer Apr 2006 A1
20060089893 Joseph et al. Apr 2006 A1
20060116892 Grimes et al. Jun 2006 A1
20060136334 Atkinson et al. Jun 2006 A1
20060136901 Nichols Jun 2006 A1
20060163343 Changryeol Jul 2006 A1
20060206436 James et al. Sep 2006 A1
20070017976 Peyret et al. Jan 2007 A1
20070030824 Ribaudo et al. Feb 2007 A1
20070055785 Stevens Mar 2007 A1
20070060284 Yacenda Mar 2007 A1
20070060306 Amaitis Mar 2007 A1
20070130085 Zhu Jun 2007 A1
20070156436 Fisher et al. Jul 2007 A1
20070162337 Hawkins et al. Jul 2007 A1
20070175984 Khandaker et al. Aug 2007 A1
20070233615 Tumminaro Oct 2007 A1
20080006685 Rackley, III et al. Jan 2008 A1
20080010190 Rackley, III et al. Jan 2008 A1
20080010191 Rackley, III et al. Jan 2008 A1
20080010192 Rackley, III et al. Jan 2008 A1
20080010193 Rackley, III et al. Jan 2008 A1
20080010196 Rackley, III et al. Jan 2008 A1
20080010204 Rackley, III et al. Jan 2008 A1
20080010215 Rackley, III et al. Jan 2008 A1
20080028395 Motta et al. Jan 2008 A1
20080033817 Billmaier et al. Feb 2008 A1
20080040265 Rackley, III et al. Feb 2008 A1
20080041938 Wise Feb 2008 A1
20080046366 Bemmel et al. Feb 2008 A1
20080052164 Abifaker Feb 2008 A1
20080065485 Hammond et al. Mar 2008 A1
20080071620 Lowe Mar 2008 A1
20080091528 Rampell et al. Apr 2008 A1
20080091545 Jennings et al. Apr 2008 A1
20080097844 Hsu et al. Apr 2008 A1
20080103972 Lanc May 2008 A1
20080114699 Yuan et al. May 2008 A1
20080126145 Rackley, III et al. May 2008 A1
20080139306 Lutnick et al. Jun 2008 A1
20080167060 Moshir et al. Jul 2008 A1
20080167106 Lutnick et al. Jul 2008 A1
20080172331 Graves et al. Jul 2008 A1
20090001159 James et al. Jan 2009 A1
20090042633 Yacenda Feb 2009 A1
20090055296 Nelsen Feb 2009 A1
20090076896 DeWitt et al. Mar 2009 A1
20090137304 Yacenda May 2009 A1
20090144161 Fisher Jun 2009 A1
20090163263 Herndon et al. Jun 2009 A1
20090187491 Bull et al. Jul 2009 A1
20090192928 Abifaker Jul 2009 A1
20090197684 Arezina et al. Aug 2009 A1
20090239657 Ryan et al. Sep 2009 A1
20090298427 Wilkinson et al. Dec 2009 A1
20100063906 Nelsen et al. Mar 2010 A1
20100069136 Safaei et al. Mar 2010 A1
20100082487 Nelsen Apr 2010 A1
20100130172 Vendrow et al. May 2010 A1
20100203943 Hughes Aug 2010 A1
20100293536 Nikitin et al. Nov 2010 A1
20100312636 Coulter et al. Dec 2010 A1
20110034229 Guziel et al. Feb 2011 A1
20110106698 Isaacson et al. May 2011 A1
20110145044 Nelsen et al. Jun 2011 A1
20110282784 Nelsen Nov 2011 A1
20110307377 Nelsen et al. Dec 2011 A1
20130073388 Heath Mar 2013 A1
20130290121 Simakov et al. Oct 2013 A1
20130304561 Warner et al. Nov 2013 A1
20140006268 Roberts et al. Jan 2014 A1
20150278845 Sorem et al. Oct 2015 A1
Foreign Referenced Citations (18)
Number Date Country
0950968 Oct 1999 EP
1519332 Mar 2005 EP
2002318951 Oct 2002 JP
20010106187 Nov 2001 KR
1020010106187 Nov 2001 KR
20040028487 Apr 2004 KR
20040052531 Jun 2004 KR
1020040052502 Jun 2004 KR
20040069294 Aug 2004 KR
20050118609 Dec 2005 KR
20090123444 Dec 2009 KR
2004004280 Jan 2004 WO
2004012118 Feb 2004 WO
2005111882 Nov 2005 WO
2008092034 Jul 2008 WO
20080167060 Jul 2008 WO
20120244930 Sep 2012 WO
2013026997 Feb 2013 WO
Non-Patent Literature Citations (7)
Entry
Extended European search report dated Sep. 23, 2016 from co-pending European application No. ˜] EP14770551.1.
ISA Korea, International Search Report of PCT/US2009/056118, dated Apr. 19, 2010, 3 pages.
ISA Korea, International Search Report of PCT/US2009/058111, dated May 26, 2010, 3 pages.
ISA Korean Intellectual Property Office, International Search Report of PCT/US2010/060875, dated Jul. 29, 2011, 10 pages.
ISA United States Patent and Trademark Office, International Search Report of PCT/US2008/073910, dated Nov. 10, 2008.
Nelsen, D.A. and Arifin, Leslie, “Systems and Methods for Authentication of a Virtual Stored Value Card,” U.S. Appl. No. 12/554,792, filed Sep. 4, 2009, 67 pages.
Nelsen, D.A., “Systems and Methods for Managing and Using a Virtual Card,” U.S. Appl. No. 12/562,091, filed Sep. 17, 2009, 60 pages.
Related Publications (1)
Number Date Country
20190066442 A1 Feb 2019 US
Continuations (1)
Number Date Country
Parent 13842709 Mar 2013 US
Child 16174174 US