System and method for digital authentication

Patent metadata

Field	Value
Publication number	US-2020279255-A1
Application number	US-202016872401-A
Country	US
Kind code	A1
Filing date	May 12, 2020
Priority date	Aug 15, 2014
Publication date	Sep 3, 2020
Grant date	—

Abstract

A system and method for using device characteristics to authenticate a transaction is disclosed. A first device can be used to request a transaction, and a second device can be used to approve the transaction. A push notification or authentication code is transmitted to a second device, and approval of the transaction is completed based in part on the hardware characteristics of the second device. A security database stores the hardware characteristics of the second device and links the characteristics to authentication profiles such that the second device can be used as a physical authentication device in multi-factor authentication.

First claim

What is claimed is:

1 . A method comprising:
receiving, at a security database, a request to enroll a user in push notification authentication; receiving, at the security database, hardware characteristics of a first customer device; storing, in the security database, the hardware characteristics of the first customer device as a device identifier associated with the user; creating, by the security database, an authentication profile for the user; linking, by the security database, the device identifier to the authentication profile to enroll the user in the push notification authentication; receiving, at an interaction channel of a service provider, a transaction request to perform a transaction from a second customer device; transmitting a push notification to the first customer device, the push notification indicating the transaction has been requested and seeking an approval from the user; receiving, at the security database, the approval from the user and the hardware characteristics of the first customer device from the first customer device; validating, by the security database, the transaction request based on the approval from the user and a comparison between the hardware characteristics of the first customer device and the device identifier saved in the security database; and approving or denying the transaction on the second customer device based on the validation.

2 . The method of claim 1 , wherein the step of validating the transaction request is based upon a distance between the first customer device and the second customer device.

3 . The method of claim 1 , wherein the step of transmitting the push notification is completed in response to determining that the first customer device and the second customer device are within a predetermined distance.

4 . The method of claim 1 , wherein the approval from the user is input into a mobile application operating on the second customer device.

5 . The method of claim 4 , wherein the approval from the user comprises data indicative of at least one of a tap, a password, a pattern, or user biometrics inputted via the mobile application.

6 . The method of claim 4 , wherein the mobile application is associated with the service provider and is configured to capture the hardware characteristics of the first customer device.

7 . The method of claim 1 , wherein:
the interaction channel is a website and the service provider is a website provider; the transaction request comprises a request to access the website; and the push notification transmitted to the first customer device replaces responses to security questions when accessing the website.

8 . The method of claim 1 , wherein:
the request to enroll the user in push notification authentication comprises user authentication preferences; and the push notification transmitted to the first customer device comprises an authentication method corresponding to the user authentication preferences.

9 . The method of claim 1 , wherein the push notification transmitted to the first customer device is transmitted via a Bluetooth or other wireless communication network.

10 . A method comprising:
receiving, at a security database, a request to enroll a user in push notification authentication; receiving, at the security database, hardware characteristics of a first customer device; storing the hardware characteristics of the first customer device in the security database; receiving, at an interaction channel of a service provider, a transaction request to perform a transaction from a second customer device; transmitting a push notification to the first customer device indicating receipt of the transaction request and seeking an approval from the user; receiving, at the security database, the approval from the user and the hardware characteristics of the first customer device from the first customer device; comparing, by the security database, the hardware characteristics received with the approval from the user with the hardware characteristics stored in the security database; and validating, by the security database, the transaction request based on the approval from the user and by using the first customer device as a hardware token.

11 . The method of claim 10 , further comprising:
creating, by the security database, an authentication profile for the user; and linking, by the security database, the hardware characteristics to the authentication profile to enroll the user in the push notification authentication.

12 . The method of claim 10 , wherein the step of validating the transaction request is based upon a distance between the first customer device and the second customer device.

13 . The method of claim 10 , wherein the step of transmitting the push notification is completed in response to determining that the first customer device and the second customer device are within a predetermined distance.

14 . The method of claim 10 , wherein:
the approval from the user is input into a mobile application operating on the second customer device; and the mobile application is associated with the service provider and is configured to capture the hardware characteristics of the first customer device.

15 . The method of claim 10 , wherein:
the request to enroll the user in push notification authentication comprises user authentication preferences; and the push notification transmitted to the first customer device comprises an authentication method corresponding to the user authentication preferences.

16 . The method of claim 10 , wherein the push notification transmitted to the first customer device is transmitted via a Bluetooth or other wireless communication network.

17 . A system comprising:
a first customer device comprising:
one or more first processors;
a first user interface in communication with the one or more first processors; and
a first memory in communication with the one or more first processors and storing a mobile application that, when executed by the one or more first processors, causes the first customer device to:
transmit a first request to enroll a user in push notification authentication;
transmit hardware characteristics of the first customer device to a security database;
receive a push notification from a backend system to approve a transaction;
determine that the user approves the transaction based on receipt of an input via the first user interface in response to receiving the push notification; and
transmit a user approval of the transaction to the backend system;

a second customer device comprising:
one or more second processors;
a second user interface in communication with the one or more second processors; and
a second memory in communication with the one or more second processors and storing instructions that, when executed by the one or more second processors, causes the second customer device to transmit a second request to the backend system to perform the transaction; and
the security database associated with the backend system that is configured to:
store hardware characteristics of one or more registered customer devices comprising the first customer device;
receive the second request to perform the transaction from the second customer device;
transmit the push notification to the first customer device;
receive the hardware characteristics of the first customer device;
receive the user approval of the transaction from the first customer device;
compare the transmitted hardware characteristics the first customer device to the stored hardware chara

Assignees

• Capital One Services Llc

Inventors

• Douglas Lawrence
• Ashfield James
• Poole Thomas S
• Fields John
• Bowers Justin
• Cogswell Drew
• Elasic John

Classifications

• H04L67/55

  Push-based network services · CPC title

• G06Q20/18

  involving self-service terminals [SST], vending machines, kiosks or multimedia terminals · CPC title

• H04W12/02

  Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] · CPC title

• G06F21/42

  using separate channels for security data · CPC title

• G06Q20/40

  Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists · CPC title