Granted Patent B2

US 12,248,611 · App. 18/395,691 · Granted Mar 11, 2025

Inventors: Lila Fakhraie (Belmont, CA); Brian M. Pearce (Pleasanton, CA); Steven Pulido (San Francisco, CA); Benjamin Soccorsy (Larkspur, CA); James Stahley (San Francisco, CA); Mojdeh Tomsich (Piedmont, CA)

Assignee: Wells Fargo Bank, N.A.

G06F21/6245H04L63/10G06F16/215G06F21/6263

Abstract

Claims (73)

1. A computing system of a first entity, the computing system comprising one or more processors configured to: transmit, to an internet browser running on a user device or to a first client application of the first entity running on the user device, an internet portal granting control over linking of accounts with third-party client applications; accept, via a login screen of the internet portal, a login credential and verify that the login credential grants access to the internet portal; present, in an interactive graphical user interface (GUI) of the internet portal displayed on a touchscreen of the user device, following verification that the login credential grants access to the internet portal, an account menu that lists a plurality of financial accounts, the plurality of financial accounts comprising a financial account with corresponding account data; detect, via the touchscreen of the user device, selection of the financial account in the account menu of the internet portal; present, in the GUI of the internet portal displayed on the touchscreen, in response to detecting selection of the financial account, an application menu that lists a plurality of client applications which are linked to the selected financial account such that subsets of the account data are accessible to each of the plurality of client applications in the application menu, the application menu comprising (i) a second client application which communicates, when executed on the user device, with a second computing system of a second entity and (ii) a third client application which communicates, when executed on the user device, with a third computing system of a third entity; present, in association with the second client application on the touchscreen, a first selectable icon configured to indicate, upon selection, that the second client application is to be unlinked from the financial account, and present, in association with the third client application on the touchscreen, a second selectable icon configured to indicate, upon selection, that the third client application is to be unlinked from the financial account; detect, via the touchscreen, selection of the first selectable icon indicating that the second client application is to be unlinked from the financial account; deactivate access to the account data by the second client application via the second computing system; receive, from the second computing system, a first application programming interface (API) request comprising a first request for a first subset of the account data; determine that access to the account data by the second client application is deactivated and, in response to determining that access to the account data by the second client application is deactivated, decline the first request for the first subset of the account data; receive, from the third computing system, a second API request comprising a second request for a second subset of the account data; determine that access to the account data by the third client application via the third computing system has not been deactivated; in response to determining that access to the account data by the third client application has not been deactivated, transmit to the third computing system the second subset of the account data; and present, in the GUI of the internet portal displayed on the touchscreen, based on the second API request, information on access to the account data by the third client application.

2. The system of claim 1 , wherein the one or more processors are further configured to present, in the GUI of the internet portal displayed on the touchscreen, the application menu comprising the third client application but not the unlinked second client application.

3. The system of claim 2 , wherein the one or more processors are further configured to present, in association with the third client application in the application menu, the second selectable icon configured to indicate, upon selection, that the third client application is to be unlinked from the financial account.

4. The system of claim 3 , where the one or more processors are further configured to:

detect, via the touchscreen, selection of the second selectable icon indicating that the third client application is to be unlinked from the financial account; and

deactivate the second access token that granted the third client application access to the account data via the third computing system.

5. The system of claim 4 , wherein the one or more processors are further configured to:

receive, from the third computing system, a third API request comprising the second access token and a third request for a third subset of the account data; and

determine that the second access token is deactivated and, in response to determining that the second access token is deactivated, decline the third request for the third subset of the account data.

6. The system of claim 1 , wherein the one or more processors are configured to:

present, in the GUI of the internet portal displayed on the touchscreen, the account menu and detect, via the account menu, selection of a second financial account comprising second account data;

present, in the GUI of the internet portal displayed on the touchscreen, in response to detecting selection of the second financial account, a second application menu comprising a second plurality of client applications that are linked to the selected second financial account such that subsets of the second account data are accessible to each client application of the second plurality of client applications, the second application menu comprising the third client application and a fourth client application which communicates, when executed on the user device, with a fourth computing system of a fourth entity; and

present, in association with the third client application on the touchscreen, a third selectable icon configured to indicate, upon selection, that the third client application is to be unlinked from the second financial account, and present, in association with the fourth client application on the touchscreen, a fourth selectable icon configured to indicate, upon selection, that the fourth client application is to be unlinked from the second financial account.

7. The system of claim 6 , wherein the one or more processors are configured to:

detect, via the touchscreen, selection of the third selectable icon indicating that the third client application is to be unlinked from the second financial account;

deactivate a third access token corresponding to the second financial account that granted the third client application access to the second account data of the second financial account via the third computing system.

8. The system of claim 7 , wherein the one or more processors are configured to:

receive, from the third computing system, a fourth API request comprising the third access token and a fourth request for a fourth subset of the second account data; and

determine that the third access token is deactivated and, in response to determining that the third access token is deactivated, decline the fourth request for the fourth subset of the second account data.

9. The system of claim 8 , wherein the one or more processors are configured to:

receive, from the fourth computing system, a fifth API request comprising a fourth access token and a fifth request for a fifth subset of the second account data;

determine that the fourth access token grants the fourth client application access to the second account data via the fourth computing system;

in response to determining that the fourth access token grants access, transmit to the fourth computing system the fifth subset of the second account data; and

present, in the GUI of the internet portal displayed on the touchscreen, based on the fifth API request, information on access to the second account data by the fourth client application.

10. The system of claim 1 , wherein the one or more processors are further configured to present, in the GUI of the internet portal displayed on the touchscreen, information on recent transactions by at least one of the second client application or the third client application.

11. The system of claim 1 , wherein the one or more processors are configured to present information on unusual activity with respect to at least one of the second client application or the third client application.

12. The system of claim 11 , wherein the one or more processors are configured to, in response to detecting unusual activity with respect to the third client application, deactivate the second access token to disable access to the account data by the third client application.

13. The system of claim 1 , wherein deactivating access to the account data by the second client application comprises deactivating a first access token, corresponding to the financial account, that granted the second client application access to the account data, and wherein determining that access to the account data by the third client application has not been deactivated comprises determining that the second access token grants the third client application access to the account data.

14. A method implemented by a first computing system of a first entity, the method comprising:

transmitting, to an internet browser running on a user device or to a first client application of the first entity running on the user device, an internet portal granting control over linking of accounts with third-party client applications;

accepting, via a login screen of the internet portal, a login credential and verify that the login credential grants access to the internet portal;

presenting, in an interactive graphical user interface (GUI) of the internet portal displayed on a touchscreen of the user device, following verification that the login credential grants access to the internet portal, an account menu that lists a plurality of financial accounts, the plurality of financial accounts comprising a financial account with corresponding account data;

detecting, via the touchscreen of the user device, selection of the financial account in the account menu of the internet portal;

presenting, in the GUI of the internet portal displayed on the touchscreen, in response to detecting selection of the financial account, an application menu that lists a plurality of client applications which are linked to the selected financial account such that subsets of the account data are accessible to each of the plurality of client applications in the application menu, the application menu comprising (i) a second client application which communicates, when executed on the user device, with a second computing system of a second entity and (ii) a third client application which communicates, when executed on the user device, with a third computing system of a third entity;

presenting, in association with the second client application on the touchscreen, a first selectable icon configured to indicate, upon selection, that the second client application is to be unlinked from the financial account, and presenting, in association with the third client application on the touchscreen, a second selectable icon configured to indicate, upon selection, that the third client application is to be unlinked from the financial account;

detecting, via the touchscreen, selection of the first selectable icon indicating that the second client application is to be unlinked from the financial account;

deactivating access to the account data by the second client application via the second computing system;

receiving, from the second computing system, a first API request comprising a first request for a first subset of the account data;

determining that access to the account data by the second client application is deactivated and, in response to determining that access to the account data by the second client application is deactivated, declining the first request for the first subset of the account data;

receiving, from the third computing system, a second API request comprising a second request for a second subset of the account data;

determining that access to the account data by the third client application via the third computing system has not been deactivated;

in response to determining that access to the account data by the third client application has not been deactivated, transmitting to the third computing system the second subset of the account data; and

presenting, in the GUI of the internet portal displayed on the touchscreen, based on the second API request, information on access to the account by the third client application.

15. The method of claim 14 , further comprising presenting, in the GUI of the internet portal displayed on the touchscreen, the application menu comprising the third client application but not the unlinked second client application.

16. The method of claim 15 , further comprising:

presenting, in association with the third client application in the application menu, the second selectable icon configured to indicate, upon selection, that the third client application is to be unlinked from the financial account,

detecting, via the touchscreen, selection of the second selectable icon indicating that the third client application is to be unlinked from the financial account; and

deactivating the second access token that granted the third client application access to the account data via the third computing system.

17. The method of claim 16 , further comprising:

receiving, from the third computing system, a third API request comprising the second access token and a third request for a third subset of the account data; and

determining that the second access token is deactivated and, in response to determining that the second access token is deactivated, declining the third request for the third subset of the account data.

18. The method of claim 17 , further comprising:

presenting, in the GUI of the internet portal displayed on the touchscreen, the account menu and detecting, via the account menu, selection of a second financial account comprising second account data;

presenting, in the GUI of the internet portal displayed on the touchscreen, in response to detecting selection of the second financial account, a second application menu comprising a second plurality of client applications that are linked to the selected second financial account such that subsets of the second account data are accessible to each client application of the second plurality of client applications, the second application menu comprising the third client application and a fourth client application which communicates, when executed on the user device, with a fourth computing system of a fourth entity;

presenting, in association with the third client application on the touchscreen, a third selectable icon configured to indicate, upon selection, that the third client application is to be unlinked from the second financial account, and presenting, in association with the fourth client application on the touchscreen, a fourth selectable icon configured to indicate, upon selection, that the fourth client application is to be unlinked from the second financial account.

19. The method of claim 18 , further comprising:

detecting, via the touchscreen, selection of the third selectable icon indicating that the third client application is to be unlinked from the second financial account;

deactivating a third access token corresponding to the second financial account that granted the third client application access to the second account data via the third computing system;

receiving, from the third computing system, a fourth API request comprising the third access token and a fourth request for a fourth subset of the second account data; and

determining that the third access token is deactivated and, in response to determining that the third access token is deactivated, declining the fourth request for the fourth subset of the second account data.

20. A first computing system of a first entity, the first computing system comprising one or more processors configured to:

transmit, to a user device, via a first client application of the first entity running on the user device, an internet portal for granting control over linking of accounts with third-party client applications, and grant, based on a credential input into the user device, access to the internet portal;

present, in the internet portal displayed on a touchscreen of the user device, following grant of access to the internet portal, an account menu that lists a financial account;

detect, via the touchscreen of the user device, selection of the financial account in the account menu of the internet portal;

present, in the internet portal displayed on the touchscreen, in response to detecting selection of the financial account, an application menu of a plurality of client applications linked to the financial account such that subsets of account data are accessible to each client application in the plurality of client applications, the application menu listing (i) a second client application which communicates with a second computing system of a second entity and (ii) a third client application which communications with a third computing system of a third entity;

present, in association with the second client application on the touchscreen, a first selectable icon configured to indicate, upon selection, that a first link between the second client application and the financial account is to be severed, and present, in association with the third client application on the touchscreen, a second selectable icon configured to indicate, upon selection, that a second link between the third client application and the financial account is to be severed;

detect, via the touchscreen, selection of the first selectable icon indicating that the first link is to be severed;

deactivate access to the account data by the second client application;

receive, from the second computing system, a first API request comprising a first request for a first subset of the account data;

determine that access to the account data by the second client application is deactivated and, in response to determining that access to the account data by the second client application is deactivated, decline the first request for the first subset of the account data;

receive, from the third computing system, a second API request comprising a second request for a second subset of the account data;

determine that access to the account data by the third client application has not been deactivated; and

in response to determining that access to the account data by the third client application has not been deactivated, transmit to the third computing system the second subset of the account data.

Continuity (14)

References Cited (400)