System and method for presenting suspect activity within a timeline
First Claim
Patent Images
1. A computer system for fraud detection, the system comprising:
- a processor;
a presentation engine;
an analytics engine;
a memory;
storing data describing;
activity data of a suspect activity, the suspect activity being associated with an account; and
account data of at least one balance metric for the account, the account data including at least two of;
a ledger balance representing an amount of money reported to a customer of the account,an available balance representing an accessible amount of money, anda collected balance representing an amount of money collected by a financial institution; and
storing executable instructions that when executed by the processor cause the presentation engine and the analytics engine to perform operations comprising;
receiving, via the analytics engine, an indication of a suspect activity;
displaying, via the presentation engine, a representation of the suspect activity on a graphical user interface, based on the indication of the suspect activity;
displaying, via the presentation engine, a representation of differences on the graphical user interface, the representation comprising differences between at least two of a ledger balance, an available balance, and a collected balance;
determining, by the analytics engine, local minimums of the representation of differences;
displaying, via the presentation engine, a lower concave hull between the local minimums of the representation of differences on the graphical user interface;
determining, by the analytics engine, a set of user interface components associated with at least one reason code, wherein the reason code is indicative of the suspect activity;
selecting, by the analytics engine, based on the at least one reason code, one of the representations of the suspect activity, the representation of the differences, or the representation of a timeline;
selecting, by the analytics engine, a period of time based on the at least one reason code associated with the suspect activity and indicative of at least one basis for classifying the activity as suspect;
determining, by the analytics engine, a priority order of the representation of the suspect activity, the representation of the differences, and the representation of the timeline to reflect the selection;
displaying, via the presentation engine, based on the priority order, a representation of the timeline on the graphical user interface, the timeline comprising an indication of activity during the period of time identified as potentially fraudulent; and
emphasizing a subset of data displayed on the graphical user interface, based on one or more determinations for an improved end-user workflow.
2 Assignments
0 Petitions
Accused Products
Abstract
Systems and methods for presenting fraud detection information are presented. In one example, a computer system analyzes empirical data to detect potentially fraudulent activity and alerts users of the potentially fraudulent activity via a fraud detection user interface. The fraud detection user interface determines a set of user interface components to suitable to present the potentially fraudulent activity and presents facts associated with the potentially fraudulent activity to a user for further analysis and investigation.
-
Citations
20 Claims
-
1. A computer system for fraud detection, the system comprising:
-
a processor; a presentation engine; an analytics engine; a memory; storing data describing; activity data of a suspect activity, the suspect activity being associated with an account; and account data of at least one balance metric for the account, the account data including at least two of; a ledger balance representing an amount of money reported to a customer of the account, an available balance representing an accessible amount of money, and a collected balance representing an amount of money collected by a financial institution; and storing executable instructions that when executed by the processor cause the presentation engine and the analytics engine to perform operations comprising; receiving, via the analytics engine, an indication of a suspect activity; displaying, via the presentation engine, a representation of the suspect activity on a graphical user interface, based on the indication of the suspect activity; displaying, via the presentation engine, a representation of differences on the graphical user interface, the representation comprising differences between at least two of a ledger balance, an available balance, and a collected balance; determining, by the analytics engine, local minimums of the representation of differences; displaying, via the presentation engine, a lower concave hull between the local minimums of the representation of differences on the graphical user interface; determining, by the analytics engine, a set of user interface components associated with at least one reason code, wherein the reason code is indicative of the suspect activity; selecting, by the analytics engine, based on the at least one reason code, one of the representations of the suspect activity, the representation of the differences, or the representation of a timeline; selecting, by the analytics engine, a period of time based on the at least one reason code associated with the suspect activity and indicative of at least one basis for classifying the activity as suspect; determining, by the analytics engine, a priority order of the representation of the suspect activity, the representation of the differences, and the representation of the timeline to reflect the selection; displaying, via the presentation engine, based on the priority order, a representation of the timeline on the graphical user interface, the timeline comprising an indication of activity during the period of time identified as potentially fraudulent; and emphasizing a subset of data displayed on the graphical user interface, based on one or more determinations for an improved end-user workflow. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A computer implemented method, comprising:
-
storing, in a memory, activity data describing a suspect activity, the suspect activity being associated with an account; storing, in the memory, account data describing at least one balance metric for the account, the account data including at least two of; a ledger balance representing an amount of money reported to a customer of the account, an available balance representing an accessible amount of money, and a collected balance representing an amount of money collected by a financial institution; receiving, via an analytics engine, an indication of a suspect activity; displaying, via a presentation engine, a representation of the suspect activity on a graphical user interface, based on the indication of the suspect activity; displaying, via the presentation engine, a representation of differences on the graphical user interface, the representation comprising differences between at least two of a ledger balance, an available balance, and a collected balance; determining, via the analytics engine, local minimums of the representation of differences; displaying, via the presentation engine, a lower concave hull between the local minimums of the representation of differences on the graphical user interface; determining, by the analytics engine, a set of user interface components associated with at least one reason code, wherein the reason code is indicative of the suspect activity; selecting, by the analytics engine, based on the at least one reason code, one of the representations of the suspect activity, the representation of the differences, or the representation of a timeline; selecting, by the analytics engine, a period of time based on the at least one reason code associated with the suspect activity and indicative of at least one basis for classifying the activity as suspect; determining, by the analytics engine, a priority order of the representation of the suspect activity, the representation of the differences, and the representation of the timeline to reflect the selection; and displaying, by the presentation engine, based on the priority order, on the graphical user interface, the representation of a timeline, the timeline comprising an indication of activity during the period of time identified as potentially fraudulent; and emphasizing a subset of data displayed on the graphical user interface, based on one or more determinations for an improved end-user workflow. - View Dependent Claims (16, 17, 18)
-
-
19. A non-transitory computer readable medium having instructions stored thereon that, when executed by at least one processor, cause an analytics engine and a presentation engine to perform operations comprising:
-
storing, in a memory, activity data describing a suspect activity, the suspect activity being associated with an account; storing, in the memory, account data describing at least one balance metric for the account, the account data including at least two of; a ledger balance representing an amount of money reported to a customer of the account, an available balance representing an accessible amount of money, and a collected balance representing an amount of money collected by a financial institution; receiving, via the analytics engine, an indication of a suspect activity; displaying, via a presentation engine, a representation of the suspect activity on a graphical user interface, based on the indication of the suspect activity; displaying, by the presentation engine, a representation of differences on the graphical user interface, the representation comprising differences between at least two of a ledger balance, an available balance, and a collected balance; determining, by the analytics engine, local minimums of the representation of differences; displaying, by the analytics engine, a lower concave hull between the local minimums of the representation of differences on the graphical user interface; determining, by the analytics engine, a set of user interface components associated with at least one reason code, wherein the reason code is indicative of the suspect activity; selecting, by the analytics engine, based on the at least one reason code, one of the representations of the suspect activity, the representation of the differences, or the representation of the timeline; selecting, by the analytics engine, a period of time based on the at least one reason code associated with the suspect activity and indicative of at least one basis for classifying the activity as suspect; determining, by the analytics engine, a priority order of the representation of the suspect activity, the representation of the differences, and the representation of the timeline to reflect the selection; and displaying, by the presentation engine, based on the priority order, the representation of a timeline, on the graphical user interface comprising an indication of activity during the period of time identified as potentially fraudulent; and emphasizing a subset of data displayed on the graphical user interface, based on one or more determinations for an improved end-user workflow. - View Dependent Claims (20)
-
Specification