Joint Payment Graphic Code Generation for Multi-User Scenarios
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current e-commerce systems lack the ability for a user to perform joint payments using a single smart terminal, as they can only display a graphic code for themselves, making it inconvenient for scenarios like subway entry/exit, bus tickets, and scenic spot purchases where multiple users need to be accounted for.
Innovation Solution
A joint payment method and system based on a binding relationship, where a server generates graphic codes for both the initiator and included users if a binding relationship exists, allowing the smart terminal to display these codes for multiple users to facilitate joint payments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a smart terminal displays only the user's own graphic code for payment, then the payment system is simple and secure, but it cannot support joint payment scenarios where one user needs to pay for multiple users
Solution Approach 1:
The graphic code is segmented into multiple independent code blocks, each corresponding to a different user. The terminal device displays multiple separate graphic codes on the same screen, allowing each code to be independently scanned and recognized by the payment system. This segmentation enables one user's terminal to display and facilitate payment for multiple users' accounts simultaneously.
Solution Approach 2:
The smart terminal is enhanced to perform multiple functions: it not only displays the user's own graphic code but also displays graphic codes for other users within the same payment account group. The terminal acts as a universal payment device that can handle both individual payments and joint payments for multiple users, making the payment system more versatile.
2Ease of operation
If the system allows one user to display graphic codes for multiple users, then joint payment convenience is improved, but the risk of unauthorized payment increases
Solution Approach 1:
The payment system implements a confirmation feedback mechanism where the terminal device displays a list of users associated with the payment account before generating their graphic codes. The user must actively select which users to include in the joint payment, and the system provides visual feedback showing which users' codes will be displayed. This feedback loop ensures the user consciously authorizes each payment action.
Solution Approach 2:
The server acts as an intermediary that verifies the binding relationship between the account holder and other users before allowing joint payment. The server mediates the payment process by validating user identities, managing the binding relationships, and ensuring that only authorized users can be included in joint payments. This intermediary layer adds security while maintaining convenience.
3Quantity of substance
If graphic codes for multiple users are displayed on a single terminal, then the number of devices needed is reduced, but the complexity of code management increases
Solution Approach 1:
Multiple graphic codes for different users are merged and displayed together on a single terminal screen. The system combines the payment capabilities of multiple user accounts into one display interface, allowing all necessary graphic codes to be visible and accessible from one device. This merging reduces the need for multiple physical terminals while the system automatically manages the complexity of organizing and displaying the codes.
Data Source
AI summary
One embodiment provides a method and system for joint payment. During operation, a joint-payment server receives a joint-payment request comprising an identifier of a user initiating a joint payment and an identifier of a user to-be-included in the joint payment; determines, based the identifiers of the user initiating the joint payment and the to-be-included user, whether a binding relationship has been established between the user initiating the joint payment and the to-be-included user; in response to determining that the binding relationship has been established, generates graphic codes respectively corresponding to the user initiating the joint payment and the to-be-included user; and sends the graphic codes to a terminal device associated with the user initiating the joint payment, thereby facilitating the terminal device to display the graphic codes to complete the joint payment.