CN113902445A

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

Info

Publication number: CN113902445A
Application number: CN202111086425.5A
Authority: CN
Inventors: 张宝月; 刘翔; 张宇悦
Original assignee: Shenzhen Futu Network Technology Co Ltd
Current assignee: Shenzhen Futu Network Technology Co Ltd
Priority date: 2021-09-16
Filing date: 2021-09-16
Publication date: 2022-01-07
Also published as: WO2023040531A1

Abstract

The application provides an account authorization method, an account authorization device, a storage medium and a computer program product, wherein the account authorization device comprises: acquiring account authorization information; sending account authorization information to a recipient; determining an authorization protocol corresponding to the signed account authorization information of the receiver; acquiring and displaying an authorization protocol; acquiring signing operation of an initiator on an authorization protocol; the authorization agreement signed by the initiator is sent to the third party. Steps in the transaction process are reduced, the authorization and verification efficiency in entrusted transaction is improved, the transaction safety is guaranteed, and the transaction convenience of a user is improved on the basis of improving the transaction efficiency.

Description

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

Technical Field

The embodiment of the application relates to the technical field of internet, in particular to an account authorization method, an account authorization device, account authorization equipment, a storage medium and a computer program product.

Background

Currently, clients such as large-asset clients, trusts, family offices, asset management companies and the like in the market all have the appeal of performing asset management in an account authorization mode when using dealer trading software, that is, the own account is authorized to one or more other accounts for performing asset management. Moreover, the asset management mode through account authorization can be applied to scenes such as joint accounts and finance of relatives and friends, and more incremental funds and transaction amount are brought. However, in the prior art, the process of the entrusting transaction is generally performed in a manual entrusting manner or in a manner of separately logging in offline, which causes a great deal of entrusting transaction procedures and low transaction efficiency, thereby seriously affecting the transaction amount.

Disclosure of Invention

The application provides an account authorization method, an account authorization device, a storage medium and a computer program product, so that steps in a transaction process are reduced, authorization and verification efficiency in entrusted transaction is improved, transaction safety is guaranteed, and convenience of user transaction is improved on the basis of improving transaction efficiency.

In a first aspect, an account authorization method is provided, including: acquiring account authorization information; sending account authorization information to a recipient; determining an authorization protocol corresponding to the signed account authorization information of the receiver; acquiring and displaying an authorization protocol; acquiring signing operation of an initiator on an authorization protocol; the authorization agreement signed by the initiator is sent to the third party.

In a second aspect, there is provided an account authorization method, including: receiving account authorization information; determining an authorization protocol corresponding to the signed account authorization information; acquiring and displaying an authorization protocol; acquiring signing operation of a receiver on an authorization protocol; the authorized agreement signed by the recipient is sent to the third party.

In a third aspect, an account authorization apparatus is provided, including: the system comprises 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 acquisition module is used for acquiring account authorization information; the first sending module is used for sending account authorization information to the receiver; the determining module is used for determining an authorization protocol corresponding to the signed account authorization information of the receiver; the second acquisition module is used for acquiring the authorization protocol; the first display module is used for displaying the authorization protocol; the third acquisition module is used for acquiring signing operation of the initiator on the authorization protocol; the second sending module is used for sending the authorization agreement signed by the initiator to the third party.

In a fourth aspect, an account authorization apparatus is provided, including: the system comprises a receiving module, a determining module, a first obtaining module, a first display module, a second obtaining module and a sending module, wherein the receiving module is used for receiving account authorization information; the determining module is used for determining an authorization protocol corresponding to the signed account authorization information; the first acquisition module is used for acquiring the authorization protocol; the first display module is used for displaying the authorization protocol; the second acquisition module is used for acquiring signing operation of a receiver on the authorization agreement; and the sending module is used for sending the authorization agreement signed by the receiver to the third party.

In a fifth aspect, an electronic device is provided, comprising: a processor and a memory, the memory being configured to store a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform a method as in the first aspect, the second aspect or implementations thereof.

A sixth aspect provides a computer readable storage medium for storing a computer program for causing a computer to perform the method as in the first aspect, the second aspect or implementations thereof.

In a seventh aspect, a computer program product is provided, which comprises computer program instructions to make a computer execute the method according to the first aspect, the second aspect or the implementation manner thereof.

In an eighth aspect, a computer program is provided, which causes a computer to perform the method as in the first aspect, the second aspect or implementations thereof.

By the technical scheme, the initiator can acquire and send the account authorization information of the initiator to the receiver, the receiver can acquire the account authorization information, the authorization protocol can be acquired when the authorization protocol corresponding to the account authorization information is confirmed to be signed, and then the receiver can send the authorization protocol signed by the receiver to the third party. The initiator can also sign the authorization agreement after determining that the receiver signs the authorization agreement corresponding to the account authorization information, and send the authorization agreement signed by the initiator to the third party. After the third party obtains the authorization agreement signed by the initiator and the receiver, the authorization agreement can be approved, and after the approval is passed, account authorization can be realized.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is an application scenario diagram provided in an embodiment of the present application;

fig. 2 is a flowchart of an account authorization method according to an embodiment of the present application;

fig. 3 is a schematic view of an account authorization relationship provided in an embodiment of the present application;

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

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

FIG. 6 is a schematic diagram of another account authorization page provided in an embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

FIG. 26 is a schematic view of an account authorization apparatus according to an embodiment of the present application;

FIG. 27 is a schematic view of another account authorization apparatus provided in an 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 Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

As described above, in the prior art, the process of the entrusting transaction is generally performed by a manual entrusting manner or by a separate offline login manner, which results in a large number of entrusting transaction procedures and low transaction efficiency, thereby seriously affecting the transaction amount.

In order to solve the technical problem, the inventive concept of the present application is: the initiator may authorize the initiator's account to one or more recipients' accounts.

It should be understood that the technical solution of the present application can be applied to the following scenarios, but is not limited to: fig. 1 is a diagram of an application scenario provided in an embodiment of the present application, as shown in fig. 1, the application scenario may include an initiator 110, a recipient 120, a server 130, and a 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 the third party 140 through a wired network or a wireless network. In some implementations, the initiator 110 may be a device used by the initiator, and the initiator may authorize its own account to one or more recipients using the initiator 110. In some implementations, the recipient 120 may be a device used by the recipient, who may use the recipient 120 to accept the originator's authorization to his account. In some implementations, an approver, such as an internal compliance approver of dealer transaction software, may approve the authorized agreement signed by the initiator and the acceptor using a third party 140.

In some implementations, the initiator 110, recipient 120, or third party 140 may be, but is not limited to, a cell phone, a tablet, a desktop, a laptop, a handheld computer, a notebook, a vehicle device, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a Personal Digital Assistant (PDA), an Augmented Reality (AR) Virtual Reality (VR) device, and the like. In some implementations, the server 130 may be used to respond to requests by the initiator 110, the recipient 120, or the third party 140. The server 130 may be one server, a server cluster formed by 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, a recipient, a server and a third party, and may actually include other numbers of initiators, recipients, servers and third parties, which is not limited in this application.

After introducing the application scenario of the embodiment of the present application, the following will explain the technical solution of the present application in detail:

fig. 2 is an interaction flowchart of an account authorization method provided in an embodiment of the present application, which may be executed by the initiator 110, the recipient 120, and the third party 140 shown in fig. 1, but is not limited thereto, and as shown in fig. 2, the method may include the following steps:

s201, an initiator acquires account authorization information;

s202, the initiator sends account authorization information to a receiver;

s203, the receiver determines that the receiver signs an authorization protocol corresponding to the account authorization information;

s204, the receiver acquires and displays the authorization protocol;

s205, the receiver acquires the signing operation of the receiver on the authorization agreement;

s206, the receiving party sends the authorization agreement signed by the receiving party to a third party;

s207, the initiator determines an authorization protocol corresponding to the signed account authorization information of the receiver;

s208, the initiator acquires and displays the authorization protocol;

s209, the initiator acquires the signing operation of the initiator on the authorization protocol;

s210, the initiator sends an authorization protocol signed by the initiator to a third party;

s211, the third party obtains the approval operation of the approval personnel on the authorization protocol signed by the receiver and the authorization protocol signed by the initiator.

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

Alternatively, S213: and the third party sends a notification message to the receiver to notify the receiver that the account authorization is successful.

In some implementations, the information interaction between the initiator and the recipient may be forwarded through a 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 implementation, the initiator and the recipient may directly perform information interaction. In short, the information interaction mode between the initiator and the receiver is not limited in the present application.

It should be understood that the embodiments of the present application are described by way of example for an initiator and an acceptor. Of course, one initiator may also authorize multiple accounts of itself to multiple recipients, and one recipient may also accept authorization of multiple accounts of multiple initiators, which is not limited in this application.

Further, when the initiator needs to delegate the recipients, at least two recommendation recipients can be recommended based on the social information of the initiator, and the account information of the recommendation recipients is displayed in the interface. Specifically, the method comprises the following steps: when the receiver is determined to be recommended, acquiring associated account information associated with the initiator, and determining the social association degree between the associated account and the initiator account based on the social information between the two accounts; meanwhile, the account credit degree and the transaction proficiency degree of the associated account are determined based on the associated account information, and then the transaction parameters of the associated account are obtained; and finally, comprehensively determining the associated recommendation degrees corresponding to the associated accounts based on the social association degrees, the account credit degrees and the transaction proficiency degrees, and selecting the associated account with higher associated recommendation degree as a recommendation receiver.

Specifically, in the process of determining the social association degree between the associated account and the initiator account based on the social information between the associated account and the initiator account, first obtaining social information amount Inf (a, B) between the two account acceptors a and the initiator B, wherein the transaction information amount comprises the sum of data amounts of chat communication, web page content corresponding to links, and the like; and simultaneously detecting whether the two accounts are friends or not, if so, detecting whether a friend introduction relationship exists between the accounts, if so, setting the friend parameter Int (A, B) to be 1, and if not, setting the friend parameter Int (A, B) to be 0. Then, the social relevance is determined based on the social information amount Inf (a, B) and the friend parameter Int (a, B) as:

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

wherein a and b are respectively set correlation factors.

In the process of associating the account credit and the transaction proficiency of the account A, the account credit is used for representing the credit Cre _ A of the receiver in the transaction process, and the credit can be directly obtained through a system and is used for reflecting the credit degree of the receiver; the trading proficiency Fic _ a is used to indicate trading capabilities of the recipient such as trading skills, strategies and the like in the trading process, and can be obtained by the following formula in the embodiment:

and further obtaining transaction parameters of the associated account based on the account credit and the transaction proficiency of the associated account A:

wherein k represents the transaction times within a preset time length, and the preset time length comprises one month, one quarter and the like; i represents the transaction identifier of a certain transaction, and pro (i) represents the transaction yield corresponding to the ith transaction.

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

Rec(A,B)＝c·Rea(A,B)+d·Tran_A

wherein c and d are set recommendation factors respectively.

In this embodiment, by recommending the associated account, an objective associated account can be recommended for the initiator based on the account information, the account association degree, the user transaction capacity, and the like, so that the initiator can select a suitable recipient based on the recommended information, and the utilization rate of the transaction information and the objectivity of the recipient selection are improved.

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

In some implementations, as shown in fig. 4, the initiator or the recipient may click on the authorization management icon in all the functional pages of the dealer transaction software to enter the authorization management page for account authorization.

It should be noted that the initiator or the recipient may also enter the authorization management page in other manners, or the initiator or the recipient may enter other pages to perform account authorization operation, which is not limited in this application.

In some implementations, all the functional pages of the dealer trading software may display a multi-account management module for the white-list user, where the multi-account management module may include: an authorization management icon and an apply for multiple accounts icon, but is not so limited.

It should be understood that the present application is not limited to the entire functional page of the dealer trading software, nor is it limited to the modules displayed on the entire functional page and the icons included in each module.

In some implementations, assuming that the initiator does not authorize its own account to any recipient, after the initiator obtains that the initiator clicks the initiate authorization button in the authorization management page, as shown in (a) of fig. 5, the authorization management page may display the authorization that has not been initiated temporarily.

In some implementations, the initiator may obtain a first operation of the initiator on an add authorization button in the authorization management page, in response to which, as shown in (b) of fig. 5, the transaction password input box is displayed.

For example, the first operation may be a single click, a double click, a press, a drag to a designated area, or a hover touch gesture, which is not limited in this application.

In some implementations, the initiator may obtain the transaction password entered by the initiator in the transaction password entry box described above. When the above-mentioned transaction password is correct, as shown in (a) of fig. 6, the initiator displays an add authorization page,

in some implementations, as shown in (b) and (c) of fig. 6, the initiator may obtain account authorization information entered by the initiator in the add authorization page described above.

In some implementations, the account authorization information may include, but is not limited to, at least one of: recipient account number, authorized account, transaction authority, funding authority, and the like.

Illustratively, the recipient account number may be a six digit number. The authorized account may be a cash account for a share or a financing instrument account for a share. The transaction rights may include: a certain stock, a certain stock option, a certain stock derivative, a certain stock option, a certain stock low price, a certain stock sold empty, etc. The funding authority may include: fund transfers, currency exchanges, and the like.

In other implementations, for an authorized account that is a financing account, the sponsor may set a corresponding financable limit, but may not exceed the maximum limit set by the sponsor. For example, as shown in fig. 7, the account authorization information may further include: upper limit of financable amount, highest upper limit, etc.

In some implementations, as shown in fig. 6 (c) or fig. 7, the initiator may acquire a second operation of the initiator on the add next button in the authorization page, and in response to the second operation, as shown in fig. 8 (a), the initiator may display an authorization information confirmation page.

It should be understood that the second operation is similar to the first operation described above and will not be described in detail herein.

For example, the authorization information confirmation page may include: account authorization information, a consent authorization identifier, and an initiate authorization button, etc., but is not limited thereto. For example, the consent authorization identification may include: "the above authorization contents are confirmed without error" and "i agree to disclose personal real name information to the other party".

In some implementations, the initiator may acquire a selection operation of the initiator to agree to the authorization identifier in the authorization information confirmation page and a third operation of the initiation authorization button, and in response to the selection operation and the third operation, as shown in (b) of fig. 8, display the transaction password input box. The third operation is similar to the first operation, and is not described in detail herein.

For example, the order of the numbers in the transaction password input box may be dynamically changed. As can be seen from comparing (b) in fig. 8 with (b) in fig. 5, the order of the numbers in the transaction password input box is different, which can improve security and privacy when the transaction password is input.

In some implementations, the initiator may obtain the transaction password input by the initiator in the transaction password input box, and when the transaction password is correct, the initiator may send the account authorization information to the recipient.

In some implementations, when the transaction password is correct, as shown in (c) of fig. 8, the initiator may display the sent authorization, and may see that the current authorization status is waiting for the recipient to accept the authorization.

In some implementations, assuming that the recipient has not successfully accepted any account authorization, after the recipient obtains that the recipient clicks the accepted authorization button in the authorization management page, as shown in fig. 9, the authorization management page displays the temporarily-accepted authorization.

In some implementations, the recipient can obtain a fifteenth operation of the recipient on an authorization record button in the authorization management page in response to the fifteenth operation to display the authorization record page. The fifteenth operation is similar to the first operation, and is not described in detail herein.

In some implementations, the recipient may obtain a sixteenth operation of the recipient on the acceptance record in the authorization record page, in response to which, as shown in (a) of fig. 10, the recipient displays the authorization record accepted by the recipient. The sixteenth operation is similar to the first operation, and is not described in detail herein.

Illustratively, the authorization record accepted by the recipient may include: account authorization information and a status toggle button. The state switching button may be a small dot icon located after the authorization state in the account authorization information, and the application does not limit the position, color, shape, and the like of the state switching button. For example: as shown in fig. 10(a), the authorization status here is: the small dot diagram after it is marked as a state switch button to receive authorization.

In some implementations, the recipient may also check whether the authorization record button has a prompt tab before obtaining the fifteenth operation of the recipient on the authorization record button in the authorization management page. And if the authorization record button is provided with the prompt tag, the receiver acquires the fifteenth operation of the receiver on the authorization record button.

Illustratively, as shown in fig. 9, the prompt tab may be identified by circle 1 in the upper right corner of the authorization record button, indicating that there is an authorization record at this time. The application does not limit the position, color, shape, etc. of the prompt tag.

In some realizations, the recipient may acquire a thirteenth operation of the recipient's status switch button for the account authorization information, in response to which, as shown in (b) of fig. 10, the authorization information confirmation page is displayed. Wherein, the authorization information confirmation page may include: account authorization information, consent authorization identifier, and accept button, but is not limited thereto. For example, the consent authorization identification may include: "the above authorization contents are confirmed without error" and "i agree to disclose personal real name information to the other party". In addition, the thirteenth operation is similar to the first operation described above, and is not described here again.

In some implementations, the recipient may obtain a selection operation of the consent authorization identifier and a fourteenth operation of the accept button by the recipient, as shown in (c) of fig. 10, to display the transaction password input box. The fourteenth operation is similar to the first operation, and is not described herein again.

In some implementation manners, the receiver may obtain the transaction password input by the receiver in the transaction password input box, and if the transaction password is correct, the receiver may determine that the receiver signs an authorization protocol corresponding to the account authorization information.

In some implementations, 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.

For example, as shown in (a) of fig. 11, the recipient displaying a page of the authorization protocol may include: i have read and signed the third party security account authorization book button and the sign button, but are not so limited.

In some implementations, after the recipient obtains the operations of the two buttons by the recipient, as shown in (b) of fig. 11, the recipient may display an agreement signing page on which the recipient may perform signing operations for the authorized agreement. The operation of the two buttons by the recipient may be selection, clicking, pressing, and the like, which is not limited in the present application.

Illustratively, as shown in (b) of fig. 11, the agreement signing page may include: the button is rewritten. The receiver can re-acquire the signing operation of the receiver on the authorization agreement after acquiring the clicking operation of the receiver on the rewrite button.

In some implementations, as shown in (b) of fig. 11, the agreement signing page may include: a submit button. The recipient can obtain the authorization agreement signed by the third party after clicking the submission button by the recipient.

In some implementations, as shown in (c) of fig. 11, after the recipient obtains the click operation of the submit button by the recipient, the recipient may display that the authorization has been accepted, and the current authorization status is waiting for the originator to sign the agreement.

In some implementations, as shown in fig. 12, the initiator may obtain a fourth operation of the initiator on the authorization record button in the authorization management page, and in response to the fourth operation, display the authorization record page. The fourth operation is similar to the first operation, and is not described in detail herein.

In some implementations, the initiator may obtain a fifth operation of the initiator on initiating the record in the authorization record page, and in response to the fifth operation, as shown in (a) of fig. 13, display the authorization record initiated by the initiator. The fifth operation is similar to the first operation, and is not described in detail herein.

For example, the record of authorization initiated by the initiator may include: account authorization information. The account authorization information may include: an authorization status. The authorization status may represent an authorization status of a current account authorization, which may also be referred to as status information.

In some implementations, if the status information is a to-be-signed agreement status, the initiator may determine that the recipient has signed an authorization agreement corresponding to the account authorization information.

In some implementations, before obtaining the fourth operation of the initiator on the authorization record button in the authorization management page, the initiator may also check whether the authorization record button has a prompt tag. And if the authorization record button is provided with a prompt tag, the initiator acquires the fourth operation of the initiator on the authorization record button.

Illustratively, as shown in fig. 12, the prompt tab may be identified by circle 1 in the upper right corner of the authorization record button, indicating that there is an authorization record at this time. The application does not limit the position, color, shape, etc. of the prompt tag.

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

For example, as shown in (a) of fig. 13, the status switching button may be a small dot icon located after the authorization status in the account authorization information, and the application does not limit the position, color, shape, and the like of the status switching button.

In some implementations, the initiator may obtain a sixth operation of the above-described status switch button by the initiator, and in response to the sixth operation, as shown in (b) of fig. 13, display the sign-up agreement page. The sixth operation is similar to the first operation, and is not described herein again.

Illustratively, as shown in (b) of fig. 13, the above signing agreement page may include: sign agreement button, but is not so limited.

In some implementations, the initiator may acquire a seventh operation of the initiator on the sign-up agreement button in the sign-up agreement page described above, and in response to the seventh operation, the initiator may display a transaction password input box, as shown in (c) of fig. 13.

In some implementations, when the initiator obtains that the transaction password entered by the initiator in the transaction password entry box is correct, the initiator may display the authorization protocol, as shown in (a) of fig. 14.

In some implementations, as shown in (a) and (b) of fig. 14, the signing operation of the initiator obtaining initiator on the authorization agreement is similar to the signing operation of the recipient obtaining recipient on the authorization agreement, and the details are not repeated herein.

In some implementations, as shown in (c) of fig. 14, after obtaining the signing operation of the initiator on the authorized agreement, the initiator can sign an agreement page, which can display the current authorization status as signed agreement.

In some implementations, the sign-up agreement page can also display an authorization record button, as shown in fig. 14 (c). When the initiator acquires the click operation for the authorization record, an authorization record page as shown in fig. 15 may be triggered and displayed, where the page may include an authorization revocation button, and when the initiator acquires the click operation for the authorization revocation button, the account authorization corresponding to the account authorization information is revoked in response to the click operation.

In some implementations, the approver can approve the authorization agreement signed by the initiator and the authorization agreement signed by the recipient, such as: but not limited to, checking account authorization information sent by the initiator, checking the identity of the recipient, and the like.

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

In some implementations, after the account authorization information is successfully authorized, the initiator may obtain an eighth operation of the initiator on an authorization record button in the authorization management page, and respond to the eighth operation to display the authorization record page. The eighth operation is similar to the first operation, and is not described herein again.

In some implementations, the initiator may obtain a ninth operation of the initiator on initiating the record in the authorization record page, and in response to the ninth operation, as shown in (a) of fig. 16, display the authorization record corresponding to the account authorization information. The ninth operation is similar to the first operation, and is not described herein again.

In some implementations, the initiator may obtain a tenth operation of the initiator on the authorization record corresponding to the account authorization information, and in response to the tenth operation, as shown in (b) of fig. 16, display a detailed page of the authorization record corresponding to the account authorization information. The tenth operation is similar to the first operation, and is not described herein again.

In some implementations, after the account authorization information is successfully authorized, the recipient may obtain a seventeenth operation of the recipient on an authorization record button in the authorization management page, and respond to the seventeenth operation to display the authorization record page. The eighteenth operation is similar to the first operation, and is not described herein again.

In some implementations, the recipient may obtain an eighteenth operation of the recipient on the acceptance record in the authorization record page, and in response to the eighteenth operation, as shown in (a) of fig. 17, display the authorization record corresponding to the account authorization information. The ninth operation is similar to the first operation, and is not described herein again.

In some implementations, the recipient may obtain a nineteenth operation of the recipient on the authorization record corresponding to the account authorization information, and in response to the nineteenth operation, as shown in (b) in fig. 17, a detailed page of the authorization record corresponding to the account authorization information is displayed. The nineteenth operation is similar to the first operation, and is not described herein again.

In some implementations, the third party sending the notification message to the originator or the recipient may be a notification message in at least one of the following forms, but is not limited to: voice and text.

In some implementations, the authorization record page can present authorization records for a plurality of authorization states, for example, the authorization states of the authorization records that can be displayed include: the other party to be authorized accepts the authorization, the agreement to be signed, the system is audited, the authorization is successful, the authorization is released, the authorization is withdrawn, the other party is rejected, etc., but is not limited to this.

For example, as shown in fig. 18, the initiation record in the authorization record page is taken as an example, and a part of the authorization record is shown, but not limited thereto. The content displayed by the receiving record in the authorization record page is also similar, and the details are not repeated herein.

In some implementations, as shown in fig. 18, the initiator may obtain a filtering operation of the initiator on all account buttons, or all status buttons below the initiation record in the authorization record page, and in response to the filtering operation, the initiator may display the filtered authorization record. Of course, the operation of filtering the acceptance record in the authorization record page is also similar, and the details of the application are not further described herein.

In some implementations, as shown in (a), (b), and (c) of fig. 19, there are filtering operations on the all account number button, the all account button, and the all status button, respectively. All accounts, and all statuses may generally be selected by default. The initiator or recipient may also display the filtered authorization records in the order of filtering.

In some implementations, as shown in fig. 20 (a), the initiator may display all account authorization information that has initiated authorization and that authorization is successful in an initiated authorization page in the authorization management page.

In other implementations, as shown in fig. 20 (b), the recipient may display all account authorization information that has accepted authorization and authorization is successful in an authorization page accepted in the authorization management page.

In some implementation manners, the initiator or the recipient may screen the displayed account of the authorization management interface, and the screening method is similar to the method for screening the initiation record or the acceptance record in the authorization record, and is not described herein again.

In some implementations, as shown in (a), (b), and (c) of fig. 21, the initiator may tag the successfully authorized account with an authorization ticket. For example, the authorization tag may be a right-facing arrow located behind the originating authorization account, and the application does not limit the location, shape, color, etc. of the authorization tag.

In some implementations, the initiator may also distinguish whether the authorized account is initiated or accepted by the arrow color, such as: the arrow color orange indicates that the authorized account is the originating account.

In some implementations, as shown in fig. 22 (a), (b), and (c), the recipient can tag the successfully authorized account with an authorization ticket. For example, the authorization tag may be a left-facing arrow located behind the accepted authorization account, and the application does not limit the location, shape, color, etc. of the authorization tag.

In some implementations, the recipient may also distinguish whether the authorized account is accepted or initiated by an arrow color, such as: the arrow color blue indicates that the authorized account is an accepted account.

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

In some implementations, the initiator may obtain an eleventh operation of the de-authorization button by the initiator, and in response to the eleventh operation, remove the authorization corresponding to the account authorization information. The eleventh operation is similar to the first operation, and is not described herein again.

For example, as shown in (b) of fig. 23, the originator may respond to the click operation to display "will revoke not revoke, determine to revoke? "in the popup, after the initiator acquires the click operation of the release button by the initiator in the popup, the transaction password input box is displayed as shown in fig. 23 (c). And when the initiator acquires the correct transaction password input by the initiator in the transaction password input box, successfully removing the authorization corresponding to the account authorization information.

In some implementations, after successfully removing the authorization corresponding to the account authorization information, as shown in fig. 24, the initiator may display the removed authorization record on the authorization record page.

In some implementations, after the account information is successfully authorized, as shown in fig. 25 (a), the detailed page of the authorization record corresponding to the account authorization information displayed on the initiator may include: the authorization button is modified.

In some implementations, the initiator may obtain a twelfth operation of the initiator on the modify authorization button, and modify the authorization corresponding to the account authorization information in response to the twelfth operation. The twelfth operation is similar to the first operation, and is not described herein again.

For example, as shown in fig. 25 (b), the initiator may respond to the click operation to display the transaction password input box after acquiring the click operation of the initiator on the modification authorization button. When the initiator obtains the correct transaction password input by the initiator in the merchant transaction password input box, the authorization information modification page is displayed as shown in fig. 25 (c), and the initiator can obtain the modification of the account authorization information by the initiator.

After account authorization is performed in the above manner, the recipient may obtain account information of the initiator, such as an account type, an account balance, and the like. The recipient may then conduct transactions, such as stock transactions, fund transactions, and the like, in the initiator's account on behalf of the initiator's authorization based on the initiator's account information. Meanwhile, the transaction record and the updated account information are uploaded to the cloud and synchronized to the terminal account of the initiator, and the initiator can acquire the transaction record and the updated account information from the account of the initiator. By the method, data synchronism, transparency and safety in the entrusted transaction process are improved.

To sum up, the technical scheme provided by the above embodiment at least brings the following beneficial effects: on one hand, the method for flow account authorization with better usability is provided, the initiator can acquire and send account authorization information of the initiator to the receiver, the receiver can acquire the account authorization information, when an authorization agreement corresponding to the account authorization information is confirmed to be signed, the authorization agreement can be acquired, and then the receiver can send the authorization agreement signed by the receiver to a third party. The initiator can also sign the authorization agreement after determining that the receiver signs the authorization agreement corresponding to the account authorization information, and send the authorization agreement signed by the initiator to the third party. After the third party obtains the authorization agreement signed by the initiator and the receiver, the authorization agreement can be approved, and after the approval is passed, account authorization can be realized. Therefore, the problem that the prior art does not support account authorization is solved.

On the other hand, in the steps of acquiring and sending account authorization information, signing an authorization protocol, canceling, modifying, withdrawing authorization and the like, the initiator and the receiver can display the transaction password input box, and the steps can be successfully performed only when the correct transaction password input in the transaction password input box is acquired, so that the security of account authorization is improved.

On the other hand, the authorization label can be added to the successfully authorized account, so that the authorization states of different accounts can be conveniently distinguished, and the user experience is improved.

Fig. 26 is a schematic diagram of an account authorization apparatus according to an embodiment of the present application, where the account authorization apparatus may be, but is not limited to, the initiator 110 shown in fig. 1, and as shown in fig. 26, the account authorization apparatus includes:

a first obtaining module 2601, configured to obtain account authorization information;

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

a determining module 2603, configured to determine an authorization protocol corresponding to the signed account authorization information of the recipient;

a second obtaining module 2604, configured to obtain an authorization protocol;

a first display module 2605 for displaying the authorization protocol;

a third obtaining module 2606, configured to obtain a signing operation of the initiator on the authorization agreement;

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

In some implementations, the first obtaining module 2601 is specifically configured to: acquiring a first operation of adding an authorization button in an authorization management page; responding to the first operation to display a transaction password input box; acquiring a transaction password input in a transaction password input box; when the transaction password is correct, displaying an adding authorization page; and acquiring account authorization information input in the adding authorization page.

In some implementations, the first sending module 2602 is specifically configured to: acquiring a second operation of a next step button for adding the authorization page; responding to the second operation to display an authorization information confirmation page, wherein the authorization information confirmation page comprises: account authorization information, an authorization approval identifier and an authorization initiating button; acquiring a selection operation of an agreement authorization identifier and a third operation of an initiation authorization button; responding to the selection operation and the third operation to display a transaction password input box; acquiring a transaction password input in a transaction password input box; and when the transaction password is correct, sending account authorization information to the receiver.

In some implementations, the determining module 2603 is specifically configured to: acquiring a fourth operation on an authorization record button in the authorization management page; responding to a fourth operation to display an authorization record page; acquiring a fifth operation of initiating recording in the authorization recording page; responding to a fifth operation to display an authorization record initiated by the initiator, wherein the authorization record initiated by the initiator comprises account authorization information; determining the state information of account authorization information; and if the state information is the state of the agreement to be signed, determining that the receiver signs the authorization agreement corresponding to the account authorization information.

In some implementations, the account authorization apparatus further includes: a view module 2608 checks to see if there is a reminder tab on the authorization record button. If the authorization record button has a prompt tag, the determining module 2603 is specifically configured to obtain a fourth operation on the authorization record button.

In some implementations, the authorization record initiated by the initiator further includes a status switch button corresponding to the account authorization information. The first display module 2605 is specifically configured to: acquiring a sixth operation on the state switching button; responding to a sixth operation to display a signing agreement page; acquiring a seventh operation on a signing agreement button in the signing agreement page; in response to a seventh operation, displaying the signed agreement.

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

It should be understood that the apparatus embodiment and the method embodiment of the initiator side may correspond to each other, and similar descriptions may refer to the method embodiment corresponding to the initiator. To avoid repetition, further description is omitted here.

Specifically, the account authorization apparatus shown in fig. 26 may execute the method embodiment on the initiator side, and the foregoing and other operations and/or functions of each module in the account authorization apparatus shown in fig. 26 are respectively for implementing the corresponding flow of the method embodiment on the initiator side, and are not repeated herein for brevity.

The above-described originating-side method embodiment of the present application is described above from the perspective of the functional module in conjunction with the drawings. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in conjunction with the embodiments in the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps in the above method embodiments in combination with hardware thereof.

Fig. 27 is a schematic diagram of an account authorization apparatus according to an embodiment of the present application, where the account authorization apparatus may be the receiving party 120 shown in fig. 1, and the account authorization apparatus includes:

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

a determining module 2702, configured to determine an authorization protocol corresponding to the signed account authorization information;

a first obtaining module 2703, configured to obtain an authorization protocol;

a first display module 2704, configured to display an authorization protocol;

a second obtaining module 2705, configured to obtain a signing operation of the recipient on the authorization agreement;

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

In some implementations, the determining module 2702 is specifically configured to: a thirteenth operation of acquiring a state switching button for account authorization information; responding to a thirteenth operation to display an authorization information confirmation page, wherein the authorization information confirmation page comprises: account authorization information and an accept button; acquiring a fourteenth operation on the acceptance button; responding to a fourteenth operation to display a transaction password input box; acquiring a transaction password input in a transaction password input box; and if the transaction password is correct, determining an authorization protocol corresponding to the signed account authorization information.

In some implementations, the account authorization apparatus further includes: a third acquisition module 2707, a second display module 2708, a fourth acquisition module 2709, and a third display module 2710. The third obtaining module 2707 is configured to obtain a fifteenth operation on an authorization record button in the authorization management page; the second display module 2708 is configured to respond to the fifteenth operation to display an authorization record page; the fourth obtaining module 2709 is configured to obtain a sixteenth operation on an acceptance record in the authorization record page; the third display module 2710 is configured to respond to the sixteenth operation to display the authorization record accepted by the recipient, where the authorization record accepted by the recipient includes account authorization information and a status switching button.

In some implementations, the account authorization apparatus further includes: view module 2711. The view module 2711 is configured to view whether the authorization record button has a reminder tag thereon. The third obtaining module 2707 is specifically configured to, if the authorization record button has a prompt tag, obtain a fifteenth operation on the authorization record button.

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

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. To avoid repetition, further description is omitted here.

Specifically, the account authorization apparatus shown in fig. 27 may execute the method embodiment on the receiving side, and the foregoing and other operations and/or functions of each module in the account authorization apparatus shown in fig. 27 are respectively for implementing corresponding flows of the method embodiment on the receiving side, and are not described herein again for brevity.

The above-described method embodiments of the receiving side of the embodiments of the present application are described above from the perspective of the functional module in conjunction with the drawings. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in conjunction with the embodiments in the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps in the above method embodiments in combination with hardware thereof.

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 a recipient in this application.

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

a memory 2810 and a processor 2820, the memory 2810 being configured to store computer programs and to transfer the program codes to the processor 2820. In other words, the processor 2820 may call and execute a computer program from the memory 2810 to implement the method in the embodiment of the present application.

For example, the processor 2820 may be configured to perform the above-described method embodiments according to instructions in the computer program.

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

general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

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

volatile memory and/or non-volatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

In some embodiments of the present application, the computer program may be divided into one or more modules, which are stored in the memory 2810 and executed by the processor 2820 to perform the methods provided herein. The one or more modules may be a series of computer program instruction segments capable of performing certain functions, the instruction segments describing the execution of the computer program in the electronic device.

As shown in fig. 28, the electronic apparatus may further include:

a transceiver 2830, the transceiver 2830 being connectable to the processor 2820 or the memory 2810.

The processor 2820 may control the transceiver 2830 to communicate with other devices, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices. The transceiver 2830 may include a transmitter and a receiver. The transceiver 2830 may further include one or more antennas.

It should be understood that the various components in the electronic device are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

The present application also provides a computer storage medium having stored thereon a computer program which, when executed by a computer, enables the computer to perform the method of the above-described method embodiments.

Embodiments of the present application also provide a computer program product containing instructions, which when executed by a computer, cause the computer to perform the method of the above method embodiments.

When implemented in software, 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. The procedures or functions described in accordance with the embodiments of the present application occur, in whole or in part, when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An account authorization method, comprising:

acquiring account authorization information;

sending the account authorization information to a receiver;

determining that the receiver signs an authorization protocol corresponding to the account authorization information;

acquiring and displaying the authorization protocol;

acquiring signing operation of an initiator on the authorization protocol;

sending the authorization agreement signed by the initiator to a third party.

2. The method of claim 1, wherein obtaining account authorization information comprises:

acquiring a first operation of adding an authorization button in an authorization management page;

responding to the first operation to display a transaction password input box;

acquiring the transaction password input in the transaction password input box;

when the transaction password is correct, displaying an adding authorization page;

and acquiring the account authorization information input in the adding authorization page.

3. The method of claim 2, wherein sending the account authorization information to the recipient comprises:

acquiring a second operation of the next step button of the authorization adding page;

responding to the second operation to display an authorization information confirmation page, wherein the authorization information confirmation page comprises: the account authorization information, the authorization approval identification and the authorization initiating button;

acquiring a selection operation of the consent authorization identifier and a third operation of the initiation authorization button;

responding to the selection operation and the third operation to display a transaction password input box;

acquiring the transaction password input in the transaction password input box;

and when the transaction password is correct, sending the account authorization information to a receiver.

4. The method of claim 2 or 3, wherein the determining that the recipient has signed an authorization agreement corresponding to the account authorization information comprises:

acquiring a fourth operation on an authorization record button in the authorization management page;

responding to the fourth operation to display an authorization record page;

acquiring a fifth operation of initiating recording in the authorization recording page;

responding to the fifth operation to display an authorization record initiated by the initiator, wherein the authorization record initiated by the initiator comprises the account authorization information;

determining status information of the account authorization information;

and if the state information is the protocol state to be signed, determining that the receiver signs the authorization protocol corresponding to the account authorization information.

5. The method of claim 4, wherein prior to the obtaining the fourth operation on the authorization record button in the authorization management page, further comprising:

checking whether a prompt tag is arranged on the authorization record button;

the fourth operation of obtaining an authorization record button in the authorization management page comprises the following steps;

and if the authorization record button is provided with the prompt tag, acquiring the fourth operation of the authorization record button.

6. The method according to claim 4, wherein the authorization record initiated by the initiator further comprises a status switch button corresponding to the account authorization information; displaying the authorization protocol includes:

acquiring a sixth operation on the state switching button;

responding to the sixth operation to display a signing agreement page;

acquiring a seventh operation on a signing agreement button in the signing agreement page;

in response to the seventh operation, displaying the signed agreement.

7. The method of claim 2 or 3, further comprising:

after the account authorization information is successfully authorized, acquiring an eighth operation on an authorization record button in the authorization management page;

responding to the eighth operation to display an authorization record page;

acquiring a ninth operation of initiating record in the authorization record page;

responding to the ninth operation to display an authorization record corresponding to the account authorization information;

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

responding to the tenth operation to display a detailed page of the authorization record corresponding to the account authorization information.

8. An account authorization method, comprising:

receiving account authorization information;

determining an authorization protocol corresponding to the signed account authorization information;

acquiring and displaying the authorization protocol;

acquiring signing operation of a receiver on the authorization agreement;

sending the authorization agreement signed by the recipient to a third party.

9. The method of claim 8, wherein determining to sign the authorization agreement to which the account authorization information corresponds comprises:

acquiring a thirteenth operation of a state switching button of the account authorization information;

responding to the thirteenth operation to display an authorization information confirmation page, wherein the authorization information confirmation page comprises: the account authorization information, the authorization approval identification and the acceptance button;

acquiring a selection operation of the consent authorization identifier and a fourteenth operation of the accept button;

responding to the selection operation and the fourteenth operation to display a transaction password input box;

acquiring the transaction password input in the transaction password input box;

and if the transaction password is correct, determining to sign an authorization protocol corresponding to the account authorization information.

10. The method of claim 9, wherein prior to the thirteenth operation of obtaining the status switch button for the account authorization information, further comprising:

acquiring a fifteenth operation on an authorization record button in the authorization management page;

responding to the fifteenth operation to display an authorization record page;

sixteenth operation of an acceptance record in the authorization record page is obtained;

responding to the sixteenth operation to display the authorization record accepted by the receiver, wherein the authorization record accepted by the receiver comprises the account authorization information and the state switching button.

11. The method of claim 10, wherein prior to the obtaining the fifteenth operation on the authorization record button in the authorization management page, further comprising:

checking whether a prompt tag is arranged on the authorization record button;

the fifteenth operation of obtaining an authorization record button in an authorization management page comprises;

and if the authorization record button is provided with the prompt tag, acquiring a fifteenth operation of the authorization record button.

12. The method of claim 10 or 11, further comprising:

obtaining seventeenth operation of an authorization record button in the authorization management page after the account authorization information is successfully authorized;

responding to the seventeenth operation to display an authorization record page;

acquiring an eighteenth operation of receiving records in the authorization record page;

responding to the eighteenth operation to display an authorization record corresponding to the account authorization information;

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

responding to the nineteenth operation to display a detailed page of the authorization record corresponding to the account authorization information.

13. An account authorization apparatus, comprising:

the first acquisition module is used for acquiring account authorization information;

the first sending module is used for sending the account authorization information to a receiver;

the determining module is used for determining that the receiver signs an authorization protocol corresponding to the account authorization information;

the second acquisition module is used for acquiring the authorization protocol;

the first display module is used for displaying the authorization protocol;

the third acquisition module is used for acquiring signing operation of the initiator on the authorization protocol;

and the second sending module is used for sending the authorization protocol signed by the initiator to a third party.

14. An account authorization apparatus, comprising:

the receiving module is used for receiving account authorization information;

the determining module is used for determining an authorization protocol corresponding to the account authorization information;

the first acquisition module is used for acquiring the authorization protocol;

the first display module is used for displaying the authorization protocol;

the second acquisition module is used for acquiring signing operation of a receiver on the authorization agreement;

and the sending module is used for sending the authorization protocol signed by the receiver to a third party.

15. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the account authorization method of any of claims 1-7 or any of claims 8-12 via execution of the executable instructions.

16. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the account authorization method according to any one of claims 1 to 7 or 8 to 12.

17. A computer program product comprising instructions for causing an electronic device to perform the account authorization method of any one of claims 1-7 or 8-12 when the computer program product is run on the electronic device.