User information gathering and distribution system

Abstract

Systems and methods relating to alerting users as to user information to be exchanged during transactions. A user information system (UIS) information circuit and an associated user information database populates an account with user information received from at least one of the user and a plurality of entities. A user information request relating to a transaction is received from an entity computing system associated with an entity over a network via a network interface circuit. A security circuit sends an alert comprising an approval request containing an identification of user information requested in the user information request to a user computing device associated with the user over the network. The security circuit receives an approval of the approval request from the user computing device, and the UIS information circuit provides the approved information to the entity to complete the transaction.

What is claimed is: 
     
         1 . A method, comprising:
 determining, by a User Information Service (UIS) system, that a user of a user computing device is predicted to engage in a potential transaction based on monitoring software applications executed on the user computing device and website activities on the user computing device;   determining, by the UIS system based on a transaction type of the potential transaction and an entity of the potential transaction, first user information corresponding to the potential transaction by comparing the potential transaction to a plurality of prior transactions of the same transaction type;   determining, by the UIS system, second user information of the user stored in a user information database;   determining, by the UIS system, whether the second user information is sufficient for the potential transaction by comparing the first user information and the second user information;   in response to determining that the second user information is not sufficient for the potential transaction, sending, by the UIS system to the user computing device, an alert indicating third user information different from the second user information;   receiving, by the UIS system from the user computing device, the third user information; and   providing, by the UIS system to an entity computing system of the entity, the second user information and the third user information.   
     
     
         2 . The method of  claim 1 , further comprising:
 determining the type of transactions based on monitoring the software applications and the web site activities; and   determining that the software applications and the website activities comprise multiple instances of the type of transactions over a period of time.   
     
     
         3 . The method of  claim 1 , further comprising:
 sending, by the UIS system to the user computing device, an alert indicative of the potential transaction; and   determining, by the UIS system from the user computing device, whether the user computing device confirms the potential transaction.   
     
     
         4 . The method of  claim 3 , further comprising in response to determining that the user computing device rejects the potential transaction, deleting, by the UIS system, the potential transaction. 
     
     
         5 . The method of  claim 1 , further comprising populating, by the UIS system in the user information database, an account of the user with the second user information received from at least one of the user computing system and a plurality of entity computing systems. 
     
     
         6 . The method of  claim 1 , further comprising analyzing, by the UIS system, a likelihood that the potential transaction is successful by comparing a first value corresponding to the transaction type to a second value comprised in the second user information. 
     
     
         7 . The method of  claim 1 , wherein the user information database is adaptive, constantly updates user information requested for certain types of transactions, and learns what user information requests to compare based on a given transaction type of prior user information requests 
     
     
         8 . At least one non-transitory computer readable medium having computer-executable instructions embodied therein that, when executed by at least one processor, causes the at least one processor to:
 determine that a user of a user computing device is predicted to engage in a potential transaction based on monitoring software applications executed on the user computing device and website activities on the user computing device;   determine based on a transaction type of the potential transaction and an entity of the potential transaction, first user information corresponding to the potential transaction by comparing the potential transaction to a plurality of prior transactions of the same transaction type;   determine second user information of the user stored in a user information database;   determine whether the second user information is sufficient for the potential transaction by comparing the first user information and the second user information;   in response to determining that the second user information is not sufficient for the potential transaction, send, to the user computing device, an alert indicating third user information different from the second user information;   receive from the user computing device, the third user information; and   provide, to an entity computing system of the entity, the second user information and the third user information.   
     
     
         9 . The non-transitory computer readable medium of  claim 8 , wherein the at least one processor is further caused to:
 determine the type of transactions based on monitoring the software applications and the website activities; and   determine that the software applications and the website activities comprise multiple instances of the type of transactions over a period of time.   
     
     
         10 . The non-transitory computer readable medium of  claim 8 , wherein the at least one processor is further caused to:
 send, to the user computing device, an alert indicative of the potential transaction; and   determine, from the user computing device, whether the user computing device confirms the potential transaction.   
     
     
         11 . The non-transitory computer readable medium of  claim 10 , wherein the at least one processor is further caused to: in response to determining that the user computing device rejects the potential transaction, deleting, by the UIS system, the potential transaction. 
     
     
         12 . The non-transitory computer readable medium of  claim 8 , wherein the at least one processor is further caused to populate in the user information database an account of the user with the second user information received from at least one of the user computing system and a plurality of entity computing systems. 
     
     
         13 . The non-transitory computer readable medium of  claim 8 , wherein the at least one processor is further caused to analyze a likelihood that the potential transaction is successful by comparing a first value corresponding to the transaction type to a second value comprised in the second user information. 
     
     
         14 . The non-transitory computer readable medium of  claim 8 , wherein the user information database is adaptive, constantly updates user information requested for certain types of transactions, and learns what user information requests to compare based on a given transaction type of prior user information requests 
     
     
         15 . A system, comprising at least one processor configured to:
 determine that a user of a user computing device is predicted to engage in a potential transaction based on monitoring software applications executed on the user computing device and website activities on the user computing device;   determine based on a transaction type of the potential transaction and an entity of the potential transaction, first user information corresponding to the potential transaction by comparing the potential transaction to a plurality of prior transactions of the same transaction type;   determine second user information of the user stored in a user information database;   determine whether the second user information is sufficient for the potential transaction by comparing the first user information and the second user information;   in response to determining that the second user information is not sufficient for the potential transaction, send, to the user computing device, an alert indicating third user information different from the second user information;   receive from the user computing device, the third user information; and   provide, to an entity computing system of the entity, the second user information and the third user information.   
     
     
         16 . The system of  claim 15 , wherein the at least one processor is further configured to:
 determine the type of transactions based on monitoring the software applications and the website activities; and   determine that the software applications and the website activities comprise multiple instances of the type of transactions over a period of time.   
     
     
         17 . The system of  claim 15 , wherein the at least one processor is further configured to:
 send, to the user computing device, an alert indicative of the potential transaction; and   determine, from the user computing device, whether the user computing device confirms the potential transaction.   
     
     
         18 . The system of  claim 10 , wherein the at least one processor is further configured to: in response to determining that the user computing device rejects the potential transaction, deleting, by the UIS system, the potential transaction. 
     
     
         19 . The system of  claim 8 , wherein the at least one processor is further configured to populate in the user information database an account of the user with the second user information received from at least one of the user computing system and a plurality of entity computing systems. 
     
     
         20 . The system of  claim 8 , wherein the at least one processor is further configured to analyze a likelihood that the potential transaction is successful by comparing a first value corresponding to the transaction type to a second value comprised in the second user information.