Identity verification method and apparatus

Abstract

The embodiments of the present specification provide identity verification methods and devices, wherein the identity verification method comprises: in the transaction process of a user and a transaction participant, determining whether the user is a user in a lost state in a project by performing identity verification on the user; if so, determining a target participant user in the project that has an identity binding relationship with the user, wherein the target participant user has pre-transaction authorization for the user; and sending identity verification results and transaction result information for the user to at least one of the target participant user and the transaction participant, wherein the transaction result information comprises information generated based on the result of judging the transaction within the transaction authorization range.

Description

[0001] This application is a divisional application of application number 202010383085.1, filed on May 8, 2020, entitled "Identity Verification Method and Apparatus". Technical Field

[0002] This specification relates to the field of Internet technology, and in particular to an identity verification method and apparatus. Background Technology

[0003] With the development of the internet, there are increasingly diverse ways to help users who are out of contact. In real life, special groups such as the elderly, children, or the disabled may lose contact with their families due to their own circumstances or accidents after going out. At the same time, their self-rescue ability is relatively weak. Therefore, when they are out of contact, they need to receive corresponding assistance so that they can be found. However, most of the current assistance methods require the participation of strangers, so there is a need to provide more effective and safer solutions. Summary of the Invention

[0004] In view of this, embodiments of this specification provide an identity verification method. One or more embodiments of this specification also relate to an identity verification device, a computing device, and a computer-readable storage medium, to address the technical deficiencies existing in the prior art.

[0005] A first aspect of the embodiments of this specification provides an identity verification method, including:

[0006] Obtain the user's identity feature image collected during the transaction process by the user and the transaction participants;

[0007] Based on the identity feature image, it is determined whether the user is a project member; the participating users in the project establish an identity binding relationship with the project members by registering their identities, and mark the identity status of the project members;

[0008] If so, if the user is marked as unreachable in the project, identify the target participating user in the project who has an identity binding relationship with the user;

[0009] Send the identity verification result for the user to at least one of the target user and the transaction participants.

[0010] Optionally, if the result of the step of determining whether the user is a project member based on the identity feature image is yes, and before the step of determining the target participating user in the project with an identity binding relationship with the user when the user is marked as unreachable in the project is executed, the method further includes:

[0011] Obtain the transaction information uploaded by the transaction terminals of the transaction participants during the transaction process;

[0012] Determine whether the transaction amount contained in the transaction information is greater than the preset transaction amount threshold in the project;

[0013] If the amount is greater than the first judgment result based on the amount, a first transaction interruption message is generated, and the first transaction interruption message is used as the transaction result message;

[0014] If the value is not greater than the transaction information, the transaction is processed to generate a transaction order, and the order information in the transaction order is used as the transaction result information.

[0015] Optionally, after the step of obtaining the transaction information uploaded by the transaction terminal of the transaction participant during the transaction process is executed, and before the step of determining whether the transaction amount contained in the transaction information is greater than the preset transaction amount threshold in the project is executed, the method further includes:

[0016] Based on the transaction information, determine the transaction scenario type;

[0017] Determine whether there exists a target authorization scenario type that is the same as the scenario type among the preset authorization scenario types for the user in the project;

[0018] If it exists, execute the step of determining whether the transaction amount is less than the preset transaction amount threshold in the project based on the transaction amount contained in the transaction information;

[0019] If it does not exist, based on the second judgment result of the scenario judgment, a second transaction interruption information is generated, and the second transaction interruption information is used as the transaction result information.

[0020] Optionally, sending the identity verification result for the user to at least one of the target participating user and the transaction participants includes:

[0021] Based on the device identifier of the transaction terminal contained in the transaction information, the location information of the transaction terminal and the participant information of the transaction participants are determined;

[0022] Based on the location information, the participant information, and the transaction result information, a request for help is generated for the user.

[0023] Based on the requested assistance information, a request for assistance is sent to the target user regarding the user's loss of contact status.

[0024] Optionally, sending the identity verification result for the user to at least one of the target participating user and the transaction participants includes:

[0025] Obtain the contact information of the target participating users;

[0026] Based on the contact information and the transaction result information, a request for help is generated for the user;

[0027] Based on the requested assistance information, a notification is sent to the transaction terminal regarding the user's loss of contact status.

[0028] Optionally, determining whether the user is a project member based on the identity feature image includes:

[0029] Image recognition is performed on the identity feature image to obtain the user's identity features;

[0030] The identity features are compared with the member features corresponding to the member feature images of the pre-stored project members in the project to obtain the feature similarity.

[0031] The user is determined to be a member of the project by judging whether the feature similarity is greater than a preset similarity threshold.

[0032] Optionally, the registration of project members' identities is achieved in the following way:

[0033] Retrieve member registration requests submitted by participating users;

[0034] The feature image carried in the member registration request is used as the member feature image and stored in the feature image library of the project.

[0035] Based on the identity relationship information carried in the member registration request, the member feature image is bound to the participating user's identity;

[0036] If the identity binding is successful, a registration completion instruction is sent in response to the member registration request.

[0037] Optionally, before the step of obtaining the user's identity feature image collected during the transaction process by the user and the transaction participants, the method further includes:

[0038] Obtain the transaction authorization request submitted by the user in the project;

[0039] Based on the transaction authorization information submitted for the transaction authorization options carried in the transaction authorization request, a transaction authorization agreement is generated in which the target participating user authorizes the user to make a transaction; the transaction authorization agreement includes at least one authorization scenario type and / or transaction amount threshold authorized by the target participating user to the user;

[0040] Based on the transaction authorization protocol, an authorization completion instruction is sent for the transaction authorization request.

[0041] Optionally, in the case that the user is a child, sending the identity verification result for the user to at least one of the target participating user and the transaction participants includes:

[0042] Obtain the contact information of the target participating user, and determine the location information of the transaction terminal and the participant information of the transaction participant based on the device identifier of the transaction terminal contained in the transaction information;

[0043] Based on the contact information, location information, participant information, and transaction result information, a request for help is generated for the child.

[0044] Based on the requested assistance information, a request for assistance regarding the child's loss of contact is sent to the transaction terminal and the target participating user.

[0045] Optionally, the identity feature image includes at least one of the following: a face image, an iris image, and a fingerprint image.

[0046] A second aspect of the embodiments of this specification provides an identity verification device, including:

[0047] The acquisition module is configured to acquire the user's identity feature image collected by the user and transaction participants during the transaction process;

[0048] The judgment module is configured to determine whether the user is a project member based on the identity feature image; the participating users in the project establish an identity binding relationship with the project members by registering their identities and marking the identity status of the project members.

[0049] If so, run the determination module, which is configured to determine the target participating users in the project who have an identity binding relationship with the user when the user is marked as unreachable in the project;

[0050] The sending module is configured to send the identity verification result for the user to at least one of the target participating user and the transaction participants.

[0051] A third aspect of the embodiments of this specification provides a computing device, including:

[0052] Memory and processor;

[0053] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions:

[0054] Obtain the user's identity feature image collected during the transaction process by the user and the transaction participants;

[0055] Based on the identity feature image, it is determined whether the user is a project member; the participating users in the project establish an identity binding relationship with the project members by registering their identities, and mark the identity status of the project members;

[0056] If so, if the user is marked as unreachable in the project, identify the target participating user in the project who has an identity binding relationship with the user;

[0057] Send the identity verification result for the user to at least one of the target user and the transaction participants.

[0058] A fourth aspect of the embodiments of this specification provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the identity verification method.

[0059] This specification provides an identity verification method. By acquiring the user's identity feature image collected during the transaction process between the user and the transaction participants, the method identifies the user and determines whether the user is a project member. If the user is a project member, it further determines whether the user is marked as unreachable within the project. This achieves identity verification of whether the user is unreachable during the transaction process. If the user is marked as unreachable, the method identifies a target participating user with an identity binding relationship with the user in the project and sends the identity verification result for the user to at least one of the target participating user and the transaction participants. This allows the target participating user and / or the transaction participants to track the unreachable user based on the user's transactions, and enables the unreachable user to enjoy transaction services and thus obtain material assistance. Attached Figure Description

[0060] Figure 1 This is a flowchart illustrating an identity verification method provided in one embodiment of this specification.

[0061] Figure 2This is a flowchart illustrating an identity verification method applied in a facial recognition payment scenario, provided by one embodiment of this specification.

[0062] Figure 3 This is a schematic diagram of an identity verification device provided in one embodiment of this specification;

[0063] Figure 4 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0064] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0065] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0066] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0067] This specification provides an identity verification method. One or more embodiments of this specification also relate to an identity verification device, a computing device, and a computer-readable storage medium, which will be described in detail in the following embodiments.

[0068] The following is an example of an identity verification method provided in this specification:

[0069] Figure 1 A flowchart of an identity verification method according to an embodiment of this specification is shown, including steps S102 to S108.

[0070] Step S102: Obtain the user's identity feature image collected by the user and transaction participants during the transaction process.

[0071] In practical applications, special groups such as the elderly, children, or disabled people may lose contact with their families after going out due to their own circumstances or accidents. At the same time, their self-rescue ability is weak. Therefore, when they are out of contact, they need to receive corresponding assistance so that they can be found. However, most current assistance methods rely on the involvement of strangers. In the embodiments of this specification, during the transaction process, the user's identity is verified to determine whether the user is out of contact. If the user is out of contact, effective and safe assistance is provided to them.

[0072] Specifically, the user refers to the buyer in the transaction process, and the transaction participant refers to the merchant with a physical store. In the transaction process between the buyer and the merchant, such as during the payment process, it is necessary to collect the buyer's identity feature image to identify the buyer. If the identity is successfully identified, the payment is made by obtaining the buyer's associated account information.

[0073] Optionally, the identity feature image includes at least one of the following: a face image, an iris image, and a fingerprint image. Any one of these identity feature images can uniquely identify a user without requiring the user to provide additional information, simplifying the payment process and enabling users to make payments even when they cannot use a mobile terminal or have forgotten key information. In addition, other uniquely identifying features of the user can be collected to identify the user and complete the payment, such as voiceprint features, etc., without limitation.

[0074] For example, after user u selects bottled water at a convenience store, they make a facial recognition payment payment using a facial recognition payment device. The price of the bottled water p1, the merchant code c1, and the device code d1 of the facial recognition payment device are used as purchase information. The facial image of user u collected by the facial recognition payment device and the purchase information are then uploaded to the server.

[0075] Step S104: Determine whether the user is a project member of the project based on the identity feature image.

[0076] Based on the user's identity feature image obtained above, the user's identity is identified to determine whether the user is a project member in the project.

[0077] Specifically, participating users in the project establish an identity binding relationship with project members by registering their identities and marking the identity status of project members.

[0078] The project refers to a project that can verify the identity of users and provide assistance to users who are out of contact. The participating users refer to the users who participate in the aforementioned project. In actual application, participating users register their close relatives, such as the elderly, children or disabled persons, in the project to become project members, so that relatives can provide assistance to their relatives in the process of transactions if they are out of contact.

[0079] The project members refer to those who participate in the project through identity registration. This allows project members to obtain the necessary items and receive corresponding assistance even when they are out of contact.

[0080] Based on the acquired user identity feature image, user identification is performed to determine whether the user is a project member. Specifically, this is done by comparing the collected user identity feature image with pre-stored member feature images in the project. The similarity comparison result determines whether the user is a project member, avoiding the need for users to actively provide identity information. This improves the user's project experience and ensures user information security. In one optional implementation provided in this specification, the determination of whether the user is a project member based on the identity feature image is implemented in the following way:

[0081] Image recognition is performed on the identity feature image to obtain the user's identity features;

[0082] The identity features are compared with the member features corresponding to the member feature images of the pre-stored project members in the project to obtain the feature similarity.

[0083] The user is determined to be a member of the project by judging whether the feature similarity is greater than a preset similarity threshold.

[0084] In practice, image recognition of identity feature images refers to identifying the user's identity features in the identity feature images. After the image recognition is completed, the user's identity features are obtained. The identified user's identity features are then compared with the member features of the pre-stored member feature images of project members in the project to obtain the feature similarity. Specifically, the feature similarity can be expressed as a percentage value (0%-100%). The higher the percentage value, the higher the similarity, that is, the greater the probability that the user is a member of the project.

[0085] In practical applications, based on past comparison experience, a similarity threshold is preset in the project. If the feature similarity is greater than the preset similarity threshold, it indicates that the user is likely to be a member of the project. In this case, the user is confirmed as a member of the project, and the following step S106 is executed. If the feature similarity is not greater than the preset similarity threshold, it indicates that the user is unlikely to be a member of the project. In this case, the user's identity image features can be re-collected, or the user can be directly determined not to be a member of the project. No restrictions are imposed here.

[0086] Using the previous example, after receiving the facial image of user u uploaded by the facial recognition payment device, the server performs facial recognition on the image to obtain user u's facial features. Then, it compares user u's facial features with the facial features of pre-stored members in the project for similarity. If the obtained feature similarity is 95%, and the preset similarity threshold is 90%, then the feature similarity is greater than the preset similarity threshold, indicating that user u has a high probability of being a member of the project. Therefore, user u is determined to be a member of the project.

[0087] In practical implementation, participating users in the project need to register the identities of project members. This requires pre-storing the member feature images and binding project members to participating users for identity verification. Based on the identity verification results, assistance is requested from the participating users whose identities are bound to the project members. In one optional implementation provided in this specification, the registration of project members' identities is specifically achieved in the following way:

[0088] Retrieve member registration requests submitted by participating users;

[0089] The feature image carried in the member registration request is used as the member feature image and stored in the feature image library of the project.

[0090] Based on the identity relationship information carried in the member registration request, the member feature image is bound to the participating user's identity;

[0091] If the identity binding is successful, a registration completion instruction is sent in response to the member registration request.

[0092] In practical applications, participating users submit member registration requests to the server by operating the client. During the process of participating users registering their identities as project members, they need to submit the feature images of the project members. These feature images can be collected during the identity registration process through image acquisition, or they can be actively uploaded by the participating users. There are no restrictions on this.

[0093] In addition, during the registration process for project members, it is also necessary to submit the relationship information between the project members and the participating users, such as son, daughter, father, mother, etc. The project members are bound to the participating users by binding their identity information with the member's feature image. There are various ways to bind the identity, such as establishing an identity binding relationship table or adding binding tags, etc., which are not limited here.

[0094] After storing the member feature image carried in the member registration request and binding the member feature image with the identity of the participating user, the identity registration of the project member is completed, and a registration completion instruction is sent for the member registration request.

[0095] Furthermore, in addition to registering the identities of participating users for project members, it is also necessary to authorize transactions for project members so that they can conduct transactions within the scope of the participating users' authorization, thereby protecting the resource security of participating users. In an optional implementation provided in this specification, before the step of obtaining the user's identity feature image collected during the transaction process is executed, the method further includes:

[0096] Obtain the transaction authorization request submitted by the user in the project;

[0097] Based on the transaction authorization information submitted for the transaction authorization options carried in the transaction authorization request, a transaction authorization agreement is generated in which the target participating user authorizes the user to make a transaction; the transaction authorization agreement includes at least one authorization scenario type and / or transaction amount threshold authorized by the target participating user to the user;

[0098] Based on the transaction authorization protocol, an authorization completion instruction is sent for the transaction authorization request.

[0099] In practical applications, in addition to submitting a member registration request to the server by operating the client as mentioned above, participating users can also select transaction authorization options and submit a transaction authorization request by operating the client. After receiving the submitted transaction authorization request, the server generates a transaction authorization agreement based on the transaction authorization information carried in the transaction authorization request.

[0100] Specifically, the transaction authorization agreement includes at least one type of authorization scenario and / or a transaction amount threshold authorized by the target participating user to the user. The type of authorization scenario refers to the type of physical store of the merchant, such as supermarket, convenience store, restaurant, clothing store, etc. The transaction amount threshold refers to the maximum amount of a single authorized consumption by the user. In addition, the transaction authorization agreement may also include the authorizing account that authorizes the user to make the transaction. The target participating user refers to a participating user who has an identity binding relationship with the user in the project.

[0101] It should be noted that due to the specific nature of the user group, users may not have activated online payment channels. Therefore, when a user is a project member, the user uses the transaction account of the target participating user whose identity is linked to the user to conduct transactions. During the transaction process, the user is subject to the transaction authorization granted by the target participating user to prevent the user from making irrational consumption and causing losses to the target participating user.

[0102] Furthermore, based on the determination that the user is a project member of the project and the result is yes, according to the transaction information uploaded by the transaction terminals of the transaction participants during the transaction process, it is determined whether the transaction meets the preset transaction conditions in the project, that is, whether the transaction meets the authorization conditions contained in the transaction authorization agreement. If it meets the conditions, it indicates that the transaction is permitted, and the corresponding transaction processing is performed according to the transaction information. If it does not meet the conditions, it indicates that the transaction is not permitted, and the transaction is interrupted, thereby further ensuring the security of the transaction. In an optional implementation provided by the embodiments of this specification, if the determination result of the step of determining whether the user is a project member of the project based on the identity feature image is yes, and before the step of determining the target participating user in the project with an identity binding relationship with the user when the user is marked as unreachable in the project is executed, it further includes:

[0103] Obtain the transaction information uploaded by the transaction terminals of the transaction participants during the transaction process;

[0104] Determine whether the transaction amount contained in the transaction information is greater than the preset transaction amount threshold in the project;

[0105] If it is greater than, it indicates that the transaction amount exceeds the authorized amount. Based on the first judgment result of the amount judgment, the first transaction interruption information is generated and the first transaction interruption information is used as the transaction result information.

[0106] If the amount is not greater than the authorized amount, it indicates that the transaction amount does not exceed the authorized amount. Based on the transaction information, the transaction is processed, a transaction order is generated, and the order information in the transaction order is used as the transaction result information.

[0107] Specifically, a transaction terminal refers to a transaction device that uses biometric data for identity verification and conducts transactions based on that verification, such as a facial recognition payment device; the transaction amount refers to the amount of the transaction in the aforementioned transaction process.

[0108] The transaction processing based on transaction information refers to obtaining the transaction account of the target user whose identity is bound to the user, as well as the transaction account of the transaction participant, based on the identification information of both parties contained in the transaction information, and completing the transaction transfer from the transaction account of the target user to the transaction account of the transaction participant according to the transaction amount contained in the transaction information, thereby generating a transaction order.

[0109] The first judgment result refers to the transaction amount being greater than the preset transaction amount threshold in the project; correspondingly, the first transaction interruption information refers to the reminder information generated for the interrupted transaction based on the transaction amount being greater than the transaction amount threshold, such as "the transaction is interrupted because the transaction amount exceeds the authorized amount".

[0110] Using the previous example, if user u is determined to be a member of the project, the purchase information uploaded by the facial recognition payment device is obtained. The purchase information includes the purchase amount p1. The preset transaction amount threshold is p2. If p1 is greater than p2, it means that the purchase amount exceeds the authorized amount. Then, the purchase interruption information "Transaction interrupted because the purchase amount p1 is greater than the authorized amount p2" is generated. This purchase interruption information is used as the transaction result information.

[0111] Assuming p1 is not greater than p2, indicating that the purchase amount does not exceed the authorized amount, the merchant account is determined based on the merchant code c1 contained in the purchase information, and the authorized account corresponding to user u is also determined. The purchase amount p1 is then transferred from the authorized account to the merchant account, thereby generating a purchase order. Specifically, the order information in the purchase order includes: user u's user code c2 in the project, merchant code c1, transfer amount p1, and the purchased item "mineral water", etc. This order information is used as the transaction result information.

[0112] In addition to using the transaction amount threshold as a transaction condition, the transaction scenario type can also be used as a transaction condition. This helps prevent losses for target users and further ensures transaction security. In one optional implementation provided in this specification, after the step of obtaining the transaction information uploaded by the transaction terminal of the transaction participant during the transaction process is executed, and before the step of determining whether the transaction amount contained in the transaction information is greater than the preset transaction amount threshold in the project is executed, the method further includes:

[0113] Based on the transaction information, determine the transaction scenario type;

[0114] Determine whether there exists a target authorization scenario type that is the same as the scenario type among the preset authorization scenario types for the user in the project;

[0115] If it exists, it indicates that the scenario type is authorized, and the step of determining whether the transaction amount is less than the preset transaction amount threshold in the project based on the transaction amount contained in the transaction information is executed;

[0116] If it does not exist, it indicates that the scenario type has not been authorized. Based on the second judgment result of the scenario judgment, a second transaction interruption information is generated, and the second transaction interruption information is used as the transaction result information.

[0117] Specifically, it is determined whether there is a target authorization scenario type that is the same as the scenario type among the preset authorization scenario types for the user in the project. For example, the authorization scenario types include supermarkets and convenience stores, and the user's transaction scenario type is convenience store, then the target authorization scenario type is convenience store.

[0118] The second judgment result refers to the absence of a target authorized scenario type with the same scenario type in the authorized scenario types; correspondingly, the second transaction interruption information refers to the reminder information generated for the interrupted transaction based on the absence of a target authorized scenario type with the same scenario type in the authorized scenario types, such as "the transaction is interrupted because the scenario type of the transaction is not an authorized scenario type".

[0119] Using the previous example, if user u is determined to be a member of the project, the purchase information uploaded by the facial recognition payment device is obtained. Based on the merchant code c1 contained in the purchase information, it is determined that the scenario type for user u's purchase of mineral water is convenience store. The authorized scenario types preset for user u in the project are supermarket and convenience store. The judgment result of whether there is a target authorized scenario type with the same purchase scenario type among the authorized scenario types preset for user u in the project is yes, indicating that the scenario type for user u's purchase of mineral water is authorized. Then, the above step of judging whether the purchase amount p1 is less than the preset purchase amount threshold in the project is executed.

[0120] Suppose that if the judgment result of determining whether there is a target authorized scenario type that is the same as the scenario type purchased by user u in the project's preset authorized scenario types is not found, it means that the scenario type for user u to purchase mineral water has not been authorized. Then, a purchase interruption message is generated: "Transaction interrupted because the purchased scenario type is not an authorized scenario type". This purchase interruption message is used as the transaction result information.

[0121] Step S106: If the user is marked as unreachable in the project, identify the target participating user in the project who has an identity binding relationship with the user.

[0122] Based on the user's identity feature image, if the determination of whether the user is a project member is yes, then further determine whether the user's corresponding identity status in the project is marked as "out of contact". If yes, it means that the target participating user cannot contact the user and considers the user to be lost or missing. In this case, the user is marked as "out of contact" in the project, thus identifying the target participating user with an identity binding relationship with the user in the project, so as to obtain the target participating user's contact information and enable the user to contact the target participating user. If no, it means that the user is not in an out of contact state, and no action needs to be taken.

[0123] In practice, a user's identity status can also be marked as "in contact," "normal," etc., without any restrictions.

[0124] Using the previous example, if user u is marked as unreachable in the project, determine the target user code c3 of the target participating user whose identity is bound to user u in the project.

[0125] Step S108: Send the identity verification result for the user to at least one of the target participating user and the transaction participants.

[0126] In practical applications, when a user's identity status is determined to be out of contact, the identity verification result for the user is sent to the target participating users and / or transaction participants who have a binding relationship with the user.

[0127] Specifically, sending the user's identity verification result to the target user and / or transaction participant with whom the user has a binding relationship means reminding the target user and / or transaction participant that the user is out of contact, and providing their location information and relevant contact information so that the user can be contacted.

[0128] When a user is marked as unreachable, there are various ways to send the user's identity verification result. In the first optional implementation provided in this specification, the sending of the user's identity verification result to the target participating user is specifically implemented in the following way:

[0129] Based on the device identifier of the transaction terminal contained in the transaction information, the location information of the transaction terminal and the participant information of the transaction participants are determined;

[0130] Based on the location information, the participant information, and the transaction result information, a request for help is generated for the user.

[0131] Based on the requested assistance information, a request for assistance is sent to the target user regarding the user's loss of contact status.

[0132] In practical applications, during the process of sending the user's identity verification results to the target user, the participant information includes the participant's name, contact number, and other information; the assistance information includes the location information of the transaction terminal where the user conducted the transaction, the participant information of the transaction participants, and the transaction result information between the user and the transaction participants; based on this, an assistance notification is sent to the target user according to the assistance information, so that the target user knows the user's location, contact information for the user, and the user's transaction status, so that the target user can contact the transaction participants and further contact the user after receiving the assistance notification.

[0133] In practice, to ensure that target participants can receive requests for help in a timely manner and receive timely assistance, multiple notification methods such as SMS notifications, telephone notifications, and push notifications within the project can be used in parallel.

[0134] Using the previous example, based on the device code d1 of the facial recognition payment device included in the purchase information, the location LI of the facial recognition payment device is determined, and based on the merchant code c1 included in the purchase information, the merchant's contact number p1 is determined. Then, based on the location LI, the merchant's contact number pn1, the user code c2 of user u in the project included in the purchase order, and the transfer amount p1, a request for help is generated for user u: "User u spent an amount of p1 at location LI, and the merchant's contact number is pn1". This request for help is then sent to the target user via SMS and telephone.

[0135] In addition to sending the user's identity verification result to the target participating user as described above, the second optional implementation provided in this specification sends the user's identity verification result to the transaction participants in the following manner:

[0136] Obtain the contact information of the target participating users;

[0137] Based on the contact information and the transaction result information, a request for help is generated for the user;

[0138] Based on the requested assistance information, a notification is sent to the transaction terminal regarding the user's loss of contact status.

[0139] In practical applications, during the process of sending identity verification results to transaction participants, the contact information of the target participant includes the target participant's contact number, address, and other information; the request for help information includes the contact information of the target participant whose identity is bound to the user, as well as the transaction result information between the user and the transaction participants; based on this, a request for help notification is sent to the transaction terminal according to the request for help information, so that the transaction participants know that the user is out of contact and how to contact the target participant and the user's transaction status, so that the transaction participants can contact the target participant after receiving the request for help notification and further enable the target participant to establish contact with the user.

[0140] In practice, to ensure that transaction participants can receive users' requests for help in a timely manner and that users can receive timely assistance, the contact information of transaction participants can be obtained through the transaction information contained in the transaction information. Furthermore, based on the contact information, multiple notification methods such as SMS notification, telephone notification, and push message in the transaction terminal can be used in parallel to notify them.

[0141] It should be noted that, in order to ensure the information security of the target users, a request for help can be sent to the transaction terminal by means of QR code encryption or hiding certain characters in the contact information.

[0142] Using the previous example, based on the target user's code c3, the target user's contact number pn2 is obtained. Based on the merchant code c1 contained in the purchase information, the user code c2 of user u in the project contained in the purchase order, and the transfer amount p1, a request for help is generated for user u: "User u is out of contact, the amount of consumption is p1, and the contact number of the target user whose identity is bound to her is pn2". This request for help is then sent to the facial recognition payment device via push notification.

[0143] In addition to the two specific implementation methods for sending user identity verification results mentioned above, in the third optional implementation method provided in this specification, when the user is a child, the step of sending user identity verification results to both the target participating user and the transaction participants is implemented in the following way:

[0144] Obtain the contact information of the target participating user, and determine the location information of the transaction terminal and the participant information of the transaction participant based on the device identifier of the transaction terminal contained in the transaction information;

[0145] Based on the contact information, location information, participant information, and transaction result information, a request for help is generated for the child.

[0146] Based on the requested assistance information, a request for assistance regarding the child's loss of contact is sent to the transaction terminal and the target participating user.

[0147] Specifically, generating a request for help for the child is similar to generating a request for help for the user as described above, and will not be repeated here. Sending a request for help notification for the child in a lost contact state is similar to sending a request for help notification for the user in a lost contact state as described above, and will not be repeated here.

[0148] In summary, this specification provides an identity verification method that acquires the user's identity feature image collected during the transaction process between the user and the transaction participants to identify the user and determine whether the user is a project member. If the user is a project member, the transaction is processed, and it is further determined whether the user is marked as unreachable in the project. This achieves identity verification of whether the user is unreachable during the transaction process. If the user is marked as unreachable, a target participating user with an identity binding relationship with the user in the project is identified, and a help notification for the user is sent to at least one of the target participating user and the transaction participants. This enables the target participating user and / or the transaction participants to track the unreachable user based on the user's transactions, and allows the unreachable user to enjoy the transaction services and thus obtain material assistance.

[0149] The following is in conjunction with the appendix Figure 2 Taking the application of the identity verification method provided in this specification in a facial recognition payment scenario as an example, the identity verification method will be further explained. Among other things, Figure 2 The present specification shows a flowchart of an identity verification method for facial recognition payment scenarios provided by an embodiment of this specification, with specific steps including steps S202 to S226.

[0150] Step S202: Obtain the user's facial image collected by the user and transaction participants during the payment process.

[0151] The user can be a member of a special group such as the elderly, children, or people with disabilities.

[0152] Specifically, before the step of obtaining the user's facial image collected during the payment process by the user and transaction participants is executed, the procedure further includes:

[0153] Obtain the payment authorization request submitted by the user in the project;

[0154] Based on the payment authorization information submitted for the payment authorization option carried in the payment authorization request, a payment authorization agreement is generated in which the target participating user authorizes payment to the user; the payment authorization agreement includes at least one authorization scenario type and / or payment amount threshold authorized by the target participating user to the user;

[0155] Based on the payment authorization protocol, an authorization completion instruction is sent for the payment authorization request.

[0156] Step S204: Perform image recognition on the face image to obtain the user's facial features.

[0157] Step S206: Compare the facial features with the facial features corresponding to the pre-stored facial images of project members in the project to obtain the feature similarity.

[0158] Step S208: Determine whether the user is a member of the project by judging whether the feature similarity is greater than a preset similarity threshold;

[0159] If so, it indicates that the user is a project member in the project, and the following step S210 is executed;

[0160] If not, it indicates that the user is not a project member, and the normal payment process will be executed.

[0161] In this project, participating users establish an identity binding relationship with project members by registering their identities and marking the identity status of project members.

[0162] Specifically, the registration of project members' identities is achieved in the following way:

[0163] Retrieve member registration requests submitted by participating users;

[0164] The facial image carried in the member registration request is used as the member's facial image and stored in the feature image library of the project;

[0165] Based on the identity relationship information carried in the member registration request, the member's facial image is bound to the participating user's identity;

[0166] If the identity binding is successful, a registration completion instruction is sent in response to the member registration request.

[0167] Step S210: Obtain the payment information uploaded by the payment terminal of the transaction participant during the payment process.

[0168] Step S212: Determine the payment scenario type based on the payment information.

[0169] Step S214: Determine whether there is a target authorization scenario type that is the same as the scenario type among the preset authorization scenario types for users in the project;

[0170] If it exists, it indicates that the scene type is authorized, and the following step S216 is executed;

[0171] If it does not exist, it indicates that the scenario type is not authorized. Based on the second judgment result of the scenario judgment, a second payment interruption information is generated, and the second payment interruption information is used as the payment result data.

[0172] Step S216: Determine whether the payment amount contained in the payment information is greater than the preset payment amount threshold in the project;

[0173] If it is greater than, it indicates that the payment amount exceeds the authorized amount. Based on the first judgment result of the amount judgment, the first payment interruption information is generated and the first payment interruption information is used as the payment result data.

[0174] If it is not greater than, it indicates that the payment amount does not exceed the authorized amount, and the following step S218 is executed.

[0175] Step S218: Based on the payment information, perform payment processing, generate a payment order, and use the order information in the payment order as payment result data.

[0176] Step S220: If a user is marked as unreachable in the project, identify the target participating users in the project who have an identity binding relationship with the user.

[0177] Specifically, the target participants are the users' relatives. By having the users register as project members, they can send help requests to the relatives through the project if the users lose contact, and thus receive appropriate assistance.

[0178] Step S222: Obtain the contact information of the target participating user, and determine the location information of the payment terminal and the participant information of the transaction participant based on the device identifier of the payment terminal contained in the payment information.

[0179] Step S224: Generate a request for help for the user based on contact information, location information, participant information, and payment result information.

[0180] Step S226: Based on the request for help information, send a request for help notification to the payment terminal and the target participating user regarding the user's loss of contact.

[0181] This specification provides an identity verification method. By acquiring the user's facial image collected during the payment process by the user and transaction participants, the method identifies the user and determines whether the user is a project member. If the user is a project member, the method further determines whether the user has been marked as unreachable in the project. This achieves identity verification of whether the user is unreachable during the payment process. If the user is marked as unreachable, the method identifies a target participating user in the project with an identity binding relationship with the user, and sends a request for assistance to the target participating user and at least one of the transaction participants. This allows the target participating user and / or transaction participants to track the unreachable user based on the payment made by the user, and enables the unreachable user to enjoy the payment service and thus obtain material assistance.

[0182] The following is an example of an identity verification device provided in this specification:

[0183] Corresponding to the above method embodiments, this specification also provides embodiments of identity verification devices. Figure 3 A schematic diagram of an identity verification device according to one embodiment of this specification is shown. Figure 3 As shown, the device includes:

[0184] The acquisition module 302 is configured to acquire the user's identity feature image collected by the user and transaction participants during the transaction process;

[0185] The judgment module 304 is configured to determine whether the user is a project member based on the identity feature image; the participating users in the project establish an identity binding relationship with the project members by registering their identities and marking the identity status of the project members.

[0186] If so, run the determination module 306, which is configured to determine the target participating user in the project who has an identity binding relationship with the user when the user is marked as unreachable in the project;

[0187] The sending module 308 is configured to send the identity verification result for the user to at least one of the target participating user and the transaction participants.

[0188] Optionally, the identity verification device further includes:

[0189] The information acquisition module is configured to acquire transaction information uploaded by the transaction terminals of the transaction participants during the transaction process;

[0190] The threshold determination module is configured to determine whether the transaction amount contained in the transaction information is greater than a preset transaction amount threshold in the project.

[0191] If the value is greater than the first value, the first generation module is run. The first generation module is configured to generate the first transaction interruption information based on the first judgment result of the amount judgment, and use the first transaction interruption information as the transaction result information.

[0192] If the value is not greater than the transaction information, the order generation module is run. The order generation module is configured to process the transaction based on the transaction information, generate a transaction order, and use the order information in the transaction order as the transaction result information.

[0193] Optionally, the identity verification device further includes:

[0194] The type determination module is configured to determine the scenario type of the transaction based on the transaction information;

[0195] The type determination module is configured to determine whether there is a target authorization scenario type that is the same as the scenario type among the preset authorization scenario types for the user in the project;

[0196] If it exists, run the threshold determination module;

[0197] If it does not exist, the second generation module is run. The second generation module is configured to generate the second transaction interruption information based on the second judgment result of the scenario judgment, and the second transaction interruption information is used as the transaction result information.

[0198] Optionally, the sending module 308 includes:

[0199] The determination information submodule is configured to determine the location information of the transaction terminal and the participant information of the transaction participants based on the device identifier of the transaction terminal contained in the transaction information.

[0200] The first information generation submodule is configured to generate a request for help for the user based on the location information, the participant information, and the transaction result information.

[0201] The first notification sending submodule is configured to send a help notification to the target participating user regarding the user's loss of contact status based on the help request information.

[0202] Optionally, the sending module 308 includes:

[0203] The first submodule for obtaining contact information is configured to obtain the contact information of the target participating user.

[0204] The second information generation submodule is configured to generate a request for help for the user based on the contact information and the transaction result information.

[0205] The second notification sending submodule is configured to send a request for help notification to the transaction terminal based on the request for help information, targeting the user in the state of being out of contact.

[0206] Optionally, the determination module 304 includes:

[0207] The feature acquisition submodule is configured to perform image recognition on the identity feature image to obtain the user's identity features;

[0208] The comparison submodule is configured to compare the identity features with the member features corresponding to the member feature images of the pre-stored project members in the project to obtain feature similarity;

[0209] The member determination submodule is configured to determine whether the user is a member of the project by judging whether the feature similarity is greater than a preset similarity threshold.

[0210] Optionally, the registration of project members' identities is achieved by running the following submodule:

[0211] The request retrieval submodule is configured to retrieve member registration requests submitted by participating users.

[0212] The storage submodule is configured to store the feature image carried in the member registration request as a member feature image in the feature image library of the project.

[0213] The identity binding submodule is configured to bind the member feature image to the participating user's identity based on the identity relationship information carried in the member registration request;

[0214] The instruction sending submodule is configured to send a registration completion instruction for the member registration request if the identity binding is successful.

[0215] Optionally, the identity verification device further includes:

[0216] The authorization request acquisition module is configured to acquire transaction authorization requests submitted by the user in the project;

[0217] The protocol generation module is configured to generate a transaction authorization agreement for the target participating user to authorize a transaction to the user based on the transaction authorization information submitted for the transaction authorization options carried in the transaction authorization request; the transaction authorization agreement includes at least one authorization scenario type and / or transaction amount threshold authorized by the target participating user to the user;

[0218] The module for sending completion instructions is configured to send an authorization completion instruction for the transaction authorization request based on the transaction authorization protocol.

[0219] Optionally, if the user is a child, the determination module 304 includes:

[0220] The second contact information acquisition submodule is configured to acquire the contact information of the target participating user, and determine the location information of the transaction terminal and the participant information of the transaction participant based on the device identifier of the transaction terminal contained in the transaction information.

[0221] The third information generation submodule is configured to generate a request for help for the child based on the contact information, the location information, the participant information, and the transaction result information.

[0222] The third notification sending submodule is configured to send a request for help notification to the transaction terminal and the target participating user regarding the child's missing status, based on the request for help information.

[0223] Optionally, the identity feature image includes at least one of the following: a face image, an iris image, and a fingerprint image.

[0224] The above is a schematic scheme of an identity verification device according to this embodiment. It should be noted that the technical solution of this identity verification device and the technical solution of the above-described identity verification method belong to the same concept. For details not described in detail in the technical solution of the identity verification device, please refer to the description of the technical solution of the above-described identity verification method.

[0225] The following is an example of a computing device provided in this specification:

[0226] Figure 4 A structural block diagram of a computing device 400 according to one embodiment of this specification is shown. The components of the computing device 400 include, but are not limited to, a memory 410 and a processor 420. The processor 420 is connected to the memory 410 via a bus 430, and a database 450 is used to store data.

[0227] The computing device 400 also includes an access device 440, which enables the computing device 400 to communicate via one or more networks 460. Examples of these networks include a Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 440 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0228] In one embodiment of this specification, the aforementioned components of the computing device 400 and Figure 4 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 4 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0229] The computing device 400 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs. The computing device 400 can also be a mobile or stationary server.

[0230] This specification provides a computing device, including a memory 410, a processor 420, and computer instructions stored in the memory and executable on the processor. The processor 420 is configured to execute the following computer-executable instructions:

[0231] Obtain the user's identity feature image collected during the transaction process by the user and the transaction participants;

[0232] Based on the identity feature image, it is determined whether the user is a project member; the participating users in the project establish an identity binding relationship with the project members by registering their identities, and mark the identity status of the project members;

[0233] If so, if the user is marked as unreachable in the project, identify the target participating user in the project who has an identity binding relationship with the user;

[0234] Send the identity verification result for the user to at least one of the target user and the transaction participants.

[0235] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the above-described identity verification method belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the above-described identity verification method.

[0236] This specification provides an embodiment of a computer-readable storage medium as follows:

[0237] This specification provides a computer-readable storage medium storing computer instructions that, when executed by a processor, are used for:

[0238] Obtain the user's identity feature image collected during the transaction process by the user and the transaction participants;

[0239] Based on the identity feature image, it is determined whether the user is a project member; the participating users in the project establish an identity binding relationship with the project members by registering their identities, and mark the identity status of the project members;

[0240] If so, if the user is marked as unreachable in the project, identify the target participating user in the project who has an identity binding relationship with the user;

[0241] Send the identity verification result for the user to at least one of the target user and the transaction participants.

[0242] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the above-described identity verification method belong to the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the above-described identity verification method.

[0243] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0244] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0245] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0246] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0247] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. An identity verification method, comprising: During the transaction process between the user and the transaction participants, the user's identity is verified to determine whether the user is a user who is out of contact in the project. If so, obtain the transaction information uploaded by the transaction terminals of the transaction participants during the transaction process; Determine whether the transaction meets the preset transaction conditions in the project; If the conditions are met, the transaction will be processed based on the transaction information, and transaction result information will be generated. Identify target participating users in the project who have an identity binding relationship with the user, wherein the target participating users have pre-authorized transactions with the user; Send the identity verification result and transaction result information for the target user and at least one of the transaction participants to the target user and the transaction participants. The transaction result information includes information generated by the judgment based on the scope of transaction authorization.

2. The identity verification method according to claim 1, before the step of determining the target participating user in the project who has an identity binding relationship with the user is executed, it further includes: Obtain the transaction information uploaded by the transaction terminals of the transaction participants during the transaction process; Determine whether the transaction amount contained in the transaction information is greater than the preset transaction amount threshold in the project; If the amount is greater than the first judgment result, a first transaction interruption message is generated based on the amount judgment, and the first transaction interruption message is used as the transaction result information; If the value is not greater than the transaction information, the transaction is processed to generate a transaction order, and the order information in the transaction order is used as the transaction result information.

3. The identity verification method according to claim 2, after the step of obtaining the transaction information uploaded by the transaction terminal of the transaction participant during the transaction process is executed, and before the step of determining whether the transaction amount contained in the transaction information is greater than the preset transaction amount threshold in the project is executed, further comprising: Based on the transaction information, determine the transaction scenario type; Determine whether there exists a target authorization scenario type that is the same as the scenario type among the preset authorization scenario types for the user in the project; If so, proceed with the step of determining whether the transaction amount contained in the transaction information is greater than the preset transaction amount threshold in the project; If it does not exist, based on the second judgment result of the scenario judgment, a second transaction interruption information is generated, and the second transaction interruption information is used as the transaction result information.

4. The identity verification method according to claim 2, wherein sending the identity verification result for the user to at least one of the target participating user and the transaction participant includes: Based on the device identifier of the transaction terminal contained in the transaction information, the location information of the transaction terminal and the participant information of the transaction participants are determined; Based on the location information, the participant information, and the transaction result information, a request for help is generated for the user. Based on the requested assistance information, a request for assistance is sent to the target user regarding the user's loss of contact status.

5. The identity verification method according to claim 2, wherein sending the identity verification result for the user to at least one of the target participating user and the transaction participant includes: Obtain the contact information of the target participating users; Based on the contact information and the transaction result information, a request for help is generated for the user; Based on the requested assistance information, a notification is sent to the transaction terminal regarding the user's loss of contact status.

6. The identity verification method according to claim 1, wherein during the transaction process between the user and the transaction participant, verifying the user's identity to determine whether the user is a user who is out of contact in the project includes: Obtain the user's identity feature image collected during the transaction process by the user and the transaction participants; Based on the identity feature image, it is determined whether the user is a project member; the participating users in the project establish an identity binding relationship with the project members by registering their identities, and mark the identity status of the project members; If so, determine whether the user is in a state of being out of contact based on the user's identity status.

7. The identity verification method according to claim 6, wherein determining whether the user is a project member based on the identity feature image includes: Image recognition is performed on the identity feature image to obtain the user's identity features; The identity features are compared with the member features corresponding to the member feature images of the pre-stored project members in the project to obtain the feature similarity. The user is determined to be a member of the project by judging whether the feature similarity is greater than a preset similarity threshold.

8. The identity verification method according to claim 6, wherein the identity registration for project members is implemented in the following manner: Retrieve member registration requests submitted by participating users; The feature image carried in the member registration request is used as the member feature image and stored in the feature image library of the project. Based on the identity relationship information carried in the member registration request, the member feature image is bound to the participating user's identity; If the identity binding is successful, a registration completion instruction is sent in response to the member registration request.

9. The identity verification method according to claim 6, before the step of obtaining the user's identity feature image collected by the user and transaction participants during the transaction process, further includes: Obtain the transaction authorization request submitted by the user in the project; Based on the transaction authorization information submitted for the transaction authorization options carried in the transaction authorization request, a transaction authorization agreement is generated in which the target participating user authorizes the user to make a transaction; the transaction authorization agreement includes at least one authorization scenario type and / or transaction amount threshold authorized by the target participating user to the user; Based on the transaction authorization protocol, an authorization completion instruction is sent for the transaction authorization request.

10. The identity verification method according to claim 2, wherein, in the case that the user is a child, sending the identity verification result for the user to at least one of the target participating user and the transaction participant includes: Obtain the contact information of the target participating user, and determine the location information of the transaction terminal and the participant information of the transaction participant based on the device identifier of the transaction terminal contained in the transaction information; Based on the contact information, location information, participant information, and transaction result information, a request for help is generated for the child. Based on the requested assistance information, a request for assistance regarding the child's loss of contact is sent to the transaction terminal and the target participating user.

11. The identity verification method according to claim 6, wherein the identity feature image includes at least one of the following: a face image, an iris image, and a fingerprint image.

12. An identity verification device, comprising: The judgment module is configured to determine whether a user is a user who is out of contact in the project by verifying the user's identity during the transaction process between the user and the transaction participants. If so, the determination module is run. The determination module is configured to obtain the transaction information uploaded by the transaction terminal of the transaction participant during the transaction process; and determine whether the transaction meets the preset transaction conditions in the project. If the conditions are met, the transaction is processed according to the transaction information, and transaction result information is generated; the target participating user in the project who has an identity binding relationship with the user is identified, wherein the target participating user has pre-authorized the transaction for the user; The sending module is configured to send the identity verification result and transaction result information of the user to at least one of the target user and the transaction participants, wherein the transaction result information includes information generated by the judgment of the transaction based on the scope of transaction authorization.

13. A computing device, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions: During the transaction process between the user and the transaction participants, the user's identity is verified to determine whether the user is a user who is out of contact in the project. If so, identify the target participating user in the project who has an identity binding relationship with the user, wherein the target participating user has pre-authorized the transaction with the user; Send the identity verification result and transaction result information for the target user and at least one of the transaction participants to the target user and the transaction participants. The transaction result information includes information generated by the judgment based on the scope of transaction authorization.

14. A computer-readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the identity verification method according to any one of claims 1 to 11.

Images