Transaction Gateway Workflow Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Merchants face difficulties and costs in integrating and maintaining multiple payment solutions and services within their transaction management systems, leading to limitations in the services they can offer, as each solution requires individual API integration, making it cumbersome to support multiple transaction methods.
Innovation Solution
A transaction gateway apparatus that allows users to configure workflows to route transaction data to various service providers, enabling real-time integration and management of multiple payment solutions from a single platform, without the need for individual API integrations, using a user-friendly interface and processing engine to convert workflows into executable transaction routes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple payment solutions and services are integrated into a transaction management system, then the variety of transaction methods offered is improved, but the device complexity and processing overhead increase
Solution Approach 1:
The patent implements a universal gateway architecture where a single integration point handles multiple payment solutions and services. The gateway acts as a multi-functional intermediary that can route transactions to different service providers based on configured workflows, eliminating the need for separate integrations for each payment method while maintaining support for diverse transaction types
Solution Approach 2:
The gateway serves as an intermediary layer between the transaction management system and multiple payment service providers. It receives transactions from the management system, determines the appropriate routing based on workflows and rules, and forwards them to the respective service providers, thereby simplifying the overall system architecture while enabling multiple integrations
2Adaptability or versatility
If multiple payment solutions are individually integrated, then the functionality is improved, but the ease of operation and maintenance deteriorates
Solution Approach 1:
The patent merges multiple payment solution integrations into a single unified gateway structure. By combining the routing logic, configuration management, and communication protocols into one consolidated component, the system maintains diverse payment functionalities while significantly improving maintenance ease through centralized management and single-point updates
3Device complexity
If a single payment solution is used, then the device complexity is reduced, but the adaptability and customer offerings are limited
Solution Approach 1:
The gateway incorporates dynamic workflow configuration capabilities that allow the routing logic to be changed without modifying the core integration structure. Users can define different transaction routes, select appropriate service providers, and adjust routing rules based on transaction characteristics, enabling the system to adapt to various service offerings while maintaining architectural simplicity
Data Source
AI summary
In one embodiment, the present invention is a transaction gateway apparatus for effecting a transaction request, the apparatus being configured to receive transaction request data, select, based on said transaction request data, one of a plurality of workflows to be performed that defines transaction data route between said apparatus and a transaction service provider specified in said workflow, wherein said apparatus is configured to: display a user interface defining a workspace within which a user can configure a workflow; access a plurality of modules, each defining respective service provider functions, a plurality of rule sets defining conditions to be fulfilled for a transaction data route to follow a specified path of a workflow; display selectable data representative of said modules and rule sets in said work space; enable a user to configure a visual representation of a workflow by: selecting a transaction type or parameter to be associated with a workflow; selecting combinations of one or more modules and rule sets to be included in said workflow, said apparatus being configured to display said selected combination in said work space; selectively defining visual links between said modules and/or rule sets to define respective workflow paths; and convert a user-configured workflow to an executable transaction data route for execution in the event that transaction request data received by said apparatus is determined thereby to match a transaction type or parameter associated with said workflow.