ATM token cash withdrawal

• US 9,721,248 B2
• Filed: 03/04/2014
• Issued: 08/01/2017
• Est. Priority Date: 03/04/2014
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Bondesen, Laura Corinne, Blackhurst, Jason P., Harkey, Scott Lee, Belchee, William Blakely, Brunswig, Tammy L.
• Primary Examiner(s): Bartley, Kenneth
• Application Number:
  US14/196,947
• Publication Number:
  US 20150254655A1
• Time in Patent Office: 1,246 Days
• Field of Search: 705 72, 705 76
• CPC Class Codes: G06Q 20/1085 involving automatic teller machines [ATMs]
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G07F 19/20 Automatic teller machines [ATMs]
• CPC Class Codes: G07F 9/001 Interfacing with vending machines using mobile or wearable devices
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols

Abstract

Embodiments of the invention are directed to a system for managing financial tokens associated with a financial account, whereby the system is directed towards generating and authenticating tokens associated with the financial account in order to grant access to a user to conduct financial transactions on the financial account using an Automated Teller Machine (ATM). The system is configured to generate a server token that is associated with at least one financial account; communicate, to a first mobile device, a server packet comprising at least the server token; receive, from an ATM, a security packet communicated from a second mobile device to the ATM comprising at least a device token; authenticate the device token, the authentication comprising comparing the device token with the server token, thereby resulting in a successful authentication of the device token; and communicate the successful authentication to the ATM.

Claims

1. A system for managing financial tokens associated with a financial account, whereby the system generates and authenticates tokens associated with the financial account in order to grant access to a user to conduct financial transactions on the financial account using an Automated Teller Machine (ATM) via a mobile device, the system comprising:

an Automated Teller Machine (ATM) with a first Near Field Communication (NFC) transmitter;

a memory;

a computing processor; and

a module stored in the memory, the module comprising instruction code executable by one or more computing processors, and configured to cause the one or more computing processors to;

generate a server token, wherein the server token is associated with at least one financial account;

encrypt the server token using an encryption algorithm, wherein the server token is encrypted at least in part based on time;

communicate, to a first mobile device, a server packet, wherein the server packet comprises at least the encrypted server token, wherein the first mobile device has paired with the ATM via a second Near Field Communication (NFC) transmitter on the first mobile device and the first NFC transmitter of the ATM;

receive, from the ATM, a security packet, wherein the security packet comprises at least a device token communicated from the first mobile device to the ATM and an identification marker of the ATM;

wherein the device token is encrypted at least in part based on time,

wherein the device token is encrypted using the encryption algorithm used to encrypt the server token;

determine that the ATM is authorized for use, wherein determining that the ATM is authorized for use comprises comparing the received identification marker of the ATM with a list of identification markers accessible by the system;

upon determining that the ATM is authorized for use, authenticate the device token, the authentication comprising comparing the device token with the server token, thereby resulting in a successful authentication of the device token; and

communicate the successful authentication to the ATM.

2. The system of claim 1, wherein, the system is further configured to:

generate a server personal identification number (PIN), wherein the server PIN is a sequence of characters; and

associate the server PIN with the server token;

wherein, the server packet further comprises the server PIN, wherein the server PIN comprises a sequence of characters;

wherein, the security packet further comprises a user inputted PIN; and

wherein, authenticating the device token further comprises comparing the server PIN with the user submitted PIN.

3. The system of claim 2, wherein generating the server PIN comprises retrieving a customer PIN associated with a customer, wherein the server PIN is generated based at least in part on the customer PIN.

4. The system of claim 2, wherein generating the server PIN comprises generating a random PIN, wherein the server PIN may be based at least in part on the random PIN.

5. The system of claim 1, wherein the module is further configured to cause the processor to disable the server token after the system has authenticated the device token associated with the server token, thereby preventing the system from authenticating a second device token associated with the server token a second time.

6. The system of claim 1, wherein the module is further configured to cause the processor to:

receive a transaction communication from the ATM wherein the transaction communication comprises an amount of money and the device token; and

debit a financial account, by the amount of money, associated with the device token.

7. The system of claim 1, wherein the module is further configured to cause the processor to store an identification marker for the first mobile device associated with the server token;

wherein the security packet further comprises a device identification marker for the first mobile device; and

wherein, authenticating the device token further comprises comparing the stored identification marker for the first mobile device and the device identification marker in the security packet.

8. The system of claim 1, wherein authenticating the device token comprises decrypting both the server token and the device token, wherein authenticating the device token further comprises comparing the decrypted device token with the decrypted server token, thereby resulting in a successful authentication of the device token.

9. The system of claim 1, wherein the security packet further comprises global position information about the ATM.

10. A method for managing financial tokens associated with a financial account, whereby the method generates and authenticates tokens associated with the financial account in order to grant access to a user to conduct financial transactions on the financial account using an Automated Teller Machine (ATM) via a mobile device, the method comprising:

providing an Automated Teller Machine (ATM) with a first Near Field Communication (NFC) transmitter;

generating, via a computing device processor, a server token, wherein the server token is associated with at least one financial account;

encrypting, via a computing device processor, the server token using an encryption algorithm, wherein the server token is encrypted at least in part based on time;

communicating, via a computing device processor, to a first mobile device, a server packet, wherein the server packet comprises at least the encrypted server token, wherein the first mobile device has paired with the ATM via a second Near Field Communication (NFC) transmitter on the first mobile device and the first NFC transmitter of the ATM;

receiving, via a computing device processor, from the ATM, a security packet, wherein the security packet comprises at least a device token communicated from the first mobile device to the ATM and an identification marker of the ATM;

wherein the device token is encrypted at least in part based on time,

wherein the device token is encrypted using the encryption algorithm used to encrypt the server token;

determining, via a computing device processor, that the ATM is authorized for use, wherein determining the ATM is authorized for use comprises comparing the received identification marker of the ATM with a list of identification markers accessible by the system;

upon determining that the ATM is authorized for use, authenticating, via a computing device processor, the device token, the authentication comprising comparing the device token with the server token, thereby resulting in a successful authentication of the device token; and

communicating, via a computing device processor, the successful authentication to the ATM.

11. The method of claim 10, wherein the method further comprises:

generating, via a computing device processor, a server personal identification number (PIN), wherein the server PIN is a sequence of characters;

associating, via a computing device processor, the server PIN with the server token;

wherein the server packet further comprises the server PIN, wherein the server PIN comprises a sequence of characters;

wherein the security packet further comprises a user inputted PIN; and

wherein, authenticating the device token further comprises comparing the server PIN with the user submitted PIN.

12. The method of claim 11, wherein generating the server PIN comprises retrieving, via a computing device processor, a customer PIN associated with a customer, wherein the server PIN is generated based at least in part on the customer PIN.

13. The method of claim 11, wherein generating the server PIN comprises generating, via a computing device processor, a random PIN, wherein the server PIN may be based at least in part on the random PIN.

14. The method of claim 10, wherein the method further comprises disabling, via a computing device processor, the server token after authenticating the device token associated with the server token, thereby preventing authentication of a second device token associated with the server token a second time.

15. The method of claim 10, wherein the method further comprises:

receiving, via a computing device processor, a transaction communication from the ATM wherein the transaction communication comprises an amount of money and the device token; and

debiting, via a computing device processor, a financial account by the amount of money associated with the device token.

16. The method of claim 10, wherein the method further comprises storing, via a computing device processor, an identification marker for the first mobile device associated with the server token;

wherein the security packet further comprises a device identification marker for the first mobile device; and

wherein, authenticating the device token further comprises comparing, via a computing device processor, the stored identification marker for the first mobile device and the device identification marker in the security packet.

17. The method of claim 10, wherein authenticating the device token comprises decrypting, via a computing device processor, both the server token and the device token, wherein authenticating the device token further comprises comparing, via a computing device processor, the decrypted device token with the decrypted server token, thereby resulting in a successful authentication of the device token.

18. The method of claim 10, wherein the security packet further comprises global position information about the ATM.

19. A computer program product for managing financial tokens associated with a financial account, whereby the product generates and authenticates tokens associated with the financial account in order to grant access to a user to conduct financial transactions on the financial account using an Automated Teller Machine (ATM) via a mobile device, the computer program product comprising non-transitory computer-readable, medium comprising code causing an apparatus to:

generate a server token, wherein the server token is associated with at least one financial account;

encrypt the server token using an encryption algorithm, wherein the server token is encrypted at least in part based on time;

communicate, to a first mobile device, a server packet, wherein the server packet comprises at least the encrypted server token, wherein the first mobile device has paired with an ATM via a second Near Field Communication (NFC) transmitter on the first mobile device and a first NFC transmitter of the ATM;

receive, from the ATM, a security packet, wherein the security packet comprises at least a device token communicated from the first mobile device to the ATM and an identification marker of the ATM;

wherein the device token is encrypted at least in part based on time,

wherein the device token is encrypted using the encryption algorithm used to encrypt the server token;

determine that the ATM is authorized for use, wherein determining the ATM is authorized for use comprises comparing the received identification marker of the ATM with a list of identification markers accessible by the system;

upon determining that the ATM is authorized for use, authenticate the device token, the authentication comprising comparing the device token with the server token, thereby resulting in a successful authentication of the device token; and

communicate the successful authentication to the ATM.

20. The computer program product of claim 19, wherein the code further causes the apparatus to:

generate a server personal identification number (PIN), wherein the server PIN is a sequence of characters; and

associate the server PIN with the server token;

wherein, the server packet further comprises the server PIN, wherein the server PIN comprises a sequence of characters;

wherein, the security packet further comprises a user inputted PIN; and

wherein, authenticating the device token further comprises comparing the server PIN with the user submitted PIN.

21. The computer program product of claim 20, wherein generating the server PIN comprises retrieving a customer PIN associated with a customer, wherein the server PIN is generated at least in part on the customer PIN.

22. The computer program product of claim 20, wherein generating the server PIN comprises generating a random PIN, wherein the server PIN may be based at least in part on the random PIN.

23. The computer program product of claim 19, wherein the program is further configured to cause the apparatus to disable the server token after the system has authenticated the device token associated with the server token, thereby preventing the system from authenticating a second device token associated with the server token a second time.

24. The computer program product of claim 19, wherein the program is further configured to cause the apparatus to:

receive a transaction communication from the ATM wherein the transaction communication comprises an amount of money and the device token; and

debit a financial account, by the amount of money, associated with the device token.

25. The computer program product of claim 19, wherein the program is further configured to cause the apparatus to store an identification marker for the first mobile device associated with the server token;

wherein the security packet further comprises a device identification marker for the first mobile device; and

wherein, authenticating the device token further comprises comparing the stored identification marker for the first mobile device and the device identification marker in the security packet.