Distributed Cache Rule Exclusion for Real-Time Payments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Real-Time Payments (RTP) systems face challenges in low latency rule exclusion due to high latency in legacy infrastructure, making it difficult to execute chargeback or reversal protection and risk rules in real-time, especially in scenarios involving money laundering and fraud.
Innovation Solution
A computer-implemented method and system that stores rules in a distributed cache associated with accounts in an RTP network, allowing for real-time account level exclusion directives to be applied based on transaction parameters, enabling the exclusion of rules for specific transactions and processing them without applying the rules when an exclusion directive is determined.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If legacy infrastructure is used for rule exclusion, then system stability is maintained, but processing latency increases and real-time capability is lost
Solution Approach 1:
The system segments the rule exclusion functionality into a separate real-time processing component that operates independently from the legacy infrastructure. This allows the legacy system to maintain stability while the segmented real-time component handles low-latency rule exclusions using distributed caching and event streaming technology.
Solution Approach 2:
An event streaming platform acts as an intermediary between the legacy infrastructure and the real-time processing requirements. It receives events from the legacy system, processes rule exclusions in real-time using distributed caches, and returns results without requiring the legacy infrastructure to change, thus maintaining stability while enabling real-time capability.
2Speed
If real-time processing is implemented, then processing speed improves, but system complexity increases due to distributed cache and event streaming infrastructure
Solution Approach 1:
The distributed caching layer and event streaming platform are designed as universal infrastructure components that serve multiple functions: real-time rule exclusion, transaction monitoring, risk assessment, and compliance checking. This multi-functionality reduces overall system complexity by consolidating multiple processing requirements into a single unified platform.
Solution Approach 2:
The system implements self-service mechanisms where the distributed cache automatically manages data expiration, the event streaming platform handles event routing and filtering, and the rule engine dynamically loads and unloads rules based on transaction patterns. This automation reduces operational complexity and maintenance overhead.
3Reliability
If multiple risk rules are executed in parallel, then comprehensive risk coverage is achieved, but processing latency increases due to parallel execution overhead
Solution Approach 1:
Risk rules are pre-compiled and cached in the distributed caching layer before transactions occur. When a transaction is processed, the system retrieves pre-compiled rule logic from the cache rather than compiling and executing rules in real-time, significantly reducing processing latency while maintaining comprehensive risk coverage through parallel execution of cached rules.
Data Source
AI summary
Systems, methods, and computer program products may store, in a distributed cache, a rule associated with a plurality of accounts in a Real-Time Payments (RTP) network, the rule being stored in association with account data associated with the plurality of accounts; receive an account level exclusion directive associated with the account; store, in the distributed cache, the account level exclusion directive in association with the account; receive transaction data associated with a transaction in the RTP network between the account and another account; retrieve, from the distributed cache, the rule, the account level exclusion directive, and the account data associated with the account; exclude, based on the account level exclusion directive, use of the rule for processing the transaction; and process, without applying the rule, the transaction in the RTP network.