Event Message Aggregation for Identity Fraud Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for detecting identity fraud are inefficient, often taking weeks or months to recognize, and can increase the risk of fraud due to the need for manual account verification and generate many false positives, making it difficult to sustain and effectively combat identity theft.
Innovation Solution
A computer-implemented method that involves an aggregating entity receiving event messages from transaction entities, which include a token associating the user with an account and a description of the event, allowing for the aggregation of indicators of events of interest without sensitive information, enabling real-time monitoring and reducing the risk of fraud detection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual account verification is used for fraud detection, then detection capability is improved, but time consumption and operational complexity increase significantly
Solution Approach 1:
The patent replaces manual mechanical verification processes with automated electronic systems. The aggregating entity automatically collects event data from multiple transaction entities, aggregates indicators, and generates fraud alerts without human intervention, thereby reducing detection time while maintaining reliability.
Solution Approach 2:
The patent introduces an intermediary aggregating entity that mediates between transaction entities and end users. This intermediary automatically aggregates event indicators from multiple sources and presents consolidated information, eliminating the need for users to manually verify each account and significantly reducing time consumption.
2Extent of automation
If pattern recognition methods are used for fraud detection, then automation level is improved, but false positive rate increases
Solution Approach 1:
The patent segments fraud detection into distinct event types (e.g., login events, transaction events, account creation events) with specific indicators for each type. This segmentation allows for more precise pattern recognition tailored to each event category, reducing false positives while maintaining high automation levels.
Solution Approach 2:
The patent changes the parameters used for pattern recognition by focusing on specific event indicators (such as unusual login locations, abnormal transaction amounts, or suspicious account behaviors) rather than generic patterns. This parameter refinement improves detection accuracy and reduces false positives.
3Reliability
If users periodically access all accounts for self-policing, then fraud detection capability is improved, but operational complexity and security risk increase
Solution Approach 1:
The patent merges multiple account verification processes into a single unified interface provided by the aggregating entity. Users receive consolidated event indicators from all their accounts in one location, eliminating the need to access and verify each account separately, thereby reducing operational complexity.
Solution Approach 2:
The system enables users to self-monitor their accounts through automated event indicators and alerts provided by the aggregating entity. Users can configure their own monitoring preferences and receive notifications only when relevant events occur, reducing the burden of continuous manual verification.
4Measurement precision
If sensitive information is transmitted for account verification, then detection accuracy is improved, but security risk increases
Solution Approach 1:
The patent extracts only the necessary event indicators (such as transaction amounts, locations, and timestamps) from complete sensitive account information. The aggregating entity processes and aggregates these extracted indicators without requiring users to transmit or expose their full sensitive data, thereby maintaining verification accuracy while reducing security risks.
Data Source
AI summary
A transaction entity handles event messages associated with events of interest. At least one type of event is identified that is of interest to a user. Each type of event further corresponds to an event type that is to be repeated by a transaction entity to an aggregating entity. Further, a description is associated with each identified type of event. The transaction entity identifies an occurrence of an event that is an identified type of event and generates an event message comprising a token that associates the user with an account maintained by the aggregating and the description that is associated with the identified type of event corresponding to the identified occurrence of the event. The event message is transmitted to the aggregating entity.


