Authentication Bridge for Payment Transaction Data Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing back-end accounting and order management systems (OMS) often lack the capability to properly pass authentication data with transaction details for payment processing, leading to issues with fraud prevention and compliance with authentication protocols, especially when these systems were not designed with future authentication initiatives in mind.
Innovation Solution
A method and system that involves providing a document to a second party to request a transaction ID, collecting and identifying authentication data within transaction details, formatting these details according to a prescribed format, and forwarding them to a third-party acquirer, utilizing an authentication bridge to ensure proper submission and recognition of authentication data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If existing back-end accounting and order management systems are used without upgrades, then system cost and complexity are reduced, but the ability to pass authentication data to acquirers is lost
Solution Approach 1:
The patent introduces an authentication bridge as an intermediary component that sits between the existing order management system and the acquirer. This bridge captures authentication data from the authentication server, associates it with transaction records in the order management system, and forwards both to the acquirer. This resolves the contradiction by enabling authentication data passing without requiring modifications to the existing OMS infrastructure, thus maintaining low implementation cost while achieving reliable authentication data transmission.
2Reliability
If authentication data fields are added to existing transaction records, then authentication capability is improved, but system complexity and data management burden increase
Solution Approach 1:
The patent segments the authentication data handling into a separate authentication bridge component rather than integrating it directly into the order management system's transaction records. The authentication bridge maintains its own data structures for authentication data and transaction records, separating the authentication functionality from the existing OMS. This segmentation allows the OMS to remain simple while the bridge handles the complexity of authentication data capture, association, and transmission.
3Reliability
If existing order management systems are upgraded to support authentication data, then authentication capability is improved, but implementation cost increases
Solution Approach 1:
The authentication bridge serves as a mediator that enables authentication data processing without requiring upgrades to the existing order management system. The bridge independently handles authentication data capture from the authentication server, association with transaction records, and forwarding to the acquirer. This approach achieves reliable authentication data processing while avoiding the costly upgrade of the OMS infrastructure.
4Adaptability or versatility
If authentication data is stored in miscellaneous fields, then data accommodation capability is improved, but data identification and formatting reliability deteriorate
Solution Approach 1:
The authentication bridge acts as an intermediary that receives transaction records from the order management system, identifies authentication data within them, and extracts it for separate processing. The bridge maintains structured data fields for authentication data and transaction records, ensuring proper identification and formatting without relying on miscellaneous fields. This resolves the contradiction by achieving data flexibility through the bridge's dedicated data structures while maintaining reliable authentication data recognition through systematic data organization and processing.
Data Source
Figure 1
Figure 2A~2B
Figure 3
AI summary
A method is provided for passing authentication data to a third party that processes a transaction. More specifically, in connection with a transaction conducted between a first party and a second party, wherein a plurality of transaction details related to the transaction are generated, including a transaction ID which identifies the transaction and authentication data which reflects a result of an attempt to authenticate the first party, the method includes: providing the second party a document over a communications network, said document requesting a transaction ID; receiving the transaction ID over the communications network from the second party; collecting the transaction details corresponding to the received transaction ID; identifying the authentication data within the collected transaction details; formatting the transaction details according to a prescribed format; and, forwarding the formatted transaction details to the third party.