Third-Party Logic Integration in Transaction Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic transaction processing systems lack the capability for third-party organizations to exert control over the processing of electronic transactions, as they often outsource this processing to service providers, which can lead to inefficiencies and inability to handle unique transaction requirements.
Innovation Solution
A logic integration system that provides a framework for securely integrating third-party logic into electronic transaction processing, using an isolated runtime environment to execute third-party programming code, thereby allowing customized transaction processing while maintaining security and control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If merchants outsource electronic transaction processing to service providers, then the burden of implementing and maintaining sophisticated transaction processing technologies is reduced, but merchants lose control over the transaction processing flow and cannot implement customized logic
Solution Approach 1:
The system segments the transaction processing into two distinct parts: the core transaction processing engine (hosted by the service provider) and the custom logic modules (provided by merchants). This segmentation allows merchants to contribute their specialized logic without needing to implement or maintain the entire transaction processing infrastructure, thus resolving the contradiction between ease of implementation and adaptability.
Solution Approach 2:
The service provider acts as an intermediary that receives custom logic from merchants, validates it, and integrates it into the transaction processing flow. This intermediary role enables merchants to exert control over specific aspects of transaction processing without directly managing the complex infrastructure, balancing ease of implementation with customized control.
2Adaptability or versatility
If merchants implement their own electronic transaction processing systems, then they maintain full control over the transaction flow, but they must bear the burden of implementing and maintaining sophisticated secure processing technologies
Solution Approach 1:
The system extracts the complex infrastructure management responsibilities from merchants and concentrates them in the service provider's platform. Merchants only need to provide their custom logic through standardized interfaces, while the service provider handles the sophisticated secure processing technologies, validation, and integration. This extraction reduces device complexity for merchants while preserving their control over custom transaction logic.
3Adaptability or versatility
If third-party code is executed directly in the service provider's environment, then customized transaction logic can be implemented, but security risks increase due to potential malicious or erroneous code
Solution Approach 1:
The system implements a nested structure where custom third-party logic is executed within isolated sandboxed environments that are nested within the service provider's secure platform. This nesting allows custom logic to run without direct access to critical system resources, enabling adaptability while maintaining security through multiple layers of containment and control.
Solution Approach 2:
The service provider implements an intermediary validation and execution layer between the custom third-party code and the core transaction processing system. This intermediary validates the safety of uploaded logic, manages its execution in controlled environments, and mediates all interactions with the main system, thus enabling custom logic execution while mitigating security risks from potentially malicious or erroneous code.
Data Source
AI summary
Methods and systems are presented for providing a framework to securely integrate third-party logic into electronic transaction processing workflow. Third-party programming code that implements different third-party logic may be obtained and stored in a repository. A transaction processing request is received from a third-party server, and an instance of a transaction processing module is instantiated within an operating runtime environment to process a transaction according to a workflow. When the instance of the transaction processing module has reached an interruption point, the instance of the transaction processing module is suspended, and a third-party programming code is executed within an isolated runtime environment. The third-party programming code is configured to provide an output value based on attributes of the transaction. The instance of the transaction processing module then determines whether to authorize or deny the transaction based in part on the output value.