Transaction Conversion System for Non-Internet Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication methods for cardholder verification are primarily designed for Internet-based transactions and do not effectively address the need for secure authentication in non-Internet based transactions, such as mobile top-ups and proximity payments, which lack the benefits of cardholder signatures and specialized authentication programs.
Innovation Solution
A transaction conversion system that bridges non-Internet based transactions to Internet protocols by using a network robot and application containers to facilitate authentication through existing Internet-based authentication programs, allowing for secure authentication across diverse communication platforms and protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If standard credit cards are used for e-commerce transactions, then transaction convenience is improved, but authentication security and fraud protection deteriorate
Solution Approach 1:
The patent introduces an authentication intermediary system that mediates between the cardholder and the merchant. This intermediary verifies the cardholder's identity through multiple factors (password, PIN, biometric data) before authorizing the transaction, thus enhancing security without significantly impacting transaction convenience for legitimate users.
Solution Approach 2:
The patent implements preliminary authentication actions before the actual transaction occurs. The cardholder must complete verification steps (entering password, PIN, or providing biometric data) in advance, allowing the system to pre-validate identity and authorize or reject transactions before goods or services are delivered.
2Reliability
If Internet authentication initiatives are implemented, then e-commerce fraud protection is improved, but applicability to non-Internet transactions deteriorates
Solution Approach 1:
The patent creates a universal authentication framework that can operate across multiple platforms and transaction types. The same authentication mechanisms (password verification, PIN validation, biometric scanning) can be deployed for both Internet-based e-commerce and non-Internet transactions such as mobile top-ups, proximity payments, and telephone orders, making the system adaptable to diverse transaction environments.
3Reliability
If separate authentication programs are developed for each transaction type, then transaction-specific security is improved, but system complexity and development burden increase
Solution Approach 1:
The patent implements a single universal authentication program that can handle multiple transaction types through a standardized interface. The authentication core remains the same across different transaction scenarios, reducing system complexity while maintaining transaction-specific security requirements through configurable verification methods.
Solution Approach 2:
The patent segments the authentication system into modular components that can be independently configured for different transaction types. The authentication flow is divided into separate verifiable steps (identity verification, credential validation, authorization) that can be selectively applied based on transaction requirements, making the system manageable despite its versatility.
Data Source
AI summary
A method is provided for completing an authenticated commercial transaction over an internet protocol (IP) network (40) for an account holder (60) engaged in the transaction via a non-IP based telecommunications platform (30). The method includes: receiving a first message from the account holder (60) via the non-IP based telecommunications platform (30), the first message triggering authentication of the account holder (60) and being in a first communication format; establishing account information for a payment instrument being used in the transaction based upon content in the first message; generating a second message using a second communication format different from the first format, the second message including the established account information; submitting the second message via the IP network (40) to a network entity (110, 200) such that an authentication document is generated (120), the authentication document (120) containing an input field (122); generating a third message using the first format, the third message being submitted to the account holder (60) via the non-IP based telecommunications platform (30) such that the account holder (60) is prompted to enter a security code; receiving a fourth message containing the entered security code from the account holder (60) via the non-IP based telecommunications platform (30), the fourth message being in the first format; and, accessing the authentication document (120) via the IP network (40) to fill-in the input field (122) of the authentication document (120) with the security code contained in the fourth message.