IP Library › Granted Patent US 12,456,116
Granted Patent B2
US 12,456,116 · App. 17/626,358 · Granted Oct 28, 2025

System and method utilizing chain of trust

Inventors: Anjana Surin (San Francisco, CA); Alan Johnson (Herriman, UT); Ansar Ansari (San Francisco, CA); Jalpesh Chitalia (Castro Valley, CA); Ramesh Shankar (San Francisco, CA); Manjush Menon (San Francisco, CA); Mark Cline (San Francisco, CA); Sanjeev Sharma (San Francisco, CA); Sayeed Mohammed (San Francisco, CA)
Assignee: Visa International Service Association
G06Q20/38215G06Q20/3674G06Q20/40145G06Q20/4097H04L9/3213H04L9/3228H04L9/3231G06Q2220/00H04L2209/56
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,456,116
App. No.
17/626,358
Granted
Oct 28, 2025
Kind
B2
Abstract

Embodiments of the invention are directed to systems and methods for authenticating a user device using an authenticating device that has previously been associated with a user and/or a credential. The user may initiate a transaction at the user device. An authenticating device associated with the transaction may be sent an authentication request corresponding to the user device. The user may indicate whether or not the user device is authenticated utilizing the authenticating device. If the user device is authenticated, the transaction may proceed. If the user device is not authenticated the transaction may be rejected.

Claims (51)

1. A method comprising:

receiving, by a resource provider computer that is a merchant computer from a first user device that is a home appliance configured to initiate a payment transaction and is not configured to store payment credential information for processing the initiated payment transaction and is not configured with an interface to receive an authentication input from a user, a transaction request comprising a device credential or a token, wherein the device credential or the token is previously associated with a second user device based on an enrollment process with an enrollment module, wherein the first user device is associated with the user;

retrieving, from a mapping stored in a memory of resource provider computer, an association between the device credential or token and the second user device, wherein the mapping indicates an association between payment credentials or tokens and a plurality of user devices, and wherein the mapping identifies a user device configured to act as an authenticating device;

identifying, by the resource provider computer, the second user device associated with the device credential or the token in the transaction request from the first user device based on the retrieved mapping, wherein the second user device acts as an authenticating device for the first user device according to the mapping to perform the authentication with the resource provider computer for the transaction request received from the first user device, wherein the first user device and second user device are associated with a same payment credential or token;

based on the second user device associated with the device credential or token being identified based on the retrieved mapping, transmitting, by the resource provider computer to the second user device, an authentication request to authenticate the resource provider computer with the first user device;

receiving, by the resource provider computer from the second user device, an authentication response, the authentication response comprising an indication that the first user device is authenticated;

transmitting, by the resource provider computer, an authorization request message to an authorizing entity computer in response to receiving the indication that the first user device is authenticated;

receiving an authorization response message authorizing the transaction request; and

receiving from the first user device a subsequent transaction request, authenticating the subsequent transaction request without requiring authentication with the second user device.

2. The method of claim 1 , wherein the resource provider computer receives the device credential associated with the user from the first user device, and the method further comprises:

obtaining, by the resource provider computer from a token provider computer, the token corresponding to the device credential and a cryptogram; and

generating, by the resource provider computer, the authorization request message to include the token and the cryptogram, and exclude the device credential.

3. The method of claim 2 , wherein the cryptogram includes data about an authentication method used in the authentication request.

4. The method of claim 1 , wherein the authorization request message further includes a first identifier for the first user device and a second identifier for the second user device, wherein transmitting the authorization request message causes the authorizing entity computer to maintain an association between the payment credential, the first identifier for the first user device, and the second identifier for the second user device, the association allowing subsequent transactions initiated by the first user device to be conducted.

5. The method of claim 1 , wherein prior to receiving the transaction request from the first user device, the method comprises:

receiving, by the resource provider computer, a first identifier of the first user device and a second identifier of the second user device;

associating, by the resource provider computer, the first user device with the second user device; and

storing, by the resource provider computer, the first identifier of the first user device with the second identifier of the second user device in a database.

6. The method of claim 5 , wherein identifying the second user device comprises retrieving the identifier of the second user device from the database.

7. The method of claim 1 , wherein the first user device does not have a user interface that includes an alphanumeric key pad.

8. The method of claim 1 , wherein the authentication request includes a biometric authentication request.

9. The method of claim 1 , wherein the first user device is a household appliance and the second user device is a mobile phone.

10. A resource provider computer comprising:

one or more processors; and

one or more computer-readable media comprising code, when executed by the one or more processors, cause the resource provider computer to perform a method comprising:

receiving, by the resource provider computer that is a merchant computer from a first user device that is a home appliance configured to initiate a payment transaction and is not configured to store payment credential information for processing the initiated payment transaction and is not configured with an interface to receive an authentication input from a user, a transaction request comprising a device credential or a token, wherein the device credential or the token is previously associated with a second user device based on an enrollment process with an enrollment module, wherein the first user device is associated with the user;

retrieving, from a mapping stored in a memory of resource provider computer, an association between the device credential or token and the second user device, wherein the mapping indicates an association between payment credentials or tokens and a plurality of user devices, and wherein the mapping identifies a user device configured to act as an authenticating device;

identifying the second user device associated with the device credential in the transaction request from the first user device based on the retrieved mapping, wherein the second user device acts as an authenticating device for the first user device according to the mapping to perform the authentication with the resource provider computer for the transaction request received from the first user device, wherein the first user device and second user device are associated with a same payment credential or token;

based on the second user device associated with the device credential or token being identified based on the retrieved mapping, transmitting, to the second user device, an authentication request to authenticate the resource provider computer with the first user device;

receiving, from the second user device, an authentication response, the authentication response comprising an indication that the first user device is authenticated;

transmitting an authorization request message to an authorizing entity computer in response to receiving the indication that the first user device is authenticated;

receiving an authorization response message authorizing the transaction request; and

receiving from the first user device a subsequent transaction request, authenticating the subsequent transaction request without requiring authentication with the second user device.

11. The resource provider computer of claim 10 , wherein the authorization response message is received from the authorizing entity computer.

12. The resource provider computer of claim 10 , wherein the resource provider computer grants access to a secure location if the authorization request message is approved.

13. The resource provider computer of claim 10 , wherein the device credential is a first identifier of the first user device.

14. The resource provider computer of claim 10 , wherein the resource provider computer stores an association between the first user device and the payment credential, and wherein the method further comprises:

receiving a de-enrollment message comprising a first identifier of the first user device; and

removing the association between the first user device and the payment credential.

15. The resource provider computer of claim 14 , wherein the transaction request is a first transaction request and the authorization request message is a first authorization request message and wherein the method further comprises:

receiving, from the first user device, a second transaction request comprising the device credential associated with the user; and

determining that the first user device is authenticated, and that communication with the second user device is not needed; and

transmitting a second authorization request message in response to determining that the first user device is authenticated.

16. The resource provider computer of claim 10 , wherein the resource provider computer receives the device credential associated with the user from the first user device, and the method further comprises:

obtaining, by the resource provider computer from a token provider computer, and a cryptogram; and

generating, by the resource provider computer, the authorization request message to include the token and the cryptogram, and exclude the device credential.

17. The method according to claim 1 , further comprising sending, by the resource provider computer, a token request message to a token service provider computer, the token request message requesting a cryptogram for the transaction,

wherein the cryptogram comprises encrypted authentication method data, an encrypted account identifier, an encrypted transaction channel indicator, and encrypted expiration information.

18. The method according to claim 1 , wherein the first user device does not include a user interface for alphanumeric input.

19. The method according to claim 1 , wherein the payment credential information is sensitive credential information.

20. The method according to claim 1 , wherein the device credential or token is a device identifier.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 14, 2022
From: SURIN, ANJANA; JOHNSON, ALAN; ANSARI, ANSAR; CHITALIA, JALPESH; SHANKAR, RAMESH; MENON, MANJUSH; CLINE, MARK; SHARMA, SANJEEV; MOHAMMED, SAYEED
To: VISA INTERNATIONAL SERVICE ASSOCIATION
Reel/Frame 058658/0287 →
Continuity (2)
Provisional Application 62875771 · Jul 18, 2019
Related Publication 20220207527A1 · Jun 30, 2022
References Cited (29)
US 8346666B2 · Lindelsee et al. · 2013 [cited by applicant]
US 8732475B2 · Fahrny et al. · 2014 [cited by applicant]
US 9996835B2 · Dill et al. · 2018 [cited by applicant]
US 10015147B2 · Narayan et al. · 2018 [cited by applicant]
US 10129250B2 · Oberheide et al. · 2018 [cited by applicant]
US 20050154925A1 · Chitrapu · 2005 [cited by examiner]
US 20050165684A1 · Jensen · 2005 [cited by examiner]
US 20080041936A1 · Vawter · 2008 [cited by examiner]
US 20120197740A1 · Grigg · 2012 [cited by examiner]
US 20130173811A1 · Ha · 2013 [cited by examiner]
US 20140230019A1 · Civelli et al. · 2014 [cited by applicant]
US 20150254665A1 · Bondesen · 2015 [cited by examiner]
US 20150348032A1 · Ioveva · 2015 [cited by examiner]
US 20160086176A1 · Silva Pinto et al. · 2016 [cited by applicant]
US 20160253669A1 · Yoon · 2016 [cited by examiner]
US 20180285875A1 · Law et al. · 2018 [cited by applicant]
AU 2016416139A1 · 2018 [cited by applicant]
CN 109716342A · 2019 [cited by applicant]
KR 101919590B1 · 2019 [cited by applicant]
WO 2005003907A2 · 2005 [cited by applicant]
WO 2016134016A1 · 2016 [cited by applicant]
WO 2017209767A1 · 2017 [cited by applicant]
A. Swift, “How to Remove a Phone from Trusted Devices in Google Account Settings”, https://tunecomp.net/remove-phone-from-trusted-devices-google-account/, Sep. 4, 2019, 11 pages. [cited by applicant]
PCT/US2020/042724 , “International Search Report and Written Opinion”, Nov. 5, 2020, 11 pages. [cited by applicant]
“Two-factor authentication for Apple ID”, https://support.apple.com/en-inHT204915, Dec. 8, 2020, 9 pages. [cited by applicant]
Application No. EP20839951.9 , Extended European Search Report, Mailed on Aug. 16, 2022, 9 pages. [cited by applicant]
Application No. CN202080051777.4 , Notice of Decision to Grant, Mailed on Nov. 9, 2024, 9 pages. [cited by applicant]
Application No. EP20839951.9 , Office Action, Mailed on May 7, 2025, 15 pages. [cited by applicant]
Application No. SG11202200133X , Written Opinion, Mailed on Sep. 30, 2024, 10 pages. [cited by applicant]