BIDIRECTIONAL AUTHENTICATION

• US 20160105425A1
• Filed: 10/13/2014
• Published: 04/14/2016
• Est. Priority Date: 10/13/2014
• Status: Active Grant

• Current Assignee: Wells Fargo Bank NA (Wells Fargo & Company)
• Original Assignee: Wells Fargo Bank NA (Wells Fargo & Company)
• Inventors: Clausen, Christopher Phillip, Suen, Darrell Lee, Lepage, Lisa Michelle, Cornman, Jeffrey A.
• Granted Patent: US 9,473,490 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety
• CPC Class Codes: H04L 63/0838 using one-time-passwords
• CPC Class Codes: H04L 63/0861 using biometrical features, e.g. fingerprint, retina-scan cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231
• CPC Class Codes: H04L 63/0869 for achieving mutual authentication cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273

Abstract

Systems, methods, and other embodiments associated with bidirectional authentication are described herein. According to one embodiment, a method includes a user receiving a communication from an entity. In response to receiving the communication from the entity, the method further includes generating a token. The token may be a one-time passcode, personal identification number (PIN), alphanumeric value, code word, pass phrase, or security question. The token is received by a device of the user. Additionally, the token is transmitted to the entity. The user may then receive evidence of the token from the entity.

Claims

1. A method, comprising:

receiving, by a user, communication from an entity;

generating a token, at a device, in response to receiving the communication, wherein the token personal identification number (PIN), alphanumeric value, code word, pass phrase, or a security question;

receiving the token;

transmitting the generated token to the entity; and

receiving evidence of the token from the entity.

2. The method of claim 1, wherein the evidence is the token, a portion of the token, or a response to the token.

3. The method of claim 1, further comprising:

requesting the entity respond with evidence of the token.

4. The method of claim 1, further comprising:

registering the device with the entity, wherein registration associates the device with the user.

5. The method of claim 1, wherein the communication is received on a communication channel that is a first digital channel, and wherein the token is transmitted on authentication channel that is a second digital channel.

6. The method of claim 5, wherein the first digital channel is different from the second digital channel.

7. The method of claim 1, wherein the token is a one-time passcode.

8. A non-transitory computer-readable medium storing computer-executable instructions that when executed by a computer cause the computer to perform a method, the method comprising:

initiating communication with a user by an entity;

receiving a request to generate a token;

generating a token that is variable;

transmitting the generated token to a device of the user; and

storing the token.

9. The method of claim 8, further comprising:

registering the user by associating the user with the device.

10. The method of claim 9, wherein registering the user further comprising:

receiving at least one of user data and device data from the user;

storing the at least one of user data and device data.

11. The method of claim 8, further comprising:

receiving a request to verify the token from the user; and

transmitting evidence of the token to the user.

12. The method of claim 11, wherein the evidence is the token, a portion of the token, or a response to the token.

13. The method of claim 8, wherein the token is personal identification number (PIN), alphanumeric value, code word, pass phrase, or a security question.

14. A system, the system comprising:

a communication logic configured to send and receive communications between a user and entity; and

a token logic configured to generate a token in response to receiving a communication from the entity, wherein the token is personal identification number (PIN), alphanumeric value, code word, pass phrase, or a security question.

15. The system of claim 14, further comprising:

a registration interface configured to facilitate a user registering a device with the entity.

16. The system of claim 14, wherein the registration interface is further configured to transmit the token to a registration logic of the entity.

17. The system of claim 16, wherein the communication is received on a communication channel that is a first digital channel, and wherein the token is transmitted on authentication channel that is a second digital channel.

18. The system of claim 17, wherein the first digital channel is different from the second digital channel.

19. The system of claim 16, wherein the registration logic is configured to associate the user with the device.

20. The system of claim 14, wherein the communication logic is further configured to receive evidence of the token from the entity, wherein the evidence is the token, a portion of the token, or a response to the token.