Systems and Methods to Configure Data for Diverse Services

• US 20130066771A1
• Filed: 07/19/2012
• Published: 03/14/2013
• Est. Priority Date: 07/22/2011
• Status: Abandoned Application

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Ciurea, Peter, Amaro, Leigh, DiGioacchino, Laura, VonDerheide, James Alan, Stiff, Nicola
• Application Number:
  US13/553,131
• Publication Number:
  US 20130066771A1
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data
• CPC Class Codes: G06Q 30/0207 Discounts or incentives, e.g. coupons or rebates
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

A computing apparatus includes: a transaction handler configured to process payment transactions; a data warehouse coupled with the transaction handler to store transaction data recording the payment transactions processed by the transaction handler; and a portal coupled with the data warehouse to store non-transaction data associated with the transaction data. The portal is further configured to receive input from account holders to specify personalization data and to store the personalization data in the data warehouse to tag the non-transaction data. The personalization data controls the access to the non-transaction data tagged with the personalization data.

Claims

1. A computer-implemented method, comprising:

storing, in a computing device, transaction data recording payment transactions processed by a transaction handler, each of the payment transactions being processed to make a payment from an issuer to an acquirer via the transaction handler in response to an identifier of an account, as issued by the issuer to a customer, being submitted by a merchant to the acquirer, the issuer to make the payment on behalf of the customer, the acquirer to receive the payment on behalf of the merchant;

storing, in the computing device, non-transaction data related to items purchased via the payment transactions as recorded in the transaction data for respective accounts;

tagging, by the computing device, the non-transaction data with personalization data in response to requests from account holders of the respective accounts; and

controlling, by the computing device, access to the non-transaction data in accordance with the personalization data.

2. The method of claim 1, wherein the non-transaction data includes at least one of:

product registration data, warranty data, user manual, product recall data, and expense category classification data.

3. The method of claim 2, wherein the personalization data includes purpose data identifying a purpose of respective tagged non-transaction data.

4. The method of claim 2, wherein the personalization data includes permission data identifying permitted usages of respective tagged non-transaction data.

5. The method of claim 2, wherein the personalization data includes context data identifying permissible context in which access to respective tagged non-transaction data is granted.

6. The method of claim 2, wherein the personalization data includes destination data identifying entities who are permitted to receive respective tagged non-transaction data.

7. The method of claim 2, wherein the non-transaction data is tagged with the personalization data at a plurality of hierarchical levels;

and personalization data at a lower level overwrites personalization data at a higher level.

8. The method of claim 7, wherein the plurality of hierarchical levels include account level, transaction level, and purchased item level.

9. The method of claim 1, wherein the non-transaction data identifies items purchased via the payment transactions as recorded in the transaction data for respective accounts.

10. The method of claim 1, further comprising:

tagging, by the computing device, the transaction data with personalization data in response to requests from account holders of the respective accounts; and

controlling, by the computing device, access to the transaction data in accordance with the personalization data used to tag the transaction data.

11. The method of claim 1, further comprising:

providing a portal configured with a user interface to allow users of accounts in which the payment transactions are made to upload at least a portion of the non-transaction data to be stored in the computing device; and

receiving, via the portal, the portion of the non-transaction data from the users.

12. The method of claim 11, further comprising:

receiving, from merchants, purchase details of the payment transactions.

13. The method of claim 1, further comprising:

expiring a portion of the transaction data and the non-transaction data based on a data expiration policy.

14. The method of claim 13, wherein the expiring of the portion of the transaction data and the non-transaction data includes deleting the portion from the computing device.

15. The method of claim 14, wherein the data expiration policy is based at least in part on input received from users of accounts in which the payment transactions are made.

16. A computer storage medium storing instructions configured to instruct a computing device to:

store, in the computing device, transaction data recording payment transactions processed by a transaction handler, each of the payment transactions being processed to make a payment from an issuer to an acquirer via the transaction handler in response to an identifier of an account, as issued by the issuer to a customer, being submitted by a merchant to the acquirer, the issuer to make the payment on behalf of the customer, the acquirer to receive the payment on behalf of the merchant;

store, in the computing device, non-transaction data related to items purchased via the payment transactions as recorded in the transaction data for respective accounts;

tag, by the computing device, at least a portion of the transaction data and the non-transaction data with personalization data in response to requests from account holders of the respective accounts; and

control, by the computing device, access to the portion of the transaction data and the non-transaction data in accordance with the personalization data.

17. A computing device, comprising:

a transaction handler configured to process payment transactions, each of the payment transactions being processed to make a payment from an issuer to an acquirer via the transaction handler in response to an identifier of an account, as issued by the issuer to a customer, being submitted by a merchant to the acquirer, the issuer to make the payment on behalf of the customer, the acquirer to receive the payment on behalf of the merchant;

a data warehouse coupled with the transaction handler to store transaction data recording the payment transactions processed by the transaction handler;

a portal coupled with the data warehouse and configured to provide a user interface to receive personalization data and to tag at least a portion of the transaction data and the non-transaction data with the personalization data; and

a broke engine coupled with the portal to control access to the portion of the transaction data and the non-transaction data in accordance with the personalization data.

18. The computing device of claim 17, wherein the personalization data includes identifying at least one of:

a purpose of respective tagged data;

permitted usages of respective tagged data;

permissible context in which access to respective tagged is granted; and

entities who are permitted to receive respective tagged data.

19. The computing device of claim 18, wherein the portal is configured to provide users of respective payment accounts in which the payment transactions are made with access to transaction data and non-transaction data associated with the respective payment accounts.

20. The computing device of claim 18, wherein the user interface is configured to allow tagging of data in a hierarchy from account level, to transaction level, and to purchased item level.