IP Library Granted Patent US 12,608,996
Granted Patent B2
US 12,608,996 · App. 18/419,127 · Granted Apr 21, 2026

Digital wallet systems and methods with responsible gaming

Inventors: Christopher Cleveland (Clovis, CA); Ben Vineyard, IV (Las Vegas, NV); Kevin Rowley (Henderson, NV); Samarth Raman (Las Vegas, NV); Abhinav Kant (Delhi, IN); Michael Smith (Las Vegas, NV)
Assignee: Aristocrat Technologies, Inc.
G07F17/3237G06Q20/108G06Q20/36G06Q20/3676G07F17/3223G07F17/3239
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,608,996
App. No.
18/419,127
Granted
Apr 21, 2026
Kind
B2
Abstract

A digital wallet computing system is described including at least one processor in communication with a memory storing instructions. The instructions cause the at least one processor to establish wireless connectivity between a mobile device and an electronic gaming device, the electronic gaming device including a device identifier, receive a funds transfer request from the mobile device, the funds transfer request identifying a funds transfer amount and an external player account, and identify an operator identity based on the device identifier. The instructions also cause the at least one processor to identify a player account, the player account associated with the operator, perform a first withdrawal transaction moving the funds transfer amount from the electronic gaming device to the player account, and in response to the first withdrawal transaction, automatically perform a second withdrawal transaction moving the funds transfer amount from the player account to the external player account.

Claims (75)

1 . A digital wallet computing system comprising:

at least one processor in communication with at least one memory device storing instructions that, when executed, cause the at least one processor to:

establish wireless connectivity between a mobile device of a player and an electronic gaming device, the electronic gaming device including a device identifier;

receive, by a digital wallet application programming interface (API), an initiation of a funds transfer request from the mobile device of the player, the funds transfer request identifying a funds transfer amount and an external player account of the player;

identify an operator identity of an operator based on the device identifier of the electronic gaming device;

identify a player account of the player, the player account associated with the operator; and

based upon receiving the initiation of the funds transfer request at the digital wallet API, cause the digital wallet API to initiate, via a message queue that automatically processes funds transfers between a casino management system (CMS) and an external provider system associated with the external player account by processing messages transmitted between the digital wallet API, the CMS, and the external provider system:

automatically performing a first withdrawal transaction moving the funds transfer amount from the electronic gaming device to the player account associated with the operator via the message queue and the CMS; and

automatically performing a second withdrawal transaction moving the funds transfer amount from the player account associated with the operator to the external player account of the player based upon the first withdrawal transaction via the message queue and the external provider system.

2 . The digital wallet computing system of claim 1 , wherein the instructions further cause the at least one processor to:

determine, in response to the initiation of the funds transfer request, that the player has stopped playing at the electronic gaming device;

determine a remaining credit balance comprising an amount of credits remaining at the electronic gaming device; and

cause the remaining credit balance to be deposited as funds into the external player account.

3 . The digital wallet computing system of claim 1 , wherein the instructions further cause the at least one processor to:

establish wireless connectivity between the mobile device of the player and a second electronic gaming device, the second electronic gaming device including a second device identifier;

receive an initiation of a second funds transfer request from the mobile device of the player, the funds transfer request identifying a second funds transfer amount and the external player account of the player; and

perform a third withdrawal transaction moving the second funds transfer amount from the external player account and causing a credit balance associated with the second funds transfer amount to be established at the second electronic gaming device identified by the second device identifier.

4 . The digital wallet computing system of claim 3 , wherein the instructions further cause the at least one processor to:

determine a responsible gaming limit comprising a threshold amount of funds;

compare the second funds transfer amount to the threshold amount of funds; and

in response to determining that the funds transfer amount is less than the threshold amount of funds, perform the third withdrawal transaction.

5 . The digital wallet computing system of claim 3 , wherein the instructions further cause the at least one processor to:

determine a responsible gaming limit comprising a threshold amount of funds;

determine a difference between an amount of funds withdrawn from the external player account, the amount of funds withdrawn including the second funds transfer amount, and an amount of funds deposited into the external player account over a predetermined period of time; and

in response to determining that the difference satisfies the threshold amount of funds by not exceeding the responsible gaming limit, perform the third withdrawal transaction.

6 . The digital wallet computing system of claim 1 , wherein the initiation of the funds transfer request from the mobile device is a first input, and wherein the instructions further cause the at least one processor to automatically perform the second withdrawal transaction further in response to the first input and without receiving a second input from the mobile device.

7 . The digital wallet computing system of claim 1 , wherein the electronic gaming device is located within a first gaming establishment of a plurality of gaming establishments, the external player account is linked to a plurality of player accounts of the player for the plurality of gaming establishments, and wherein the player account is one of the plurality of player accounts and is directly accessible at the first gaming establishment and is not directly accessible at a second gaming establishment of the plurality of gaming establishments.

8 . A computer-implemented method of providing digital wallet transactions implemented by a processor in communication with a memory device, the method comprising:

establishing wireless connectivity between a mobile device of a player and an electronic gaming device, the electronic gaming device including a device identifier;

receiving, by a digital wallet application programming interface (API), an initiation of a funds transfer request from the mobile device of the player, the funds transfer request identifying a funds transfer amount and an external player account of the player;

identifying an operator identity of an operator based on the device identifier of the electronic gaming device;

identifying a player account of the player, the player account associated with the operator; and

based upon receiving the initiation of the funds transfer request at the digital wallet API, causing the digital wallet API to initiate, via a message queue that automatically processes funds transfers between a casino management system (CMS) and an external provider system associated with the external player account by processing messages transmitted between the digital wallet API, the CMS, and the external provider system:

automatically performing a first withdrawal transaction moving the funds transfer amount from the electronic gaming device to the player account associated with the operator via the message queue and the CMS; and

automatically performing a second withdrawal transaction moving the funds transfer amount from the player account associated with the operator to the external player account of the player based upon the first withdrawal transaction via the message queue and the external provider system.

9 . The method of claim 8 , further comprising:

determining, in response to the initiation of the funds transfer request, that the player has stopped playing at the electronic gaming device;

determining a remaining credit balance comprising an amount of credits remaining at the electronic gaming device; and

causing the remaining credit balance to be deposited as funds into the external player account.

10 . The method of claim 8 , further comprising:

establishing wireless connectivity between the mobile device of the player and a second electronic gaming device, the second electronic gaming device including a second device identifier;

receiving an initiation of a second funds transfer request from the mobile device of the player, the funds transfer request identifying a second funds transfer amount and the external player account of the player; and

performing a third withdrawal transaction moving the second funds transfer amount from the external player account and causing a credit balance associated with the second funds transfer amount to be established at the second electronic gaming device identified by the second device identifier.

11 . The method of claim 10 , further comprising:

determining a responsible gaming limit comprising a threshold amount of funds;

comparing the second funds transfer amount to the threshold amount of funds; and

in response to determining that the funds transfer amount is less than the threshold amount of funds, performing the third withdrawal transaction.

12 . The method of claim 10 , further comprising:

determining a responsible gaming limit comprising a threshold amount of funds;

determining a difference between an amount of funds withdrawn from the external player account, the amount of funds withdrawn including the second funds transfer amount, and an amount of funds deposited into the external player account over a predetermined period of time; and

in response to determining that the difference satisfies the threshold amount of funds by not exceeding the responsible gaming limit, performing the third withdrawal transaction.

13 . At least one non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to:

establish wireless connectivity between a mobile device of a player and an electronic gaming device, the electronic gaming device including a device identifier;

receive, by a digital wallet application programming interface (API), an initiation of a funds transfer request from the mobile device of the player, the funds transfer request identifying a funds transfer amount and an external player account of the player;

identify an operator identity of an operator based on the device identifier of the electronic gaming device;

identify a player account of the player, the player account associated with the operator; and

based upon receiving the initiation of the funds transfer request at the digital wallet API, cause the digital wallet API to initiate, via a message queue that automatically processes funds transfers between a casino management system (CMS) and an external provider system associated with the external player account by processing messages transmitted between the digital wallet API, the CMS, and the external provider system:

automatically performing a first withdrawal transaction moving the funds transfer amount from the electronic gaming device to the player account associated with the operator via the message queue and the CMS; and

automatically performing a second withdrawal transaction moving the funds transfer amount from the player account associated with the operator to the external player account of the player based upon the first withdrawal transaction via the message queue and the external provider system.

14 . The at least one non-transitory computer-readable medium of claim 13 , wherein the instructions further cause the at least one processor to:

establish wireless connectivity between the mobile device of the player and a second electronic gaming device, the second electronic gaming device including a second device identifier;

receive an initiation of a second funds transfer request from the mobile device of the player, the funds transfer request identifying a second funds transfer amount and the external player account of the player; and

perform a third withdrawal transaction moving the second funds transfer amount from the external player account and causing a credit balance associated with the second funds transfer amount to be established at the second electronic gaming device identified by the second device identifier.

15 . The at least one non-transitory computer-readable medium of claim 14 , wherein the instructions further cause the at least one processor to:

determine a responsible gaming limit comprising a threshold amount of funds;

compare the second funds transfer amount to the threshold amount of funds; and

in response to determining that the funds transfer amount is less than the threshold amount of funds, perform the third withdrawal transaction.

16 . The at least one non-transitory computer-readable medium of claim 14 , wherein the instructions further cause the at least one processor to:

determine a responsible gaming limit comprising a threshold amount of funds;

determine a difference between an amount of funds withdrawn from the external player account, the amount of funds withdrawn including the second funds transfer amount, and an amount of funds deposited into the external player account over a predetermined period of time; and

in response to determining that the difference satisfies the threshold amount of funds by not exceeding the responsible gaming limit, perform the third withdrawal transaction.

17 . The at least one non-transitory computer-readable medium of claim 13 , wherein the initiation of the funds transfer request from the mobile device is a first input, and wherein the instructions further cause the at least one processor to automatically perform the second withdrawal transaction further in response to the first input and without receiving a second input from the mobile device.

18 . The at least one non-transitory computer-readable medium of claim 13 , wherein the electronic gaming device is located within a first gaming establishment of a plurality of gaming establishments, the external player account is linked to a plurality of player accounts of the player for the plurality of gaming establishments, and wherein the player account is one of the plurality of player accounts and is directly accessible at the first gaming establishment and is not directly accessible at a second gaming establishment of the plurality of gaming establishments.

19 . The digital wallet computing system of claim 1 , wherein the instructions further cause the at least one processor to cause the digital wallet API to initiate automatically performing the first withdrawal transaction and the second withdrawal transaction by causing the digital wallet API to transmit at least one funds transfer message to the message queue that causes the first withdrawal transaction and the second withdrawal transaction to be performed.

20 . The digital wallet computing system of claim 19 , wherein the instructions further cause the at least one processor to cause the digital wallet API to convert the funds transfer request from a first format to a second format, and wherein the funds transfer message comprises funds transfer data associated with the funds transfer request, the funds transfer data being in the second format.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 23, 2024
From: CLEVELAND, CHRISTOPHER; VINEYARD, BEN, IV; ROWLEY, KEVIN; RAMAN, SAMARTH; KANT, ABHINAV; SMITH, MICHAEL
To: ARISTOCRAT TECHNOLOGIES, INC.
Reel/Frame 066207/0276 →
Continuity (4)
Continuation 17491528 · Sep 30, 2021
Provisional Application 63242990 · Sep 10, 2021
Provisional Application 63112400 · Nov 11, 2020
Related Publication 20240161574A1 · May 16, 2024
References Cited (114)
US 5830067A · Graves · 1998 [cited by applicant]
US 5967895A · Kellen · 1999 [cited by applicant]
US 6183362B1 · Boushy · 2001 [cited by applicant]
US 6306038B1 · Graves · 2001 [cited by applicant]
US 6311976B1 · Yoseloff · 2001 [cited by applicant]
US 6988946B2 · Michaelson · 2006 [cited by applicant]
US 7066815B2 · Walker · 2006 [cited by applicant]
US 7128652B1 · Lavoie · 2006 [cited by applicant]
US 7524244B2 · Walker · 2009 [cited by applicant]
US 7588495B2 · Walker · 2009 [cited by applicant]
US 7727071B2 · Giobbi · 2010 [cited by applicant]
US 7785183B1 · Stockham · 2010 [cited by applicant]
US 7806761B2 · Walker · 2010 [cited by applicant]
US 7815502B2 · Hardy · 2010 [cited by applicant]
US 8475257B2 · Bienvenue · 2013 [cited by applicant]
US 9305427B2 · Walker · 2016 [cited by applicant]
US 9558619B2 · Froy · 2017 [cited by applicant]
US 9659435B2 · Rogers · 2017 [cited by applicant]
US 9659459B2 · Phillips · 2017 [cited by applicant]
US 9922493B2 · Walker · 2018 [cited by applicant]
US 10269209B2 · Miltenberger · 2019 [cited by applicant]
US 10726670B2 · Price · 2020 [cited by applicant]
US 11508217B2 · Harris · 2022 [cited by applicant]
US 20010007815A1 · Philipsson · 2001 [cited by applicant]
US 20020094860A1 · Itkis · 2002 [cited by applicant]
US 20040053694A1 · Rowe · 2004 [cited by applicant]
US 20040082384A1 · Walker · 2004 [cited by applicant]
US 20040148251A1 · Kavoun · 2004 [cited by applicant]
US 20040248645A1 · Blackburn · 2004 [cited by applicant]
US 20050020354A1 · Nguyen · 2005 [cited by examiner]
US 20050059467A1 · Saffari · 2005 [cited by applicant]
US 20050187014A1 · Saffari · 2005 [cited by applicant]
US 20050193209A1 · Saunders · 2005 [cited by applicant]
US 20050250569A1 · Kane · 2005 [cited by applicant]
US 20060154727A1 · Okuniewicz · 2006 [cited by applicant]
US 20060205477A1 · Fisk · 2006 [cited by applicant]
US 20060205481A1 · Dominelli · 2006 [cited by applicant]
US 20060247035A1 · Rowe · 2006 [cited by applicant]
US 20070060237A1 · Rowe · 2007 [cited by applicant]
US 20070202941A1 · Miltenberger · 2007 [cited by applicant]
US 20070259709A1 · Kelly · 2007 [cited by applicant]
US 20070298873A1 · Nguyen · 2007 [cited by applicant]
US 20080009344A1 · Graham · 2008 [cited by examiner]
US 20080150678A1 · Giobbi · 2008 [cited by applicant]
US 20090111560A1 · Davis · 2009 [cited by applicant]
US 20090143128A1 · Cautley · 2009 [cited by applicant]
US 20090275399A1 · Kelly · 2009 [cited by applicant]
US 20090276341A1 · McMahan · 2009 [cited by applicant]
US 20100229108A1 · Gerson · 2010 [cited by applicant]
US 20110009188A1 · Adiraju · 2011 [cited by applicant]
US 20110245943A1 · Agarwal · 2011 [cited by applicant]
US 20110276475A1 · Godejohn · 2011 [cited by examiner]
US 20110287823A1 · Guinn · 2011 [cited by applicant]
US 20120225726A1 · Anderson · 2012 [cited by applicant]
US 20130130766A1 · Harris · 2013 [cited by applicant]
US 20130212008A1 · Edwards · 2013 [cited by examiner]
US 20140221071A1 · Calio · 2014 [cited by applicant]
US 20140256407A1 · Graf · 2014 [cited by applicant]
US 20140274277A1 · Cuddy · 2014 [cited by applicant]
US 20140357354A1 · Gura · 2014 [cited by applicant]
US 20150194020A1 · Lamendola · 2015 [cited by applicant]
US 20150235507A1 · Newton · 2015 [cited by applicant]
US 20150302482A1 · Vagner · 2015 [cited by applicant]
US 20160335855A1 · Ishibashi · 2016 [cited by applicant]
US 20170270493A1 · Lugli · 2017 [cited by applicant]
US 20190188956A1 · Higgins · 2019 [cited by examiner]
US 20190220853A1 · Srinivasan · 2019 [cited by applicant]
US 20200043045A1 · Jurich, Jr. · 2020 [cited by applicant]
US 20200051377A1 · Montenegro · 2020 [cited by applicant]
US 20200099694A1 · Weiss · 2020 [cited by applicant]
US 20200226885A1 · Weaver · 2020 [cited by applicant]
US 20200402353A1 · Higgins · 2020 [cited by applicant]
US 20210134104A1 · Harris · 2021 [cited by applicant]
US 20210233351A1 · Meltzer · 2021 [cited by applicant]
US 20210327189A1 · Jarvis · 2021 [cited by applicant]
US 20220032168A1 · Gupta · 2022 [cited by applicant]
US 20220036692A1 · Gupta · 2022 [cited by applicant]
US 20220270434A1 · Welch · 2022 [cited by applicant]
US 20230137728A1 · Anbazhagan · 2023 [cited by applicant]
US 20240112179A1 · Vineyard, IV · 2024 [cited by applicant]
US 20240249588A1 · Shepherd · 2024 [cited by applicant]
Office Action (Final Rejection) dated May 9, 2024 for U.S. Appl. No. 17/491,291 (pp. 1-15). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Nov. 21, 2024 for U.S. Appl. No. 17/491,291 (pp. 1-8). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Nov. 27, 2024 for U.S. Appl. No. 18/468,405 (pp. 1-9). [cited by applicant]
Office Action (Non-Final Rejection) dated Jun. 24, 2022 for U.S. Appl. No. 17/491,200 (pp. 1-11). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Dec. 27, 2022 for U.S. Appl. No. 17/491,200 (pp. 1-13). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Jan. 19, 2023 for U.S. Appl. No. 17/491,200 (pp. 1-2). [cited by applicant]
Office Action (Non-Final Rejection) dated Dec. 8, 2022 for U.S. Appl. No. 17/443,738 (pp. 1-19). [cited by applicant]
Office Action (Non-Final Rejection) dated Dec. 12, 2022 for U.S. Appl. No. 17/443,745 (pp. 1-9). [cited by applicant]
Office Action (Non-Final Rejection) dated Feb. 21, 2023 for U.S. Appl. No. 17/491,291 (pp. 1-24). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Apr. 13, 2023 for U.S. Appl. No. 17/491,200 (pp. 1-7). [cited by applicant]
Notice of Allowance dated Apr. 13, 2023 for U.S. Appl. No. 17/491,200 (pp. 1-7). [cited by applicant]
Office Action (Final Rejection) dated Apr. 20, 2023 for U.S. Appl. No. 17/443,738 (pp. 1-13). [cited by applicant]
Office Action (Non-Final Rejection) dated Mar. 15, 2023 for U.S. Appl. No. 17/491,523 (pp. 1-29). [cited by applicant]
Office Action (Final Rejection) dated Mar. 24, 2023 for U.S. Appl. No. 17/443,745 (pp. 1-11). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Jun. 23, 2023 for U.S. Appl. No. 17/809,844 (pp. 1-9). [cited by applicant]
Office Action (Non-Final Rejection) dated Jun. 14, 2023 for U.S. Appl. No. 17/491,528 (pp. 1-9). [cited by applicant]
Office Action (Final Rejection) dated Jul. 27, 2023 for U.S. Appl. No. 17/491,291 (pp. 1-31). [cited by applicant]
Office Action (Non-Final Rejection) dated Jul. 28, 2023 for U.S. Appl. No. 17/443,745 (pp. 1-7). [cited by applicant]
Office Action (Non-Final Rejection) dated Sep. 7, 2023 for U.S. Appl. No. 17/443,738 (pp. 1-14). [cited by applicant]
Office Action (Final Rejection) dated Sep. 22, 2023 for U.S. Appl. No. 17/491,523 (pp. 1-37). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Oct. 13, 2023 for U.S. Appl. No. 17/491,528 (pp. 1-8). [cited by applicant]
Office Action (Non-Final Rejection) dated Dec. 5, 2023 for U.S. Appl. No. 17/491,291 (pp. 1-15). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Oct. 24, 2023 for U.S. Appl. No. 17/443,745 (pp. 1-7). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Dec. 19, 2023 for U.S. Appl. No. 17/491,528 (pp. 1-8). [cited by applicant]
Office Action (Final Rejection) dated Feb. 14, 2024 for U.S. Appl. No. 17/443,738 (pp. 1-14). [cited by applicant]
Office Action (Non-Final Rejection) dated Jul. 3, 2024 for U.S. Appl. No. 17/443,738 (pp. 1-15). [cited by applicant]
Office Action (Non-Final Rejection) dated Aug. 12, 2024 for U.S. Appl. No. 18/468,405 (pp. 1-8). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Sep. 30, 2024 for U.S. Appl. No. 17/491,291 (pp. 1-9). [cited by applicant]
Office Action (Non-Final Rejection) dated Sep. 29, 2024 for U.S. Appl. No. 17/958,117 (pp. 1-8). [cited by applicant]
Office Action (Non-Final Rejection) dated Oct. 7, 2024 for U.S. Appl. No. 17/958,109 (pp. 1-21). [cited by applicant]
Office Action (Final Rejection) dated Oct. 7, 2025 for U.S. Appl. No. 17/443,738 (pp. 1-19). [cited by applicant]
Office Action (Final Rejection) dated May 15, 2025 for U.S. Appl. No. 17/958,109 (pp. 1-22). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Oct. 6, 2025 for U.S. Appl. No. 17/958,109 (pp. 1-11). [cited by applicant]