Data processing method and device, resource transfer method and device, payment method and device, equipment and medium

Abstract

The embodiment of the invention discloses a data processing method, which comprises the following steps: acquiring a user binding request, determining a first account to be bound on a first server, sending user binding request feedback data, and enabling a terminal to display candidate binding objects; obtaining binding object selection data, determining each target binding object, and determining a target server in 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, so that any target server binds the second account to the first account; the second account and the first account correspond to the same user identity data.

Description

[0001] This application is a divisional application of a patent application with an application date of September 28, 2020, an application number of 202011039604.9, and an invention title of "A Data Processing, Resource Transfer, Payment Method, Device, Equipment and Medium". Technical Field

[0002] This 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

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

[0004] In view of this, a more efficient data processing solution for account binding services is needed. Summary of the Invention

[0005] 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.

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

[0007] Embodiments of this specification provide a first data processing method, which is applied to a first server and includes:

[0008] Obtain a user binding request sent by a 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;

[0009] 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 in the servers corresponding to each target binding object;

[0010] Bind the first account to the second accounts on each target server, and send an account binding request to each target server so that any one of the target servers binds the second account on the target server to the first account;

[0011] Wherein, the second account corresponds to the same user identity data as the first account.

[0012] Embodiments of this specification provide a second data processing method, which is applied to a second server and includes:

[0013] 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 contains 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.

[0014] Send authentication feedback data or consultation feedback data to the first server, where the authentication feedback data or the consultation feedback data contains 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.

[0015] If an account binding request sent by the first server is obtained, then bind the second account to the first account.

[0016] The embodiments of this specification provide a first resource transfer method, which is applied to a third server and includes:

[0017] Obtain a first resource transfer request sent by a terminal, and determine a third account and a fourth account for which resource transfer is to be performed and the resource transfer amount; wherein, the third account is an account on the third server, and the third account and the fourth account are bound by using the above first or second data processing method.

[0018] 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 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 increase the resources of the third account by the resource transfer amount; or,

[0019] 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.

[0020] The embodiments of this specification provide a second resource transfer method, which is applied to a fourth server and includes:

[0021] If a resource transfer request sent by a third server is obtained, then determine the fourth account on the fourth server for which resource transfer is to be performed, and determine the resource transfer amount.

[0022] 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,

[0023] If it is determined according to the resource transfer request that the resources of the third account on the third server for which resource transfer is to be performed are reduced by the resource transfer amount, then the resources of the fourth account are increased by the resource transfer amount;

[0024] Wherein, the third account is an account on the third server, and the third account and the fourth account are bound by the above first or second data processing method.

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

[0026] Obtain a first payment request sent by a terminal, and determine a fifth account, a sixth account for which funds are to be deducted, 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 by the above first or second data processing method;

[0027] Send a second payment request to the sixth server where the sixth account is located, so that the sixth server reduces the funds of the sixth account by the payment amount.

[0028] The embodiment of the present specification provides a second payment method, which is applied to a sixth server and includes:

[0029] If a payment request sent by the fifth server is obtained, then determine the sixth account on the sixth server for which funds are to be deducted, and determine the payment amount;

[0030] Reduce the funds of the sixth account by the payment amount, and send payment feedback data to the fifth server;

[0031] Wherein, the sixth account and the fifth account on the fifth server are bound by the above first or second data processing method, the fifth account is a user login account on the fifth server, and the fifth account is used to receive payment requests sent by the terminal.

[0032] The embodiment of the present specification provides a data processing device, including:

[0033] A preliminary 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;

[0034] An initial binding module, configured 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 in the servers corresponding to each of the target binding objects;

[0035] An account binding module, configured to

[0036] bind the first account to the second accounts on each of the target servers, and send an account binding request to each of the target servers, so that any one of the target servers binds the second account on that target server to the first account;

[0037] wherein, the second accounts correspond to the same user identity data as the first account.

[0038] An embodiment of this specification provides a data processing device, including:

[0039] A preliminary binding module, configured to, if an identity authentication request or a binding consultation request sent by a first server is obtained, and the identity authentication request or the binding consultation request includes user identity data corresponding to a first account, determine a second account on the device that corresponds to the same user identity data as 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, the authentication feedback data or the consultation feedback data including 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;

[0040] An account binding module, configured to, if an account binding request sent by the first server is obtained, bind the second account to the first account.

[0041] An embodiment of this specification provides a resource transfer device, including:

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

[0043] 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 amount of resource transfer; 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 amount of resource transfer, increase the resources of the third account by the amount of resource transfer; or,

[0044] reduce the resources of the third account by the amount of resource transfer, and send a second resource transfer request to a fourth server where the fourth account is located, so that the fourth server increases the resources of the fourth account by the amount of resource transfer.

[0045] An embodiment of this specification provides a resource transfer device, including:

[0046] A transfer acceptance module, configured to, if a resource transfer request sent by a third server is obtained, determine a fourth account on the device for which resource transfer is to be performed, and determine the resource transfer amount;

[0047] 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 a third account for which resource transfer is to be performed by the resource transfer amount; or,

[0048] if it is determined according to the resource transfer request that the resources of the third account for which resource transfer is to be performed on the third server are reduced by the resource transfer amount, increase the resources of the fourth account by the resource transfer amount;

[0049] wherein, the third account is an account on the third server, and the third account and the fourth account are bound by using the above first or second data processing method.

[0050] An embodiment of this specification provides a payment device, including:

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

[0052] A payment module, configured to send a second payment request to a sixth server where the sixth account is located, so that the sixth server reduces the funds of the sixth account by the payment amount.

[0053] An embodiment of this specification provides a payment device, including:

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

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

[0056] wherein, the sixth account and a fifth account on the fifth server are bound by using the above first or second data processing method, 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.

[0057] An embodiment of this specification provides a data processing device, including:

[0058] At least one processor;

[0059] And,

[0060] A memory communicatively connected to the at least one processor;

[0061] Wherein,

[0062] The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the above-mentioned first or second data processing method.

[0063] An embodiment of this specification provides a resource transfer device, including:

[0064] At least one processor;

[0065] And,

[0066] A memory communicatively connected to the at least one processor;

[0067] Wherein,

[0068] The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the above-mentioned first or second resource transfer method.

[0069] An embodiment of this specification provides a payment device, including:

[0070] At least one processor;

[0071] And,

[0072] A memory communicatively connected to the at least one processor;

[0073] Wherein,

[0074] The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the above-mentioned first or second payment method.

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

[0076] An embodiment of this specification provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the first or second resource transfer method described above.

[0077] An embodiment of this specification provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the first or second payment method described above.

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

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

[0080] To more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following will briefly introduce the drawings required for the description of the embodiments of this specification or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in this specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

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

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

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

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

[0085] Figure 5 It is another schematic diagram of a page in the first embodiment of this specification.

[0086] Figure 6 It is another schematic diagram of a page in the first embodiment of this specification.

[0087] Figure 7 It is another schematic diagram of a page in the first embodiment of this specification.

[0088] Figure 8 It is another schematic diagram of a page in the first embodiment of this specification.

[0089] Figure 9 It is another page schematic diagram in the first embodiment of this specification.

[0090] Figure 10 It is another page schematic diagram in the first embodiment of this specification.

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

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

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

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

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

[0096] Figure 16 It is a structural schematic diagram of the data processing device in the seventh embodiment of this specification.

[0097] Figure 17 It is a structural schematic diagram of the data processing device in the eighth embodiment of this specification.

[0098] Figure 18 It is a structural schematic diagram of the resource transfer device in the ninth embodiment of this specification.

[0099] Figure 19 It is a structural schematic diagram of the resource transfer device in the tenth embodiment of this specification

[0100] Figure 20 It is a structural schematic diagram of the payment device in the eleventh embodiment of this specification.

[0101] Figure 21 It is a structural schematic diagram of the payment device in the twelfth embodiment of this specification. Detailed implementation manners

[0102] To enable those skilled in the art to better understand the technical solutions in this specification, the following will clearly and completely describe the technical solutions in the embodiments of this specification in conjunction with the accompanying drawings in the embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. Based on the embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of this application.

[0103] In the prior art, people can use Internet accounts to use various Internet services. Among them, some Internet services require users to bind different Internet accounts for business requirements or to improve the user experience.

[0104] 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 mobile phones, computers, pads, TVs), 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 transformed according to needs. In addition, a third-party application can assist the execution subject to execute this embodiment. For example Figure 1 As shown, the data processing method in this embodiment can be executed by a server, and a corresponding application 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, output, or page or information processing can be performed (for the user) through the terminal or the application, so as to assist the server in executing the data processing method in this embodiment.

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

[0106] S103: The (execution subject) obtains a user binding request sent by the terminal, determines the first account to be bound on the first server, and sends user binding request feedback data to the terminal so that the terminal displays candidate binding objects;

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

[0108] There are various ways to trigger a terminal to send a user binding request. For example, the triggering terminal can install the corresponding application described above (which may be called the triggering application). After the user opens the corresponding interface of the triggering application, the triggering application provides account binding services for the user through corresponding options or buttons on the interface. For example Figure 4 As shown in the interface, there is an option "I want to bind" on the interface. The user can click this option to initiate the account binding service. Since the user operates the triggering application to initiate the account binding service, and the first server is the server corresponding to the triggering application, after the user initiates the account binding service, the triggering terminal can generate a user binding request according to the user's operation and send the user binding request to the first server. Correspondingly, the first server obtains the user binding request sent by the triggering terminal. Specifically, the first server receives the user binding request sent by the triggering terminal (receiving the request is a type of obtaining the request).

[0109] The first server can determine the first account to be bound on the first server in the following 1.1 and / or 1.2 ways (this embodiment is not limited to the 1.1 and / or 1.2 ways):

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

[0111] When the user operates the triggering application, if the user logs in to an account on the first server on the triggering terminal (i.e., the triggering application on the triggering terminal), for example Figure 4 As shown, after the user initiates the account binding service, the triggering terminal sends a user binding request to the first server. The first server can use the login account of the user on the triggering terminal (the account on the first server) as the first account to be bound.

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

[0113] After the user initiates the account binding service, there can be a corresponding input box on the triggering application for the user to enter account information (such as a username or account number), as Figure 5 shown; since the user operates the triggering application to initiate the account binding service, the account entered by the user generally should be the account of the user on the first server; and / or, after the user initiates the account binding service, the triggering application can display a list of the user's accounts (a list of the accounts opened by the user on the first server) for the user to select an account. For example Figure 5 shows a situation where there are 3 accounts on the first server, Figure 5 which is only for illustration and does not represent actual accounts.

[0114] The triggering terminal can include the account input or selected by the user in the user binding request and send it to the first server, so that the first server can determine the first account according to the user binding request. For example, the account included in the user binding request is used as the first account to be bound.

[0115] After the first server determines the first account to be bound, it can send user binding request feedback data to the triggering terminal to enable the triggering terminal to display candidate binding objects. A candidate binding object is an object that can be bound. Here, the "object" can be an organization name or a business service provider name, etc. The owner of the first server can pre-construct relevant Internet protocols with each object, such as a data transfer protocol or a data authentication protocol, etc. An object that has constructed the above Internet protocol with the service provider of the first server can be called a candidate binding object, that is, the triggering terminal can display a list of candidate binding objects for the user to select. For example Figure 6 shows a situation where there are 4 candidate binding objects, Figure 6 which is only for illustration and does not represent actual object names.

[0116] After the first server determines the first account to be bound and before sending the user binding request feedback data to the triggering terminal, it can first perform identity authentication or other authentication on the user identity data corresponding to the first account. After the authentication passes, it sends the user binding request feedback data to the triggering terminal.

[0117] S103: (Execution subject) 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 in the servers corresponding to each of the target binding objects;

[0118] After the triggering terminal displays the candidate binding objects, it can determine the object selected by the user according to the user operation and send the binding object selection data to the first server. The binding object selection data can include the selection data of the candidate binding objects by the user. The first server obtains the binding object selection data sent by the triggering terminal and determines the object selected by the user according to the binding object selection data. The object selected by the user is used as the target binding object, that is, the first server determines each target binding object according to the binding object selection data.

[0119] After the first server determines each target binding object, it can determine one or more target servers in the servers corresponding to each target binding object and send an account binding request to each target server. As above, the "object" can be an organization name or a business service provider name, etc. Then, 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 service represented by the object.

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

[0121] S1031: Before the first server sends an account binding request to each target server, it sends an identity authentication request or a binding consultation request to the servers corresponding to each of the target binding objects. The identity authentication request or the binding consultation request includes the user identity data corresponding to the first account, so that any one of the servers corresponding to each of the target binding objects determines a second account on this server that has the same user identity data as the first account.

[0122] Specifically, after the first server determines each target binding object, it can send an identity authentication request or a binding consultation request to the servers 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 numbers), so that any one of the servers corresponding to each target binding object determines the second account on this server after receiving the identity authentication request or the binding request; among them, the second account has the same user identity data as the first account.

[0123] For example, if the target binding objects include object A, object B, and object C, then 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 on it that has the same user identity data as the first account, the server corresponding to object B determines the second account on it that has the same user identity data as the first account, and the server corresponding to object C determines the second account on it that has the same user identity data as the first account. Generally, the servers corresponding to different target binding objects are different. If there are multiple target binding objects, there can be multiple servers corresponding to each target binding object, and there can be multiple determined second accounts.

[0124] Any one of the servers corresponding to the target binding object can send authentication feedback data or consultation feedback data to the first server.

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

[0126] 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, it can obtain the authentication feedback data (corresponding to the identity authentication request) or the consultation feedback data (corresponding to the binding consultation request) sent by any server corresponding to each target binding object. For any server corresponding to each target binding object, the authentication feedback data or the consultation feedback data sent by this server may include the account information of the second account determined by this server, and the first server can determine the second account on this server according to the authentication feedback data or the consultation feedback data sent by this server.

[0127] 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, it sends candidate account data to the triggering terminal. The candidate account data is used to enable the terminal to display the second accounts determined by the servers corresponding to each of the target binding objects.

[0128] Specifically, after the first server determines the second accounts on each server corresponding to each target binding object, it can send candidate account data to the triggering terminal. The candidate account data may include the account information of the second accounts on each server corresponding to each target binding object, so that the triggering terminal can display the second accounts 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 triggering terminal can display a list of the second accounts for the user to select. For example Figure 7 As shown, assume that the user selects candidate binding objects 1 to 3. The server of object 1 has 3 second accounts, and both objects 2 and 3 have 1 second account. Figure 7 This is only for illustration and does not represent the actual object names.

[0129] The following further explains two possible situations:

[0130] Situation 1: There is no such second account on a certain or some servers corresponding to the target binding object

[0131] There may be no such second account on the server corresponding to some of the target binding objects. Assume that server S1 is the server corresponding to target binding object A (for example only, not specific). There is no such second account on server S1. After the first server obtains the authentication feedback data or the consultation feedback data sent by server S1, it can determine that there is no such second account on server S1 according to the authentication feedback data or the consultation feedback data sent by server S1. In this case, the above candidate account data is also used to enable the triggering terminal to display a first prompt message, and the first prompt message is used to prompt that there are no bindable accounts for the target binding object corresponding to the server without the second account. For example, there is no second account on the server corresponding to object 3. For exampleFigure 8 As shown. Continuing with the above example, the first prompt message 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 a bindable account can have the above first prompt message.

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

[0133] As above, if the triggering terminal displays the second prompt message, the user may need to open an account for the "target binding object corresponding to the server where the second account does not exist", for example, the user clicks on the second prompt message. In this case, the triggering terminal can obtain the user's account opening request and send the user's account opening request to the first server. As above, if there are multiple target binding objects without bindable accounts, and each target binding object without a bindable account can have the above second prompt message, the triggering terminal can determine which second prompt message corresponding to which target binding object the user has clicked, so as to determine which target binding object's account the user needs to open, and include the target binding object (and its object data) for which the user wants to open an account in the user's account opening request.

[0134] Correspondingly, after obtaining the user's account opening request sent by the triggering terminal, the first server can determine which or which target binding objects' accounts the user wants to open, and use the server corresponding to the target binding object for which the user wants to open an account as the account opening server, that is, the first server determines one or more account opening servers according to the account opening request.

[0135] The first server sends an account opening request to each account opening server to enable each account opening server to open a second account, and the opened second account should correspond to the same user identity data as the first account. Since the account opening server itself is the server corresponding to the target binding object, the account opening server has previously received an identity authentication request or a binding consultation request sent by the first server and containing the user identity data corresponding to the first account. Therefore, the account opening request may or may not contain the user identity data corresponding to the first account.

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

[0137] After the first server sends an account opening request to each account opening server, it may 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.

[0138] After obtaining the opening feedback data, the first server may send candidate account supplement data to the triggering terminal, and the candidate account supplement data is used to enable the terminal to display the second accounts opened by each account opening server. Since there may be a second account on the server corresponding to some target binding objects before the first server sends the identity authentication request or the binding consultation request, after the first server sends the candidate account supplement data to the triggering terminal, the second accounts opened by each account opening server may be displayed together with "there is a second account on the server corresponding to the target binding object before the first server sends the identity authentication request or the binding consultation request". For example, the account of the server corresponding to Object 3 is opened, as shown in Figure 9 shown.

[0139] Case 2: There are multiple second accounts on one or some of the servers corresponding to the target binding object

[0140] For any target binding object, if the server corresponding to the target binding object determines multiple second accounts after receiving the identity authentication request or the binding consultation request sent by the first server, the above candidate account data is also used to enable the triggering terminal to display the multiple second accounts of the server corresponding to the target binding object, as shown in Figures 7 to 9 any one shown.

[0141] Assume that server S2 is the server corresponding to the target binding object B (for example only, not specifically designated). After receiving the identity authentication request or binding consultation request sent by the first server, if server S2 determines multiple second accounts, then server S2 can determine one or more recommended second accounts (referred to as "recommended accounts" for convenience, and the recommended accounts are also the second accounts recommended for binding) from the multiple second accounts on it, and include the account data of the recommended accounts 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 accounts based on the account historical operation data of the multiple second accounts on it.

[0142] The first server receives the authentication feedback data or consultation feedback data sent by server S2, and determines the recommended accounts on server S2 according to the authentication feedback data or consultation feedback data sent by server S2. In this case, the above candidate account data is also used to cause the triggering terminal to display the first recommendation information, and the first recommendation information is used to prompt the recommended accounts. For example, account 1 on the server corresponding to object 1 is the recommended account, for example Figures 7 to 9 As shown for any one. 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 first recommendation information.

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

[0144] Specifically, the first server can determine the second accounts recommended for binding from each second account of the servers corresponding to each target binding object according to its historical interaction data with the servers corresponding to each target binding object, that is, the "second accounts recommended for binding determined from all the second accounts".

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

[0146] 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 accounts 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.

[0147] The first server obtains the binding account selection data sent by the trigger terminal, determines one or more second accounts (referred to as selected second accounts for convenience) selected by the user according to the binding account selection data, and uses the servers where the respective selected second accounts are located as target servers. It can be seen that if the respective selected second accounts come from multiple servers, there are multiple target servers.

[0148] In this embodiment, the target server can also be determined by other means. For example, after the user selects the target binding object, the server corresponding to the target binding object is used as the target server.

[0149] Generally speaking, when the user selects the target binding object, it means that the user hopes to bind the first account to the second accounts of each target binding object. If there is a second account for each target binding object, 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.

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

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

[0152] 2.1. Bind to the target server first, and then bind to the first server

[0153] The first server may send an account binding request to each of the target servers, so that any one of the target servers binds the second account on that target server to the first account; obtain the account binding request feedback data sent by any one 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 that target server to the first account, then bind the first account to the second account on that target server.

[0154] 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 the second account on it to the first account, that is, first the target server binds the second account on it to the first account.

[0155] Any target server may send account binding request feedback data to the first server. The first server obtains the (first) account binding request feedback data sent by any one 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 that target server to the first account, then bind the first account to the second account on that target server, that is, later the first server binds the first account and the second account.

[0156] 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 according to the account binding request feedback data sent by the target server S3 that the target server S3 has bound the second account on it to the first account, then the first server binds the first account to the second account on the target server S3.

[0157] 2.2. First the first server binds, then the target server binds

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

[0159] The first server may bind the first account to the second accounts 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, first the first server binds the first account and 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, later the target server binds the second account to the first account.

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

[0161] Specifically, the account binding request may include the user identity data corresponding to the first account.

[0162] In 2.1 or 2.2 above, for any target server, if there are multiple second accounts on that 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), it can bind all the second accounts on it to the first account, or the target server binds one of the second accounts on that target server to the first account.

[0163] In 2.1 or 2.2 above, for any target server, before the target server binds the second account on it to the first account, it can authenticate the user identity data corresponding to the first account and the user identity data corresponding to the second account or perform other authentication. After the authentication passes, it binds the second account on it to the first account.

[0164] 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 that 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 that target server to the first account.

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

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

[0167] The first server binding the first account and the second account may specifically refer to the first server itself generating and storing the binding relationship between the first account and the second account; the target server binding the second account and the first account 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 a consensus protocol may be pre-constructed 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.

[0168] In addition, the first server may send user feedback data to the triggering terminal, so that the triggering terminal displays the account binding result, that is, the account binding result of the first account and the second account. For example, Figure 10 as shown.

[0169] Specifically, the first account or the second account may both be a resource storage or resource transfer account.

[0170] It should be noted that when the first server sends any request or any data to any one of the servers corresponding to each target binding object, it is possible that the first server does not directly send the request or data to any one of the servers corresponding to each target binding object. Instead, the first server sends the request or data to be sent to an intermediate server, and the intermediate server sends the request or data to be sent to any one of the servers corresponding to each target binding object. For example, server S6 is any one of the servers corresponding to the target binding object. When the first server sends any request or any data to server S6, it is possible that the first server does not directly send the request or data to server S6. Instead, the first server sends the request or data to be sent to an intermediate server, and the intermediate server sends the request or data to be sent to server S6.

[0171] When any one of the servers corresponding to each target binding object sends any request or any data to the first server, it is possible that any one of the servers corresponding to each target binding object does not directly send the request or data to the first server. Instead, any one of the servers corresponding to each target binding object sends the request or data to be sent to an intermediate server, and the intermediate server sends the request or data to be sent to the first server. Continuing with the above example, server S6 is any one of the servers 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. Instead, server S6 sends the request or data to be sent to an intermediate server, and the intermediate server sends the request or data to be sent to the first server.

[0172] Regardless of whether the intermediate server receives requests and data from the first server or any server corresponding to each target binding object, it can authenticate the requests or data, and after successful authentication, send the requests and data to the first server or any server corresponding to each target binding object.

[0173] It should be noted that in this embodiment, the triggering terminal is variable. For example, the user logs in to the first account on terminal a and initiates an account binding service, and then logs in to the first account on terminal b to select a second account. In this case, the triggering terminal changes from terminal a to terminal b.

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

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

[0176] Through the account opening process, the user can, in one go, open an account and bind the account to an object that the user wants to bind but has no account for.

[0177] By the user's selection of the second account, the second account that the user wants to bind can be determined, that is, the other party of the account that the user wants to bind. Moreover, the user can select multiple second accounts, thereby completing the binding of the first account and the second accounts.

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

[0179] Through this embodiment, one-to-many account binding can be achieved in one go, that is, binding of one first account to multiple second accounts, improving the account binding efficiency. When the user binds the accounts, there is no need to input personal identity data, and the first server can automatically obtain the user identity data corresponding to the first account, further improving the account binding efficiency and enhancing the account binding security.

[0180] In the prior art, in order to perform electronic payment and improve the electronic payment experience, a user may bind their third-party payment account to an account of a financial institution (including but not limited to a bank) to enable electronic payment services such as quick payment. Among them, for quick payment, it is necessary to complete the binding of the user's bank account and the account of the third-party payment institution in a tripartite (user, bank, payment institution) agreement framework in advance.

[0181] With the increase in the number of third-party payment institutions, a user may need to bind their financial institution account (hereinafter taking a bank account as an example) to the accounts of multiple third-party payment institutions. However, in the prior art, the user must initiate the binding of the bank account through a third-party payment institution, and each third-party payment institution can only bind its own account to the bank account. In addition, the binding processes between each third-party payment institution and the bank account are different. The user needs to enter binding elements (including but not limited to name, identity information, bank card number, mobile phone number) during each binding process, which is easy for the user to fill in incorrectly, resulting in a complicated binding process and low binding efficiency.

[0182] 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 third-party payment institution account can be used as the second account, so as to complete the binding of one bank account to multiple third-party institution accounts at one time, effectively improving the account binding efficiency. This embodiment can initiate account binding from the bank side and does not depend on each third-party payment institution. During the account binding process, the user does not need to enter personal information, and the bank side can automatically obtain the first account and the user identity information corresponding to the first account, further improving the account binding efficiency and account binding security.

[0183] It should be noted that during the process of binding a financial institution account and a third-party payment institution account, the above-mentioned intermediate server can be a server of the Network Union or UnionPay.

[0184] 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 (furthermore, from the target server).

[0185] 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 a mobile phone, a computer, a pad, a 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 according to needs. In addition, a third-party application program can also assist the execution subject to execute this embodiment. For example Figure 1As shown, the data processing method in this embodiment can be executed by a server, and a corresponding application can be installed on the terminal (held by the user). Data can be transmitted between the terminal or the application and the server. Data collection, input, output, or page or information processing (for the user) can be performed through the terminal or the application, so as to assist the server in executing the data processing method in this embodiment.

[0186] As Figure 11 shown, the data processing method provided in this embodiment is applied to a second server (i.e., the execution entity is the second server), and includes:

[0187] 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 contains user identity data corresponding to a 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;

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

[0189] S204: Send authentication feedback data or consultation feedback data to the first server, where the authentication feedback data or the consultation feedback data contains 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 target server;

[0190] In this embodiment, when 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 that has 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 that has the same user identity data as the first account.

[0191] In this embodiment, if an account opening request sent by the first server is received, then open a second account that has the same user identity data as the first account according to the account opening request;

[0192] Send opening feedback data to the first server, where the opening feedback data contains account data of the second account opened according to the account opening request.

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

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

[0195] S206: If an account binding request sent by the first server is obtained, bind the second account to the first account.

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

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

[0198] Determine the 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.

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

[0200] Determine the second account to be bound from the multiple second accounts, and bind the second account to be bound to the first account.

[0201] After the second server binds the second account on it to the first account, it can send account binding request feedback data to the first server.

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

[0203] 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 any request or any data to the intermediate server, and the intermediate server sends the any request or any data to the second server.

[0204] For the content not described in detail in this embodiment, refer to the first embodiment.

[0205] Through this embodiment, one-to-many account binding can be achieved at one time, that is, the binding of one first account to multiple second accounts, which improves the account binding efficiency. When the user binds the accounts, there is no need to input personal identity data, and the first server can automatically obtain the user identity data corresponding to the first account, further improving the account binding efficiency and enhancing the security of account binding.

[0206] This embodiment, like the first embodiment, can be used for the binding of financial institution accounts and third-party payment institution accounts.

[0207] As shown in the first embodiment, both the first account and the second account can be resource storage or resource transfer accounts. After binding the first account and the second accounts through the first or second embodiment, resource transfer can be performed between the first account and each second account bound to the first account.

[0208] 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, TVs), 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 diverse and can be set, used, or changed according to needs. In addition, a third-party application can 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 a corresponding application can be installed on the terminal (held by the user). Data transmission can be carried out between the terminal or the application and the server, and data can be collected, input, output, or page or information processing can be performed (for the user) through the terminal or the application, so as to assist the server in executing the resource transfer method in this embodiment.

[0209] As Figure 12 shown, the resource transfer method provided in this embodiment is applied to a third server (that is, the execution subject is the third server), and includes:

[0210] S301: Obtain a first resource transfer request sent by a terminal, and determine a third account, a fourth account to which resource transfer is to be performed, and the amount of resource transfer; wherein, the third account is an account on the third server, and the third account and the fourth account are bound by the method described in the first or second embodiment;

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

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

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

[0214] The third account for which resource transfer is to be performed is an account on the third server. The determination method of the third account is the same as that of the first account, for example, determined by user input or according to the logged-in account of the second triggering terminal. The first account and any second account bound to the first account can both be used as the 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 fourth account for which resource transfer is to be performed 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 both be used as the resource transfer-out or resource transfer-in account, so the third account can be equivalent to the first account or the second account.

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

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

[0218] 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 the resource transfer feedback data sent by the fourth server. 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.

[0219] The second resource transfer request may include the 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 can determine the fourth account on the fourth server for which the resource transfer is to be performed and determine the resource transfer amount.

[0220] 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 receiving 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; obtain 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 increase the resources of the third account by the resource transfer amount.

[0221] 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 sending server, then the third server reduces the resources of the third account by the resource transfer amount and sends 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.

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

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

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

[0225] The fourth embodiment of this specification (hereinafter referred to as "this embodiment") provides a resource transfer method. The execution subject of this embodiment may be a terminal (including but not limited to mobile phones, computers, pads, TVs), 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 diverse and can be set, used, or changed according to needs. In addition, a third-party application program may 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 a corresponding application 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 or input or output through the terminal or the application, or page or information processing can be performed (for the user), thereby assisting the server to execute the resource transfer method in this embodiment.

[0226] As Figure 13 shown, the resource transfer method provided in this embodiment is applied to a fourth server (i.e., the execution entity is the fourth server), and includes:

[0227] S402: If a resource transfer request sent by a third server is obtained, determine the fourth account on the fourth server for which resource transfer is to be performed, and determine the resource transfer amount;

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

[0229] S404: 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,

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

[0231] Wherein, the third account is an account on the third server, and the third account and the fourth account are bound by the method described in the first or second embodiment.

[0232] For the content not described in detail in this embodiment, refer to the third embodiment.

[0233] In this embodiment, by binding the third account and the fourth account by the method of the first or second embodiment, one-to-many account binding can be achieved at one time, improving the account binding efficiency. Resource transfer through the bound accounts further improves the resource transfer efficiency.

[0234] The resources in the third or fourth embodiment include virtual resources, and the virtual resources include funds. Therefore, 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. Therefore, the third or fourth embodiment can also be a recharge method.

[0235] Payment can be a form of fund transfer, so the third or fourth embodiment can also be a payment method.

[0236] The fifth embodiment of this specification (hereinafter referred to as "this embodiment") provides a payment method. The execution entity of this embodiment can be a terminal (including but not limited to mobile phones, computers, pads, TVs), or a server, or an operating system, or a payment platform, or a payment system, etc. That is, the execution entity can be diverse and can be set, used, or changed according to needs. Additionally, a third-party application can assist the execution entity in executing this embodiment. For example Figure 1 As shown, the payment method in this embodiment can be executed by the server, and a corresponding application 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, output, or page or information processing can be performed (for the user) through the terminal or the application, so as to assist the server in executing the payment method in this embodiment.

[0237] As Figure 14 shown, the payment method provided in this embodiment is applied to the fifth server (i.e., the execution entity is the fifth server), and includes:

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

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

[0240] The fifth server can obtain a first payment request sent by the terminal (referred to as the "third triggering terminal" for convenience, and the first, second, and third triggering terminals can be the same or different).

[0241] Referring to the first embodiment, the user can initiate a resource transfer service through the application corresponding to the fifth server, and then the third triggering terminal sends a first payment request to the fifth server.

[0242] The fifth account is an account on the fifth server. The determination method of the fifth account follows that of the first account. For example, it can be determined by user input or based on the login account of the third triggering terminal. Although the fifth server obtains the first payment request, the fifth account may not be the fund deduction account. For example, in the context of express payment, the third-party payment institution server obtains the first payment request sent by the user terminal, but the fund deduction account can be a financial institution account bound to the third-party payment institution account.

[0243] The sixth account for which fund deduction is to be made can be determined by the user and included in the first payment request. Therefore, the fifth server can determine the sixth account based on the first payment request.

[0244] The payment amount can be included in the first payment request. Therefore, the fifth server can determine the payment amount based on the first payment request.

[0245] The fifth account and the sixth account are bound using the method described in the first or second embodiment. If the fifth account and the sixth account are not bound when the first payment request is obtained (determined by the fifth server), then the fifth server can, like the first server in the first embodiment, use the data processing method in the first embodiment to bind the fifth account and the sixth account.

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

[0247] The second payment request can 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 can determine the sixth account to be paid on the sixth server and determine the payment amount.

[0248] After the sixth server reduces the funds of the sixth account by the payment amount, it can send payment feedback data to the fifth server. If the fifth server determines that the payment amount has been deducted from the sixth account based on the payment feedback data sent by the sixth server, it can send user feedback data to the third triggering terminal so that the second triggering terminal displays the payment result.

[0249] If the fifth server is the receiving server corresponding to the payment, after the fifth server determines that the payment amount has been deducted from the sixth account based on the payment feedback data sent by the sixth server, it can increase the funds of the receiving account on the fifth server by the payment amount.

[0250] If the fifth server is not the receiving server corresponding to the payment, after determining that the payment amount has been deducted from the sixth account according to the payment feedback data sent by the sixth server, the fifth server may send a collection instruction to the receiving server, so that the receiving server increases the payment amount on its receiving account.

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

[0252] Referring to the first or second embodiment, the data transmission between the fifth server and the sixth server, and between the fifth server and the receiving server may be carried out through an intermediate server. Among them, the intermediate server includes but is not limited to a network union or a UnionPay server or a payment supervision institution server.

[0253] In this embodiment, by using the method of the first or second embodiment to bind the third account and the fourth account, one-to-many account binding can be achieved at one time, improving the account binding efficiency. Making payments through the bound accounts further improves the payment efficiency.

[0254] The sixth embodiment of this specification (hereinafter referred to as "this embodiment") provides a payment method. The execution subject of this embodiment may be a terminal (including but not limited to mobile phones, computers, pads, TVs) or a server or an operating system or a payment platform or a payment system, etc. That is, the execution subject can be diverse and can be set, used, or changed according to needs. In addition, a third-party application may assist the execution subject in executing this embodiment. For example Figure 1 As shown, the payment method in this embodiment can be executed by a server, and a corresponding application can be installed on the terminal (held by the user). Data transmission can be carried out between the terminal or the application and the server, and data collection or input or output or page or information processing (to the user) can be carried out through the terminal or the application, so as to assist the server in executing the payment method in this embodiment.

[0255] As Figure 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:

[0256] S602: If a payment request sent by the fifth server is obtained, determine the sixth account on the sixth server where the funds are to be deducted, and determine the payment amount;

[0257] 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.

[0258] S604: Reduce the funds in the sixth account by the payment amount, and send payment feedback data to the fifth server;

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

[0260] For the content not described in detail in this embodiment, refer to the fourth embodiment.

[0261] In this embodiment, by using the method of the first or second embodiment to bind the third account and the fourth account, one-to-many account binding can be achieved at one time, improving the account binding efficiency. Making payments through the bound accounts further improves the payment efficiency.

[0262] 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), so as to achieve (one-to-many) account binding between different countries or regions. Similarly, the third and fourth servers (and the intermediate server) in the third or fourth embodiment or the fifth and sixth servers (and the intermediate server) in the fifth or sixth embodiment may also be located in different countries or regions, so as to achieve resource transfer or payment between different countries or regions.

[0263] As Figure 16 shown, the seventh embodiment of this specification provides a data processing device, including:

[0264] A preliminary binding module 701, 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;

[0265] An initial binding module 703, configured 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 in the servers corresponding to each target binding object;

[0266] An account binding module 705, configured to

[0267] Bind the first account to the second accounts on each of the target servers, and send an account binding request to each of the target servers, so that any one of the target servers binds the second account on that target server to the first account;

[0268] Wherein, the second accounts correspond to the same user identity data as the first account.

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

[0270] Optionally, before sending the account binding request to each target server, the preliminary binding module 701 is further configured to send an identity authentication request or a binding consultation request to the server corresponding to each target binding object, and the identity authentication request or the binding consultation request includes the user identity data corresponding to the first account, so that any one of the servers corresponding to each target binding object determines the second account on that server that corresponds to the same user identity data as the first account.

[0271] Optionally, after sending the identity authentication request or the binding consultation request to any one of the servers corresponding to each target binding object, the preliminary binding module 701 is further configured to obtain the authentication feedback data or the consultation feedback data sent by any one of the servers corresponding to each target binding object, and determine the second account on that server according to the authentication feedback data or the consultation feedback data sent by that server.

[0272] Optionally, after determining the second account on that server according to the authentication feedback data or the consultation feedback data sent by any one of the servers corresponding to each target binding object, and before determining one or more target servers, the preliminary binding module 701 is further configured to send candidate account data to the terminal, and the candidate account data is used to enable the terminal to display the second accounts determined by the servers corresponding to each target binding object.

[0273] Optionally, after sending the identity authentication request or the binding consultation request to any one of the servers corresponding to each target binding object, the preliminary binding module 701 is further configured to

[0274] obtain the authentication feedback data or the consultation feedback data sent by any one of the servers corresponding to each target binding object. If it is determined that there is no second account on a certain server corresponding to a target binding object, the candidate account data is further used to enable the terminal to display a first prompt message, and the first prompt message is used to prompt that there is no bindable account for the target binding object corresponding to the server where the second account does not exist.

[0275] Optionally, after the preliminary binding module 701 sends an identity authentication request or a binding consultation request to any server corresponding to each of the target binding objects, it obtains the 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 certain server corresponding to the target binding object, the candidate account data is further used to cause the terminal to display a second prompt message, and the second prompt message is further used to prompt the user to open an account for the target binding object corresponding to the server where the second account does not exist.

[0276] Optionally, after the preliminary binding module 701 sends the candidate account data to the terminal, it obtains the user account opening request sent by the terminal, and determines one or more account opening servers according to the user account opening request;

[0277] Send an account opening request 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.

[0278] Optionally, after the preliminary binding module 701 sends an account opening request to each of the account opening servers, it obtains the opening feedback data sent by any one of the account opening servers, and determines the second account opened by the account opening server according to the opening feedback data;

[0279] Send candidate account supplementary data to the terminal, and the candidate account supplementary data is used to cause the terminal to display the second accounts opened by each of the account opening servers.

[0280] Optionally, after the preliminary binding module 701 obtains the authentication feedback data or consultation feedback data sent by any server corresponding to each of the target binding objects, it determines the second account recommended for binding on the server according to the authentication feedback or consultation feedback data sent by the server.

[0281] Optionally, the candidate account data is further used to cause the terminal to display a first recommendation message, and the first recommendation message is used to prompt the second account recommended for binding.

[0282] Optionally, after the preliminary binding module 701 determines 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, it determines the second account recommended for binding from the second accounts of each server corresponding to each of the target binding objects;

[0283] The candidate account data is further used to cause the terminal to display a second recommendation message, and the second recommendation message is used to prompt the second account recommended for binding.

[0284] Optionally, determining a second account recommended for binding from each of the second accounts of the servers corresponding to each of the target binding objects includes:

[0285] Determining a second account recommended for binding from each of the second accounts of the servers corresponding to each of the target binding objects according to the historical interaction data between the first server and the servers corresponding to each of the target binding objects.

[0286] 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 target server binds a second account on the target server to the first account includes:

[0287] Sending an account binding request to each of the target servers so that any target server binds one of the second accounts on the target server to the first account.

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

[0289] Obtaining the bound account selection data sent by the terminal, determining one or more selected second accounts according to the bound account selection data, and taking the servers where the one or more selected second accounts are located as target servers.

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

[0291] Sending an account binding request to each of the target servers so that any target server binds the second account on the target server to the first account; obtaining the account binding request feedback data sent by any target server, 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, then binding the first account to the second account on the target server; or,

[0292] After binding the first account to the second account of any target server, sending 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.

[0293] Optionally, the apparatus further includes:

[0294] A sending module, configured to send user feedback data to the terminal so that the terminal displays the account binding result.

[0295] Optionally, when obtaining the account binding request, the first account is the logged-in account of the terminal;

[0296] Or,

[0297] Determine the first account according to the account binding request.

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

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

[0300] 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.

[0301] As Figure 17 shown, the eighth embodiment of this specification provides a data processing device, including:

[0302] A preliminary binding module 802, configured to, 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, determine a second account on the device that has the same user identity data as the first account; where the first account is an account on the first server; and send authentication feedback data or consultation feedback data to the first server, where the authentication feedback data or the 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;

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

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

[0305] Optionally, after obtaining the identity authentication request or the binding consultation request sent by the first server, if the preliminary binding module 802 determines that there is no account on the second server that has 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 that has the same user identity data as the first account.

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

[0307] Send opening feedback data to the first server, where the opening feedback data includes account data of the second account opened according to the account opening request.

[0308] Optionally, after receiving an identity authentication request or a 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 the consultation feedback data further includes account data of a recommended account, and the recommended account is one or more second accounts.

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

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

[0311] 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.

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

[0313] Determine a second account to be bound from the multiple second accounts, and bind the second account to be bound to the first account.

[0314] Optionally, the device further includes:

[0315] A sending module, configured to send account binding request feedback data to the first server after binding the second account to the first account.

[0316] 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 an intermediate server, and the intermediate server sends the any request or any data to the second server.

[0317] As Figure 18 shown, the ninth embodiment of this specification provides a resource transfer device, including:

[0318] A transfer initiation module 901, configured to obtain a first resource transfer request sent by a terminal, and determine a third account and a fourth account for which resource transfer is to be performed, and the amount of resource transfer; wherein, the third account is an account on the device, and the third account and the fourth account are bound by the method described in the first or second embodiment.

[0319] A transfer module 903, 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 amount of resource transfer; 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 amount of resource transfer, then increase the resources of the third account by the amount of resource transfer; or,

[0320] Reduce the resources of the third account by the amount of resource transfer, and send a second resource transfer request to a fourth server where the fourth account is located, so that the fourth server increases the resources of the fourth account by the amount of resource transfer.

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

[0322] As Figure 19 shown, the tenth embodiment of this specification provides a resource transfer device, including:

[0323] A transfer acceptance module 1002, configured to determine a fourth account on the device for which resource transfer is to be performed and the amount of resource transfer if a resource transfer request sent by a third server is obtained;

[0324] A transfer module 1004, configured to reduce the resources of the fourth account by the amount of resource transfer, and send resource transfer feedback data to the third server, so that the third server increases the resources of a third account for which resource transfer is to be performed by the amount of resource transfer; or,

[0325] If it is determined according to the resource transfer request that the third server reduces the resources of a third account for which resource transfer is to be performed by the amount of resource transfer, then increase the resources of the fourth account by the amount of resource transfer;

[0326] wherein, the third account is an account on the third server, and the third account and the fourth account are bound by the method described in the first or second embodiment.

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

[0328] As Figure 20As shown in the figure, the eleventh embodiment of this specification provides a payment device, including:

[0329] A payment initiation module 1101, configured to obtain a first payment request sent by a terminal, determine a fifth account, a sixth account for which funds are to be deducted, 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 by the method described in the first or second embodiment.

[0330] A payment module 1103, configured to send a second payment request to a sixth server where the sixth account is located, so that the sixth server reduces the funds of the sixth account by the payment amount.

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

[0332] As Figure 21 As shown in the figure, the twelfth embodiment of this specification provides a payment device, including:

[0333] A payment acceptance module 1202, configured to determine a sixth account on the device for which funds are to be deducted and a payment amount if a payment request sent by a fifth server is obtained.

[0334] A payment module 1204, configured to reduce the funds of the sixth account by the payment amount and send payment feedback data to the fifth server.

[0335] Wherein, the sixth account and the fifth account on the fifth server are bound by 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.

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

[0337] It should be noted that the devices 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 devices in the seventh or eighth embodiment, or the intermediate server may be in a different country or region from the devices in the seventh or eighth embodiment), so as to achieve (one-to-many) account binding between different countries or regions. Similarly, the devices (and intermediate servers) in the ninth or tenth embodiment or the devices (and intermediate servers) in the eleventh or twelfth embodiment may also be located in different countries or regions, so as to achieve resource transfer or payment between different countries or regions.

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

[0339] At least one processor; and a memory communicatively connected to the at least one processor;

[0340] Wherein,

[0341] The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the data processing method described in the first or second embodiment.

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

[0343] At least one processor; and a memory communicatively connected to the at least one processor;

[0344] Wherein,

[0345] The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the resource transfer method described in the third or fourth embodiment.

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

[0347] At least one processor; and a memory communicatively connected to the at least one processor;

[0348] Wherein,

[0349] The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the payment method described in the fifth or sixth embodiment.

[0350] The sixteenth embodiment of this specification provides a computer-readable storage medium, which 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.

[0351] The seventeenth embodiment of this specification provides a computer-readable storage medium, which 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.

[0352] The seventeenth embodiment of this specification provides a computer-readable storage medium, which 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.

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

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

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

[0356] The specific embodiments of this specification have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily have to be performed in the specific order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

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

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

[0359] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements to method flows). However, with the development of technology, many method flow improvements today can be regarded as direct improvements to hardware circuit structures. Almost all designers obtain the corresponding hardware circuit structures by programming the improved method flows into the hardware circuits. Therefore, it cannot be said that an improvement to a method flow cannot be implemented using hardware entity modules. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logical function is determined by the user programming the device. Designers can program a digital system "integrated" on a single PLD by themselves, without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compilers used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called a Hardware Description Language (HDL). There is not just one type of HDL, but many types, 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. Currently, the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that by simply performing a little logical programming on the method flow using the above-mentioned several hardware description languages and programming it into the integrated circuit, it is easy to obtain the hardware circuit that implements the logical method flow.

[0360] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller 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 the form of pure computer-readable program code, it is entirely possible to make the controller implement the same function in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or the structures within the hardware component.

[0361] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can 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 any combination of these devices.

[0362] For the convenience of description, when describing the above devices, they are described separately as 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.

[0363] Those skilled in the art should understand that the embodiments of this specification can be provided as a method, a system, or a computer program product. Therefore, the embodiments of this specification can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0364] This specification is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, special-purpose computers, embedded processors, or other programmable data processing devices to produce a machine, such that the instructions executed by the processors of the computer or other programmable data processing devices generate means for implementing the functions specified in one or more of the flows Figure 1 or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0365] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable memory produce a manufacture including instruction means that implement the functions specified in one or more of the flows Figure 1 or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0366] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more of the flows Figure 1 or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more of the blocks.

[0367] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

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

[0369] 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.

[0370] 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.

[0371] 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.

[0372] 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.

[0373] The above is only for the embodiments of this specification and is not intended to limit this application. For those skilled in the art, various changes and modifications can be made to this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included within the scope of the claims of this application.

Claims

1. A data processing method, applied to a first server, comprising: Determine a first account to be bound on the first server, and determine one or more target servers, where there is at least one second account on each target server, and the second account corresponds to the same user identity data as the first account; For each target server: Bind the first account on the first server to the second account on the target server; And Send an account binding request to the target server to instruct the target server to bind the first account to the second account on the target server.

2. The method according to claim 1, wherein determining the first account to be bound on the first server comprises: After the user initiates an account binding service through a login account on the terminal, obtain the user binding request sent by the terminal; And Determine the first account based on the user binding request.

3. The method according to claim 2, wherein the first account is the login account; or the first account is another account selected by the user through the login account.

4. The method according to claim 1, wherein determining one or more target servers comprises: Display candidate binding objects through the terminal; And Obtain the binding object selection data sent by the terminal, determine each target binding object according to the binding object selection data, and determine the one or more target servers in the servers corresponding to each target binding object.

5. The method according to claim 4, before sending the account binding request to the target server, the method further comprises: Send an identity authentication request or a binding consultation request to the servers corresponding to each target binding object, where 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 the second account on the server that corresponds to the same user identity data as the first account.

6. The method according to claim 5, after sending the identity authentication request or the binding consultation request to any server corresponding to each target binding object, the method further comprises: Obtain the authentication feedback data or the consultation feedback data sent by any server corresponding to each target binding object, and determine the second account on the server according to the authentication feedback data or the consultation feedback data sent by the server.

7. The method according to claim 6, after determining the second account on the server according to the authentication feedback data or the consultation feedback data sent by any server corresponding to each target binding object, before determining one or more target servers, the method further comprises: Send candidate account data to the terminal, where the candidate account data is used to enable the terminal to display the second accounts determined by the servers corresponding to each target binding object.

8. The method according to claim 7, after sending the identity authentication request or the binding consultation request to any server corresponding to each target binding object, 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 certain server corresponding to the target binding object, the candidate account data is further used to cause the terminal to display a first prompt message, and the first prompt message is used to prompt that there is no bindable account for the target binding object corresponding to the server where the second account does not exist.

9. The method according to claim 7, 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 includes: 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 certain server corresponding to the target binding object, the candidate account data is further used to cause the terminal to display a second prompt message, and the second prompt message is further used to prompt the user to open an account for the target binding object corresponding to the server where the second account does not exist.

10. The method according to claim 9, after sending candidate account data to the terminal, the method further includes: Obtain a user account opening request sent by the terminal, and determine one or more account opening servers according to the user account opening request; and Send an account opening request 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.

11. The method according to claim 10, after sending an account opening request to each of the account opening servers, the method further includes: Obtain the opening feedback data sent by any one of the account opening servers, and determine the second account opened by the account opening server according to the opening feedback data; and Send candidate account supplementary data to the terminal, and the candidate account supplementary data is used to cause the terminal to display the second accounts opened by each of the account opening servers.

12. The method according to claim 6, 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 includes: Determine the second account recommended for binding on the server according to the authentication feedback or consultation feedback data sent by the server.

13. The method according to claim 12, before determining one or more target servers, the method further includes: Send candidate account data to the terminal, and the candidate account data is used to cause the terminal to display the second accounts determined by the servers corresponding to each of the target binding objects, and is further used to cause the terminal to display a first recommendation message, and the first recommendation message is used to prompt the second account recommended for binding.

14. The method according to claim 7, 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 includes: Determine the second account recommended for binding from each of the second accounts of the servers corresponding to each of the target binding objects; and The candidate account data is further used to cause the terminal to display a second recommendation message, and the second recommendation message is used to prompt the second account recommended for binding.

15. The method according to claim 14, determining the second account to be recommended for binding from each of the second accounts of the servers corresponding to each of the target binding objects includes: Determining the second account to be recommended for binding from each of the second accounts of the servers corresponding to each of the target binding objects according to the historical interaction data between the first server and the servers corresponding to each of the target binding objects.

16. The method according to claim 1, for any target server, if there are multiple second accounts on the target server, sending an account binding request to the target server to instruct the target server to bind the first account to the second account on the target server includes: Sending the account binding request to the target server, so that the target server binds one of the second accounts on the target server to the first account.

17. The method according to claim 7, determining one or more target servers among the servers corresponding to each of the target binding objects includes: Obtaining the binding account selection data sent by the terminal, determining the selected one or more second accounts according to the binding account selection data, and using the servers where the selected one or more second accounts are located as the target servers.

18. The method according to claim 1, binding the first account to a second account on the target server at the first server; And sending an account binding request to the target server to instruct the target server to bind the first account to the second account on the target server includes: Sending the account binding request to the target server, so that the target server binds the second account on the target server to the first account; obtaining the account binding request feedback data sent by the target server, 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, then binding the first account to the second account on the target server; or, After binding the first account to the second account of the target server, sending 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.

19. The method according to claim 1, the method further includes: Sending user feedback data to the terminal, so that the terminal displays the account binding result.

20. The method according to claim 1, the account binding request includes the user identity data corresponding to the first account.

21. The method according to claim 1, the first account or the second account is a resource storage or resource transfer account.

22. The method according to any one of claims 4 to 21, if the first server sends any request or any data to any one of the servers 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 one of the servers corresponding to each target binding object.

23. A data processing method, applied to a second server, includes: Obtain an account binding request sent by the first server, where the account binding request is used to request binding the first account to a second account on the second server. The first account is an account on the first server, and the second account corresponds to the same user identity data as the first account; And Bind the second account on the second server and the first account, where the second server is one of one or more target servers determined by the first server, and there is at least one second account on each target server.

24. The method according to claim 23, wherein binding the second account on the second server and the first account includes: Generate and store the binding relationship between the second account on the second server and the first account.

25. The method according to claim 23, before obtaining the account binding request sent by the first server, the method further includes: Obtain an identity authentication request or a binding consultation request sent by the first server, where the identity authentication request or the binding consultation request contains the user identity data corresponding to the first account, and determine the second account on the second server; And Send authentication feedback data or consultation feedback data to the first server, where the authentication feedback data or the consultation feedback data contains the account data of the second account, so that the first server determines the one or more target servers.

26. The method according to claim 25, after obtaining the identity authentication request or the 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, 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.

27. The method according to claim 25, the method further includes: 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; And Send opening feedback data to the first server, where the opening feedback data contains the account data of the second account opened according to the account opening request.

28. The method according to claim 25, if there are multiple second accounts on the second server, the authentication feedback data or the consultation feedback data further includes the account data of the recommended account, and the recommended account is one or more second accounts.

29. The method according to claim 28, determine the recommended account according to the account historical operation data of the multiple second accounts.

30. The method according to claim 23, if there are multiple second accounts on the second server, binding the second account on the second server and the first account includes: Determine the 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.

31. The method according to claim 23, if there are multiple second accounts on the second server, binding the second accounts on the second server and the first account includes: Determining the second account to be bound from the multiple second accounts, and binding the second account to be bound to the first account.

32. The method according to claim 23, after binding the second account on the second server and the first account, the method further includes: Sending account binding request feedback data to the first server.

33. The method according to any one of claims 23 to 32, 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.

34. A resource transfer method, applied to a third server, includes: Obtaining a first resource transfer request sent by a terminal, and determining a third account and a fourth account for which resource transfer is to be performed and the amount of resource transfer; wherein, the third account is an account on the third server, and the third account and the fourth account are bound by the method according to any one of claims 1 to 33; Sending 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 amount of resource transfer; obtaining the resource transfer feedback data sent by the fourth server, if it is determined according to the resource transfer feedback data that the resources of the fourth account are reduced by the amount of resource transfer, then increasing the resources of the third account by the amount of resource transfer; or, Reducing the resources of the third account by the amount of resource transfer, and sending 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 amount of resource transfer.

35. A resource transfer method, applied to a fourth server, includes: If a resource transfer request sent by a third server is obtained, determining the fourth account on the fourth server for which resource transfer is to be performed, and determining the amount of resource transfer; Reducing the resources of the fourth account by the amount of resource transfer, and sending resource transfer feedback data to the third server, so that the third server increases the resources of the third account for which resource transfer is to be performed by the amount of resource transfer; Or, If it is determined according to the resource transfer request that the resources of the third account for which resource transfer is to be performed on the third server are reduced by the amount of resource transfer, then increasing the resources of the fourth account by the amount of resource transfer; wherein, the third account is an account on the third server, and the third account and the fourth account are bound by the method according to any one of claims 1 to 33.

36. A payment method, applied to a fifth server, includes: Obtain a first payment request sent by a terminal, and determine a fifth account, a sixth account for which funds are to be deducted, 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 by the method described in any one of claims 1 to 33. Send a second payment request to the sixth server where the sixth account is located, so that the sixth server reduces the funds of the sixth account by the payment amount.

37. A payment method, applied to a sixth server, includes: If a payment request sent by a fifth server is obtained, determine the sixth account on the sixth server for which funds are to be deducted, and determine the payment amount. Reduce the funds of the sixth account by the payment amount, and send payment feedback data to the fifth server. Wherein, the sixth account and the fifth account on the fifth server are bound by the method described in any one of claims 1 to 33, the fifth account is a user login account on the fifth server, and the fifth account is used to receive payment requests sent by the terminal.

38. A data processing device includes: A preliminary binding module, configured to determine a first account to be bound on the device. An initial binding module, configured to determine one or more target servers, and there is at least one second account on each target server, and the second account corresponds to the same user identity data as the first account. An account binding module, configured for each target server: bind the first account on the device to the second account on the target server; And send an account binding request to the target server to instruct the target server to bind the first account to the second account on the target server.

39. The device according to claim 38, the device further includes a first server, and the first account is an account on the first server.

40. A data processing device includes an account binding module, configured to: Obtain an account binding request sent by a first server, the account binding request is used to request binding a first account to a second account on the device, the first account is an account on the first server, and the second account corresponds to the same user identity data as the first account; and It is also used to bind the second account and the first account on the device, wherein, The device is one of one or more devices determined by the first server, and there is at least one second account on each device.

41. The device according to claim 40, the device further includes a second server, and the second account is an account on the second server.

42. A resource transfer device includes: A transfer initiation module, configured to obtain a first resource transfer request sent by a terminal, and determine a third account and a fourth account for which resources are 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 by the method described in any one of claims 1 to 33. 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, 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.

43. The device according to claim 42, wherein the device further comprises a third server, and the third account is an account on the third server.

44. A resource transfer device, comprising: A transfer acceptance module, configured to, if a resource transfer request sent by a third server is obtained, determine a fourth account on the device for which resource transfer is to be performed, and determine the resource transfer amount; 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 a third account for which resource transfer is to be performed by the resource transfer amount; Or, If it is determined according to the resource transfer request that the resources of the third account for which resource transfer is to be performed on the third server are reduced by the resource transfer amount, then increase the resources of the fourth account by the resource transfer amount; wherein the third account is an account on the third server, and the third account and the fourth account are bound by the method described in any one of claims 1 to 33.

45. The device according to claim 44, wherein the device further comprises a fourth server, and the fourth account is an account on the fourth server.

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

47. The device according to claim 46, wherein the device further comprises a fifth server, and the fifth account is an account on the fifth server.

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

49. The device according to claim 48, wherein the device further includes a sixth server, and the sixth account is an account on the sixth server.

50. A data processing device, comprising: At least one processor; And, A memory communicatively connected to the at least one processor; Wherein, The memory stores instructions executable by the at least one processor. When the instructions are executed by the at least one processor, the at least one processor is enabled to execute the data processing method described in any one of claims 1 to 22 or 23 to 33.

51. A resource transfer device, comprising: At least one processor; And, A memory communicatively connected to the at least one processor; Wherein, The memory stores instructions executable by the at least one processor. When the instructions are executed by the at least one processor, the at least one processor is enabled to execute the resource transfer method described in claim 34 or 35.

52. A payment device, comprising: At least one processor; And, A memory communicatively connected to the at least one processor; Wherein, The memory stores instructions executable by the at least one processor. When the instructions are executed by the at least one processor, the at least one processor is enabled to execute the payment method described in claim 36 or 37.

53. A 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 any one of claims 1 to 22 or 23 to 33 is implemented.

54. A 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 claim 34 or 35 is implemented.

55. A computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the payment method described in claim 36 or 37 is implemented.

Images