Resource account binding method, server, device, system and storage medium

Abstract

The present application discloses a resource account binding method, server, device, system and storage medium, which belongs to the field of data processing. The method includes: obtaining the target user real-name information from the application side, the target user real-name information includes the user real-name information of the target user; receiving the target resource account information sent by the application side, the target resource account information includes the resource account information of the target user; in the case where the cloud server has the user real-name information consistent with the target user real-name information, the target resource account information is bound to the target identifier, the target identifier includes the main identifier in the cloud server that has a corresponding relationship with the target user real-name information; the cloud server stores the main identifier and the user real-name information with a corresponding relationship, and the main identifier corresponds to the user real-name information one by one. According to the embodiment of the present application, the number of binding operations of the user can be reduced, thereby simplifying the binding operation when the user uses multiple applications.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a resource account binding method, server, device, system and storage medium. Background Art

[0002] With the development of network technology, payment can be made through various applications (Application, APP). In order to facilitate payment, users can bind their resource accounts in the application so that they can directly use their resource accounts to make payments in the application later.

[0003] Different applications have their own user systems. When a user switches to use different applications, even if the same resource account is used before and after the application is switched, if the resource account is not bound in the application after the switch, the user needs to bind his resource account to the application after the switch. That is, when the user switches to different applications, the user needs to perform multiple binding operations, which is cumbersome. Summary of the invention

[0004] Embodiments of the present application provide a resource account binding method, server, device, system, and storage medium, which can reduce the number of binding operations performed by a user, thereby simplifying the binding operations when the user uses multiple applications.

[0005] In the first aspect, an embodiment of the present application provides a resource account binding method, which is applied to a cloud server, wherein the cloud server stores a primary identifier and user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one-to-one; the method includes: obtaining the target user real-name information from the application side, the target user real-name information including the user real-name information of the target user; receiving the target resource account information sent by the application side, the target resource account information including the resource account information of the target user; when the cloud server has user real-name information that is consistent with the target user real-name information, binding the target resource account information to the target identifier, the target identifier including the primary identifier in the cloud server that has a corresponding relationship with the target user real-name information.

[0006] In a second aspect, an embodiment of the present application provides a resource account binding method, which is applied to an application side, and the method includes: obtaining target user real-name information and target resource account information, the target user real-name information includes the user real-name information of the target user, and the target resource account information includes the resource account information of the target user; sending the target user real-name information to a cloud server, so that the cloud server queries and obtains a primary identifier having a corresponding relationship with the target user real-name information, the cloud server stores the primary identifier and user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one-to-one; sending the target resource account information to the cloud server, so that the cloud server binds the target resource account information to the primary identifier having a corresponding relationship with the target user real-name information.

[0007] In the third aspect, an embodiment of the present application provides a server, which stores a primary identifier and user real-name information with a corresponding relationship, and the primary identifier and the user real-name information correspond one-to-one; the server includes: a receiving module, used to obtain the target user real-name information from the application side, the target user real-name information includes the user real-name information of the target user; and, used to receive the target resource account information sent by the application side, the target resource account information includes the resource account information of the target user; a binding module, used to bind the target resource account information to the target identifier when the server has user real-name information consistent with the target user real-name information, the target identifier includes the primary identifier in the server that has a corresponding relationship with the target user real-name information.

[0008] In a fourth aspect, an embodiment of the present application provides an application device, comprising: a receiving module, used to obtain target user real-name information and target resource account information, the target user real-name information includes the user real-name information of the target user, and the target resource account information includes the resource account information of the target user; a sending module, used to send the target user real-name information to a cloud server, so that the cloud server can query and obtain a primary identifier having a corresponding relationship with the target user real-name information, the cloud server stores the primary identifier and user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one-to-one; and, used to send the target resource account information to the cloud server, so that the cloud server can bind the target resource account information with the primary identifier having a corresponding relationship with the target user real-name information.

[0009] In a fifth aspect, an embodiment of the present application provides a server, comprising a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the resource account binding method in the first aspect is implemented.

[0010] In a sixth aspect, an embodiment of the present application provides an application device, including a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the resource account binding method in the second aspect is implemented.

[0011] In a seventh aspect, an embodiment of the present application provides a resource account binding system, comprising the server in the fifth aspect and the application device in the sixth aspect.

[0012] In an eighth aspect, an embodiment of the present application provides a computer storage medium having computer program instructions stored thereon, and when the computer program instructions are executed by a processor, the resource account binding method in the first aspect or the resource account binding method in the second aspect is implemented.

[0013] The embodiment of the present application provides a resource account binding method, server, device, system and storage medium, wherein a cloud server stores a primary identifier and user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one by one. The primary identifier corresponding to the user real-name information of the same user is the same. The cloud server can obtain the target user real-name information from the application side, and receive the target resource account information sent by the application side. In the case where the target user real-name information exists in the primary identifier and user real-name information having a corresponding relationship stored in the cloud server, the target resource account information is bound to the target identifier to complete the binding of the resource account represented by the target resource account information of the target user and the target user represented by the target identifier. In the case where the user uses multiple applications, the resource account information and the primary identifier bound in the cloud server are shared by multiple applications. For a resource account represented by one resource account information, the user only needs to perform one binding operation, thereby reducing the number of binding operations of the user and simplifying the binding operation when the user uses multiple applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0015] Figure 1 A schematic diagram of an embodiment of a resource account binding system applied to the resource account binding method provided in an embodiment of the present application;

[0016] Figure 2 A flowchart of an embodiment of the resource account binding method provided in the first aspect of the present application;

[0017] Figure 3 A flowchart of another embodiment of the resource account binding method provided in the first aspect of the present application;

[0018] Figure 4 A flowchart of another embodiment of the resource account binding method provided in the first aspect of the present application;

[0019] Figure 5 A flowchart of another embodiment of the resource account binding method provided in the first aspect of the present application;

[0020] Figure 6 A flowchart of an embodiment of a resource account binding method provided in the second aspect of the present application;

[0021] Figure 7 A flowchart of another embodiment of the resource account binding method provided in the second aspect of the present application;

[0022] Figure 8 A flowchart of another embodiment of the resource account binding method provided in the second aspect of the present application;

[0023] Fig. 9 A flowchart of an embodiment of a resource account binding method applied to a resource account binding system provided by the present application;

[0024] Fig.10 A schematic diagram of the structure of an embodiment of a server provided in the third aspect of the present application;

[0025] Fig.11 A schematic diagram of the structure of another embodiment of the server provided in the third aspect of the present application;

[0026] Fig.12 A schematic structural diagram of another embodiment of the server provided in the third aspect of the present application;

[0027] Fig.13 A schematic diagram of the structure of an embodiment of an application device provided in the fourth aspect of the present application;

[0028] Fig.14 A schematic structural diagram of another embodiment of the application device provided in the fourth aspect of the present application;

[0029] Fig.15 A schematic structural diagram of another embodiment of the application device provided in the fourth aspect of the present application;

[0030] Fig.16 A schematic diagram of the structure of an embodiment of a server provided in the fifth aspect of the present application. DETAILED DESCRIPTION

[0031] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

[0032] With the development of network technology and payment technology, payment can be made through various applications. When a user has multiple resource accounts, the user can choose one of the resource accounts to make a payment. Users can use different resource accounts for different payments, or they can use the same resource account, which is not limited here. In order to facilitate payment, users can bind their resource accounts in the application. Due to the different resource institutions and merchants involved in the payment business, users need to use different applications. Different applications each have their own user system. When a user switches to different applications, if a resource account needs to be bound, the resource account needs to be bound in each application used, resulting in a cumbersome binding operation. For example, the resource account is a bank card, and the number of applications used by user A1 is N1. User A1 needs to bind M1 bank cards in each application, so user A1 needs to perform N1×M1 binding operations.

[0033] In order to solve the problem of cumbersome binding operations mentioned above, the embodiments of the present application provide a resource account binding method, server, device, system and storage medium, which can reduce binding operations and improve the convenience and speed of user resource account binding.

[0034] The resource account binding method provided in the embodiment of the present application can be applied to the scenario of managing resource accounts and using resource accounts for payment. Figure 1 A schematic diagram of an embodiment of a resource account binding system applied by the resource account binding method provided in the embodiment of the present application. Figure 1As shown, the resource account binding system may include an application side 11 and a cloud server 12. The application side may include a user terminal 111 and / or an application background server 112 on which an application is installed. In some cases, the resource account binding system may also include an account opening institution server 13. The user terminal 111 may communicate and interact with one or more application background servers 112. One or more application background servers 112 may communicate and interact with the cloud server 12, that is, multiple application sides 11 may share one cloud server 12. The application side 11 may also communicate and interact with the account opening institution server 13.

[0035] The resource account can be managed through the application side 11 and the cloud server 12, such as binding, unbinding, viewing, etc. The resource account can be paid through the application side 11, the cloud server 12 and the account opening institution server 13.

[0036] A first aspect of the present application provides a resource account binding method, which can be applied to a cloud server, that is, the resource account binding method can be executed by the cloud server. Figure 2 This is a flow chart of an embodiment of the resource account binding method provided in the first aspect of the present application. Figure 2 As shown, the resource account binding method may include steps S201 to S203.

[0037] In step S201, the target user's real-name information is obtained from the application side.

[0038] The target user real-name information includes the target user's user real-name information. The target user can be any user and is not limited here. The user real-name information corresponds to the user one-to-one. The user real-name information is unique to the user, and the user real-name information of different users is different.

[0039] The application side may include a user terminal with an application installed, or may include a backend server of an application installed on a user terminal, or may include a user terminal with an application installed and a backend server of an application. The application side may obtain information input by the user or stored in the user terminal through the application. The cloud server obtains the target user's real-name information from the application side, which may be obtained from the user terminal, such as the user's real-name information input into the user terminal during the registration or login process in the application.

[0040] In some examples, the user's real-name information may include an ID number.

[0041] In other examples, user real-name information may also include, but is not limited to, one or more of user name, user ID type, and mobile phone number, and may be set according to work scenarios and work requirements.

[0042] For example, the user real-name information includes the ID number. For another example, the user real-name information includes the ID number and the mobile phone number. For another example, the user real-name information includes the ID number, the user name, the user ID type and the mobile phone number.

[0043] In step S202, the target resource account information sent by the application side is received.

[0044] The target resource account information includes the resource account information of the target user. Specifically, the target resource account information is the resource account information of the resource account that needs to be bound to the target user. The target resource account information can be obtained by the application side. The resource account information can be used to characterize the resource account, such as the resource account information can include the resource account identifier.

[0045] In some examples, the resource account information may include but is not limited to bank card identification information. The bank card identification information may represent a bank card, such as the bank card identification information may include a bank card number, and may also include cardholder bank information, etc., which is not limited here.

[0046] In step S203, when the cloud server has user real-name information that is consistent with the target user real-name information, the target resource account information is bound to the target identifier.

[0047] The cloud server stores a primary identifier and user real-name information with a corresponding relationship, and the primary identifier corresponds to the user real-name information one by one. The primary identifier is used to identify the user real-name information. The user real-name information is unique, and correspondingly, the primary identifier is also unique. The primary identifier may include numbers, letters or other symbols, and the form of the primary identifier is not limited here.

[0048] The cloud server has user real-name information that is consistent with the target user's real-name information, indicating that the target user has registered with the cloud server and activated the cloud server binding service. The target user's user real-name information can be found in the cloud server, so the target resource account information can be directly bound to the target identifier. The target identifier includes a primary identifier in the cloud server that has a corresponding relationship with the target user's real-name information. The target user's real-name information can represent the target user, and the target identifier has a corresponding relationship with the target user's real-name information. Correspondingly, the target identifier can represent the target user. Binding the target resource account information to the target identifier is to bind the resource account represented by the target resource account information to the target user.

[0049] When a user uses multiple applications, the resource account represented by the resource account information bound by the user in one application does not need to be bound again in other applications. For example, the resource account is a bank card, and the number of applications used by user A1 is N1. To complete the binding of M1 bank cards, user A1 only needs to perform M1 binding operations in N1 applications.

[0050] In an embodiment of the present application, the cloud server stores a primary identifier and user real-name information with a corresponding relationship, and the primary identifier corresponds to the user real-name information one-to-one. The primary identifier corresponding to the user real-name information of the same user is the same. The cloud server can obtain the target user real-name information from the application side, and receive the target resource account information sent by the application side. In the case where the target user real-name information exists in the primary identifier and user real-name information with a corresponding relationship stored in the cloud server, the target resource account information is bound to the target identifier to complete the binding of the resource account represented by the target resource account information of the target user and the target user represented by the target identifier. In the case where the user uses multiple applications, the resource account information and primary identifier bound in the cloud server are shared by multiple applications. For a resource account represented by one resource account information, the user only needs to perform one binding operation, thereby reducing the number of binding operations for the user and simplifying the binding operation when the user uses multiple applications.

[0051] Figure 3 This is a flowchart of another embodiment of the resource account binding method provided in the first aspect of the present application. Figure 3 and Figure 2 The difference is that Figure 3 The resource account binding method shown may further include steps S204 to S206.

[0052] In step S204, when the cloud server does not have user real-name information that is consistent with the target user real-name information, a primary identifier is allocated to the target user real-name information.

[0053] The cloud server does not have the same user real-name information as the target user's real-name information, which means that the target user has not yet registered on the cloud server and needs to complete the target user's registration. Allocating a primary identifier to the target user's real-name information is equivalent to allocating a primary identifier to the target user.

[0054] In step S205, a correspondence between the target user real-name information and the primary identifier assigned to the target user real-name information is established, and the target user real-name information and the primary identifier assigned to the target user real-name information are stored.

[0055] The cloud server stores the corresponding target user real-name information and the primary identifier assigned to the target user real-name information, so that when the target user performs a binding operation again in the future, the primary identifier assigned to the target user real-name information can be queried in the cloud server.

[0056] In step S206, the target resource account information is bound to the primary identifier assigned to the target user real-name information.

[0057] The above steps S204 and S205 complete the registration of the target user in the cloud server. After the registration is completed, the target resource account needs to be bound to the primary identifier assigned to the target user's real-name information, that is, the binding of the target user's resource account and the target user is completed.

[0058] The cloud server does not have user real-name information that is consistent with the target user's real-name information in the above embodiment, indicating that the target user is not registered in the cloud server. In this embodiment, the target user can be registered in the cloud server and the resource account can be bound to the target user.

[0059] Figure 4 This is a flowchart of another embodiment of the resource account binding method provided in the first aspect of the present application. Figure 4 and Figure 2 The difference is that Figure 4 The resource account binding method shown may further include step S207 and step S208.

[0060] In step S207, a slave identifier is allocated to the resource account information obtained from the application side, and a corresponding relationship between the slave identifier and the resource account information is established.

[0061] In the embodiment of the present application, the application side uses the slave identifier assigned to the resource account information to make payment during the payment process. The cloud server can assign the slave identifier to the resource account information before payment.

[0062] The slave identifier can be used to identify resource account information, that is, it can be used to identify the resource account. Therefore, the slave identifier can be used for payment. Specifically, the resource account corresponding to the slave identifier can be located according to the slave identifier, so that the resource account corresponding to the slave identifier can be used for payment. Since the resource account and the resource account information corresponding to the resource account are unique, the slave identifier is also unique accordingly.

[0063] In some examples, no matter how many times payment is made, only one slave identifier may be assigned to the same resource account information. The same slave identifier corresponding to the resource account information is used in multiple payments, that is, a corresponding slave identifier is assigned to each resource account information. In the case where a resource account needs to be used for multiple payments in the future, each payment can always be made using the slave identifier assigned to the resource account.

[0064] In other examples, multiple payments are made, and each payment is assigned a slave identifier to the same resource account. Multiple payments correspond to the allocation of multiple slave identifiers to the resource account information, and the multiple slave identifiers may be different. In each payment, a slave identifier corresponding to the resource account information in this payment is used for payment. In this example, the correspondence between the slave identifier and the resource account information may not be established.

[0065] Specifically, the cloud server can receive the real-name information of the target user sent by the application side; search for the target identifier based on the real-name information of the target user; send the resource account information bound to the target identifier to the application side; receive the selected resource account information sent by the application side, and assign a slave identifier to the selected resource account information.

[0066] That is, the cloud server can assign a slave identifier to the resource account information corresponding to the resource account selected by the user. After the cloud server finds the target identifier, it can send all the resource account information bound to the target identifier to the application side in a list. The program background server can receive the selection instruction of the user terminal, obtain the resource account information selected by the selection instruction, and send the resource account information selected by the selection instruction to the cloud server. After receiving the selected resource account information, the cloud server can assign a slave identifier to the selected resource account information.

[0067] The cloud server can establish a correspondence between the slave identifier and the resource account information, so that in the subsequent payment process, the resource account information corresponding to the slave identifier used for payment can be found, and the resource account represented by the found resource account information can be used for payment.

[0068] In step S208, the slave identifier assigned to the resource account information is sent to the application side, so that the application side saves the slave identifier and uses the slave identifier for payment.

[0069] In the case where the application side includes a user terminal, the slave identifier can be saved to the user terminal. In the case where the application side includes an application background server, the slave identifier can be saved to the application background server. In the case where the application side includes a user terminal and an application background server, the slave identifier can be saved to the user terminal and / or the application background server, which is not limited here.

[0070] What the cloud server sends to the application side is the slave identifier assigned to the resource account information. That is, the application side saves the slave identifier but does not save the resource account information, thus avoiding resource account information leakage on the application side and reducing the risk of resource account information leakage.

[0071] Figure 5 This is a flowchart of another embodiment of the resource account binding method provided in the first aspect of the present application. Figure 5 and Figure 4 The difference is that Figure 5 The resource account binding method shown may further include steps S209 to S211.

[0072] In step S209, a payment message sent by the application side is received.

[0073] The payment message includes a target slave identifier. The target slave identifier is the slave identifier selected for payment, that is, the slave identifier used for this payment. The payment message sent by the application side can be specifically generated according to the payment message sent by the user terminal.

[0074] In step S210, the target resource account information is searched.

[0075] The target resource account information is the resource account information corresponding to the target slave identifier in the cloud server. The cloud server establishes the corresponding relationship between the slave identifier and the resource account information before payment, so that the resource account information corresponding to the target slave identifier, that is, the target resource account information, can be found.

[0076] In step S211, the target resource account information is sent to the application side, so that the application side completes the payment using the target resource account information.

[0077] The application side can use the target resource account information to interact with the account opening institution server to complete the payment process.

[0078] In an embodiment of the present application, the cloud server may provide the application side with resource account information corresponding to the slave identifier sent by the application side during the payment process, thereby ensuring that the application side can complete the payment in the resource account represented by the resource account information.

[0079] A second aspect of the present application provides a resource account binding method, which can be applied to the application side in the above embodiment, that is, the resource account binding method can be executed by the application side. Figure 6 This is a flow chart of an embodiment of the resource account binding method provided in the second aspect of the present application. Figure 6 As shown, the resource account binding method may include steps S301 to S303.

[0080] In step S301, the target user real-name information and the target resource account information are obtained.

[0081] The target user real-name information includes the target user's real-name information. In some examples, when the application side includes a user terminal, the user terminal can obtain the target user's real-name information from the user's input. In other examples, when the application side includes an application background server, the application background server can obtain the target user's real-name information from the user terminal.

[0082] For example, the application side can obtain the target user's real-name information when the target user registers through the application in the user terminal; it can also send a prompt message during the resource account binding process to prompt the target user to enter the target user's real-name information into the user terminal, which is not limited here.

[0083] The target resource account information includes the resource account information of the target user. In some examples, when the application side includes a user terminal, the user terminal can obtain the resource account information from the user's input or push message. In other examples, the application side can obtain the target resource account information from the user terminal.

[0084] For example, the target resource account information acquired by the application side may be the target resource account information input by the target user into the user terminal, or may be the pushed target resource account information received by the application side, which is not limited here.

[0085] The application side can obtain the target user real-name information and the target resource account information separately in batches, and is not required to obtain the target user real-name information and the target resource account information at the same time, which is not limited here.

[0086] In some examples, the user's real-name information may include an ID number.

[0087] In other examples, user real-name information may also include, but is not limited to, one or more of user name, user ID type, and mobile phone number, and may be set according to work scenarios and work requirements.

[0088] In some examples, resource account information may include, but is not limited to, bank card identification information.

[0089] In step S302, the real-name information of the target user is sent to the cloud server, so that the cloud server queries and obtains a primary identifier that has a corresponding relationship with the real-name information of the target user.

[0090] The cloud server stores the corresponding main identifier and user real name information, and the main identifier corresponds to the user real name information. The cloud server queries and obtains the specific content of the main identifier corresponding to the target user real name information, which can be referred to the relevant description in the above embodiment and will not be repeated here.

[0091] In some examples, after obtaining the real-name information of the target user, the application side can authenticate the real-name information of the target user, and send the real-name information of the target user to the cloud server if the authentication is successful and the target user is authorized.

[0092] Specifically, the application side can authenticate the target user's real-name information by itself; it can also call the user's real-name information in other databases to authenticate the target user's real-name information; it can also call other servers to assist in completing the authentication of the target user's real-name information, which is not limited here. The application side will only send the target user's real-name information to the cloud server if the target user authorizes the target user's real-name information, that is, it allows the use of the cloud server binding service.

[0093] In step S303, the target resource account information is sent to the cloud server so that the cloud server binds the target resource account information with a primary identifier that has a corresponding relationship with the target user real-name information.

[0094] The specific content of the cloud server binding the target resource account information with the main identifier corresponding to the target user real-name information can be found in the relevant description in the above embodiment, which will not be repeated here.

[0095] In an embodiment of the present application, the application side provides the acquired target user real-name information and target resource account information to the cloud server, so that the cloud server can query the primary identifier corresponding to the target user real-name information, and bind the target resource account information to the primary identifier corresponding to the target user real-name information, so as to complete the binding of the resource account represented by the target resource account information of the target user and the target user represented by the target identifier in the cloud server. In the case where the user uses multiple applications, the resource account information and primary identifier bound in the cloud server are shared by multiple applications. Since the user real-name information is unique, for a resource account represented by a resource account information, the user only needs to perform one binding operation, thereby reducing the number of binding operations of the user and simplifying the binding operation when the user uses multiple applications.

[0096] Figure 7 This is a flowchart of another embodiment of the resource account binding method provided in the second aspect of the present application. Figure 7 and Figure 6 The difference is that Figure 7The resource account binding method shown may further include steps S304 to S309.

[0097] In step S304, the target user's real-name information is sent to the cloud server.

[0098] The user can select the resource account to be used for payment, and the application side can interact with the cloud server to allocate a slave identifier for payment to the resource account information corresponding to the resource account. The application side sends the target user's real-name information to the cloud server, so that the cloud server can query and obtain the master identifier corresponding to the target real-name information, and obtain all resource account information bound to the master identifier corresponding to the target real-name information.

[0099] In step S305, resource account information bound to a primary identifier corresponding to the real-name information of the target user is received.

[0100] The cloud server stores resource account information bound to a primary identifier that corresponds to the real-name information of the target user. The application side can receive the resource account information bound to the primary identifier that corresponds to the real-name information of the target user sent by the cloud server. In some examples, the resource account information bound to the primary identifier that corresponds to the real-name information of the target user received by the application side can be a list, and the list includes all resource account information bound to the primary identifier that corresponds to the real-name information of the target user.

[0101] The application side may generate display configuration information according to the resource account information bound to the primary identifier that has a corresponding relationship with the real-name information of the target user. The display configuration information is used to instruct the user terminal to display the resource account information bound to the primary identifier that has a corresponding relationship with the real-name information of the target user. In the case where the application side includes an application background server, the application background server may send the display configuration information to the user terminal so that the user terminal displays the resource account information bound to the primary identifier that has a corresponding relationship with the real-name information of the target user. In the case where the application side includes a user terminal, the user terminal may display the resource account information bound to the primary identifier that has a corresponding relationship with the real-name information of the target user according to the generated display configuration information.

[0102] In step S306, a selection instruction is received.

[0103] In the case where the application side includes a user terminal, the user terminal receives a selection instruction input by the user. In the case where the application side includes an application background server, the user terminal receives the user input, generates a selection instruction based on the user input, and sends the selection instruction to the application background server. The selection instruction is used to select resource account information. For example, the resource account information bound to the primary identifier having a corresponding relationship with the target user's real-name information includes resource account information M1, resource account information M2, and resource account information M3, and the selection instruction can select one of the resource account information M1, resource account information M2, and resource account information M3.

[0104] In step S307, the resource account information selected by the selection instruction is sent to the cloud server.

[0105] The application sends the resource account information selected by the selection instruction to the cloud server, so that the cloud server allocates a slave identifier to the resource account information selected by the selection instruction. When payment is made in the resource account represented by the resource account information selected by the selection instruction, the slave identifier can be used for payment.

[0106] In step S308, a slave identifier assigned by the cloud server to the resource account information is received.

[0107] In some examples, the application side receives a slave identifier assigned by the cloud server to the resource account information selected for the selected instruction.

[0108] In step S309, the slave identifier is stored.

[0109] In the case where the application side includes a user terminal, the user terminal may store the slave identifier. In the case where the application side includes an application background server, the application background server may store the slave identifier. In the case where the application side includes a user terminal and an application background server, the user terminal and / or the application background server may store the slave identifier.

[0110] The application side stores the slave identifier instead of the resource account information, thereby preventing the resource account information from being leaked from the application side and reducing the risk of resource account information leakage. In the subsequent payment process, the slave identifier is used for payment.

[0111] Figure 8 This is a flowchart of another embodiment of the resource account binding method provided in the second aspect of the present application. Figure 8 and Figure 7 The difference is that Figure 8 The resource account binding method shown may further include steps S310 to S313. In step S310, a payment message is generated.

[0112] The payment message includes a target slave identifier, which is a slave identifier selected for payment.

[0113] In the case where the application side includes an application background server, the application background server may receive a payment request initiated by a user terminal and generate a payment message according to the payment request. The payment request is used to indicate the target slave identifier. That is, the payment request may include information for indicating the target slave identifier. For example, the user terminal receives an input operation performed by a target user on the user terminal, selects one of the resource accounts bound to the target user, and initiates a payment request for indicating payment of the selected slave identifier.

[0114] In step S311, a payment message is sent to the cloud server.

[0115] The application sends a payment message to the cloud server so that the cloud server obtains the target slave identifier and can query the resource account information corresponding to the target slave identifier in the cloud server.

[0116] In some examples, the application side may authenticate the target user's real-name information; if the authentication is successful and the target user is authorized, the target user's real-name information is sent to the cloud server.

[0117] Specifically, the application side can authenticate the target user's real-name information by itself; it can also call the user's real-name information in other databases to authenticate the target user's real-name information; it can also call other servers to assist in completing the authentication of the target user's real-name information, which is not limited here. The application side will only send the target user's real-name information to the cloud server if the target user authorizes the target user's real-name information, that is, it allows the use of the cloud server binding service.

[0118] In step S312, the target resource account information sent by the cloud server is received.

[0119] The target resource account information is resource account information that has a corresponding relationship with the target slave identifier in the cloud server.

[0120] In step S313, the target resource account information is sent to the account opening institution server so that the account opening institution server completes the payment according to the target resource account information.

[0121] The application sends the target resource account information to the account opening institution server, so that the account opening institution server can deduct the amount paid in the resource account represented by the target resource account information.

[0122] The application side stores the slave identifier, and the application side obtains the resource account information corresponding to the slave identifier selected for payment through interaction with the cloud server, thereby completing the payment using the resource account information.

[0123] There is no limit to the number of application sides in the resource account binding method applied to the cloud server or application side. The application side in the resource account binding method in the above embodiment can be the backend server of any application, and multiple application sides can jointly implement the resource account binding method with the cloud server.

[0124] For example, the application side involved in steps S201 to S206 may be the first application side, that is, the first application; the application side involved in steps S207 and S208 may be the second application side, that is, the second application; the application side in steps S209 to S211 may be the third application side, that is, the third application. Multiple application sides realize the sharing of user and resource account binding through the cloud server.

[0125] For another example, the application side involved in steps S301 to S303 may be the first application side, that is, the first application; the application side involved in steps S304 to S309 may be the second application side, that is, the second application; the application side in steps S310 to S313 may be the third application side, that is, the third application. Multiple application sides realize the sharing of user and resource account binding through the cloud server.

[0126] The type of application corresponding to the application side is not limited here. For example, when the resource account is a bank card, the application side can be the backend server of a bank application, the backend server of a mini-program portal, the backend server of a merchant application, the backend server of an institution application, etc.

[0127] The identification formats of the master identification and the slave identification are not limited here. For example, the slave identification may be a data string consisting of 13 to 19 digits and conforming to the basic verification rules of the resource account.

[0128] The following is an explanation of the process of the resource account binding method provided in the embodiment of the present application from the perspective of the resource account binding system. The resource account binding system may include the cloud server and the application side in the above embodiment. The resource account binding system may also include the account opening institution server in the above embodiment, etc., which is not limited here. Here, the application side includes the application background server and the user terminal as an example.

[0129] Fig. 9This is a flow chart of an embodiment of a resource account binding method applied to a resource account binding system provided by the present application. Fig. 9 As shown, the resource binding method may include steps S401 to S418.

[0130] In step S401, the application background server obtains the target user real-name information and the target resource account information from the user terminal.

[0131] In step S402, the cloud server obtains the target user's real-name information from the application backend server.

[0132] In step S403, the cloud server receives the target resource account information sent by the application backend server.

[0133] In step S404, when the cloud server does not have user real-name information that is consistent with the target user real-name information, the cloud server allocates a primary identifier for the target user real-name information.

[0134] In step S405, the cloud server establishes a correspondence between the target user's real-name information and the primary identifier assigned to the target user's real-name information, and stores the target user's real-name information and the primary identifier assigned to the target user's real-name information.

[0135] In step S406, the cloud server binds the target resource account information with the primary identifier assigned to the target user real-name information.

[0136] In step S407, when the cloud server has user real-name information that is consistent with the target user real-name information, the cloud server binds the target resource account information with the target identifier.

[0137] In step S408, the cloud server assigns a slave identifier to the resource account information obtained from the application backend server, and establishes a corresponding relationship between the slave identifier and the resource account information.

[0138] In step S409, the cloud server sends the slave identifier assigned to the resource account information to the application backend server.

[0139] The slave identifier may be stored in a user terminal and / or a program backend server, which is not limited here.

[0140] In step S410, the application backend server receives a payment request initiated by a user terminal.

[0141] In step S411, the application backend server generates a payment message according to the payment request.

[0142] In step S412, the application backend server sends a payment message to the cloud server.

[0143] In step S413, the cloud server queries and obtains target resource account information corresponding to the target slave identifier.

[0144] In step S414, the cloud server sends the target resource account information to the application backend server.

[0145] In step S415, the application backend server sends the target resource account information to the account opening institution server.

[0146] In step S416, the account opening institution server uses the target resource account information to make payment.

[0147] In step S417, the application background server receives the payment result information sent by the switch mechanism server. The payment result information is used to represent the payment result, such as payment success, payment failure, payment amount, etc., which is not limited here.

[0148] In step S418, the application backend server sends payment result information to the user terminal.

[0149] The specific contents of the above steps S401 to S418 can be found in the relevant descriptions in the above embodiments, which will not be repeated here.

[0150] The resource account binding method applied to the resource account binding system may also include other steps. The specific contents of the other steps can be found in the relevant descriptions in the above embodiments, which will not be repeated here. In the resource account binding system, the resource processing method in the embodiment of the present application can be used to realize the sharing of the binding of users and resource accounts in the cloud server by multiple applications, thereby reducing the user's binding operations on resource accounts.

[0151] The third aspect of the present application provides a server, which can be regarded as the cloud server in the above embodiment. In the embodiment of the present application, the server stores a primary identifier and user real-name information with a corresponding relationship, and the primary identifier corresponds to the user real-name information one by one. Fig.10 This is a schematic diagram of the structure of an embodiment of a server provided in the third aspect of the present application. Fig.10 As shown, the server 500 may include a receiving module 501 and a binding module 502 .

[0152] The receiving module 501 can be used to obtain the target user real-name information from the application side, including the target user's user real-name information; and to receive the target resource account information sent by the application side, including the target user's resource account information.

[0153] In some examples, the user's real-name information may include an ID number.

[0154] In other examples, the user real-name information may also include one or more of the user name, user ID type, and mobile phone number.

[0155] In some examples, the resource account information includes bank card identification information.

[0156] The binding module 502 can be used to bind the target resource account information with the target identifier when the server has user real-name information consistent with the target user real-name information. The target identifier includes a primary identifier in the server that has a corresponding relationship with the target user real-name information.

[0157] In an embodiment of the present application, the server stores a primary identifier and user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one-to-one. The primary identifier corresponding to the user real-name information of the same user is the same. The server can obtain the target user real-name information from the application side, and receive the target resource account information sent by the application side. In the case where the target user real-name information exists in the primary identifier and user real-name information having a corresponding relationship stored in the server, the target resource account information is bound to the target identifier to complete the binding of the resource account represented by the target resource account information of the target user and the target user represented by the target identifier. In the case where the user uses multiple applications, the resource account information and the primary identifier bound in the server are shared by multiple applications. For a resource account represented by one resource account information, the user only needs to perform one binding operation, thereby reducing the number of binding operations for the user and simplifying the binding operation when the user uses multiple applications.

[0158] Fig.11 A schematic diagram of the structure of another embodiment of the server provided in the third aspect of the present application. Fig.11 and Fig.10 The difference is that Fig.11 The server 500 shown may also include a first identification allocation module 503 , a relationship establishment module 504 and a storage module 505 .

[0159] The first identifier allocation module 503 may be configured to allocate a primary identifier to the target user real-name information when the server does not have user real-name information that is consistent with the target user real-name information.

[0160] The relationship establishing module 504 may be used to establish a corresponding relationship between the target user's real-name information and the primary identifier assigned to the target user's real-name information.

[0161] The storage module 505 may be used to store the target user's real-name information and the primary identifier assigned to the target user's real-name information.

[0162] The binding module 502 may be used to bind the target resource account information with the primary identifier assigned to the target user real-name information.

[0163] Fig.12 A schematic structural diagram of another embodiment of the server provided in the third aspect of the present application. Fig.12 and Fig.10 The difference is that Fig.12 The server 500 shown may further include a second identification allocation module 506 , a sending module 507 and a query module 508 .

[0164] The second identifier allocation module 506 may be used to allocate a slave identifier to the resource account information obtained from the application side, and establish a corresponding relationship between the slave identifier and the resource account information.

[0165] The sending module 507 may be used to send the slave identifier assigned to the resource account information to the application side, so that the application side saves the slave identifier and uses the slave identifier for payment.

[0166] In some examples, the above-mentioned second identifier allocation module 506 can be specifically used to: receive the real-name information of the target user sent by the application side; search for the target identifier based on the real-name information of the target user; send the resource account information bound to the target identifier to the application side; receive the selected resource account information sent by the application side, and allocate a slave identifier to the selected resource account information.

[0167] The above-mentioned receiving module 501 can also be used to receive the payment message sent by the application side.

[0168] The payment message includes a target slave identifier. The target slave identifier is a slave identifier selected for payment;

[0169] The query module 508 may be used to search for target resource account information.

[0170] The target resource account information is resource account information that has a corresponding relationship with the target slave identifier in the server.

[0171] The sending module 507 may also be used to send the target resource account information to the application side, so that the application side can complete the payment using the target resource account information.

[0172] A fourth aspect of the present application provides an application device, which can be regarded as the application side in the above-mentioned embodiment, and specifically can be the user terminal and / or application background server in the above-mentioned embodiment. Fig.13 This is a schematic diagram of the structure of an embodiment of the application device provided in the fourth aspect of the present application. Fig.13 As shown, the application device 600 may include a receiving module 601 and a sending module 602 .

[0173] The receiving module 601 may be used to obtain target user real-name information and target resource account information, where the target user real-name information includes the target user's user real-name information, and the target resource account information includes the target user's resource account information;

[0174] The sending module 602 can be used to send the target user's real-name information to the cloud server, so that the cloud server can query and obtain a primary identifier that corresponds to the target user's real-name information. The cloud server stores the primary identifier and user real-name information that have a corresponding relationship, and the primary identifier corresponds to the user real-name information one by one; and, to send the target resource account information to the cloud server, so that the cloud server can bind the target resource account information to the primary identifier that has a corresponding relationship with the target user's real-name information.

[0175] In some examples, the user's real-name information may include an ID number.

[0176] In other examples, the user real-name information may also include one or more of the user name, user ID type, and mobile phone number.

[0177] In some examples, the resource account information includes bank card identification information.

[0178] In an embodiment of the present application, the application device provides the acquired target user real-name information and target resource account information to the cloud server, so that the cloud server can query the primary identifier corresponding to the target user real-name information, and bind the target resource account information to the primary identifier corresponding to the target user real-name information, so as to complete the binding of the resource account represented by the target resource account information of the target user and the target user represented by the target identifier in the cloud server. In the case where the user uses multiple applications, the resource account information and primary identifier bound in the cloud server are shared by multiple applications. Since the user real-name information is unique, for a resource account represented by a resource account information, the user only needs to perform one binding operation, thereby reducing the number of binding operations of the user and simplifying the binding operation when the user uses multiple applications.

[0179] Fig.14 A schematic structural diagram of another embodiment of the application device provided in the fourth aspect of the present application. Fig.14 and Fig.13 The difference is that Fig.14 The illustrated application device 600 may also include a storage module 603 .

[0180] The receiving module 601 may also be used to receive a slave identifier assigned by the cloud server to the resource account information.

[0181] The storage module 603 may be used to store the slave identifier.

[0182] In some examples, the sending module 602 may also be used to send the target user's real-name information to a cloud server.

[0183] The receiving module 601 can also be used to receive resource account information bound to a primary identifier that corresponds to the target user's real-name information; and to receive a selection instruction, where the selection instruction is used to select the resource account information.

[0184] The sending module 602 may also be used to send the resource account information selected by the selection instruction to the cloud server.

[0185] Fig.15 A structural diagram of another embodiment of the application device provided in the fourth aspect of the present application. Fig.15 and Fig.14 The difference is that Fig.15 The illustrated application device 600 may also include a generation module 604 .

[0186] The generation module 604 may be used to generate a payment message.

[0187] The payment message includes a target slave identifier, which is a slave identifier selected for payment.

[0188] The sending module 602 may also be used to send payment messages to a cloud server.

[0189] The receiving module 601 may also be used to receive target resource account information sent by the cloud server.

[0190] The target resource account information is resource account information that has a corresponding relationship with the target slave identifier in the cloud server.

[0191] The sending module 602 is also used to send the target resource account information to the account opening institution server, so that the account opening institution server completes the payment according to the target resource account information.

[0192] In some examples, the sending module 602 may also be used to authenticate the real-name information of the target user; if the authentication is successful and the target user is authorized, the real-name information of the target user is sent to the cloud server.

[0193] The fifth aspect of the present application provides a server, which can be regarded as the cloud server in the above embodiment. Fig.16 This is a schematic diagram of the structure of an embodiment of a server provided in the fifth aspect of the present application. Fig.16 As shown, the server 700 includes a memory 701 , a processor 702 , and a computer program stored in the memory 701 and executable on the processor 702 .

[0194] In an example, the processor 702 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 the embodiments of the present application.

[0195] The memory 701 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 701 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these.

[0196] The memory may include a read-only memory (ROM), a random access memory (RAM), a disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the model publishing method in the distributed system according to the present application.

[0197] The processor 702 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 701, so as to implement the resource account binding method in the first aspect of the above embodiment.

[0198] In one example, the server 700 may further include a communication interface 703 and a bus 704. Fig.16 As shown, the memory 701, the processor 702, and the communication interface 703 are connected via a bus 704 and communicate with each other.

[0199] The communication interface 703 is mainly used to realize the communication between the modules, devices, units and / or equipment in the embodiment of the present application. The communication interface 703 can also be used to access input devices and / or output devices.

[0200] The bus 704 includes hardware, software, or both, coupling the components of the server 700 to each other. By way of example and not limitation, the bus 704 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a Memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of the above. Where appropriate, the bus 704 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.

[0201] The sixth aspect of the present application also provides an application device, which can be regarded as the application side in the above embodiment, and specifically may include a user terminal and / or an application background server in the above embodiment. The application device may include a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the resource account binding method provided in the second aspect above.

[0202] In some examples, the application device may further include a communication interface and a bus. The memory, the processor, and the communication interface may be connected via the bus and communicate with each other.

[0203] For specific descriptions of the memory, processor, computer program, communication interface, bus, etc. in the application device, please refer to the relevant descriptions of the memory, processor, computer program, communication interface, bus, etc. in the server in the fifth aspect, which will not be repeated here.

[0204] The seventh aspect of the present application provides a resource account binding system, which may include the server provided in the fifth aspect and the application device provided in the sixth aspect. The specific contents of the server provided in the fifth aspect and the application device provided in the sixth aspect can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0205] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the resource account binding method of the first aspect or the resource account binding method of the second aspect in the above-mentioned embodiment can be implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (Read-Only Memory, referred to as ROM), a random access memory (Random Access Memory, referred to as RAM), a disk or an optical disk, etc., which is not limited here.

[0206] It should be clear that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For server embodiments, application device embodiments, system embodiments, and computer-readable storage medium embodiments, the relevant parts can refer to the description part of the method embodiment. The present application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application. In addition, for the sake of brevity, a detailed description of known method technologies is omitted here.

[0207] The above reference is according to the method of the embodiment of the present application, the flow chart of the device (system) and the computer program product and / or the block diagram described various aspects of the present application.It should be understood that each square box in the flow chart and / or the block diagram and the combination of each square box in the flow chart and / or the block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the realization of the function / action specified in one or more square boxes of the flow chart and / or the block diagram.Such a processor can 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 can also be understood that each square box in the block diagram and / or the flow chart and the combination of the square boxes in the block diagram and / or the flow chart can also be realized by the dedicated hardware that performs the specified function or action, or can be realized by the combination of dedicated hardware and computer instructions.

[0208] Those skilled in the art should understand that the above embodiments are exemplary rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on the study of the drawings, the specification and the claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other devices or steps; the quantifier "one" does not exclude multiple; the terms "first" and "second" are used to indicate names rather than to indicate any specific order. Any figure marks in the claims should not be understood as limiting the scope of protection. The functions of multiple parts appearing in the claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A resource account binding method, characterized in that: Applied to a cloud server, the cloud server stores a primary identifier and user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one by one; The method comprises: Acquire the target user real-name information from the first application side, wherein the target user real-name information includes the user real-name information of the target user; Receiving target resource account information sent by the first application side, the target resource account information including resource account information of the target user; In the case where the cloud server has user real-name information that is consistent with the target user real-name information, the target resource account information is bound to a target identifier, the target identifier includes the primary identifier in the cloud server that has a corresponding relationship with the target user real-name information, the resource account information and the primary identifier bound in the cloud server are shared by multiple applications, different applications each have their own user system, and multiple applications are installed on the user terminal; Receiving a payment message and the target user's real-name information sent by the second application side; Query the target resource account information and send it to the second application side, so that the second application side sends the target resource account information to the account opening institution server, so that the account opening institution server completes the payment according to the target resource account information; The number of applications used by the target user is N1. To complete the binding of M1 resource accounts, the target user only needs to perform M1 binding operations in the N1 applications.

2. The method according to claim 1, characterized in that After acquiring the target user's real name information from the first application side, the method further includes: In the case that the cloud server does not have the user real-name information that is consistent with the target user real-name information, assigning a primary identifier to the target user real-name information; Establishing a correspondence between the target user real-name information and the primary identifier assigned to the target user real-name information, and storing the target user real-name information and the primary identifier assigned to the target user real-name information; The target resource account information is bound to the primary identifier assigned to the target user real-name information.

3. The method according to claim 1, characterized in that Also includes: Assigning a slave identifier to the resource account information obtained from the application side, and establishing a corresponding relationship between the slave identifier and the resource account information; The slave identifier assigned to the resource account information is sent to the application side, so that the application side saves the slave identifier and uses the slave identifier for payment.

4. The method according to claim 3, characterized in that The step of allocating a slave identifier to the resource account information obtained from the application side includes: Receiving the target user real-name information sent by the application side; Searching for the target identifier according to the real-name information of the target user; Sending the resource account information bound to the target identifier to the application side; The selected resource account information sent by the application side is received, and the slave identifier is allocated to the selected resource account information.

5. The method according to claim 3, characterized in that: Also includes: receiving a payment message sent by the application side, wherein the payment message includes a target slave identifier, and the target slave identifier is the slave identifier selected for payment; Searching for target resource account information, where the target resource account information is the resource account information having a corresponding relationship with the target slave identifier in the cloud server; The target resource account information is sent to the application side so that the application side completes the payment using the target resource account information.

6. The method according to any one of claims 1 to 5, characterized in that The user real-name information includes the ID number; The user real-name information also includes one or more of the user name, user ID type, and mobile phone number.

7. The method according to any one of claims 1 to 5, characterized in that The resource account information includes bank card identification information.

8. A resource account binding method, characterized in that: Applied to an application side, the application side includes a first application side and a second application side, the method includes: The first application side acquires target user real-name information and target resource account information, wherein the target user real-name information includes the user real-name information of the target user, and the target resource account information includes the resource account information of the target user; The first application sends the target user real-name information to the cloud server, so that the cloud server queries and obtains a primary identifier corresponding to the target user real-name information, and the cloud server stores the primary identifier and the user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one by one; The first application sends the target resource account information to the cloud server, so that the cloud server binds the target resource account information with the primary identifier corresponding to the target user real-name information, the resource account information and the primary identifier bound in the cloud server are shared by multiple applications, different applications each have their own user system, and multiple applications are installed on the user terminal; The second application sends a payment message and the target user's real name information to the cloud server, so that the cloud server searches for the target resource account information; The second application side receives the target resource account information sent by the cloud server, and sends the target resource account information to the account opening institution server, so that the account opening institution server completes the payment according to the target resource account information; The number of applications used by the target user is N1. To complete the binding of M1 resource accounts, the target user only needs to perform M1 binding operations in the N1 applications.

9. The method according to claim 8, characterized in that Also includes: receiving a slave identifier assigned by the cloud server to the resource account information; The slave identification is stored.

10. The method according to claim 9, characterized in that Before receiving the slave identifier assigned by the cloud server to the resource account information, the method further includes: Sending the target user's real-name information to the cloud server; Receiving the resource account information bound to the primary identifier having a corresponding relationship with the real-name information of the target user; receiving a selection instruction, wherein the selection instruction is used to select the resource account information; The resource account information selected by the selection instruction is sent to the cloud server.

11. The method according to claim 9, characterized in that Also includes: generating a payment message, wherein the payment message includes a target slave identifier, wherein the target slave identifier is the slave identifier selected for payment; Sending the payment message to the cloud server; Receiving target resource account information sent by the cloud server, wherein the target resource account information is the resource account information having a corresponding relationship with the target slave identifier in the cloud server; The target resource account information is sent to the account opening institution server so that the account opening institution server completes the payment according to the target resource account information.

12. The method according to claim 8, characterized in that Sending the target user's real-name information to the cloud server includes: Authenticating the real-name information of the target user; When the authentication is successful and the target user is authorized, the real-name information of the target user is sent to the cloud server.

13. The method according to any one of claims 8 to 12, characterized in that The user real-name information includes the ID number; The user real-name information also includes one or more of the user name, user ID type, and mobile phone number.

14. The method according to any one of claims 8 to 12, characterized in that The resource account information includes bank card identification information.

15. A server, characterized in that: The server stores a primary identifier and user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one by one; The server comprises: A receiving module, used to obtain target user real-name information from the application side, wherein the target user real-name information includes the user real-name information of the target user; and used to receive target resource account information sent by the application side, wherein the target resource account information includes the resource account information of the target user; A binding module, used to bind the target resource account information with a target identifier when the server has user real-name information that is consistent with the target user real-name information, the target identifier includes the primary identifier in the server that has a corresponding relationship with the target user real-name information, the resource account information and the primary identifier bound in the server are shared by multiple applications, different applications each have their own user system, and multiple applications are installed on the user terminal; The receiving module is also used to receive the payment message sent by the second application side and the real-name information of the target user; A query module, used to query the target resource account information; A sending module, used for sending to the second application side, so that the second application side sends the target resource account information to the account opening institution server, so that the account opening institution server completes the payment according to the target resource account information; The number of applications used by the target user is N1. To complete the binding of M1 resource accounts, the target user only needs to perform M1 binding operations in the N1 applications.

16. An application device, characterized in that: include: A receiving module, used to obtain target user real-name information and target resource account information, wherein the target user real-name information includes the user real-name information of the target user, and the target resource account information includes the resource account information of the target user; A sending module, used for sending the target user real-name information to a cloud server, so that the cloud server can query and obtain a primary identifier corresponding to the target user real-name information, the cloud server stores the primary identifier and the user real-name information having a corresponding relationship, and the primary identifier corresponds to the user real-name information one by one; and, used for sending the target resource account information to the cloud server, so that the cloud server binds the target resource account information to the primary identifier corresponding to the target user real-name information, the resource account information and the primary identifier bound in the cloud server are shared by multiple applications, different applications each have their own user system, and multiple applications are installed on the user terminal; The sending module is also used to send a payment message and the target user's real-name information to the cloud server, so that the cloud server can find the target resource account information; The receiving module is also used to receive the target resource account information sent by the cloud server; The sending module is also used to send the target resource account information to the account opening institution server, so that the account opening institution server completes the payment according to the target resource account information; The number of applications used by the target user is N1. To complete the binding of M1 resource accounts, the target user only needs to perform M1 binding operations in the N1 applications.

17. A server, characterized in that: comprising a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the resource account binding method according to any one of claims 1 to 7 is implemented.

18. An application device, characterized in that: comprising a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the resource account binding method according to any one of claims 8 to 14 is implemented.

19. A resource account binding system, characterized in that: Includes the server as claimed in claim 17 and the application device as claimed in claim 18.

20. A computer storage medium, characterized in that The computer storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the resource account binding method according to any one of claims 1 to 14 is implemented.

Images