There remains a need in the art for cardless ATM transactions and related methods.
Generally provided is a cardless ATM transaction driven by inputs from both 1) a personal computing device, and 2) an ATM. In embodiments, inputs from a personal computing device are used to create data set(s) that are subsequently used to drive an ATM transaction in a similar fashion to the dataset(s) created from a traditional debit card when inserted into an ATM to initiate an ATM transaction. As a result, embodiments allow for a cardless ATM transaction to be performed.
Method and system embodiments are directed to: 1) creating a mobile-wallet data set, and 2) executing an ATM transaction using the mobile-wallet data set. Embodiments are generally described in the context of computer-readable logic executed by one or more general-purpose computers. For example, in a portion of an embodiment, computer readable logic is stored on a server computer system and accessed by a client computer via a communications link or a network, such as an intranet, Internet, virtual private network, or another computer network. And because the basic structures and functions related to computer-readable routines and corresponding implementations are known, they have not been shown or described in detail below to avoid unnecessarily obscuring the described embodiments.
Details are set forth in the following description and in
In the following figures, identical reference numbers identify identical or at least generally similar elements. In the flow diagrams, a rectangle represents a process, task, action, or operation; a diamond presents a question; and a parallelogram shows input or output.
In an embodiment, personal computing device 4 sends mobile-wallet data set to server 6 that then forwards mobile-wallet data set to server 8 for hosting. In another embodiment, computing device 4 sends mobile-wallet data set to server 6 that executes an algorithm on at least a portion of mobile-wallet data set and thereby determines the appropriate host-server destination for mobile-wallet data set. In response to reaching this algorithm-driven-host-server-destination determination, mobile-wallet data set is then forwarded from server 8 to the identified host-server destination from amongst a plurality of host servers. In an embodiment, server 6 may have a plurality of host-server destinations to select from, wherein the plurality of host-server destinations are specific as to the type of mobile-wallet data set that they each respectively host. In other words, each host-server destination (i.e., host server) may respectively host different types of mobile-wallet data set(s). Mobile-wallet data set may include data that the algorithm (performed on server 6) determines is associated with a specific banking institution, and in response to reaching this determination, causes mobile-wallet data set to be forwarded from server 6 to the dedicated host server for that specific bank or bank data. As an illustrative example, mobile-wallet data set relating to ABC bank is sent from server 6 to a host server dedicated to hosting ABC-bank mobile-wallet data sets; mobile-wallet data set relating to DEF bank is sent from server 6 to a host server dedicated to hosting DEF-bank mobile-wallet data sets; mobile-wallet data set relating to MI bank is sent from server 6 to a host server dedicated to hosting GHI-bank mobile-wallet data sets; and so on.
In an embodiment, a mobile-cash-access app is launched on personal computing device 4, and “password/passcode” data-entry page 22 is displayed on personal computing device 4′s touchscreen GUI. In response to entering an acceptable password/passcode, “home” page 24 is subsequently displayed on personal computing device 4′s touchscreen GUI. In response to selecting “set up withdrawal” displayed on “home” page 24 on the touchsceen GUI, “accounts” page 26 is subsequently displayed on personal computing device 4′s touchscreen GUI. In response to selecting the card image on the touchscreen GUI that represents the account and desired mobile data set to be used in the transaction, “PIN” page 28 is subsequently displayed on personal computing device 4′s touchscreen GUI. In response to entering the correct PIN associated with the account and desired mobile data set to be used in the transaction, “cash amount” page 30 is subsequently displayed on personal computing device 4′s touchscreen GUI. In response to selecting a cash amount on personal computing device 4′s touchscreen GUI, pre-staging of the cardless ATM transaction using personal computing device 4 is complete.
In an embodiment, “home screen” 24 is displayed on personal computing device 4′s touchscreen GUI. In response to selecting the “pay” button on “home screen” page 24, “select queued transaction” page 34 is subsequently displayed on personal computing device 4′s touchscreen GUI. In response to selecting the desired queued transaction, “scan code” page 36 is subsequently displayed on personal computing device 4′s touchscreen GUI. In response to personal computing device 4 scanning the two-dimensional data code such as the QR CODE® displayed on ATM 2′s GUI interface “transaction processing” page 38 is subsequently displayed on personal computing device 4′s touchscreen GUI. In response to the ATM transaction being complete, “transaction complete” page 40 is subsequently displayed on personal computing device 4′s touchscreen GUI.
Regarding data-transfer 104a, in response to receiving token-data transfer 104a, mobile-wallet server 8 executes an algorithm that i) validates the authenticity of personal computing device 4, ii) validates the authenticity of the mobile-cash-access app running on personal computing device 4, iii) validates the app passcode entered by the consumer, and iv) validates the token. In response to validating these items, mobile-wallet server 8 sends available consumer financial accounts to personal computing device 4 shown as data transfer 110. In response to receiving available consumer financial accounts, personal computing device 4 displays the available consumer financial accounts on the GUI of personal computing device 4; an illustrative embodiment of this is shown on webpage 26 of
Regarding data transfer 104b from personal computing device 4 to PIN authentication engine server 10, in response to receiving data transfer 104b, PIN authentication engine server 10 then forwards at least a portion of data transfer 104b to EFT network and issuer for PIN authentication purposes. In an alternate embodiment, in addition to receiving token-data transfer 104b, an embodiment has PIN authentication engine server 10 also receiving the consumer's PIN data entry that has been entered by the consumer into ATM 2 or personal computing device 4.
Data transfer 105 represents the i) card number, ii) PIN, and iii) transaction data set being sent from ATM 2 to EFT network 14 via ATM driver 12. Data transfer 105 is sent to EFT network in order to receive authorization to execute the transaction. Upon authorizing the transaction (based at least in part on the data provided by data transfer 104b), EFT network 14 sends authorization data set 106 to ATM 2 via ATM driver 12. The transaction is then authorized and settlement occurs as is commonly known in the ATM industry and is represented as data transfer 107. A digital receipt is then delivered to personal computing device 2 from cloud server 6 as shown by data transfer 108.
Persons of ordinary skill in the art will appreciate that changes could be made to the embodiments described above without departing from the broad inventive concepts thereof. It is to be understood, therefore, that this invention is not limited to the particular embodiments disclosed, but it is intended to cover modifications within the spirit and scope of the present invention as defined by the appended claim.
This patent application claims priority to U.S. provisional patent application Ser. No. 61/990,946 filed on May 9, 2014. This application also claims priority to PCT application PCT/US15/030174 filed on May 11, 2015. The subject matter of both applications is hereby incorporated by reference.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2015/030174 | 5/11/2015 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2015/172150 | 11/12/2015 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6045039 | Stinson | Apr 2000 | A |
6155484 | Sasaki | Dec 2000 | A |
7689508 | Davis et al. | Mar 2010 | B2 |
7890422 | Hirka et al. | Feb 2011 | B1 |
8452257 | Granucci et al. | May 2013 | B2 |
8639621 | Ellis | Jan 2014 | B1 |
8751239 | Tian et al. | Jun 2014 | B2 |
8751313 | Fisher | Jun 2014 | B2 |
8751391 | Freund | Jun 2014 | B2 |
8960537 | Bulawa et al. | Feb 2015 | B2 |
9014662 | Gailloux et al. | Apr 2015 | B1 |
9026459 | Fisher | May 2015 | B2 |
10223678 | Park | Mar 2019 | B2 |
20030028481 | Flitcroft | Feb 2003 | A1 |
20060180654 | Meek | Aug 2006 | A1 |
20080126145 | Rackley, III et al. | May 2008 | A1 |
20100070412 | Stanley | Mar 2010 | A1 |
20100235283 | Gerson | Sep 2010 | A1 |
20100250410 | Song et al. | Sep 2010 | A1 |
20110238573 | Varadarajan | Sep 2011 | A1 |
20120160912 | Laracey | Jun 2012 | A1 |
20120303528 | Weiner | Nov 2012 | A1 |
20130124411 | Kobres | May 2013 | A1 |
20130124855 | Varadarajan et al. | May 2013 | A1 |
20130238497 | Ramachandran | Sep 2013 | A1 |
20140046842 | Irudayam | Feb 2014 | A1 |
20140172703 | Black | Jun 2014 | A1 |
20140263618 | McCarthy | Sep 2014 | A1 |
20150019944 | Kalgi | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
2587432 | May 2013 | EP |
2688026 | Jan 2014 | EP |
WO-2013045898 | Apr 2013 | WO |
WO-2014013071 | Jan 2014 | WO |
Entry |
---|
International Search Report for corresponding PCT application, dated Aug. 7, 2015. |
Intellectual Property Office of Singapore Search Report and Written Opinion, dated Jun. 15, 2017, for corresponding Singapore Application No. 11201609361P. |
Number | Date | Country | |
---|---|---|---|
20170262823 A1 | Sep 2017 | US |
Number | Date | Country | |
---|---|---|---|
61990946 | May 2014 | US |