Fraud detection system automatic rule population engine

• US 9,760,861 B2
• Filed: 04/27/2012
• Issued: 09/12/2017
• Est. Priority Date: 04/29/2011
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Boding, B. Scott, Siddens, Cory H.
• Primary Examiner(s): Fleischer, Mark A
• Application Number:
  US13/458,910
• Publication Number:
  US 20120278246A1
• Time in Patent Office: 1,964 Days
• Field of Search: 705 38, 705 44, 705318, 705 67, 705 76, 705 18, 705 728
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Embodiments of the invention are directed to a fraud detection system that stores fraud detection rules and merchant profiles. The fraud detection system allows a user to designate fraud detection rules as core fraud detection rules, and the fraud detection system can automatically populate new merchant profiles with the user'"'"'s core fraud detection rules.

Claims

1. A method comprising:

determining a plurality of existing fraud-detection rules, wherein each existing fraud-detection rule comprises at least one condition;

providing, by a server computer, a user interface on a client computer for viewing the plurality of existing fraud-detection rules;

receiving, by the server computer from the client computer, a user selection of a set of the fraud-detection rules for a first merchant profile for a user via the user interface, wherein the set of the fraud-detection rules is a subset of the plurality of existing fraud-detection rules;

activating a core rule indicator to identify, by the server computer, the selected set of the fraud-detection rules as a core fraud-detection rules set for the user in a database;

subsequently receiving, by the server computer from the client computer, a request to generate a second merchant profile for the user;

generating, by the server computer, the second merchant profile in response to the request;

retrieving, by the server computer, the core fraud-detection rules set associated with the user from the database;

automatically populating, by the server computer, the second merchant profile for the user with the core fraud-detection rules set based at least in part on the core rule indicator;

providing, by the server computer and at a second time, the user interface on the client computer for viewing the set of existing fraud-detection rules for receiving one or more additional fraud-detection rules corresponding with the second merchant profile;

receiving the one or more additional fraud-detection rules from the plurality of existing fraud-detection rules, wherein the one or more additional fraud-detection rules are selected from the plurality of existing fraud-detection rules;

modifying, by the server computer, the second merchant profile to include the one or more additional fraud-detection rules received from the client computer; and

using, by the server computer, the fraud-detection rules from the core fraud-detection rules set and the one or more additional fraud-detection rules to process transaction details received in an authorization request message transmitted from a merchant access device to the server computer, the authorization request message transmitted between a user computer and the merchant access device using a communications network.

2. The method of claim 1 further comprising:

selecting a core fraud-detection rule from the core fraud-detection rules set; and

associating the selected core fraud-detection rule with one or more of a plurality of previously generated merchant profiles.

3. The method of claim 2 further comprising:

associating an action with the selected core fraud-detection rule for each of the one or more of the plurality of previously generated merchant profiles, wherein the action is either to monitor, accept, reject or review a transaction.

4. The method of claim 1, wherein modifying the second merchant profile to include the one or more additional fraud-detection rules further comprises:

receiving, by the server computer, a second request to generate a new fraud-detection rule for the second merchant profile, the second request including at least one condition for the new fraud-detection rule;

generating, by the server computer, the new fraud-detection rule using the at least one condition; and

recording, by the server computer, the new fraud-detection rule with the second merchant profile in the database.

5. The method of claim 1, further comprising:

providing, by the server computer, the user interface including a first user-selectable option to generate the second merchant profile with the core fraud-detection rules set and a second user-selectable option to generate the second merchant profile without the core fraud-detection rules set, wherein the request to generate the second merchant profile for the user includes a user selection for the second merchant profile to be generated with the core fraud-detection rules set.

6. The method of claim 1, further comprising:

subsequently receiving, by the server computer, a request to generate a third merchant profile for the user;

generating, by the server computer, the third merchant profile in response to the request;

retrieving, by the server computer, the core fraud-detection rules set associated with the user; and

automatically populating, by the server computer, the third merchant profile for the user with the core fraud-detection rules set.

7. The method of claim 1, wherein the authorization request message complies with ISO 8583 standard.

8. The method of claim 1, wherein the merchant access device is a point of sale (POS) terminal.

9. A server computer comprising:

a processor; and

a non-transitory computer-readable storage medium, comprising code executable by the processor for implementing a method comprising;

determining a plurality of existing fraud-detection rules, wherein each existing fraud-detection rule comprises at least one condition;

providing a user interface on a client computer for viewing the plurality of existing fraud-detection rules;

receiving a user selection of a set of the fraud-detection rules for a first merchant profile for a user via the user interface from the client computer, wherein the set of the fraud-detection rules is a subset of the plurality of existing fraud-detection rules;

activating a core rule indicator to identify the selected set of the fraud-detection rules as a core fraud-detection rules set for the user in a database;

subsequently receiving a request to generate a second merchant profile for the user from the client computer;

generating the second merchant profile in response to the request;

retrieving the core fraud-detection rules set associated with the user from the database;

automatically populating the second merchant profile for the user with the core fraud-detection rules set based at least in part on the core rule indicator;

providing, at a second time, the user interface on the client computer for viewing the set of existing fraud-detection rules for receiving one or more additional fraud-detection rules corresponding with the second merchant profile;

receiving the one or more additional fraud-detection rules from the plurality of existing fraud-detection rules, wherein the one or more additional fraud-detection rules are selected from the plurality of existing fraud-detection rules;

modifying the second merchant profile to include the one or more additional fraud-detection rules received from the client computer; and

using the fraud-detection rules from the core fraud-detection rules set and the one or more additional fraud-detection rules to process transaction details received in an authorization request message transmitted from a merchant access device to the server computer, the authorization request message transmitted between a user computer and the merchant access device using a communications network.

10. The server computer of claim 9, wherein the method further comprises:

selecting a core fraud-detection rule from the core fraud-detection rules set; and

associating the selected core fraud-detection rule with one or more of a plurality of previously generated merchant profiles.

11. The server computer of claim 10, wherein the method further comprises:

associating an action with the selected core fraud-detection rule for each of the one or more of the plurality of previously generated merchant profiles, wherein the action is either to monitor, accept, reject or review a transaction.

12. The server computer of claim 9, wherein modifying the second merchant profile to include the one or more additional fraud-detection rules further comprises:

receiving a second request to generate a new fraud-detection rule for the second merchant profile, the second request including at least one condition for the new fraud-detection rule;

generating the new fraud-detection rule using the at least one condition; and

recording the new fraud-detection rule with the second merchant profile in the database.

13. The server computer of claim 9, wherein the method further comprises:

providing the user interface including a first user-selectable option to generate the second merchant profile with the core fraud-detection rules set and a second user-selectable option to generate the second merchant profile without the core fraud-detection rules set, wherein the request to generate the second merchant profile for the user includes a user selection for the second merchant profile to be generated with the core fraud-detection rules set.

14. A method comprising:

receiving, by a client computer, a plurality of existing fraud-detection rules from a fraud-detection system, wherein each existing fraud-detection rule comprises at least one condition;

displaying, via a user interface provided by the client computer, the plurality of existing fraud-detection rules from the fraud-detection system;

receiving a selection of a set of fraud-detection rules for a first merchant profile via the user interface, wherein the set of fraud-detection rules is a subset of the plurality of existing fraud-detection rules;

transmitting, by the client computer to the fraud-detection system, from the plurality of fraud-detection rules, the set of fraud-detection rules for the first merchant profile, wherein the set of fraud-detection rules is recorded by the fraud-detection system as a core fraud-detection rules set for a user in a database by activating a core rule indicator;

transmitting, by the client computer at a second time, a request to the fraud-detection system to generate a second merchant profile for the user;

displaying at least the core fraud-detection rules set associated with the user retrieved from the database based at least in part on the core rule indicator;

receiving a second selection that comprises one or more additional fraud-detection rules via the user interface to add to the second merchant profile, wherein the second merchant profile is generated in response to the second selection, and wherein the second merchant profile is automatically populated with the retrieved core fraud-detection rules set associated with the user; and

transmitting, by the client computer via the user interface, from the plurality of fraud-detection rules, a second set of fraud-detection rules for the second merchant profile that comprises at least the core fraud-detection rules set and the one or more additional fraud-detection rules,

wherein the fraud-detection rules from the core fraud-detection rules set and the one or more additional fraud-detection rules are used to process transaction details received in an authorization request message transmitted from a merchant access device to the fraud-detection system, the authorization request message transmitted between a user computer and the merchant access device using a communications network.

15. The method of claim 14, further comprising:

transmitting, by the client computer, conditions for creating a new core fraud-detection rule;

displaying, by the client computer, the new core fraud-detection rule; and

transmitting, by the client computer, a request to add the new core fraud-detection rule to one or more of a plurality of previously generated merchant profiles.

16. The method of claim 15, further comprising:

activating for each of the one or more of the plurality of previously generated merchant profiles an action to monitor, accept, reject, or review a transaction.

17. The method of claim 15, wherein the new core fraud-detection rule is stored in the database and associated with the one or more of the plurality of previously generated merchant profiles in a merchant profiles database.

18. A client computer comprising:

a processor; and

a non-transitory computer-readable storage medium, comprising code executable by the processor for implementing a method comprising;

receiving a plurality of existing fraud-detection rules from a fraud-detection system via a user interface, wherein each existing fraud-detection rule comprises at least one condition;

displaying, via the user interface provided by the client computer, the plurality of existing fraud-detection rules from the fraud-detection system;

receiving a selection of a set of fraud-detection rules for a first merchant profile via the user interface, wherein the set of fraud-detection rules is a subset of the plurality of existing fraud-detection rules;

transmitting to the fraud-detection system from the plurality of fraud-detection rules, the set of fraud-detection rules for the first merchant profile, wherein the set of fraud-detection rules is recorded by the fraud-detection system as a core fraud-detection rules set for a user in a database by activating a core rule indicator;

transmitting at a second time, a request to the fraud-detection system to generate a second merchant profile for the user;

displaying at least the core fraud-detection rules set associated with the user retrieved from the database based at least in part on the core rule indicator;

receiving a second selection that comprises one or more additional fraud-detection rules via the user interface to add to the second merchant profile, wherein the second merchant profile is generated in response to the second selection, and wherein the second merchant profile is automatically populated with the retrieved core fraud-detection rules set associated with the user; and

transmitting, by the client computer via the user interface, from the plurality of fraud-detection rules, a second set of fraud-detection rules for the second merchant profile that comprises at least the core fraud-detection rules set and the one or more additional fraud-detection rules,

wherein the fraud-detection rules from the core fraud-detection rules set and the one or more additional fraud-detection rules are used to process transaction details received in an authorization request message transmitted from a merchant access device to the fraud-detection system, the authorization request message transmitted between a user computer and the merchant access device using a communications network.

19. The client computer of claim 18, wherein the method further comprises:

transmitting conditions for creating a new core fraud-detection rule;

displaying the new core fraud-detection rule; and

transmitting a request to add the new core fraud-detection rule to one or more of a plurality of previously generated merchant profiles.

20. The client computer of claim 19, wherein the method further comprises:

activating for each of the one or more of the plurality of previously generated merchant profiles an action to monitor, accept, reject or review a transaction.

21. The client computer of claim 19, wherein the new core fraud-detection rule is stored in the database and associated with the one or more of the plurality of previously generated merchant profiles in a merchant profiles database.