Method and System for Fraud Detection and Notification

• US 20120203698A1
• Filed: 02/07/2012
• Published: 08/09/2012
• Est. Priority Date: 02/07/2011
• Status: Abandoned Application

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Duncan, Dustin, Mai, Gloria
• Application Number:
  US13/368,101
• Publication Number:
  US 20120203698A1
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 20/425 using two different networks, one for transaction and one for security confirmation

Abstract

Methods and systems for an automated dialer enhancements. The methods may analyze transactions. The analysis of the transactions may comprise of triggers which are met when a delta threshold is exceeded, when an immediate threshold is exceeded, or when a rule is met. A notification strategy is implemented after a trigger is fired and accounts may be blocked or held. Reappearing transactions are flagged and escalated.

Claims

1. A method comprising:

a) receiving a transaction case comprising transaction data associated with an account, wherein the transaction data includes a first transaction score;

b) determining, by a server computer, a transaction score delta using the first transaction score and a second transaction score;

c) determining if the transaction score delta meets a delta trigger;

d) determining an immediate transaction score;

e) determining if the immediate transaction score meets an immediate trigger;

f) determining if the transaction data in the transaction case meets one or more rule triggers; and

g) performing additional processing if steps c), e), and f) are met.

2. The method of claim 1, wherein performing the additional processing comprises performing a notification strategy, which notifies a user that a transaction case is likely fraudulent.

3. The method of claim 2, wherein performing the additional processing further comprises storing the transaction data in the transaction case in a database, and wherein the steps a), c), d), e), f), and g) are also performed by the server computer.

4. The method of claim 1, further comprising:

analyzing, by the server computer, the transaction data in the transaction case and stored additional transaction data in the database;

determining, by the server computer, a pattern associated with previous transaction cases;

determining, by the server computer, if the transaction data in the transaction case meets one or more strategy rule triggers, wherein the strategy rule trigger is associated with a strategy rule based on the pattern; and

performing the notification strategy if the strategy rule trigger is met, thereby determining whether the transaction case is likely to be fraudulent.

5. The method of claim 1, wherein the additional processing further comprises placing a block on the account if one or more of the delta trigger, the immediate trigger, the rule trigger, or the strategy rule trigger, are met.

6. The method of claim 3, wherein the notification strategy comprises:

contacting, in real-time, the user via at least one of the following;

SMS, e-mail, phone call, and interactive voice response;

requesting further action from the user if the user is not immediately reached; and

recording and storing, in a database, whether the user has been contacted.

7. The method of claim 6, further comprising placing a block on the account if one or more of the delta trigger, the immediate trigger, or the rule trigger are met, and if the user is not immediately reached.

8. The method of claim 1, wherein the delta trigger is met when the transaction score delta associated with the transaction case exceeds a threshold transaction score delta.

9. The method of claim 1, wherein the immediate trigger is met when the immediate transaction score associated with the transaction case exceeds a threshold immediate transaction score.

10. The method of claim 1, wherein the one or more rule triggers are not based on the first transaction score.

11. A server computer, comprising a processor, and a non-transitory computer readable medium comprising code executable by the processor to perform the method, the method comprising:

a) receiving a transaction case comprising transaction data associated with an account, wherein the transaction data includes a first transaction score;

b) determining a transaction score delta using the first transaction score and a second transaction score;

c) determining if the transaction score delta meets a delta trigger;

d) determining an immediate transaction score;

e) determining if the immediate transaction score meets an immediate trigger;

f) determining if the transaction data in the transaction case meets one or more rule triggers; and

g) performing additional processing if steps c), e), and f) are met.

12. The server computer of claim 11, wherein performing the additional processing comprises performing a notification strategy to a user associated with the account if one or more of the delta trigger, the immediate trigger, or the rule trigger, are met, thereby determining whether the transaction case is likely to be fraudulent.

13. The server computer of claim 12, wherein performing the additional processing further comprises storing the transaction data in the transaction case in a database, and wherein the steps a), c), d), e), f), and g) are also performed by the server computer.

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

analyzing, by the server computer, the transaction data in the transaction case and stored transaction data in the database;

determining, by the server computer, a pattern associated with previous transaction cases;

determining, by the server computer, if the transaction data in the transaction case meets one or more strategy rule triggers, wherein the strategy rule trigger is associated with a strategy rule based on the pattern; and

performing the notification strategy if the strategy rule trigger is met, thereby determining whether the transaction case is likely to be fraudulent.

15. The server computer of claim 11, wherein the additional processing further comprises placing a block on the account if one or more of the delta trigger, the immediate trigger, the rule trigger, or the strategy rule trigger, are met.

16. The server computer of claim 13, wherein the notification strategy comprises:

contacting, in real-time, the user via at least one of the following;

SMS, e-mail, phone call, and interactive voice response;

requesting further action from the user if the user is not immediately reached; and

recording and storing, in the database, whether the user has been contacted.

17. The server computer of claim 16, wherein the method further comprises placing a block on the account if one or more of the delta trigger, the immediate trigger, or the rule trigger are met, and if the user is not immediately reached.

18. The server computer of claim 11, wherein the delta trigger is met when the transaction score delta associated with the transaction case exceeds a threshold transaction score delta.

19. The server computer of claim 11, wherein the immediate trigger is met when the immediate transaction score associated with the transaction case exceeds a threshold immediate transaction score.

20. The server computer of claim 11, wherein the one or more rule triggers are not based on the first transaction score.