SYSTEM AND METHOD USING SUPERKEYS AND SUBKEYS

• US 20100125546A1
• Filed: 11/10/2009
• Published: 05/20/2010
• Est. Priority Date: 11/19/2008
• Status: Abandoned Application

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Scott, Joe, Siegel, Kevin, Hilgers, Nancy, Barrett, Melyssa
• Application Number:
  US12/616,028
• Publication Number:
  US 20100125546A1
• Time in Patent Office: Days
• US Class Current: 707/607
• CPC Class Codes: G06F 16/24556 Aggregation; Duplicate elimination
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/03 Credit; Loans; Processing thereof
• CPC Class Codes: G06Q 40/08 Insurance
• CPC Class Codes: G07F 7/08 by coded identity card or credit card or other personal identification means without personal verification means G07F7/02

Abstract

Systems and methods for providing aggregated transaction level data for a particular user to multiple information requesters are disclosed. Subkeys are assigned to user inquiries from multiple information requesters and a super key is assigned to those subkeys to link them to one or more user identifiers such as a username or Social Security number. Account level data is provided based on the super key and the user identifiers. Duplicate requests for aggregated transaction level data contained in the user inquiries can be deleted. User inquiry response files containing transaction level aggregate data can be sent to the information requesters based on the assigned subkeys.

Claims

1. A method for providing aggregated user data comprising:

receiving a plurality of different user inquiry messages relating to a user from a plurality of information requesters at a transaction server;

assigning subkeys to the different user inquiry messages;

combining the plurality of user inquiry messages into a combined user inquiry message using the transaction server;

assigning a super key to the combined user inquiry message using the transaction server; and

sending the super key and the combined user inquiry message from the transaction server to one or more data sources.

2. The method of claim 1 further comprising receiving raw transaction level data for at least some accounts associated with the user.

3. The method of claim 2 wherein the plurality of different user inquiry messages relating to the user each comprise at least one request for aggregated transaction level data for at least some accounts associated with the user.

4. The method of claim 3 wherein combining the plurality of user inquiry messages further comprises deleting duplicate requests for aggregated transaction level data in the plurality of user inquiry messages.

5. The method of claim 4 further comprising assigning the super key to the accounts associated with the user.

6. The method of claim 5 further comprising running a report on the raw transaction level data to generate the requested aggregated transaction level data in the plurality of user inquiry messages using the transaction server.

7. The method of claim 6 further comprising parsing the requested aggregated transaction level data into a plurality of individual user inquiry response files based on the sub keys and sending the plurality of individual user inquiry response files to the information requester corresponding to the sub keys.

8. A system for providing user risk data comprising:

a transaction database; and

an aggregator,

wherein the aggregator is configured to receive a plurality of different user inquiry messages relating to a user from a plurality of information requesters, combine the plurality of user inquiry messages in a combined user inquiry message, assign a super key to the combined user inquiry message; and

send the super key and the combined user inquiry message to one or more data sources.

9. The system of claim 8 wherein the aggregator is further configured to assign subkeys to the different user inquiry messages.

10. The system of claims 9 wherein the plurality of different user inquiry messages each comprise at least one request for aggregated transaction level data.

11. The system of claim 10 wherein the aggregator is further configured to delete duplicate requests for aggregated transaction level data in the plurality of user inquiry messages.

12. The system of claim 11 wherein the aggregator is further configured to receive a linkage response file from the one or more data sources that comprises links between at least some accounts associated with the user and the super key.

13. The system of claim 12 wherein the aggregator is further configured to link the super key to the subkeys.

17. A method of reporting user account data based on a combined user inquiry message using a server comprising:

receiving the combined user inquiry message using the server;

parsing a super key from the combined user inquiry message using the server;

parsing user identifiers from the combined user inquiry message using the server;

retrieving account data associated with the user identifiers using the server; and

sending the account data to one or more other servers from the server.

14. The system of claim 17 wherein the aggregator is further configured to receive raw transaction level data for at least some of the accounts associated with the user.

15. The system of claim 14 wherein the aggregator is further configured to run at least one report on the raw transaction level data to generate at least some of the requested aggregated transaction level data in the plurality of user inquiry messages

16. The system of claim 15 wherein the aggregator is further configured to parse the requested aggregated transaction level data into a plurality of individual user inquiry response files based on the sub keys and sending the plurality of individual user inquiry response files to the information requesters corresponding to the sub keys.

18. The method of claim 17 wherein sending the account data to one or more other servers from the server further comprises linking the account data to the super key.