CN110689332A

CN110689332A - Resource account binding method, storage medium and electronic device

Info

Publication number: CN110689332A
Application number: CN201910858410.2A
Authority: CN
Inventors: 武树珍; 邹小舟
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-09-11
Filing date: 2019-09-11
Publication date: 2020-01-14
Anticipated expiration: 2039-09-11
Also published as: CN110689332B

Abstract

The present disclosure provides a resource account binding method, a storage medium, and an electronic device; relates to the technical field of information security. One resource account binding method can be applied to a resource platform; the method comprises the following steps: after receiving a binding request for binding a resource account and a target application platform, verifying whether the state of a current user on the resource platform meets a preset condition; and after the state of the current user on the resource platform is verified, providing the resource account information of the current user to the target application platform, wherein the resource account information is used for binding a resource account. The method and the device can simplify the operation steps when the resource account and the target application platform are bound and improve the binding success rate to a certain extent.

Description

Resource account binding method, storage medium and electronic device

Technical Field

The present disclosure relates to the field of information security technologies, and in particular, to a resource account binding method, a resource account binding apparatus, an electronic device, and a computer-readable storage medium.

Background

In many scenarios, the resource account needs to be bound to the target application platform, so that operations such as resource transfer can be conveniently realized through the resource account under the target application platform.

For example, more and more users bind a bank account (a resource account) and a third party payment platform (a target application platform), so that money transfer operations such as recharging, cash withdrawal or consumption can be performed directly in the third party payment platform through the bound bank account.

However, in the prior art, when a resource account and a target application platform are bound, there are problems of multiple binding operation steps, low binding success rate and the like.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

An object of the embodiments of the present disclosure is to provide a resource account binding method, a resource account binding apparatus, an electronic device, and a computer-readable storage medium, so as to simplify operation steps when a resource account and a target application platform are bound and improve a binding success rate to a certain extent.

According to one aspect of the present disclosure, a resource account binding method is provided, which is applied to a resource platform, and the method includes:

after receiving a binding request for binding a resource account and a target application platform, verifying whether the state of a current user on the resource platform meets a preset condition;

and after the state of the current user on the resource platform is verified, providing the resource account information of the current user to the target application platform, wherein the resource account information is used for binding a resource account.

According to one aspect of the present disclosure, there is provided a resource account binding method applied to a target application platform, the method including:

receiving resource account information sent by a resource platform; the resource account information is provided by the resource platform when the state of the current user on the resource platform meets a preset condition;

and binding the resource account based on the resource account information.

According to one aspect of the present disclosure, there is provided a resource account binding method, including:

after a resource platform receives a binding request for binding a resource account and a target application platform, resource account information of a current user is provided to the target application platform;

and jumping to the target application platform to perform resource account binding based on the resource account information.

According to one aspect of the present disclosure, there is provided a resource account binding apparatus applied to a resource platform, the apparatus including:

the login verification module is used for verifying whether the state of the current user on the resource platform meets a preset condition or not after receiving a binding request for binding the resource account with the target application platform;

and the information providing module is used for providing the resource account information of the current user to the target application platform after the state of the current user on the resource platform is verified, and the resource account information is used for binding a resource account.

In an exemplary embodiment of the present disclosure, the apparatus further includes:

and the skip control module is used for acquiring skip configuration information of the target application platform and skipping from the resource platform to the target application platform according to the skip configuration information.

In an exemplary embodiment of the present disclosure, the jump control module jumps to the target application platform according to the following steps: sending a jump request to the target application platform so that the target application platform carries out jump authority verification on the resource platform according to the jump request; and after the target application platform verifies the jumping authority of the resource platform, jumping to the target application platform according to the jumping configuration information.

the token information circulation module is used for receiving token information sent by the target application platform after the jump authority of the resource platform is verified; and carrying the token information when the resource account information of the current user is provided to the target application platform.

In an exemplary embodiment of the present disclosure, the information transmitting module includes:

a reference information obtaining unit, configured to obtain identity information retained by the current user on the resource platform, where the identity information is used as reference information;

the identity consistency verification unit is used for sending the reference information to the target application platform so that the target application platform can carry out identity consistency verification on the current user based on the reference information;

and the resource account information providing unit is used for responding to an information acquisition request sent by the target application platform after the identity consistency verification is passed, and providing the resource account information of the current user to the target application platform.

In an exemplary embodiment of the present disclosure, the reference information obtaining unit is specifically configured to encrypt, according to a specified encryption manner, the identity information retained by the current user on the resource platform, and use the encrypted identity information as the reference information.

In an exemplary embodiment of the present disclosure, the information providing module is configured to send the resource account information of the current user to a server associated with the target application platform, so that the target application platform obtains the resource account information from the server and performs resource account binding.

In an exemplary embodiment of the present disclosure, the target application platform is a blockchain node; and the information providing module encrypts the resource account information through a consensus algorithm and stores the resource account information into a blockchain network, so that the target application platform can acquire the resource account information from the blockchain network.

According to one aspect of the present disclosure, there is provided a resource account binding apparatus applied to a target application platform, the apparatus including:

the information receiving module is used for receiving the resource account information sent by the resource platform; the resource account information is provided by the resource platform when the state of the current user on the resource platform meets a preset condition;

and the account binding module is used for binding the resource account based on the resource account information.

a reference information unit, configured to receive the identity information of the current user provided by the resource platform, where the identity information is used as reference information;

the comparison information acquisition unit is used for acquiring the identity information retained by the current user on the target application platform as comparison information;

the identity consistency verification unit is used for verifying the identity consistency of the current user based on the reference information and the comparison information;

and the information acquisition request unit is used for sending an information acquisition request to the resource platform after the identity consistency verification of the current user passes, so that the resource platform responds to the information acquisition request to provide the resource account information of the current user to the target application platform.

In an exemplary embodiment of the disclosure, the comparison information obtaining unit is specifically configured to encrypt the identity information retained by the current user on the target application platform according to the specified encryption manner, and use the encrypted identity information as the comparison information.

the communication number verification module is used for acquiring the communication number of the current user from the resource account information; sending verification information to the terminal equipment of the current user through the communication number; and receiving the input information of the current user, and performing consistency comparison on the input information and the verification information.

the skip permission verification module is used for receiving a skip request sent by the resource platform; and performing jump authority verification on the resource platform according to the jump request so that the resource platform jumps to the target application platform according to the jump configuration information after the jump authority verification is passed.

the information source verification module is used for sending token information to the resource platform after the jump authority of the resource platform passes verification so that the resource platform carries the token information when providing the resource account information to the target application platform; and verifying the source of the resource account information according to the token information carried by the resource platform when providing the resource account information.

According to an aspect of the present disclosure, there is provided an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the method of any one of the above via execution of the executable instructions.

According to an aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of any one of the above.

Exemplary embodiments of the present disclosure may have some or all of the following benefits:

in the resource account binding method provided by some example embodiments of the present disclosure, on one hand, resource account information of a current user is provided to a target application platform through a resource platform, and the user does not need to perform complex operations such as resource account information input; therefore, the resource account binding method in the present exemplary embodiment can greatly reduce the binding operation steps of the user, and improve the binding operation efficiency of the user. On the other hand, the resource platform provides the resource account information of the current user to the target application platform instead of the user inputting the resource account information by himself, so that the problem that the user needs to perform binding operation again due to inputting wrong information can be avoided; meanwhile, the condition that account binding fails due to the fact that the resource account information input by the user is inconsistent with the actual resource account information can be avoided, and therefore the resource account binding success rate can be improved to a great extent.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

FIG. 1 is a diagram illustrating an exemplary system architecture to which a resource account binding method and apparatus according to an embodiment of the present disclosure may be applied;

2A-2G schematically illustrate an interactive interface in a resource account binding process in one embodiment of the disclosure;

3A-3G schematically illustrate an interactive interface in a resource account binding process in one embodiment of the disclosure;

FIG. 4 schematically illustrates a flow diagram of a resource account binding method according to one embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow diagram of a resource account binding method according to one embodiment of the present disclosure;

FIG. 6 schematically shows a flow diagram of an identity consistency verification process in one embodiment of the present disclosure;

FIG. 7 schematically illustrates a flow diagram of an identity consistency verification process in one embodiment of the present disclosure;

FIG. 8 schematically illustrates an interaction flow diagram of a resource account binding method according to one embodiment of the present disclosure;

FIG. 9 schematically illustrates a flow diagram of a resource account binding method according to one embodiment of the present disclosure;

10A-10F schematically illustrate an interactive interface in a resource account binding process in one embodiment of the disclosure;

FIG. 11 schematically illustrates a block diagram of a resource account binding apparatus according to one embodiment of the present disclosure;

FIG. 12 schematically illustrates a block diagram of a resource account binding apparatus according to one embodiment of the present disclosure;

FIG. 13 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

Fig. 1 is a schematic diagram illustrating a system architecture of an exemplary application environment to which a resource account binding method and a resource account binding apparatus according to an embodiment of the present disclosure may be applied.

As shown in fig. 1, the system architecture 100 may include one or more of

terminal devices

101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few. The

terminal devices

101, 102, 103 may be various electronic devices having a display screen, including but not limited to desktop computers, portable computers, smart phones, tablet computers, and the like. It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, server 105 may be a server cluster comprised of multiple servers, or the like.

The resource account binding method provided by the embodiment of the present disclosure may be executed by the server 105, and accordingly, the resource account binding apparatus may also be disposed in the server 105. The resource account binding method provided by the embodiment of the present disclosure may also be executed by the

terminal devices

101, 102, and 103, and correspondingly, the resource account binding apparatus may be disposed in the

terminal devices

101, 102, and 103. The resource account binding method provided in the present disclosure may also be executed by the

terminal devices

101, 102, and 103 and the server 105 together, and accordingly, the resource account binding apparatus may be disposed in the

terminal devices

101, 102, and 103 and the server 105, which is not particularly limited in this exemplary embodiment.

For example, in an exemplary embodiment, it may be that a user initiates a binding request with a target application platform at a resource platform on a

terminal device

101, 102, 103; after receiving a binding request for binding a resource account and a target application platform, a resource platform verifies whether the state of a current user on the resource platform meets a preset condition; after the state of the current user on the resource platform is verified, the resource account information of the current user is sent to a server 105 of a target application platform through a network 104; the target application platform client, also installed on the

terminal devices

101, 102, 103, obtains resource account information from the server 105 to complete the account binding.

The technical solution of the embodiment of the present disclosure is explained in detail below:

in this exemplary embodiment, an example will be described in which the resource platform is a bank platform and the target application platform is a third-party payment platform. However, it is easily understood by those skilled in the art that the resource platform may be other resource platforms such as stock platform, securities platform or fund platform; the target application platform can also be other application platforms such as a shopping platform, an information inquiry platform and the like. The bank platform may include a bank client installed in the

terminal devices

101, 102, and 103, and may further include a bank background server disposed in the server 105; the third-party payment platform can comprise a third-party payment platform client installed on the

terminal devices

101, 102 and 103, and can further comprise a third-party payment background server arranged on the server 105; in addition, the bank platform client and the third party payment platform client may be independent clients or functional modules integrated in other application programs, which are not limited in this exemplary embodiment.

Referring to fig. 2A to 2G, in a technical solution provided by the inventor, when a user first binds a bank account on a third-party payment platform, the method may be implemented by the following steps:

as shown in fig. 2A, the user logs in the third party payment platform and views the bound bank account through the entrance "bank card". As shown in fig. 2B, if the user binds the bank account on the third party payment platform for the first time, the user is prompted to input the payment password. As shown in fig. 2C, after the user inputs the payment password, the user is prompted to input the payment password again for confirmation. As shown in fig. 2D, after the user completes the setting of the payment password, the bank account identification information, such as a bank card number, input by the user is received. As shown in fig. 2E, the user is prompted to enter the bank account type and bank reservation information; the bank reservation information comprises a user name, identity document information, communication numbers such as mobile phone numbers and the like. As shown in fig. 2F, the third party payment platform sends the bank reservation information input by the user to the bank platform for verification, and after the bank platform verifies that there is no error, the third party payment platform sends a verification code to the terminal device of the user through the communication number reserved by the user; further, after the user enters the verification code he or she received, the third party payment platform may compare it with the issued verification code. After the verification of the verification code is passed, the bank account input by the user is bound to the third party payment platform, as shown in fig. 2G.

Referring to fig. 3A to 3G, in a technical solution provided by the inventor, when a user does not bind a bank account on a third-party payment platform for the first time, the method may be implemented by:

as shown in fig. 3A, the user logs in the third party payment platform and views the bound bank account through the entrance "bank card". As shown in fig. 3B, if the user does not perform bank account binding on the third party payment platform for the first time, the currently bound bank account is displayed; and the user can bind a new bank account through the entrance 'add bank card'. As shown in fig. 3C, after the user is prompted to enter a payment password, the user is authenticated. As shown in fig. 3D, after the identity authentication of the user is performed through the payment password, the user name retained on the third-party payment platform when the user previously binds to the bank account is displayed, and the bank account identification information, such as the bank card number, input by the user is received. As shown in fig. 3E, the user is prompted to enter the type of bank account and the communication number retained on the bank platform, such as a mobile phone number. As shown in fig. 3F, the third party payment platform sends the bank reserved communication number input by the user and the identity information retained when the user previously binds to the bank account to the bank platform for verification, and after the bank platform verifies that there is no error, the third party payment platform sends a verification code to the terminal device of the user through the communication number reserved by the user on the third party payment platform; further, after the user enters the verification code he or she received, the third party payment platform may compare it with the issued verification code. As shown in fig. 3F, after the verification of the verification code is passed, the bank account input by the user is bound to the third party payment platform.

In the above resource account binding scheme provided by the inventor, there may be the following to be improved.

For example:

first, the binding operation steps are numerous. For example, in the resource account binding process, three basic operation pages are involved, namely a bank account identification information (such as a bank card number) input page, a personal information (such as a user name, an identity document type, an identity document number and a communication number) input page and a verification code input page. The information acquisition of the three operation pages mostly depends on the active input of a user, namely, more steps are needed for the active operation of the user; meanwhile, if the information is input incorrectly, the information needs to be input again, which further increases the operation steps of the user.

Secondly, the binding success rate needs to be further improved. For example, in the binding process, a user is required to input information reserved in a bank platform to send the information to the bank platform for identity verification; however, in the actual operation process, the bank platform reservation information input by the user may not be consistent with the actual bank platform reservation information, which may reduce the binding success rate.

Again, safety is to be further improved. For example, when the identity information of the user is leaked, in the binding process, only whether the identity information input by the user matches with the information retained by the bank platform is checked, but whether the binding operation is initiated by the user himself cannot be verified, so that a risk may exist.

Based on one or more of the problems, the example embodiment provides a resource account binding method, which is applied to a resource platform; referring to fig. 4, the method may include:

step S410, after receiving a binding request for binding a resource account and a target application platform, verifying whether the state of a current user on the resource platform meets a preset condition.

Step S420, after the state of the current user on the resource platform is verified, resource account information of the current user is provided to the target application platform, and the resource account information is used for resource account binding.

In addition, the present exemplary embodiment provides a resource account binding method, which is applied to a target application platform; referring to fig. 5, the method may include:

in step S510, receiving resource account information sent by the resource platform; the resource account information is provided by the resource platform when the state of the current user on the resource platform meets a preset condition.

In step S520, resource account binding is performed based on the resource account information.

In the resource account binding method provided by the present exemplary embodiment, on one hand, the resource account information of the current user is provided to the target application platform through the resource platform, and the user does not need to perform complex operations such as resource account information input; therefore, the resource account binding method in the present exemplary embodiment can greatly reduce the binding operation steps of the user, and improve the binding operation efficiency of the user. On the other hand, the resource platform provides the resource account information of the current user to the target application platform instead of the user inputting the resource account information by himself, so that the problem that the user needs to perform binding operation again due to inputting wrong information can be avoided; meanwhile, the condition that account binding fails due to the fact that the resource account information input by the user is inconsistent with the actual resource account information can be avoided, and therefore the resource account binding success rate can be improved to a great extent.

In the following, in an embodiment, each step of the resource account binding method applied to the resource platform is described in more detail.

In step S410, after receiving a binding request for binding a resource account with a target application platform, a resource platform verifies whether a state of a current user on the resource platform satisfies a preset condition.

In this exemplary embodiment, the resource platform may be, for example, a bank platform; the user can log in the bank platform through various entries, for example, entries such as a bank platform client, a bank platform intelligent terminal, a bank platform applet (the applet may be a script program running depending on a main application program, for example, an applet running depending on a WeChat application program, etc.), or a two-dimensional code provided by the bank intelligent terminal.

After logging in to the bank platform, the current user may initiate a binding request to bind the resource account with the target application platform. For example, the bank platform may provide a list page of application platforms supporting the resource account binding method in this example embodiment, and the current user may select a target application platform that needs to be bound in the list page, for example, select a third party payment platform as the target application platform, and then request to bind the bank account with the selected third party payment platform. In addition, in some exemplary embodiments of the present disclosure, before the user requests to bind the bank account with the selected third party payment platform, the user may also be requested to confirm the protocol related to the binding; for example, a link address for binding a related protocol and a selection item for confirming acceptance of the protocol are provided for a user, and whether the user accepts the protocol is judged according to whether the user selects the selection item; if the user does not confirm the acceptance protocol, the user can be prompted to confirm through a popup window or other modes; moreover, as will be readily understood by those skilled in the art, the user may also be requested to confirm the binding-related protocol in other steps as needed, which is not particularly limited in the exemplary embodiment.

After receiving a binding request for binding a bank account with a third-party payment platform, the bank platform can verify whether the current user state meets a preset condition. For example, in the present exemplary embodiment, whether the login status information of the current user is legal may be verified; for example, a bank platform login password input by a current user is obtained and verified; for another example, a unique identifier of a terminal device used by a current user, for example, an IMEI code (International Mobile Equipment Identity) of the terminal device, is obtained, and the obtained unique identifier of the terminal device is compared with a unique identifier of a terminal device logged in history, and if the unique identifier is in the history, it can be considered that the current user and the account owner of the bank account are the same person; if the login state information of the current user is verified to be legal, the state of the current user can be considered to meet the preset condition.

It should be noted that, in the present exemplary embodiment, it may also be verified whether other state information of the current user meets a preset condition; for example, a bank platform digital certificate installed on the current terminal device may be verified to determine whether the bank platform digital certificate is valid; and if the current user state is valid, the current user state is considered to meet the preset condition. For another example, the user may be requested to input the specified personal information (e.g., input the identity document information, input the communication number, or input the verification code), and verify whether the personal information input by the user is correct, and if the personal information input by the user is correct, the current user status is considered to satisfy the preset condition. For another example, the biometric information of the current user may also be verified, such as face verification, fingerprint verification, etc., for the current user, and if the verification is passed, the state of the current user is considered to satisfy the preset condition, etc.; these are within the scope of the disclosure, and the disclosure is not limited thereto.

In step S420, after the status of the current user on the resource platform is verified, the resource account information of the current user is provided to the target application platform for account binding.

In this example embodiment, after the resource platform passes the status verification of the current user, the resource platform may provide the resource account information of the current user to the target application platform for account binding in multiple ways.

For example, one implementation manner may be that the resource platform performs unilateral binding (such as a subscription) on the resource account and the target application platform, and after the unilateral binding is completed, the resource platform sends the resource account information of the current user and the identification information of the current user on the target application platform to the target application platform, so that the target application platform records the resource account information of the current user and the corresponding identification information, and completes the final binding.

For example, firstly, a bank platform acquires identification information of a current user on a third-party payment platform, for example, receives a user name, an account number and the like of the current user on the third-party payment platform, which are input by the current user; secondly, after acquiring the user name of the current user on the third-party payment platform, the bank platform can perform unilateral binding on the bank account and the third-party payment platform; and thirdly, after the unilateral binding is finished, the bank platform sends the resource account information (such as bank account identification information, user name, identity document information, communication number and the like) of the current user and the identification information of the current user on the third-party payment platform to the third-party payment platform, so that the third-party payment platform establishes the association relationship between the bank account of the current user and the identification information of the user name or account number and the like sent by the bank platform, records the association relationship, and finishes the final binding.

For example, in order to improve the security of the binding process, another implementation manner may be to first jump from the resource platform to the target application platform, and then implement account binding by using the target application platform based on the resource account information of the current user received by the target application platform. This embodiment will be further described below.

First, in this exemplary embodiment, the resource platform may obtain jump configuration information of the target application platform, and jump from the resource platform to the target application platform according to the jump configuration information. Taking the target application platform and the resource platform as application programs installed in the same terminal device as an example, the jump configuration information may include, for example, target application platform URL (uniform resource locator) information, target application platform Scheme (protocol header) information, target application platform Path (Path) information, and the like, which are recorded in the resource platform in advance. After the jump configuration information of the target application platform is obtained, jumping to the target application platform can be carried out according to the jump configuration information.

In order to further enhance the security of the application program jump, in this exemplary embodiment, the target application platform may verify the jump authority of the resource platform. For example, in this exemplary embodiment, before the resource platform jumps to the target application platform, a jump request may be first sent to the target application platform, so that the target application platform performs jump authority verification on the resource platform according to the jump request. For example, the skip request may include skip information such as an IP address of the resource platform, path information of a resource platform client, a resource platform type identifier, and a skip scene identifier; after receiving the jump request, the target application platform can verify the jump authority of the resource platform according to the mapping relation between the preset jump information and the jump authority.

For example, in the present exemplary embodiment, different scene identifiers may be respectively set for skip scenes such as two-dimensional codes provided by a bank platform client, a bank platform intelligent terminal, a bank platform applet, or a bank intelligent terminal; meanwhile, a mapping relation between each scene identifier and the skipping authority is configured in advance on a third-party payment platform; the bank platform can carry the scene value of the corresponding jump scene in the jump request sent to the target application platform; and then, the third party payment platform can carry out skip permission verification on the bank platform according to the scene value. For another example, a mapping relationship between each bank platform identifier (such as a bank name, a bank type identifier or other identifiers) and the jump authority may be preconfigured on the third-party payment platform; the bank platform can carry a corresponding bank platform identifier in the jump request sent to the target application platform; and then, the third party payment platform can carry out skip permission verification on the bank platform according to the bank platform identification.

Further, after the jump authority of the target application platform to the resource platform is verified, a token message (token) may be sent to the resource platform; and the resource platform receives and stores the token information and carries the token information when providing the resource account information for the target application platform. Furthermore, when the target application platform receives the resource account information provided by the resource platform, the token information can be verified; for example, whether the received token information is consistent with the token information sent to the resource platform is confirmed, and if not, it indicates that the received resource account information may not originate from the resource platform, and there may be a risk; furthermore, the security of the binding process can be further improved by this step.

In this example embodiment, consistency verification may be performed on the identity information retained by the current user on the resource platform and the identity information retained on the target application platform, so that the risk of account binding is further reduced. For example, referring to FIG. 6:

in step S610, the identity information retained by the current user on the resource platform is obtained as reference information. In this example embodiment, the identity information may include, for example, a name of the current user, identity document information (such as an identity document type and an identity document number), and the like. In addition, in order to avoid plaintext leakage of the identity information of the user, in the present exemplary embodiment, the identity information retained by the current user on the resource platform may be encrypted according to a specified encryption manner, and the encrypted identity information is used as the reference information.

For example, the resource platform and the target application platform may jointly define the specified encryption mode; for example, the common agreement is encrypted in an asymmetric manner, for example, a pair of a public key and a private key is generated first, and the resource platform reserves the private key and provides the public key to the target application platform; furthermore, the resource platform may convert the identity information retained by the current user on the resource platform into first digest information by using a hash function, and encrypt the first digest information by using the private key, so as to obtain the reference information.

In step S620, the reference information is sent to the target application platform, so that the target application platform performs identity consistency verification on the current user based on the reference information.

For example, the target application platform may obtain identity information that is retained by the current user on the target application platform, as comparison information. Similarly, in order to avoid plaintext leakage of the identity information of the user, in the present embodiment, the identity information retained by the current user on the target application platform may be encrypted according to the above specified encryption method, and the encrypted identity information is used as the comparison information. For example, the target application platform may convert the identity information retained by the current user on the target application platform into the second digest information by using the hash function.

After receiving the reference information sent by the resource platform, the target application platform may decrypt the reference information by using the public key, so as to obtain the first digest information. Further, the second summary information and the first summary information may be compared; if the second abstract information is consistent with the first abstract information, the identity information retained by the current user on the resource platform is proved to be consistent with the identity information retained on the target application platform, so that the user initiating the binding request from the resource platform and the user operating the target application platform can be ensured to be the same user to a great extent. In addition, in order to further avoid the disclosure of the user identity information, in this exemplary embodiment, the target application platform may compare the second summary information with the first summary information in an independent program domain, which is not particularly limited in this exemplary embodiment.

In step S630, in response to the information obtaining request sent by the target application platform after the identity consistency verification passes, the resource account information of the current user is provided to the target application platform.

For example, after the identity consistency verification is passed, the target application platform may send an information acquisition request to the resource platform; after receiving the information acquisition request, the resource platform may provide the resource account information of the current user to the target application platform. In this example embodiment, the resource platform may send the resource account information of the current user to a server associated with the target application platform, so that the target application platform obtains the resource account information from the server and performs account binding. Alternatively, the resource account information of the current user may be provided to the client of the target application platform through inter-process communication, such as sharing a memory, and the like, which is not particularly limited in this exemplary embodiment.

In addition, in order to avoid transmitting plaintext information, in this exemplary embodiment, the resource account information of the current user may be encrypted according to an agreed encryption method and then provided to the target application platform; for example, the resource account information of the current user may be encrypted in a symmetric encryption manner, or the resource account information of the current user may be encrypted in an asymmetric encryption manner. Taking an asymmetric encryption mode as an example, a pair of a public key and a private key may be generated first, and the target application platform reserves the private key and provides the public key to the resource platform; furthermore, the resource platform can encrypt the resource account information of the current user by using a public key and then provide the encrypted resource account information to the target application platform; the target application platform can decrypt by using the private key after receiving the encrypted information provided by the resource platform.

In another embodiment, the steps of the resource account binding method applied to the target application platform are described in more detail below.

In this exemplary embodiment, the resource platform may be, for example, a bank platform, and the target application platform may be, for example, a third party payment platform. After the current user logs in the bank platform, a binding request for binding the bank account with the third-party payment platform can be initiated. After receiving a binding request for binding a bank account with a third-party payment platform, the bank platform can verify whether the current user state meets a preset condition. For example, in the present exemplary embodiment, whether the login status information of the current user is legal may be verified; for example, a bank platform login password input by a current user is obtained and verified; for another example, a unique identifier of a terminal device used by the current user, such as an IMEI code of the terminal device, is obtained, and the obtained unique identifier of the terminal device is compared with a unique identifier of a terminal device logged in history, and if the unique identifier is in the history, the current user and the account owner of the bank account can be considered to be the same person, and the like; in other example embodiments of the present disclosure, it may also be verified whether other state information such as real name information of the current user meets a preset condition, which is not particularly limited in this example embodiment.

In step S520, the target application platform performs account binding based on the resource account information.

For example, one implementation manner may be that the resource platform first performs unilateral binding (such as a subscription) on the resource account and the third-party payment platform, and after the unilateral binding is completed, the resource platform sends the resource account information of the current user and the identification information of the current user on the target application platform to the target application platform. And the target application platform records the received resource account information and the identification information of the current user to finish the final binding.

For example, firstly, a bank platform acquires identification information of a current user on a third-party payment platform, such as a user name and account information; if receiving the user name of the current user on the third-party payment platform input by the current user; secondly, after acquiring the user name of the current user on the third-party payment platform, the bank platform can perform unilateral binding on the bank account and the third-party payment platform; and thirdly, after the unilateral binding is finished, the bank platform sends resource account information such as the bank account, the user name and the identity document information of the current user and the user name of the current user on the third-party payment platform to the third-party payment platform. The third party payment platform can establish the incidence relation between the bank account of the current user and the identification information such as the user name or the account number sent by the bank platform based on the above, record the incidence relation and complete the final binding.

And the third-party payment platform records the received association relationship between the bank account of the current user and the user name, and completes the final binding.

For example, to improve the security of the binding process, another implementation may be to first jump from the resource platform to the target application platform; and then the target application platform realizes account binding based on the resource account information of the current user received by the target application platform. This embodiment will be further described below.

In this exemplary embodiment, the resource platform may first send a jump request to the target application platform; after receiving the jump request, the target application platform can perform jump authority verification on the resource platform according to the jump request. For example, the skip request may include skip information such as an IP address of the resource platform, path information of a resource platform client, a resource platform type identifier, and a skip scene identifier; after receiving the jump request, the target application platform can verify the jump authority of the resource platform according to the mapping relation between the preset jump information and the jump authority.

In this example embodiment, the target application platform may also perform consistency verification on the identity information retained by the current user on the resource platform and the identity information retained on the target application platform, so as to further reduce the risk of account binding. For example, referring to FIG. 7:

in step S710, receiving the identity information of the current user provided by the resource platform as reference information; in step S720, acquiring identity information retained by the current user on the target application platform as comparison information; in step S730, performing identity consistency verification on the current user based on the reference information and the comparison information; in step S740, after the identity consistency verification of the current user passes, an information obtaining request is sent to the resource platform, so that the resource platform responds to the information obtaining request to provide the resource account information of the current user to the target application platform. The details of steps S710 to S740 have been described in detail in steps S610 to S630, and thus are not repeated herein.

In addition, in some exemplary embodiments of the present disclosure, in order to reduce the risk of account binding, before account binding is performed based on the resource account information, a communication account of the user may also be verified. For example, a communication account retained by the current user on the resource platform may be first obtained from the received resource account information, and then the target application platform may send verification information to the terminal device of the current user through the communication account.

For example, the communication account may be a mobile phone number retained by the current user on the resource platform; the third party payment platform can send verification information, such as a verification code and the like, to the terminal equipment of the current user through the mobile phone number. After receiving the verification code, the user can input the verification code into a third party payment platform; the third party payment platform can compare the consistency of the verification code input by the user and the verification code sent by the third party payment platform, if the verification code is consistent, the verification of the communication account number of the user is passed, and then the subsequent binding step can be continued.

For another example, the third party payment platform may request the bank platform to send verification information, such as a verification code, to the terminal device of the current user through the mobile phone number. After receiving the verification code, the user can input the verification code into a third party payment platform; the third party payment platform sends the verification code input by the user to the bank platform; the bank platform carries out consistency comparison on the verification code input by the user and the verification code sent by the bank platform, and returns a comparison result; if the communication account number is consistent with the communication account number, the communication account number of the user passes the verification, and the subsequent binding step can be continued.

The resource account binding method in the present exemplary embodiment is further described below with reference to a specific binding scenario. In the binding scene, the resource platform is a bank platform, and the target application platform is a third-party payment platform; the third-party payment platform can comprise a third-party payment platform client and a third-party payment platform server; in addition, the third-party payment platform can also comprise a binding service page and a binding service background which are operated based on the third-party payment platform client; certainly, according to different system architectures, the third-party payment platform may not include the binding service page and the binding service background; the present exemplary embodiment is not limited thereto. As shown in fig. 8, wherein:

in step S801, the bank platform may provide a list page of an application platform supporting the resource account binding method in this example embodiment; if the current user selects a third party payment platform as the target application platform in the list page, the bank account can be requested to be bound with the selected third party payment platform. After receiving the binding request, the bank platform can verify whether the current user state meets the preset condition, and after the verification is passed, the bank platform can jump to a third-party payment platform, for example, a third-party payment platform client is opened.

In step S802, the third party payment platform client may send a binding service request and a service identifier to the binding service background; the service mark may be used as a unique identifier of the current binding process, and the service identifier may be, for example, a randomly generated character sequence.

In step S803, after receiving the binding service request, the binding service background may confirm the login state of the current user at the third party payment platform client, and if the current user is not in the login state, prompt the current user to log in the third party payment platform client. In addition, in this step, the user may also perform operations such as switching the currently logged-in account, which is not particularly limited in this exemplary embodiment.

In step S804, after confirming that the current user has logged in the third party payment platform client, the binding service background may query the third party payment platform server whether the third party payment platform already retains the identity information of the user. Generally, if the current user has previously bound a bank account in the third party payment platform, the third party payment platform server retains the identity information of the user.

In step S805, the third party payment platform server returns the query result to the binding service background. In step S806, the query result received by the binding service background is displayed on the binding service page, and the binding service page is controlled to perform page jump based on the query result; for example, if the query result received by the binding service background is that the third party payment platform server does not retain the identity information of the user, the process goes to the following step S807; on the contrary, if the query result received by the binding service background leaves the identity information of the user for the third party payment platform server, the process goes to the following step S811.

In step S807, if the third party payment platform server does not retain the identity information of the user, it indicates that the current user binds the bank account on the third party payment platform for the first time, and therefore, the user can jump to the bank account binding entry of the third party payment platform client to bind the account; for example, in step S808, the bank account of the current user may be bound to the third party payment platform through the steps shown in fig. 2A to fig. 2G. In step S809, after the account binding is completed, a binding completion notification is sent to the binding service page. In step S810, the current user account binding may be prompted to complete through the binding service page.

In step S811, if the third party payment platform server retains the identity information of the user, the third party payment platform client may be requested to verify the payment password of the current user. In step S812, the third party payment platform client may provide a payment password input interface to the current user after receiving the payment password verification request. In step S813, a payment password input by the user through the payment password input interface is received. In step S814, the received payment password is sent to the third party payment platform server for verification.

In step S815, if the third party payment platform server confirms that the payment password input by the current user is correct, a token message is returned to the third party payment platform client; the third-party payment platform client can carry the token information in the subsequent data interaction process with the third-party payment platform server to prove that the data really come from the third-party payment platform client, so that the data transmission safety in the binding process is improved.

In step S816, the third party payment platform client sends payment password verification passing information to the binding service page. In step S817, after the payment password is verified, the binding service page requests resource account information from the binding service background; in this example embodiment, the resource account information may include bank account identification information (e.g., bank card number), user name, identity document information (e.g., identity document type and identity document number), and a communication number, which is also called a bank card. Of course, in other exemplary embodiments of the present disclosure, the resource account information may also include more or less information, and may also include other information, which is not particularly limited in this exemplary embodiment.

In step S818, the binding service background starts an identity consistency verification process for the current user after receiving the request information of the binding service page. In step S819, the identity information retained by the current user on the third party payment platform server is requested from the third party payment platform server. In step S820, the received identity information returned by the third party payment platform server is used as comparison information; meanwhile, the identity information of the current user provided by the bank platform is used as reference information; and then, identity consistency verification is carried out on the current user based on the reference information and the comparison information.

In step S821, if the identity consistency verification performed on the current user passes, an information acquisition request may be sent to the bank platform. In step S822, the bank platform provides the resource account information of the current user to the binding service background in response to the information obtaining request. In step S823, after receiving the resource account information, the binding service background selects a part of the information to send to the binding service page for display, and meanwhile, before sending, desensitization processing may be performed on the information to be sent; for example, a part of characters in the bank card number and a part of characters in the user name are subjected to mask processing, and the like. In step S824, after receiving the desensitized resource account information, the binding service page displays the desensitized resource account information to the user for confirmation.

In step S825, the user confirms whether the resource account information is incorrect on the binding service page. In step S826, after the user confirms that the resource account information is correct, the binding service page sends an account binding request to the binding service background. In step S827, the binding service background starts a process of verifying the communication number of the current user after receiving the request message of the binding service page. In step S828, the binding service background requests the third party payment platform server to send verification information, such as a verification code, to the communication number retained by the current user. In step S829, the third party payment platform server sends a verification code to the terminal device of the user through the communication number reserved by the user; and after the transmission is finished, the binding service background is informed. In step S830, the binding service background controls the binding service page to provide an authentication code input interface.

In step S831, the binding service page presents the authentication code input interface to the user. In step S832, the binding service page receives the verification code input by the user through the verification code input interface and sends the verification code to the binding service background. In step S833, the binding service background sends the verification code input by the user to the third party payment platform server for verification. In step S834, if the verification code input by the user is verified by the third party payment platform server, the association relationship between the bank account and the third party payment platform may be established and recorded, that is, the account binding is completed. In step S835, the binding service background sends an account binding completion notification to the bank. In step S836, the binding service background sends an account binding completion notification to the binding service page. In step S837, the binding service page notifies the user that the account binding is complete.

In the resource account binding process of the above exemplary embodiments, security in the binding process is ensured from multiple aspects, and the binding risk is reduced. For example, on one hand, the state information such as the login state of the user is verified on the resource platform; for example, after a user initiates a binding request from a resource platform, the resource platform needs the user to log in the resource platform, and checks a login password, a login device, and the like, so as to ensure that the login user and the resource account owner are the same person. On the other hand, the target application platform verifies the jumping authority of the resource platform; meanwhile, the target application platform verifies the login state of the user. In another aspect, the summary information obtained by converting the user identity information retained by the resource platform is compared with the user identity information summary information retained by the target application platform, so that identity consistency verification of the user is realized; meanwhile, the process also reduces the risk of user information leakage to a certain extent. For example, the summary information of the user identity information is compared, but the plaintext of the user identity information is not compared, and the plaintext information of the user identity information retained by the other party cannot be obtained by the resource platform and the target application platform before the verification is passed. On the other hand, the authority of the user is further verified through a verification mode of the target application platform, such as a payment password verification mode. Therefore, by the resource account binding method according to some exemplary embodiments of the present disclosure, not only the security during the binding process can be ensured, but also the security during the binding process can be improved to a certain extent compared with the prior art.

In addition, in the prior art, the target application platform may need to configure different resource account binding methods for each resource platform, so that the development cost is high, and the account binding of each resource platform cannot be supported in batch. Based on the scheme in some exemplary embodiments of the present disclosure, only the jump permission needs to be configured for each resource platform, so that the development cost is greatly reduced, and account binding of multiple resource platforms can be simultaneously supported.

In the following, in yet another embodiment, a description is given of still another resource account binding method in the present exemplary embodiment. Referring to fig. 9, the resource account binding method may include steps S910 and S920 described below. The resource account binding method can be executed by a terminal such as a mobile phone, wherein:

in step S910, after the resource platform receives the binding request for binding the resource account and the target application platform, the resource account information of the current user is provided to the target application platform.

For example, the bank platform may provide a list page of the application platform that supports the resource account binding method in this example embodiment. Referring to fig. 10A, after the current user selects the third party payment platform as the target application platform in the list page, the bank platform may show the bank card number to be bound and the communication number of the user to the user; the user may then click on the "next" request to bind the bank account with the selected third party payment platform. In addition, the user can be requested to confirm the protocol related to the binding before clicking the next step, namely sending the binding request; for example, a link address for binding a related protocol and a selection item for confirming acceptance of the protocol are provided for a user, and whether the user accepts the protocol is judged according to whether the user selects the selection item; if the user does not confirm acceptance of the protocol, the user may be prompted for confirmation by a pop-up window or other means.

In step S920, jump from the resource front to the target application platform to perform account binding based on the resource account information.

For example, referring to fig. 10B, after receiving the binding request, the bank platform requests to jump to a third party payment platform (e.g., application a); and after the confirmation operation of the user is received, the third party payment platform client is opened. Referring to fig. 10C, after jumping to the third party payment platform, the third party payment platform may selectively display the received resource account information, so that the user may confirm that the resource account information is correct. Referring to fig. 10D, after the user confirms that the resource account information is correct, the third party payment platform may request the user to input a payment password for authentication. Referring to fig. 10E, if the payment password input by the user is correct, the communication number of the user may be verified; for example, the user is requested to enter the authentication code he or she received. Referring to fig. 10F, if the third party payment platform confirms that the verification code input by the user is correct, the account binding may be completed.

In addition, in the above steps, the order of the steps shown in fig. 10C, 10D, and 10E may be adjusted according to the requirement. For example, the user may first be requested to enter a payment password; after confirming that the payment password input by the user is correct, requesting the user to confirm the resource account information; and after the user confirms that the resource account information is correct, verifying the communication number of the user. For another example, the user may be first requested to enter a payment password; after confirming that the payment password input by the user is correct, verifying the communication number of the user; and if the communication number of the user passes the verification, requesting the user to confirm the resource account information. For example, the user may be first requested to confirm the resource account information; after the user confirms that the resource account information is correct, verifying the communication number of the user; if the user's communication number is authenticated, the user is requested to enter a payment password, etc. These are also within the scope of the present disclosure and the exemplary embodiments are not limited thereto.

In the resource account binding process in the present exemplary embodiment, on one hand, the operations that the user needs to perform only include a confirmation operation and a verification operation of inputting a verification code and a payment password, and complex operations such as resource account information input are not required; therefore, the resource account binding method in the present exemplary embodiment can greatly reduce the binding operation steps of the user, and improve the binding operation efficiency of the user. On the other hand, the resource platform provides the resource account information of the current user to the target application platform instead of the user inputting the resource account information by himself, so that the problem that the user needs to perform binding operation again due to inputting wrong information can be avoided; meanwhile, the condition that the binding is failed due to the fact that the resource account information input by the user is inconsistent with the actual resource account information can be avoided, and therefore the binding success rate of the resource account can be improved to a great extent; for example, based on the statistics of the inventor, when a user binds a bank account on a certain third-party payment platform, an event that binding fails due to the fact that the user forgets part of information of the bank account (such as a bank card number, a bank account type, a belonging bank, an identity document number, a communication number and the like) accounts for 67% of all binding failure events; by the resource account binding method in the exemplary embodiment, the problem that the bank account binding fails due to the fact that the user forgets part of the bank account information can be solved.

In an exemplary embodiment of the present disclosure, the target application platform is a blockchain node; the target application platform is a block chain node; providing the resource account information of the current user to the target application platform comprises: and encrypting the resource account information through a consensus algorithm and storing the encrypted resource account information to a blockchain network so that the target application platform can acquire the resource account information from the blockchain network. The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer. The resource account binding method in this exemplary embodiment may be applied to the above block chain. For example, the target application platform may be a blockchain node of a platform product service layer. The bank platform can encrypt the resource account information through a consensus algorithm and store the encrypted resource account information to the blockchain network, so that the target application platform can acquire the resource account information from the blockchain network to bind the resource account. In detail:

the block chain underlying platform can comprise processing modules such as user management, basic service, intelligent contract and operation monitoring. The user management module is responsible for identity information management of all blockchain participants, and comprises public and private key generation maintenance (account management), key management, user real identity and blockchain address corresponding relation maintenance (authority management) and the like, and under the authorization condition, the user management module supervises and audits the transaction condition of certain real identities and provides rule configuration (wind control audit) of risk control; the basic service module is deployed on all block chain node equipment and used for verifying the validity of the service request, recording the service request to storage after the effective request is identified in a consensus mode, for a new service request, the basic service firstly conducts interface adaptation analysis and authentication processing (interface adaptation), then encrypts resource account information through a consensus algorithm (consensus management), transmits the encrypted resource account information to a shared account book (network communication) in a complete and consistent mode, and records and stores the encrypted resource account information; the intelligent contract module is responsible for registering and issuing contracts, triggering the contracts and executing the contracts, developers can define contract logics through a certain programming language, issue the contract logics to a block chain (contract registration), call keys or other event triggering and executing according to the logics of contract clauses, complete the contract logics and simultaneously provide the function of upgrading and canceling the contracts; the operation monitoring module is mainly responsible for deployment, configuration modification, contract setting, cloud adaptation in the product release process and visual output of real-time states in product operation, such as: alarm, monitoring network conditions, monitoring node equipment health status, and the like.

The platform product service layer provides basic capability and an implementation framework of typical application, and developers can complete block chain implementation of business logic based on the basic capability and the characteristics of the superposed business. The application service layer provides the application service based on the block chain scheme for the business participants to use.

It should be noted that although the various steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that these steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.

Further, in this example embodiment, a resource account binding apparatus is also provided. The resource account binding device can be applied to terminal equipment and can also be applied to the terminal equipment and a server simultaneously. Referring to fig. 11, the resource account binding apparatus 1100 may include a login authentication module 1110 and an information providing module 1120. Wherein:

the login verification module 1110 is configured to verify whether a current state of a user on a resource platform meets a preset condition after receiving a binding request for binding a resource account with a target application platform;

and an information providing module 1120, configured to provide the resource account information of the current user to the target application platform for account binding after the status of the current user on the resource platform is verified.

In an exemplary embodiment of the disclosure, the information providing module 1120 is configured to send the resource account information of the current user to a server associated with the target application platform, so that the target application platform obtains the resource account information from the server and performs account binding.

Further, in this example embodiment, a resource account binding apparatus is also provided. The resource account binding apparatus may be a target application platform. Referring to fig. 12, the resource account binding apparatus 1200 may include an information receiving module 1210 and an account binding module 1220. Wherein:

an information receiving module 1210, configured to receive resource account information sent by a resource platform; the resource account information is provided by the resource platform when the state of the current user on the resource platform meets a preset condition;

an account binding module 1220, configured to perform account binding based on the resource account information.

The specific details of each module or unit in the resource account binding apparatus have been described in detail in the corresponding resource account binding method, and therefore are not described herein again.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

FIG. 13 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present disclosure. It should be noted that the computer system 1300 of the electronic device shown in fig. 13 is only an example, and should not bring any limitation to the functions and the scope of the application of the embodiments of the present disclosure.

As shown in fig. 13, the computer system 1300 includes a Central Processing Unit (CPU)1301 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1302 or a program loaded from a storage section 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for system operation are also stored. The CPU 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.

The following components are connected to the I/O interface 1305: an input portion 1306 including a keyboard, a mouse, and the like; an output section 1307 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1308 including a hard disk and the like; and a communication section 1309 including a network interface card such as a LAN card, a modem, or the like. The communication section 1309 performs communication processing via a network such as the internet. A drive 1310 is also connected to the I/O interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1310 as necessary, so that a computer program read out therefrom is mounted into the storage portion 1308 as necessary.

In particular, the processes described below with reference to the flowcharts may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via communications component 1309 and/or installed from removable media 1311. The computer program executes various functions defined in the method and apparatus of the present application when executed by a Central Processing Unit (CPU) 1301. In some embodiments, computer system 1300 may also include an AI (artificial intelligence) processor for processing computing operations related to machine learning.

It should be noted that the computer readable media shown in the present disclosure may be computer readable signal media or computer readable storage media or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method as described in the embodiments above.

As another aspect, the present application also provides an electronic device, including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the resource account binding method provided herein via execution of the executable instructions.

It is to be understood that other embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with the scope of the disclosure being limited only by the following claims.

Claims

1. A resource account binding method is applied to a resource platform; characterized in that the method comprises:

2. The resource account binding method of claim 1, further comprising:

and acquiring skip configuration information of the target application platform, and skipping from the resource platform to the target application platform according to the skip configuration information.

3. The method for binding the resource account according to claim 2, wherein the jumping from the resource platform to the target application platform according to the jumping configuration information comprises:

sending a jump request to the target application platform so that the target application platform carries out jump authority verification on the resource platform according to the jump request;

and after the target application platform verifies the jumping authority of the resource platform, jumping to the target application platform according to the jumping configuration information.

4. The resource account binding method of claim 3, further comprising:

receiving token information sent by the target application platform after the jump authority of the resource platform is verified; and

and carrying the token information when the resource account information of the current user is provided to the target application platform.

5. The resource account binding method according to any one of claims 1 to 4, wherein providing the resource account information of the current user to the target application platform comprises:

acquiring identity information retained by the current user on the resource platform as reference information;

sending the reference information to the target application platform so that the target application platform can carry out identity consistency verification on the current user based on the reference information;

and responding to an information acquisition request sent by the target application platform after the identity consistency verification is passed, and providing the resource account information of the current user to the target application platform.

6. The resource account binding method according to any one of claims 1 to 4, wherein the target application platform is a block chain node; providing the resource account information of the current user to the target application platform comprises:

and encrypting the resource account information through a consensus algorithm and storing the encrypted resource account information to a blockchain network so that the target application platform can acquire the resource account information from the blockchain network.

7. A resource account binding method is applied to a target application platform, and is characterized by comprising the following steps:

and binding the resource account based on the resource account information.

8. The resource account binding method of claim 7, further comprising:

receiving the identity information of the current user provided by the resource platform as reference information;

acquiring identity information retained by the current user on the target application platform as comparison information;

performing identity consistency verification on the current user based on the reference information and the comparison information;

and after the identity consistency of the current user is verified, sending an information acquisition request to the resource platform, so that the resource platform responds to the information acquisition request to provide the resource account information of the current user to the target application platform.

9. The resource account binding method according to claim 8, wherein the reference information is encrypted in a specified encryption manner; the acquiring identity information retained by the current user on the target application platform as comparison information includes:

and encrypting the identity information retained by the current user on the target application platform according to the specified encryption mode, and taking the encrypted identity information as the comparison information.

10. The method of claim 7, wherein prior to resource account binding based on the resource account information, the method further comprises:

acquiring the communication number of the current user from the resource account information;

sending verification information to the terminal equipment of the current user through the communication number;

and receiving the input information of the current user, and performing consistency comparison on the input information and the verification information.

11. The resource account binding method according to any one of claims 7 to 10, wherein the method further comprises:

receiving a skip request sent by the resource platform;

and performing jump authority verification on the resource platform according to the jump request so that the resource platform jumps to the target application platform according to the jump configuration information after the jump authority verification is passed.

12. The resource account binding method of claim 11, further comprising:

after the jump authority of the resource platform passes verification, sending token information to the resource platform so that the resource platform carries the token information when providing the resource account information to the target application platform; and

and verifying the source of the resource account information according to the token information carried by the resource platform when providing the resource account information.

13. A method for binding resource accounts, the method comprising:

14. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of any one of claims 1-13.

15. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the method of any of claims 1-13 via execution of the executable instructions.