ALIAS REPUTATION INTERACTION SYSTEM

• US 20110047076A1
• Filed: 07/29/2010
• Published: 02/24/2011
• Est. Priority Date: 08/24/2009
• Status: Abandoned Application

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Rewis, Benjamin, Faith, Patrick, Carlson, Mark, Stan, Patrick
• Application Number:
  US12/846,764
• Publication Number:
  US 20110047076A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0609 Buyer or seller confidence or verification

Abstract

Systems and method for generating reputation information for an alias are provided. The alias is associated with an entity. Payment transaction information related to a first alias associated with a first entity is received. The payment transaction information includes payment transactions performed by the first entity. In addition, non-payment transaction information related to the first alias is also received. The non-payment transactions include transaction between the first alias and one or more objects. The payment transaction information and the non-payment transaction information is analyzed to associate the one or more objects with the first alias. Thereafter, reputation information for the first alias is generated based at least in part on the payment transaction information and the non-payment transaction information.

Claims

1. A computer-implemented method for generating reputation information for an alias, wherein the alias is associated with an entity, by a computer system, the method comprising:

receiving payment transaction information related to a first alias associated with a first entity, the payment transaction information including payment transactions performed by the first entity;

receiving non-payment transaction information related to the first alias, the non-payment transactions including transaction between the first alias and one or more objects;

analyzing the payment transaction information and the non-payment transaction information;

associating the one or more objects with the first alias based at least in part on the payment transaction information and the non-payment transaction information; and

generating reputation information for the first alias based at least in part on the payment transaction information and the non-payment transaction information related to the first alias and to the one or more objects.

2. The method of claim 1 further comprising:

receiving information about a transaction between a first object and a second object, from among the one or more objects; and

associating the second object with the first object.

3. The method of claim 2 wherein the first object and the second object includes a person, a device, or another entity.

4. The method of claim 1 further comprising:

monitoring transaction information between the first alias and the one or more objects and updating the associations between the first alias and the one or more objects.

5. The method of claim 4 wherein updating the associations include:

severing an association between a first object and the first alias;

or

creating an association between a second object and the alias where none existed before.

6. The method of claim 1 wherein the payment transaction information is received from a payment processing network.

7. The method of claim 1 wherein generating reputation information includes generating a reputation score for the first alias.

8. The method of claim 1 further comprising providing risk analysis information for a transaction between the first alias and an object after initiation of the transaction but prior to completion of the transaction.

9. The method of claim 1 further comprising:

receiving information about payment transaction and non-payment transaction of a second alias;

analyzing the information about the payment transaction and the non-payment transaction of the second alias to determine whether the second alias is associated with the first entity; and

if it is determined that the second alias is associated with the entity, associating the second alias with the first alias and associating the reputation information of the first alias with the second alias.

10. A system for generating reputation information for an entity, the system comprising:

a data receiving module configured to receive payment transaction information and non-payment transaction information of an alias associated with an entity;

an analysis module configured to analyze the payment transaction information and non-payment transaction information, and associate an object with the alias based at least in part on the payment transaction information and non-payment transaction information, wherein the payment transaction information and non-payment transaction information includes transactions between the alias and the object;

a storage module configured to store the association information between the object and the alias;

a reputation information generation module configured to receive the association information and generate reputation information for the alias based on the payment transaction information and non-payment transaction information; and

a network interface module configured to communicate with one or more external systems to receive the payment transaction information and non-payment transaction information and to send the reputation information.

11. The system of claim 10 wherein the non-payment transaction information includes information about data transmission between the alias and an object.

12. The system of claim 10 wherein the data receiving module receives the payment transaction information from a payment processing network.

13. The system of claim 12 wherein the data receiving module is further configured to periodically receive the payment transaction information between the object and the alias.

14. The system of claim 10 wherein the analysis module is further configured to:

determine whether there is a first object that shares payment transaction information and/or non-payment transaction information with a second object, wherein both the first object and the second object are associated with the alias; and

associate the first object with the second object, if it is determined that the first object shares payment transaction information and/or non-payment transaction information with the second object.

15. The system of claim 10 wherein the reputation generation module is further configured to:

receive information regarding a request for a transaction between a first object and the alias;

determine a reputation for the first object and the reputation for the alias;

determine a risk score for the transaction between the first object and the alias; and

provide the risk score to the first object and to the alias.

16. The system of claim 15 further comprising a payment processing network configured to receive the reputation information of the first object and the reputation information of the alias and determine whether to allow or deny a transaction between the first object and the alias, based at least in part on the reputation information of the first object and the reputation information of the alias.

17. The system of claim 10 wherein the object is a person, a device, or another entity.