A data processing, resource transfer, payment method, device, equipment and medium

Abstract

A data processing, resource transfer, and payment method, apparatus, device, and medium are disclosed in this specification. An embodiment of this specification discloses a data processing method, comprising: acquiring a user binding request; determining a first account to be bound on a first server; sending user binding request feedback data to a terminal to display candidate binding objects; acquiring binding object selection data; determining each target binding object; determining a target server among the servers corresponding to each target binding object; binding the first account to a second account on each target server; and sending an account binding request to each target server, causing any target server to bind the second account to the first account; the second account and the first account correspond to the same user identity data.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing, resource transfer, payment method, device, equipment and medium. Background Art

[0002] In the prior art, people can use various Internet services using Internet accounts, among which some Internet services require users to bind different Internet accounts due to business requirements or to improve user experience.

[0003] In view of this, a more efficient account binding business-related data processing solution is needed. Summary of the invention

[0004] The embodiments of this specification provide a data processing, resource transfer, payment method, device, equipment and medium to solve the technical problem of how to more efficiently process data related to account binding services.

[0005] To solve the above technical problems, the embodiments of this specification provide the following technical solutions:

[0006] The embodiment of this specification provides a first data processing method, which is applied to a first server and includes:

[0007] Acquire a user binding request sent by the terminal, determine a first account to be bound on the first server, and send user binding request feedback data to the terminal so that the terminal displays candidate binding objects;

[0008] Acquire binding object selection data sent by the terminal, determine each target binding object according to the binding object selection data, and determine one or more target servers among the servers corresponding to each target binding object;

[0009] Binding the first account to a second account on each of the target servers, and sending an account binding request to each of the target servers, so that any of the target servers binds the second account on the target server to the first account;

[0010] The second account and the first account correspond to the same user identity data.

[0011] The embodiment of this specification provides a second data processing method, which is applied to a second server and includes:

[0012] If an identity authentication request or a binding consultation request sent by the first server is obtained, and the identity authentication request or the binding consultation request includes the user identity data corresponding to the first account, then determining a second account on the second server that has the same user identity data as the first account; wherein the first account is an account on the first server;

[0013] Sending authentication feedback data or consultation feedback data to the first server, wherein the authentication feedback data or consultation feedback data includes account data of the second account, so that the first server determines one or more target servers and sends an account binding request to each of the target servers;

[0014] If the account binding request sent by the first server is obtained, the second account is bound to the first account.

[0015] The embodiment of this specification provides a first resource transfer method, which is applied to a third server and includes:

[0016] Acquire a first resource transfer request sent by the terminal, determine a third account and a fourth account to be transferred and a resource transfer amount; wherein the third account is an account on the third server, and the third account and the fourth account are bound using the first or second data processing method;

[0017] Sending a second resource transfer request to a fourth server where the fourth account is located, so that the fourth server reduces the resources of the fourth account by the resource transfer amount; obtaining resource transfer feedback data sent by the fourth server, and if it is determined according to the resource transfer feedback data that the resources of the fourth account are reduced by the resource transfer amount, then increasing the resources of the third account by the resource transfer amount; or,

[0018] The resources of the third account are reduced by the resource transfer amount, and a second resource transfer request is sent to the fourth server where the fourth account is located, so that the fourth server increases the resources of the fourth account by the resource transfer amount.

[0019] The embodiment of this specification provides a second resource transfer method, which is applied to a fourth server and includes:

[0020] If the resource transfer request sent by the third server is obtained, determining a fourth account on the fourth server to which the resource transfer is to be performed, and determining the resource transfer amount;

[0021] reducing the resources of the fourth account by the resource transfer amount, and sending resource transfer feedback data to the third server, so that the third server increases the resources of the third account to be transferred by the resource transfer amount; or

[0022] If it is determined according to the resource transfer request that the third server reduces the resources of the third account to be transferred by the resource transfer amount, then the resources of the fourth account are increased by the resource transfer amount;

[0023] The third account is an account on the third server, and the third account is bound to the fourth account using the first or second data processing method.

[0024] The embodiment of this specification provides a first payment method, which is applied to a fifth server and includes:

[0025] Obtaining a first payment request sent by the terminal, determining a fifth account and a sixth account to be deducted funds and a payment amount; wherein the fifth account is a user login account on the fifth server, and the fifth account and the sixth account are bound using the first or second data processing method described above;

[0026] A second payment request is sent to a sixth server where the sixth account is located, so that the sixth server reduces the funds in the sixth account by the payment amount.

[0027] The embodiment of this specification provides a second payment method, which is applied to the sixth server, including:

[0028] If the payment request sent by the fifth server is obtained, determining a sixth account on the sixth server from which funds are to be deducted, and determining a payment amount;

[0029] reducing the funds in the sixth account by the payment amount, and sending payment feedback data to the fifth server;

[0030] Among them, the sixth account is bound to the fifth account on the fifth server using the first or second data processing method mentioned above, the fifth account is the user login account on the fifth server, and the fifth account is used to receive the payment request sent by the terminal.

[0031] The present invention provides a data processing device, including:

[0032] a pre-binding module, configured to obtain a user binding request sent by a terminal, determine a first account to be bound on the device, and send user binding request feedback data to the terminal so that the terminal displays candidate binding objects;

[0033] An initial binding module, used to obtain binding object selection data sent by the terminal, determine each target binding object according to the binding object selection data, and determine one or more target servers among the servers corresponding to each target binding object;

[0034] Account binding module, used for

[0035] Binding the first account to a second account on each of the target servers, and sending an account binding request to each of the target servers, so that any of the target servers binds the second account on the target server to the first account;

[0036] The second account and the first account correspond to the same user identity data.

[0037] The present invention provides a data processing device, including:

[0038] A preparatory binding module, for determining a second account on the device corresponding to the same user identity data as the first account if an identity authentication request or binding consultation request sent by the first server is obtained, and the identity authentication request or binding consultation request includes user identity data corresponding to the first account; wherein the first account is an account on the first server; and sending authentication feedback data or consultation feedback data to the first server, wherein the authentication feedback data or consultation feedback data includes account data of the second account, so that the first server determines one or more target servers and sends an account binding request to each of the target servers;

[0039] The account binding module is used to bind the second account to the first account if an account binding request sent by the first server is obtained.

[0040] The embodiment of this specification provides a resource transfer device, including:

[0041] A transfer initiation module, configured to obtain a first resource transfer request sent by a terminal, determine a third account and a fourth account to be transferred and a resource transfer amount; wherein the third account is an account on the device, and the third account and the fourth account are bound using the first or second data processing method described above;

[0042] a transfer module, configured to send a second resource transfer request to a fourth server where the fourth account is located, so that the fourth server reduces the resources of the fourth account by the resource transfer amount; obtain resource transfer feedback data sent by the fourth server, and if it is determined according to the resource transfer feedback data that the resources of the fourth account are reduced by the resource transfer amount, then increase the resources of the third account by the resource transfer amount; or,

[0043] The resources of the third account are reduced by the resource transfer amount, and a second resource transfer request is sent to the fourth server where the fourth account is located, so that the fourth server increases the resources of the fourth account by the resource transfer amount.

[0044] The embodiment of this specification provides a resource transfer device, including:

[0045] a transfer acceptance module, configured to determine a fourth account on the device to which resources are to be transferred and an amount of resources to be transferred if a resource transfer request sent by a third server is obtained;

[0046] a transfer module, configured to reduce the resources of the fourth account by the resource transfer amount, and send resource transfer feedback data to the third server, so that the third server increases the resources of the third account to be transferred by the resource transfer amount; or

[0047] If it is determined according to the resource transfer request that the third server reduces the resources of the third account to be transferred by the resource transfer amount, then the resources of the fourth account are increased by the resource transfer amount;

[0048] The third account is an account on the third server, and the third account is bound to the fourth account using the first or second data processing method.

[0049] The embodiment of this specification provides a payment device, including:

[0050] a payment initiation module, configured to obtain a first payment request sent by a terminal, determine a fifth account and a sixth account to be deducted funds, and a payment amount; wherein the fifth account is a user login account on the device, and the fifth account and the sixth account are bound using the first or second data processing method described above;

[0051] The payment module is used to send a second payment request to a sixth server where the sixth account is located, so that the sixth server reduces the funds in the sixth account by the payment amount.

[0052] The embodiment of this specification provides a payment device, including:

[0053] a payment acceptance module, configured to determine a sixth account on the device from which funds are to be deducted and a payment amount if a payment request sent by the fifth server is obtained;

[0054] a payment module, configured to reduce the funds in the sixth account by the payment amount and send payment feedback data to the fifth server;

[0055] Among them, the sixth account is bound to the fifth account on the fifth server using the first or second data processing method mentioned above, the fifth account is the user login account on the fifth server, and the fifth account is used to receive the payment request sent by the terminal.

[0056] The embodiment of this specification provides a data processing device, including:

[0057] at least one processor;

[0058] as well as,

[0059] a memory communicatively coupled to the at least one processor;

[0060] in,

[0061] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to perform the first or second data processing method mentioned above.

[0062] The embodiment of this specification provides a resource transfer device, including:

[0063] at least one processor;

[0064] as well as,

[0065] a memory communicatively coupled to the at least one processor;

[0066] in,

[0067] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to execute the first or second resource transfer method.

[0068] The embodiment of this specification provides a payment device, including:

[0069] at least one processor;

[0070] as well as,

[0071] a memory communicatively coupled to the at least one processor;

[0072] in,

[0073] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the first or second payment method mentioned above.

[0074] An embodiment of the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the first or second data processing method described above is implemented.

[0075] An embodiment of the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the first or second resource transfer method described above is implemented.

[0076] The embodiments of this specification provide a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the first or second payment method described above is implemented.

[0077] At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:

[0078] It can realize one-to-many account binding at one time, improve the efficiency of account binding, and improve the efficiency of resource transfer and payment between bound accounts. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments of this specification or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0080] Figure 1 It is a schematic diagram of the execution body of the data processing method in the first embodiment of this specification.

[0081] Figure 2 It is a flowchart of the data processing method in the first embodiment of this specification.

[0082] Figure 3 It is a schematic diagram of the data processing process in the first embodiment of this specification.

[0083] Figure 4 It is a page schematic diagram in the first embodiment of this specification.

[0084] Figure 5 This is another page schematic diagram in the first embodiment of this specification.

[0085] Figure 6 This is another page schematic diagram in the first embodiment of this specification.

[0086] Figure 7 This is another page schematic diagram in the first embodiment of this specification.

[0087] Figure 8 This is another page schematic diagram in the first embodiment of this specification.

[0088] Fig. 9 This is another page schematic diagram in the first embodiment of this specification.

[0089] Fig.10This is another page schematic diagram in the first embodiment of this specification.

[0090] Fig.11 It is a flowchart of the data processing method in the second embodiment of this specification.

[0091] Fig.12 It is a flowchart of the resource transfer method in the third embodiment of this specification.

[0092] Fig.13 It is a flowchart of the resource transfer method in the fourth embodiment of this specification.

[0093] Fig.14 It is a flowchart of the payment method in the fifth embodiment of this specification.

[0094] Fig.15 It is a flowchart of the payment method in the sixth embodiment of this specification.

[0095] Fig.16 It is a schematic diagram of the structure of the data processing device in the seventh embodiment of this specification.

[0096] Fig.17 It is a schematic diagram of the structure of the data processing device in the eighth embodiment of this specification.

[0097] Fig.18 It is a schematic diagram of the structure of the resource transfer device in the ninth embodiment of this specification.

[0098] Fig.19 This is a schematic diagram of the structure of the resource transfer device in the tenth embodiment of this specification.

[0099] Fig. 20 It is a schematic diagram of the structure of the payment device in the eleventh embodiment of this specification.

[0100] Fig.21 It is a schematic diagram of the structure of the payment device in the twelfth embodiment of this specification. DETAILED DESCRIPTION

[0101] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0102] In the prior art, people can use various Internet services using Internet accounts, among which some Internet services require users to bind different Internet accounts due to business requirements or to improve user experience.

[0103] The first embodiment of this specification (hereinafter referred to as "this embodiment") provides a data processing method. The execution subject of this embodiment can be a terminal (including but not limited to a mobile phone, computer, pad, TV) or a server or an operating system or a data processing platform or a data processing system, etc., that is, the execution subject can be various and can be set, used or changed as needed. In addition, there can also be a third-party application to assist the execution subject in executing this embodiment. For example Figure 1 As shown, the data processing method in this embodiment can be executed by a server, and an application corresponding to the server can be installed on a terminal (held by the user). Data can be transmitted between the terminal or the application and the server, and data can be collected, input or output, or pages or information processing can be performed (for the user) through the terminal or the application, thereby assisting the server in executing the data processing method in this embodiment.

[0104] like Figure 2 and Figure 3 As shown, the data processing method provided in this embodiment is applied to the first server, including:

[0105] S103: (Executing subject) obtaining a user binding request sent by the terminal, determining a first account to be bound on the first server, and sending user binding request feedback data to the terminal, so that the terminal displays candidate binding objects;

[0106] In this embodiment, the execution subject may be the first server. The execution subject may obtain a user binding request sent by a terminal (may be referred to as a "triggering terminal"), and determine a first account to be bound on the first server.

[0107] The trigger terminal may send a user binding request in a variety of ways. For example, the trigger terminal may install the above-mentioned corresponding application (which may be referred to as the trigger application). When the user opens the corresponding interface of the trigger application, the account binding service is provided to the user through the corresponding options or buttons on the interface, such as Figure 4The interface shown has an "I want to bind" option, and the user can click on this option to initiate the account binding service. Since the user initiates the account binding service by operating the trigger application, and the first server is the server corresponding to the trigger application, after the user initiates the account binding service, the trigger terminal can generate a user binding request according to the user operation and send the user binding request to the first server. Correspondingly, the first server obtains the user binding request sent by the trigger terminal. Specifically, the first server receives the user binding request sent by the trigger terminal (receiving a request is a type of obtaining a request).

[0108] The first server may determine the first account to be bound on the first server by means of 1.1 and / or 1.2 (this embodiment is not limited to means of 1.1 and / or 1.2):

[0109] 1.1. The first account is the login account of the triggering terminal when obtaining the user binding request;

[0110] When the user operates the trigger application, if the user logs into the account on the first server on the trigger terminal (ie, the trigger application on the trigger terminal), for example Figure 4 As shown, after the user initiates the account binding service, the trigger terminal sends a user binding request to the first server, and the first server can use the user's login account on the trigger terminal (the account on the first server) as the first account to be bound.

[0111] 1.2. Determine the first account according to the user binding request

[0112] After the user initiates the account binding service, a corresponding input box may be provided on the triggering application for the user to enter account information (such as user name or account number). Figure 5 As shown; since the user triggers the application to initiate the account binding service, the user input should generally be the user's account on the first server; and / or, after the user initiates the account binding service, the trigger application can display the user's account list (a list of accounts opened by the user on the first server) for the user to select an account. For example Figure 5 The following figure shows a situation where there are three first server accounts. Figure 5 The figures are for illustration only and do not represent actual accounts.

[0113] The trigger terminal may include the account input or selected by the user in a user binding request and send it to the first server, so that the first server may determine the first account according to the user binding request, for example, use the account included in the user binding request as the first account to be bound.

[0114] After the first server determines the first account to be bound, it can send user binding request feedback data to the trigger terminal so that the trigger terminal displays candidate binding objects. Candidate binding objects are objects that can be bound, and the "object" here can be an organization name or a business service provider name, etc. The owner of the first server can pre-build relevant Internet protocols with each object, such as data transmission protocols or data authentication protocols, etc. The objects that have built the above Internet protocols with the service provider of the first server can be called candidate binding objects, that is, the trigger terminal can display a list of candidate binding objects for the user to choose. For example Figure 6 shows the situation where there are 4 candidate binding objects, Figure 6 The names are for reference only and do not represent actual object names.

[0115] After the first server determines the first account to be bound, before sending user binding request feedback data to the trigger terminal, it can first perform identity authentication or other authentication on the user identity data corresponding to the first account, and send user binding request feedback data to the trigger terminal after the authentication is passed.

[0116] S103: (Executing subject) obtaining binding object selection data sent by the terminal, determining each target binding object according to the binding object selection data, and determining one or more target servers from the servers corresponding to each target binding object;

[0117] After the trigger terminal displays the candidate binding objects, the object selected by the user can be determined according to the user operation, and the binding object selection data can be sent to the first server, and the binding object selection data can include the user's selection data for the candidate binding objects. The first server obtains the binding object selection data sent by the trigger terminal, determines the object selected by the user according to the binding object selection data, and uses the object selected by the user as the target binding object, that is, the first server determines each target binding object according to the binding object selection data.

[0118] After the first server determines each target binding object, it can determine one or more target servers from the servers corresponding to each target binding object, and send an account binding request to each target server. As above, "object" can be an organization name or a business service provider name, etc. For any object, the server corresponding to the object can be a subordinate server of the organization represented by the object or a server used to provide the business represented by the object.

[0119] Specifically, one or more target servers may be determined in the servers corresponding to each target binding object in the following manner:

[0120] S1031: before sending an account binding request to each target server, the first server sends an identity authentication request or a binding consultation request to the server corresponding to each target binding object, wherein the identity authentication request or the binding consultation request includes the user identity data corresponding to the first account, so that any server corresponding to each target binding object determines a second account on the server corresponding to the same user identity data as the first account;

[0121] Specifically, after the first server determines each target binding object, it can send an identity authentication request or a binding consultation request to the server corresponding to each target binding object. The identity authentication request or the binding consultation request includes the user identity data corresponding to the first account (i.e., the user identity data used to register the first account, including but not limited to the user ID number or other identity number), so that any server corresponding to each target binding object can determine the second account on the server after receiving the identity authentication request or the binding request; wherein the second account corresponds to the same user identity data as the first account.

[0122] For example, if the target binding objects include object A, object B, and object C, the first server can send an identity authentication request or a binding consultation request to the server corresponding to object A, the server corresponding to object B, and the server corresponding to object C, so that the server corresponding to object A determines the second account corresponding to the same user identity data as the first account, the server corresponding to object B determines the second account corresponding to the same user identity data as the first account, and the server corresponding to object C determines the second account corresponding to the same user identity data as the first account. Generally, different target binding objects correspond to different servers. If there are multiple target binding objects, there can be multiple servers corresponding to each target binding object, and there can be multiple second accounts determined.

[0123] Any server corresponding to the target binding object may send authentication feedback data or consultation feedback data to the first server.

[0124] S1033: After the first server sends an identity authentication request or a binding consultation request to any server corresponding to each of the target binding objects, the first server obtains authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, and determines the second account on the server according to the authentication feedback data or consultation feedback data sent by the server;

[0125] Specifically, after the first server sends an identity authentication request or a binding consultation request to any server corresponding to each of the target binding objects, the authentication feedback data (corresponding to the identity authentication request) or consultation feedback data (corresponding to the binding consultation request) sent by any server corresponding to each of the target binding objects can be obtained. For any server corresponding to each of the target binding objects, the authentication feedback data or consultation feedback data sent by the server may include the account information of the second account determined by the server, and the first server can determine the second account on the server based on the authentication feedback data or consultation feedback data sent by the server.

[0126] S1035: After the first server determines the second account on the server according to the authentication feedback data or the consultation feedback data sent by any server corresponding to each of the target binding objects, the first server sends candidate account data to the triggering terminal, where the candidate account data is used to enable the terminal to display the second account determined by the server corresponding to each of the target binding objects;

[0127] Specifically, after the first server determines the second account on each server corresponding to each target binding object, it can send candidate account data to the trigger terminal. The candidate account data can include account information of the second account on each server corresponding to each target binding object, so that the trigger terminal displays the second account on each server corresponding to each target binding object. The second account can be used as a candidate binding account for the first account, that is, the trigger terminal can display an account list of the second account for the user to select. Figure 7 As shown, assuming that the user selects candidate binding objects 1 to 3, the server of object 1 has 3 second accounts, and objects 2 and 3 each have 1 second account. Figure 7 The names are for reference only and do not represent actual object names.

[0128] The following is a further description of two possible situations:

[0129] Case 1: The second account does not exist on one or some servers corresponding to the target binding object

[0130] The above-mentioned second account may not exist on the server corresponding to some target binding objects. Assuming that server S1 is the server corresponding to the target binding object A (only an example, not specific), and the above-mentioned second account does not exist on server S1, after the first server obtains the authentication feedback data or consultation feedback data sent by server S1, it can determine that the above-mentioned second account does not exist on server S1 according to the authentication feedback data or consultation feedback data sent by server S1. In this case, the above-mentioned candidate account data is also used to trigger the terminal to display the first prompt information, and the first prompt information is used to prompt that the target binding object corresponding to the server where the second account does not exist has no bindable account. For example, the server corresponding to object 3 does not have a second account, for example Figure 8 As shown. Using the above example, the first prompt information is used to prompt that the target binding object A has no bindable account. If there are multiple target binding objects without bindable accounts, each target binding object without bindable accounts can have the above first prompt information.

[0131] Using the above example, if the second account does not exist on a server corresponding to the target binding object, the candidate account data is also used to cause the trigger terminal to display a second prompt message, and the second prompt message is used to prompt the user to open an account of "the target binding object corresponding to the server where the second account does not exist". For example, if the server corresponding to object 3 does not have a second account, the second prompt message prompts the user to open an account for object 3, for example Figure 8 As shown. Continuing with the above example, if the server S1 does not have the above second account, the second prompt information is used to prompt the user to open an account of the target binding object A, and the account of the target binding object A is also the account of the server S1. If there are multiple target binding objects that do not have a bindable account, each target binding object that does not have a bindable account can have the above second prompt information. In addition, the second prompt information itself can be in the form of an option or a button, and the user can open an account by clicking the second prompt information, for example Figure 8 shown.

[0132] As above, if the trigger terminal displays the second prompt information, the user may need to open an account of the "target binding object corresponding to the server where the second account does not exist", for example, the user clicks on the second prompt information. In this case, the trigger terminal can obtain the user's request to open an account and send a user activation request to the first server. As above, if there are multiple target binding objects that do not have a bindable account, each target binding object that does not have a bindable account can have the above-mentioned second prompt information, and the trigger terminal can determine which target binding object the user clicked on and corresponding to the second prompt information, thereby determining which target binding object the user needs to open an account for, and include the target binding object (object data) for which the user wants to open an account in the user activation request.

[0133] Correspondingly, after the first server obtains the user activation request sent by the trigger terminal, it can determine which target binding object account or accounts the user wants to activate, and use the server corresponding to the target binding object whose account the user wants to open as the account activation server, that is, the first server determines one or more account activation servers based on the account activation request.

[0134] The first server sends an account activation request to each account activation server so that each account activation server activates the second account. The activated second account should correspond to the same user identity data as the first account. Since the account activation server itself is the server corresponding to the target binding object, the account activation server has previously obtained the identity authentication request or binding consultation request sent by the first server and containing the user identity data corresponding to the first account. Therefore, the account activation request may or may not contain the user identity data corresponding to the first account.

[0135] Any account opening server may send opening feedback data to the first server, and the opening feedback data may include account data of the opened second account.

[0136] After sending the account opening request to each account opening server, the first server can obtain the opening feedback data sent by any account opening server, and determine the second account opened by the account opening server according to the opening feedback data sent by the account opening server.

[0137] After obtaining the activation feedback data, the first server may send candidate account supplementary data to the trigger terminal, and the candidate account supplementary data is used to enable the terminal to display the second account opened by each account activation server. Since the server corresponding to some target binding objects already has a second account before the first server sends an identity authentication request or a binding consultation request, after the first server sends the candidate account supplementary data to the trigger terminal, the second account opened by each account activation server may be displayed together with "the second account existed on the server corresponding to the target binding object before the first server sends an identity authentication request or a binding consultation request". For example, the account of the server corresponding to object 3 is activated, for example Fig. 9 shown.

[0138] Case 2: Multiple second accounts exist on one or some servers corresponding to the target binding object

[0139] For any target binding object, if the server corresponding to the target binding object determines multiple second accounts after obtaining the identity authentication request or binding consultation request sent by the first server, the above candidate account data is also used to enable the trigger terminal to display multiple second accounts of the server corresponding to the target binding object, for example Figures 7 to 9 Any one shown.

[0140] Assuming that server S2 is the server corresponding to the target binding object B (only an example, not specific), after receiving the identity authentication request or binding consultation request sent by the first server, server S2 determines multiple second accounts, then server S2 can determine one or more recommended second accounts (may be called "recommended accounts", recommended accounts are also recommended second accounts for binding) from the multiple second accounts on it, and include the account data of the recommended account in the authentication feedback data or consultation feedback data sent by server S2 to the first server. Among them, server S2 can determine the recommended account based on the account history operation data of the multiple second accounts on it.

[0141] The first server receives the authentication feedback data or consultation feedback data sent by the server S2, and determines the recommended account on the server S2 according to the authentication feedback data or consultation feedback data sent by the server S2. In this case, the candidate account data is also used to trigger the terminal to display the first recommendation information, and the first recommendation information is used to prompt the recommended account. For example, the account 1 on the server corresponding to the object 1 is the recommended account, for example Figures 7 to 9 For any target binding object, if the server corresponding to the target binding object has multiple second accounts, the target binding object can have the above-mentioned first recommendation information.

[0142] In addition, after the first server determines the second account on the server based on the authentication feedback data or consultation feedback data sent by any server corresponding to each target binding object, it can also determine the recommended binding second account from all the second accounts on the server corresponding to each target binding object. The above-mentioned candidate account data is also used to enable the trigger terminal to display second recommendation information, and the second recommendation information is used to prompt the recommendation of the above-mentioned "recommended binding second account determined from all second accounts".

[0143] Specifically, the first server may determine the recommended second account for binding from the second accounts of the servers corresponding to the target binding objects based on the historical interaction data between the first server and the servers corresponding to the target binding objects, that is, "the recommended second account for binding determined from all the second accounts".

[0144] S1037: Determining one or more target servers among the servers corresponding to each of the target binding objects includes: obtaining binding account selection data sent by the terminal, determining one or more selected second accounts according to the binding account selection data, and taking the server where the one or more selected second accounts are located as the target server.

[0145] Specifically, for any target binding object, the second account on the server corresponding to the target binding object is also the second account of the target binding object. After the trigger terminal displays the second account of each target binding object through the candidate account data, the user can select the second account to be bound, so that the trigger terminal can obtain the user's operation on the second account, generate binding account selection data, and send the binding account selection data to the first server. Among them, the binding account selection data may include the second account selected by the user.

[0146] The first server obtains the binding account selection data sent by the triggering terminal, determines one or more second accounts selected by the user (may be referred to as selected second accounts) according to the binding account selection data, and uses the server where each selected second account is located as the target server. It can be seen that if each selected second account comes from multiple servers, there are multiple target servers.

[0147] In this embodiment, the target server may also be determined by other methods, for example, after the user selects a target binding object, the server corresponding to the target binding object is used as the target server.

[0148] Generally speaking, if the user selects a target binding object, it means that the user wants to bind the first account to the second account of each target binding object. If each target binding object has a second account, the user will select at least one second account for each target binding object, so that the target server is the server corresponding to the target binding object.

[0149] S105: Bind the first account to a second account on each of the target servers, and send an account binding request to each of the target servers, so that any of the target servers binds the second account on the target server to the first account; wherein the second account and the first account correspond to the same user identity data.

[0150] After determining one or more target servers, the first account can be bound to the second account on each target server, that is, the first server binds the first account to the second account on each target server, and sends an account binding request to each target server, so that any target server binds the second account on the target server to the first account. Specifically, the first account can be bound to each selected second account by the method of 2.1 and / or 2.2 (this embodiment is not limited to the method of 2.1 and / or 2.2):

[0151] 2.1. Bind the target server first, then bind the first server

[0152] The first server may send an account binding request to each of the target servers so that any of the target servers binds the second account on the target server to the first account; and obtain account binding request feedback data sent by any of the target servers. If it is determined according to the account binding request feedback data that the target server has bound the second account on the target server to the first account, the first account is bound to the second account on the target server.

[0153] For example, for any target server S3, the first server sends an account binding request to the target server S3, so that the target server S3 binds its second account to the first account, that is, the target server first binds its second account to the first account.

[0154] Any target server can send account binding request feedback data to the first server. The first server obtains the (first) account binding request feedback data sent by any of the target servers. If it is determined according to the account binding request feedback data that the target server has bound the second account on the target server to the first account, the first account is bound to the second account on the target server, that is, the first server then binds the first account to the second account.

[0155] Continuing with the above example, the first server obtains the account binding request feedback data sent by the target server S3. If it is determined that the target server S3 has bound its second account to the first account based on the account binding request feedback data sent by the target server S3, the first server binds the first account to the second account on the target server S3.

[0156] 2.2. Bind the first server first, then bind the target server

[0157] After the first server binds the first account to a second account of any target server, the first server sends an account binding request to the target server, so that the target server binds the second account on the target server to the first account.

[0158] The first server can bind the first account to the second account on each target server, and then make each target server bind the second account on it to the first account. For example, for any target server S4, the first server binds the first account to the second account on the target server S4, that is, the first server first binds the first account to the second account; then the first server sends an account binding request to the target server S4, so that the target server S4 binds the second account on it to the first account, that is, the target server then binds the second account to the first account.

[0159] In 2.2, after any of the target servers binds the second account on the target server to the first account, it can send account (second) binding request feedback data to the first server, and the first server determines whether the target server has bound the second account on the target server to the first account based on the account binding request feedback data.

[0160] In particular, the account binding request may include user identity data corresponding to the first account.

[0161] In the above 2.1 or 2.2, for any target server, if there are multiple second accounts on the target server, after the target server obtains the account binding request sent by the first server (regardless of the account binding request in 2.1 or 2.2, the same below), all the second accounts on it can be bound to the first account, or the target server can bind one of the second accounts on the target server to the first account.

[0162] In 2.1 or 2.2 above, for any target server, before binding the second account on it with the first account, the target server can perform identity authentication or other authentication on the user identity data corresponding to the first account and the user identity data corresponding to the second account, and bind the second account on it with the first account after the authentication is passed.

[0163] In this embodiment, sending an account binding request to each of the target servers so that any of the target servers binds the second account on the target server to the first account includes: sending an account binding request to each of the target servers so that any of the target servers binds one of the second accounts on the target server to the first account.

[0164] For example, for any target server S5, if there are multiple second accounts on it, the account binding request sent by the first server enables the target server S5 to bind one of the second accounts on it to the first account.

[0165] Specifically, in this embodiment, for any target server, if there are multiple second accounts on the target server, and in the aforementioned S1037, the user selects a second account of the target server, then the account binding request sent by the first server to the target server may include the second account on the target server selected by the user, so that the target server binds the second account selected by the user to the first account.

[0166] The binding of the first account and the second account by the first server may specifically refer to the first server itself generating and storing the binding relationship between the first account and the second account; the binding of the second account and the first account by the target server may specifically refer to the target server itself generating and storing the binding relationship between the second account and the first account. An account binding protocol or consensus protocol may be pre-established between the first server and the servers corresponding to each candidate binding object, so that the first server and the target server can generate and store the binding relationship between the first account and the second account.

[0167] In addition, the first server may send user feedback data to the trigger terminal so that the trigger terminal displays the account binding result, that is, the account binding result of the first account and the second account, for example Fig.10 shown.

[0168] In particular, the first account or the second account may be a resource storage or resource transfer account.

[0169] It should be noted that when the first server sends any request or any data to any server corresponding to each target binding object, the first server may not directly send the request or data to any server corresponding to each target binding object, but the first server sends the request or data to be sent to the intermediate server, and the intermediate server sends the request or data to be sent to any server corresponding to each target binding object. For example, server S6 is any server corresponding to the target binding object. When the first server sends any request or any data to server S6, the first server may not directly send the request or data to server S6, but the first server sends the request or data to be sent to the intermediate server, and the intermediate server sends the request or data to be sent to server S6.

[0170] When any server corresponding to each target binding object sends any request or any data to the first server, it is possible that any server corresponding to each target binding object does not directly send the request or data to the first server, but any server corresponding to each target binding object sends the request or data to be sent to the intermediate server, and the intermediate server sends the request or data to be sent to the first server. Using the above example, server S6 is any server corresponding to the target binding object. When server S6 sends any request or any data to the first server, it is possible that server S6 does not directly send the request or data to the first server, but server S6 sends the request or data to be sent to the intermediate server, and the intermediate server sends the request or data to be sent to the first server.

[0171] No matter the intermediate server receives the request and data from the first server or any server corresponding to each target binding object, it can authenticate the request or data, and then send the request and data to the first server or any server corresponding to each target binding object after the authentication is passed.

[0172] It should be noted that in this embodiment, the trigger terminal is variable. For example, if a user logs in to a first account on terminal a and initiates an account binding service, and then logs in to the first account on terminal b and selects a second account, the trigger terminal changes from terminal a to terminal b.

[0173] In this embodiment, the candidate binding objects can be diverse, giving the user the right to choose; the first account represents one of the accounts that the user wants to bind; the target binding object represents the object that the user wants to bind.

[0174] The first server sends an identity authentication request or a binding consultation request to the server corresponding to each target binding object, and obtains authentication feedback data or consultation feedback data sent by the server corresponding to each target binding object, thereby realizing authentication, matching or consensus on the user identity data corresponding to the first account between the first server and the server corresponding to each target binding object.

[0175] The account opening process allows users to open and bind accounts for objects they want to bind but do not have accounts with at one time.

[0176] Through the user's selection of the second account, the second account that the user wants to bind, that is, the other party of the account to be bound, can be determined, and the user can select multiple second accounts to complete the binding of the first account and the second account.

[0177] In this embodiment, the user first selects a target binding object, thereby determining a server corresponding to each target binding object from servers corresponding to each candidate object, and allowing the server corresponding to each target binding object to determine a second account thereon; then the user selects a second account, thereby determining a target server from servers corresponding to each target binding object, and then realizing binding of the first account and the second account on each target server.

[0178] This embodiment can realize one-to-many account binding at one time, that is, binding of a first account to multiple second accounts, thereby improving the efficiency of account binding. Users do not need to enter personal identity data when binding, and the first server can automatically obtain the user identity data corresponding to the first account, further improving the efficiency of account binding and improving the security of account binding.

[0179] In the prior art, in order to make electronic payments and improve the electronic payment experience, users can bind their third-party payment accounts with financial institution (including but not limited to bank) accounts to activate electronic payment services such as quick payment. Among them, quick payment requires the user's bank account to be bound with the account of the third-party payment institution in advance under the three-party (user, bank, payment institution) agreement framework.

[0180] As the number of third-party payment institutions increases, users may need to bind their financial institution accounts (hereinafter taking bank accounts as an example) with accounts of multiple third-party payment institutions. However, in the prior art, users must initiate the binding of bank accounts through third-party payment institutions, and each third-party payment institution can only bind its own account with a bank account. In addition, the binding process between each third-party payment institution and the bank account is different. Users must enter binding elements (including but not limited to name, identity information, bank card number, mobile phone number) during each binding process. Users are prone to filling in errors, resulting in a complicated binding process and low binding efficiency.

[0181] In this embodiment, the bank server can be used as the first server, the bank account can be used as the first account, each third-party payment institution can be used as a candidate binding object, the server of each third-party payment institution can be used as the target server, and the account of the third-party payment institution can be used as the second account. It can complete the binding of a bank account to multiple third-party institution accounts at one time, effectively improving the efficiency of account binding. In this embodiment, account binding can be initiated from the bank side without relying on each third-party payment institution. During the account binding process, the user does not need to enter personal information, and the bank can automatically obtain the first account and the user identity information corresponding to the first account, further improving the efficiency and security of account binding.

[0182] It should be noted that, in the process of binding the financial institution account and the third-party payment institution account, the above-mentioned intermediate server can be a server of ChinaNetPay or ChinaUnionPay.

[0183] The first embodiment of this specification is mainly described from the perspective of the first server, and the second embodiment of this specification is mainly described from the perspective of the second server (further, from the target server).

[0184] The second embodiment of this specification (hereinafter referred to as "this embodiment") provides a data processing method. The execution subject of this embodiment can be a terminal (including but not limited to mobile phones, computers, pads, televisions) or a server or an operating system or a data processing platform or a data processing system, etc., that is, the execution subject can be various and can be set, used or changed as needed. In addition, there can also be a third-party application to assist the execution subject in executing this embodiment. For example Figure 1As shown, the data processing method in this embodiment can be executed by a server, and an application corresponding to the server can be installed on a terminal (held by the user). Data can be transmitted between the terminal or the application and the server, and data can be collected, input or output, or pages or information processing can be performed (for the user) through the terminal or the application, thereby assisting the server in executing the data processing method in this embodiment.

[0185] like Fig.11 As shown, the data processing method provided in this embodiment is applied to the second server (that is, the execution subject is the second server), including:

[0186] S202: If an identity authentication request or a binding consultation request sent by the first server is obtained, and the identity authentication request or the binding consultation request includes user identity data corresponding to the first account, then determine a second account on the second server that has the same user identity data as the first account; wherein the first account is an account on the first server;

[0187] The second server in this embodiment obtains the identity authentication request or binding consultation request sent by the first server, which means that the second server in this embodiment is a server corresponding to the target binding object in the first embodiment, that is, a server corresponding to the candidate binding object.

[0188] S204: Sending authentication feedback data or consultation feedback data to the first server, wherein the authentication feedback data or consultation feedback data includes account data of the second account, so that the first server determines one or more target servers and sends an account binding request to each of the target servers;

[0189] In this embodiment, an identity authentication request or a binding consultation request sent by the first server is obtained. If there is no account on the second server corresponding to the same user identity data as the first account, the authentication feedback data or the consultation feedback data is used to enable the first server to determine that there is no account on the second server corresponding to the same user identity data as the first account.

[0190] In this embodiment, if an account opening request sent by the first server is received, a second account corresponding to the same user identity data as the first account is opened according to the account opening request;

[0191] Sending activation feedback data to the first server, wherein the activation feedback data includes account data of a second account activated according to the account activation request.

[0192] In this embodiment, if there are multiple second accounts, the authentication feedback data or consultation feedback data also includes account data of a recommended account, and the recommended account is one or more second accounts.

[0193] In this embodiment, the recommended account is determined according to the historical account operation data of the plurality of second accounts.

[0194] S206: If the account binding request sent by the first server is obtained, bind the second account to the first account;

[0195] The account binding request here may be the account binding request in 2.1 or 2.2, which means that the second server in this embodiment has become a target server in the first embodiment.

[0196] In this embodiment, if there are multiple second accounts, binding the second account to the first account includes:

[0197] Determine a second account to be bound from the multiple second accounts according to the account binding request, and bind the second account to be bound to the first account.

[0198] In this embodiment, if there are multiple second accounts, binding the second account to the first account includes:

[0199] A second account to be bound is determined from the multiple second accounts, and the second account to be bound is bound to the first account.

[0200] After the second server binds the second account on itself to the first account, it may send account binding request feedback data to the first server.

[0201] The account binding request feedback data here may be the account binding request feedback data in 2.1 or the account binding request feedback data in 2.2.

[0202] Referring to the first embodiment, in this embodiment, if the second server needs to send any request or any data to the first server, the second server can send the arbitrary request or any data to the intermediate server, and the intermediate server sends the arbitrary request or any data to the second server.

[0203] For the contents not described in detail in this embodiment, refer to the first embodiment.

[0204] This embodiment can realize one-to-many account binding at one time, that is, binding of a first account to multiple second accounts, thereby improving the efficiency of account binding. Users do not need to enter personal identity data when binding, and the first server can automatically obtain the user identity data corresponding to the first account, further improving the efficiency of account binding and improving the security of account binding.

[0205] This embodiment is the first embodiment and can be used to bind a financial institution account with a third-party payment institution account.

[0206] As shown in the first embodiment, the first account and the second account can both be resource storage or resource transfer accounts. After the first account and the second account are bound through the first or second embodiment, resources can be transferred between the first account and each second account bound to the first account.

[0207] The third embodiment of this specification (hereinafter referred to as "this embodiment") provides a resource transfer method. The execution subject of this embodiment can be a terminal (including but not limited to mobile phones, computers, pads, televisions) or a server or an operating system or a resource transfer platform or a resource transfer system, etc., that is, the execution subject can be various and can be set, used or changed as needed. In addition, there can also be a third-party application to assist the execution subject in executing this embodiment. For example Figure 1 As shown, the resource transfer method in this embodiment can be executed by a server, and an application corresponding to the server can be installed on a terminal (held by a user). Data can be transmitted between the terminal or the application and the server, and data can be collected, input or output, or pages or information can be processed (for the user) through the terminal or the application, thereby assisting the server in executing the resource transfer method in this embodiment.

[0208] like Fig.12 As shown, the resource transfer method provided in this embodiment is applied to the third server (that is, the execution subject is the third server), including:

[0209] S301: Acquire a first resource transfer request sent by a terminal, determine a third account and a fourth account to be transferred resources, and a resource transfer amount; wherein the third account is an account on the third server, and the third account and the fourth account are bound using the method described in the first or second embodiment;

[0210] The third server in this embodiment is equivalent to the first server in the first embodiment or the second server (or target server) in the second embodiment.

[0211] The third server may obtain a first resource transfer request sent by a terminal (which may be referred to as a "second trigger terminal". The trigger terminal in the first embodiment is the first trigger terminal. The first trigger terminal and the second trigger terminal may be the same or different).

[0212] Referring to the first embodiment, the user may initiate a resource transfer service through an application corresponding to the third server, and then the second trigger terminal sends a first resource transfer request to the third server.

[0213] The third account to be transferred is an account on the third server, and the third account is determined in the same manner as the first account, for example, by user input or according to the login account of the second trigger terminal. The first account and any second account bound to the first account can be used as resource transfer-out or resource transfer-in accounts, so the third account can be equivalent to the first account or the second account.

[0214] The fourth account to be transferred can be determined by the user and included in the first resource transfer request, so the third server can determine the fourth account according to the first resource transfer request. Similarly, the first account and any second account bound to the first account can be used as a resource transfer-out or resource transfer-in account, so the third account can be equivalent to the first account or the second account.

[0215] The resource transfer amount may be included in the first resource transfer request, so the third server may determine the resource transfer amount according to the first resource transfer request.

[0216] The third account is bound to the fourth account using the method described in the first or second embodiment. If (determined by the third server) the third account and the fourth account are not yet bound when the first resource transfer request is obtained, the third server can bind the third account and the fourth account using the data processing method of the first embodiment, just like the first server of the first embodiment.

[0217] S303: Send a second resource transfer request to the fourth server where the fourth account is located, so that the fourth server reduces the resources of the fourth account by the resource transfer amount; obtain resource transfer feedback data sent by the fourth server, and if it is determined according to the resource transfer feedback data that the resources of the fourth account are reduced by the resource transfer amount, then increase the resources of the third account by the resource transfer amount; or, reduce the resources of the third account by the resource transfer amount, and send a second resource transfer request to the fourth server where the fourth account is located, so that the fourth server increases the resources of the fourth account by the resource transfer amount.

[0218] The second resource transfer request may include account data of the fourth account and the resource transfer amount, so that after the fourth server where the fourth account is located obtains the second resource transfer request, it determines the fourth account to be transferred to on the fourth server and determines the resource transfer amount.

[0219] If the first resource transfer request is to transfer resources from the fourth account to the third account, that is, the third server is the resource transfer-in server, then the third server sends a second resource transfer request to the fourth server where the fourth account is located, so that the fourth server reduces the resources of the fourth account by the resource transfer amount; obtains the resource transfer feedback data sent by the fourth server, and if it is determined according to the resource transfer feedback data that the resources of the fourth account are reduced by the resource transfer amount, then increases the resources of the third account by the resource transfer amount.

[0220] If the first resource transfer request is to transfer resources from the third account to the fourth account, that is, the third server is the resource transfer-out server, the third server will reduce the resources of the third account by the resource transfer amount, and send a second resource transfer request to the fourth server where the fourth account is located, so that the fourth server will increase the resources of the fourth account by the resource transfer amount.

[0221] The third server may send the user feedback data to the second trigger terminal, so that the second trigger terminal displays the resource transfer result.

[0222] With reference to the first or second embodiment, data transmission between the third server and the fourth server may be performed through an intermediate server.

[0223] In this embodiment, by binding the third account and the fourth account using the method of the first or second embodiment, one-to-many account binding can be achieved at one time, thereby improving the efficiency of account binding. By transferring resources through the bound accounts, the efficiency of resource transfer is further improved.

[0224] The fourth embodiment of this specification (hereinafter referred to as "this embodiment") provides a resource transfer method. The execution subject of this embodiment can be a terminal (including but not limited to mobile phones, computers, pads, televisions) or a server or an operating system or a resource transfer platform or a resource transfer system, etc., that is, the execution subject can be various and can be set, used or changed as needed. In addition, a third-party application can also assist the execution subject in executing this embodiment. For example Figure 1As shown, the resource transfer method in this embodiment can be executed by a server, and an application corresponding to the server can be installed on a terminal (held by a user). Data can be transmitted between the terminal or the application and the server, and data can be collected, input or output, or pages or information can be processed (for the user) through the terminal or the application, thereby assisting the server in executing the resource transfer method in this embodiment.

[0225] like Fig.13 As shown, the resource transfer method provided in this embodiment is applied to the fourth server (that is, the execution subject is the fourth server), including:

[0226] S402: If a resource transfer request sent by the third server is obtained, a fourth account on the fourth server to which resources are to be transferred is determined, and a resource transfer amount is determined;

[0227] The third server in this embodiment is equivalent to the first server in the first embodiment or the second server (or target server) in the second embodiment, and the resource transfer request in this embodiment is the second resource transfer request in the third embodiment.

[0228] S404: reducing the resources of the fourth account by the resource transfer amount, and sending resource transfer feedback data to the third server, so that the third server increases the resources of the third account to be transferred by the resource transfer amount; or

[0229] If it is determined according to the resource transfer request that the third server reduces the resources of the third account to be transferred by the resource transfer amount, then the resources of the fourth account are increased by the resource transfer amount;

[0230] The third account is an account on the third server, and the third account is bound to the fourth account using the method described in the first or second embodiment.

[0231] For the contents not described in detail in this embodiment, refer to the third embodiment.

[0232] In this embodiment, by binding the third account and the fourth account using the method of the first or second embodiment, one-to-many account binding can be achieved at one time, thereby improving the efficiency of account binding. By transferring resources through the bound accounts, the efficiency of resource transfer is further improved.

[0233] The resources in the third or fourth embodiment include virtual resources, and the virtual resources include funds, so the resource transfer in the third or fourth embodiment can be a fund transfer, such as recharging from the third account to the fourth account or from the fourth account to the third account, so the third or fourth embodiment can also be a recharging method.

[0234] Payment can be used as a type of fund transfer, so the third or fourth embodiment can also be a payment method.

[0235] The fifth embodiment of this specification (hereinafter referred to as "this embodiment") provides a payment method. The execution subject of this embodiment can be a terminal (including but not limited to a mobile phone, computer, pad, TV) or a server or an operating system or a payment platform or a payment system, etc., that is, the execution subject can be various and can be set, used or changed as needed. In addition, a third-party application can also assist the execution subject in executing this embodiment. For example Figure 1 As shown, the payment method in this embodiment can be executed by the server, and an application corresponding to the server can be installed on the terminal (held by the user). Data can be transmitted between the terminal or the application and the server, and data can be collected, input or output, or pages or information processing can be performed (to the user) through the terminal or the application, thereby assisting the server in executing the payment method in this embodiment.

[0236] like Fig.14 As shown, the payment method provided in this embodiment is applied to the fifth server (that is, the execution subject is the fifth server), including:

[0237] S501: Obtain a first payment request sent by the terminal, determine a fifth account and a sixth account to be deducted funds and a payment amount; wherein the fifth account is a user login account on the fifth server, and the fifth account and the sixth account are bound using the method described in the first or second embodiment;

[0238] The fifth server in this embodiment is equivalent to any one of the first to fourth servers, or may be the target server in the second embodiment.

[0239] The fifth server may obtain a first payment request sent by a terminal (which may be referred to as a "third trigger terminal"; the first, second and third trigger terminals may be the same or different).

[0240] With reference to the first embodiment, the user may initiate a resource transfer service through an application corresponding to the fifth server, and then the third trigger terminal sends a first payment request to the fifth server.

[0241] The fifth account is an account on the fifth server, and the fifth account is determined in the same manner as the first account, for example, by user input or according to the login account of the third trigger terminal. Although the fifth server obtains the first payment request, the fifth account may not be a fund deduction account. For example, in a quick payment scenario, the third-party payment institution server obtains the first payment request sent by the user terminal, but the fund deduction account may be a financial institution account bound to the third-party payment institution account.

[0242] The sixth account from which funds are to be deducted may be determined by the user and included in the first payment request, so the fifth server may determine the sixth account based on the first payment request.

[0243] The payment amount may be included in the first payment request, so the fifth server may determine the payment amount based on the first payment request.

[0244] The fifth account and the sixth account are bound using the method described in the first or second embodiment. If (the fifth server determines) the fifth account and the sixth account are not bound when the first payment request is obtained, the fifth server can bind the fifth account and the sixth account using the data processing method of the first embodiment, just like the first server of the first embodiment.

[0245] S503: Sending a second payment request to the sixth server where the sixth account is located, so that the sixth server reduces the funds in the sixth account by the payment amount.

[0246] The second payment request may include the account data of the sixth account and the payment amount, so that after the sixth server where the sixth account is located obtains the second payment request, it determines the sixth account to be paid on the sixth server and determines the payment amount.

[0247] After reducing the funds in the sixth account by the payment amount, the sixth server may send payment feedback data to the fifth server. If the fifth server determines that the payment amount has been deducted from the sixth account according to the payment feedback data sent by the sixth server, the user feedback data may be sent to the third trigger terminal so that the second trigger terminal displays the payment result.

[0248] If the fifth server is the receiving server corresponding to the payment, after the fifth server determines that the sixth account has deducted the payment amount based on the payment feedback data sent by the sixth server, the funds in the receiving account on the fifth server can be increased by the payment amount.

[0249] If the fifth server is not the payment receiving server corresponding to the payment, after the fifth server determines that the sixth account has deducted the payment amount based on the payment feedback data sent by the sixth server, it can send a payment instruction to the payment receiving server so that the payment server increases the payment account on it by the payment amount.

[0250] Among them, the fifth server can be a third-party payment institution server, the sixth server can be a financial institution server, the fifth account can be the third-party payment institution account of the paying user, the sixth account can be the financial institution account of the paying user, and the receiving account can be the third-party payment institution account of the receiving user.

[0251] Referring to the first or second embodiment, data transmission between the fifth server and the sixth server, and between the fifth server and the payment server may be performed through an intermediate server, wherein the intermediate server includes but is not limited to a NetsUnion or UnionPay server or a payment regulatory agency server.

[0252] In this embodiment, by binding the third account and the fourth account using the method of the first or second embodiment, one-to-many account binding can be achieved at one time, thereby improving the efficiency of account binding. Payment is made through the bound account, thus further improving the payment efficiency.

[0253] The sixth embodiment of this specification (hereinafter referred to as "this embodiment") provides a payment method. The execution subject of this embodiment can be a terminal (including but not limited to a mobile phone, computer, pad, TV) or a server or an operating system or a payment platform or a payment system, etc., that is, the execution subject can be various and can be set, used or changed as needed. In addition, a third-party application can also assist the execution subject in executing this embodiment. For example Figure 1 As shown, the payment method in this embodiment can be executed by the server, and an application corresponding to the server can be installed on the terminal (held by the user). Data can be transmitted between the terminal or the application and the server, and data can be collected, input or output, or pages or information processing can be performed (to the user) through the terminal or the application, thereby assisting the server in executing the payment method in this embodiment.

[0254] like Fig.15 As shown, the payment method provided in this embodiment is applied to the sixth server (that is, the execution subject is the sixth server), including:

[0255] S602: If the payment request sent by the fifth server is obtained, determining a sixth account on the sixth server from which funds are to be deducted, and determining a payment amount;

[0256] The sixth server in this embodiment is equivalent to any one of the first to fourth servers, or may be the target server in the second embodiment. The payment request in this embodiment is the second payment request in the fourth embodiment.

[0257] S604: reducing the funds in the sixth account by the payment amount, and sending payment feedback data to the fifth server;

[0258] The sixth account is bound to the fifth account on the fifth server using the method described in the first or second embodiment, the fifth account is a user login account on the fifth server, and the fifth account is used to receive payment requests sent by a terminal.

[0259] For the contents not described in detail in this embodiment, please refer to the fourth embodiment.

[0260] In this embodiment, by binding the third account and the fourth account using the method of the first or second embodiment, one-to-many account binding can be achieved at one time, thereby improving the efficiency of account binding. Payment is made through the bound account, thus further improving the payment efficiency.

[0261] It should be noted that the first and second servers in the first or second embodiment may be located in different countries or regions (the intermediate server may be in the same country or region as the first or second server, or the intermediate server may be in a different country or region from the first or second server), thereby realizing (one-to-many) account binding between different countries or regions. Similarly, the third and fourth servers (and intermediate servers) in the third or fourth embodiment or the fifth and sixth servers (and intermediate servers) in the fifth or sixth embodiment may also be located in different countries or regions, thereby realizing resource transfer or payment between different countries or regions.

[0262] like Fig.16 As shown, the seventh embodiment of this specification provides a data processing device, including:

[0263] A pre-binding module 701 is used to obtain a user binding request sent by a terminal, determine a first account to be bound on the device, and send user binding request feedback data to the terminal so that the terminal displays candidate binding objects;

[0264] The initial binding module 703 is used to obtain the binding object selection data sent by the terminal, determine each target binding object according to the binding object selection data, and determine one or more target servers among the servers corresponding to each target binding object;

[0265] Account binding module 705, used for

[0266] Binding the first account to a second account on each of the target servers, and sending an account binding request to each of the target servers, so that any of the target servers binds the second account on the target server to the first account;

[0267] The second account and the first account correspond to the same user identity data.

[0268] Optionally, the device also includes a first server, and the first account is an account on the first server.

[0269] Optionally, the preliminary binding module 701 is also used to send an identity authentication request or a binding consultation request to the server corresponding to each target binding object before sending an account binding request to each target server. The identity authentication request or binding consultation request includes the user identity data corresponding to the first account, so that any server corresponding to each target binding object can determine a second account on the server that corresponds to the same user identity data as the first account.

[0270] Optionally, the preliminary binding module 701 is also used to, after sending an identity authentication request or a binding consultation request to any server corresponding to each of the target binding objects, obtain authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, and determine the second account on the server based on the authentication feedback data or consultation feedback data sent by the server.

[0271] Optionally, the preliminary binding module 701 is also used to send candidate account data to the terminal after determining the second account on the server based on the authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, and before determining one or more target servers, wherein the candidate account data is used to enable the terminal to display the second account determined by the server corresponding to each of the target binding objects.

[0272] Optionally, the preliminary binding module 701 is further configured to, after sending an identity authentication request or a binding consultation request to any server corresponding to each target binding object,

[0273] Obtain authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects. If it is determined that the second account does not exist on a server corresponding to the target binding object, the candidate account data is also used to enable the terminal to display a first prompt message, and the first prompt message is used to prompt that the target binding object corresponding to the server where the second account does not exist has no bindable account.

[0274] Optionally, the preliminary binding module 701 is also used to, after sending an identity authentication request or a binding consultation request to any server corresponding to each of the target binding objects, obtain authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects. If it is determined that the second account does not exist on a server corresponding to the target binding object, the candidate account data is also used to enable the terminal to display a second prompt message, and the second prompt message is also used to prompt the user to open an account of the target binding object corresponding to the server where the second account does not exist.

[0275] Optionally, the pre-binding module 701 is further configured to, after sending the candidate account data to the terminal, obtain a user activation request sent by the terminal, and determine one or more account activation servers according to the user activation request;

[0276] An account opening request is sent to each of the account opening servers, so that each of the account opening servers opens a second account corresponding to the same user identity data as the first account.

[0277] Optionally, the pre-binding module 701 is further configured to, after sending an account activation request to each of the account activation servers, obtain activation feedback data sent by any of the account activation servers, and determine the second account activated by the account activation server according to the activation feedback data;

[0278] Sending candidate account supplementary data to the terminal, wherein the candidate account supplementary data is used to enable the terminal to display the second accounts opened by each of the account opening servers.

[0279] Optionally, the preliminary binding module 701 is also used to, after obtaining authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, determine the second account recommended for binding on the server according to the authentication feedback or consultation feedback data sent by the server.

[0280] Optionally, the candidate account data is also used to enable the terminal to display first recommendation information, where the first recommendation information is used to prompt a second account to be recommended for binding.

[0281] Optionally, the pre-binding module 701 is further configured to determine the second account on the server according to the authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, and then determine the recommended second account for binding from each of the second accounts on the server corresponding to each of the target binding objects;

[0282] The candidate account data is further used to enable the terminal to display second recommendation information, where the second recommendation information is used to prompt a second account to be recommended for binding.

[0283] Optionally, determining the recommended second account for binding from the second accounts of the server corresponding to the target binding objects includes:

[0284] According to the historical interaction data between the first server and the server corresponding to each of the target binding objects, the recommended second account for binding is determined from the second accounts of the server corresponding to each of the target binding objects.

[0285] Optionally, for any target server, if there are multiple second accounts on the target server, sending an account binding request to each of the target servers so that any of the target servers binds the second account on the target server to the first account includes:

[0286] An account binding request is sent to each of the target servers, so that any of the target servers binds one of the second accounts on the target server to the first account.

[0287] Optionally, determining one or more target servers from the servers corresponding to each of the target binding objects includes:

[0288] The binding account selection data sent by the terminal is obtained, one or more selected second accounts are determined according to the binding account selection data, and a server where the one or more selected second accounts are located is used as a target server.

[0289] Optionally, binding the first account to a second account on each of the target servers, and sending an account binding request to each of the target servers so that any of the target servers binds the second account on the target server to the first account includes:

[0290] Sending an account binding request to each of the target servers so that any of the target servers binds the second account on the target server to the first account; obtaining account binding request feedback data sent by any of the target servers, and if it is determined according to the account binding request feedback data that the target server has bound the second account on the target server to the first account, binding the first account to the second account on the target server; or,

[0291] After binding the first account with a second account of any target server, an account binding request is sent to the target server, so that the target server binds the second account on the target server to the first account.

[0292] Optionally, the device further comprises:

[0293] The sending module is used to send user feedback data to the terminal so that the terminal displays the account binding result.

[0294] Optionally, the first account is a login account of the terminal when obtaining the account binding request;

[0295] or,

[0296] The first account is determined according to the account binding request.

[0297] Optionally, the account binding request includes user identity data corresponding to the first account.

[0298] Optionally, the first account or the second account is a resource storage or resource transfer account.

[0299] Optionally, if the first server sends any request or any data to any server corresponding to each target binding object, the first server sends the any request or any data to the intermediate server, and the intermediate server sends the any request or any data to any server corresponding to each target binding object.

[0300] like Fig.17 As shown, the eighth embodiment of this specification provides a data processing device, including:

[0301] The pre-binding module 802 is used to determine a second account on the device corresponding to the same user identity data as the first account if an identity authentication request or binding consultation request sent by the first server is obtained, and the identity authentication request or binding consultation request includes user identity data corresponding to the first account; wherein the first account is an account on the first server; and send authentication feedback data or consultation feedback data to the first server, wherein the authentication feedback data or consultation feedback data includes account data of the second account, so that the first server determines one or more target servers and sends an account binding request to each of the target servers;

[0302] The account binding module 804 is configured to bind the second account to the first account if an account binding request sent by the first server is obtained.

[0303] Optionally, the device also includes a second server, and the second account is an account on the second server.

[0304] Optionally, after obtaining the identity authentication request or binding consultation request sent by the first server, if the preliminary binding module 802 determines that there is no account on the second server corresponding to the same user identity data as the first account, then the authentication feedback data or consultation feedback data is used to enable the first server to determine that there is no account on the second server corresponding to the same user identity data as the first account.

[0305] Optionally, the pre-binding module 802 is further configured to, if an account opening request sent by the first server is received, open a second account corresponding to the same user identity data as the first account according to the account opening request;

[0306] Sending activation feedback data to the first server, wherein the activation feedback data includes account data of a second account activated according to the account activation request.

[0307] Optionally, after obtaining the identity authentication request or binding consultation request sent by the first server, if the preliminary binding module 802 determines that there are multiple second accounts, the authentication feedback data or consultation feedback data also includes account data of the recommended account, and the recommended account is one or more second accounts.

[0308] Optionally, the preliminary binding module 802 is further configured to determine the recommended account according to the historical account operation data of the plurality of second accounts.

[0309] Optionally, if there are multiple second accounts, binding the second account to the first account includes:

[0310] Determine a second account to be bound from the multiple second accounts according to the account binding request, and bind the second account to be bound to the first account.

[0311] Optionally, if there are multiple second accounts, binding the second account to the first account includes:

[0312] A second account to be bound is determined from the multiple second accounts, and the second account to be bound is bound to the first account.

[0313] Optionally, the device further comprises:

[0314] The sending module is used to send account binding request feedback data to the first server after binding the second account to the first account.

[0315] Optionally, if the second server sends any request or any data to the first server, the second server sends the any request or any data to the intermediate server, and the intermediate server sends the any request or any data to the second server.

[0316] like Fig.18 As shown, the ninth embodiment of this specification provides a resource transfer device, including:

[0317] The transfer initiation module 901 is used to obtain a first resource transfer request sent by the terminal, determine a third account and a fourth account to be transferred resources, and a resource transfer amount; wherein the third account is an account on the device, and the third account and the fourth account are bound using the method described in the first or second embodiment;

[0318] The transfer module 903 is configured to send a second resource transfer request to the fourth server where the fourth account is located, so that the fourth server reduces the resources of the fourth account by the resource transfer amount; obtain resource transfer feedback data sent by the fourth server, and if it is determined according to the resource transfer feedback data that the resources of the fourth account are reduced by the resource transfer amount, then increase the resources of the third account by the resource transfer amount; or,

[0319] The resources of the third account are reduced by the resource transfer amount, and a second resource transfer request is sent to the fourth server where the fourth account is located, so that the fourth server increases the resources of the fourth account by the resource transfer amount.

[0320] Optionally, the device also includes a third server, and the third account is an account on the third server.

[0321] like Fig.19 As shown, the tenth embodiment of this specification provides a resource transfer device, including:

[0322] The transfer acceptance module 1002 is used to determine a fourth account on the device to which resources are to be transferred and determine a resource transfer amount if a resource transfer request sent by the third server is obtained;

[0323] The transfer module 1004 is configured to reduce the resources of the fourth account by the resource transfer amount, and send resource transfer feedback data to the third server so that the third server increases the resources of the third account to be transferred by the resource transfer amount; or

[0324] If it is determined according to the resource transfer request that the third server reduces the resources of the third account to be transferred by the resource transfer amount, then the resources of the fourth account are increased by the resource transfer amount;

[0325] The third account is an account on the third server, and the third account is bound to the fourth account using the method described in the first or second embodiment.

[0326] Optionally, the device further includes a fourth server, and the fourth account is an account on the fourth server.

[0327] like Fig. 20As shown, the eleventh embodiment of this specification provides a payment device, including:

[0328] The payment initiation module 1101 is used to obtain the first payment request sent by the terminal, determine the fifth account and the sixth account to be deducted funds and the payment amount; wherein the fifth account is the user login account on the device, and the fifth account and the sixth account are bound using the method described in the first or second embodiment;

[0329] The payment module 1103 is used to send a second payment request to the sixth server where the sixth account is located, so that the sixth server reduces the funds in the sixth account by the payment amount.

[0330] Optionally, the device also includes a fifth server, and the fifth account is an account on the fifth server.

[0331] like Fig.21 As shown, the twelfth embodiment of this specification provides a payment device, including:

[0332] The payment acceptance module 1202 is used to determine a sixth account on the device from which funds are to be deducted and a payment amount if a payment request sent by the fifth server is obtained;

[0333] A payment module 1204, configured to reduce the funds in the sixth account by the payment amount and send payment feedback data to the fifth server;

[0334] The sixth account is bound to the fifth account on the fifth server using the method described in the first or second embodiment, the fifth account is a user login account on the fifth server, and the fifth account is used to receive payment requests sent by a terminal.

[0335] Optionally, the device further includes a sixth server, and the sixth account is an account on the sixth server.

[0336] It should be noted that the apparatus in the seventh or eighth embodiment may be located in different countries or regions (the intermediate server may be in the same country or region as the apparatus in the seventh or eighth embodiment, or the intermediate server may be in a different country or region from the apparatus in the seventh or eighth embodiment), thereby realizing (one-to-many) account binding between different countries or regions. Similarly, the apparatus (and intermediate server) in the ninth or tenth embodiment or the apparatus (and intermediate server) in the eleventh or twelfth embodiment may also be located in different countries or regions, thereby realizing resource transfer or payment between different countries or regions.

[0337] A thirteenth embodiment of the present specification provides a data processing device, including:

[0338] at least one processor; and a memory communicatively coupled to the at least one processor;

[0339] in,

[0340] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to execute the data processing method described in the first or second embodiment.

[0341] A fourteenth embodiment of the present specification provides a resource transfer device, including:

[0342] at least one processor; and a memory communicatively coupled to the at least one processor;

[0343] in,

[0344] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to execute the resource transfer method described in the third or fourth embodiment.

[0345] The fifteenth embodiment of the present specification provides a payment device, including:

[0346] at least one processor; and a memory communicatively coupled to the at least one processor;

[0347] in,

[0348] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to execute the payment method described in the fifth or sixth embodiment.

[0349] The sixteenth embodiment of the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the data processing method described in the first or second embodiment is implemented.

[0350] The seventeenth embodiment of the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the resource transfer method described in the third or fourth embodiment is implemented.

[0351] The seventeenth embodiment of the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the payment method described in the fifth or sixth embodiment is implemented.

[0352] It should be noted that the data processing device executing the first embodiment and the data processing device executing the second embodiment may be located in different countries or regions, thereby realizing (one-to-many) account binding between different countries or regions. Similarly, the resource transfer device executing the third embodiment and the resource transfer device executing the fourth embodiment, the payment device executing the fifth embodiment and the payment device executing the sixth embodiment may be located in different countries or regions, thereby realizing resource transfer or payment between different countries or regions.

[0353] It should be noted that the computer-readable storage medium for implementing the first embodiment and the computer-readable storage medium for implementing the second embodiment may be located in different countries or regions, thereby realizing (one-to-many) account binding between different countries or regions. Similarly, the computer-readable storage medium for implementing the third embodiment and the computer-readable storage medium for implementing the fourth embodiment, the computer-readable storage medium for implementing the fifth embodiment, and the computer-readable storage medium for implementing the sixth embodiment may be located in different countries or regions, thereby realizing resource transfer or payment between different countries or regions.

[0354] The above embodiments may be used in combination, and modules with the same name between different embodiments or within the same embodiment may be the same or different.

[0355] The above describes specific embodiments of the present specification, and other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily have to be performed in the specific order or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0356] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer-readable storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0357] The apparatus, device, non-volatile computer-readable storage medium and method provided in the embodiments of this specification correspond to each other, and therefore, the apparatus, device, and non-volatile computer storage medium also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the corresponding apparatus, device, and non-volatile computer storage medium will not be repeated here.

[0358] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0359] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0360] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0361] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0362] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may be in the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0363] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0364] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0365] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0366] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0367] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0368] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0369] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0370] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0371] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0372] The above is only an embodiment of this specification and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A data processing method, applied to a first server, comprising: Acquire a user binding request sent by the terminal, determine a first account to be bound on the first server, and send user binding request feedback data to the terminal so that the terminal displays candidate binding objects; Acquire binding object selection data sent by the terminal, determine each target binding object according to the binding object selection data, and determine one or more target servers among the servers corresponding to each target binding object; Binding the first account to a second account on each of the target servers, and sending an account binding request to each of the target servers so that any of the target servers binds the second account on the target server to the first account; including: after any of the target servers binds the second account on the target server to the first account, binding the first account to the second account on the target server; or, after binding the first account to the second account on any of the target servers, binding the second account on the target server to the first account by any of the target servers; The second account and the first account correspond to the same user identity data.

2. The method according to claim 1, before sending the account binding request to each target server, the method further comprises: An identity authentication request or a binding consultation request is sent to the server corresponding to each of the target binding objects, wherein the identity authentication request or the binding consultation request includes the user identity data corresponding to the first account, so that any server corresponding to each of the target binding objects can determine a second account on the server that has the same user identity data as the first account.

3. The method according to claim 2, after sending an identity authentication request or a binding consultation request to any server corresponding to each of the target binding objects, the method further comprises: Acquire authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, and determine the second account on the server according to the authentication feedback data or consultation feedback data sent by the server.

4. The method according to claim 3, after determining the second account on the server according to the authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, and before determining one or more target servers, the method further comprises: Sending candidate account data to the terminal, the candidate account data is used to enable the terminal to display the second account determined by the server corresponding to each of the target binding objects.

5. The method according to claim 4, after sending an identity authentication request or a binding consultation request to any server corresponding to each of the target binding objects, the method further comprises: Obtain authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects. If it is determined that the second account does not exist on a server corresponding to the target binding object, the candidate account data is also used to enable the terminal to display a first prompt message, and the first prompt message is used to prompt that the target binding object corresponding to the server where the second account does not exist has no bindable account.

6. The method according to claim 4, after sending an identity authentication request or a binding consultation request to any server corresponding to each of the target binding objects, the method further comprises: Obtain authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects. If it is determined that the second account does not exist on a server corresponding to the target binding object, the candidate account data is also used to enable the terminal to display a second prompt message, and the second prompt message is also used to prompt the user to open an account of the target binding object corresponding to the server where the second account does not exist.

7. The method according to claim 6, after sending the candidate account data to the terminal, the method further comprises: Obtaining a user activation request sent by a terminal, and determining one or more account activation servers according to the user activation request; An account opening request is sent to each of the account opening servers, so that each of the account opening servers opens a second account corresponding to the same user identity data as the first account.

8. The method according to claim 7, after sending the account opening request to each of the account opening servers, the method further comprises: Acquire activation feedback data sent by any of the account activation servers, and determine the second account activated by the account activation server according to the activation feedback data; Sending candidate account supplementary data to the terminal, wherein the candidate account supplementary data is used to enable the terminal to display the second accounts opened by each of the account opening servers.

9. The method according to claim 3, after obtaining the authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, the method further comprises: The second account recommended for binding on the server is determined according to the authentication feedback or consultation feedback data sent by the server.

10. The method according to claim 9, wherein the candidate account data is further used to enable the terminal to display first recommendation information, wherein the first recommendation information is used to prompt a second account to be recommended for binding.

11. The method according to claim 4, after determining the second account on the server according to the authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, the method further comprises: Determining a second account recommended for binding from each second account of the server corresponding to each of the target binding objects; The candidate account data is further used to enable the terminal to display second recommendation information, where the second recommendation information is used to prompt a second account to be recommended for binding.

12. The method according to claim 11, wherein determining the recommended second account for binding from the second accounts of the server corresponding to each of the target binding objects comprises: According to the historical interaction data between the first server and the server corresponding to each of the target binding objects, the recommended second account for binding is determined from the second accounts of the server corresponding to each of the target binding objects.

13. The method of claim 1, wherein for any target server, if there are multiple second accounts on the target server, sending an account binding request to each of the target servers so that any of the target servers binds the second account on the target server to the first account comprises: An account binding request is sent to each of the target servers, so that any of the target servers binds one of the second accounts on the target server to the first account.

14. The method according to claim 4, wherein determining one or more target servers among the servers corresponding to each of the target binding objects comprises: The binding account selection data sent by the terminal is obtained, one or more selected second accounts are determined according to the binding account selection data, and a server where the one or more selected second accounts are located is used as a target server.

15. The method of claim 1, binding the first account to the second account on each of the target servers, and sending an account binding request to each of the target servers so that any of the target servers binds the second account on the target server to the first account, comprises: Sending an account binding request to each of the target servers, so that any of the target servers binds the second account on the target server to the first account; Obtaining account binding request feedback data sent by any of the target servers, and if it is determined according to the account binding request feedback data that the target server has bound the second account on the target server to the first account, binding the first account to the second account on the target server; or, After binding the first account with a second account of any target server, an account binding request is sent to the target server, so that the target server binds the second account on the target server to the first account.

16. The method of claim 1, further comprising: Sending user feedback data to the terminal so that the terminal displays the account binding result.

17. The method according to claim 1, wherein the first account is a login account of the terminal when obtaining the account binding request; or, The first account is determined according to the account binding request.

18. The method of claim 1, wherein the account binding request includes user identity data corresponding to the first account.

19. The method of claim 1, wherein the first account or the second account is a resource storage or resource transfer account.

20. According to the method described in any one of claims 1 to 19, if the first server sends any request or any data to any server corresponding to each target binding object, the first server sends the arbitrary request or any data to the intermediate server, and the intermediate server sends the arbitrary request or any data to any server corresponding to each target binding object.

21. A data processing method, applied to a second server, comprising: If an identity authentication request or a binding consultation request sent by the first server is obtained, and the identity authentication request or the binding consultation request includes the user identity data corresponding to the first account, then determining a second account on the second server that has the same user identity data as the first account; wherein the first account is an account on the first server; Sending authentication feedback data or consultation feedback data to the first server, wherein the authentication feedback data or consultation feedback data includes account data of the second account, so that the first server determines one or more target servers and sends an account binding request to each of the target servers; If the account binding request sent by the first server is obtained, the second account is bound to the first account; including: generating and storing a binding relationship between the second account and the first account.

22. According to the method as claimed in claim 21, after obtaining the identity authentication request or binding consultation request sent by the first server, if there is no account on the second server corresponding to the same user identity data as the first account, then the authentication feedback data or consultation feedback data is used to enable the first server to determine that there is no account on the second server corresponding to the same user identity data as the first account.

23. The method of claim 21, if an account opening request sent by the first server is received, opening a second account corresponding to the same user identity data as the first account according to the account opening request; Sending activation feedback data to the first server, wherein the activation feedback data includes account data of a second account activated according to the account activation request.

24. The method of claim 21, wherein if there are multiple second accounts, the authentication feedback data or consultation feedback data further includes account data of a recommended account, and the recommended account is one or more second accounts.

25. The method of claim 24, wherein the recommended account is determined based on historical account operation data of the plurality of second accounts.

26. The method of claim 21, if there are multiple second accounts, binding the second account to the first account comprises: Determine a second account to be bound from the multiple second accounts according to the account binding request, and bind the second account to be bound to the first account.

27. The method of claim 21, if there are multiple second accounts, binding the second account to the first account comprises: A second account to be bound is determined from the multiple second accounts, and the second account to be bound is bound to the first account.

28. The method of claim 21, after binding the second account to the first account, the method further comprises: Sending account binding request feedback data to the first server.

29. According to the method described in any one of claims 21 to 28, if the second server sends any request or any data to the first server, the second server sends the arbitrary request or any data to the intermediate server, and the intermediate server sends the arbitrary request or any data to the second server.

30. A resource transfer method, applied to a third server, comprising: Acquire a first resource transfer request sent by a terminal, determine a third account and a fourth account to be transferred resources and a resource transfer amount; wherein the third account is an account on the third server, and the third account and the fourth account are bound using the method described in any one of claims 1 to 29; Sending a second resource transfer request to a fourth server where the fourth account is located, so that the fourth server reduces the resources of the fourth account by the resource transfer amount; obtaining resource transfer feedback data sent by the fourth server, and if it is determined according to the resource transfer feedback data that the resources of the fourth account are reduced by the resource transfer amount, then increasing the resources of the third account by the resource transfer amount; or, The resources of the third account are reduced by the resource transfer amount, and a second resource transfer request is sent to the fourth server where the fourth account is located, so that the fourth server increases the resources of the fourth account by the resource transfer amount.

31. A resource transfer method, applied to a fourth server, comprising: If the resource transfer request sent by the third server is obtained, determining a fourth account on the fourth server to which the resource transfer is to be performed, and determining the resource transfer amount; reducing the resources of the fourth account by the resource transfer amount, and sending resource transfer feedback data to the third server, so that the third server increases the resources of the third account to be transferred by the resource transfer amount; or, If it is determined according to the resource transfer request that the third server reduces the resources of the third account to be transferred by the resource transfer amount, then the resources of the fourth account are increased by the resource transfer amount; The third account is an account on the third server, and the third account is bound to the fourth account using the method described in any one of claims 1 to 29.

32. A payment method, applied to a fifth server, comprising: Obtaining a first payment request sent by the terminal, determining a fifth account and a sixth account to be deducted funds and a payment amount; wherein the fifth account is a user login account on the fifth server, and the fifth account and the sixth account are bound using the method described in any one of claims 1 to 29; A second payment request is sent to a sixth server where the sixth account is located, so that the sixth server reduces the funds in the sixth account by the payment amount.

33. A payment method, applied to a sixth server, comprising: If the payment request sent by the fifth server is obtained, determining a sixth account on the sixth server from which funds are to be deducted, and determining a payment amount; reducing the funds in the sixth account by the payment amount, and sending payment feedback data to the fifth server; The sixth account is bound to the fifth account on the fifth server using the method described in any one of claims 1 to 29, the fifth account is a user login account on the fifth server, and the fifth account is used to receive payment requests sent by a terminal.

34. A data processing device, comprising: a pre-binding module, configured to obtain a user binding request sent by a terminal, determine a first account to be bound on the device, and send user binding request feedback data to the terminal so that the terminal displays candidate binding objects; An initial binding module, used to obtain binding object selection data sent by the terminal, determine each target binding object according to the binding object selection data, and determine one or more target servers among the servers corresponding to each target binding object; An account binding module is used to bind the first account to a second account on each of the target servers, and send an account binding request to each of the target servers, so that any of the target servers binds the second account on the target server to the first account; including: after any of the target servers binds the second account on the target server to the first account, the first account is bound to the second account on the target server; or after the first account is bound to the second account on any of the target servers, any of the target servers binds the second account on the target server to the first account; The second account and the first account correspond to the same user identity data.

35. The apparatus of claim 34, further comprising a first server, wherein the first account is an account on the first server.

36. A data processing device, comprising: A preparatory binding module, for determining a second account on the device corresponding to the same user identity data as the first account if an identity authentication request or binding consultation request sent by the first server is obtained, and the identity authentication request or binding consultation request includes user identity data corresponding to the first account; wherein the first account is an account on the first server; and sending authentication feedback data or consultation feedback data to the first server, wherein the authentication feedback data or consultation feedback data includes account data of the second account, so that the first server determines one or more target servers and sends an account binding request to each of the target servers; The account binding module is used to bind the second account to the first account if the account binding request sent by the first server is obtained; including: generating and storing a binding relationship between the second account and the first account.

37. The apparatus of claim 36, further comprising a second server, wherein the second account is an account on the second server.

38. A resource transfer device, comprising: a transfer initiating module, configured to obtain a first resource transfer request sent by a terminal, determine a third account and a fourth account to be transferred resources, and a resource transfer amount; wherein the third account is an account on the device, and the third account and the fourth account are bound using the method according to any one of claims 1 to 29; a transfer module, configured to send a second resource transfer request to a fourth server where the fourth account is located, so that the fourth server reduces the resources of the fourth account by the resource transfer amount; obtain resource transfer feedback data sent by the fourth server, and if it is determined according to the resource transfer feedback data that the resources of the fourth account are reduced by the resource transfer amount, then increase the resources of the third account by the resource transfer amount; or, The resources of the third account are reduced by the resource transfer amount, and a second resource transfer request is sent to the fourth server where the fourth account is located, so that the fourth server increases the resources of the fourth account by the resource transfer amount.

39. The apparatus of claim 38, further comprising a third server, wherein the third account is an account on the third server.

40. A resource transfer device, comprising: a transfer acceptance module, configured to determine a fourth account on the device to which resources are to be transferred and an amount of resources to be transferred if a resource transfer request sent by a third server is obtained; a transfer module, configured to reduce the resources of the fourth account by the resource transfer amount, and send resource transfer feedback data to the third server, so that the third server increases the resources of the third account to be transferred by the resource transfer amount; or, If it is determined according to the resource transfer request that the third server reduces the resources of the third account to be transferred by the resource transfer amount, then the resources of the fourth account are increased by the resource transfer amount; The third account is an account on the third server, and the third account is bound to the fourth account using the method described in any one of claims 1 to 29.

41. The apparatus of claim 40, further comprising a fourth server, wherein the fourth account is an account on the fourth server.

42. A payment device, comprising: a payment initiation module, configured to obtain a first payment request sent by a terminal, determine a fifth account and a sixth account to be deducted funds, and a payment amount; wherein the fifth account is a user login account on the device, and the fifth account and the sixth account are bound using the method described in any one of claims 1 to 29; The payment module is used to send a second payment request to a sixth server where the sixth account is located, so that the sixth server reduces the funds in the sixth account by the payment amount.

43. The apparatus of claim 42, further comprising a fifth server, wherein the fifth account is an account on the fifth server.

44. A payment device, comprising: a payment acceptance module, configured to determine a sixth account on the device from which funds are to be deducted and a payment amount if a payment request sent by the fifth server is obtained; a payment module, configured to reduce the funds in the sixth account by the payment amount and send payment feedback data to the fifth server; The sixth account is bound to the fifth account on the fifth server using the method described in any one of claims 1 to 29, the fifth account is a user login account on the fifth server, and the fifth account is used to receive payment requests sent by a terminal.

45. The apparatus of claim 44, further comprising a sixth server, wherein the sixth account is an account on the sixth server.

46. ​​A data processing device comprising: at least one processor; as well as, a memory communicatively coupled to the at least one processor; in, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the data processing method according to any one of claims 1 to 20 or 21 to 29.

47. A resource transfer device, comprising: at least one processor; as well as, a memory communicatively coupled to the at least one processor; in, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the resource transfer method described in claim 30 or 31.

48. A payment device comprising: at least one processor; as well as, a memory communicatively coupled to the at least one processor; in, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the payment method described in claim 32 or 33.

49. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the data processing method described in any one of claims 1 to 20 or 21 to 29.

50. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the resource transfer method of claim 30 or 31.

51. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the payment method of claim 32 or 33.

Images