Card linking method, user terminal, server, system and storage medium

Abstract

A card binding method, a user terminal, a server, a system and a storage medium are provided, which relate to the technical field of data processing. The method includes: calling a first application program to scan an information carrier pattern to accept the access of the user terminal to a first page address indicated by the first application program, and obtaining a card number of a target card indicated by the information carrier pattern (S201); obtaining user information of a target user from a background server of the first application program (S202); sending a second page address corresponding to the redirected card binding page to the user terminal (S203), the card binding page including at least a part of the card number of the target card; receiving a card binding confirmation message sent by the card binding page from the user terminal to indicate identity information of the target user (S204); and using the identity information to interact with a card issuing server and a background server of the card binding application program, and completing the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program (S205). The method can improve the efficiency of card binding in application programs.

Description

[Technical field]

[0001] This application claims priority to Chinese patent application No. 202111038223.3, filed on September 6, 2021, entitled "Card binding method, user terminal, server, system and storage medium," the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the technical field of data processing, and in particular to a card binding method, a user terminal, a server, a system, and a storage medium. [Background technology]

[0003] 2. Description of the Related Art With the development of electronic information technology, the scope of application of electronic payment is becoming wider and wider. Users can realize electronic payment by bank cards through operation of application programs on user terminals.

[0004] Before an application program can realize electronic payment using a bank card, the bank card must first be linked to the user account of the application program. However, due to the diversity of application programs, the methods of setting the activation guide for the card binding function in different application programs are different, and it is inconvenient for users to search for the activation guide for the card binding function in the application program, so that users spend a long time searching for the activation guide for the card binding function in the application program, which reduces the efficiency of users using the application program to bind their cards. Summary of the Invention

[0005] The embodiments of the present application provide a card binding method, a user terminal, a server, a system and a storage medium, which can improve the efficiency of card binding in application programs.

[0006] In a first aspect, an embodiment of the present application is a card binding method applied to a card binding server, comprising: accepting an access of a user terminal to a first page address indicated by calling a first application program and scanning an information carrier pattern, and acquiring a card number of a target card indicated by the information carrier pattern; acquiring user information of a target user from a background server of the first application program, the target user being a user who has logged in to the first application program, the user information including a user identifier of the target user in the first application program; and acquiring a card number of a target card indicated by the information carrier pattern from a background server of the first application program, the target user being a user who has logged in to the first application program, the user information including a user identifier of the target user in the first application program; a page address to a user terminal, the card binding page including at least a portion of the card number of the target card; receiving a card binding confirmation message sent by the card binding page from the user terminal, the card binding confirmation message being for indicating identity information of the target user; and using the identity information to interact with a card issuing server and a background server of a card binding application program to complete binding between a card identifier of the target card and a user identifier of the target user in the card binding application program, the card binding application program including a first application program.

[0007] In a second aspect, an embodiment of the present application is a card binding method applied to a user terminal, comprising: invoking a first application program to scan an information carrier pattern, accessing a first page address of a card binding server indicated by the information carrier pattern, and sending a card number of a target card indicated by the information carrier pattern to the card binding server, so as to trigger the card binding server to obtain user information of the target user from a background server of the first application program; the target user is a user who has logged in to the first application program, and the user information includes a user identifier of the target user in the first application program; Provided is a card binding method, the method including: receiving a second page address sent by a card binding server, accessing the second page address, and displaying a card binding page corresponding to the second page address, the card binding page including at least a part of a card number of a target card; and in response to a user's input on the card binding page, sending a card binding confirmation message to the card binding server for indicating identity information of the target user, such that the card binding server utilizes the identity information to interact with a card issuing server and a background server of a card binding application program to complete binding between a card identifier of the target card and a user identifier of the target user in the card binding application program, the card binding application program including a first application program.

[0008] In a third aspect, an embodiment of the present application provides a card binding method applied to a background server of an application program, the method including: when the application program is a first application program, and the card binding server accepts access from a user terminal to a first page address indicated by calling the first application program and scanning an information carrier pattern, sending user information of a target user to the card binding server, the target user being a user who has logged in to the first application program, and the user information including a user identifier of the target user in the first application program; and when the card binding server receives a card binding confirmation message, interacting with the card binding server to complete binding between the card identifier of the target card and the user identifier of the target user in the first application program, the card binding confirmation message being sent from the user terminal in response to an input by the user to a card binding page, for indicating identity information of the target user, the card binding page including at least a portion of the card number of the target card, and the card binding application program including the first application program.

[0009] In a fourth aspect, an embodiment of the present application is a server including an interaction module, the interaction module including a receiving unit and a sending unit, the interaction module is used to call a first application program and scan an information carrier pattern to accept an access of a user terminal to a first page address indicated by the information carrier pattern, and obtain a card number of a target card indicated by the information carrier pattern, and is used to obtain user information of a target user from a background server of the first application program, the target user being a user who has logged in to the first application program, and the user information includes a user identifier of the target user in the first application program; the sending unit is used to send a redirected card binding page to the first application program. a card binding application program including a first application program and a second application program, the ... being used for receiving a card binding confirmation message sent by the card binding page from the user terminal, the card binding confirmation message being used for indicating identity information of the target user

[0010] In a fifth aspect, an embodiment of the present application is a user terminal including a scanning module, an interaction module, and a display module, wherein the interaction module includes a sending unit, the scanning module is used to scan an information carrier pattern when a first application program is invoked, the interaction module is used to scan the information carrier pattern to access a first page address of an indicated card binding server, and send a card number of a target card indicated by the information carrier pattern to the card binding server, so as to trigger the card binding server to obtain user information of the target user from a background server of the first application program, the target user is a user who has logged in to the first application program, and the user information includes a user identifier of the target user in the first application program, and the interaction module is used to send the ... the display module is used for receiving a second page address transmitted via the card issuing server and accessing the second page address, the display module is used for displaying a card binding page corresponding to the second page address, the card binding page including at least a portion of a card number of the target card, the sending unit is further used for sending a card binding confirmation message to the card binding server in response to the user's input of the card binding page, such that the card binding server utilizes the identity information to interact with the card issuing server and the background server of the card binding application program to complete binding between the card identifier of the target card and the user identifier of the target user in the card binding application program, the card binding confirmation message is for indicating the identity information of the target user, and the card binding application program includes a first application program.

[0011] In a sixth aspect, an embodiment of the present application provides a server including an interaction module, the interaction module including a sending unit, the sending unit sending user information of a target user to the card binding server when the application program is a first application program, the target user is a user who accessed the first application program, and the user information includes a user identifier of the target user in the first application program, when the card binding server accepts access from the user terminal to a first page address indicated by calling the first application program and scanning the information carrier pattern, the target user is a user who accessed the first application program, and the user information includes a user identifier of the target user in the first application program, the interaction module interacting with the card binding server when the card binding server receives a card binding confirmation message, and completing binding between the card identifier of the target card and the user identifier of the target user in the first application program, the card binding confirmation message being sent from the user terminal in response to an input by the user to the card binding page, for indicating identity information of the target user, the card binding page including at least a portion of the card number of the target card, and the card binding application program including the first application program.

[0012] In a seventh aspect, an embodiment of the present application provides a server including a processor and a memory storing computer program commands, the server realizing the card linking method of the first aspect when the processor executes the computer program commands.

[0013] In an eighth aspect, an embodiment of the present application provides a user terminal including a processor and a memory storing computer program commands, the user terminal realizing the card linking method of the second aspect when the processor executes the computer program commands.

[0014] In a ninth aspect, an embodiment of the present application provides a server including a processor and a memory storing computer program commands, the server realizing the card binding method of the third aspect when the processor executes the computer program commands.

[0015] In a tenth aspect, an embodiment of the present application provides a card binding system including the server of the seventh aspect, the user terminal of the eighth aspect, and the server of the ninth aspect.

[0016] In an eleventh aspect, an embodiment of the present application provides a computer readable storage medium having stored thereon computer program commands which, when executed by a processor, realise the card linking method of the first aspect, the card linking method of the second aspect or the card linking method of the third aspect.

[0017] The embodiments of the present application provide a card binding method, a user terminal, a server, a system, and a storage medium, in which the user terminal calls a first application program to scan an information carrier pattern, triggers access to a first page address of the card binding server indicated by the access information carrier pattern, and sends the card number of the target card indicated by the scanning of the information carrier pattern to the card binding server, so as to trigger the card binding server to obtain user information of the target user who has logged into the first application program from the background server of the first application program. The user terminal receives and accesses a second page address corresponding to the card binding page, and displays the card binding page. The user terminal sends the user confirmed identity information to the card binding server through the card binding confirmation information, so that the card binding server completes the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program through interaction with the card issuing server and interaction with the background server of the card binding application program. A user does not need to search for a card linking function start guide in an application program, but can directly use a scan function of a user terminal, and by jumping to a card linking page to link the card, the time required for the user to link the card is reduced, and the efficiency of the user linking the card by utilizing the application program is improved. [Brief description of the drawings]

[0018] In order to more clearly explain the technical solutions of the embodiments of the present application, the following briefly introduces drawings necessary for the embodiments of the present application. Those skilled in the art can further derive other drawings based on these drawings even without creative labor. [Figure 1] FIG. 1 is a schematic diagram illustrating an example of a scene in which a card linking method according to an embodiment of the present application is applied. [Diagram 2]1 is a flowchart of an embodiment of a card binding method according to a first aspect of the present application. [Diagram 3] FIG. 13 is a schematic diagram of an example of a card linking page displayed on a user terminal according to an embodiment of the present application. [Figure 4] 4 is a flowchart of another embodiment of a card binding method according to the first aspect of the present application. [Diagram 5] FIG. 13 is a schematic diagram of another example of a card linking page displayed on a user terminal in accordance with an embodiment of the present application. [Figure 6] FIG. 13 is a schematic diagram of another example of a card linking page displayed on a user terminal according to an embodiment of the present application. [Figure 7] FIG. 13 is a schematic diagram of a further example of a card binding page displayed on a user terminal in accordance with an embodiment of the present application. [Figure 8] 4 is a flowchart of another embodiment of a card binding method according to the first aspect of the present application. [Figure 9] 4 is a flowchart of a further embodiment of a card binding method according to the first aspect of the present application. [Figure 10] 4 is a flowchart of an embodiment of a card binding method according to a second aspect of the present application. [Figure 11] 4 is a flowchart of another embodiment of a card binding method according to the second aspect of the present application. [Figure 12] 11 is a flowchart of an embodiment of a card binding method according to a third aspect of the present application. [Figure 13] 11 is a flowchart of another embodiment of a card binding method according to the third aspect of the present application. [Figure 14] 11 is a flowchart of another embodiment of a card binding method according to the third aspect of the present application. [Figure 15] 4 is a flowchart of a further embodiment of a card linking method according to the third aspect of the present application. [Figure 16] 1 is a flowchart of an example of a card binding process, according to an embodiment of the present application. [Figure 17]FIG. 11 is a structural schematic diagram of an embodiment of a server according to the fourth aspect of the present application. [Figure 18] FIG. 11 is a structural schematic diagram of another embodiment of a server according to the fourth aspect of the present application; [Figure 19] FIG. 11 is a structural schematic diagram of another embodiment of a server according to the fourth aspect of the present application. [Figure 20] FIG. 11 is a structural schematic diagram of a further embodiment of a server according to the fourth aspect of the present application; [Figure 21] FIG. 11 is a structural schematic diagram of an embodiment of a user terminal according to the fifth aspect of the present application; [Figure 22] FIG. 11 is a structural schematic diagram of an embodiment of a server according to the sixth aspect of the present application. [Diagram 23] FIG. 11 is a structural schematic diagram of another embodiment of a server according to the sixth aspect of the present application; [Figure 24] FIG. 11 is a structural schematic diagram of another embodiment of a server according to the sixth aspect of the present application. [Diagram 25] FIG. 13 is a structural schematic diagram of an embodiment of a server according to the seventh aspect of the present application. [Figure 26] FIG. 13 is a structural schematic diagram of an embodiment of a user terminal according to the eighth aspect of the present application. [Figure 27] FIG. 13 is a structural schematic diagram of an embodiment of a server according to the ninth aspect of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] The following describes in detail the characteristics and exemplary embodiments of each aspect of the present application, and in order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described in more detail below in conjunction with drawings and specific examples. It should be understood that the specific examples described herein are provided only to illustrate the present application, and do not limit the present application. Those skilled in the art can implement the present application without the need for some of these specific details. The following description of the embodiments is intended to provide an example of the present application so as to better understand the present application.

[0020] With the continuous development of electronic information technology, the application scope of electronic payment is becoming wider and wider. A user can realize electronic payment by bank card by operating an application program (Application, APP) on a user terminal. Before realizing electronic payment by bank card by application program, a bank card needs to be linked with a user account of the application program first, and when logging in to the user account to use the application program, a payment can be made by using the bank card linked with the user account in the application program. However, it is difficult for a user to find the activation guide of the linking function in the application program, and the settings of the activation guide of the card linking function in different application programs are different, so that a user spends a long time searching for the activation guide of the card linking function in the application program, which reduces the efficiency of a user using the application program to link a card.

[0021] The embodiments of the present application provide a card linking method, a user terminal, a server, a system, and a storage medium, which allow a user to directly use the scan function of the user terminal to jump to the card linking page to link the card without needing to search for the activation guide of the card linking function in the application program, thereby reducing the time required for the user to link the card and improving the efficiency of the user to link the card using the application program.

[0022] The card linking method in the embodiment of the present application relates to a user terminal, a background server of each application program, a card linking server, and a card issuing server. FIG. 1 is a schematic diagram of an example of an application scene of the card linking method in the embodiment of the present application. As shown in FIG. 1, the user terminal 11 may perform communication interaction with the background server 12 of each application program, the user terminal 11 may perform communication interaction with the card linking server 13, the card linking server 13 may perform communication interaction with the background server 12 of each application program, and the card linking server 13 may perform communication interaction with the card issuing server 14. In FIG. 1, in order to distinguish the background servers of different programs, the background servers corresponding to different programs are indicated by different symbols, and the background server 121 is the background server of the application program A1, the background server 122 is the background server of the application program A2, and the background server 123 is the background server of the application program A3.

[0023] The user terminal 11 can perform man-machine interaction with a user. The user terminal 11 can install two or more application programs. Specifically, the user terminal 11 may include terminal devices such as a mobile phone and a tablet computer, and is not limited here.

[0024] The background server 12 is a background server of an application program. The background servers of different application programs may be different background servers or the same background server, and are not limited here. The background server 12 interacts with the user terminal 11, provides necessary information to the corresponding application program in the user terminal 11, and can receive commands sent by the corresponding application program through the user terminal 11.

[0025] The card binding server 13 can provide a card binding function. In the embodiment of the present application, the card binding server 13 can interact with the user terminal 11, provide a card binding page to the user terminal so that the user further operates the card binding through the user terminal, and can also obtain information fed back by the user terminal 11. The card binding server 13 can interact with the background server 12 of the application program, and obtain information required for card binding from the background server 12 of the application program.

[0026] The card issuing server 14 is a server of the card issuing institution, and records information on the bank card and the user who is the card owner, etc. The card issuing server 14 can interact with the card binding server 13 to perform identity authentication for the bank card and user corresponding to the information provided to the card binding server.

[0027] Hereinafter, a card binding method, a user terminal, a server, a system, and a storage medium according to an embodiment of the present application will be described.

[0028] A first aspect of the present application provides a card linking method applied to a card linking server, i.e., the card linking method can be executed by the card linking server. Figure 2 is a flowchart of an embodiment of the card linking method according to the first aspect of the present application. As shown in Figure 2, the card linking method can include steps S201 to S205.

[0029] In step S201, a first application program is called and an information carrier pattern is scanned to accept access from a user terminal to a first page address indicated by the information carrier pattern, and the card number of a target card indicated by the information carrier pattern is obtained.

[0030] The information carrier pattern can be a carrier of the first page address and the card number of the target card. When a user logs in and enters a first application program of the user terminal, the user terminal can call the first application program to scan the information carrier pattern, thereby obtaining the first page address and the card number of the target card.

[0031] In the embodiments of the present application, the form of the information carrier pattern is not limited. In some examples, the information carrier pattern can include a two-dimensional code. The information recorded in the two-dimensional code can include a first page address and a card number of the target card. That is, the user terminal can read the first page address and the card number of the target card by calling the first application program and scanning the two-dimensional code. The user terminal can jump to the first page address to access the first page address and send the card number of the target card to the card binding server. Correspondingly, the card binding server accepts the user terminal's access to the first page address and receives the card number of the target card sent by the user terminal.

[0032] In some other examples, the information carrier pattern can include a two-dimensional code. The information recorded in the two-dimensional code can include a first page address and the encrypted card number of the target card. Specifically, the encrypted card number of the target card is the card number of the target card encrypted using the first key in the above-mentioned embodiment. The user terminal can jump to the first page address to access the first page address, and send the encrypted card number of the target card to the card binding server. In response, the card binding server accepts the user terminal's access to the first page address and receives the encrypted card number of the target card.

[0033] Specifically, the two-dimensional code in the above example may be printed on the surface of a card using a card as a carrier, may be printed on paper using paper as a carrier, or may be displayed as an electronic two-dimensional code, and is not limited here. The two-dimensional code may be generated according to a standard by the owner of the card issuing server and provided to the card owner. The two-dimensional code may be generated according to a standard by the owner of the card binding server and provided to the card owner via an interface.

[0034] In some other examples, the information carrier pattern can include a card face pattern of the target card. The card face pattern includes a page jump identifier and a card number of the target card. The page jump identifier may be a specific pattern, and is not limited here. The user terminal can store a first page address corresponding to the page jump identifier, and when the user terminal invokes a first application program and scans the page jump identifier, an access to the first page address is triggered. The user terminal can directly send the card number of the target card to the card binding server, that is, the card binding server obtains the card number of the target card from the user terminal. The user terminal can encrypt the card number of the target card with a first key and send the encrypted card number of the target card to the card binding server, that is, the card binding server obtains the encrypted card number of the target card from the user terminal.

[0035] Since the information carrier pattern is the bearer of the first page address and the card number of the target card, the user terminal can directly access the first page address by calling the first application program and scanning the carrier pattern, thereby starting the card binding operation, and the user does not need to search for the activation guide of the card binding service in the first application program, which further reduces the operations required by the user in the card binding process.

[0036] The first page address is one page address of the card's binding server. The first page address may be the same page address for different users, different application programs, and different user terminals. For example, the same user can log in to a plurality of different application programs in the same user terminal, and access the first page address by jumping to the same page address by the different application programs in the user terminal. Also, for example, different users can log in to the same application program in different user terminals, and access the first page address by jumping to the same page address by the application programs in the different user terminals. Also, for example, different users can log in to different application programs in different user terminals, and access the first page address by jumping to the same page address by the different application programs in the different user terminals.

[0037] Here, the execution timing relationship between the access of the user terminal to the first page address and the transmission of the card number of the target card to the card linking server is not limited, that is, the execution timing relationship between the card linking server accepting the access of the user terminal to the first page address and obtaining the card number of the target card from the user terminal is not limited. In some examples, the user terminal can access the first page address and can transmit the card number of the target card to the card linking server together so that the card linking server obtains the card number of the target card from the user terminal. In some other examples, the access of the user terminal to the first page address and the transmission of the card number of the target card to the card linking server can be performed in a sequential order.

[0038] The target card may be a linked card. The target card may include, but is not limited to, a card that can be used for payment, such as a bank card, a membership card, etc.

[0039] In some examples, the card binding server obtains the encrypted card number of the target card from the user terminal. Correspondingly, the card binding server can decrypt the encrypted card number of the target card to obtain the card number of the target card. Specifically, the card binding server receives the card number of the target card encrypted by the first key sent from the user terminal. The card binding server decrypts the encrypted card number of the target card using a second key paired with the first key stored in advance to obtain the card number of the target card. The first key and the second key may be symmetric keys, i.e., the first key and the second key are the same. The first key and the second key may be asymmetric keys, i.e., the first key and the second key are different. Here, the specific types of the first key and the second key are not limited.

[0040] By encrypting and transmitting the card number of the target card, the risk of the card number of the target card being leaked is reduced and the security of the card number of the target card is guaranteed, thereby improving the security of the card linking process.

[0041] In step S202, user information of the target user is obtained from the background server of the first application program.

[0042] The card-linking server acquires user information of the target user from a background server of the first application program in response to the user terminal's access to the first page address. The user terminal jumps to the first page address by the first application program and accesses the first page address, and the card-linking server can identify the application program accessing the first page address and the user logged in to the application program. The target user is the user logged in to the first application program.

[0043] Specifically, the card binding server can send a user information request message to the background server of the first application program in response to the user terminal's access to the first page address. The user information request message is used to request user information of the target user from the background server of the first application program. In response to the user information request message, the background server of the first application program feeds back the user information of the target user to the card binding server. In some examples, the user information request message may include a temporary identifier of the target user, and the background server of the first application program may identify the target user based on the temporary identifier.

[0044] The user information includes a user identifier of the target user in the first application program. The user identifier of the target user in the first application program is used to identify the target user in the first application program. The user identifier may be a user registration account, a user registration number, a user registration name, etc., and is not limited here. The user identifiers of the same target user in different application programs may be the same or different, and is not limited here.

[0045] The user information may further include other information, and is not limited thereto. In some examples, the user information may further include identity information. The identity information of the target user is information that can reveal the personal identity of the target user. For example, the identity information may include, but is not limited to, one or more of the following information: name, certificate number, mobile phone number, email address, etc.

[0046] In some examples, the card binding server may first authenticate the first application program and determine whether to obtain user information of the target user from the background server of the first application program. Specifically, after accepting the user terminal's access to the first page address by the first application program and obtaining the card number of the target card from the user terminal, the card binding server first determines whether the first application program is an application program supported by the card binding server. If the first application program is an application program supported by the card binding server, the card binding server obtains user information of the target user from the background server of the first application program. If the first application program is not an application program supported by the card binding server, the card binding server does not obtain user information of the target user from the background server of the first application program. The application programs supported by the card binding server are application programs in a whitelist, and by determining in advance whether the first application program is supported by the binding server, it is possible to avoid binding the card to an unauthorized application program or an application program that does not comply with the requirements, thereby ensuring the safety and reliability of the card binding.

[0047] In step S203, a second page address corresponding to the redirected card binding page is sent to the user terminal.

[0048] When the card binding server obtains the user information of the target user, the card binding server may redirect the page address accessed by the user terminal. The card binding server sends a second page address corresponding to the card binding page to the user terminal, so that the user terminal accesses the second page address to display the card binding page. The resource information included in the card binding page is provided by the card binding server.

[0049] In some examples, the card binding page includes at least a portion of the card number of the target card. The card number of the target card is the card number of the target card obtained in step S201. The card binding page may include the complete card number of the target card, or may include a card number with some symbols of the target card hidden, and is not limited here. For example, the card binding page may include a card number with the middle four digits of symbols hidden.

[0050] The card binding page includes at least a portion of the card number of the target card, and the card number of the target card does not need to be manually entered by the user, avoiding possible errors in manually entering the card number and reducing the user's operations in the card binding process, thereby improving the success rate of card binding and simplifying the card binding procedure.

[0051] For example, Fig. 3 is a schematic diagram of an example of a card linking page displayed on a user terminal according to an embodiment of the present application. As shown in Fig. 3, the card linking page includes a card number of the target card, 6259****0101, with the middle four digits of the symbol hidden.

[0052] In step S204, a card linking confirmation message transmitted based on the card linking page is received from the user terminal.

[0053] The card binding confirmation message is sent by the user terminal in response to the user's input into the card binding page and is identity information to indicate the target user.

[0054] If the user information obtained by the card linking server from the background server of the first application program does not include identity information of the target user, the user terminal can obtain identity information of the target user through user input on the card linking page of the user terminal, and send the identity information of the target user to the card linking server via a card linking confirmation message.

[0055] If the user information obtained by the card binding server from the background server of the first application program includes identity information of the target user, the card binding page may include the identity information, and correspondingly, the card binding confirmation message includes identity verification information, which indicates that the identity information included in the card binding page is correct.

[0056] In step S205, the identity information is used to interact with the card issuing server and the background server of the card binding application program to complete binding between the card identifier of the target card and the user identifier of the target user in the card binding application program.

[0057] The card binding server interacts with the card issuing server to authenticate identity information of the target card and the target user. The card binding server interacts with a background server of the card binding application program to provide a card identifier of the target card to the background server of the card binding application program, and realizes binding between the card identifier of the target card and the user identifier of the target user in the card binding application program. The card binding application program includes a first application program.

[0058] The card identifier of the target card may be assigned by the card binding server. In some examples, the card identifier may include a card number and / or a card payment identifier token (Token). When the card identifier includes a card payment identifier token, different application programs corresponding to the same card have different card payment identifier tokens. The card payment identifier token is an alternative value of the card number of the card, and is composed of, but is not limited to, 13 to 19 digits. By performing card binding using the card payment identifier token, the security of card binding can be further improved.

[0059] In an embodiment of the present application, the card binding server accepts the user terminal's access to the first page address indicated by calling the first application program and scanning the information carrier pattern, and obtains the card number of the target card indicated by the information carrier pattern. The first page address is provided by the card binding server in bulk. The card binding server obtains user information of the target user who logged into the first application program from the background server of the first application program. The user terminal's access to the first page address triggers the card binding server to send a second page address corresponding to the redirected card binding page to the user terminal, so that the user terminal accesses the second page address to display the card binding page. The card binding server determines the identity information of the target user through the card binding confirmation message sent from the user terminal based on the card binding page, and thus can complete the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program through interaction with the card issuing server and interaction with the background server of the card binding application program. The user does not need to search for a card linking function start guide in an application program, but can call up a first application program, scan an information carrier pattern, jump to a card linking page and link the card, thereby reducing the time required for the user to link the card and improving the efficiency of the user linking the card by utilizing the application program.

[0060] Next, a specific process of linking the card identifier of the target card with the user identifier of the target user in the first application program will be described. Fig. 4 is a flowchart of another embodiment of the card linking method according to the first aspect of the present application. Fig. 4 differs from Fig. 2 in that step S205 in Fig. 2 is specifically divided into steps S2051 to S2053 in Fig. 6.

[0061] In step S2051, a card binding validation message is sent to the card issuing server so that the card issuing server uses the identity information to perform validation verification of the card binding.

[0062] The card linking activation message includes the card number and identity information of the target card. The card linking activation verification is a verification of whether the card number of the target card matches the identity information of the target user. The card issuing server stores the correspondence between the card number of the card and the identity information of the card's cardholder. If the identity information of the target user matches the identity information of the cardholder of the target card stored in the card issuing server, the target user is identified as the cardholder of the target card, that is, the card number of the target card matches the identity information of the target user, and the card linking activation verification is successful. If the identity information of the target user does not match the identity information of the cardholder of the target card stored in the card issuing server, the target user is identified as not the cardholder of the target card, that is, the card number of the target card does not match the identity information of the target user, and the card linking activation verification fails. The card linking activation verification can identify whether the target user is the cardholder of the target card, thereby ensuring the security of the card linking.

[0063] In step S2052, the result information of the validation verification of the card association transmitted from the card issuing server is received.

[0064] The result information of the validation verification of the card binding is used to indicate whether the validation verification of the card binding has been successful or not.

[0065] In step S2053, if the result information of the card linking activation verification indicates that the card linking activation verification is successful, a first card linking notification message is sent to the background server of the first application program so that the background server of the first application program completes linking between the card identifier of the target card and the user identifier of the target user in the first application program.

[0066] The first card binding notification message includes result information of the validation verification of the card binding and the card identifier of the target card. When the validation verification of the card binding is successful, the card binding server allows the background server of the first application program to bind the target card, i.e., allows the card identifier of the target card to be bound to the user identifier of the target user in the first application program.

[0067] If the result information of the card binding validation verification indicates that the card binding validation verification has failed, the card binding server can send a card binding failure notification message to the background server of the first application program, and the card binding failure notification message can include the result information of the card binding validation verification. If the result information of the card binding validation verification indicates that the card binding validation verification has failed, the card binding server does not send the card identifier of the target card to the background server of the first application program, i.e., does not allow the target card to be bound by the background server of the first application program.

[0068] In some examples, the card binding page further includes an option of an application program supported by the card binding server. Correspondingly, the card binding confirmation message is also used to indicate the selected card binding application program. The option of the application program supported by the card binding server can be selected by the user to select the application program that requires card binding. For example, FIG. 5 is a schematic diagram of another example of a card binding page displayed on a user terminal according to an embodiment of the present application. As shown in FIG. 5, the card binding page includes a card number of a target card and an option of an application program, where the card number of the target card is 6259****0101, and the option of the application program includes four options that can be selected by the user: "bound to A1 application program", "bound to A2 application program", "bound to A3 application program", and "bound to A4 application program".

[0069] In some other examples, the card binding page may further include an identity information entry area, which is advantageous for requiring the user to manually enter identity information and then using the identity information to authenticate the identity of the target user. For example, FIG. 6 is a schematic diagram of another example of a card binding page displayed on a user terminal according to an embodiment of the present application. Compared with FIG. 5, FIG. 6 adds an identity information entry area P1 to the card binding page. As shown in FIG. 6, the identity information entry area may include a real name entry area P11, a certificate type entry area P12, a certificate number entry area P13, and a mobile phone number entry area P14.

[0070] In some other examples, when the user information further includes identity information, the card binding page can further include identity information. For example, Fig. 7 is a schematic diagram of a further example of a card binding page displayed on a user terminal according to an embodiment of the present application. Compared with Fig. 5, Fig. 7 adds identity information to the card binding page, and the identity information includes name, certificate type, certificate number and mobile phone number.

[0071] The card binding page further includes identity information, which eliminates the need for the user to manually input the identity information and can use the identity information to authenticate the target user, avoiding possible errors caused by manually inputting the identity information and reducing the user's operations during the card binding process, thereby improving the success rate of card binding and simplifying the card binding procedure.

[0072] In the above embodiment, the card-binding confirmation message may include information that can indicate the identifier of the card-binding application program or other card-binding application programs, and is not limited thereto.

[0073] If the card binding page further includes an option of application programs supported by the card binding server, and the card binding confirmation message is further used to indicate the selected card binding application program, the card binding application program includes the application program selected by the user from the option of application programs supported by the card binding server. Specifically, the card binding application program can include a first application program and a second application program. The second application program is different from the first application program, that is, the second application program includes at least one application program other than the first application program among the application programs supported by the card binding server. The second application program may include one application program, or may include two or more application programs, where the number of the second application programs is not limited. For example, the card binding page after the user operation is as shown in FIG. 7, and if the first application program is an A1 application program, the second application program includes an A2 application program and an A4 application program.

[0074] A specific card linking process between the card identifier of the target card and the user identifier of the target user in the second application program will be described below. Figure 8 is a flowchart of another embodiment of the card linking method according to the first aspect of the present application. Figure 8 differs from Figure 4 in that step S205 in Figure 2 is further divided into steps S2054 to S2056 in Figure 8.

[0075] In step S2054, a card binding matching message is sent to the background server of the second application program, so that the background server of the second application program searches for a user identifier matching the identity information.

[0076] The card-binding matching message includes identity information. The background server of the second application program stores a correspondence relationship between a user identifier in the second application program of the user and the identity information. The background server of the second application program acquires the identity information of the target user from the card-binding matching message, matches the identity information in the card-binding matching message with the identity information of the user stored in the background server of the second application program, and identifies a user identifier corresponding to the identity information that matches the identity information in the card-binding matching message as a user identifier that matches the identity information in the card-binding matching message.

[0077] In step S2055, if a user identifier matching the identity information is found, card binding request information transmitted from the background server of the second application program is received.

[0078] The background server of the second application program searches for a user identifier matching the identity information, which indicates that the target user has registered with the second application program, i.e., the target user is included in the registered users of the second application program. The background server of the second application program can send a card binding request message to the target card binding server to request the card identifier of the target card.

[0079] If the background server of the second application program is unable to search for a user identifier that matches the identity information, this indicates that the target user is not registered in the second application program, i.e., the target user is not included in the registered users of the second application program, and no linking is performed in the second application program for the target card.

[0080] In some examples, the card binding matching message has a validity period. Within the validity period, the card binding matching message is valid. When the validity period is exceeded, the card binding matching message expires. That is, if the card binding server does not receive a card binding request message sent from the background server of the second application program within the validity period, the card binding process for the second application program is terminated.

[0081] In step S2056, a notification message of the binding of the second card is sent to the background server of the second application program so that the background server of the second application program completes the binding between the card identifier of the target card and the user identifier of the target user in the second application program.

[0082] The second card binding notification message includes a card identifier of the target card. The user identifier of the target user in the second application program is a user identifier matching the identity information. The background server of the second application program can receive the second card binding notification message and complete the binding between the card identifier of the target card and the user identifier of the target user in the second application program.

[0083] In some examples, in step S2055, before receiving the card binding request message sent from the background server of the second application program, the background server of the second application program may push a confirmation request message to a user corresponding to the searched user identifier matching the identity information. The confirmation request message is used to prompt the user to specify whether to bind the card, and the format of the confirmation request message is not limited here. When the background server of the second application program receives a message specifying the card binding fed back from the user by the user terminal, it sends a card binding request message to the card binding server. That is, when the user identifier matching the identity information is searched and the background server of the second application program receives a message specifying the card binding fed back from the user by the user terminal, the card binding server receives the card binding request message sent from the background server of the second application program. The safety of the card binding is more guaranteed by the reconfirmation of the user.

[0084] When the card-bound application program includes multiple second application programs, the card-bound server can execute the above steps S2054 to S2056 for the background server of each second application program.

[0085] Steps S2051 to S2053 may be executed before or after steps S2054 to S2056, or steps S2051 to S2053 may be executed synchronously with steps S2054 to S2056. In the embodiments of the present application, the execution timing of steps S2051 to S2053 and steps S2054 to S2056 is not limited.

[0086] The card binding application program includes a first application program and a second application program. Using the identity information, the card issuing server and the background server of the card binding application program can interact with each other to complete the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program, and the card binding operations of the multiple application programs can be started at once, without the need to go to and access each application program to start the card binding operation, simplifying the card binding process in the card binding sheet of the multiple application programs. In addition, the card binding operations of the multiple application programs can be started at once, and the interrelationship between the multiple application programs linked to the same card can also be strengthened, making it easier for the user to manage.

[0087] In some embodiments, to further ensure the security of card binding, a further secure authentication can be performed between the card binding server and the user terminal by a dynamic authentication code. Figure 9 is a flowchart of a further embodiment of a card binding method according to the first aspect of the present application. The difference between Figure 9 and Figure 2 is that the card binding method shown in Figure 9 may further include steps S206 to S208, and step S205 in Figure 2 can be specifically divided into step S2057 in Figure 9.

[0088] In step S206, a dynamic authentication code request message sent from the user terminal is received.

[0089] In some examples, the user terminal can send a dynamic authentication code request message to the card binding server in response to a user input. The dynamic authentication code request message is used to request a dynamic authentication code from the card binding server.

[0090] In step S207, send a first dynamic authentication code to the user terminal.

[0091] The first dynamic authentication code is a dynamic authentication code sent by the card binding server to the user terminal. For example, the card binding server can obtain the mobile phone number of the target user from the identity information of the target user, and send the first dynamic authentication code to the user terminal of the target user via a short message.

[0092] In step S208, a second dynamic authentication code sent from the user terminal is received.

[0093] The second dynamic authentication code is a dynamic authentication code input by a user and received by the user terminal, and the first dynamic authentication code may be the same as or different from the second dynamic authentication code.

[0094] In step S2057, if the first dynamic authentication code and the second dynamic authentication code match, use the identity information to interact with the card issuing server and the background server of the card binding application program, and complete the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program.

[0095] The card binding server uses the first dynamic authentication code and the second dynamic authentication code to authenticate the dynamic authentication code. If the first dynamic authentication code matches the second dynamic authentication code, indicating that the authentication of the dynamic authentication code is passed, the card identifier of the target card can be bound to the user identifier of the target user in the card binding application program. If the first dynamic authentication code and the second dynamic authentication code do not match, the card binding process is stopped.

[0096] The card binding process continues only when the dynamic authentication code passes authentication, thereby preventing card binding by unauthorized users and further improving the security of card binding.

[0097] In some embodiments, after the card identifier of the target card is bound to the user identifier of the target user in the card binding application program, the card binding server can send a third page address corresponding to the redirected card binding result page to the user terminal, and the card binding server can accept the user terminal's access to the third page address.

[0098] The card binding result page is used to indicate that binding between the card identifier of the target card and the user identifier of the target user in the card binding application program is complete. The user terminal accesses the third page address and displays the card binding result page to indicate to the user that the card binding was successful.

[0099] In some embodiments, if linking of the card identifier of the target card with the user identifier of the target user in the card linking application program is not allowed, i.e., if card linking fails, the card linking server sends a page address corresponding to the redirected card linking failure presentation page to the user terminal, and displays the card linking failure presentation page to the user via the user terminal, informing the user of the card linking failure.

[0100] In some embodiments, the card binding server may provide a card binding management page to the user terminal, so that the user manages the binding relationship of the target card. Specifically, the card binding server can accept the access of the user terminal to a fourth page address corresponding to the card binding management page. The card binding management page includes a binding relationship between the card identifier of the target card and the user identifier of the target user in the card binding application program. The card binding server receives a management operation command of the user terminal, and performs a management operation on the binding relationship indicated by the management operation command.

[0101] The management operation may include one or more of the following: a deactivate operation, an activate operation, and a set payment limit operation. The management operation may further include other types of operations, and is not limited thereto.

[0102] The deactivation operation is an operation for deactivating a linking relationship between a card identifier of a target card and a user identifier of a target user in one or more application programs. A deactivation operation is executed for a certain linking relationship, that is, a payment using the target card is deactivated in the application program corresponding to the linking relationship.

[0103] The activation operation is an operation for validating a link between the card identifier of a target card and the user identifier of a target user in one or more application programs. An activation operation is performed for a certain link, that is, the activation operation is performed to validate payment using the target card in the application program corresponding to the link.

[0104] The payment limit setting operation is an operation for setting a payment limit for a linking relationship between the card identifier of a target card and the user identifier of a target user in one or more application programs. The payment limit setting operation is executed for a certain linking relationship, that is, the payment limit of the target card is set in the application program corresponding to the linking relationship.

[0105] In addition, the first page address, the second page address, the third page address and the fourth page address in the above embodiment may specifically include Uniform Resource Locator (URL) addresses, but are not limited thereto.

[0106] A second aspect of the present application provides a card linking method applied to a user terminal, i.e., the card linking method can be executed by a user terminal. Figure 10 is a flowchart of an embodiment of the card linking method according to the second aspect of the present application. As shown in Figure 10, the card linking method can include steps S301 to S303.

[0107] In step S301, a first application program is called to scan an information carrier pattern, so as to trigger the card linking server to obtain user information of the target user from the background server of the first application program, and a first page address of the card linking server indicated by the information carrier pattern is accessed, and the card number of the target card indicated by the information carrier pattern is sent to the card linking server.

[0108] The user terminal can call the first application program to scan the information carrier pattern, which jumps to a browser to access a first page address of the card binding server. The user terminal's access to the first page address can trigger the card binding server to obtain user information of the target user from a background server of the first application program. The target user is a user who has logged in to the first application program. The user information includes a user identifier of the target user in the first application program.

[0109] The user terminal can transmit the unencrypted card number of the target card to the card binding server. The user terminal may transmit the encrypted card number of the target card to the card binding server, i.e., transmit the card number of the target card encrypted by the first key to the card binding server. The card binding server stores a second key paired with the first key, and the card binding server can use the second key to decrypt the encrypted card number of the target card. In some examples, what the user terminal obtains may be the encrypted card number of the target card. In some other examples, what the user terminal obtains may be the unencrypted card number of the target card. The user terminal can encrypt the card number of the target card using the first key to obtain the encrypted card number of the target card.

[0110] In some examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes the first page address and the card number of the target card.

[0111] In some other examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes the first page address and the encrypted card number of the target card.

[0112] In some other examples, the information carrier pattern includes a card face pattern of the target card, the card face pattern includes a page jump identifier and a card number of the target card, and the page jump identifier has a corresponding relationship with the first page address.

[0113] In step S302, the second page address transmitted by the card-linking server is received, the second page address is accessed, and the card-linking page corresponding to the second page address is displayed.

[0114] The card binding page includes at least a portion of the target card's card number.

[0115] In some examples, the card binding page further includes options for application programs supported by the card binding server.

[0116] In some alternative examples, the card's binding page may further include an area for writing identity information.

[0117] In some other examples, the user information may further include identity information, and correspondingly, the card's binding page may further include identity information.

[0118] In step S303, in response to the user's input on the card binding page, the card binding server uses the identity information to interact with the card issuing server and the background server of the card binding application program to complete the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program, and sends a card binding confirmation message to the card binding server.

[0119] The card binding confirmation message indicates identity information of the target user. The card binding application program includes a first application program.

[0120] In some examples, if the card binding page further includes an option for application programs supported by the card binding server, the card binding confirmation message is also used to indicate the selected card binding application program, the card binding application program further including a second application program different from the first application program.

[0121] The input by the user to the card binding page can be related to the content of the card binding page. For example, the card binding page includes at least a part of the card number of the target card, or the card binding page includes at least a part of the card number of the target card and identity information, and the input by the user to the card binding page can include a specific input to the application program. As another example, the card binding page includes at least a part of the card number of the target card and an entry area for the identity information, and the input by the user to the card binding page can include a confirmation input to the entry input of the entry area for the identity information. As another example, the card binding page includes at least a part of the card number of the target card, options of the application program supported by the card binding server, and an entry area for the identity information, and the input by the user to the card binding page can include a confirmation input, a selection input to the application program, and an entry input to the entry area for the identity information.

[0122] In some examples, the card identifier includes a card number and / or a card payment identifier token.

[0123] For the specific contents of steps S301 to S303, reference may be made to the relevant descriptions in the above embodiments, and they will not be described here.

[0124] In an embodiment of the present application, the user terminal calls the first application program to scan the information carrier pattern, triggering access to the first page address of the card binding server indicated by the information carrier pattern, and sends the card number of the target card indicated by the information carrier pattern to the card binding server, so as to trigger the card binding server to obtain the user information of the target user who has logged into the first application program from the background server of the first application program. The user terminal receives the second page address corresponding to the card binding page, accesses the second page address, and displays the card binding page. The user terminal sends the identity information confirmed by the user and the selected card binding application program to the card binding server through a card binding confirmation message, so that the card binding server completes the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program through interaction with the card issuing server and interaction with the background server of the card binding application program. The user does not need to search for a card linking function start guide in the application program, but can directly use the scan function of the user terminal, and by jumping to a card linking page to link the card, the time required for the user to link the card is reduced, and the efficiency of the user linking the card by utilizing the application program is improved.

[0125] When the card-binding application program includes a first application program and a second application program, the user terminal sends the user-confirmed identity information and the selected card-binding application program to the card-binding server through a card-binding confirmation message, so that the card-binding server completes the binding between the card identifier of the target card and the user identifier of the target user in the card-binding application program through interaction with the card issuing server and interaction with the background server of the card-binding application program, and the card-binding operations of multiple application programs can be started collectively, without the need to access each application program to start the card-binding operation, simplifying the card-binding process in the card-binding sheet of multiple application programs. In addition, the card-binding operations of multiple application programs are started collectively, and the interrelationship between multiple application programs of the same card binding is also strengthened, making it easier for users to manage.

[0126] In some embodiments, to further ensure the security of card binding, a dynamic authentication code can be used to perform additional security authentication between the user terminal and the card binding server. Figure 11 is a flowchart of another embodiment of the card binding method according to the second aspect of the present application. The difference between Figure 11 and Figure 10 is that the card binding method shown in Figure 11 further includes steps S304 to S306.

[0127] In step S304, a dynamic authentication code request message is sent to the binding server.

[0128] In step S305, the first dynamic authentication code sent from the card binding server is received.

[0129] In step S306, send the second dynamic authentication code to the card binding server, so as to cause the card binding server to perform authentication of the dynamic authentication code.

[0130] In addition, when the card linking method includes steps S304 to S306, only if the authentication of the dynamic authentication code of the card linking server is successful, the card linking server uses the identity information to interact with the card issuing server and the background server of the card linking application program, and completes the linking between the card identifier of the target card and the user identifier of the target user in the card linking application program.

[0131] For the specific contents of steps S304 to S306, reference may be made to the relevant contents in the above embodiments, and they will not be described here.

[0132] In some embodiments, after the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program is completed, the user terminal receives a third page address corresponding to the card binding result page sent from the card binding server, accesses the third page address, and displays the card binding result page. The card binding result page is used to indicate that the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program is completed.

[0133] In some embodiments, if linking of the card identifier of the target card with the user identifier of the target user in the card linking application program is not allowed, i.e., if card linking fails, the user terminal can receive a page address corresponding to the redirected card linking failure presentation page sent by the card linking server, access the page address, display the card linking failure presentation page, and instruct the user of the card linking failure.

[0134] In some embodiments, the card binding server may provide a card binding management page to the user terminal, so that the user manages the binding relationship of the target card. The user terminal accesses a fourth page address of the card binding server, and displays the card binding management page corresponding to the fourth page address. The card binding management page includes a binding relationship between a card identifier of the target card and a user identifier of the target user in the card binding application program. In response to the user's input, the user terminal sends a management operation command to the card binding server, and the management operation command instructs the card binding server to manage and operate the binding relationship.

[0135] The management operation includes one or more of a deactivation operation, an activation operation, and a payment limit setting operation.

[0136] For specific contents such as the fourth page address, the card linking management page, the linking relationship, and the management operation, please refer to the relevant descriptions in the above embodiments, and they will not be described here.

[0137] The third aspect of the present application provides a card linking method applied to a background server of an application program, that is, the card linking method can be executed by the background server of an application program. The background server, which is an application program corresponding to the background, is a background server of a first application program. Figure 12 is a flowchart of an embodiment of the card linking method according to the third aspect of the present application. As shown in Figure 12, the card linking method can include steps S401 and S402.

[0138] In step S401, when the application program is a first application program, the card binding server calls the first application program, scans the information carrier pattern, and upon receiving access from the user terminal to the indicated first page address, transmits user information of the target user to the card binding server.

[0139] The target user is a user who has logged in to the first application program. The user information includes a user identifier of the target user in the first application program.

[0140] In some examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes the first page address and the card number of the target card.

[0141] In some other examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes the first page address and the encrypted card number of the target card.

[0142] In some other examples, the information carrier pattern includes a card face pattern of the target card, the card face pattern includes a page jump identifier and a card number of the target card, and the page jump identifier has a corresponding relationship with the first page address.

[0143] In step S402, if the card binding server receives a card binding confirmation message, interact with the card binding server to complete the binding between the card identifier of the target card and the user identifier of the target user in the first application program.

[0144] The card binding confirmation message is sent by the user terminal in response to the user's input into the card binding page and is used to indicate identity information of the target user. The card binding page includes at least a portion of the card number of the target card. The card binding application program includes a first application program.

[0145] In some examples, the card's binding page further includes an area for entering identity information.

[0146] In some alternative examples, the user information further includes identity information and the card's binding page further includes identity information.

[0147] In some examples, the card identifier includes a card number and / or a card payment identifier token.

[0148] For the specific contents of step S401 and step S402, reference may be made to the relevant descriptions in the above embodiments, and they will not be described here.

[0149] In the embodiment of the present application, when the card binding server accepts the user terminal's access to the first page address indicated by calling the first application program and scanning the information carrier pattern, the card binding server can transmit the user information of the target user to the card binding server as a background server of the first application program. The user terminal receives the second page address corresponding to the card binding page, accesses the second page address, and displays the card binding page. The user terminal transmits the identity information confirmed by the user and the selected card binding application program to the card binding server through the card binding confirmation message. As a background server of the first application program, the card binding server can interact with the binding server and complete the binding between the card identifier of the target card and the user identifier of the target user in the first application program. The user does not need to search for the activation guide of the card binding function in the application program, but can jump to the card binding page by calling the first application program and scanning the information carrier pattern to perform card binding, thereby reducing the time required for the user to bind the card and improving the efficiency of the user using the application program to bind the card.

[0150] When the application program is a first application program, a specific process of the interaction between the background server and the card binding server is introduced. Figure 13 is a flowchart of another embodiment of the card binding method according to the third aspect of the present application. The difference between Figure 13 and Figure 12 is that step S402 in Figure 12 is specifically divided into step S4021 and step S4022 in Figure 13.

[0151] In step S4021, if the card linking server receives a result of the card linking validation verification indicating that the card linking validation verification was successful, it receives a first card linking notification message sent from the card linking server.

[0152] The first card binding notification message includes result information of the card binding validation verification and the card identifier of the target card.

[0153] In step S4022, the card identifier of the target card is associated with the user identifier of the target user in the first application program.

[0154] For the specific contents of step S4021 and step S4022, reference may be made to the relevant descriptions in the above embodiments, and they will not be described here.

[0155] In some embodiments, the card-binding page further includes an option of application programs supported by the card-binding server, and the card-binding confirmation message is also used to indicate the selected card-binding application program, and the card-binding application program further includes a second application program. The first application program is different from the second application program. Figure 14 is a flowchart of another embodiment of the card-binding method according to the third aspect of the present application. Figure 14 is different from Figure 12 in that Figure 14 can further include step S403.

[0156] In step S403, if the application program is a second application program and the card binding server receives a card binding confirmation message sent from the user terminal, it interacts with the binding server to complete binding between the card identifier of the target card and the user identifier of the target user in the second application program.

[0157] When the application program corresponding to the background server is used as the first application program, it can interact with the binding server to complete the binding between the card identifier of the target card and the user identifier of the target user in the first application program. When the application program corresponding to the background server is used as the second application program, the background server can also interact with the binding server to complete the binding between the card identifier of the target card and the user identifier of the target user in the second application program. The background server of the application program can start the card binding operation of multiple application programs at once by matching it with the user terminal and the card binding server, and it is not necessary to access each application program respectively to start the card binding operation, simplifying the card binding process in the card binding sheet of multiple application programs. In addition, the card binding operation of multiple application programs is started at once, and the interrelationship between multiple application programs linked to the same card is also strengthened, making it easier for the user to manage.

[0158] When the application program is a second application program, a specific process of the interaction between the background server and the card binding server is introduced. Figure 15 is a flowchart of a further embodiment of the card binding method according to the third aspect of the present application. Figure 15 is different from Figure 14 in that step S403 in Figure 14 is specifically divided into steps S4031 to S4035 in Figure 15.

[0159] In step S4031, a card binding matching message sent from a card binding server is received, where the card binding matching message includes identity information.

[0160] In step S4032, a user identifier that matches the identity information is searched for, and the user identifier that matches the identity information is identified as the user identifier of the target user in the second application program.

[0161] In step S4033, card binding request information is sent to the card binding server.

[0162] The card binding request message is used to request the card identifier of the target card.

[0163] In step S4034, a second card binding notification message sent from the card binding server is received.

[0164] The second card binding notification message includes the card identifier of the target card.

[0165] In step S4035, the card identifier of the target card is associated with the user identifier of the target user in the second application program.

[0166] For the specific contents of steps S4031 to S4035, reference may be made to the relevant descriptions in the above embodiments, and they will not be described here.

[0167] For ease of understanding, the overall flow of the card binding method in the above embodiment is described below as an example. Figure 16 is a flowchart of an example of a card binding process according to the embodiment of the present application. Here, the first background server is a background server of a first application program, and the second background server is a background server of a second application program. As shown in Figure 16, the card binding process may include steps S501 to S524.

[0168] In step S501, the user terminal invokes a first application program to scan an information carrier pattern.

[0169] In step S502, the user terminal scans the information carrier pattern to access a first page address of the binding server of the indicated card.

[0170] In step S503, the user terminal transmits the card number indicated by the information carrier pattern to the card binding server.

[0171] In step S504, the card-binding server transmits a user information request message to the first background server, requesting user information of the target user who has logged in to the first application program from the first background server.

[0172] In step S505, the first background server authenticates the identity of the card binding server.

[0173] In step S506, if the identity authentication of the tied server is successful, the first background server feeds back the user information of the target user to the tied server.

[0174] Here, the user information includes a user identifier of the target user in the first application program and identity information of the target user. For ease of description, the user identifier of the target user in the first application program is referred to as a first user identifier.

[0175] In step S507, the card binding server sends the redirected second page address to the user terminal.

[0176] The second page address is the address of the card's binding page.

[0177] In step S508, the user terminal accesses the second page address.

[0178] In step S509, the user terminal displays a card binding page.

[0179] In step S510, the user terminal receives the user's input to the card binding page and generates a card binding confirmation message.

[0180] In step S511, the user terminal sends a card binding confirmation message to the card binding server.

[0181] The card binding confirmation message is used to indicate the identity information of the target user and the selected card binding application program. The card binding application program includes a first application program and a second application program. For ease of description, the background server of the second application program is referred to as the second background server here.

[0182] In step S512, the card binding server sends a card binding validation message to the card issuing server.

[0183] In step S513, the card issuing server obtains the card number and the target user's identity information from the card linking activation message, performs card linking activation verification using the card number and the target user's identity information, and obtains result information of the card linking activation verification.

[0184] In step S514, the card issuing server transmits the result information of the validation verification of the card binding to the card binding server.

[0185] In step S515, if the result information of the card binding activation verification indicates that the card binding activation verification is successful, the card binding server sends a first card binding notification message to the first background server.

[0186] The first card binding notification message includes a card identifier.

[0187] In step S516, the first background server associates the card identifier with the first user identifier.

[0188] In step S517, the card binding server sends a card binding matching message to the second background server.

[0189] The card binding matching message includes identity information of the target user.

[0190] In step S518, the second background server searches for a user identifier that matches the identity information, and identifies the user identifier that matches the identity information as the user identifier of the target user in the second application program.

[0191] For ease of explanation, the user identifier of the target user in the second application program is referred to herein as the second user identifier.

[0192] In step S519, the second background server sends a card binding request message to the card binding server to request a card identifier.

[0193] In step S520, the card binding server sends a second card binding notification message to the second background server.

[0194] The second card binding notification message includes a card identifier.

[0195] In step S521, the second background server associates the card identifier with the second user identifier.

[0196] In step S522, the card binding server transmits a third page address to the user terminal.

[0197] The third page address is the card binding results page.

[0198] In step S523, the user terminal accesses the third page address.

[0199] In step S524, the user terminal displays the card binding result page.

[0200] For the specific contents of the above steps S501 to S524, reference may be made to the relevant descriptions in the above embodiments, and they will not be described here.

[0201] A fourth aspect of the present application provides a server, which is a card binding server in the above embodiment. Figure 17 is a structural schematic diagram of an embodiment of the server according to the fourth aspect of the present application. As shown in Figure 17, the server 600 may include an interaction module 601, and the interaction module 601 may include a receiving unit 6011 and a sending unit 6012.

[0202] The interaction module 601 is used to call a first application program and scan an information carrier pattern to accept access from a user terminal to a first page address indicated by the information carrier pattern, and obtain the card number of a target card indicated by the information carrier pattern, and can also be used to obtain user information of a target user from a background server of the first application program.

[0203] The target user is a user who has logged in to the first application program. The user information includes a user identifier of the target user in the first application program.

[0204] In some examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes a first page address and a card number of the target card.

[0205] In some other examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes the first page address and the encrypted card number of the target card.

[0206] In some other examples, the information carrier pattern includes a card face pattern of the target card, the card face pattern includes a page jump identifier and a card number of the target card, and the page jump identifier has a corresponding relationship with the first page address.

[0207] The sending unit 6012 is used for sending a second page address corresponding to the redirected card binding page to the user terminal.

[0208] The card binding page includes at least a portion of the target card's card number.

[0209] In some examples, the card binding page may further include options for application programs supported by the card binding server.

[0210] In some alternative examples, the card's binding page may further include an area for writing identity information.

[0211] In some other examples, the user information may further include identity information, and the card's binding page may further include identity information.

[0212] The receiving unit 6011 can further be used for receiving card binding confirmation information sent by the user terminal based on the card binding page.

[0213] The card binding verification information is used to indicate the identity information of the target user.

[0214] The interaction module 601 uses the identity information to interact with the card issuing server and the background server of the card binding application program to complete binding between the card identifier of the target card and the user identifier of the target user in the card binding application program.

[0215] The card binding application programs include a first application program.

[0216] In some examples, the card identifier includes a card number and / or a card binding identifier token.

[0217] In an embodiment of the present application, the card binding server accepts the user terminal's access to the first page address indicated by calling the first application program and scanning the information carrier pattern, and obtains the card number of the target card indicated by the information carrier pattern. The first page address is provided by the card binding server in bulk. The card binding server obtains user information of the target user who logged into the first application program from the background server of the first application program. The user terminal's access to the first page address triggers the card binding server to send the second page address corresponding to the redirected card binding page to the user terminal, so that the user terminal accesses the second page address to display the card binding page. The card binding server can complete the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program through interaction with the card issuing server and interaction with the background server of the card binding application program by the user terminal identifying the identity information of the target user based on the card binding confirmation information sent by the card binding page. The user does not need to search for a card linking function start guide in an application program, but can call up a first application program, scan an information carrier pattern, jump to a card linking page and link the card, thereby reducing the time required for the user to link the card and improving the efficiency of the user linking the card by utilizing the application program.

[0218] In some embodiments, the sending unit 6012 can be used to send card binding activation information to a card issuing server, so that the card issuing server uses the identity information to perform card binding activation verification.

[0219] The card binding activation information includes the card number and identity information of the target card.

[0220] The receiving unit 6011 can be used to receive the result information of the card binding validation verification sent by the card issuing server.

[0221] When the result information of the card linking activation verification indicates that the card linking activation verification is successful, the above-mentioned sending unit 6012 sends a first card linking notification message to the background server of the first application program, so that the background server of the first application program completes the linking between the card identifier of the target card and the user identifier of the target user in the first application program.

[0222] The first card binding notification message includes result information of the card binding validation verification and the card identifier of the target card.

[0223] In some embodiments, if the card binding page can further include application program options supported by the card binding server, the card binding confirmation message is also used to indicate the selected card binding application program, and the card binding application program further includes a second application program different from the first application program.

[0224] The above-mentioned sending unit 6012 can further be used to send a card binding matching message to the background server of the second application program, so that the background server of the second application program searches for a user identifier matching the identity information.

[0225] The card binding matching message includes identity information.

[0226] The above receiving unit 6011 can be used to receive a card binding request message sent by the background server of the second application program when a user identifier matching the identity information is found.

[0227] The card binding request message is used to request the card identifier of the target card.

[0228] The above-mentioned sending unit 6012 can be used to send a notification message of binding of the second card to the background server of the second application program, so that the background server of the second application program completes the binding between the card identifier of the target card and the user identifier of the target user in the second application program.

[0229] The notification message of the second card binding includes a card identifier of the target card, and the user identifier of the target user in the second application program is a user identifier that matches the identity information.

[0230] Fig. 18 is a structural schematic diagram of another embodiment of a server according to the fourth aspect of the present application. The difference between Fig. 18 and Fig. 17 is that the server 600 shown in Fig. 18 may further include a decryption module 602.

[0231] The receiving unit 6011 receives the card number of the target card encrypted by the first key sent from the user terminal.

[0232] The decryption module 602 decrypts the encrypted card number of the target card using a second key that is paired with the first key stored in advance, and acquires the card number of the target card.

[0233] In some embodiments, the receiving unit 6011 receives a dynamic authentication code request message sent from a user terminal.

[0234] The sending unit 6012 can be used to send a first dynamic authentication code to a user terminal.

[0235] The receiving unit 6011 can be used to receive a second dynamic authentication code sent by a user terminal.

[0236] If the first dynamic authentication code and the second dynamic authentication code match, the above-mentioned interaction module 601 uses the identity information to interact with the card issuing server and the background server of the card binding application program, and completes the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program.

[0237] Fig. 19 is a structural schematic diagram of another embodiment of a server according to the fourth aspect of the present application. Fig. 19 differs from Fig. 17 in that a server 600 shown in Fig. 19 may further include an authentication module 603.

[0238] The authentication module 603 is used to determine whether the first application program is an application program supported by the card's binding server.

[0239] The receiving unit 6011 obtains user information of the target user from the background server of the first application program when the first application program is an application program supported by the card binding server.

[0240] In some embodiments, the sending unit 6012 is used to send a third page address corresponding to the redirected card binding result page to the user terminal.

[0241] The card binding result page is used to indicate that binding between the card identifier of the target card and the user identifier of the target user in the card binding application program is complete.

[0242] The interaction module 601 can be used to receive a user terminal access to a third page address.

[0243] Fig. 20 is a structural schematic diagram of a further embodiment of a server according to the fourth aspect of the present application. The difference between Fig. 20 and Fig. 17 is that the server 600 shown in Fig. 20 may further include an execution module 604.

[0244] The interaction module 601 is used to accept access from the user terminal to a fourth page address corresponding to a card binding management page.

[0245] The card binding management page includes a binding relationship between the card identifier of the target card and the user identifier of the target user in the card binding application program.

[0246] The receiving unit 6011 can be used to receive a management operation command of a user terminal.

[0247] The execution module 604 can be used to execute a management operation according to the management operation command on the binding relationship indicated by the management operation command.

[0248] In some examples, the management operation includes one or more of a deactivate operation, an activate operation, and a set payment limit operation.

[0249] A fifth aspect of the present application provides a user terminal. FIG. 21 is a structural schematic diagram of an embodiment of a user terminal according to the fifth aspect of the present application. As shown in FIG. 21, the user terminal 700 may include a scan module 701, an interaction module 702 and a display module 703. The interaction module 702 may include a sending unit 7021. In some examples, the interaction module 702 may further include a receiving unit 7022.

[0250] The scan module 701 can be used to scan the information carrier pattern when the first application program is invoked.

[0251] The interaction module 702 can be used to scan the information carrier pattern to access a first page address of the indicated card binding server, and send the card number of the target card indicated by the carrier pattern to the card binding server, so as to trigger the card binding server to obtain user information of the target user from the background server of the first application program.

[0252] The target user is a user who has logged in to the first application program. The user information includes a user identifier of the target user in the first application program.

[0253] In some examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes a first page address and a card number of the target card.

[0254] In some other examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes the first page address and the encrypted card number of the target card.

[0255] In some other examples, the information carrier pattern includes a card face pattern of the target card, the card face pattern includes a page jump identifier and a card number of the target card, and the page jump identifier has a corresponding relationship with the first page address.

[0256] The interaction module 702 can be used to receive the second page address sent by the card binding server and access the second page address.

[0257] The display module 703 can be used to display the binding page of the card corresponding to the second page address.

[0258] The card binding page includes at least a portion of the target card's card number.

[0259] In some examples, the card binding page further includes an option of application programs supported by the card binding server, and correspondingly, the card binding confirmation message is also used to indicate the selected card binding application program, and the card binding application program further includes a second application program different from the first application program.

[0260] In some other examples, the card's binding page further includes an area for writing identity information.

[0261] In some other examples, the user information further includes identity information and the card's binding page further includes identity information.

[0262] The sending unit 7021 can be used to send a card binding confirmation message to the card binding server in response to the user's input on the card binding page, so that the card binding server uses the identity information to interact with the card issuing server and the background server of the card binding application program to complete the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program.

[0263] The card binding confirmation message indicates identity information of the target user. The card binding application program includes a first application program.

[0264] In some examples, the card identifier includes a card number and / or a card payment identifier token.

[0265] In an embodiment of the present application, the user terminal calls a first application program to scan the information carrier pattern, triggers access to a first page address of the card binding server indicated by the access information carrier pattern, and sends the card number of the target card indicated by the information carrier pattern to the card binding server, so as to trigger the card binding server to obtain user information of the target user who logs in to the first application program from the background server of the first application program. The user terminal receives a second page address corresponding to the card binding page, accesses the second page address, and displays the card binding page. The user terminal sends the user confirmed identity information and the selected card binding application program to the card binding server through a card binding confirmation message, so that the card binding server completes the binding between the card identifier of the target card and the user identifier of the target user in the card binding application program through interaction with the card issuing server and interaction with the background server of the card binding application program. The user does not need to search for a card linking function start guide in an application program, but can directly use the scan function of the user terminal, and by jumping to a card linking page to link the card, the time required for the user to link the card is reduced, and the efficiency of the user linking the card using the application program is improved.

[0266] When the card-binding application program includes a first application program and a second application program, the user terminal transmits the user-confirmed identity information and the selected card-binding application program to the card-binding server according to the card-binding confirmation information, and the card-binding server completes the binding between the card identifier of the target card and the user identifier of the target user in the card-binding application program through the interaction with the card issuing server and the interaction with the background server of the card-binding application program, and the card-binding operation of multiple application programs can be started collectively, and there is no need to access each application program to start the card-binding operation, simplifying the card-binding process in the card-binding sheet of multiple application programs. In addition, the card-binding operation of multiple application programs is started collectively, and the interrelationship between the multiple application programs linked to the same card is also strengthened, making it easier for the user to manage.

[0267] In some embodiments, the above sending unit 7021 can be used to send the card number of the target card encrypted by the first key to the card binding server.

[0268] The card binding server stores a second key that pairs with the first key.

[0269] In some embodiments, the sending unit 7021 sends the request information for the dynamic authentication code to the card binding server.

[0270] The receiving unit 7022 can further be used for receiving a first dynamic authentication code sent by a card binding server.

[0271] The above sending unit 7021 can further be used to send a second dynamic authentication code to the card binding server, so that the card binding server performs the dynamic authentication code.

[0272] In some embodiments, the interaction module 702 receives a third page address corresponding to the card binding result page sent by the card binding server, accesses the third page address, and displays the card binding result page.

[0273] The card binding result page is used to indicate that binding between the card identifier of the target card and the user identifier of the target user in the card binding application program has been completed.

[0274] In some embodiments, the interaction module 702 can further be used to access a fourth page address of the card binding server.

[0275] In some embodiments, the display module 703 can further be used to display a card binding management page corresponding to the fourth page address.

[0276] The card binding management page includes a binding relationship between the card identifier of the target card and the user identifier of the target user in the card binding application program.

[0277] The sending unit 7021 can be used to send management operation commands to the card binding server in response to a user's input.

[0278] The management operation command instructs the card's binding server to manage and manipulate the binding relationship.

[0279] In some examples, the management operation includes one or more of a deactivate operation, an activate operation, and a set payment limit operation.

[0280] A sixth aspect of the present application provides a server, which is a background server in the above embodiment. When an application program corresponding to the background server is used as a first application program, the background server is a background server of the first application program in the above embodiment, and when an application program corresponding to the background server is used as a second application program, the background server is a background server of the second application program in the above embodiment. FIG. 22 is a structural schematic diagram of an embodiment of a server according to the sixth aspect of the present application. As shown in FIG. 22, the server 800 can include an interaction module 801. The interaction module 801 can include a sending unit 8011. In some examples, the interaction module 801 can further include a receiving unit 8012.

[0281] The sending unit 8011 can be used to send user information of the target user to the card linking server when the application program is a first application program and the card linking server accepts access from the user terminal to a first page address indicated by calling the first application program and scanning the information carrier pattern.

[0282] The target user is a user who has logged in to the first application program. The user information includes a user identifier of the target user in the first application program.

[0283] In some examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes a first page address and a card number of the target card.

[0284] In some other examples, the information carrier pattern includes a two-dimensional code, and the information recorded in the two-dimensional code includes the first page address and the encrypted card number of the target card.

[0285] In some other examples, the information carrier pattern includes a card face pattern of the target card, the card face pattern includes a page jump identifier and a card number of the target card, and the page jump identifier has a corresponding relationship with the first page address.

[0286] The interaction module 801 can be used to interact with the card binding server and complete the binding between the card identifier of the target card and the user identifier of the target user in the first application program when the card binding server receives a card binding confirmation message.

[0287] The card binding confirmation message is sent by the user terminal in response to a user input on the binding page and is used to indicate identity information of the target user. The card binding page includes at least a portion of the card number of the target card. The card binding application program includes a first application program.

[0288] In some examples, the card binding page further includes options for application programs supported by the card binding server.

[0289] In some other examples, the card's binding page further includes an area for writing identity information.

[0290] In some other examples, the user information further includes identity information and the card's binding page further includes identity information.

[0291] In some examples, the card identifier includes a card number and / or a card payment identifier token.

[0292] In the embodiment of the present application, when the card binding server accepts the user terminal's access to the first page address indicated by calling the first application program and scanning the information carrier pattern, it can transmit the user information of the target user to the card binding server as a background server of the first application program. The user terminal receives the second page address corresponding to the card binding page, accesses the second page address, and displays the card binding page. The user terminal transmits the identity information confirmed by the user and the selected card binding application program to the card binding server according to the card binding confirmation information. As a background server of the first application program, it can interact with the binding server and complete the binding between the card identifier of the target card and the user identifier of the target user in the first application program. The user does not need to search for the activation guide of the card binding function in the application program, but can jump to the card binding page by calling the first application program and scanning the information carrier pattern to perform card binding, thereby reducing the time required for the user to bind the card and improving the efficiency of the user using the application program to bind the card.

[0293] 23 is a structural schematic diagram of another embodiment of a server according to the sixth aspect of the present application. The difference between FIG. 23 and FIG. 22 is that a server 800 may further include a linking module 802.

[0294] The above-mentioned receiving unit 8012 receives a first card binding notification message sent from the card binding server when the card binding server receives a card binding activation verification result indicating that the card binding activation verification is successful.

[0295] The first card binding notification message includes result information of the card binding validation verification and the card identifier of the target card.

[0296] The linking module 802 can be used to link the card identifier of the target card and the user identifier of the target user in the first application program.

[0297] In some embodiments, if the card binding page further includes application program options supported by the card binding server, the card binding confirmation message is used to indicate the selected card binding application program, and the card binding application program further includes a second application program different from the first application program.

[0298] The interaction module 801 can be used, when the application program is a second application program and the card binding server receives a card binding confirmation message sent from the user terminal, to interact with the binding server to complete binding between the card identifier of the target card and the user identifier of the target user in the second application program.

[0299] 24 is a structural schematic diagram of another embodiment of a server according to the sixth aspect of the present application. The difference between FIG. 24 and FIG. 23 is that a server 800 may further include a search module 803.

[0300] The receiving unit 8012 receives a card binding matching message sent from a card binding server, where the card binding matching message includes identity information.

[0301] The search module 803 searches for a user identifier that matches the identity information, and identifies the user identifier that matches the identity information as the user identifier of the target user in the second application program.

[0302] The sending unit 8011 is used for sending a card binding request message to the card binding server, and the card binding request message can be used to request the card identifier of the target card.

[0303] The above-mentioned receiving unit 8012 is used for receiving a second card binding notification message sent by the card binding server, where the second card binding notification message includes the card identifier of the target card.

[0304] The linking module 803 can be used to link the card identifier of the target card with the user identifier of the target user in the second application program.

[0305] The seventh aspect of the present application provides a server. Fig. 25 is a structural schematic diagram of an embodiment of the server according to the seventh aspect of the present application. As shown in Fig. 25, the server 900 includes a memory 901, a processor 902, and a computer program stored in the memory 901 and executable by the processor 902.

[0306] In one example, the processor 902 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of embodiments of the present application.

[0307] The memory 901 may include a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk storage media device, an optical storage media device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it operates to perform the operations described in the card binding method applied to the card binding server in the embodiment of the present application.

[0308] The processor 902 reads the computer program instructions stored in the memory 901 and executes the computer program corresponding to the executable program code, thereby implementing the binding method applied in the card binding server in the above embodiment.

[0309] In an example, the server 900 may further include a communication interface 903 and a bus 904. As shown in Fig. 25, the memory 901, the processor 902, and the communication interface 903 are connected via the bus 904 to complete communication with each other.

[0310] The communication interface 903 is mainly used to realize communication between each module, device, unit and / or equipment in the embodiment of the present application. An input device and / or an output device can also be connected via the communication interface 903.

[0311] Bus 904 may include hardware, software, or both, and may couple together components of server 900. For example, bus 904 may include, but is not limited to, an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low pin count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or any other suitable bus or a combination of two or more thereof. Where appropriate, bus 904 may include one or more buses. Although embodiments herein are illustrated and described with a particular bus, this application contemplates any suitable bus or interconnect.

[0312] The eighth aspect of the present application provides a user terminal. Fig. 26 is a structural schematic diagram of an embodiment of a user terminal according to the eighth aspect of the present application. As shown in Fig. 26, the user terminal 1000 includes a memory 1001, a processor 1002, and a computer program stored in the memory 1001 and executable by the processor 1002.

[0313] In one example, the processor 1002 may include a central processing unit (CPU) or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of embodiments of the present application.

[0314] The memory 1001 may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software that includes computer-executable instructions, and when the software is executed (e.g., by one or more processors), it operates to perform the operations described in the card binding method applied to the card binding server in the embodiment of the present application.

[0315] The processor 1002 realizes the linking method applied to the card linking server in the above embodiment by reading executable program code stored in the memory 1001 and executing a computer program corresponding to the executable program code.

[0316] In an example, the server 1000 may further include a communication interface 1003 and a bus 1004. As shown in Fig. 26, the memory 1001, the processor 1002, and the communication interface 1003 are connected via the bus 1004 to complete communication with each other.

[0317] The communication interface 1003 is mainly used to realize communication between each module, apparatus, unit and / or device in the embodiment of the present application. An input device and / or an output device can also be connected via the communication interface 1003.

[0318] Bus 1004 may include hardware, software, or both, and may couple together components of server 900. For example, bus 904 may include, but is not limited to, an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low pin count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or any other suitable bus or a combination of two or more thereof. Where appropriate, bus 1004 may include one or more buses. Although embodiments herein are illustrated and described with a particular bus, this application contemplates any suitable bus or interconnect.

[0319] The ninth aspect of the present application provides a server. Fig. 27 is a structural schematic diagram of an embodiment of the server according to the ninth aspect of the present application. As shown in Fig. 27, the server 1100 includes a memory 1101, a processor 1102, and a computer program stored in the memory 1101 and executable by the processor 1102.

[0320] In one example, the processor 1102 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of embodiments of the present application.

[0321] The memory 1101 may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it operates to perform the operations described in the card binding method applied to the card binding server in the embodiment of the present application.

[0322] The processor 1102 realizes the binding method applied to the card binding server in the above embodiment by reading the executable program code stored in the memory 1101 and executing a computer program corresponding to the executable program code.

[0323] In an example, the server 1100 may further include a communication interface 1103 and a bus 1104. As shown in Fig. 27, the memory 1101, the processor 1102, and the communication interface 1103 are connected via the bus 1104 to complete communication with each other.

[0324] The communication interface 1103 is mainly used to realize communication between each module, device, unit and / or equipment in the embodiment of the present application. An input device and / or an output device can also be connected via the communication interface 1103.

[0325] Bus 1104 may include hardware, software, or both, and may couple together components of server 900. For example, bus 904 may include, but is not limited to, an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low pin count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or any other suitable bus or a combination of two or more thereof. Where appropriate, bus 1004 may include one or more buses. Although embodiments herein are illustrated and described with a particular bus, this application contemplates any suitable bus or interconnect.

[0326] The tenth aspect of the present application provides a card binding system, which can include the card binding server, the user terminal, and the application program server in the above embodiment. For the specific contents of the card binding server, the user terminal, and the application program server, and the specific contents of the interaction between the card binding server, the user terminal, and the application program server, refer to the relevant descriptions in the above embodiment, and will not be described here.

[0327] The eleventh aspect of the present application provides a computer-readable storage medium, which stores computer program commands. When the computer program commands are executed by a processor, the card binding method in the above embodiment can be realized and the same technical effect can be achieved, and in order to avoid duplication, they will not be described here. Here, examples of the computer-readable storage medium may include non-transitory computer-readable storage media such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and are not limited here.

[0328] In addition, each embodiment in this specification is described gradually, and the same or similar parts between each embodiment may be referred to each other, and each embodiment mainly describes the difference from other embodiments. For the server embodiment, the user terminal embodiment, the system embodiment, and the computer-readable storage medium embodiment, the description of the method embodiment may be referred to in the relevant part. The present application is not limited to the specific steps and structures described above. Those skilled in the art may make various changes, modifications, and additions, or change the order between steps after departing from the spirit of the present application. For simplicity, a detailed description of the known method technology is omitted here.

[0329] The above describes the various aspects of the present application with reference to flowcharts and / or block diagrams of methods, apparatuses (systems) and computer program products according to the embodiments of the present application. It should be understood that each block in the flowcharts and / or block diagrams and combinations of each block in the flowcharts and / or block diagrams may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing device, thereby generating a machine, such that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams. Such a processor may be, but is not limited to, a general purpose processor, a special purpose processor, a special application processor, or a field programmable logic circuit. It should be understood that each block in the block diagrams and / or flowcharts and combinations of blocks in the block diagrams and / or flowcharts may be implemented by dedicated hardware performing the specified functions or operations, or by a combination of dedicated hardware and computer instructions.

[0330] As can be understood by those skilled in the art, the above embodiments are not exemplary. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Those skilled in the art can understand and realize other variations of the disclosed embodiments after studying the drawings, the specification and the claims. In the claims, the term "comprises" does not exclude other devices or steps. The quantifier "a" does not exclude a plurality. The terms "first" and "second" are used to indicate names, and do not indicate any particular order. Any drawing labeling in the claims should not be understood as limiting the scope of protection. The functions of multiple parts described in the claims can be realized by one single hardware or software module. If certain technical features appear in different dependent claims, it does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A card binding method applied to a card binding server, comprising: Invoke a first application program to scan the information carrier pattern; Accepting an access from a user terminal to the designated first page address, and obtaining a card number of a target card indicated by a carrier pattern; The user ID of the target user is sent from the background server of the first application program. and acquiring user information of the target user logging in to the first application program. the user information is a previous user in the first application program, Including a user identifier of the target user; The second page address corresponding to the redirected card binding page is sent to the user. the card linking page is sent to the user's terminal, and the card linking page is at least Including a part of Confirmation of card linking transmitted from the user terminal via the card linking page. A message is received, and a confirmation message for linking the card is sent to the target user's ID. and Using the identity information, a card issuing server and a card linking application The application program interacts with the background server of the target card. The card identifier and the target user in the card binding application program and completing the binding of the card to the user identifier of the user, and executing the application program for binding the card. the application program is an application program to be linked with the card identifier of the target card, and the application program to be linked with the card includes a first application program; How to link a card.

2. The information carrier pattern includes a two-dimensional code, and information recorded in the two-dimensional code The information includes the first page address and the card number of the target card, or The information recorded in the dimensional code is the first page address and the encrypted target page address. Contains the card number of the card, or, The information carrier pattern includes a pattern of a card surface of the target card, the pattern of the card surface includes a page jump identifier and a card number of the target card, and the page jump identifier has a corresponding relationship with the first page address. The method of claim 1.

3. Using the identity information, a card issuing server and an access to the card binding server are The application program interacts with the background server to The card identifier of the card and the card binding application program Completing the binding with the user identifier of the target user is The card issuing server uses the identity information to validate and verify the card binding. The card issuing server is provided with the card number of the target card and the identity sending a card binding activation message including the card's identity information; Receives information on the result of validation verification of card binding transmitted from the card issuing server. And, The result information of the validation verification of the card linking indicates that the validation verification of the card linking was successful. When the user indicates that the first application program has been started, the background service of the first application program is started. The server inputs the card identifier of the target card and a pre-defined number in the first application program. The first application is configured to complete the association with the user identifier of the target user. The result information of the validation verification of the linking of the card is stored in the background server of the program. and sending a notification message of the first card binding including the card identifier of the target card. and The method of claim 1.

4. The card binding page is an application supported by the card binding server. The application program option is further included, and a confirmation message for linking the card is displayed. The message further indicates an application program associated with the selected card. The card binding application program is used for the second application. The present invention further includes a program for Using the identity information, a card issuing server and an access to the card binding server are The application program interacts with the background server to The card identifier of the card and the card binding application program Completing the binding with the user identifier of the target user is A background server of the second application program The second application is configured to search for a user identifier matching the identity information. Binding of a card containing said identity information to a background server of the program Sending a matching message to If a user identifier that matches the identity information is found, the second application The card number of the target card sent by the background server of the application program receiving a card binding request message requesting a card identifier; The background server of the second application program A card identifier and a user of the target user in the second application program The background of the second application program is started so as to complete the binding with the identifier. A notification message of the association of the second card including the card identifier of the target card is sent to the round server. a message to the target user in the second application program. The user identifier is a user identifier that matches the identity information. , further comprising: The method of claim 1.

5. The card's binding page further includes an area for writing identity information; or The user information further includes the identity information, and the card's binding page The message further includes the identity information. The method of claim 1.

6. Obtaining the card number of the target card from the user terminal The card number of the target card encrypted by the first key transmitted by the user terminal receiving a code number; The encrypted Decrypting the card number of the target card to obtain the card number of the target card. include, The method of claim 1.

7. Using the identity information, a card issuing server and an access to the card binding server are The application program interacts with the background server to The card identifier of the card and the card binding application program Before completing the binding with the user identifier of the target user, receiving a dynamic authentication code request message sent by the user terminal; And, Sending a first dynamic authentication code to the user terminal; receiving a second dynamic authentication code sent by the user terminal; Further comprising: Using the identity information, a card issuing server and an access to the card binding server are The application program interacts with the background server to The card identifier of the card and the card binding application program Completing the binding with the user identifier of the target user is The first dynamic authentication code and the second dynamic authentication code match. In this case, the identity information is used to link the card issuing server and the card. It interacts with the background server of the application program and In the application program for linking the card identifier of the target card with the card completing a binding with a user identifier of the target user; The method of claim 1.

8. Access to a first page address by a first application program of a user terminal After accepting the access and obtaining the card number of the target card from the user terminal, The first application program is supported by a binding server of the card. determining whether the program is a supported application program; The first application program transmits a signal to a background server of the first application program in front of the target user. The acquisition of the above user information is The first application program is supported by a binding server of the card. the first application program is an application program to be executed; obtaining the user information of the target user from a background server of the The method of claim 1.

9. Using the identity information, a card issuing server and an access to the card binding server are The application program interacts with the background server to The card identifier of the card and the card binding application program After completing the association with the user identifier of the target user, The third page address corresponding to the redirected card binding result page is added to the The card association result page is sent to the user terminal, and the card association result page includes the card ID of the target card. The user ID of the target user in the application program for linking the card is used to indicate that the binding to the user identifier has been completed; and accepting access from the user terminal to the third page address; and Included in The method of claim 1.

10. Accessing the user terminal to a fourth page address corresponding to a card binding management page. The card association management page receives the card identifier of the target card. and the user identification of the target user in the application program for linking the card Including a linking relationship with Besshi, Receive a management operation command from a user terminal, and and performing management operations on the attachment relationships. The management operations include a deactivation operation, an activation operation, and a payment limit setting operation. The present invention includes one or more of the following works: The method of claim 1.

11. The card identifier comprises a card number and / or a card payment identifier token.

11. The method according to any one of 1 to 10.

12. A card linking method applied to a user terminal, comprising: Invoking a first application program to scan the information carrier pattern; A first page address of a card binding server indicated by the information carrier pattern and the card binding server accesses the first application program. Triggers the acquisition of user information of the target user from the program's background server. The information carrier pattern instructs the card binding server to A card number of a target card is transmitted, and the target user executes the first application program. the user information is a user who has logged in to the first application program, a user identifier of the target user in the RAM; The second page address transmitted by the card binding server is received and the second page address is accessing the second page address and associating the card corresponding to the second page address; a page is displayed, and the card linking page is at least one of the card number of the target card Including a part of The card binding server uses the identity information to Background server and interaction with application programs for binding and an application program for linking the card identifier of the target card with the card. The user may then complete the association with the user identifier of the target user in the system. In response to an input to a linking page of the card, the identity information of the target user is A confirmation message of the card binding to indicate the information of the card binding server is sent to the card binding server. transmitting a card-linked application program, the card-linked application program being an application program to be linked with a card identifier of the target card, the card-linked application program including the first application program; How to link a card.

13. The information carrier pattern includes a two-dimensional code, and information recorded in the two-dimensional code The information includes the first page address and the card number of the target card, or The information recorded in the dimensional code is the first page address and the encrypted target page address. Contains the card number of the card, or, The information carrier pattern includes a pattern of a card surface of the target card, the pattern of the card surface includes a page jump identifier and a card number of the target card, and the page jump identifier has a corresponding relationship with the first page address. The method of claim 12.

14. The card binding page is an application supported by the card binding server. The application program option is further included, and a confirmation message for linking the card is displayed. The message further indicates an application program for binding the selected card. and the card binding application program is a second application Further, the present invention includes a The method of claim 12.

15. The card's binding page further includes an area for writing identity information; or The user information further includes the identity information, and the card's binding page The message further includes the identity information. The method of claim 12.

16. Transmitting the card number of the target card to the card binding server includes: The card number of the target card encrypted by the first key is transmitted to the card linking server. The card binding server stores a second key that is paired with the first key. Including, The method of claim 12.

17. The second page address transmitted by the card binding server is received and the second page address is After accessing page address 2, Sending a dynamic authentication code request message to the card binding server. and, receiving a first dynamic authentication code sent from the card binding server; And, The card binding server performs authentication of the dynamic authentication code. and transmitting a second dynamic authentication code to the card binding server. 、 The method of claim 12.

18. In response to the card binding result page sent by the card binding server, receiving a corresponding third page address and accessing the third page address; A result page of the card association is displayed, and the result page of the card association is displayed as the target card. The card identifier and the card are associated in an application program. is used to indicate that binding of the target user with the user identifier has been completed. Further including: The method of claim 12.

19. Access a fourth page address of the card binding server, a management page for linking a card corresponding to the address, and The message is a card identifier of the target card and an application program for linking the card and a linking relationship with the user identifier of the target user in the In response to a user's input, a management operation command is sent to the binding server of the card, The management operation is to instruct the card binding server to perform the management operation of the binding relationship. and The management operations include a deactivation operation, an activation operation, and a payment limit setting operation. The present invention includes one or more of the following works: The method of claim 12.

20. The card identifier comprises a card number and / or a card payment identifier token.

20. The method according to any one of claims 12 to 19.

21. A server including an interaction module, The interaction module includes a receiving unit and a sending unit; The interaction module invokes a first application program. The user terminal scans the information carrier pattern to the first page address indicated. Accepting access and the card of the target card indicated by the information carrier pattern A program code for acquiring a version number of the first application program. the target user is a user who has logged in to the first application program, and the user information includes a user identifier of the target user in the first application program; The sending unit sends a second page corresponding to the binding page of the redirected card. The linking page of the card is used to transmit the ID and password to the user terminal. Including at least a part of the card number of the target card, The receiving unit receives the linking page of the card transmitted from the user terminal. A card binding confirmation message is received, and the card binding confirmation message is received. The message is used to indicate identity information of the target user; The interaction module utilizes the identity information to issue a card. The transaction server and the background server of the card binding application program The card identifier of the target card and the application of the link of the card are and completing a link between the application program and the user identifier of the target user, the application program for linking the card being an application program to be linked with the card identifier of the target card, the application program for linking the card including the first application program; server.

22. A user interface including a scan module, an interaction module, and a display module. The terminal, The interaction module includes a sending unit; The scan module detects when a first application program is invoked. used to scan the information carrier pattern, The interaction module scans the information carrier pattern and Accessing a first page address of a binding server of a card to be bound, and The background server transfers the target user from the background server of the first application program. The card is then forwarded to a binding server to trigger the card to obtain user information of the user. Used to transmit the card number of the target card indicated by the information carrier pattern The target user is a user who logged in to the first application program. the user information is the target user in the first application program, a user identifier for the user, The interaction module receives the first message sent by the card binding server. and used to receive a second page address and access the second page address. 、 The display module displays a card binding page corresponding to the second page address. The card's linking page is used to display the card number of the target card. At least a portion of The sending unit is further used for sending a card-binding confirmation message to the card-binding server in response to the user's input of the card-binding page, so that the card-binding server uses identity information to interact with a card issuing server and a background server of a card-binding application program to complete the binding between the card identifier of the target card and the user identifier of the target user in the card-binding application program, the card-binding confirmation message is for indicating the identity information of the target user, and the card-binding application program is an application program to be bound with the card identifier of the target card, and the card-binding application program includes the first application program; User terminal.

23. A server including a processor and a memory storing computer program commands. And, When the processor executes the computer program commands, 1. A card linking method according to claim 1, server.

24. A user interface including a processor and a memory storing computer program commands. A terminal, When the processor executes the computer program commands, 20. A card linking method according to any one of claims 1 to 20, User terminal.

25. A server according to claim 23; A user terminal according to claim 24; Applied to the background server of the card binding application program A server that realizes the card binding method and Equipped with The card binding method applied to the background server of the card binding application program comprises: The application program is a first application program, Calls up an application program and scans the information carrier pattern to The card binding server accepts the access from the user terminal to the first page address In this case, the user information of the target user is transmitted to the card linking server, and the target user a user who has logged in to the first application program, and the user information a user identifier of the target user in the first application program; And, When the card binding server receives a card binding confirmation message, The card identifier of the target card and the first application are linked by interacting with the linking server of the and completing the association with the user identifier of the target user in the application program; The card linking confirmation message is sent from the user terminal to the card linking page by the user. a message sent in response to an input to a page indicating identity information of said target user; The card's linking page is for identifying at least one of the card numbers of the target card. a part of the application program for linking the card with the card identifier of the target card, the application program for linking the card being an application program to be linked with the card identifier of the target card, the application program for linking the card including the first application program; Card binding system.

26. A computer readable storage medium having computer program commands stored thereon. A body, The computer program instructions, when executed by a processor, cause the computer to 21. A method for implementing the linking method according to claim 20, A computer-readable storage medium.

Images