IP Library Granted Patent US 11,429,742
Granted Patent B1
US 11,429,742 · App. 16/211,391 · Granted Aug 30, 2022

Control tower restrictions on third party platforms

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 (San Francisco, CA)
Assignee: Wells Fargo Bank, N.A.
G06F21/6245H04L63/10G06F16/215G06F21/6263
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 11,429,742
App. No.
16/211,391
Granted
Aug 30, 2022
Kind
B1
Abstract

Systems, methods, and apparatuses for providing a customer a central location to manage permissions provided to third-parties and devices to access and use customer information maintained by a financial institution are described. The central location serves as a central portal where a customer of the financial institution can manage all access to account information and personal information stored at the financial institution. Accordingly, the customer does not need to log into each individual third-party system or customer device to manage previously provided access to the customer information or to provision new access to the customer information. A user additionally is able to have user data and third-party accounts of the user deleted from devices, applications, and third-party systems via a central portal. Restrictions on how user data is used by devices, applications, and third-party systems can be imposed via a central portal.

Claims (44)

1. A service provider computing system comprising:

a network interface configured to communicate via a telecommunications network; and

a processor and a memory having stored thereon instructions which, when executed by the processor, cause the processor to:

maintain a listing of one or more computing devices, wherein the listing includes identifiers for each computing device corresponding to one of a tablet computer, a smart speaker, a vehicle, a wearable device, or an internet-of-things (IOT) device;

receive, via the network interface, an access request from a computing device of the one or more computing devices, the access request identifying a user account and data corresponding to the user account;

verify, based on an identifier of the computing device, that a user of the user account has granted the computing device access to the data;

in response to verifying that the user has granted access, use the network interface to transmit the data to the computing device;

receive, from a user device of the user, an instruction that includes the identifier identifying the computing device and requesting deletion of the user account for which the data was provided to the computing device;

generate, responsive to receiving the instruction, a command that requests deletion of the user account and the data from the computing device; and

use the network interface to transmit the command to the computing device to request the computing device to, consistent with the instruction from the user device, delete the user account and the data received from the service provider computing system;

wherein the instructions are further configured to cause the processor to maintain a listing of one or more applications installed on the user device and an indicator for each respective application to indicate whether the user of the user account has granted the respective application access to the data corresponding to the user account.

2. The system of claim 1 , wherein the command includes an API call to the computing device, wherein the API call identifies the user and the data to be deleted or restricted.

3. The system of claim 1 , wherein the access request is an API call transmitted by the computing device to the service provider computing system.

4. The system of claim 1 , wherein the command instructs the computing device to delete the data from all computer-readable storage media controlled by the computing device.

5. The system of claim 1 , wherein the instruction identifies a selection made, via a graphical interface presented by a client application running on the user device, between permitting a use of the data and prohibiting the use of the data.

6. The system of claim 5 , wherein the data identifies a credit or debit card, and wherein the use corresponds with use of the credit or debit card in an identified category of financial transactions.

7. The system of claim 6 , wherein the account data is for a credit or debit card, and wherein the identified category of financial transactions is foreign transactions.

8. The system of claim 1 , wherein the instruction is a first instruction, wherein the command is a first command, and wherein the instructions are further configured to cause the processor to:

receive, from the user device of the user, a second instruction that identifies an application of the one or more applications installed on the user device and requests granting the application access to the user data; and

modifying, responsive to receiving the second instruction, the indicator for the application to indicate that the user of the user account has granted the application access to the data corresponding to the user account.

9. The system of claim 1 , wherein the instructions are further configured to cause the processor to:

identify that one of the one or more applications is a calendar application; and

transmit, to the calendar application, a list of upcoming payments owed by the user for display by the calendar application to remind the user.

10. A method comprising:

maintaining, by a service provider computing system, a listing of one or more computing devices, wherein the listing includes identifiers for each computing device corresponding to one of a tablet computer, a smart speaker, a vehicle, a wearable device, or an internet-of-things (IOT) device;

receiving, by the service provider computing system, an access request from a computing device of the one or more computing devices, the access request identifying a user account and data corresponding to the user account;

verifying, by the service provider computing system, based on an identifier of the computing device, that a user of the user account has granted the computing device access to the data;

in response to verifying that the user has granted access, transmitting, by the service provider computing system, the data to the computing device;

receiving, by the service provider computing system, from a user device of the user, an instruction that includes the identifier identifying the computing device and requesting deletion of the user account for which the data was provided to the computing device;

generating, by the service provider computing system, responsive to receiving the instruction, a command that requests deletion of the user account and the data from the computing device;

transmitting, by the service provider computing system, the command to the computing device to request the computing device to, consistent with the instruction from the user device, delete the user account and the data received from the service provider computing system; and

maintaining, by the service provider computing system, a listing of one or more applications installed on the user device and an indicator for each respective application to indicate whether the user of the user account has granted the respective application access to the data corresponding to the user account.

11. The method of claim 10 , wherein the command includes an API call to the computing device, wherein the API call identifies the user and the data to be deleted or restricted.

12. The method of claim 10 , wherein the command instructs the computing device to delete the data from all computer-readable storage media controlled by the computing device.

13. The method of claim 10 , wherein the instruction identifies a selection made, via a graphical interface presented by a client application running on the user device, between permitting a use of the data and prohibiting the use of the data.

14. The method of claim 13 , wherein the data includes account data usable in financial transactions, and wherein the use corresponds with use of the data in an identified category of financial transactions.

15. The method of claim 14 , wherein the account data is for a credit or debit card, and wherein the identified category of financial transactions is foreign transactions.

16. The method of claim 10 , wherein the access request comprises an API call transmitted by the computing device to the service provider computing system.

17. The method of claim 10 , wherein the instruction is a first instruction, wherein the command is a first command, and further comprising:

receiving, by the service provider computing system, from the user device of the user, a second instruction that identifies an application of the one or more applications installed on the user device and requests granting the application access to the user data; and

modifying, by the service provider computing system, responsive to receiving the second instruction, the indicator for the application to indicate that the user of the user account has granted the application access to the data corresponding to the user account.

18. The method of claim 10 , further comprising:

identifying, by the service provider computing system, that one of the one or more applications is a calendar application; and

transmitting, by the service provider computing system, to the calendar application, a list of upcoming payments owed by the user for display by the calendar application to remind the user.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 2, 2019
From: FAKHRAIE, LILA; PEARCE, BRIAN M.; PULIDO, STEVEN; SOCCORSY, BENJAMIN; STAHLEY, JAMES; TOMSICH, MOJDEH
To: WELLS FARGO BANK, N.A.
Reel/Frame 049658/0034 →
Continuity (7)
Continuation 16204831 · Nov 29, 2018
Continuation In Part 15723078 · Oct 2, 2017
Continuation In Part 15629423 · Jun 21, 2017
Provisional Application 62766400 · Oct 16, 2018
Provisional Application 62529360 · Jul 6, 2017
Provisional Application 62403396 · Oct 3, 2016
Provisional Application 62357737 · Jul 1, 2016