Wallet Subscription Authorization via Intermediate Page Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing subscription authorization processes for electronic wallets involve multiple jumps and switches, leading to poor user experience, especially in unstable network conditions, and disrupt the flow of acquisition and marketing activities, affecting overall conversion rates.
Innovation Solution
A 'one-stop' binding method is introduced, utilizing a third-party intermediate page embedded in the wallet client, which interacts with a system server and wallet server through an intermediate server, reducing jumps and completing the subscription process seamlessly without network disruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional subscription authorization process is used, then multiple jumps and switches occur between different pages and systems, but user experience deteriorates and subscription completion rate decreases
Solution Approach 1:
The patent introduces an intermediate page as a mediator component that bridges the user interface and the subscription authorization system. This intermediate page receives subscription requests from the target client, manages the authorization flow, and coordinates communication between the client and wallet system, thereby eliminating the need for multiple page jumps and switches while improving the overall subscription authorization process
Solution Approach 2:
The patent merges multiple discrete steps of the subscription authorization process into a unified flow handled by the intermediate page. Instead of separate operations for initiating subscription, switching to wallet client, and completing authorization, these steps are combined into a single seamless process where the intermediate page manages the entire authorization lifecycle within one interface context
2Productivity
If multiple page jumps and switches are required, then system functionality is maintained, but user experience and conversion rates are negatively affected
Solution Approach 1:
The intermediate page serves as a mediator that consolidates the subscription authorization functionality, eliminating the need for users to navigate between multiple pages and switches. It handles the entire authorization process within a single page context, thereby reducing device complexity from the user's perspective while maintaining all necessary system functionalities through backend coordination
Solution Approach 2:
The intermediate page is designed as a universal component that handles multiple functions within a single interface: it processes subscription requests, manages authorization states, coordinates with the wallet system, and presents results to users. This multi-functional design eliminates the need for separate dedicated pages for each function, reducing overall system complexity
3Reliability
If traditional authorization flow is used, then system servers can process subscriptions, but network disruptions and unstable connections cause process failures
Solution Approach 1:
The intermediate page implements beforehand cushioning by pre-managing the authorization state and maintaining local context before network operations occur. It buffers the authorization process against network disruptions by keeping track of subscription requests and their states locally, allowing the system to resume or recover from interruptions without complete process failure
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments of this specification provide a subscription authorization method, applied to a target client embedded with an SDK provided by a third party. The target client runs in an operating system provided by a serving party. The method includes: in response to a subscription application initiated by a user in the target client, activating, by the SDK, an intermediate page provided by the third party, where the subscription application is used to apply for authorization to bind a first account of the user in a target electronic wallet to a second account of the user in the serving party; initiating, by the intermediate page, a subscription request to a system server corresponding to the serving party by using an intermediate server corresponding to the third party, to obtain a subscription request number; and further, initiating, by the intermediate page to a wallet client of the target electronic wallet, a first request carrying the subscription request number, so that the wallet client initiates a binding request to the system server, and the binding request triggers the system server to interact with the wallet server of the target electronic wallet based on the subscription request number through forwarding by the intermediate server, to complete the binding.