Card Binding Method for Mobile Payment Terminals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile payment systems require users to perform cumbersome operations, such as downloading and re-binding card applications for each bank card when switching terminals, leading to low card binding efficiency, especially for NFC payments.
Innovation Solution
A card binding method that allows users to enter verification information for one bank card to bind multiple bank cards, utilizing a digital wallet server and bank servers to verify and deliver card applications and personalization data, simplifying the binding process by reducing the need for repetitive information input.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If users bind each bank card separately by downloading card applications and inputting information for each card, then each card can be bound securely, but card binding efficiency is low and the process is cumbersome
Solution Approach 1:
The patent merges multiple card binding operations into a single unified process. Instead of requiring separate binding procedures for each bank card, the system allows users to bind multiple cards simultaneously through one verification process, where the verification result is shared across all selected cards, dramatically improving binding efficiency
Solution Approach 2:
The system performs preliminary selection of multiple bank cards before the verification step. Users can pre-select which cards to bind, and then a single verification operation binds all selected cards at once, eliminating the need to repeat verification for each card individually
2Adaptability or versatility
If users re-bind cards after terminal change by downloading and re-inputting all card information, then cards can be bound to the new terminal, but the operation is time-consuming and complex
Solution Approach 1:
The patent implements a copying mechanism where card binding information is synchronized across terminals. When a user binds cards on one terminal, the binding relationship is stored and can be quickly replicated on another terminal through account login, eliminating the need to re-download and re-verify each card
Solution Approach 2:
The binding mechanism is designed to be universal across different terminals. By using account-based storage of binding relationships, the system allows users to bind cards once and access them from any terminal logged into the same account, making the binding process terminal-agnostic
3Reliability
If card applications and personalization data are locally stored in the terminal, then payment can be performed offline, but terminal changes require re-binding all cards
Solution Approach 1:
The patent introduces a server as an intermediary that stores card binding relationships and personalization data. This allows local terminals to have offline payment capability while the server maintains the master binding information, enabling seamless synchronization when terminals change without requiring full re-binding
Data Source
Figure 1
Figure 2A-1
Figure 2A-2
AI summary
Embodiments of this application disclose a card binding method and a terminal, and relate to the field of mobile payment technologies. The present invention is intended to resolve a prior-art problem of relatively low card binding efficiency caused because a user performs a relatively cumbersome operation in a first-time card binding process, or in a card binding process in which a terminal is changed. The card binding method disclosed in the embodiments of this application is applied to a terminal. The method includes: displaying a first screen, where the first screen displays at least two bank cards associated with an account number with which a digital wallet APP is currently logged in to; determining a to-be-verified bank card and at least one to-be-bound bank card from the at least two bank cards; displaying a second screen, where the second screen is used to prompt a user to enter verification information of the to-be-verified bank card; and sending the verification information to a server to request the server to deliver a card application and personalization data corresponding to each to-be-bound bank card to the terminal after verification performed on the verification information succeeds, to complete binding of the at least one to-be-bound bank card.