Event-Driven Fraud Detection Architecture

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Financial institutions face challenges in providing real-time account balances and detecting fraud due to high latency and inaccurate data from various financial transaction processing systems, which use different data formats and record milestones differently, making it difficult to obtain a complete historical record for transactions.

Innovation Solution

An event-driven architecture that listens for financial transaction events, enriches transaction data in real-time, and publishes enriched events to an event stream, allowing for reduced latency, accurate account information, and improved fraud detection by analyzing transaction data throughout its lifecycle.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If financial institutions make many requests to various financial transaction processing systems to obtain real-time transaction information, then the completeness of transaction data is improved, but the latency in providing current information increases

Engineering Contradiction:

Improvecompleteness of transaction dataVSAvoidlatency in providing account balance

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by establishing event subscriptions with financial transaction processing systems in advance. Event listeners are configured to automatically receive transaction events as they occur, eliminating the need for repeated requests. This preliminary setup enables real-time data capture without latency, resolving the contradiction between data completeness and response time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where event listeners continuously monitor transaction events and automatically update account balance information. This continuous feedback loop ensures that the most current transaction data is always available without requiring additional requests, maintaining both data completeness and real-time responsiveness.

Inventive Principle:

Principle #23Feedback

2Productivity

If financial institutions retrieve raw data directly from external systems, then the operational load on internal systems is reduced, but the accuracy and reliability of account information decreases

Engineering Contradiction:

Improveoperational efficiencyVSAvoidaccuracy of account information

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system introduces an intermediary layer consisting of event listeners and data processing components that receive raw transaction events from external systems. This intermediary layer enriches, validates, and standardizes the data before it reaches internal systems, ensuring high accuracy while maintaining operational efficiency. The intermediary acts as a buffer that enhances data quality without adding significant operational burden.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If different financial transaction processing systems use different data formats and record different data milestones, then the versatility of the system is improved, but the difficulty of obtaining a complete historical record increases

Engineering Contradiction:

Improvecompatibility with multiple transaction systemsVSAvoiddifficulty of obtaining complete transaction history

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a universal event listener framework that can handle multiple data formats and transaction milestones from different financial processing systems. The event listeners are designed with multi-functional capabilities to parse, normalize, and standardize diverse event formats into a unified structure. This universal approach enables the system to maintain complete transaction histories across multiple systems without increasing complexity, as the same framework handles all variations.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11803854B1System and method for fraud detection using event driven architecture

Publication Date: 2023.10.31 UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA)

AI summary

A system and method of providing real time account information for financial accounts is disclosed. The system includes an event based architecture including an event stream. Financial transaction processing systems publish transaction events to the event stream. A transaction service listening to the event stream detects new transaction events. The transaction service takes action to enrich transaction data. A middleware system reconciles existing transactions and persists transaction records in long term storage. The system can detect fraudulent transactions before the transactions have been posted to the financial account. The system can also be used to provide real time notifications to customers about potential fraudulent activity.