US 12,333,576 B2
Network security linkage
Balin Kina Brandt, Brooklyn, NY (US); Laura Fisher, Rock Hill, SC (US); Marie Jeanette Floyd, Toronto (CA); Katherine J. McGee, San Francisco, CA (US); Teresa Lynn Rench, Mount Holly, NC (US); and Sruthi Vangala, San Francisco, CA (US)
Assigned to Wells Fargo Bank, N.A., San Francisco, CA (US)
Filed by Wells Fargo Bank, N.A., San Francisco, CA (US)
Filed on Nov. 20, 2023, as Appl. No. 18/514,354.
Application 18/514,354 is a continuation of application No. 17/852,896, filed on Jun. 29, 2022, granted, now 11,823,087.
Application 17/852,896 is a continuation of application No. 16/238,299, filed on Jan. 2, 2019, granted, now 11,386,412.
Claims priority of provisional application 62/666,587, filed on May 3, 2018.
Claims priority of provisional application 62/666,591, filed on May 3, 2018.
Claims priority of provisional application 62/656,750, filed on Apr. 12, 2018.
Claims priority of provisional application 62/656,753, filed on Apr. 12, 2018.
Prior Publication US 2024/0086978 A1, Mar. 14, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 20/40 (2012.01); G06Q 20/02 (2012.01); G06Q 20/08 (2012.01); G06Q 20/10 (2012.01); G06Q 20/16 (2012.01); G06Q 20/22 (2012.01); G06Q 20/32 (2012.01); G06Q 20/36 (2012.01); G06Q 30/0279 (2023.01); G06Q 40/03 (2023.01); G06Q 50/00 (2024.01); G10L 15/18 (2013.01); G10L 15/22 (2006.01); G10L 17/00 (2013.01); H04L 9/40 (2022.01); H04M 3/51 (2006.01); H04W 4/029 (2018.01); H04W 4/38 (2018.01)
CPC G06Q 30/0279 (2013.01) [G06Q 20/02 (2013.01); G06Q 20/0855 (2013.01); G06Q 20/108 (2013.01); G06Q 20/16 (2013.01); G06Q 20/227 (2013.01); G06Q 20/3224 (2013.01); G06Q 20/3676 (2013.01); G06Q 20/4014 (2013.01); G06Q 40/03 (2023.01); G06Q 50/01 (2013.01); G10L 15/1807 (2013.01); G10L 15/22 (2013.01); G10L 17/00 (2013.01); H04L 63/102 (2013.01); H04L 63/104 (2013.01); H04M 3/5183 (2013.01); H04W 4/029 (2018.02); H04W 4/38 (2018.02); G10L 2015/228 (2013.01); H04L 2209/56 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A service provider computing system comprising one or more processors, the service provider computing system configured to:
identify, based on analysis of one or more audio files captured using at least one of a first user device of a first user or a second user device of a second user, a verbal trigger to form an authentication circle between the first user and the second user;
associate a first login credential with the first user such that the first login credential grants the first user access to a dashboard, and associate a second login credential with the second user such that the second login credential grants the second user access to the dashboard;
in response to verifying that a first entered credential submitted via a login screen of the dashboard corresponds to the first login credential, enable (i) selection of a third-party account of the first user that is secured by a third-party computing system such that successful login with the third-party computing system is required to access the third-party account, and (ii) selection of account permissions defining account functionality to be granted, through access to the dashboard, to users in the authentication circle;
receive, via the dashboard, a first input selecting to link the third-party account to the authentication circle, and a second input identifying a permission level restricting account functionality to be granted to the second user through the dashboard;
in response to the first and second inputs, link the third-party account of the first user to the authentication circle by:
transmitting, to the third-party computing system, a request to link the third-party account to the authentication circle; and
receiving, from the third-party computing system in response to the request, a security access token generated by the third-party computing system to grant the service provider computing system access to the third-party account;
transmit, to the third-party computing system, a first application programming interface (API) account access request with the security access token;
receive account data from the third-party computing system in response to the first API account access request;
present the account data to the first user via the dashboard;
in response to verifying a second entered credential received via the login screen of the dashboard corresponds to the second login credential, identify, in the dashboard, the first user, the second user, and the third-party account; and
present, via the dashboard, to the second user, the account data as restricted by the permission level, wherein the dashboard provides access to the third-party account through the dashboard using the first login credential and the second login credential without requiring users to directly connect to and authenticate with the third-party computing system, thereby enabling access by multiple users with different credentials to the third-party account at different permission levels via the dashboard of the service provider computing system.