US 12,219,065 B2
Persistent login
Shaoyen Chang, Stamford, CT (US); William Mahoney, Stamford, CT (US); Chidhambaram Mathevan Pillai, Stamford, CT (US); Seulkee Park, Stamford, CT (US); Jeremy T. Mack, Brighton, MI (US); Shahul Shaik, Hyderabad (IN); Sathyanarayana Mahendran, Hyderabad (IN); and Marina Loginova, Stamford, CT (US)
Assigned to Synchrony Bank, Stamford, CT (US)
Filed by Synchrony Bank, Stamford, CT (US)
Filed on Feb. 2, 2024, as Appl. No. 18/430,766.
Application 18/430,766 is a continuation of application No. 18/312,615, filed on May 5, 2023, granted, now 11,943,356.
Application 18/312,615 is a continuation of application No. 17/728,416, filed on Apr. 25, 2022, granted, now 11,689,368, issued on Jun. 27, 2023.
Application 17/728,416 is a continuation of application No. 17/083,692, filed on Oct. 29, 2020, granted, now 11,349,662, issued on May 31, 2022.
Claims priority of provisional application 62/927,552, filed on Oct. 29, 2019.
Prior Publication US 2024/0259202 A1, Aug. 1, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 9/32 (2006.01); H04L 9/08 (2006.01); H04L 9/40 (2022.01); H04L 29/06 (2006.01); H04L 67/306 (2022.01)
CPC H04L 9/3213 (2013.01) [H04L 9/088 (2013.01); H04L 9/3226 (2013.01); H04L 63/105 (2013.01); H04L 63/1433 (2013.01); H04L 67/306 (2013.01)] 21 Claims
OG exemplary drawing
 
1. A computer-implemented method, comprising:
receiving metadata corresponding to a first account associated with a user and a first entity, wherein the metadata is received through a Uniform Resource Locator (URL) activated through the first entity, and wherein the metadata provides an indication that the user has been authenticated in relation to the first entity;
transmitting a request for a set of credentials corresponding to a second account associated with the user and a second entity, wherein when the request is received by the user, the user provides the set of credentials;
generating an access token associated with the second account, wherein the access token is generated as a result of the set of credentials being validated, and wherein the access token provides a link between the first account and the second account;
generating a refresh token associated with the access token;
providing the access token and the refresh token, wherein when the access token is received by the first entity, the first entity uses the access token to access and retrieve information associated with the second account from the second entity;
receiving a new request to obtain a new access token, wherein the new request includes the refresh token, and wherein the new request is received as a result of the access token being expired; and
using the refresh token to generate the new access token for accessing the information associated with the second account.