Transaction Processing Architecture for Real-Time Installment Offers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional transaction processing systems lack automated mechanisms for converting transactions into installment loans, leading to inefficiencies in identifying eligible transactions and offering installment loans in real-time.

Innovation Solution

Implementing a system that utilizes event brokers, analyzers, and ephemeral container instances to process transaction data in real-time, generating loan conversion offers, and triggering account allocations based on eligibility criteria, while ensuring data security through encryption and tokenization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If conventional transaction processing methods are used, then transaction processing is simple, but automated conversion to installment loans is not possible and real-time processing is unable

Engineering Contradiction:
Improveautomated conversion to installment loansVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system is divided into distinct functional modules: event brokers that receive transaction data, analyzers that evaluate eligibility, container instances that generate offers, and account allocation systems that execute conversions. This segmentation allows each component to perform its specific function independently, enabling automated conversion while managing complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Event brokers serve as intermediaries between transaction sources and the installment loan conversion process. They receive transaction event data, route it to appropriate analyzers, and coordinate the overall workflow. This intermediary layer enables automated processing by centralizing data reception and distribution, reducing the complexity of direct point-to-point connections.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If manual processing methods are used, then system complexity is low, but processing speed and real-time capability are insufficient

Engineering Contradiction:
Improvereal-time processing speedVSAvoidprocessing system complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-defining eligibility criteria and processing workflows before transactions occur. Event brokers are pre-configured to receive specific transaction types, and analyzers have pre-loaded conversion rules. This preparation enables real-time processing by avoiding the need for manual analysis during transaction processing moments.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous processing by keeping event brokers, analyzers, and container instances in constant operational readiness. Transaction data flows continuously through the system without interruption, and the architecture supports concurrent processing of multiple transactions simultaneously, ensuring real-time capability while managing complexity through continuous automated operation.

Inventive Principle:
Principle #20Continuity of useful action

3Loss of time

If transactions are processed without real-time analysis, then processing is simpler, but eligibility determination and offer generation occur too late

Engineering Contradiction:
Improvetime delay in offer generationVSAvoidreal-time processing system complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system replaces manual mechanical processing with automated electronic systems. Event brokers automatically receive and parse transaction data, analyzers automatically evaluate eligibility based on predefined criteria, and container instances automatically generate offers. This substitution eliminates time delays by removing manual intervention steps while managing complexity through standardized automated workflows.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If data is processed without security measures, then processing is faster, but data security and protection are compromised

Engineering Contradiction:
Improvedata securityVSAvoidsecurity implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system uses ephemeral container instances that are created temporarily for each processing task and automatically terminated afterward. These short-living containers execute processing functions and then disappear, reducing the attack surface and minimizing data exposure risks. This approach enhances security by limiting the lifespan of processing environments while managing complexity through automated lifecycle management.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS20260080465A1Real-time online transactional processing systems and methods
Publication Date: 2026.03.19 FIDELITY INFORMATION SERVICES LLC
  • US20260080465A1 patent drawing
  • US20260080465A1 patent drawing
  • US20260080465A1 patent drawing

AI summary

Systems and methods for real time, online transaction processing are disclosed. The system may include one or more memory units storing instructions and one or more processors configured to execute the instructions to perform a method. The method may include receiving, from an event broker, event data that includes account data. The operations may include using a data structure to identify an issuer system associated with the account data and an enrollment status of the issuer system. The method may include generating a filtered transaction data structure to an analyzer and receiving a result data structure. The method may include generating, based on the result data structure, a linked data structure comprising installment loan parameters and an online address. The method may include routing the linked data structure to a user device and receiving approval data that triggers an account allocation.