WO2023040531A1 - Account authorization method and apparatus, device, storage medium, and computer program product - Google Patents

Abstract

An account authorization method and apparatus, a device, a storage medium, and a computer program product. The method comprises: obtaining account authorization information (S201); sending the account authorization information to a receiver (S202); determining that the receiver has signed an authorization agreement corresponding to the account authorization information (S207); obtaining and displaying the authorization agreement (S208); obtaining a signing operation of an initiator on the authorization agreement (S209); and sending the authorization agreement signed by the initiator to a third party (S210). According to the method, steps in a transaction process are reduced, the authorization and verification efficiency in an entrusted transaction is improved, the security of the transaction is ensured, and the convenience of user transactions is improved on the basis of improving transaction efficiency.

Description

Account authorization method, device, equipment, storage medium and computer program product

priority information

This application claims the priority of the Chinese patent application number "202111086425.5" filed on September 16, 2021 with the title of "Account Authorization Method, Device, Equipment, Storage Medium, and Computer Program Product", and the entire content of the application Incorporated in this application by reference.

technical field

The embodiments of the present application relate to the technical field of the Internet, and in particular to an account authorization method, device, equipment, storage medium, and computer program product.

Background technique

At present, customers with large assets in the market, trusts, family offices, asset management companies and other customers all have demands for asset management through account authorization when using brokerage trading software, that is, to authorize their own accounts to one or more other accounts for asset management. Moreover, this asset management method through account authorization can also be applied to scenarios such as joint accounts and financial management for relatives and friends, thereby bringing more incremental funds and transaction volume. However, in the prior art, entrusted transactions are generally carried out through manual entrustment, or by logging in separately offline, which leads to complicated entrusted transaction procedures and low transaction efficiency, thereby seriously affecting the transaction volume.

Contents of the invention

This application provides an account authorization method, device, equipment, storage medium and computer program products, so as to reduce the steps in the transaction process, improve the efficiency of authorization and verification in entrusted transactions, and ensure the security of transactions. On the basis of this, the convenience of user transactions is improved.

In the first aspect, an account authorization method is provided, including: obtaining account authorization information; sending account authorization information to the recipient; determining that the recipient has signed an authorization agreement corresponding to the account authorization information; obtaining and displaying the authorization agreement; The signing operation on the agreement; send the authorization agreement signed by the sponsor to the third party.

In the second aspect, an account authorization method is provided, including: receiving account authorization information; determining to sign an authorization agreement corresponding to the account authorization information; obtaining and displaying the authorization agreement; obtaining the signing operation of the recipient on the authorization agreement; License agreement signed by the person.

In a third aspect, an account authorization device is provided, including: a first acquisition module, a first sending module, a determination module, a second acquisition module, a first display module, a third acquisition module, and a second sending module, wherein the first The obtaining module is used to obtain account authorization information; the first sending module is used to send account authorization information to the recipient; the determination module is used to determine that the recipient has signed an authorization agreement corresponding to the account authorization information; the second obtaining module is used to obtain the authorization agreement; The first display module is used to display the authorization agreement; the third acquisition module is used to obtain the initiator's signing operation on the authorization agreement; the second sending module is used to send the authorization agreement signed by the initiator to the third party.

In a fourth aspect, an account authorization device is provided, including: a receiving module, a determination module, a first acquisition module, a first display module, a second acquisition module, and a sending module, wherein the receiving module is used to receive account authorization information; determine module, used to determine the authorization agreement corresponding to the signed account authorization information; the first acquisition module, used to obtain the authorization agreement; the first display module, used to display the authorization agreement; the second acquisition module, used to obtain the recipient's authorization agreement The signing operation; the sending module is used to send the authorization agreement signed by the recipient to the third party.

In a fifth aspect, there is provided an electronic device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and perform the process described in the first aspect, the second aspect or methods in their respective implementations.

In a sixth aspect, there is provided a computer-readable storage medium for storing a computer program, and the computer program causes a computer to execute the method in the first aspect, the second aspect, or each implementation thereof.

In a seventh aspect, a computer program product is provided, including computer program instructions, the computer program instructions cause a computer to execute the method in the first aspect, the second aspect, or each implementation manner thereof.

In an eighth aspect, a computer program is provided, which enables a computer to execute the method in the first aspect, the second aspect, or each implementation thereof.

Through the technical solution of this application, the initiator can obtain and send the initiator's account authorization information to the recipient, and the recipient can obtain the account authorization information, and can obtain the authorization agreement when signing the authorization agreement corresponding to the account authorization information, and then , the recipient can send the authorization agreement signed by the above recipient to the third party. The originator can also sign the authorization agreement after confirming that the recipient has signed the authorization agreement corresponding to the above account authorization information, and send the authorization agreement signed by the originator to the third party. After the third party obtains the authorization agreement signed by the initiator and the recipient, it can approve the authorization agreement. After the approval, the account authorization can be realized. The above method reduces the steps in the transaction process and improves the authorization in the entrusted transaction. And the efficiency of verification, and ensure the security of transactions, on the basis of improving transaction efficiency, improve the convenience of user transactions.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

FIG. 1 is a diagram of an application scenario provided by an embodiment of the present application;

FIG. 2 is a flow chart of an account authorization method provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of an account authorization relationship provided by an embodiment of the present application;

Fig. 4 is a schematic diagram of an account authorization page provided by the embodiment of the present application;

Fig. 5 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 6 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 7 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 8 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

FIG. 9 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 10 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 11 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 12 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 13 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 14 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 15 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 16 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 17 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 18 is a schematic diagram of another account authorization page provided by the embodiment of this application;

Fig. 19 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 20 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 21 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 22 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 23 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 24 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 25 is a schematic diagram of another account authorization page provided by the embodiment of the present application;

Fig. 26 is a schematic diagram of an account authorization device provided by an embodiment of the present application;

Fig. 27 is a schematic diagram of another account authorization device provided by the embodiment of the present application;

Fig. 28 is a schematic block diagram of an electronic device 2800 provided by an embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

It should be noted that the terms "first" and "second" in the description and claims of the present invention and the above drawings are used to distinguish similar objects, but not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or server comprising a series of steps or elements is not necessarily limited to the expressly listed instead, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus.

As mentioned above, in the prior art, in the process of entrusted transactions, it is generally carried out through manual entrustment, or by logging in separately offline. This method leads to complicated entrusted transaction procedures and low transaction efficiency, which seriously affects the transaction volume. .

In order to solve the above-mentioned technical problems, the inventive idea of this application is: the initiator can authorize the account of the initiator to the accounts of one or more recipients.

It should be understood that the technical solution of the present application can be applied to the following scenarios, but is not limited to: Exemplarily, FIG. 1 is a diagram of an application scenario provided by the embodiment of the application. As shown in FIG. 1 , the application scenario may include Initiator 110 , Recipient 120 , Server 130 and Third Party 140 . The initiator 110 or the recipient 120 may be connected to the server 130 through a wired network or a wireless network, and the server 130 may be connected to a third party 140 through a wired network or a wireless network. In some implementation manners, the initiator 110 may be a device used by the initiator, and the initiator may use the initiator 110 to authorize his account to one or more recipients. In some implementation manners, the recipient 120 may be a device used by the recipient, and the recipient may use the recipient 120 to accept the account authorized by the initiator. In some practicable manners, the approval personnel, such as the internal compliance approval personnel of the trading software of a securities company, can use the third party 140 to approve the authorization agreement signed by the initiator and the acceptor.

In some implementations, the initiator 110, the recipient 120, or the third party 140 can be mobile phones, tablet computers, desktops, laptops, handheld computers, notebook computers, vehicle-mounted devices, ultra-mobile personal computers (ultra-mobile personal computer (UMPC), netbook, and cellular phone, personal digital assistant (personal digital assistant, PDA), augmented reality (augmented reality, AR)\virtual reality (virtual reality, VR) equipment, etc., but not limited thereto. In some implementations, server 130 may be used to respond to requests from initiator 110 , recipient 120 , or third party 140 . Wherein, the server 130 may be one server, or a server cluster composed of multiple servers, or a cloud platform control center, which is not limited in this embodiment of the present application. In addition, FIG. 1 exemplarily shows an initiator, an acceptor, a server, and a third party, and may actually include other numbers of initiators, acceptors, servers, and third parties, which are not limited in the present application.

After introducing the application scenarios of the embodiments of the present application, the technical solution of the present application will be described in detail below:

Fig. 2 is an interactive flow chart of an account authorization method provided by the embodiment of the present application. This method can be executed by the initiator 110, the recipient 120, and the third party 140 as shown in Fig. 1, but is not limited thereto, as shown in Fig. 2 As shown, the method may include the following steps:

S201. The initiator acquires account authorization information;

S202. The initiator sends account authorization information to the recipient;

S203. The recipient determines that the recipient signs an authorization agreement corresponding to the account authorization information;

S204. The recipient acquires and displays the authorization agreement;

S205. The recipient acquires the signature operation of the recipient on the authorization agreement;

S206. The recipient sends the authorization agreement signed by the recipient to the third party;

S207. The initiator determines that the recipient has signed an authorization agreement corresponding to the account authorization information;

S208. The initiator obtains and displays the authorization agreement;

S209. The initiator acquires the initiator's signing operation on the authorization agreement;

S210. The initiator sends the authorization agreement signed by the initiator to the third party;

S211. The third party obtains the approval operation performed by the approver on the authorization agreement signed by the acceptor and the authorization agreement signed by the initiator.

Optionally, S212: the third party sends a notification message to the initiator, so as to notify the initiator that the account authorization is successful.

Optionally, S213: the third party sends a notification message to the recipient, so as to notify the recipient that the account authorization is successful.

In some practicable manners, the information interaction between the initiator and the recipient may be forwarded by the server. For example, S202 may include: the initiator sends account authorization information to the server, and the server forwards the account authorization information to the initiator.

In another practicable manner, the initiator and the receiver can directly exchange information. In a word, this application does not limit the information exchange mode between the initiator and the receiver.

It should be understood that the embodiment of the present application is described by taking one initiator and one acceptor as an example. Of course, one sponsor can also authorize multiple accounts of himself to multiple recipients, and one recipient can also accept authorization from multiple accounts of multiple sponsors, which is not limited in this application.

Further, when the initiator needs to entrust an acceptor, at least two recommendees may be recommended based on the initiator's social information, and the account information of the recommendees may be displayed on the interface. Specifically: when determining the recommendation recipient, obtain the associated account information associated with the promoter, and based on the social information between the associated account and the promoter account, determine the degree of social connection between the two; at the same time, based on the associated account information Determine the account credit and transaction proficiency of the associated account, and then obtain the transaction parameters of the associated account; finally, based on the social connection, account credit, and transaction proficiency, comprehensively determine the associated recommendation for each associated account, and select the one with a higher associated recommendation Linked accounts act as referral recipients.

Specifically, based on the social information between the associated account and the initiator account, in the process of determining the degree of social association between the two, first obtain the amount of social information Inf(A , B), where the amount of transaction information includes the sum of the data amount of chat communication, the data amount of the web page content corresponding to the link, etc.; at the same time, it is detected whether the two accounts are friends, and if it is a friend, it is detected whether there is an Friend introduction relationship, if yes, friend parameter Int(A,B)=1, if not, friend parameter Int(A,B)=0. Afterwards, based on the amount of social information Inf(A,B) and the friend parameter Int(A,B), the degree of social connection is determined as:

Rea(A,B)=a·log ₂ Inf(A,B)+b·Int(A,B)

Among them, a and b are the set correlation factors respectively.

In the process of account credit and transaction proficiency based on the associated account A, the account credit is used to represent the credit Cre_A of the recipient in the transaction process, and the credit can be directly obtained through the system to reflect the credit of the recipient; transaction proficiency Fic_A is used to represent the recipient's transaction skills, strategies and other transaction capabilities during the transaction process. In this embodiment, it can be obtained by the following formula:

Then, based on the account credit and transaction proficiency of the associated account A, the transaction parameters of the associated account are obtained:

Among them, k represents the number of transactions within the preset time period, which includes one month, one quarter, etc.; i represents the transaction identifier of a certain transaction, and pro(i) represents the transaction income corresponding to the i-th transaction.

Based on the degree of social association, account credit and transaction proficiency, the degree of association recommendation corresponding to each associated account is comprehensively determined. For example, by means of weighted summation, the association recommendation between account A and account B is obtained:

Re c(A,B)＝c·Re a(A,B)+d·Tran_A

Among them, c and d are the set recommendation factors respectively.

In this embodiment, through the above method of recommending associated accounts, it is possible to recommend objective associated accounts for the initiator based on account information, account association degree, user transaction ability, etc., so that the initiator can select an appropriate account based on the recommended information. It improves the utilization rate of transaction information and the objectivity of recipient selection.

Exemplarily, the authorization relationship between the initiator and the authorizer may be as shown in FIG. 3 , but is not limited thereto.

In some possible implementations, as shown in Figure 4, the sponsor or recipient can click the authorization management icon on the full function page of a certain brokerage's trading software to enter the authorization management page to perform account authorization operations.

It should be noted that the initiator or acceptor can also enter the authorization management page through other means, or the initiator or acceptor can enter other pages to perform account authorization operations, and this application does not limit this.

In some practicable manners, all function pages of the above-mentioned brokerage trading software may display a multi-account management module for whitelist users, and the multi-account management module may include: authorization management icons and application multi-account icons, but not limited thereto.

It should be understood that this application does not limit all functional pages of the brokerage trading software, nor does it limit the modules displayed on all functional pages and the icons included in each module.

In some practicable ways, assuming that the initiator does not authorize his account to any recipient, after the initiator obtains that the initiator clicks the authorization button on the authorization management page, as shown in (a) in Figure 5 , the authorization management page will display that there is no authorization initiated yet.

In some practicable manners, the initiator can obtain the initiator's first operation on the Add Authorization button on the authorization management page, and respond to the first operation, as shown in (b) in Figure 5, to display the transaction password input box .

Exemplarily, the above-mentioned first operation may specifically be single click, double-click, press, drag to a designated area, or a floating touch gesture, etc., which is not limited in the present application.

In some practicable manners, the initiator may obtain the transaction password entered by the initiator in the above transaction password input box. When the above transaction password is correct, as shown in (a) in Figure 6, the initiator will display the add authorization page,

In some practicable manners, as shown in (b) and (c) in FIG. 6 , the initiator may obtain the account authorization information entered by the initiator on the above-mentioned adding authorization page.

In some practicable manners, the account authorization information may include at least one of the following, but is not limited thereto: recipient account number, authorized account, transaction authority, fund authority, and the like.

Exemplarily, the recipient's account number may be a six-digit number. The authorized account can be a cash account of a certain stock or a margin trading account of a certain stock. Trading authority may include: a certain stock, a certain option, a certain derivative, a certain equity, a certain low-priced stock, a certain short sale, etc. Fund permissions may include: fund transfer and currency exchange, etc.

In other practicable ways, for an authorized account that is a financing account, the originator can set a corresponding upper limit of the financing amount, but it cannot exceed the upper limit set by the originator. For example, as shown in FIG. 7 , the account authorization information may also include: an upper limit of a financing amount, a maximum upper limit, and the like.

In some practicable manners, as shown in (c) or FIG. 7 in FIG. 6, the initiator can obtain the second operation of the initiator on the next button in the adding authorization page, and respond to the second operation, as shown in FIG. 8 As shown in (a) in , the initiator can display the authorization information confirmation page.

It should be understood that the second operation is similar to the above first operation, and will not be repeated in this application.

Exemplarily, the authorization information confirmation page may include: account authorization information, an authorization authorization identifier, an authorization initiation button, etc., but is not limited thereto. For example, the consent authorization mark may include: "The above authorization content is confirmed to be correct" and "I agree to disclose personal real-name information to the other party".

In some practicable manners, the initiator may obtain the initiator's selection operation of the consent authorization logo on the authorization information confirmation page and the third operation of the initiation authorization button, and respond to the selection operation and the third operation, as shown in Figure 8 (b) to display the transaction password input box. Wherein, the third operation is similar to the above-mentioned first operation, and will not be repeated in this application.

Exemplarily, the arrangement sequence of numbers in the transaction password input box may be dynamically changed. Comparing (b) in Fig. 8 and (b) in Fig. 5, it can be seen that the sequence of numbers in the transaction password input box is different, which can improve the security and privacy when entering the transaction password.

In some practicable manners, the initiator can obtain the transaction password entered by the initiator in the above-mentioned transaction password input box, and when the above-mentioned transaction password is correct, the initiator can send the above-mentioned account authorization information to the recipient.

In some practicable manners, when the above-mentioned transaction password is correct, as shown in (c) in FIG. 8 , the initiator can display that the authorization has been sent, and it can be seen that the current authorization status is waiting for the recipient to accept the authorization.

In some practicable ways, assuming that the recipient has not successfully accepted any account authorization, after the recipient obtains that the recipient clicks the accept authorization button on the authorization management page, as shown in Figure 9, the authorization management page at this time It will show that there are no licenses accepted yet.

In some practicable manners, the recipient may obtain the recipient's fifteenth operation on the authorization record button on the authorization management page, and display the authorization record page in response to the fifteenth operation. Wherein, the fifteenth operation is similar to the above-mentioned first operation, and will not be repeated in this application.

In some practicable manners, the recipient can acquire the recipient's sixteenth operation on the acceptance record in the authorization record page, and respond to the sixteenth operation, as shown in (a) in Figure 10, to display that the recipient accepts the authorization record. Wherein, the sixteenth operation is similar to the first operation above, and will not be repeated in this application.

Exemplarily, the authorization record accepted by the recipient may include: account authorization information and a status switching button. Wherein, the state switching button may be a small dot icon located behind the authorization state in the account authorization information, and this application does not limit the position, color and shape of the state switching button. For example: as shown in Figure 10(a), the authorization status here is: waiting for authorization, and the small dot icon after it is a status switch button.

In some practicable manners, before the recipient obtains the recipient's fifteenth operation on the authorization record button on the authorization management page, the recipient can first check whether there is a prompt label on the authorization record button. If the authorization record button has the above-mentioned prompt label, the recipient obtains the recipient's fifteenth operation on the authorization record button.

Exemplarily, as shown in FIG. 9 , the prompt label may be a circle 1 mark in the upper right corner of the authorization record button, indicating that there is an authorization record at this time. This application does not limit the position, color and shape of the prompt label.

In some practicable manners, the recipient can obtain the thirteenth operation of the recipient on the state switching button of the account authorization information, and respond to the thirteenth operation, as shown in (b) in Figure 10, to display authorization information confirmation page. Wherein, the authorization information confirmation page may include: account authorization information, consent authorization logo and accept button, but not limited thereto. For example, the consent authorization mark may include: "The above authorization content is confirmed to be correct" and "I agree to disclose personal real-name information to the other party". In addition, the thirteenth operation is similar to the first operation above, and will not be repeated here.

In some practicable manners, the acceptor can obtain the selection operation of the consent authorization logo and the fourteenth operation of the acceptor on the accept button, as shown in (c) in FIG. 10 , to display the transaction password input box. Wherein, the fourteenth operation is similar to the first operation above, and will not be repeated here.

In some practicable manners, the recipient can obtain the transaction password entered by the recipient in the transaction password input box, and if the transaction password is correct, the recipient can determine that the recipient signs an authorization agreement corresponding to the account authorization information.

In some practicable manners, after the recipient determines that the recipient signs the authorization agreement corresponding to the account authorization information, the recipient may obtain and display the authorization agreement.

Exemplarily, as shown in (a) in FIG. 11 , the page where the recipient displays the authorization agreement may include: I have read and signed the "Third Party Securities Account Authorization Letter" button and a signature button, but not limited thereto.

In some practicable ways, after the acceptor acquires the recipient's operation on the above two buttons, as shown in (b) in Figure 11, the acceptor can display the agreement signing page, and the acceptor can click on this page Perform the signing operation for the authorization agreement. Wherein, the recipient's operation on these two buttons may be selecting, clicking, pressing, etc., which is not limited in this application.

Exemplarily, as shown in (b) in FIG. 11 , the above agreement signing page may include: a rewrite button. The recipient can obtain the recipient's signature operation on the authorization agreement after obtaining the recipient's click operation on the rewrite button.

In some implementable manners, as shown in (b) in FIG. 11 , the above agreement signing page may include: a submit button. The accepting party can obtain the authorization agreement signed by the third party after the accepting party clicks on the submit button.

In some practicable ways, as shown in (c) in Figure 11, after the acceptor obtains the click operation of the acceptor on the submit button, the acceptor can display that the authorization has been accepted, and the current authorization status is waiting for the initiator to sign the agreement .

In some practicable manners, as shown in FIG. 12 , the initiator may acquire the initiator's fourth operation on the authorization record button on the authorization management page, and display the authorization record page in response to the fourth operation. Wherein, the fourth operation is similar to the above-mentioned first operation, and will not be repeated in this application.

In some practicable manners, the originator can obtain the initiator's fifth operation on the origination record in the authorization record page, and respond to the fifth operation, as shown in (a) in Figure 13, to display the authorization initiated by the initiator Record. Wherein, the fifth operation is similar to the above-mentioned first operation, and will not be repeated in this application.

Exemplarily, the authorization record initiated by the initiator may include: account authorization information. Wherein, the account authorization information may include: authorization status. The authorization status may indicate the authorization status of the current account authorization, and the authorization status may also be referred to as status information.

In some practicable manners, if the status information is the status of an agreement to be signed, the initiator may determine that the recipient has signed the authorization agreement corresponding to the account authorization information.

In some practicable manners, before obtaining the initiator's fourth operation on the authorization record button on the authorization management page, the initiator may first check whether there is a prompt label on the authorization record button. If there is a prompt label on the authorization record button, the initiator obtains the initiator's fourth operation on the authorization record button.

Exemplarily, as shown in FIG. 12 , the prompt label may be a circle 1 mark in the upper right corner of the authorization record button, indicating that there is an authorization record at this time. This application does not limit the position, color and shape of the prompt label.

In some practicable manners, the authorization record initiated by the initiator may further include: a state switching button corresponding to the account authorization information.

Exemplarily, as shown in (a) in Figure 13, the state switch button can be a small dot icon located after the authorization state in the account authorization information. This application specifies the position, color and shape of the state switch button. No limit.

In some practicable manners, the initiator may obtain the initiator's sixth operation on the above-mentioned state switching button, and respond to the sixth operation, as shown in (b) in FIG. 13 , to display an agreement signing page. Wherein, the sixth operation is similar to the above first operation, and will not be repeated here.

Exemplarily, as shown in (b) of FIG. 13 , the signing agreement page may include: a signing agreement button, but not limited thereto.

In some practicable manners, the initiator can acquire the initiator's seventh operation on the signing agreement button on the above-mentioned signing agreement page, and in response to the seventh operation, as shown in (c) in Figure 13, the initiator can display the transaction Password input box.

In some practicable manners, when the initiator acquires that the transaction password entered by the initiator in the transaction password input box is correct, as shown in (a) in FIG. 14 , the initiator may display the authorization agreement.

In some practicable manners, as shown in (a) and (b) in Figure 14, the initiator's operation of obtaining the initiator's signature on the authorization agreement is similar to the above-mentioned operation of the recipient's acquisition of the recipient's signature on the authorization agreement, This application will not go into details here.

In some practicable manners, as shown in (c) in FIG. 14 , after acquiring the initiator's signing operation on the authorization agreement, the initiator can sign the agreement page, and the page can display that the current authorization status is the signed agreement.

In some practicable manners, as shown in (c) in FIG. 14 , the above signing agreement page may also display an authorization record button. When the initiator obtains the click operation for the authorization record, it can trigger the display of the authorization record page as shown in Figure 15, which may include a withdrawal authorization button. When the initiator obtains the click operation for the withdrawal authorization button , in response to the click operation, to withdraw the account authorization corresponding to the above account authorization information.

In some achievable ways, the approver can approve the authorization agreement signed by the initiator and the authorization agreement signed by the recipient, such as: review the account authorization information sent by the initiator, verify the identity of the initiator, and verify the identity of the recipient. Identity, etc., but not limited to.

It should be understood that when the third party passes the review of the authorization agreement signed by the initiator and the recipient, the corresponding authorization relationship can be successfully added.

In some practicable manners, after the account authorization information is successfully authorized, the initiator may obtain the initiator's eighth operation on the authorization record button on the authorization management page, and display the authorization record page in response to the eighth operation. Wherein, the eighth operation is similar to the above first operation, and will not be repeated here.

In some practicable manners, the originator can obtain the initiator's ninth operation on the initiation record on the authorization record page, and respond to the ninth operation, as shown in (a) in Figure 16, to display the account authorization information corresponding Authorization record. Wherein, the ninth operation is similar to the above-mentioned first operation, and will not be repeated here.

In some practicable manners, the initiator may obtain the initiator's tenth operation of the authorization record corresponding to the account authorization information, and respond to the tenth operation, as shown in (b) in Figure 16, to display the account authorization information corresponding to The details page of the authorization record. Wherein, the tenth operation is similar to the above first operation, and will not be repeated here.

In some practicable manners, after the account authorization information is successfully authorized, the recipient can acquire the recipient's seventeenth operation on the authorization record button on the authorization management page, and display the authorization record page in response to the seventeenth operation. Wherein, the eighteenth operation is similar to the above first operation, and will not be repeated here.

In some practicable manners, the recipient can obtain the recipient's eighteenth operation on the acceptance record in the authorization record page, and respond to the eighteenth operation, as shown in (a) in Figure 17, to display the account authorization The authorization record corresponding to the information. Wherein, the ninth operation is similar to the above-mentioned first operation, and will not be repeated here.

In some practicable manners, the recipient can obtain the recipient's nineteenth operation on the authorization record corresponding to the above-mentioned account authorization information, and respond to the nineteenth operation, as shown in (b) in Figure 17, to display the account The detailed page of the authorization record corresponding to the authorization information. Wherein, the nineteenth operation is similar to the above first operation, and will not be repeated here.

In some implementable manners, the notification message sent by the third party to the initiator or recipient may be a notification message in at least one of the following forms, but is not limited thereto: voice, text.

In some possible implementations, the authorization record page can display authorization records of various authorization states. For example, the authorization states of the authorization records that can be displayed include: waiting for the other party to accept authorization, waiting to sign an agreement, under review by the system, authorization successful, authorization complete Rescission, withdrawal of authorization and rejection by the other party, etc., but not limited to this.

Exemplarily, as shown in FIG. 18 , taking the initiation record in the authorization record page as an example, some authorization records are shown, but not limited thereto. The contents displayed in the acceptance record on the authorization record page are also similar, and the present application will not repeat them here.

In some practicable manners, as shown in Figure 18, the initiator can obtain the initiator's screening operation on all account buttons, all account buttons or all status buttons below the initiation record on the authorization record page, and in response to the screening operation, initiate party can display the filtered authorization records. Of course, the screening operation for the acceptance record in the authorization record page is also similar, and the present application will not repeat it here.

In some practicable manners, as shown in (a), (b) and (c) of FIG. 19 , the screening operations are respectively performed on all account buttons, all account buttons and all status buttons. Generally, all accounts, all accounts and all states can be selected by default. The initiator or acceptor can also display the filtered authorization records in the order of filtering.

In some implementation manners, as shown in (a) of FIG. 20 , the initiator can display all account authorization information for which authorization has been initiated and authorized successfully on the initiated authorization page of the authorization management page.

In other practicable manners, as shown in (b) of FIG. 20 , the acceptor may display all account authorization information that has accepted authorization and has been authorized successfully on the accepted authorization page of the authorization management page.

In some practicable manners, the initiator or recipient can screen the accounts displayed on the authorization management interface. The screening method is similar to the above-mentioned method for initiating records or accepting records in authorization records, and this application will not repeat them here.

In some practicable manners, as shown in (a), (b) and (c) of Figure 21, the initiator can add an authorization tag to the successfully authorized account. For example, the authorization label may be an arrow pointing to the right at the back of the initiated authorization account, and this application does not impose any restrictions on the position, shape and color of the authorization label.

In some practicable manners, the initiator can also distinguish whether the authorized account is initiated or accepted by the color of the arrow, for example, if the arrow color is orange, it means that the authorized account is the initiated account.

In some practicable manners, as shown in (a), (b) and (c) of FIG. 22 , the recipient can add an authorization tag to the successfully authorized account. For example, the authorization label may be an arrow facing left behind the accepted authorized account, and this application does not impose any restrictions on the position, shape and color of the authorization label.

In some practicable manners, the recipient can also distinguish whether the authorized account is accepted or initiated by the color of the arrow, for example, if the arrow color is blue, it indicates that the authorized account is an accepted account.

In some practicable manners, after the account information is authorized successfully, as shown in (a) of FIG. 23 , the detail page of the authorization record corresponding to the account authorization information displayed on the initiator may include: a deauthorization button.

In some practicable manners, the initiator may obtain the initiator's eleventh operation on the deauthorization button, and respond to the eleventh operation to cancel the authorization corresponding to the account authorization information. Wherein, the eleventh operation is similar to the above-mentioned first operation, and will not be repeated here.

Exemplarily, as shown in (b) of Figure 23, after obtaining the initiator's click operation on the deauthorization button, the initiator may respond to the click operation to display a pop-up message saying "The deauthorization will be irreversible, are you sure you want to deauthorize?" window, after the initiator obtains the initiator's click operation on the release button in the pop-up window, as shown in (c) of Figure 23, a transaction password input box is displayed. When the initiator obtains the correct transaction password entered by the initiator in the transaction password input box, the authorization corresponding to the above account authorization information is successfully released.

In some practicable manners, after successfully canceling the authorization corresponding to the account authorization information, as shown in FIG. 24 , the initiator can display the canceled authorization record on the authorization record page.

In some practicable manners, after the account information is authorized successfully, as shown in (a) of FIG. 25 , the detail page of the authorization record corresponding to the account authorization information displayed on the initiator may include: modify authorization button.

In some practicable manners, the initiator may obtain the initiator's twelfth operation on the modify authorization button, and respond to the twelfth operation to modify the authorization corresponding to the account authorization information. Wherein, the twelfth operation is similar to the first operation above, and will not be repeated here.

Exemplarily, as shown in (b) of FIG. 25 , after acquiring the initiator's click operation on the modification authorization button, the initiator may display a transaction password input box in response to the click operation. When the initiator obtains the correct transaction password entered by the initiator in the merchant’s transaction password input box, as shown in (c) of Figure 25, the authorization information modification page is displayed, and the initiator can obtain the initiator’s modification of the account authorization information .

After the account is authorized in the above manner, the recipient can obtain the initiator's account information, such as account type, account balance and so on. Afterwards, the recipient can conduct transactions in the sponsor's account in the sponsor's authorized name based on the sponsor's account information, such as stock trading, fund trading, and the like. At the same time, the transaction records and updated account information will be uploaded to the cloud and synchronized to the initiator's terminal account. The initiator can obtain the transaction records and updated account information in his own account. Through the above method, data synchronization, transparency and security in the entrusted transaction process are improved.

To sum up, the technical solutions provided by the above embodiments bring at least the following beneficial effects: On the one hand, this application provides a streamlined account authorization method with good ease of use, and the initiator can obtain and send the initiator’s account Authorization information to the recipient, the recipient can obtain the account authorization information, and can obtain the authorization agreement when signing the authorization agreement corresponding to the account authorization information, and then the recipient can send the authorization agreement signed by the above-mentioned recipient to the third party . The originator can also sign the authorization agreement after confirming that the recipient has signed the authorization agreement corresponding to the above account authorization information, and send the authorization agreement signed by the originator to the third party. After the third party obtains the authorization agreement signed by the initiator and the recipient, the authorization agreement can be approved, and the account authorization can be realized after the approval is passed. Therefore, the problem that the prior art does not support account authorization is solved.

On the other hand, in this application, during the steps of obtaining and sending account authorization information, signing an authorization agreement, and canceling, modifying, and withdrawing authorization, the initiator and recipient will display the transaction password input box. Only when the transaction password input box is obtained Only when the correct transaction password is entered can the above steps be successfully carried out, thereby improving the security of account authorization.

On the other hand, this application can add an authorization label to the account that has been authorized successfully, so that the authorization status of different accounts can be easily distinguished, and the user experience is improved.

Fig. 26 is a schematic diagram of an account authorization device provided by the embodiment of the present application. The account authorization device may be the initiator 110 as shown in Fig. 1, but is not limited thereto. As shown in Fig. 26, the account authorization device includes:

The first obtaining module 2601 is used to obtain account authorization information;

The first sending module 2602, configured to send account authorization information to the recipient;

A determination module 2603, configured to determine that the recipient has signed an authorization agreement corresponding to the account authorization information;

The second obtaining module 2604 is used to obtain the authorization agreement;

The first display module 2605 is used to display the authorization agreement;

The third obtaining module 2606 is used to obtain the sponsor's signing operation on the authorization agreement;

The second sending module 2607 is configured to send the authorization agreement signed by the initiator to the third party.

In some implementable manners, the first acquiring module 2601 is specifically configured to: acquire the first operation of the Add Authorization button on the authorization management page; display the transaction password input box in response to the first operation; acquire the transaction password input box in the transaction password input box. The transaction password entered in ; when the transaction password is correct, the add authorization page is displayed; obtain the account authorization information entered on the add authorization page.

In some implementable manners, the first sending module 2602 is specifically configured to: acquire the second operation of the next button on the adding authorization page; respond to the second operation to display the authorization information confirmation page, and the authorization information confirmation page includes: Account authorization information, consent authorization logo and initiation authorization button; obtain the selection operation of the consent authorization logo and the third operation of the initiation authorization button; respond to the selection operation and the third operation to display the transaction password input box; obtain the transaction password The transaction password entered in the input box; when the transaction password is correct, the account authorization information will be sent to the recipient.

In some implementable manners, the determining module 2603 is specifically configured to: obtain the fourth operation on the authorization record button on the authorization management page; display the authorization record page in response to the fourth operation; obtain the initiation record on the authorization record page The fifth operation; in response to the fifth operation, to display the authorization record initiated by the initiator, the authorization record initiated by the initiator includes account authorization information; determine the status information of the account authorization information; if the status information is the status of the agreement to be signed, then determine The recipient has signed the authorization agreement corresponding to the account authorization information.

In some implementable manners, the account authorization apparatus further includes: a checking module 2608, configured to check whether there is a prompt label on the authorization record button. If there is a prompt label on the authorization record button, the determination module 2603 is specifically configured to obtain a fourth operation on the authorization record button.

In some practicable manners, the authorization record initiated by the initiator also includes a state switching button corresponding to the account authorization information. The first display module 2605 is specifically used to: obtain the sixth operation on the state switching button; respond to the sixth operation to display the signing agreement page; obtain the seventh operation on the signing agreement button in the signing agreement page; respond to the seventh Action to show signed agreement.

In some implementable manners, the account authorization apparatus further includes: a fourth obtaining module 2609 , a second display module 2610 , a fifth obtaining module 2611 , a third display module 2612 , a sixth obtaining module 2613 and a fourth display module 2614 . Among them, the fourth obtaining module 2609 is used to obtain the eighth operation of the authorization record button on the authorization management page after the account authorization information is successfully authorized; the second display module 2610 is used to display the authorization record page in response to the eighth operation The fifth obtaining module 2611 is used to obtain the ninth operation on the initiation record in the authorization record page; the third display module 2612 is used to respond to the ninth operation to display the authorization record corresponding to the account authorization information; the sixth obtaining module 2613 The tenth operation for acquiring the authorization record corresponding to the account authorization information; the fourth display module 2614 is configured to display the detailed page of the authorization record corresponding to the account authorization information in response to the tenth operation.

It should be understood that the device embodiment and the method embodiment on the initiator side may correspond to each other, and similar descriptions may refer to the corresponding method embodiment on the initiator side. To avoid repetition, details are not repeated here.

Specifically, the account authorization device shown in FIG. 26 can execute the above method embodiment on the initiator side, and the aforementioned and other operations and/or functions of the various modules in the account authorization device shown in FIG. For the sake of brevity, the corresponding process of the side method embodiment is not repeated here.

The foregoing embodiments of the methods at the initiator side in the embodiments of the present application are described from the perspective of functional modules with reference to the accompanying drawings. It should be understood that the functional modules may be implemented in the form of hardware, may also be implemented by instructions in the form of software, and may also be implemented by a combination of hardware and software modules. Specifically, each step of the method embodiment in the embodiment of the present application can be completed by an integrated logic circuit of the hardware in the processor and/or instructions in the form of software, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as hardware The decoding processor is executed, or the combination of hardware and software modules in the decoding processor is used to complete the execution. Optionally, the software module may be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, and registers. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps in the above method embodiments in combination with its hardware.

Fig. 27 is a schematic diagram of an account authorization device provided in an embodiment of the present application. The account authorization device may be the recipient 120 as shown in Fig. 1, and the account authorization device includes:

A receiving module 2701, configured to receive account authorization information;

A determination module 2702, configured to determine the authorization agreement corresponding to the signed account authorization information;

The first obtaining module 2703 is used to obtain the authorization agreement;

The first display module 2704 is used to display the authorization agreement;

The second obtaining module 2705 is used to obtain the signing operation of the recipient on the authorization agreement;

A sending module 2706, configured to send the authorization agreement signed by the recipient to a third party.

In some implementable manners, the determination module 2702 is specifically configured to: obtain the thirteenth operation of the state switching button of the account authorization information; respond to the thirteenth operation to display the authorization information confirmation page, and the authorization information confirmation page includes: account Authorization information and the accept button; obtain the fourteenth operation of the accept button; respond to the fourteenth operation to display the transaction password input box; obtain the transaction password input in the transaction password input box; if the transaction password is correct, confirm the signature The authorization agreement corresponding to the account authorization information.

In some implementation manners, the account authorization apparatus further includes: a third obtaining module 2707 , a second display module 2708 , a fourth obtaining module 2709 and a third display module 2710 . Wherein, the third obtaining module 2707 is used to obtain the fifteenth operation on the authorization record button in the authorization management page; the second display module 2708 is used to display the authorization record page in response to the fifteenth operation; the fourth obtaining module 2709 The sixteenth operation for obtaining the acceptance record in the authorization record page; the third display module 2710 is used for responding to the sixteenth operation, to display the authorization record accepted by the recipient, and the authorization record accepted by the recipient includes account authorization information and state toggle buttons.

In some implementable manners, the account authorization apparatus further includes: a checking module 2711 . The checking module 2711 is used to check whether there is a prompt label on the authorization record button. The third acquiring module 2707 is specifically configured to acquire the fifteenth operation on the authorization record button if there is a prompt label on the authorization record button.

In some implementation manners, the account authorization apparatus further includes: a fifth obtaining module 2712 , a fourth display module 2713 , a sixth obtaining module 2714 , a fifth display module 2715 , a seventh obtaining module 2716 and a sixth display module 2717 . Among them, the fifth obtaining module 2712 is used to obtain the seventeenth operation on the authorization record button in the authorization management page after the account authorization information is successfully authorized; the fourth display module 2713 is used to display the authorization in response to the seventeenth operation. record page; the sixth obtaining module 2714 is used to obtain the eighteenth operation on the acceptance record in the authorization record page; the fifth display module 2715 is used to display the authorization record corresponding to the account authorization information in response to the eighteenth operation; The seventh obtaining module 2716 is used to obtain the nineteenth operation of the authorization record corresponding to the account authorization information; the sixth display module 2717 is used to display the detailed page of the authorization record corresponding to the account authorization information in response to the nineteenth operation.

It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, details are not repeated here.

Specifically, the account authorization device shown in FIG. 27 can execute the above-mentioned method embodiment on the accepting side, and the aforementioned and other operations and/or functions of each module in the account authorizing device shown in FIG. For the sake of brevity, the corresponding processes of the method embodiments are not repeated here.

The above embodiments of the methods on the receiving side of the embodiments of the present application are described from the perspective of functional modules with reference to the accompanying drawings. It should be understood that the functional modules may be implemented in the form of hardware, may also be implemented by instructions in the form of software, and may also be implemented by a combination of hardware and software modules. Specifically, each step of the method embodiment in the embodiment of the present application can be completed by an integrated logic circuit of the hardware in the processor and/or instructions in the form of software, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as hardware The decoding processor is executed, or the combination of hardware and software modules in the decoding processor is used to complete the execution. Optionally, the software module may be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, and registers. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps in the above method embodiments in combination with its hardware.

Fig. 28 is a schematic block diagram of an electronic device 2800 provided by an embodiment of the present application. The electronic device 2800 may be an initiator or an acceptor in this application.

As shown in Figure 28, the electronic device 2800 may include:

A memory 2810 and a processor 2820 , the memory 2810 is used to store computer programs, and transmit the program codes to the processor 2820 . In other words, the processor 2820 can invoke and run a computer program from the memory 2810, so as to implement the method in the embodiment of the present application.

For example, the processor 2820 can be used to execute the above-mentioned method embodiments according to the instructions in the computer program.

In some embodiments of the present application, the processor 2820 may include but not limited to:

General-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates Or transistor logic devices, discrete hardware components, and so on.

In some embodiments of the present application, the memory 2810 includes but is not limited to:

volatile memory and/or non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash. The volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (Static RAM, SRAM), Dynamic Random Access Memory (Dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synch link DRAM, SLDRAM) and Direct Memory Bus Random Access Memory (Direct Rambus RAM, DR RAM).

In some embodiments of the present application, the computer program can be divided into one or more modules, and the one or more modules are stored in the memory 2810 and executed by the processor 2820 to complete the method. The one or more modules may be a series of computer program instruction segments capable of accomplishing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

As shown in Figure 28, the electronic device may also include:

Transceiver 2830, which can be connected to the processor 2820 or the memory 2810.

Wherein, the processor 2820 can control the transceiver 2830 to communicate with other devices, specifically, can send information or data to other devices, or receive information or data sent by other devices. The transceiver 2830 may include a transmitter and a receiver. The transceiver 2830 may further include an antenna, and the number of antennas may be one or more.

It should be understood that the various components in the electronic device are connected through a bus system, wherein the bus system includes not only a data bus, but also a power bus, a control bus and a status signal bus.

The present application also provides a computer storage medium, on which a computer program is stored, and when the computer program is executed by a computer, the computer can execute the methods of the above method embodiments.

The embodiment of the present application also provides a computer program product including instructions, and when the instructions are executed by a computer, the computer executes the methods of the above method embodiments.

When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transferred from a website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a digital video disc (digital video disc, DVD)), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.

The above is only the specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the application, and should be covered Within the protection scope of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (17)

1. An account authorization method, characterized in that it includes:

   Obtain account authorization information;

   Send the account authorization information to the recipient;

   Confirm that the recipient has signed the authorization agreement corresponding to the account authorization information;

   Obtain and display said license agreement;

   Obtain the sponsor's signing operation on the authorization agreement;

   sending the authorization agreement signed by the sponsor to a third party.
2. The method according to claim 1, wherein said acquiring account authorization information comprises:

   Obtain the first action on the Add Authorization button in the Authorization Management page;

   In response to the first operation, to display a transaction password input box;

   Obtain the transaction password entered in the transaction password input box;

   When the transaction password is correct, the add authorization page is displayed;

   Obtain the account authorization information input on the adding authorization page.
3. The method according to claim 2, wherein the sending the account authorization information to the recipient comprises:

   Obtain the second operation of the next button on the adding authorization page;

   In response to the second operation, an authorization information confirmation page is displayed, and the authorization information confirmation page includes: the account authorization information, an authorization authorization identification, and an authorization initiation button;

   Obtaining a selection operation on the consent authorization identifier and a third operation on the initiation authorization button;

   Responding to the selection operation and the third operation, displaying a transaction password input box;

   Obtain the transaction password entered in the transaction password input box;

   When the transaction password is correct, send the account authorization information to the recipient.
4. The method according to claim 2 or 3, wherein the determined recipient has signed an authorization agreement corresponding to the account authorization information, including:

   Obtain the fourth operation on the authorization record button on the authorization management page;

   In response to the fourth operation, to display an authorization record page;

   Acquiring the fifth operation on the initiation record in the authorization record page;

   In response to the fifth operation, to display an authorization record initiated by the initiator, where the authorization record initiated by the initiator includes the account authorization information;

   determining status information of the account authorization information;

   If the status information is the status of an agreement to be signed, it is determined that the recipient has signed the authorization agreement corresponding to the account authorization information.
5. The method according to claim 4, characterized in that before obtaining the fourth operation on the authorization record button in the authorization management page, further comprising:

   Check whether there is a prompt label on the authorization record button;

   The fourth operation of obtaining the authorization record button on the authorization management page includes;

   If the authorization record button has the prompt label, the fourth operation on the authorization record button is acquired.
6. The method according to claim 4, wherein the authorization record initiated by the initiator further includes a state switching button corresponding to the account authorization information; displaying the authorization agreement includes:

   Obtain a sixth operation on the state switching button;

   In response to the sixth operation, to display the signing agreement page;

   Obtaining the seventh operation of the signing agreement button on the signing agreement page;

   In response to the seventh operation, the signed agreement is displayed.
7. The method according to claim 2 or 3, further comprising:

   After the account authorization information is successfully authorized, obtain an eighth operation on the authorization record button on the authorization management page;

   In response to the eighth operation, to display an authorization record page;

   The ninth operation of obtaining the initiation record in the authorization record page;

   In response to the ninth operation, display an authorization record corresponding to the account authorization information;

   The tenth operation of obtaining the authorization record corresponding to the account authorization information;

   In response to the tenth operation, a detailed page of the authorization record corresponding to the account authorization information is displayed.
8. An account authorization method, characterized in that it includes:

   Receive account authorization information;

   Determine to sign the authorization agreement corresponding to the account authorization information;

   Obtain and display said license agreement;

   Obtain the signing operation of the recipient on the authorization agreement;

   sending the authorization agreement signed by the recipient to a third party.
9. The method according to claim 8, wherein the determining to sign the authorization agreement corresponding to the account authorization information includes:

   Acquiring the thirteenth operation of the state switch button for the account authorization information;

   In response to the thirteenth operation, an authorization information confirmation page is displayed, and the authorization information confirmation page includes: the account authorization information, the consent authorization logo and an accept button;

   Acquiring the selection operation of the consent authorization logo and the fourteenth operation of the acceptance button;

   In response to the selection operation and the fourteenth operation, to display a transaction password input box;

   Obtain the transaction password entered in the transaction password input box;

   If the transaction password is correct, it is determined to sign an authorization agreement corresponding to the account authorization information.
10. The method according to claim 9, characterized in that, before the thirteenth operation of obtaining the state switching button of the account authorization information, further comprising:

    Obtain the fifteenth operation of the authorization record button on the authorization management page;

    In response to the fifteenth operation, to display an authorization record page;

    Obtain the sixteenth operation on the acceptance record in the authorization record page;

    In response to the sixteenth operation, to display the authorization record accepted by the recipient, the authorization record accepted by the recipient includes the account authorization information and the state switching button.
11. The method according to claim 10, characterized in that before obtaining the fifteenth operation on the authorization record button in the authorization management page, it also includes:

    Check whether there is a prompt label on the authorization record button;

    The acquisition of the fifteenth operation of the authorization record button on the authorization management page includes;

    If the prompt label is on the authorization record button, a fifteenth operation on the authorization record button is obtained.
12. The method according to claim 10 or 11, further comprising:

    After the account authorization information is successfully authorized, obtain a seventeenth operation on the authorization record button on the authorization management page;

    In response to the seventeenth operation, display an authorization record page;

    Obtain an eighteenth operation on the acceptance record in the authorization record page;

    In response to the eighteenth operation, display an authorization record corresponding to the account authorization information;

    The nineteenth operation of obtaining the authorization record corresponding to the account authorization information;

    In response to the nineteenth operation, a detailed page of the authorization record corresponding to the account authorization information is displayed.
13. An account authorization device, characterized in that it comprises:

    A first obtaining module, configured to obtain account authorization information;

    A first sending module, configured to send the account authorization information to the recipient;

    A determination module, configured to determine that the recipient has signed the authorization agreement corresponding to the account authorization information;

    a second obtaining module, configured to obtain the authorization agreement;

    a first display module, configured to display the authorization agreement;

    The third obtaining module is used to obtain the signing operation of the sponsor on the authorization agreement;

    The second sending module is configured to send the authorization agreement signed by the initiator to a third party.
14. An account authorization device, characterized in that it comprises:

    A receiving module, configured to receive account authorization information;

    A determination module, configured to determine to sign an authorization agreement corresponding to the account authorization information;

    a first obtaining module, configured to obtain the authorization agreement;

    a first display module, configured to display the authorization agreement;

    The second obtaining module is used to obtain the signing operation of the recipient on the authorization agreement;

    A sending module, configured to send the authorization agreement signed by the recipient to a third party.
15. An electronic device, characterized in that it comprises:

    processor; and

    a memory for storing executable instructions of the processor;

    Wherein, the processor is configured to execute the account authorization method according to any one of claims 1-7 or any one of claims 8-12 by executing the executable instructions.
16. A computer-readable storage medium, on which a computer program is stored, wherein, when the computer program is executed by a processor, the account authorization method described in any one of claims 1-7 or 8-12 is implemented.
17. A computer program product containing instructions, characterized in that, when the computer program product is run on an electronic device, the electronic device is made to perform the account authorization described in any one of claims 1-7 or 8-12 method.

Images