CN112053161A

CN112053161A - Binding processing method, device and equipment

Info

Publication number: CN112053161A
Application number: CN202011053659.5A
Authority: CN
Inventors: 殷雅雯
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-05-09
Filing date: 2020-05-09
Publication date: 2020-12-08
Anticipated expiration: 2040-05-09
Also published as: WO2021227966A1; CN112053161B; CN111311251B; CN111311251A

Abstract

The embodiment of the specification provides a binding processing method, a binding processing device and binding processing equipment, wherein the binding processing method comprises the following steps: a second server of the resource storage mechanism receives a binding request sent by a second client of the resource storage mechanism, and if the target user is determined not to register the payment account of the payment application, an account registration request of the target user is sent to a first server of the payment application; the first server side performs registration processing on the payment account according to the registration information included in the account registration request to obtain account identification information of the target user; sending the account identification information to a second server to enable the second server to perform binding processing according to the account identification information; and if the first server side determines that the operation processing of the target user on the first client side of the payment application meets the preset safety authentication condition, the first server side performs safety authentication processing on the target user through the first client side.

Description

Binding processing method, device and equipment

This patent application is application number: 202010387135.3, filing date: the patent application filed in 9/5/2020 is a divisional application of the Chinese patent application entitled "binding processing method, device and equipment".

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a binding processing method, device and apparatus.

Background

With the rapid development of the mobile payment industry, various payment applications are in transit. In order to ensure the payment security, when a user registers a payment account of a payment application for the first time, not only the identity of the user needs to be verified, but also the device environment of the terminal device where the payment application is located needs to be verified. To implement the payment function of the payment application, the user typically performs the binding of the bank card after the payment account registration is successful. Currently, the binding mode of the bank card is usually to complete the binding of the bank card for the user to operate the payment application. The single binding mode cannot meet the binding requirements of users in different scenes.

Disclosure of Invention

One or more embodiments of the present disclosure provide a binding processing method, an apparatus, and a device, which complete binding between a payment account and a storage account without increasing user operations, and meet binding requirements of a user in different scenarios.

To solve the above technical problem, one or more embodiments of the present specification are implemented as follows:

one or more embodiments of the present specification provide a binding processing method, which is applied to a first server of a payment application. The method comprises the step of receiving an account registration request of a target user, which is sent by a second server side of a resource storage mechanism. Wherein the account registration request is sent based on a binding request sent by the target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered by the target user. The account registration request includes registration information of the target user. And sending the account identification information obtained by performing the registration processing of the payment account according to the registration information to the second server, so that the second server performs the binding processing according to the account identification information. And if the operation processing of the target user on the first client of the payment application is determined to meet the preset safety authentication condition and the binding time length of the payment account corresponding to the account identification information and the storage account does not exceed the preset time length, carrying out safety authentication processing on the target user through the first client.

One or more embodiments of the present specification provide a binding processing method, which is applied to a second server of a resource storage mechanism. The method includes receiving a binding request sent by a second client of the resource storage mechanism. Wherein the binding request is sent based on a binding operation of a target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application of the target user. The binding request includes first account information of the storage account. And if the target user is determined not to register the payment account of the payment application, sending an account registration request of the target user to a first server of the payment application according to the first account information. So that the first service end sends the account identification information obtained by the registration processing of the payment account to the second service end. And when it is determined that the operation processing of the target user on the first client of the payment application meets a preset safety authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, performing safety authentication processing on the target user through the first client. And receiving the account identification information sent by the first service terminal. And binding according to the account identification information and the first account information. And sending binding result information to the second client.

One or more embodiments of the present specification provide a binding processing method applied to a first client of a payment application. The method comprises the step of receiving an acquisition request of security authentication information sent by a first service terminal of the payment application. The obtaining request is sent after the first server sends account identification information obtained by account registration processing to a second server based on an account registration request of a target user sent by the second server of the resource storage mechanism, and it is determined that operation processing of the target user on the first client meets a preset security authentication condition and binding duration of a payment account corresponding to the account identification information and the target user on a storage account of the resource storage mechanism does not exceed preset duration. The account registration request is sent by the second server based on a binding request sent by the target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered by the target user. And acquiring the equipment information of the terminal equipment, and generating the equipment fingerprint of the terminal equipment according to the equipment information. And sending the device fingerprint to the first service end so that the first service end carries out security authentication processing according to the device fingerprint.

One or more embodiments of the present specification provide a binding processing method applied to a second client of a resource storage mechanism. The method includes sending a binding request to a second server of the resource store mechanism in response to a binding operation by a target user. The binding request is used for requesting to bind the payment account of the payment application of the target user with the storage account of the target user in the resource storage mechanism. The binding request includes first account information of the storage account. And enabling the second server to send an account registration request to the first server of the payment application, and performing binding processing according to the account identification information obtained by performing registration processing on the payment account and sent by the first server and the first account information. And receiving the binding result information sent by the second server. After the first server sends the account identification information to the second server, when it is determined that the operation processing of the target user on the first client of the payment application meets a preset security authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, the first client performs security authentication processing on the target user.

One or more embodiments of the present specification provide a binding processing apparatus, which is applied to a first server of a payment application. The device comprises a receiving module, a first server side and a second server side, wherein the receiving module is used for receiving an account registration request of a target user, and the account registration request is sent by the second server side of the resource storage mechanism. Wherein the account registration request is sent based on a binding request sent by the target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered by the target user. The account registration request includes registration information of the target user. The device also comprises a sending module which sends the account identification information obtained by registering the payment account according to the registration information to the second server so that the second server can carry out binding processing according to the account identification information. The device further comprises an authentication module, and if the operation processing of the target user on the first client of the payment application is determined to meet a preset safety authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account is determined not to exceed a preset duration, the safety authentication processing is performed on the target user through the first client.

One or more embodiments of the present specification provide a binding processing apparatus, which is applied to a second server of a resource storage mechanism. The apparatus includes a receiving module that receives a binding request sent by a second client of the resource storage mechanism. Wherein the binding request is sent based on a binding operation of a target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application of the target user. The binding request includes first account information of the storage account. The device further comprises a determining module, and if the target user is determined not to register the payment account of the payment application, the determining module sends an account registration request of the target user to a first server of the payment application according to the first account information. So that the first service end sends the account identification information obtained by the registration processing of the payment account to the second service end. And when it is determined that the operation processing of the target user on the first client of the payment application meets a preset safety authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, performing safety authentication processing on the target user through the first client. The device also comprises a binding module which receives the account identification information sent by the first service terminal. And binding according to the account identification information and the first account information. The device also comprises a sending module which sends the binding result information to the second client.

One or more embodiments of the present specification provide a binding processing apparatus applied to a first client of a payment application. The device comprises a receiving module, a processing module and a processing module, wherein the receiving module receives an acquisition request of security authentication information sent by a first service terminal of the payment application. The obtaining request is sent after the first server sends account identification information obtained by account registration processing to a second server based on an account registration request of a target user sent by the second server of the resource storage mechanism, and it is determined that operation processing of the target user on the first client meets a preset security authentication condition and binding duration of a payment account corresponding to the account identification information and the target user on a storage account of the resource storage mechanism does not exceed preset duration. The account registration request is sent by the second server based on a binding request sent by the target user; the binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered by the target user. The device also comprises an acquisition module, which acquires the equipment information of the terminal equipment and generates the equipment fingerprint of the terminal equipment according to the equipment information. The apparatus also includes a sending module that sends the device fingerprint to the first server. And the first server side performs security authentication processing according to the device fingerprint.

One or more embodiments of the present specification provide a binding processing apparatus applied to a second client of a resource storage mechanism. The apparatus includes a sending module that sends a binding request to a second server of the resource store mechanism in response to a binding operation by a target user. The binding request is used for requesting to bind the payment account of the payment application of the target user with the storage account of the target user in the resource storage mechanism. The binding request comprises first account information of the storage account, so that the second server sends an account registration request to the first server of the payment application. And binding the account identification information obtained by the registration processing of the payment account and the first account information, which are sent by the first server. The device also comprises a receiving module which receives the binding result information sent by the second server. After the first server sends the account identification information to the second server, when it is determined that the operation processing of the target user on the first client of the payment application meets a preset security authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, the first client performs security authentication processing on the target user.

One or more embodiments of the present specification provide a binding processing device. The apparatus includes a processor. The apparatus also comprises a memory arranged to store computer executable instructions. The computer-executable instructions, when executed, cause the processor to receive an account registration request of a target user sent by a second server of a resource storage mechanism. Wherein the account registration request is sent based on a binding request sent by the target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered by the target user. The account registration request includes registration information of the target user. And sending the account identification information obtained by performing the registration processing of the payment account according to the registration information to the second server, so that the second server performs the binding processing according to the account identification information. And if the operation processing of the target user on the first client of the payment application is determined to meet the preset safety authentication condition and the binding time length of the payment account corresponding to the account identification information and the storage account does not exceed the preset time length, carrying out safety authentication processing on the target user through the first client.

One or more embodiments of the present specification provide a binding processing device. The apparatus includes a processor. The apparatus also comprises a memory arranged to store computer executable instructions. The computer-executable instructions, when executed, cause the processor to receive a binding request sent by a second client of the resource storage mechanism. Wherein the binding request is sent based on a binding operation of a target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application of the target user. The binding request includes first account information of the storage account. And if the target user is determined not to register the payment account of the payment application, sending an account registration request of the target user to a first server of the payment application according to the first account information. So that the first service end sends the account identification information obtained by the registration processing of the payment account to the second service end. And when it is determined that the operation processing of the target user on the first client of the payment application meets a preset safety authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, performing safety authentication processing on the target user through the first client. And receiving the account identification information sent by the first service terminal. And binding according to the account identification information and the first account information. And sending binding result information to the second client.

One or more embodiments of the present specification provide a binding processing device. The apparatus includes a processor. The apparatus also comprises a memory arranged to store computer executable instructions. The computer executable instructions, when executed, cause the processor to receive an acquisition request for security authentication information sent by a first service end of the payment application. The obtaining request is sent after the first server sends account identification information obtained by account registration processing to a second server based on an account registration request of a target user sent by the second server of the resource storage mechanism, and it is determined that operation processing of the target user on the first client meets a preset security authentication condition and binding duration of a payment account corresponding to the account identification information and the target user on a storage account of the resource storage mechanism does not exceed preset duration. The account registration request is sent by the second server based on a binding request sent by the target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered by the target user. And acquiring the equipment information of the terminal equipment, and generating the equipment fingerprint of the terminal equipment according to the equipment information. And sending the device fingerprint to the first service end so that the first service end carries out security authentication processing according to the device fingerprint.

One or more embodiments of the present specification provide a binding processing device. The apparatus includes a processor. The apparatus also comprises a memory arranged to store computer executable instructions. The computer-executable instructions, when executed, cause the processor to send a bind request to a second server of the resource store mechanism in response to a bind operation by a target user. The binding request is used for requesting to bind the payment account of the payment application of the target user with the storage account of the target user in the resource storage mechanism. The binding request includes first account information of the storage account. And enabling the second server to send an account registration request to the first server of the payment application, and performing binding processing according to the account identification information obtained by performing registration processing on the payment account and sent by the first server and the first account information. And receiving the binding result information sent by the second server. After the first server sends the account identification information to the second server, when it is determined that the operation processing of the target user on the first client of the payment application meets a preset security authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, the first client performs security authentication processing on the target user.

One or more embodiments of the present specification provide a storage medium. The storage medium is used to store computer-executable instructions. The computer-executable instructions, when executed, receive an account registration request of a target user sent by a second server of a resource storage mechanism. Wherein the account registration request is sent based on a binding request sent by the target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered by the target user. The account registration request includes registration information of the target user. And sending the account identification information obtained by performing the registration processing of the payment account according to the registration information to the second server, so that the second server performs the binding processing according to the account identification information. And if the operation processing of the target user on the first client of the payment application is determined to meet the preset safety authentication condition and the binding time length of the payment account corresponding to the account identification information and the storage account does not exceed the preset time length, carrying out safety authentication processing on the target user through the first client.

One or more embodiments of the present specification provide a storage medium. The storage medium is used to store computer-executable instructions. The computer-executable instructions, when executed, receive a binding request sent by a second client of the resource storage mechanism. Wherein the binding request is sent based on a binding operation of a target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application of the target user. The binding request includes first account information of the storage account. And if the target user is determined not to register the payment account of the payment application, sending an account registration request of the target user to a first server of the payment application according to the first account information. So that the first service end sends the account identification information obtained by the registration processing of the payment account to the second service end. And when it is determined that the operation processing of the target user on the first client of the payment application meets a preset safety authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, performing safety authentication processing on the target user through the first client. And receiving the account identification information sent by the first service terminal. And binding according to the account identification information and the first account information. And sending binding result information to the second client.

One or more embodiments of the present specification provide a storage medium. The storage medium is used to store computer-executable instructions. The computer-executable instructions, when executed, receive an acquisition request for security authentication information sent by a first service end of the payment application. The obtaining request is sent after the first server sends account identification information obtained by account registration processing to a second server based on an account registration request of a target user sent by the second server of the resource storage mechanism, and it is determined that operation processing of the target user on the first client meets a preset security authentication condition and binding duration of a payment account corresponding to the account identification information and the target user on a storage account of the resource storage mechanism does not exceed preset duration. The account registration request is sent by the second server based on a binding request sent by the target user. The binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered by the target user. And acquiring the equipment information of the terminal equipment, and generating the equipment fingerprint of the terminal equipment according to the equipment information. And sending the device fingerprint to the first service end so that the first service end carries out security authentication processing according to the device fingerprint.

One or more embodiments of the present specification provide a storage medium. The storage medium is used to store computer-executable instructions. The computer-executable instructions, when executed, send a binding request to a second server of the resource storage mechanism in response to a binding operation of the target user. The binding request is used for requesting to bind the payment account of the payment application of the target user with the storage account of the target user in the resource storage mechanism. The binding request includes first account information of the storage account. And enabling the second server to send an account registration request to the first server of the payment application, and performing binding processing according to the account identification information obtained by performing registration processing on the payment account and sent by the first server and the first account information. And receiving the binding result information sent by the second server. After the first server sends the account identification information to the second server, when it is determined that the operation processing of the target user on the first client of the payment application meets a preset security authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, the first client performs security authentication processing on the target user.

Drawings

In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, the drawings that are needed in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and that other drawings can be obtained by those skilled in the art without inventive exercise.

Fig. 1 is a first schematic view of a binding processing method according to one or more embodiments of the present disclosure;

fig. 2 is a schematic diagram of a second scenario of a binding processing method according to one or more embodiments of the present disclosure;

fig. 3 is a first flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 4 is a second flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 5 is a third flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 6 is a fourth flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 7 is a fifth flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 8 is a sixth flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 9 is a seventh flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 10 is an eighth flowchart of a binding processing method according to one or more embodiments of the present specification;

fig. 11 is a ninth flowchart illustrating a binding processing method according to one or more embodiments of the present disclosure;

fig. 12 is a tenth flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 13 is an eleventh flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 14 is a twelfth flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 15 is a thirteenth flowchart illustrating a binding processing method according to one or more embodiments of the present disclosure;

fig. 16 is a fourteenth flowchart illustrating a binding processing method according to one or more embodiments of the present disclosure;

fig. 17 is a fifteenth flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 18 is a sixteenth flowchart of a binding processing method according to one or more embodiments of the present disclosure;

fig. 19 is a schematic diagram illustrating a first module composition of a binding processing apparatus according to one or more embodiments of the present disclosure;

fig. 20 is a schematic diagram illustrating a second module composition of a binding processing apparatus according to one or more embodiments of the present disclosure;

fig. 21 is a schematic diagram illustrating a third module composition of a binding processing apparatus according to one or more embodiments of the present disclosure;

fig. 22 is a schematic diagram illustrating a fourth module composition of a binding processing apparatus according to one or more embodiments of the present disclosure;

fig. 23 is a schematic structural diagram of a binding processing device according to one or more embodiments of the present specification.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

Fig. 1 is a schematic view of an application scenario of a binding processing method according to one or more embodiments of the present specification, as shown in fig. 1, the scenario includes: the system comprises a first client of the payment application, a first server of the payment application, a second client of the resource storage mechanism and a second server of the resource storage mechanism. The first client and the second client may be a mobile phone, a tablet computer, a desktop computer, a portable notebook computer, or the like (only the mobile phone is shown in fig. 1); it should be understood that, an application program (app for short) of the payment application is installed in the first client, and a resource management application program of the resource storage mechanism is installed in the second client; the first server and the second server may be independent servers, or may be a server cluster composed of a plurality of servers.

Specifically, when the target user is located anywhere, such as at home, at a company, at a resource storage mechanism, etc., if the payment account of the payment application to be registered needs to be bound with the storage account of the resource storage mechanism, the second client of the resource storage mechanism may be operated to perform account binding processing. And the second client responds to the binding operation of the target user, and sends a binding request to the second server so as to request that the storage account of the target user in the resource storage mechanism is bound with the payment account of the payment application of the target user, so that the payment authority for payment of the payment account based on the storage account is granted. The second server receives the binding request sent by the second client, determines whether the target user has registered the payment account of the payment application according to the first account information of the storage account to be bound, which is included in the binding request, and sends an account registration request to the first server if the determination result is negative. The first server side performs registration processing on the payment account according to the registration information included in the account registration request to obtain account identification information of the target user, and sends the account identification information to the first server side; and the first server performs binding processing according to the received account identification information and the first account information of the storage account to be bound, and sends binding result information to the second client. And when the binding result information is binding success information and the target user operates the first client to perform related service processing, if the first service end determines that the operation processing of the target user on the first client meets the preset safety authentication condition, performing safety authentication processing on the target user through the first client. It should be noted that, when the target user has registered the payment account of the payment application and needs to bind the payment account with the storage account of the target user in the resource storage mechanism, the second client may also be operated to implement account binding, and a specific process is described in detail later.

Further, as shown in fig. 2, the second client may also be a self-service operating machine of the resource storage mechanism, specifically, when the target user performs service transaction in the resource storage mechanism, for example, opening a storage account, performing resource transfer, and the like, if the target user has a need to bind the payment account of the payment application to be registered with the storage account of the resource storage mechanism, the self-service operating machine of the resource storage mechanism may be operated, and the self-service operating machine sends a binding request to the second server of the resource storage mechanism based on the binding operation of the target user, so as to implement registration of the payment account and binding of the payment account with the storage account in the above manner. Particularly, when the self-service operation machine has a function of opening a storage account, the opening of the storage account, the registration of a payment account, the binding of the storage account and the payment account, and the like can be simultaneously realized. Generally, the opening of the storage account, the registration of the payment account and the like all need to perform identity authentication on the target user, and at this time, the opening of the storage account, the registration of the payment account and the like can be simultaneously realized through one-time identity authentication, so that the user operation can be reduced, and the user experience is improved.

Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Fig. 3 is a flowchart illustrating a binding processing method according to one or more embodiments of the present specification, where the method in fig. 3 can be executed by the first server in fig. 1, as shown in fig. 3, and the method includes the following steps:

step S102, receiving an account registration request of a target user sent by a second server of the resource storage mechanism; the account registration request is sent by the second server when the second server receives a binding request sent by a second client of the resource storage mechanism used by the target user and determines that the target user does not register the payment account of the payment application; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of a payment application to be registered by the target user so as to grant payment authority of the payment account for payment based on the storage account; the account registration request comprises registration information of the target user;

specifically, when the target user needs to bind the payment account of the payment application to be registered with the storage account of the resource storage mechanism, the second client of the resource storage mechanism may be operated to perform account binding processing. And the second client responds to the binding operation of the target user and sends a binding request to a second server of the resource storage mechanism so as to request to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered of the target user. And after receiving the binding request sent by the second client, the second server determines whether the target user has registered the payment account of the payment application according to the first account information of the storage account to be bound, which is included in the binding request, and sends an account registration request to the first server if the determination result is negative. The storage account of the target user in the resource storage mechanism may be a savings account, a credit account, or the like.

Step S104, registering the payment account according to the registration information to obtain account identification information of the target user;

step S106, the account identification information is sent to the second server, so that the second server performs binding processing according to the account identification information;

step S108, if the operation processing of the target user on the first client of the payment application is determined to meet the preset safety authentication condition, the safety authentication processing is carried out on the target user through the first client.

In one or more embodiments of the present specification, when receiving an account registration request sent by a second server of a resource storage mechanism, a first server performs registration processing on a payment account, and sends obtained account identification information of a target user to the second server, so that the second server performs binding processing according to the account identification information; the account registration request is sent when the second server receives a binding request sent by a second client of the resource storage mechanism used by the target user and determines that the target user does not register the payment account of the payment application; and the first server side performs security authentication processing on the target user through the first client side after determining that the operation processing of the target user on the first client side of the payment application meets a preset security authentication condition. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Considering that the target user may have registered the payment account when the target user operates the second client to perform the binding operation between the payment account and the storage account; based on this, in order to avoid repeated registration of the payment account, in one or more embodiments of the present specification, when the second server receives the binding request sent by the second client, a payment account inquiry request is first sent to the first server to determine whether the target user has registered the payment account of the payment application. Correspondingly, as shown in fig. 4, before step S102, the method may further include:

step S100-2, receiving a payment account inquiry request sent by a second server; the payment account inquiry request is sent by the second server when receiving a binding request sent by a second client of the resource storage mechanism used by a target user; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application of the target user so as to grant payment authority of the payment account for payment based on the storage account; the payment account inquiry request comprises identity information of a target user associated with the storage account;

the identity information is provided when a target user opens a storage account in a resource storage mechanism, and the identity information is authenticated by authority and has authenticity and validity; such as the user name of the target user, the identification document number of the target user, etc.

And S100-4, if the associated account identification information is not inquired according to the identity information, sending an inquiry result representing that the account identification information is not inquired to the second server, so that the second server determines the payment account of the target user unregistered payment application and sends an account registration request.

Specifically, the first service end matches the identity information included in the payment account query request with each identity information in the designated user information base, and sends a query result representing that account identification information is not queried to the second service end when all matching fails. The user information base comprises the incidence relation between the identity information of a plurality of users and the account identification information of the payment account.

Correspondingly, as shown in fig. 4, step S102 includes the following steps S102-2;

step S102-2, receiving an account registration request of a target user sent by a second server; wherein the account registration request includes registration information of the target user;

in order to realize the binding of the payment account to be registered and the storage account to be bound, and facilitate subsequent security authentication of the target user, in one or more embodiments of the present specification, the account inquiry request further includes first account information of the storage account to be bound, and the registration request further includes a contact manner of the target user associated with the storage account to be bound. Specifically, as shown in fig. 5, step S104 may include the following steps S104-2 and S104-4;

step S104-2, generating account identification information of a target user according to a preset generation rule of the account identification;

the generation rule may be set in practical application as needed, and is not specifically limited in this specification.

Step S104-4, the generated account identification information, the contact information and the identity information of the registration information, the first account information of the storage account included in the account inquiry request and the first authentication identification representing the security authentication to be performed are subjected to associated recording to obtain first recording information;

generally, when a payment account is registered, a client needs to collect identity information provided by a user and verify the collected identity information. In the embodiment of the specification, because the identity information in the account inquiry request sent by the second server is the identity information provided by the target user when the resource storage mechanism sets up the storage account, and the identity information is authenticated by authority and has authenticity and validity, when the first server performs the registration processing of the payment account, the first server does not need to acquire the identity information provided by the user again, and can directly perform the registration processing of the payment account based on the identity information in the account inquiry request, so that the registration of the payment account is completed under the condition that the user feels no sense, the user operation is reduced, and the user experience is improved.

In order to avoid performing security authentication on the target user for multiple times, as shown in fig. 5, in one or more embodiments of the present specification, if the security authentication is passed in step S108, the method further includes:

step S110, updating the first authentication identifier in the first record information to be a second authentication identifier; and the second authentication identification represents that the security authentication passes.

In order to ensure the security of the registration of the payment account, in one or more embodiments of the present specification, the registration information includes the contact information of the target user associated with the storage account to be bound, and accordingly, as shown in fig. 6, step S104 may include the following steps S104-6 to S104-10:

step S104-6, first verification information is sent to a contact way included in the registration information, so that the second client sends the acquired first verification information to be verified, which is input by the target user, to the second server, and the second server sends the first verification information to be verified to the first server;

step S104-8, receiving first verification information to be verified, which is sent by a second server;

and step S104-10, if the first verification information to be verified passes the verification, performing registration processing on the payment account according to the registration information to obtain account identification information of the target user.

The contact information may be a mobile phone number, an email address, etc. Taking the contact way as a mobile phone number as an example for explanation, after sending an account registration request to the first service side, the second service side also sends a verification information acquisition request to the second client side; the second client displays an input interface of the verification information based on the verification information acquisition request; after receiving the account registration request, the first service end sends first verification information to the mobile phone number in an information mode, and stores the first verification information and the first contact way in a related mode; when a target user receives information sent by a first service terminal, inputting first verification information in the information into an input interface displayed by a second client terminal, and clicking a determination control in the input interface to submit the first verification information to be verified; the second client acquires first verification information to be verified submitted by a target user, and sends the first verification information to be verified and the contact information to the second server; the second server side sends the received first verification information to be verified and the contact information to the first server side; the first server side inquires first verification information stored in association according to the received contact information, matches the inquired first verification information with first verification information to be verified, if the matching is successful, the verification is determined to be passed, and account registration processing is carried out according to registration information; and if the matching fails, sending registration failure information to the second server side so that the second server side sends binding failure information to the second client side.

Therefore, the first server sends the first verification code to the contact way included in the registration information and verifies the first verification code, so that the risk that other people impersonate the target user to operate can be reduced, and the service safety is ensured.

Considering that in this embodiment of the present specification, the registration of the payment account and the secure authentication of the target user are performed asynchronously, in order to avoid the potential safety hazard caused by the long asynchronous time interval, as shown in fig. 7, in one or more embodiments of the present specification, after step S106, the method further includes:

step S107, recording the sending time of the account identification information;

optionally, the sending time is recorded in association with the first record information, or the sending time is recorded in association with the account identification information.

Correspondingly, as shown in fig. 7, step S108 may include the following steps S108-2 to S108-8:

step S108-2, if the target user is determined to successfully log in the first client of the payment application and the authentication identifier in the first record information inquired according to the contact information in the login information is the first authentication identifier, determining whether the number of account identification information associated with the identity information in the inquired first record information does not exceed a preset number;

step S108-4, acquiring current time, and determining the binding duration of the payment account and the storage account corresponding to the first record information according to the recorded sending time and the current time;

step S108-6, determining whether the binding time length exceeds a preset time length;

step S108-8, if it is determined that the number of the account identification information associated with the identity information does not exceed the preset number and the binding duration does not exceed the preset duration, it is determined that the operation processing of the target user on the first client of the payment application meets the preset security authentication condition, and the security authentication processing is performed on the target user through the first client.

Because the registration of the payment account is performed under the condition that the target user is not sensitive, that is, the target user is not required to set account information of the payment account, the target user can log in through the contact way of the target user associated with the bound storage account when logging in for the first time. Specifically, when the first service end determines that the target user successfully logs in the first client end, the first service end queries related first record information according to the contact information included in the login information, determines whether an authentication identifier included in the first record information is a first authentication identifier, and waits for a service request sent by the first client end if the authentication identifier is not the first authentication identifier; if the account identification information is the first authentication identification, inquiring the quantity of the associated account identification information according to the identity information in the first record information, determining whether the inquired quantity exceeds a preset quantity, if not, acquiring the current time, and determining the binding duration of the payment account corresponding to the account identification information in the first record information and the storage account corresponding to the first account information according to the recorded sending time and the acquired current time; determining whether the binding time length exceeds a preset time length, if so, sending first prompt information to the first client side so that the target user can perform binding operation of the storage account again, or perform security authentication by using other security authentication modes approved by the payment application; and if the preset time length is not exceeded, determining that the preset safety authentication condition is met, and performing safety authentication processing on the target user through the first client. The preset quantity is the upper limit of the quantity of the payment accounts which can be registered by the user, and the preset quantity and the preset duration can be set in practical application according to needs.

It should be noted that, if the first service end receives the service request sent by the first client in the process of determining whether the preset security authentication condition is met or when the preset security authentication condition is met, and the service request needs to perform security authentication processing on the target user, the target user may be subjected to security authentication processing based on the service request. And when the first client receives the first prompt message sent by the first server, the target user can operate the first client to bind other storage accounts.

By judging the quantity of the account identification information associated with the identity information and the binding time, the risk of illegal operation caused by excessive registration of the payment account by the user can be avoided, and potential safety hazards caused by too long binding time can be avoided.

Further, in the process that the target user logs in the first client through the contact manner, the step of determining, by the first service end, that the target user successfully logs in the first client includes:

receiving a login request sent by a first client, and sending second verification information to a contact way included in the login request so that the first client sends the acquired second verification information to be verified, which is input by a target user, to a first service end; and receiving second authentication information to be authenticated sent by the first client, and determining that the target user successfully logs in the first client if the second authentication information to be authenticated passes the authentication.

Specifically, the login interface of the first client comprises an account input field, a verification information acquisition control and a verification information input field, and after a target user inputs a contact way of the target user associated with a storage account in the account input field, the verification information acquisition control can be clicked; after detecting the click operation of the verification information acquisition control, the first client sends a login request to the first service end according to the acquired contact way, and if the first service end inquires the associated first record information according to the contact way included in the login request, the first service end sends second verification information to the contact way and stores the second verification information in association with the contact way; the target user inputs the received second verification information into the verification information input field and clicks the determination control; the first client sends the acquired second verification information to be verified and the contact way to the first service end; the first server side inquires the second verification information stored in association according to the received contact information, matches the inquired second verification information with the received second verification information to be verified, if matching is successful, the target user is determined to be successful in login, and if matching is failed, login failure information is sent to the first client side. Therefore, the first login of the target user is completed based on the contact way and the second verification information, after the login is successful, the first server side can modify account information, login passwords and the like of a payment account of the target user based on an account modification request sent by the target user through the first client side, and the target user can subsequently log in based on the modified account information and login passwords.

In order to avoid malicious machine behaviors, in one or more embodiments of the present disclosure, as shown in fig. 8, step S108 may include the following steps S108-10 and S108-12:

step S108-10, if the operation processing of the target user on the first client of the payment application is determined to meet the preset safety authentication condition, sending an acquisition request of safety authentication information to the first client, so that the first client acquires the equipment information of the terminal equipment, generates an equipment fingerprint based on the equipment information, and sends the equipment fingerprint to the first service end;

and S108-12, receiving the device fingerprint sent by the first client, and if the risk assessment according to the device fingerprint is determined to pass, determining that the security authentication of the target user passes.

Specifically, an equipment fingerprint sent by a first client is received, and the equipment fingerprint is sent to a designated risk assessment system, so that the risk assessment system carries out risk assessment based on the equipment fingerprint and sends a risk assessment result to a first server; and if the first service end determines that the received risk evaluation result is risk-free, determining that the security authentication of the target user passes.

It should be emphasized that, when the first user operates the first client to register the payment account of the payment application for the first time, the first service end first obtains the device fingerprint of the terminal device where the first client is located during the registration processing of the payment account, and performs the registration processing of the payment account after the device fingerprint is verified. In the embodiment of the application, an asynchronous security authentication mode is provided, that is, after a target user operates a second client to register a payment account and bind the payment account with a storage account, security authentication processing is performed when the target user logs in a first client for the first time, so that not only can the security authentication requirement of payment application be met, but also the account binding requirement of the user in an account binding scene based on the second client can be met.

Further, when the target user has registered the payment account of the payment application, the target user may also operate the second client to bind the payment account with the storage account, specifically, as shown in fig. 9, after step S100-2, the method may further include:

step S112, if the associated account identification information is inquired according to the identity information, the inquired account identification information is sent to the second server, so that the second server performs binding processing according to the account identification information;

step S114, the first account information of the storage account included in the account inquiry request and the sent account identification information are subjected to associated recording to obtain second recording information; and the second record information represents that the payment account corresponding to the sent account identification information is successfully bound with the storage account.

When the associated account identification information is inquired according to the identity information, the target user is determined to register the payment account of the payment application, and because the security authentication processing is carried out in the previous registration process of the payment account, the inquired account identification information can be directly sent to the second server side so as to enable the second server side to carry out binding processing; and performing association recording on the first account information of the storage account included in the account query request and the queried account identification information to represent that the binding is successful, and when the target user logs in the second client, performing security authentication again is not needed.

Further, considering that the target user may also have registered multiple payment accounts, as shown in fig. 10, step S112 may specifically include:

step S112-2, if the associated account identification information is inquired according to the identity information, determining whether the quantity of the inquired account identification information is one, if so, executing step S112-4, otherwise, executing step S112-6;

step S112-4, sending the inquired account identification information to a second server, so that the second server performs binding processing according to the account identification information, and executing step S114;

step S112-6, address information is obtained from the account inquiry request, second account information of the payment account corresponding to the inquired account identification information is displayed on a display interface corresponding to the address information in the second client, and target second account information selected by the target user based on the display interface is obtained;

and step S112-8, sending the account identification information corresponding to the target second account information to the second server, and executing step S114.

Therefore, when the plurality of account identification information are inquired, the corresponding second account information is displayed in the corresponding display interface based on the address information included in the account inquiry request, the target second account information selected by the target user based on the display interface is obtained, and the target second account information does not need to be obtained through the second server, so that the leakage of the account information of the user is avoided, the communication frequency is reduced, and the data processing efficiency is improved.

On the basis of the same technical concept, corresponding to the binding processing methods described in fig. 3 to fig. 10, another binding processing method is provided in one or more embodiments of the present specification, fig. 11 is a flowchart illustrating another binding processing method provided in one or more embodiments of the present specification, and the method in fig. 11 can be executed by a second server of the resource storage mechanism in fig. 1; as shown in fig. 11, the method comprises the steps of:

step S202, receiving a binding request sent by a second client of the resource storage mechanism; the method comprises the steps that a binding request is sent based on the binding operation of a target user, and the binding request is used for requesting to bind a storage account of the target user in a resource storage mechanism with a payment account of a payment application of the target user so as to grant payment authority of the payment account for payment based on the storage account; the binding request comprises first account information of the storage account;

specifically, when the target user needs to bind the payment account of the payment application to be registered with the storage account of the resource storage mechanism, the second client of the resource storage mechanism may be operated to perform account binding processing. And the second client responds to the binding operation of the target user and sends a binding request to a second server of the resource storage mechanism so as to request to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application to be registered of the target user.

Step S204, if the payment account of the payment application is determined not to be registered by the target user, sending an account registration request of the target user to a first service end of the payment application according to the first account information so that the first service end performs registration processing of the payment account to obtain account identification information of the target user, and performing security authentication processing on the target user through a first client end when the operation processing of the target user on the first client end of the payment application is determined to meet a preset security authentication condition;

step S206, receiving the account identification information sent by the first server, performing binding processing according to the account identification information and the first account information, and sending binding result information to the second client.

In one or more embodiments of the present description, when receiving a binding request sent by a second client of a resource storage mechanism, a second server of the resource storage mechanism sends the binding request based on a binding operation of a target user; if the target user does not register the payment account of the payment application, sending an account registration request of the target user to a first service end of the payment application according to first account information of a storage account included in the binding request, and carrying out binding processing according to account identification information sent by the first service end. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

In order to facilitate the first server to query the account identification information of the payment account, in one or more embodiments of the present specification, as shown in fig. 12, step S204 may include the following steps S204-2 to S204-8:

step S204-2, acquiring the identity information of the associated target user from the specified database according to the first account information;

the designated database comprises the association relation between the first account information and the identity information, the contact information and the like.

Step S204-4, according to the acquired identity information and the first account information, sending an account query request to the second server, so that the second server queries the associated account identification information according to the identity information;

step S204-6, if a query result which is sent by the second server and represents that account identification information is not queried is received, determining that a payment account of the payment application is not registered by the target user;

step S204-8, an account registration request of the target user is sent to the first service end of the payment application according to the first account information, so that the first service end performs registration processing of the payment account to obtain account identification information of the target user, and when it is determined that operation processing of the target user on the first client end of the payment application meets preset safety authentication conditions, safety authentication processing is performed on the target user through the first client end.

In order to facilitate the first server to perform the registration process of the payment account and subsequently log in the second client by the target user, in one or more embodiments of the present specification, as shown in fig. 13, step S204 may further include the following steps S204-10 and S204-12;

step S204-10, if the payment account of the payment application is determined not to be registered by the target user, acquiring the contact information of the associated target user from the specified database according to the first account information;

step S204-12, according to the contact way, sending an account registration request of the target user to the first service end of the payment application, so that when the first service end performs the registration processing of the payment account, the first verification information is sent to the contact way.

Correspondingly, in order to secure the registration of the payment account, as shown in fig. 13, after step S204-12, the method further includes:

step S205-2, sending a verification information acquisition request to the second client so that the second client displays the input interface and acquires first verification information to be verified, which is input by the target user based on the input interface;

step S205-4, receiving first verification information to be verified, which is sent by a second client;

step S205-6, the first verification information to be verified is sent to the first service end, so that the first service end performs registration processing on the payment account when the first verification information is verified to pass.

Further, in order to confirm that the target user binds the payment account of the payment application with the storage account of the resource storage mechanism, in one or more embodiments of the present specification, as shown in fig. 14, step S204 may further include the following steps S204-14;

step S204-14, if the target user is determined not to register the payment account of the payment application and the signing information of the preset binding protocol signed by the target user is determined to be acquired, sending an account registration request of the target user to a first service end of the payment application according to the first account information.

Optionally, the binding request includes signing information of a preset binding protocol, and accordingly, the second server acquires the signing information from the binding request; or after receiving the binding request sent by the second client, the second server sends a binding protocol signing request to the second client, so that the second client displays the preset binding protocol and acquires signing information of the binding protocol signed by the target user, and sends the acquired signing information to the second server. It should be noted that, the signing process of the signing agreement is not specifically limited in this specification, and may be set in an actual application as needed. By having the target user sign the binding agreement, not only can the user be informed of the relevant matters, but also the signed information can be used as confirmation information for the target user to confirm the binding.

Further, as shown in fig. 15, in one or more embodiments of the present specification, step S206 includes:

step S206-2, the received account identification information and the first account information are subjected to associated recording to obtain third recording information; the third record information represents that the payment account corresponding to the account identification information is successfully bound with the storage account corresponding to the first account information;

and step S206-4, sending the binding success information to the second client.

Further, when the binding processing of the second server fails, the binding failure information is sent to the second client.

It should be noted that, for specific implementation of the above steps, reference may be made to the foregoing related description, and repeated details are not described here.

Corresponding to the binding processing method described above, based on the same technical concept, one or more embodiments of the present specification further provide another binding processing method, fig. 16 is a flowchart of another binding processing method provided by one or more embodiments of the present specification, and the method in fig. 16 can be executed by the first client of the payment application in fig. 1; as shown in fig. 16, the method includes the steps of:

step S302, receiving a request for acquiring security authentication information sent by a first server of a payment application; the obtaining request is sent when the operation processing of the target user on the first client side is determined to meet the preset safety certification condition after the first server side carries out account registration processing on the account registration request of the target user sent by the second server side based on the resource storage mechanism; the account registration request is a binding request sent by a second server based on a second client of the target user using the resource storage mechanism and is sent when the target user is determined not to register the payment account of the payment application; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of a payment application to be registered by the target user so as to grant payment authority of the payment account for payment based on the storage account;

step S304, acquiring the equipment information of the terminal equipment, and generating the equipment fingerprint of the terminal equipment according to the equipment information;

the device information includes information such as device identification, MAC address of the device, system version number of the device, and the like. The generation mode of the device fingerprint can be set in practical application according to needs, and is not limited in this specification.

Step S306, the device fingerprint is sent to the first service end, so that the first service end performs security authentication processing according to the device fingerprint.

In one or more embodiments of the present specification, step S302 may further include, before:

step S300-2, responding to the login operation of the target user based on the login interface, and sending a login request to the first service terminal; the login request comprises a contact information of a target user associated with the storage account, so that the first server side sends second verification information to the contact information;

step S300-4, second authentication information to be authenticated input by a target user in a login interface is obtained, and the second authentication information to be authenticated is sent to a first service end, so that the first service end authenticates the second authentication information to be authenticated;

and step S300-6, receiving login result information sent by the first server.

In one or more embodiments of the present specification, when receiving an acquisition of security authentication information sent by a first service end of a payment application, a first client of the payment application generates a device fingerprint of a terminal device where the first client is located, and sends the device fingerprint to the first service end, so that the first service end performs security authentication processing; the obtaining request is sent when the operation processing of the target user on the first client side is determined to meet the preset safety certification condition after the first server side carries out account registration processing on the account registration request of the target user sent by the second server side based on the resource storage mechanism; and the account registration request is a binding request sent by a second server based on a second client of the target user using the resource storage mechanism, and is sent when the target user is determined not to register the payment account of the payment application. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Corresponding to the above-described binding processing method, based on the same technical concept, one or more embodiments of the present specification further provide another binding processing method, fig. 17 is a flowchart of another binding processing method provided by one or more embodiments of the present specification, and the method in fig. 17 can be executed by a second client of the resource storage mechanism in fig. 1; as shown in fig. 17, the method includes the steps of:

step S402, responding to the binding operation of the target user, and sending a binding request to a second server of the resource storage mechanism; the binding request is used for requesting to bind a payment account of a payment application of a target user with a storage account of the target user in a resource storage mechanism so as to grant payment authority of the payment account for payment based on the storage account; the binding request comprises first account information of a storage account, so that the second server side carries out binding processing according to the first account information;

step S404, receiving the binding result information sent by the second server.

In order to ensure the security of the registration of the payment account, in one or more embodiments of the present specification, as shown in fig. 18, after step S402, the method further includes:

step S403-2, receiving a verification information acquisition request sent by a second server; the authentication information acquisition request is sent based on an account registration request of a target user sent to a first server of the payment application;

step S403-4, an input interface is displayed according to the verification information acquisition request;

step S403-6, acquiring first verification information to be verified, which is input in an input interface by a target user;

step S403-8, the acquired first verification information to be verified is sent to the second server, so that the second server sends the first verification information to be verified to the first server, and the first server performs registration processing on the payment account when the first verification information to be verified passes verification.

Further, in order to enable the second server to determine that the target user agrees to bind the payment account of the target user with the storage account, in one or more embodiments of the present specification, step S404 further includes:

and acquiring the signing information of the target user signing the preset binding protocol, and sending the signing information to the second server so that the second server performs related processing based on the signing information.

Optionally, in response to the binding operation of the target user, the signing information that the target user signs the preset binding protocol is obtained, and a binding request is sent to the second server according to the obtained signing information and the first account information of the storage account to be bound. Or after sending the binding request to the second server, receiving a protocol signing request sent by the second server, displaying the preset signing protocol, and acquiring signing information of the preset binding protocol signed by the target user.

It should be noted that, for the specific implementation process of the above steps, reference may be made to the foregoing related description, and repeated details are not described here.

In one or more embodiments of the present specification, the second client, in response to a binding operation of a target user, sends a binding request to a second server of the resource storage mechanism, so that when the second server determines that a payment account of the payment application is not registered by the target user, the second server sends an account registration request to a first server of the payment application, and performs binding processing based on account identification information of the payment account sent by the first server; and when the first server side determines that the preset safety authentication condition is met, carrying out safety authentication processing on the target user. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Corresponding to the binding processing method described above, based on the same technical concept, one or more embodiments of the present specification further provide a binding processing apparatus applied to a first server of a payment application. Fig. 19 is a schematic diagram illustrating a module composition of a binding processing apparatus according to one or more embodiments of the present disclosure, and as shown in fig. 19, the apparatus includes:

a receiving module 501, configured to receive an account registration request of a target user sent by a second server of a resource storage mechanism; the account registration request is sent by the second server when the second server receives a binding request sent by the target user by using a second client of the resource storage mechanism and determines that the target user does not register the payment account of the payment application; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application to be registered by the target user so as to grant the payment account with payment authority for payment based on the storage account; the account registration request comprises registration information of the target user;

a registration module 502, configured to perform registration processing on a payment account according to the registration information to obtain account identification information of the target user;

a sending module 503, configured to send the account identifier information to the second server, so that the second server performs binding processing according to the account identifier information;

an authentication module 504, configured to perform security authentication processing on the target user through a first client of the payment application if it is determined that operation processing of the target user on the first client meets a preset security authentication condition.

In the binding processing apparatus provided in one or more embodiments of the present specification, when an account registration request sent by a second server of a resource storage mechanism is received, registration processing of a payment account is performed, and obtained account identification information of a target user is sent to the second server, so that the second server performs binding processing according to the account identification information; the account registration request is sent when the second server receives a binding request sent by a second client of the resource storage mechanism used by the target user and determines that the target user does not register the payment account of the payment application; and the first server side performs security authentication processing on the target user through the first client side after determining that the operation processing of the target user on the first client side of the payment application meets a preset security authentication condition. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Optionally, the apparatus further comprises: a query module;

the query module receives a payment account query request sent by a second server of the resource storage mechanism before the receiving module 501 receives an account registration request of a target user sent by the second server; wherein the payment account inquiry request is sent based on the binding request, the payment account inquiry request including the identity information of the target user associated with the storage account; and the number of the first and second groups,

if the associated account identification information is not inquired according to the identity information, sending an inquiry result representing that the account identification information is not inquired to the second server, so that the second server determines that the target user does not register the payment account of the payment application, and sending the account registration request.

Optionally, the registration information includes: the contact information of the target user associated with the storage account;

the registration module 502 is configured to send first verification information to the contact information, so that the second client sends the acquired to-be-verified first verification information input by the target user to the second server, and the second server sends the to-be-verified first verification information to the first server; and the number of the first and second groups,

receiving the first verification information to be verified, which is sent by the second server;

and if the first verification information to be verified passes the verification, performing account registration processing according to the registration information.

Optionally, the account query request further includes: first account information of the storage account; the registration information includes: the contact information of the target user associated with the storage account;

the registration module 502 generates account identification information of the target user according to a preset generation rule of the account identification; and the number of the first and second groups,

performing association recording on the generated account identification information, the generated contact information, the generated identity information, the generated first account information and a first authentication identification representing security authentication to be performed to obtain first recording information;

after the security authentication of the target user is passed through the first client, the method further includes:

updating the first authentication identifier in the first record information into a second authentication identifier; wherein the second authentication identification characterizes that the security authentication passes.

Optionally, the apparatus further comprises: a recording module;

the recording module records the sending time of the account identification information after the sending module 503 sends the account identification information to the second server;

the authentication module 504, if it is determined that the target user successfully logs in the first client and the authentication identifier in the first record information queried according to the contact information in the login information is the first authentication identifier, determines whether the number of account identification information associated with the identity information in the queried first record information does not exceed a preset number; and the number of the first and second groups,

acquiring current time, and determining the binding duration of the payment account and the storage account corresponding to the first record information according to the sending time and the current time;

determining whether the binding time length exceeds a preset time length;

if the number of the account identification information associated with the identity information is determined not to exceed the preset number and the binding time length does not exceed the preset time length, determining that the operation processing of the target user on the first client of the payment application meets a preset safety authentication condition.

Optionally, the authentication module 504 receives a login request sent by the first client; and the number of the first and second groups,

sending second verification information to a contact way included in the login request so that the first client sends the acquired second verification information to be verified input by the target user to the first service terminal;

receiving the second verification information to be verified, which is sent by the first client;

and if the second verification information to be verified passes the verification, determining that the target user successfully logs in the first client.

Optionally, the authentication module 504 is configured to send an obtaining request of security authentication information to the first client, so that the first client obtains device information of a terminal device where the first client is located, generates a device fingerprint based on the device information, and sends the device fingerprint to the first service end; and the number of the first and second groups,

and receiving the device fingerprint sent by the first client, and if the risk assessment according to the device fingerprint is determined to pass, determining that the security authentication of the target user passes.

Optionally, the payment account inquiry request further includes: first account information of the storage account; the device further comprises: a correlation module;

the query module is used for sending the queried account identification information to the second server side if the associated account identification information is queried according to the identity information, so that the second server side can perform binding processing according to the account identification information;

the association module is used for performing association recording on the first account information and the inquired account identification information to obtain second recording information; and the second record information represents that the binding between the payment account corresponding to the inquired account identification information and the storage account is successful.

Optionally, the account query request further includes: address information;

the inquiry module is used for determining whether the inquired account identification information is one or not;

if yes, sending the inquired account identification information to the second server;

if not, displaying second account information of the payment account corresponding to the inquired account identification information on a display interface corresponding to the address information in the second client, and acquiring target second account information selected by the target user based on the display interface;

and sending the account identification information corresponding to the target second account information to the second server.

Optionally, the second client includes: a resource management application of the resource storage mechanism or a self-service operator of the resource storage mechanism.

It should be noted that, the embodiment of the binding processing apparatus applied to the first service end in this specification and the embodiment of the binding processing method applied to the first service end in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to the implementation of the binding processing method applied to the first service end, and repeated parts are not described again.

Corresponding to the binding processing method described above, based on the same technical concept, one or more embodiments of the present specification further provide another binding processing apparatus, which is applied to a second server of a resource storage mechanism. Fig. 20 is a schematic block diagram of another binding processing apparatus according to one or more embodiments of the present disclosure, and as shown in fig. 20, the apparatus includes:

a receiving module 601, configured to receive a binding request sent by a second client of the resource storage mechanism; the binding request is sent based on the binding operation of a target user, and the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of a payment application of the target user so as to grant the payment account with payment authority for payment based on the storage account; the binding request includes first account information of the storage account;

a determining module 602, configured to send an account registration request of the target user to a first server of the payment application according to the first account information if it is determined that the target user does not register the payment account of the payment application, so that the first server performs registration processing on the payment account to obtain account identification information of the target user, and performs security authentication processing on the target user through a first client when it is determined that operation processing of the target user on the first client of the payment application satisfies a preset security authentication condition;

a binding module 603, configured to receive the account identifier information sent by the first service end, and perform binding processing according to the account identifier information and the first account information;

a sending module 604, which sends the binding result information to the second client.

One or more embodiments of the present specification provide a binding processing apparatus, upon receiving a binding request sent by a second client of a resource storage mechanism, where the binding request is sent based on a binding operation of a target user; if the target user does not register the payment account of the payment application, sending an account registration request of the target user to a first service end of the payment application according to first account information of a storage account included in the binding request, and carrying out binding processing according to account identification information sent by the first service end. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Optionally, the determining module 602 obtains the associated identity information of the target user from a specified database according to the first account information; and the number of the first and second groups,

sending an account query request to the second server according to the identity information and the first account information, so that the second server queries the associated account identification information according to the identity information;

and if a query result which is sent by the second server and indicates that the account identification information is not queried is received, determining that the target user does not register the payment account of the payment application.

Optionally, the determining module 602 acquires, according to the first account information, a contact address of the associated target user from a designated database; and the number of the first and second groups,

and sending an account registration request of the target user to a first service end of the payment application according to the contact way, so that when the first service end performs registration processing of a payment account, first verification information is sent to the contact way.

Optionally, the sending module 604 sends a verification information obtaining request to the second client, so that the second client displays an input interface and obtains first verification information to be verified, which is input by the target user based on the input interface; and the number of the first and second groups,

receiving the first verification information to be verified, which is sent by the second client;

and sending the first verification information to be verified to the first service end, so that the first service end performs registration processing of a payment account when the first verification information is verified to pass.

Optionally, the determining module 602, if it is determined that the signing information of the preset binding protocol signed by the target user is obtained, sends an account registration request of the target user to the first server of the payment application according to the first account information.

Optionally, the binding module 603 performs association recording on the account identification information and the first account information to obtain third record information; and the third record information represents that the binding of the payment account corresponding to the account identification information and the storage account corresponding to the first account information is successful.

It should be noted that, the embodiment of the binding processing apparatus applied to the second server in this specification and the embodiment of the binding processing method applied to the second server in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to the implementation of the corresponding binding processing method applied to the second server, and repeated details are not repeated.

Further, on the basis of the same technical concept, corresponding to the binding processing method described above, one or more embodiments of the present specification further provide another binding processing apparatus, which is applied to a first client of a payment application. Fig. 21 is a schematic diagram of module components of another binding processing apparatus according to one or more embodiments of the present disclosure, and as shown in fig. 21, the apparatus includes:

a receiving module 701, configured to receive an acquisition request of security authentication information sent by a first service end of the payment application; the obtaining request is sent when the operation processing of the target user on the first client side is determined to meet a preset safety authentication condition after the first server side carries out account registration processing on an account registration request of the target user sent by a second server side based on a resource storage mechanism; the account registration request is sent by the second server side when the target user is determined not to register the payment account of the payment application based on a binding request sent by the target user using a second client of the resource storage mechanism; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application to be registered by the target user so as to grant the payment account with payment authority for payment based on the storage account;

an obtaining module 702, configured to obtain device information of a terminal device where the terminal device is located, and generate a device fingerprint of the terminal device according to the device information;

a sending module 703, configured to send the device fingerprint to the first server, so that the first server performs security authentication processing according to the device fingerprint.

Optionally, the apparatus further comprises: a login module;

the login module is configured to send a login request to the first service end in response to a login operation of the target user based on a login interface before the receiving module 701 receives an acquisition request of security authentication information sent by the first service end of the payment application; the login request comprises a contact way of the target user associated with the storage account, so that the first server side sends second verification information to the contact way; and the number of the first and second groups,

acquiring second verification information to be verified input by the target user in the login interface;

sending the second verification information to be verified to the first service end so that the first service end verifies the second verification information to be verified;

and receiving login result information sent by the first service terminal.

In the binding processing apparatus provided in one or more embodiments of the present specification, when receiving an acquisition of security authentication information sent by a first service end of a payment application, a device fingerprint of a terminal device where the device fingerprint is located is generated, and the device fingerprint is sent to the first service end, so that the first service end performs security authentication processing; the obtaining request is sent when the operation processing of the target user on the first client side is determined to meet the preset safety certification condition after the first server side carries out account registration processing on the account registration request of the target user sent by the second server side based on the resource storage mechanism; and the account registration request is a binding request sent by a second server based on a second client of the target user using the resource storage mechanism, and is sent when the target user is determined not to register the payment account of the payment application. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

It should be noted that, the embodiment of the binding processing apparatus applied to the first client in this specification and the embodiment of the binding processing method applied to the first client in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to the implementation of the corresponding binding processing method applied to the first client, and repeated details are not repeated.

Further, on the basis of the same technical concept, corresponding to the binding processing method described above, one or more embodiments of the present specification further provide another binding processing apparatus, which is applied to a second client of the resource storage mechanism. Fig. 22 is a schematic block diagram of another binding processing apparatus according to one or more embodiments of the present disclosure, and as shown in fig. 22, the apparatus includes:

a sending module 801, configured to send a binding request to a second server of the resource storage mechanism in response to a binding operation of a target user; the binding request is used for requesting to bind a payment account of the payment application of the target user with a storage account of the target user in the resource storage mechanism so as to grant the payment account with payment authority for payment based on the storage account; the binding request comprises first account information of the storage account, so that the second server side carries out binding processing according to the first account information;

a receiving module 802, configured to receive the binding result information sent by the second server.

Optionally, the apparatus further comprises: a display module;

the receiving module 802, after the sending module 801 sends a binding request to a second server of a resource storage mechanism, further receives an authentication information obtaining request sent by the second server; the verification information acquisition request is sent based on an account registration request of the target user sent to a first server of the payment application;

the display module displays an input interface according to the verification information acquisition request; and the number of the first and second groups,

acquiring first verification information to be verified input by the target user in the input interface;

and sending the first verification information to be verified to the second server, so that the second server sends the first verification information to be verified to the first server, and the first server performs registration processing on a payment account when the first verification information to be verified passes verification.

Optionally, the apparatus further comprises: an acquisition module;

the obtaining module obtains the signing information that the target user signs the preset binding protocol before the receiving module 802 receives the binding result information sent by the second server, and sends the signing information to the second server, so that the second server performs related processing based on the signing information.

The binding processing apparatus provided in one or more embodiments of the present specification, in response to a binding operation of a target user, sends a binding request to a second server of a resource storage mechanism, so that the second server sends an account registration request to a first server of a payment application when determining that the target user does not register a payment account of the payment application, and performs binding processing based on account identification information of the payment account sent by the first server; and when the first server side determines that the preset safety authentication condition is met, carrying out safety authentication processing on the target user. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

It should be noted that, the embodiment of the binding processing apparatus applied to the second client in this specification and the embodiment of the binding processing method applied to the second client in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to the implementation of the corresponding binding processing method applied to the second client, and repeated details are not described again.

Further, corresponding to the binding processing method described above, based on the same technical concept, one or more embodiments of the present specification further provide a binding processing device, where the binding processing device is configured to execute the binding processing method described above, and fig. 23 is a schematic structural diagram of the binding processing device provided in one or more embodiments of the present specification.

As shown in fig. 23, the binding processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 901 and a memory 902, where one or more stored applications or data may be stored in the memory 902. Memory 902 may be, among other things, transient storage or persistent storage. The application program stored in memory 902 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in the binding processing device. Still further, the processor 901 may be configured to communicate with the memory 902 to execute a series of computer-executable instructions in the memory 902 on the bound processing device. The binding processing apparatus may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input-output interfaces 905, one or more keyboards 906, and the like.

In one particular embodiment, the binding processing apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the binding processing apparatus, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:

receiving an account registration request of a target user sent by a second server of the resource storage mechanism; the account registration request is sent by the second server when the second server receives a binding request sent by the target user by using a second client of the resource storage mechanism and determines that the target user does not register the payment account of the payment application; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application to be registered by the target user so as to grant the payment account with payment authority for payment based on the storage account; the account registration request comprises registration information of the target user;

registering a payment account according to the registration information to obtain account identification information of the target user;

sending the account identification information to the second server to enable the second server to perform binding processing according to the account identification information;

and if the operation processing of the target user on the first client of the payment application is determined to meet the preset safety authentication condition, carrying out safety authentication processing on the target user through the first client.

In the binding processing device provided in one or more embodiments of the present specification, when receiving an account registration request sent by a second server of a resource storage mechanism, registration processing of a payment account is performed, and obtained account identification information of a target user is sent to the second server, so that the second server performs binding processing according to the account identification information; the account registration request is sent when the second server receives a binding request sent by a second client of the resource storage mechanism used by the target user and determines that the target user does not register the payment account of the payment application; and the first server side performs security authentication processing on the target user through the first client side after determining that the operation processing of the target user on the first client side of the payment application meets a preset security authentication condition. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Optionally, before the receiving, when executed, an account registration request of the target user sent by the second server of the resource storage mechanism, the computer-executable instructions further include:

receiving a payment account inquiry request sent by the second server; wherein the payment account inquiry request is sent based on the binding request, the payment account inquiry request including the identity information of the target user associated with the storage account;

Optionally, the registration information comprises, when executed, computer executable instructions for: the contact information of the target user associated with the storage account;

the registering process of the payment account according to the registration information comprises the following steps:

sending first verification information to the contact way, so that the second client sends the acquired first verification information to be verified, which is input by the target user, to the second server, and the second server sends the first verification information to be verified to the first server;

Optionally, the computer executable instructions, when executed, further comprise: first account information of the storage account; the registration information includes: the contact information of the target user associated with the storage account;

the registering processing of the payment account according to the registration information to obtain the account identification information of the target user includes:

generating account identification information of the target user according to a preset generation rule of the account identification;

Optionally, when executed, the computer-executable instructions, after sending the account identification information to the second server, further include:

recording the sending time of the account identification information;

the determining that the operation processing of the target user on the first client of the payment application meets a preset security authentication condition includes:

if the target user is determined to successfully log in the first client and the authentication identifier in the first record information inquired according to the contact information in the login information is the first authentication identifier, determining whether the quantity of account identification information associated with the identity information in the inquired first record information does not exceed a preset quantity; and the number of the first and second groups,

determining whether the binding time length exceeds a preset time length;

Optionally, the computer-executable instructions, when executed, said determining that the target user successfully logs in to the client comprise:

receiving a login request sent by the first client;

Optionally, when executed, the performing, by the first client, a security authentication process on the target user includes:

sending an acquisition request of security authentication information to the first client so that the first client acquires the equipment information of the terminal equipment, generating an equipment fingerprint based on the equipment information, and sending the equipment fingerprint to the first service terminal;

Optionally, the payment account query request, when executed by the computer-executable instructions, further comprises: first account information of the storage account; the method further comprises the following steps:

if the associated account identification information is inquired according to the identity information, the inquired account identification information is sent to the second server, so that the second server can perform binding processing according to the account identification information; and the number of the first and second groups,

performing association recording on the first account information and the inquired account identification information to obtain second recording information; and the second record information represents that the binding between the payment account corresponding to the inquired account identification information and the storage account is successful.

Optionally, the computer executable instructions, when executed, further comprise: address information;

the sending the inquired account identification information to the second server includes:

determining whether the inquired number of the account identification information is one;

Optionally, the computer executable instructions, when executed, the second client comprises: a resource management application of the resource storage mechanism or a self-service operator of the resource storage mechanism.

In another particular embodiment, a binding processing apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the binding processing apparatus, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:

receiving a binding request sent by a second client of the resource storage mechanism; the binding request is sent based on the binding operation of a target user, and the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of a payment application of the target user so as to grant the payment account with payment authority for payment based on the storage account; the binding request includes first account information of the storage account;

if the target user is determined not to register the payment account of the payment application, sending an account registration request of the target user to a first service end of the payment application according to the first account information so that the first service end performs registration processing of the payment account to obtain account identification information of the target user, and performing security authentication processing on the target user through a first client end when the operation processing of the target user on the first client end of the payment application is determined to meet a preset security authentication condition;

and receiving the account identification information sent by the first service end, performing binding processing according to the account identification information and the first account information, and sending binding result information to the second client.

One or more embodiments of the present specification provide a binding processing device, upon receiving a binding request sent by a second client of a resource storage mechanism, where the binding request is sent based on a binding operation of a target user; if the target user does not register the payment account of the payment application, sending an account registration request of the target user to a first service end of the payment application according to first account information of a storage account included in the binding request, and carrying out binding processing according to account identification information sent by the first service end. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Optionally, the computer-executable instructions, when executed, said determining that the target user is not registered for the payment account of the payment application comprise:

acquiring the associated identity information of the target user from a specified database according to the first account information;

Optionally, when executed, the sending an account registration request of the target user to the first server of the payment application according to the first account information includes:

acquiring a related contact way of the target user from a specified database according to the first account information;

Optionally, when executed, after sending the account registration request of the target user to the first server of the payment application according to the first account information, the computer-executable instructions further include:

sending a verification information acquisition request to the second client so that the second client displays an input interface and acquires first verification information to be verified, which is input by the target user based on the input interface;

and if the signing information of the target user signing a preset binding protocol is determined to be acquired, sending an account registration request of the target user to a first server of the payment application according to the first account information.

Optionally, when executed, the computer-executable instructions perform binding processing according to the account identification information, including:

performing association recording on the account identification information and the first account information to obtain third recording information; and the third record information represents that the binding of the payment account corresponding to the account identification information and the storage account corresponding to the first account information is successful.

receiving an acquisition request of security authentication information sent by a first server of a payment application; the obtaining request is sent when the operation processing of the target user on the first client side is determined to meet a preset safety authentication condition after the first server side carries out account registration processing on an account registration request of the target user sent by a second server side based on a resource storage mechanism; the account registration request is sent by the second server side when the target user is determined not to register the payment account of the payment application based on a binding request sent by the target user using a second client of the resource storage mechanism; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application to be registered by the target user so as to grant the payment account with payment authority for payment based on the storage account;

acquiring equipment information of the terminal equipment, and generating an equipment fingerprint of the terminal equipment according to the equipment information;

and sending the device fingerprint to the first service end so that the first service end carries out security authentication processing according to the device fingerprint.

Optionally, before the receiving the request for obtaining the security authentication information sent by the first service end of the payment application, the computer-executable instructions further include:

responding to the login operation of the target user based on a login interface, and sending a login request to the first service terminal; the login request comprises a contact way of the target user associated with the storage account, so that the first server side sends second verification information to the contact way;

and receiving login result information sent by the first service terminal.

In the binding processing device provided in one or more embodiments of the present specification, when receiving the acquisition of the security authentication information sent by the first service end of the payment application, the binding processing device generates a device fingerprint of the terminal device in which the binding processing device is located, and sends the device fingerprint to the first service end, so that the first service end performs security authentication processing; the obtaining request is sent when the operation processing of the target user on the first client side is determined to meet the preset safety certification condition after the first server side carries out account registration processing on the account registration request of the target user sent by the second server side based on the resource storage mechanism; and the account registration request is a binding request sent by a second server based on a second client of the target user using the resource storage mechanism, and is sent when the target user is determined not to register the payment account of the payment application. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

responding to the binding operation of the target user, and sending a binding request to a second server side of the resource storage mechanism; the binding request is used for requesting to bind a payment account of the payment application of the target user with a storage account of the target user in the resource storage mechanism so as to grant the payment account with payment authority for payment based on the storage account; the binding request comprises first account information of the storage account, so that the second server side carries out binding processing according to the first account information;

and receiving the binding result information sent by the second server.

Optionally, the computer executable instructions, when executed, further comprise, after sending the binding request to the second server of the resource storage mechanism:

receiving a verification information acquisition request sent by the second server; the verification information acquisition request is sent based on an account registration request of the target user sent to a first server of the payment application;

displaying an input interface according to the verification information acquisition request;

Optionally, when executed, before receiving the binding result information sent by the second server, the computer-executable instructions further include:

and acquiring signing information of the target user signing a preset binding protocol, and sending the signing information to the second server so that the second server performs related processing based on the signing information.

The binding processing device provided in one or more embodiments of the present specification, in response to a binding operation of a target user, sends a binding request to a second server of a resource storage mechanism, so that the second server sends an account registration request to a first server of a payment application when determining that the target user does not register a payment account of the payment application, and performs binding processing based on account identification information of the payment account sent by the first server; and when the first server side determines that the preset safety authentication condition is met, carrying out safety authentication processing on the target user. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

It should be noted that the embodiment of the binding processing device in this specification and the embodiment of the binding processing method in this specification are based on the same inventive concept, and therefore specific implementation of this embodiment may refer to implementation of the corresponding binding processing method, and repeated details are not described again.

Further, based on the same technical concept, one or more embodiments of the present specification further provide a storage medium for storing computer-executable instructions, where in a specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, and the like, and when the storage medium stores the computer-executable instructions, the following processes can be implemented when the processor executes the computer-executable instructions:

When executed by a processor, a computer-executable instruction stored in a storage medium provided in one or more embodiments of the present specification performs registration processing of a payment account when receiving an account registration request sent by a second server of a resource storage mechanism, and sends obtained account identification information of a target user to the second server, so that the second server performs binding processing according to the account identification information; the account registration request is sent when the second server receives a binding request sent by a second client of the resource storage mechanism used by the target user and determines that the target user does not register the payment account of the payment application; and the first server side performs security authentication processing on the target user through the first client side after determining that the operation processing of the target user on the first client side of the payment application meets a preset security authentication condition. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Optionally, the computer-executable instructions stored in the storage medium, when executed by the processor, before receiving an account registration request of a target user sent by a second server of the resource storage mechanism, further include:

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, cause the registration information to include: the contact information of the target user associated with the storage account;

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, further comprise: first account information of the storage account; the registration information includes: the contact information of the target user associated with the storage account;

Optionally, the computer-executable instructions stored in the storage medium, when executed by the processor, further include, after the sending the account identification information to the second server:

recording the sending time of the account identification information;

determining whether the binding time length exceeds a preset time length;

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, determine that the target user successfully logs in to the client, comprising:

receiving a login request sent by the first client;

Optionally, the storage medium stores computer-executable instructions that, when executed by a processor, perform a security authentication process on the target user by the first client, including:

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, further comprise: first account information of the storage account; the method further comprises the following steps:

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, further comprise: address information;

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, the second client comprises: a resource management application of the resource storage mechanism or a self-service operator of the resource storage mechanism.

In another specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, or the like, and the storage medium stores computer-executable instructions that, when executed by the processor, implement the following process:

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, upon receiving a bind request sent by a second client of a resource storage mechanism, wherein the bind request is sent based on a bind operation of a target user; if the target user does not register the payment account of the payment application, sending an account registration request of the target user to a first service end of the payment application according to first account information of a storage account included in the binding request, and carrying out binding processing according to account identification information sent by the first service end. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, determine that the target user is not registered for the payment account of the payment application, comprising:

Optionally, when executed by a processor, the sending an account registration request of the target user to a first server of the payment application according to the first account information includes:

Optionally, the storage medium stores computer-executable instructions, which when executed by the processor, further include, after sending the account registration request of the target user to the first server of the payment application according to the first account information:

Optionally, when executed by a processor, the computer-executable instructions stored in the storage medium perform binding processing according to the account identification information, including:

Optionally, the storage medium stores computer-executable instructions, which when executed by the processor, further include, before receiving an acquisition request of security authentication information sent by the first service end of the payment application, the method further includes:

and receiving login result information sent by the first service terminal.

When executed by a processor, computer-executable instructions stored in a storage medium provided in one or more embodiments of the present specification generate a device fingerprint of a terminal device located in the storage medium when receiving an acquisition of security authentication information sent by a first service end of a payment application, and send the device fingerprint to the first service end, so that the first service end performs security authentication processing; the obtaining request is sent when the operation processing of the target user on the first client side is determined to meet the preset safety certification condition after the first server side carries out account registration processing on the account registration request of the target user sent by the second server side based on the resource storage mechanism; and the account registration request is a binding request sent by a second server based on a second client of the target user using the resource storage mechanism, and is sent when the target user is determined not to register the payment account of the payment application. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

and receiving the binding result information sent by the second server.

Optionally, the computer-executable instructions stored in the storage medium, when executed by the processor, further include, after sending the binding request to the second server of the resource storage mechanism:

Optionally, the storage medium stores computer-executable instructions, which when executed by a processor, further include, before receiving the binding result information sent by the second server:

When executed by a processor, computer-executable instructions stored in a storage medium provided in one or more embodiments of the present specification send a binding request to a second server of a resource storage mechanism in response to a binding operation of a target user, so that the second server sends an account registration request to a first server of a payment application when determining that the target user does not register a payment account of the payment application, and performs binding processing based on account identification information of the payment account sent by the first server; and when the first server side determines that the preset safety authentication condition is met, carrying out safety authentication processing on the target user. Therefore, when the target user operates the second client of the resource storage mechanism to bind the account, the registration of the payment account and the binding of the payment account and the storage account can be simultaneously realized on the basis of not increasing any user operation; and the register processing of the payment account and the safety certification processing of the target user are executed in an asynchronous mode, so that the safety certification requirement of the payment application is met, and the account binding requirement of the user in different scenes is met.

It should be noted that the embodiment of the storage medium in this specification and the embodiment of the binding processing method in this specification are based on the same inventive concept, and therefore specific implementation of this embodiment may refer to implementation of the corresponding binding processing method, and repeated details are not repeated.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following 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 desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., 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 which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.

One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims

1. A binding processing method is applied to a first service end of a payment application and comprises the following steps:

receiving an account registration request of a target user sent by a second server of the resource storage mechanism; wherein the account registration request is sent based on a binding request sent by the target user; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application to be registered by the target user; the account registration request comprises registration information of the target user;

sending account identification information obtained by performing registration processing on the payment account according to the registration information to the second server, so that the second server performs binding processing according to the account identification information;

and if the operation processing of the target user on the first client of the payment application is determined to meet the preset safety authentication condition and the binding time length of the payment account corresponding to the account identification information and the storage account does not exceed the preset time length, carrying out safety authentication processing on the target user through the first client.

2. The method of claim 1, before receiving the account registration request of the target user sent by the second server of the resource storage mechanism, further comprising:

3. The method of claim 1, the registration information comprising: the contact information of the target user associated with the storage account;

4. The method of claim 2, the account query request further comprising: first account information of the storage account; the registration information includes: the contact information of the target user associated with the storage account;

5. The method of claim 4, the determining that operational processing of the target user on the first client of the payment application satisfies a preset security authentication condition, comprising:

if the target user is determined to successfully log in the first client and the authentication identifier in the first record information inquired according to the contact information in the login information is the first authentication identifier, determining whether the quantity of account identification information associated with the identity information in the inquired first record information does not exceed a preset quantity;

if the number of the account identification information associated with the identity information does not exceed the preset number, determining that the operation processing of the target user on the first client of the payment application meets a preset safety authentication condition.

6. The method of claim 5, the determining that the target user successfully logs into the client, comprising:

receiving a login request sent by the first client;

7. The method of claim 1, the performing, by the first client, a secure authentication process on the target user, comprising:

8. The method according to claim 1, further comprising, after sending the account identification information obtained by performing registration processing of the payment account according to the registration information to the second server, the step of:

recording the sending time of the account identification information;

if it is determined that the operation processing of the target user on the first client of the payment application meets a preset security authentication condition and the binding duration between the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, performing security authentication processing on the target user through the first client, including:

if the operation processing of the target user on the first client of the payment application is determined to meet a preset safety authentication condition, acquiring the current time, and determining the binding duration of the payment account and the storage account corresponding to the account identification information according to the recorded sending time and the current time;

and determining whether the binding time length exceeds a preset time length, and if not, performing security authentication processing on the target user through the first client.

9. The method of claim 2, the payment account inquiry request further comprising: first account information of the storage account; the method further comprises the following steps:

10. The method of claim 9, the account query request further comprising: address information;

determining whether the inquired account identification information is unique in quantity;

11. The method of any of claims 1-10, the account registration request sent based on a binding request sent by the target user using a second client of the resource storage mechanism; the second client includes: a resource management application of the resource storage mechanism or a self-service operator of the resource storage mechanism.

12. A binding processing method is applied to a second server side of a resource storage mechanism and comprises the following steps:

receiving a binding request sent by a second client of the resource storage mechanism; the binding request is sent based on the binding operation of a target user, and the binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application of the target user; the binding request includes first account information of the storage account;

if the target user is determined not to register the payment account of the payment application, sending an account registration request of the target user to a first service terminal of the payment application according to the first account information, so that the first service terminal sends account identification information obtained by registration processing of the payment account to a second service terminal; when it is determined that the operation processing of the target user on the first client of the payment application meets a preset safety authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, performing safety authentication processing on the target user through the first client;

13. The method of claim 12, the determining that the target user is not registered for a payment account for the payment application, comprising:

14. The method of claim 12, the sending the account registration request of the target user to the first server of the payment application according to the first account information, comprising:

15. The method of claim 14, after sending the account registration request of the target user to the first server of the payment application according to the first account information, further comprising:

16. The method of claim 12, the sending the account registration request of the target user to the first server of the payment application according to the first account information, comprising:

17. The method of any of claims 12-16, the binding process according to the account identification information, comprising:

18. A binding processing method is applied to a first client of a payment application and comprises the following steps:

receiving an acquisition request of security authentication information sent by a first service terminal of the payment application; the obtaining request is sent after the first server sends account identification information obtained by account registration processing to a second server based on an account registration request of a target user sent by the second server of a resource storage mechanism, and it is determined that operation processing of the target user on the first client meets a preset safety authentication condition and binding duration of a payment account corresponding to the account identification information and the target user on a storage account of the resource storage mechanism does not exceed preset duration; the account registration request is sent based on a binding request sent by the target user; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application to be registered by the target user;

19. The method of claim 18, before receiving the request for obtaining the security authentication information sent by the first service end of the payment application, further comprising:

and receiving login result information sent by the first service terminal.

20. A binding processing method is applied to a second client of a resource storage mechanism and comprises the following steps:

responding to the binding operation of the target user, and sending a binding request to a second server side of the resource storage mechanism; the binding request is used for requesting to bind a payment account of the payment application of the target user with a storage account of the target user in the resource storage mechanism; the binding request comprises first account information of the storage account, so that the second server sends an account registration request to the first server of the payment application, and binding processing is carried out according to account identification information obtained by carrying out registration processing on the payment account and the first account information sent by the first server;

receiving binding result information sent by the second server;

after the first server sends the account identification information to the second server, when it is determined that the operation processing of the target user on the first client of the payment application meets a preset security authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, the first client performs security authentication processing on the target user.

21. The method of claim 20, after sending the binding request to the second server of the resource store, further comprising:

22. The method according to claim 20 or 21, before receiving the binding result information sent by the second server, further comprising:

23. A binding processing device is applied to a first service end of a payment application and comprises the following components:

the receiving module is used for receiving an account registration request of a target user, which is sent by a second server of the resource storage mechanism; wherein the account registration request is sent based on a binding request sent by the target user; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application to be registered by the target user; the account registration request comprises registration information of the target user;

the sending module is used for sending the account identification information obtained by registering the payment account according to the registration information to the second server so as to enable the second server to perform binding processing according to the account identification information;

and the authentication module is used for performing security authentication processing on the target user through the first client if the operation processing of the target user on the first client of the payment application is determined to meet a preset security authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account is determined not to exceed a preset duration.

24. The apparatus of claim 23, the apparatus further comprising: a recording module;

the recording module is used for recording the sending time of the account identification information;

the authentication module acquires current time if the operation processing of the target user on the first client of the payment application is determined to meet preset safety authentication conditions, and determines the binding duration of the payment account corresponding to the account identification information and the storage account according to the recorded sending time and the current time; and determining whether the binding time length exceeds a preset time length, and if not, performing security authentication processing on the target user through the first client.

25. A binding processing device applied to a second server of a resource storage mechanism comprises:

the receiving module is used for receiving a binding request sent by a second client of the resource storage mechanism; the binding request is sent based on the binding operation of a target user, and the binding request is used for requesting to bind the storage account of the target user in the resource storage mechanism with the payment account of the payment application of the target user; the binding request includes first account information of the storage account;

a determining module, configured to send an account registration request of the target user to a first server of the payment application according to the first account information if it is determined that the target user does not register the payment account of the payment application, so that the first server sends account identification information obtained by processing a registration of the payment account to the second server; when it is determined that the operation processing of the target user on the first client of the payment application meets a preset safety authentication condition and the binding duration of the payment account corresponding to the account identification information and the storage account does not exceed a preset duration, performing safety authentication processing on the target user through the first client;

the binding module is used for receiving the account identification information sent by the first service end and binding the account identification information and the first account information;

a sending module, configured to send binding result information to the second client.

26. A binding processing apparatus applied to a first client of a payment application, comprising:

the payment application comprises a receiving module, a processing module and a processing module, wherein the receiving module receives an acquisition request of security authentication information sent by a first service terminal of the payment application; the obtaining request is sent after the first server sends account identification information obtained by account registration processing to a second server based on an account registration request of a target user sent by the second server of a resource storage mechanism, and it is determined that operation processing of the target user on the first client meets a preset safety authentication condition and binding duration of a payment account corresponding to the account identification information and the target user on a storage account of the resource storage mechanism does not exceed preset duration; the account registration request is sent by the second server based on a binding request sent by the target user; the binding request is used for requesting to bind a storage account of the target user in the resource storage mechanism with a payment account of the payment application to be registered by the target user;

the acquisition module acquires the equipment information of the terminal equipment and generates the equipment fingerprint of the terminal equipment according to the equipment information;

and the sending module is used for sending the device fingerprint to the first service end so as to enable the first service end to perform security authentication processing according to the device fingerprint.

27. A binding processing device applied to a second client of a resource storage mechanism comprises:

the sending module is used for responding to the binding operation of the target user and sending a binding request to a second server side of the resource storage mechanism; the binding request is used for requesting to bind a payment account of the payment application of the target user with a storage account of the target user in the resource storage mechanism; the binding request comprises first account information of the storage account, so that the second server sends an account registration request to the first server of the payment application, and binding processing is carried out according to account identification information obtained by carrying out registration processing on the payment account and the first account information sent by the first server;

the receiving module is used for receiving the binding result information sent by the second server;

28. A binding processing device comprising:

a processor; and the number of the first and second groups,

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

29. A binding processing device comprising:

a processor; and the number of the first and second groups,

30. A binding processing device comprising:

a processor; and the number of the first and second groups,

31. A binding processing device comprising:

a processor; and the number of the first and second groups,

receiving binding result information sent by the second server;

32. A storage medium storing computer-executable instructions that when executed implement the following:

33. A storage medium storing computer-executable instructions that when executed implement the following:

34. A storage medium storing computer-executable instructions that when executed implement the following:

35. A storage medium storing computer-executable instructions that when executed implement the following:

receiving binding result information sent by the second server;