Simulated Payment Interface for Mobile Transaction Speed
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face inconvenience and inefficiency when making online payments, as they often need to load separate payment applications, which can be time-consuming and complicated, especially when authentication is required.
Innovation Solution
A method and system for processing payments on a mobile terminal that allows users to initiate payments through a pre-set payment platform, selecting between different loading processes based on the internet connection type, either loading the payment application immediately for enhanced security or simulating payment interfaces in the purchase application to streamline the payment process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the payment application is loaded immediately in the foreground process, then the security and encryption capabilities are enhanced, but the loading time and operational complexity increase
Solution Approach 1:
The patent creates simulated payment interfaces within the purchase application that replicate the functionality of the actual payment application. These simulated interfaces allow users to complete payment operations without loading the full payment application, thereby reducing loading time while maintaining operational capability for standard transactions
Solution Approach 2:
The system pre-loads or pre-prepares payment interfaces and authentication mechanisms in the background before they are actually needed. This allows the payment application to be ready for immediate use when security is required, without causing delays during the user-initiated payment process
2Reliability
If the payment application is loaded immediately in the foreground process, then the encryption capabilities are improved, but the ease of operation deteriorates
Solution Approach 1:
Simulated payment interfaces are embedded within the purchase application, allowing users to access payment functionality directly without switching applications or dealing with complex loading processes. The simulated interfaces provide the same user experience as the full payment application for routine operations
Solution Approach 2:
The payment functionality is merged into the purchase application through integrated simulated interfaces. This consolidation allows users to complete the entire purchase and payment process within a single application context, eliminating the need to load separate payment applications while maintaining security through selective activation of encryption capabilities
3Productivity
If the payment application is simulated in the purchase application, then the loading time is reduced, but the security capabilities are compromised
Solution Approach 1:
The system dynamically adjusts between simulated and actual payment application modes based on security requirements. For standard transactions, the simulated interfaces provide fast processing. When security risks are detected or high-security transactions are initiated, the system seamlessly transitions to loading the actual payment application with full encryption capabilities
Solution Approach 2:
The simulated payment interfaces act as an intermediary layer between the user and the actual payment application. They handle routine payment operations efficiently while providing a secure gateway that can trigger the full payment application when enhanced security is needed, thus bridging the gap between speed and security
Data Source
AI summary
Method and device for processing a payment are disclosed. The method is performed at a user device and includes: receiving a user instruction for starting a payment through a pre-set payment platform; selecting a respective loading process from a plurality of loading processes for invoking a payment application, wherein: the plurality of loading processes include: a first loading process for invoking the payment application immediately in a foreground process and a second loading process for simulating at least one payment interface of the payment application in the purchase application before loading the payment application in the user device; and presenting a first payment interface at the mobile terminal in response to the user instruction and the selection of the respective loading process.