A method and device for account binding

Abstract

This specification discloses a method and device for account binding, which receives a resource account binding request input by a user, determines the first channel required for processing the resource account binding request and the state of the first channel, and if the first channel is not available, obtains the designated user information from the locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier, verifies the first resource account identifier according to the designated user information, and displays the resource account binding result information to the user according to the verification result, and when the first channel is available, performs binding processing on the first application account identifier and the first resource account identifier based on the first channel. Even if the user does not have an available first channel when requesting resource account binding, the resource account binding result can be displayed to the user, which not only improves the success rate of account binding when there is no available first channel, but also improves the user's account binding experience.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a method and device for account binding. Background Art

[0002] Currently, more and more users are binding their resource accounts on the resource platform with their application accounts on the application platform, so that when the user logs in to the application account on the application platform, the user can use the resources in the resource account to obtain services.

[0003] For example, when the resource platform is a bank and the application platform is a third-party payment platform, the user can bind the user's bank account (ie, resource account) to the user account of the third-party payment platform (ie, application account). After the user logs in to the user account, the funds in the bank account can be used to obtain services.

[0004] When binding a resource account with an application account, data needs to be transmitted between the resource platform and the application platform through a specified type of channel. If data cannot be transmitted through the specified type of channel, the resource account and the application account cannot be bound, which brings a poor account binding experience to users. Summary of the invention

[0005] The embodiments of this specification provide a method and device for account binding to partially solve the above-mentioned problems existing in the prior art.

[0006] The embodiments of this specification adopt the following technical solutions:

[0007] This specification provides a method for account binding, the method comprising:

[0008] Receive a resource account binding request input by a user, wherein the resource account binding request carries a first application account identifier and a first resource account identifier;

[0009] Determine a channel required for processing the resource account binding request as a first channel, and determine a state of the first channel;

[0010] If it is determined that the first channel is unavailable according to the state of the first channel, acquiring designated user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier;

[0011] Verifying the first resource account identifier according to the designated user information;

[0012] According to the verification result, information about the resource account binding result is displayed to the user;

[0013] When it is determined that the first channel is available according to the state of the first channel and / or when an application service is executed for the first resource account identifier according to the operation of the user, the first application account identifier and the first resource account identifier are bound based on the first channel through the resource platform corresponding to the first resource account.

[0014] Optionally, determining a channel required for processing the resource account binding request specifically includes:

[0015] Sending the resource account binding request to a service center so that the service center determines the first channel and a status of the first channel;

[0016] Receiving information of the first channel sent by the service center;

[0017] Determining the state of the first channel specifically includes:

[0018] Receive the status of the first channel sent by the service center.

[0019] Optionally, the designated user information includes a second application account identifier and a second resource account identifier;

[0020] Verifying the first resource account identifier according to the designated user information specifically includes:

[0021] Comparing the first application account identifier with the second application account identifier to obtain a first comparison result, and comparing the first resource account identifier with the second resource account identifier to obtain a second comparison result;

[0022] The first resource account identifier is verified according to at least one of the first comparison result and the second comparison result.

[0023] Optionally, verifying the first resource account identifier according to the designated user information specifically includes:

[0024] If it is determined according to the designated user information that the first resource account identifier has not passed the verification, determining the target service that can be executed by the resource platform for the first resource account identifier, and obtaining the authorization information of the user for the target service;

[0025] The target business and the authorization information are sent to the resource platform through a service center, a result of the resource platform executing the target business is determined, and the first resource account identifier is verified according to the result of the resource platform executing the target business.

[0026] Optionally, sending the target service and the authorization information to the resource platform through a service center specifically includes:

[0027] Sending the target service and the authorization information to the service center, so that the service center determines a channel required for processing the target service as a second channel and a state of the second channel;

[0028] If it is determined according to the state of the second channel that the second channel is available, sending the target service and the authorization information to the resource platform through the service center;

[0029] Determining the result of the resource platform executing the target business specifically includes:

[0030] Receive the result of the resource platform executing the target business sent by the service center.

[0031] Optionally, information about the resource account binding result is displayed to the user, specifically including:

[0032] Displaying the resource account binding result page;

[0033] If the resource account binding result page includes information indicating successful binding, the first resource account identifier is added to the resource account identifier corresponding to the first application account identifier, so that the user can select the first resource account identifier.

[0034] Optionally, binding the first application account identifier with the first resource account identifier through a resource platform corresponding to the first resource account based on the first channel specifically includes:

[0035] Sending the resource account binding request and the verification result to the resource platform based on the first channel, so that the resource platform processes the resource account binding request according to the verification result;

[0036] Based on the first channel, receiving a result of the resource platform processing the resource account binding request;

[0037] According to the result of the resource platform processing the resource account binding request, the first application account identifier and the first resource account identifier are bound.

[0038] Optionally, the resource account includes a bank account.

[0039] This specification provides a method for account binding, the method comprising:

[0040] The service center receives a resource account binding request sent by the application platform, wherein the resource account binding request carries a first application account identifier and a first resource account identifier;

[0041] According to the resource account binding request, determining a channel required for processing the resource account binding request as a first channel;

[0042] monitoring a state of the first channel, and sending the first channel and the state of the first channel to the application platform;

[0043] If it is monitored that the state of the first channel is unavailable, obtaining the designated user information from the locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier;

[0044] Verifying the first resource account identifier according to the designated user information;

[0045] Sending the verification result to the application platform so that the application platform displays information about the resource account binding result to the user;

[0046] When the status of the first channel is monitored to be available and / or when an application service executed for the first resource account identifier according to the user's operation is received from the application platform, the first application account identifier and the first resource account identifier are bound based on the first channel through the resource platform corresponding to the first resource account.

[0047] This specification provides an account binding device, the device comprising:

[0048] A first receiving module, configured to receive a resource account binding request input by a user, wherein the resource account binding request carries a first application account identifier and a first resource account identifier;

[0049] A first determining module is used to determine a channel required for processing the resource account binding request as a first channel, and determine a state of the first channel;

[0050] a first acquisition module, configured to acquire specified user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier, if it is determined that the first channel is unavailable according to the state of the first channel;

[0051] A first verification module, configured to verify the first resource account identifier according to the designated user information;

[0052] A display module, used to display information of resource account binding result to the user according to the verification result;

[0053] A binding module is used to bind the first application account identifier with the first resource account identifier based on the first channel through the resource platform corresponding to the first resource account when it is determined that the first channel is available according to the state of the first channel and / or when an application service is executed for the first resource account identifier according to the operation of the user.

[0054] This specification provides an account binding device, the device comprising:

[0055] A second receiving module, configured to receive, at a service center where the device is located, a resource account binding request sent by an application platform, wherein the resource account binding request carries a first application account identifier and a first resource account identifier;

[0056] A second determining module is used to determine, according to the resource account binding request, a channel required for processing the resource account binding request as a first channel;

[0057] a second monitoring module, configured to monitor the state of the first channel, and send the first channel and the state of the first channel to the application platform;

[0058] a second acquisition module, configured to acquire specified user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier if the state of the first channel is monitored to be unavailable;

[0059] A second verification module, configured to verify the first resource account identifier according to the designated user information;

[0060] A sending module, used to send the verification result to the application platform, so that the application platform displays the resource account binding result information to the user;

[0061] A processing module is used to bind the first application account identifier with the first resource account identifier based on the first channel through the resource platform corresponding to the first resource account when the status of the first channel is monitored to be available and / or when an application service executed for the first resource account identifier according to the operation of the user and sent by the application platform is received.

[0062] This specification provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned account binding method is implemented.

[0063] An electronic device provided in this specification includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned account binding method when executing the program.

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

[0065] In this specification, a resource account binding request input by a user can be received, the resource account binding request carries a first application account identifier and a first resource account identifier, and a channel required for processing the resource account binding request is determined as the first channel. The state of the first channel is determined. If the first channel is determined to be unavailable according to the state of the first channel, the specified user information is obtained from the locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier, and the first resource account identifier is verified according to the specified user information. According to the verification result, the information of the resource account binding result is displayed to the user. When the first channel is determined to be available according to the state of the first channel, the first application account identifier and the first resource account identifier are bound based on the first channel. In this specification, even if the user does not have an available first channel when requesting resource account binding, the resource account binding result can be displayed to the user according to the result of verifying the first resource account identifier. If the first channel is available, the resource account binding request input by the user is processed again, which not only improves the success rate of account binding when there is no available first channel, but also improves the user's account binding experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] The drawings described herein are used to provide a further understanding of this specification and constitute a part of this specification. The illustrative embodiments and descriptions of this specification are used to explain this specification and do not constitute an improper limitation on this specification. In the drawings:

[0067] Figure 1 A schematic diagram of the structure of the account binding system provided in the embodiments of this specification;

[0068] Figure 2 A flowchart of an account binding method provided in an embodiment of this specification;

[0069] Figure 3 An interactive flow chart of verifying a first resource account identifier through a resource platform provided in an embodiment of this specification;

[0070] Figure 4 A schematic diagram of an account binding interaction process provided in an embodiment of this specification;

[0071] Figure 5 A flowchart of another method for account binding provided in an embodiment of this specification;

[0072] Figure 6 A schematic diagram of the structure of an account binding device provided in an embodiment of this specification;

[0073] Figure 7 A schematic diagram of another account binding device provided in an embodiment of this specification

[0074] Figure 8 A schematic diagram of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0075] In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0076] When a user logs in to an application account on an application platform, he can use the resource acquisition service in the resource account. Therefore, the resource account of the resource platform can be bound to the application account of the application platform. When binding a resource account to an application account, data transmission between the resource platform and the application platform needs to pass through a specified type channel. Therefore, the existing account binding method is generally that after the application platform receives the user's resource account binding request, it determines the available specified type channel (that is, the first channel), and sends the resource account binding request and the resource account binding information input by the user to the resource platform through the first channel. After the resource platform processes the resource account binding request, it also sends the processing result to the application platform through the first channel. The application platform determines the resource account binding result based on the processing result. Among them, the first channel is the channel for data transmission between the resource platform and the application platform during the processing of the resource account binding request.

[0077] Once the first channel is unavailable, that is, during the resource account binding process, the application platform and the resource platform cannot exchange data, resulting in the failure of the resource account binding request processing, and the inability to bind the resource account to the application account, thus giving users a poor account binding experience.

[0078] In this specification, resource accounts may include resource accounts such as bank accounts, stock accounts, and fund accounts, so resource platforms may include resource platforms such as bank platforms, stock platforms, and fund platforms. Application accounts may include application accounts such as third-party payment accounts and shopping accounts, so application platforms may include application platforms such as third-party payment platforms and shopping platforms.

[0079] For ease of description, this specification takes the resource account as a bank account, the resource platform as a bank platform, the application account as a third-party payment account, and the application platform as a third-party payment platform as an example to illustrate the account binding method. Among them, the bank platform can be a bank server or a bank client, and the third-party payment platform can include a third-party payment platform client (that is, an application platform) and a third-party payment platform server (that is, a service center).

[0080] At present, after a user logs into a third-party payment account (i.e., an application account) on a third-party payment platform, the process of binding the application account with the bank account is as follows: Figure 1 As shown, Figure 1 A schematic diagram of the structure of the account binding system provided in the embodiment of this specification, Figure 1 In the figure, arrows indicate the direction of data transmission, solid arrows are the first channel, and dotted arrows are the common data transmission channel.

[0081] First, the user enters a card binding request on the application platform, which carries the bank card number entered by the user and the account ID of the user account registered by the user on the application platform. Secondly, the application platform sends the card binding request to the service center, which can determine the issuing bank of the bank card based on the bank card number, and determine the available card binding channel from the card binding channels of each card organization corresponding to the issuing bank, where the card organizations include platforms such as ChinaNet UnionPay, UnionPay, Visa International Service Association (VISA) and MasterCard International (MasterCard). After that, the service center sends the card binding request to the card organization through the available card binding channel, and the card organization forwards the card binding request to the corresponding issuing bank through the available card binding channel to process the card binding request. Finally, the issuing bank sends the processing result to the card organization, which sends it to the service center through the first channel, and the service center forwards it to the application platform. The application platform determines the result of the card binding based on the processing result.

[0082] In the above card binding process, the first channel is the data transmission channel in the card binding request processing process. It is actually a logical channel for data interaction between the service center, the card organization, and the issuing bank. In the hardware bottom layer, it may include multiple physical channels. When the first channel is available, the card binding request can be processed through the first channel. If the first channel is unavailable, the card binding request cannot be processed and the user fails to bind the card.

[0083] It should be noted here that, in general, the first channel is available, that is, data can be transmitted. However, if the resource platform fails, for example, when the bank platform is upgraded, or when the network fails, the first channel cannot transmit data, that is, the first channel is unavailable. Of course, there may be other factors that cause the first channel to be unavailable, and this specification does not limit the situation where the first channel is unavailable.

[0084] Therefore, in order to solve the problem of account binding failure caused by the unavailability of the first channel and improve the user's account binding experience, in this manual, when the first channel is unavailable, the specified user information can be obtained from the locally pre-stored user information, and the first resource account identifier can be verified according to the specified user information. Based on the verification result, the resource account binding result is displayed to the user. When the first channel is available, the resource account binding processing is performed based on the first channel.

[0085] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0086] Figure 2 A flowchart of an account binding method provided in an embodiment of this specification may include the following steps:

[0087] S100: receiving a resource account binding request input by a user, wherein the resource account binding request carries a first application account identifier and a first resource account identifier.

[0088] In this specification, when the application account is bound to the bank account, the third-party payment platform cannot directly interact with the bank platform. Instead, the third-party payment platform sends the resource account binding request to the service center that meets the specified requirements, and the service center forwards it to the card organization through the first channel, and then the card organization forwards it to the bank platform through the first channel. Therefore, when the application scenario of this specification is the bank card binding scenario, Figure 2 The execution subject of the account binding method shown is the application platform system, including the application platform and the service center. Of course, it can also be considered Figure 2 The execution subject of the account binding method shown is the application platform. In other application scenarios applicable to this specification, for example, the resource platform is a stock platform, etc., it can be determined according to the actual situation. Figure 2 The execution entity of the account binding method shown.

[0089] For ease of description, the following content is still explained using the resource platform as a bank platform as an example.

[0090] In this specification, the application platform can be installed on the user terminal, or the user can directly open the application platform on the user terminal. The application platform may include a food delivery platform, a car rental platform, etc. When the user needs to bind a resource account, first, the application platform can determine the application account logged in by the user. For example, the application platform can obtain the first application account identifier of the user's application account, wherein the first application account identifier is determined when the user registers an account on the application platform. According to the first application account identifier, the user's application account on the application platform and the information of the user using the application account can be determined.

[0091] Then, the application platform may also determine the type of the application account according to the first application account identifier. The type of the application account may include a real-name type and a non-real-name type. The information of the real-name type application account includes user identity information, while the information of the non-real-name type application account does not include user identity information. The user identity information may include a user identity identifier such as the user's ID number.

[0092] Afterwards, the application platform may display a resource account binding page to the user based on the type of user account. Specifically, the content displayed on the resource account binding page is different for different types of user accounts. When the user account type is a real-name type, the content displayed on the resource account binding page includes asking the user to enter the first resource account identification information. When the user account type is a non-real-name type, the content displayed on the resource account binding page includes asking the user to enter the first resource account identification information and the user identity identification information. In addition, in addition to the first resource account identification information, the resource account binding page may also include other information. For example, when the first resource account identification information is a credit card number, the other information may include the credit card expiration date, etc.

[0093] Finally, after displaying the resource account binding page to the user, the user's operation can be monitored, and the first resource account identifier, user identity identifier and other information can be determined according to the user's operation. When the user completes the information input according to the content displayed on the resource account binding page, it can be considered that the user enters the resource account binding request on the resource account binding page, and the application platform can receive the resource account binding request. Therefore, the resource account binding request carries the first application account identifier, the first resource account identifier and the user identity information.

[0094] S102: Determine a channel required for processing the resource account binding request as a first channel, and determine a state of the first channel.

[0095] After receiving the resource account binding request, the application platform may determine a channel required for processing the resource account binding request as a first channel, and determine a state of the first channel.

[0096] Specifically, the application platform may send a resource account binding request to the service center. After receiving the resource account binding request, the service center may determine the resource platform according to the first resource account identifier. The first resource account identifier may include a bank card number. According to the bank card number, the issuing bank (that is, the issuing bank platform) may be determined. The service center may determine the data transmission channel (that is, the first channel) from the service center through any card organization to the issuing bank. The first channel is used to transmit data in the process of processing the resource account binding request (that is, the first channel is a contract signing channel for processing the card binding request). For each card organization, the first channel from the service center through the card organization to the issuing bank is a logical channel, which may include multiple physical channels at the hardware level. Therefore, the service center can determine each first channel.

[0097] Furthermore, the service center may monitor the status of each first channel, wherein the status of the first channel may include an available status and an unavailable status. The service center may send each first channel and the status of each first channel to the application platform.

[0098] S104: If it is determined that the first channel is unavailable according to the state of the first channel, obtaining designated user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier.

[0099] After receiving each first channel and the status of each first channel sent by the service center, the application platform can determine whether the first channel is available according to the status of the first channel. If the status of the first channel is available, the first channel is determined to be available. If the status of the first channel is unavailable, the first channel is determined to be unavailable. In addition, in this specification, the service center can also determine whether each first channel is available after determining each first channel and the status of each first channel, and send the result of determining whether each first channel is available to the application platform.

[0100] If the application platform determines that all first channels are unavailable, or the result received by the application platform from the service center is that all first channels are unavailable, the specified user information is obtained from the user information pre-stored in the service center based on at least one of the first application account identifier and the first resource account identifier.

[0101] Specifically, the application platform may send a request to the service center to obtain the designated user information. After receiving the request to obtain the designated user information, the service center may obtain the designated user information from the pre-stored user information according to the first application account identifier and / or the first resource account identifier. For example, the service center may query and obtain each designated user information corresponding to the first application account identifier from the pre-stored user information according to the first application account identifier. Each designated user information may include information such as the second application account identifier (that is, the first application account identifier), the second resource account identifier, and the designated user identity identifier. The service center may also query and obtain each designated user information corresponding to the first resource account identifier from the pre-stored user information according to the first resource account identifier. Each designated user information may include information such as the second application account identifier, the second resource account identifier (that is, the first resource account identifier), and the designated user identity identifier. Of course, other information may also be included in the designated user information, such as contact information, user name, etc.

[0102] S106: Verify the first resource account identifier according to the designated user information.

[0103] After obtaining the designated user information, the service center may send the designated user information to the application platform, and the application platform may verify the first resource account identifier based on the designated user information. The service center may also verify the first resource account identifier based on the designated user information, and then send the verification result to the application platform.

[0104] The following description is made by taking the verification of the first resource account identifier by the service center as an example.

[0105] In this specification, the service center may compare the information in the resource account binding request input by the user with the designated user information, and determine the verification result according to the comparison result.

[0106] Specifically, first, the service center can compare the first application account identifier with the second application account identifier to obtain a first comparison result, and compare the first resource account identifier with the second resource account identifier to obtain a second comparison result. In addition, the service center can also compare the user identity information in the resource account binding request input by the user and the specified user identity information in the specified user information as other comparison results, etc.

[0107] Then, the service center verifies the first resource account identifier according to at least one of the first comparison result, the second comparison result, and the other comparison results.

[0108] If the first comparison result is consistent, and the second comparison result is consistent, the service center can determine that the first resource account identifier has passed the verification. That is, when the first comparison result is consistent and the second comparison result is consistent, the information of the application account contains the first resource account identifier. A common situation is that the user binds the first resource account identifier to the application account before the resource account is bound, and then unbinds the binding operation, so that the first resource account identifier is pre-stored in the service center. Therefore, the service center can determine that the first resource account identifier has passed the verification.

[0109] It should be noted that when verifying the first resource account identifier based on the first comparison result and / or the second comparison result, other comparison results may also be referred to. For example, when the user identity identifier in the resource binding request is inconsistent with the specified user identity identifier, the service center may determine that the first resource account identifier has failed the verification.

[0110] If the first comparison result is inconsistent, the service center can determine that the first resource account identifier has not passed the verification. That is, based on the first resource account identifier, the second application account identifier obtained by the service center from the pre-stored user information is inconsistent with the first application account identifier, indicating that in the information pre-stored by the service center, the first resource account identifier is bound to the second application account identifier, and the second application account identifier is inconsistent with the first application account identifier. One possible situation is that the user entered the resource account identifier of another user, so the service center can determine that the first resource account identifier has not passed the verification.

[0111] If the second comparison result is inconsistent, that is, according to the first application account identifier, the second resource account identifier obtained by the service center from the pre-stored user information is inconsistent with the first resource account identifier, which means that the service center has not pre-stored the first resource account identifier. One possible situation is that the user has not bound the first resource account identifier with the first application account identifier before. Alternatively, the service center has not found the specified user information in the pre-stored user information based on at least one of the first application account identifier and the first resource account identifier. Therefore, the service center can determine the resource platform corresponding to the first resource account identifier and verify the first resource account identifier through the resource platform.

[0112] Figure 3 An interactive flow chart of verifying a first resource account identifier through a resource platform is provided in an embodiment of this specification.

[0113] First, the service center may determine the target business that can be executed by the resource platform for the first resource account identifier, and obtain the user's authorization information for the target business.

[0114] Specifically, the service center can determine the target business from the pre-stored businesses. The target business is the business that the resource platform can execute for the first resource account identifier. For example, the service center can pre-store withholding business, transfer business, payment business, etc. Taking the target business as the withholding business as an example, the service center can obtain authorization information for the target business. After the service center determines the withholding business, it sends the withholding business to the application platform. The application platform can determine the business agreement of the withholding business from the pre-stored information and display the business agreement of the withholding business to the user. The user can browse the business agreement. The application platform can monitor the user's operations. When the user clicks the "Agree" button or enters the login password and other operations, it can be considered that the user agrees to execute the withholding business, that is, the user has authorized the withholding business. The application platform can obtain the authorization information and send the authorization information to the service center.

[0115] Then, the target business and the authorization information are sent to the resource platform, the result of the resource platform executing the target business is determined, and the first resource account identifier is verified according to the result of the resource platform executing the target business.

[0116] Specifically, the service platform can determine the channel required to process the target business as the second channel and the status of the second channel. Since the second channel is used to process the deduction business and the first channel is used to process the card binding request, the first channel and the second channel are different channels and there is no necessary connection between the two. With reference to the content of determining the first channel and the status of the first channel, the service center can determine each second channel and the status of each second channel. The service center can monitor the status of the second channel. If it is determined that the second channel is available based on the status of the second channel, the target business and authorization information are sent to the resource platform through the second channel, that is, the target business and authorization information are sent to the card organization through the second channel, and the card organization sends the target business and authorization information to the issuing bank. After receiving the target business and authorization information, the issuing bank processes the target business. When the channel attribute of the second channel is that the application platform completes the verification, the issuing bank does not need to repeat the verification. When the channel attribute of the second channel is that the issuing bank completes the verification, the issuing bank can send verification information to the user. After the application platform receives the verification information input by the user, it sends the verification information to the service center, and the service center sends the verification information to the card organization through the second channel, and the card organization forwards the verification information to the issuing bank through the second channel. The issuing bank can execute the withholding business and send the execution result of the withholding business to the card organization through the second channel, and the card organization sends the execution result to the service center through the second channel.

[0117] The service center may send the execution result to the application platform, and the application platform may verify the first resource account identifier according to the execution result, and the service center may also verify the first resource account identifier according to the execution result. Whether it is the application platform or the service center, when verifying the first resource account identifier according to the execution result, if the result of the resource platform executing the target business is successful, that is, the execution result of the issuing bank is a successful deduction, then it can be determined that the first resource account identifier has passed the verification; if the result of the resource platform executing the target business is a failure, that is, the execution result of the issuing bank is a failed deduction, then it can be determined that the first resource account identifier has not passed the verification.

[0118] The above is an explanation based on the example of the service center verifying the first resource account identifier. Of course, the application platform can also verify the first resource account identifier. The process of the application platform verifying the first resource account identifier can refer to the above content and will not be repeated in this manual.

[0119] S108: According to the verification result, information on the resource account binding result is displayed to the user.

[0120] After verifying the first resource account identifier, the application platform may display information about the resource account binding result to the user according to the verification result.

[0121] Specifically, if the service center verifies the first resource account identifier, the service center may send the verification result to the application platform, or the application platform may directly verify the first resource account identifier to obtain the verification result.

[0122] If it is determined that the first resource account identifier fails to pass the verification, it is determined that the resource account binding result fails, and the application platform can display a resource account binding result page to the user, and the page includes information that the resource binding result fails.

[0123] If it is determined that the first resource account identifier has passed the verification, the page where the application platform displays the resource account binding result to the user may include the information that the resource binding is successful. It should be noted that although the application platform displays the information that the resource binding is successful to the user, and the first resource account identifier is successfully bound to the first application account identifier, it does not mean that the user can directly use the resources in the first resource account identifier after logging into the application account. This is because the first channel is unavailable, and the resource platform has not performed a binding process on the first resource account identifier and the first application account identifier, that is, at this time, the binding of the first resource account identifier and the first application account identifier is only the mutual association of the identification information, but the resource acquisition service in the first resource account identifier cannot be used. However, there is an exception, that is, if the issuing bank supports binding the first resource account identifier and the first application account identifier when executing the debit card business and the execution result of the debit card business is a successful debit card, then at this time, the first resource account identifier and the first application account identifier are truly bound, that is, after the user logs into the application account, the resource acquisition service in the first resource account identifier can be used.

[0124] Therefore, if the resource account binding result page includes information about successful binding, the first resource account identifier is added to the resource account identifier corresponding to the first application account identifier, so that the user can select the first resource account identifier. That is, after the user logs in to the application account, when the application platform determines to execute the application service, the user can select the first resource account identifier in the resource account identifier list. Among them, the application service may include food delivery service, car rental service, etc.

[0125] S110: When it is determined that the first channel is available according to the state of the first channel and / or when an application service is executed for the first resource account identifier according to the operation of the user, the first application account identifier and the first resource account identifier are bound based on the first channel through the resource platform corresponding to the first resource account.

[0126] In this specification, the application platform or server can monitor the status of the first channel. When the first channel is determined to be available according to the status of the first channel, or when the application platform determines to execute the application service for the first resource account identifier according to the user's operation (for example, the user uses the resource in the first resource account identifier on the application platform to obtain the service corresponding to the application service), the application platform can request the service center to process the resource account binding request again. The first application account identifier and the first resource account identifier are bound based on the first channel through the resource platform corresponding to the first resource account.

[0127] Specifically, the service center can send the resource account binding request to the resource platform based on the first channel, so that the resource platform processes the resource account binding request; based on the first channel, receive the result of the resource platform processing the resource account binding request. Using the above example, the service center can send the resource account binding request to the card organization through the first channel, and the card organization sends the resource account binding request to the issuing bank through the first channel. The issuing bank processes the resource account binding request and sends the processing result to the card organization through the first channel, and the card organization sends the processing result to the service center through the first channel. Among them, the processing of the resource account binding request by the issuing bank can refer to the existing processing method.

[0128] That is, in this specification, when the user requests to bind the first application account identifier and the first resource account identifier for the first time, the first channel for processing the binding is unavailable, resulting in the application platform or service center being unable to process the user's resource account binding request through the resource platform. Therefore, the application platform or service center may perform information verification on the resource account binding request input by the user. If the verification is completed, the result of successful binding is displayed to the user. In fact, the real account binding is not completed at this time. When the user uses the resources in the first resource account on the application platform to obtain services and / or when the application platform or service center monitors that the first channel is available, the resource account binding request is processed through the first channel. At this time, the verification result and the resource account binding request may be sent to the resource platform through the first channel, and the resource platform verifies the information in the resource account binding request based on the received verification result. According to the verification result of the resource platform, the application platform or service center can process the first resource account identifier and the first application account identifier.

[0129] The service center may send the processing result to the application platform, and the application platform may perform binding processing on the first application account identifier and the first resource account identifier according to the result of the resource platform's processing of the resource account binding request received. If the processing result of the resource platform is successful, the first application account identifier and the first resource account identifier are bound. If the processing result of the resource platform is unsuccessful, the first application account identifier and the first resource account identifier are refused to be bound. It should be noted that at this time, after the application platform binds the first application account identifier and the first resource account identifier, the user can use the resources in the first resource account identifier to obtain services after logging into the application account, that is, this is a true account binding. If the application platform refuses to bind the first application account identifier and the first resource account identifier, the application platform may display information about the binding failure to the user.

[0130] For ease of understanding, Figure 4 This is a schematic diagram of an account binding interaction process provided in an embodiment of this specification. Figure 4 As shown:

[0131] The application platform receives a resource account binding request input by a user, and sends the resource account binding request to a service center. The service center determines each first channel and the status of each first channel, and sends each first channel and the status of each first channel to the application platform. If each first channel is determined to be unavailable based on the status of each first channel, the application platform sends a request to the service center to obtain designated user information. The service center obtains designated user information from pre-stored user information based on at least one of the first resource account identifier and the first application account identifier, and verifies the first resource account identifier based on the designated user information. The verification result includes verification passed, verification failed, or determining a target business and verifying the first resource account identifier based on the target business. The service center may send the verification result to the application platform, and the application platform displays information on the resource account binding result based on the verification result. When it is determined that the first channel is available and / or the application platform executes application services for the first resource account based on the user's operation, the application platform requests the service center to process the resource account binding request again. The service center sends the resource account binding request to the card organization through the first channel, and the card organization sends the resource account binding request to the issuing bank through the first channel. The issuing bank processes the resource account binding request and sends the processing result to the card organization through the first channel, and the card organization sends the processing result to the service center. The service center sends the processing result to the application platform, and the application platform performs binding processing on the first resource account identifier and the first application account identifier based on the processing result.

[0132] The above content is explained by taking the resource platform as a bank platform as an example. In this specification, the resource platform may also include other platforms such as a stock platform and a fund platform. The following takes other platforms as examples to briefly describe the account binding process.

[0133] The application platform receives a resource account binding request input by a user, and determines each first channel and the status of each first channel, wherein the first channel is a channel for the application platform to transmit data with other platforms in the process of processing the resource account binding request. If each first channel is determined to be unavailable based on the status of each first channel, the application platform can obtain the specified user information from the pre-stored user information based on at least one of the first resource account identifier and the first application account identifier, and verify the first resource account identifier based on the specified user information, and the verification result includes verification passed, verification failed, or determining the target business, and verifying the first resource account identifier based on the target business. The application platform displays the information of the resource account binding result based on the verification result. When it is determined that the first channel is available, the application platform sends the resource account binding request to other platforms through the first channel. The other platforms process the resource account binding request and send the processing result to the application platform through the first channel. The application platform performs binding processing on the first resource account identifier and the first application account identifier based on the processing result.

[0134] based on Figure 2 This manual also describes the account binding request from the perspective of the service center, such as Figure 5 As shown, Figure 5 Another method flow chart of account binding provided in the embodiment of this specification specifically includes the following steps:

[0135] S200: The service center receives a resource account binding request sent by the application platform, where the resource account binding request carries a first application account identifier and a first resource account identifier.

[0136] S202: According to the resource account binding request, determine a channel required for processing the resource account binding request as a first channel.

[0137] S204: Monitor the state of the first channel, and send the first channel and the state of the first channel to the application platform.

[0138] S206: If it is monitored that the status of the first channel is unavailable, obtain designated user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier.

[0139] S208: Verify the first resource account identifier according to the designated user information.

[0140] S210: Send the verification result to the application platform, so that the application platform displays the resource account binding result information to the user.

[0141] S212: When the status of the first channel is monitored to be available and / or when an application service executed for the first resource account identifier according to the user's operation is received from the application platform, the first application account identifier and the first resource account identifier are bound based on the first channel through the resource platform corresponding to the first resource account.

[0142] The contents of step S200 to step S212 can refer to the above related descriptions and will not be repeated here.

[0143] Based on the account binding method described above, the embodiment of this specification also provides a structural diagram of an account binding device, such as Figure 6 shown.

[0144] Figure 6 A schematic diagram of a structure of an account binding device provided in an embodiment of this specification, the device comprising:

[0145] A first receiving module 601 is configured to receive a resource account binding request input by a user, wherein the resource account binding request carries a first application account identifier and a first resource account identifier;

[0146] A first determination module 602 is used to determine a channel required for processing the resource account binding request as a first channel, and determine a state of the first channel;

[0147] A first acquisition module 603 is configured to acquire specified user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier if it is determined that the first channel is unavailable according to the state of the first channel;

[0148] A first verification module 604, configured to verify the first resource account identifier according to the designated user information;

[0149] A display module 605 is used to display information of resource account binding result to the user according to the verification result;

[0150] The binding module 606 is used to bind the first application account identifier with the first resource account identifier based on the first channel through the resource platform corresponding to the first resource account when it is determined that the first channel is available according to the state of the first channel and / or when an application service is executed for the first resource account identifier according to the operation of the user.

[0151] Optionally, the first receiving module 601 is specifically used to determine the application account logged in by the user and the type of the application account; display a resource account binding page to the user according to the type of the application account; and receive a resource account binding request entered by the user on the resource account binding page.

[0152] Optionally, the first determination module 602 is specifically configured to send the resource account binding request to a service center so that the service center determines the first channel and the state of the first channel; and receive information about the first channel sent by the service center;

[0153] The first determining module 602 is specifically configured to receive the state of the first channel sent by the service center.

[0154] Optionally, the first acquisition module 603 is specifically used to receive the designated user information sent by the service center, wherein the designated user information is acquired by the service center from user information pre-stored in the service center based on at least one of the first application account identifier and the first resource account identifier.

[0155] Optionally, the designated user information includes a second application account identifier and a second resource account identifier;

[0156] The first verification module 604 is specifically used to compare the first application account identifier with the second application account identifier to obtain a first comparison result, and to compare the first resource account identifier with the second resource account identifier to obtain a second comparison result; and to verify the first resource account identifier based on at least one of the first comparison result and the second comparison result.

[0157] Optionally, the first verification module 604 is specifically used to, if the first comparison result is consistent and the second comparison result is consistent, determine that the first resource account identifier has passed the verification; if the first comparison result is inconsistent, determine that the first resource account identifier has not passed the verification; if the second comparison result is inconsistent, determine the resource platform corresponding to the first resource account identifier, and verify the first resource account identifier through the resource platform.

[0158] Optionally, the first verification module 604 is specifically used to, if it is determined based on the specified user information that the first resource account identifier has not passed the verification, determine the target business that the resource platform can execute for the first resource account identifier, and obtain the user's authorization information for the target business; send the target business and the authorization information to the resource platform through the service center, determine the result of the resource platform executing the target business, and verify the first resource account identifier based on the result of the resource platform executing the target business.

[0159] Optionally, the first verification module 604 is specifically configured to send the target business and the authorization information to the service center, so that the service center determines a channel required for processing the target business as the second channel and a status of the second channel; if the second channel is determined to be available according to the status of the second channel, the target business and the authorization information are sent to the resource platform through the service center;

[0160] The first verification module 604 is specifically configured to receive a result of the resource platform executing the target business, which is sent by the service center.

[0161] Optionally, the first verification module 604 is specifically used to determine whether the first resource account identifier has passed the verification if the resource platform executes the target business successfully; if the resource platform executes the target business unsuccessfully, determine whether the first resource account identifier has failed the verification.

[0162] Optionally, the display module 605 is specifically used to display the resource account binding result page; wherein, if the resource account binding result page includes successful binding information, the first resource account identifier is added to the resource account identifier corresponding to the first application account identifier, so that the user selects the first resource account identifier.

[0163] Optionally, the binding module 606 is specifically configured to, when it is determined according to the state of the first channel that the first channel is available and it is determined to execute an application service, bind the first application account identifier with the first resource account identifier based on the first channel.

[0164] Optionally, the binding module 606 is specifically used to send the resource account binding request and the verification result to the resource platform based on the first channel, so that the resource platform processes the resource account binding request according to the verification result; based on the first channel, receive the result of the resource platform's processing of the resource account binding request; and bind the first application account identifier with the first resource account identifier according to the received result of the resource platform's processing of the resource account binding request.

[0165] Optionally, the resource account includes a bank account.

[0166] Based on the account binding method described above, the embodiment of this specification also provides a structural diagram of another account binding device, such as Figure 7 shown.

[0167] Figure 7 A schematic diagram of the structure of another account binding device provided in an embodiment of this specification, the device comprising:

[0168] A second receiving module 701 is configured to receive, at a service center where the device is located, a resource account binding request sent by an application platform, wherein the resource account binding request carries a first application account identifier and a first resource account identifier;

[0169] A second determining module 702 is used to determine, according to the resource account binding request, a channel required for processing the resource account binding request as a first channel;

[0170] A second monitoring module 703, configured to monitor the state of the first channel, and send the first channel and the state of the first channel to the application platform;

[0171] A second acquisition module 704 is configured to acquire specified user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier if the state of the first channel is monitored to be unavailable;

[0172] A second verification module 705 is used to verify the first resource account identifier according to the designated user information;

[0173] A sending module 706, configured to send the verification result to the application platform, so that the application platform displays information about the resource account binding result to the user;

[0174] Processing module 707 is used to bind the first application account identifier with the first resource account identifier based on the first channel through the resource platform corresponding to the first resource account when the status of the first channel is monitored to be available and / or when an application service executed for the first resource account identifier according to the operation of the user and sent by the application platform is received.

[0175] The embodiments of this specification also provide a computer-readable storage medium, which stores a computer program. The computer program can be used to execute the account binding method described above.

[0176] Based on the account binding method described above, this specification also proposes Figure 8 The schematic structure diagram of the electronic device shown in FIG. Figure 8 At the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include hardware required for other services. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to implement the account binding method described above.

[0177] Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the executor of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for account binding, characterized in that: The method comprises: Receive a resource account binding request input by a user, wherein the resource account binding request carries a first application account identifier and a first resource account identifier; Determine a channel required for processing the resource account binding request as a first channel, and determine a state of the first channel; If it is determined that the first channel is unavailable according to the state of the first channel, acquiring designated user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier; Verifying the first resource account identifier according to the designated user information; According to the verification result, information about the resource account binding result is displayed to the user; If it is determined that the first resource account identifier fails to pass the verification, it is determined that the resource account binding result fails, and a page of resource account binding results is displayed to the user, the page including information about the resource binding result failure; If it is determined that the first resource account identifier passes the verification, the page showing the resource account binding result to the user includes information that the resource binding is successful. At this time, the binding of the first resource account identifier and the first application account identifier is the mutual association of the identifier information, and the resource in the first resource account identifier cannot be used to obtain services; When it is determined that the first channel is available according to the state of the first channel and / or when an application service is executed for the first resource account identifier according to the operation of the user, the first application account identifier and the first resource account identifier are bound based on the first channel through the resource platform corresponding to the first resource account.

2. The method according to claim 1, characterized in that Determine the channel required to process the resource account binding request, specifically including: Sending the resource account binding request to a service center so that the service center determines the first channel and a status of the first channel; Receiving information of the first channel sent by the service center; Determining the state of the first channel specifically includes: Receive the status of the first channel sent by the service center.

3. The method according to claim 1, characterized in that The designated user information includes a second application account identifier and a second resource account identifier; Verifying the first resource account identifier according to the designated user information specifically includes: Comparing the first application account identifier with the second application account identifier to obtain a first comparison result, and comparing the first resource account identifier with the second resource account identifier to obtain a second comparison result; The first resource account identifier is verified according to at least one of the first comparison result and the second comparison result.

4. The method according to claim 1, characterized in that Verifying the first resource account identifier according to the designated user information specifically includes: If it is determined according to the designated user information that the first resource account identifier has not passed the verification, determining the target service that can be executed by the resource platform for the first resource account identifier, and obtaining the authorization information of the user for the target service; The target business and the authorization information are sent to the resource platform through a service center, a result of the resource platform executing the target business is determined, and the first resource account identifier is verified according to the result of the resource platform executing the target business.

5. The method according to claim 4, characterized in that Sending the target business and the authorization information to the resource platform through the service center specifically includes: Sending the target service and the authorization information to the service center, so that the service center determines a channel required for processing the target service as a second channel and a state of the second channel; If it is determined according to the state of the second channel that the second channel is available, sending the target service and the authorization information to the resource platform through the service center; Determining the result of the resource platform executing the target business specifically includes: Receive the result of the resource platform executing the target business sent by the service center.

6. The method according to claim 1, characterized in that Displaying the resource account binding result information to the user, specifically including: Displaying the resource account binding result page; If the resource account binding result page includes information indicating successful binding, the first resource account identifier is added to the resource account identifier corresponding to the first application account identifier, so that the user can select the first resource account identifier.

7. The method according to claim 1, characterized in that The step of binding the first application account identifier with the first resource account identifier through a resource platform corresponding to the first resource account based on the first channel specifically includes: Sending the resource account binding request and the verification result to the resource platform based on the first channel, so that the resource platform processes the resource account binding request according to the verification result; Based on the first channel, receiving a result of the resource platform processing the resource account binding request; According to the result of the resource platform processing the resource account binding request, the first application account identifier and the first resource account identifier are bound.

8. The method according to any one of claims 1 to 7, characterized in that: The resource account includes a bank account.

9. A method for account binding, characterized in that: The method comprises: The service center receives a resource account binding request sent by the application platform, wherein the resource account binding request carries a first application account identifier and a first resource account identifier; According to the resource account binding request, determining a channel required for processing the resource account binding request as a first channel; monitoring a state of the first channel, and sending the first channel and the state of the first channel to the application platform; If it is monitored that the state of the first channel is unavailable, obtaining the designated user information from the locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier; Verifying the first resource account identifier according to the designated user information; Sending the verification result to the application platform so that the application platform displays information about the resource account binding result to the user; If it is determined that the first resource account identifier fails to pass the verification, it is determined that the resource account binding result fails, and the application platform displays a resource account binding result page to the user, and the page includes information about the resource binding result failure; If it is determined that the first resource account identifier passes the verification, the application platform displays the resource account binding result page to the user, which includes information that the resource binding is successful. At this time, the binding of the first resource account identifier and the first application account identifier is the mutual association of the identifier information, and the resource in the first resource account identifier cannot be used to obtain services; When the status of the first channel is monitored to be available and / or when an application service executed for the first resource account identifier according to the user's operation is received from the application platform, the first application account identifier and the first resource account identifier are bound based on the first channel through the resource platform corresponding to the first resource account.

10. An account binding device, characterized in that: The device comprises: A first receiving module, configured to receive a resource account binding request input by a user, wherein the resource account binding request carries a first application account identifier and a first resource account identifier; A first determination module is used to determine a channel required for processing the resource account binding request as a first channel, and determine a state of the first channel; a first acquisition module, configured to acquire specified user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier, if it is determined that the first channel is unavailable according to the state of the first channel; A first verification module, configured to verify the first resource account identifier according to the designated user information; A display module, used for displaying information of resource account binding result to the user according to the verification result, including: if it is determined that the first resource account identifier fails to pass the verification, it is determined that the resource account binding result fails, and a page of resource account binding result is displayed to the user, and the page includes information of resource binding result failure; if it is determined that the first resource account identifier passes the verification, the page of resource account binding result displayed to the user may include information of resource binding success, at which time the binding of the first resource account identifier and the first application account identifier is the mutual association of identification information, and the resource in the first resource account identifier cannot be used to obtain services; A binding module is used to bind the first application account identifier with the first resource account identifier based on the first channel through the resource platform corresponding to the first resource account when it is determined that the first channel is available according to the state of the first channel and / or when an application service is executed for the first resource account identifier according to the operation of the user.

11. An account binding device, characterized in that: The device comprises: A second receiving module, configured to receive, at a service center where the device is located, a resource account binding request sent by an application platform, wherein the resource account binding request carries a first application account identifier and a first resource account identifier; A second determining module is used to determine, according to the resource account binding request, a channel required for processing the resource account binding request as a first channel; a second monitoring module, configured to monitor the state of the first channel, and send the first channel and the state of the first channel to the application platform; a second acquisition module, configured to acquire specified user information from locally pre-stored user information according to at least one of the first application account identifier and the first resource account identifier if the state of the first channel is monitored to be unavailable; A second verification module, configured to verify the first resource account identifier according to the designated user information; A sending module, used to send the verification result to the application platform, so that the application platform displays the information of the resource account binding result to the user. If it is determined that the first resource account identifier fails to pass the verification, it is determined that the resource account binding result fails, and the application platform displays a page of the resource account binding result to the user, and the page contains information about the resource binding result failure. If it is determined that the first resource account identifier passes the verification, the page of the resource account binding result displayed by the application platform to the user may contain information about the resource binding success. At this time, the binding of the first resource account identifier and the first application account identifier is the mutual association of the identification information, and the resource in the first resource account identifier cannot be used to obtain the service; A processing module is used to bind the first application account identifier with the first resource account identifier based on the first channel through the resource platform corresponding to the first resource account when the status of the first channel is monitored to be available and / or when an application service executed for the first resource account identifier according to the operation of the user and sent by the application platform is received.

12. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of claims 1 to 8 or 9 is implemented.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method described in any one of claims 1 to 8 or 9 is implemented.

Images