Identity verification method, business handling method and device

Abstract

The embodiment of the invention discloses an identity verification method, and the method prompts a user to carry out the reverse payment of a verification account which is opened in a bank by a third-party financial platform through the binding of a same-name bank account of a third-party account which is opened in the third-party financial platform. And the authenticity of the identity of the user is verified by verifying the consistency of the collection information of the verification account and the payment instruction. And the user can immediately complete the verification operation as long as completing the payment behavior and confirming that the payment behavior is completed. Through the scheme, the success rate of verification operation can be improved, and the user experience is optimized. The identity verification device, the business handling method and the business handling device in the embodiment of the specification also have the above beneficial effects.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an identity verification method, a business handling method and a device. Background Art

[0002] In the field of financial services, when users conduct certain business on third-party financial platforms, they need to ensure the authenticity of their identities. Currently, the routine operation is for the third-party financial platform to randomly transfer a sum of money to the bank account designated by the user, and the user enters the amount of money received in the bank account on the identity verification page of the third-party financial platform for identity verification. This process is also called positive payment verification.

[0003] However, the forward payment verification is restricted by the bank's large and small amount gateways, and the verification funds may not arrive in time, which will cause users to be unable to verify in time, the verification operation success rate is low, and the user experience is poor. Summary of the invention

[0004] One or more embodiments of the present specification provide an identity verification method, a business processing method and a device, which implements user identity verification by means of reverse payment, is not subject to the transfer time limit of the bank's large and small amount gateways, and can improve the efficiency of identity verification.

[0005] In a first aspect, an identity verification method is provided, which is applicable to a third-party financial platform, and the method comprises: In response to the identity verification request initiated for the target user, a remittance instruction is issued to the target user; the remittance instruction is used to prompt the target user to remit a specified amount of money to the verification account opened by the third-party financial platform in the bank through a designated bank account within a designated time; the designated bank account is a bank account with the same name that is bound to the third-party account opened by the target user on the third-party financial platform; In response to the target user confirming that the payment has been made, obtaining payment information of the verification account, and verifying the consistency between the payment information and the payment instruction; Based on the consistency verification result of the payment information and the payment instruction, it is determined whether the identity of the target user has been verified.

[0006] As an optional implementation manner of the method of the first aspect, in response to an identity verification request initiated for a target user, issuing a payment instruction to the target user specifically includes: In response to an identity verification request initiated for the target user, an identity verification session is initiated to the target user, and based on the service to be handled by the target user, a session scenario identifier is allocated to the identity verification session; The payment instruction is issued to the target user in the identity verification session.

[0007] Specifically, in response to the target user confirming that the payment has been made, obtaining the payment information generated by the verification account, and verifying the consistency between the payment information and the payment instruction, specifically includes: In response to the target user confirming that the payment has been made within the validity period of the identity verification session, the payment receipt information of the verification account within the validity period of the identity verification session is obtained, and the consistency of the payment receipt information and the payment instruction is verified; the deadline of the identity verification session is less than the specified time of the payment instruction.

[0008] Specifically, in response to the target user confirming that the payment has been made, obtaining the payment information generated by the verification account, and verifying the consistency between the payment information and the payment instruction, specifically includes: If the target user does not confirm that the payment has been made within the validity period of the identity verification session, the identity verification session is terminated; the end time of the identity verification session is less than the specified time of the payment instruction; In response to the target user initiating a payment verification request, initiating a payment verification session, and allocating a session scenario identifier to the payment verification session based on the business to be handled by the target user; Acquiring payment information input by the user in the payment verification session; Match the payment information with the payment information generated by the verification account to determine the payment information corresponding to the payment information; According to the session scenario identifier of the payment verification session, searching for an identity verification session with the same session scenario identifier, and obtaining a payment instruction in the identity verification session; Verify the consistency between the payment information and the payment instruction in the identity verification session.

[0009] As an optional implementation manner of the method of the first aspect, verifying the consistency between the payment information and the payment instruction specifically includes: Verify whether the payment time of the payment information is consistent with the specified time of the payment instruction; Verify whether the amount of the payment received in the payment information is consistent with the amount specified in the payment instruction; Verify whether the payment account in the payment information is consistent with the designated bank account in the payment instruction.

[0010] As an optional implementation manner of the method of the first aspect, the method further includes: Before verifying the consistency between the payment information and the payment instruction, verifying whether the payment information has been verified; If the payment information has been verified, it is determined that the identity verification of the target user has failed; If the payment information has not been verified, the consistency between the payment information and the payment instruction is verified.

[0011] In a second aspect, a business handling method is provided, which is applicable to a third-party financial platform, and the method includes: In response to a user's request for handling a target business, performing a risk assessment on the target business; If the target business does not have any risk, continue the processing of the target business; If the target business is at risk, the processing of the target business is terminated, and the identity of the user is verified using the above-mentioned identity verification method; In response to the identity verification of the user being passed, continuing the processing process of the target business; In response to the user's identity verification failing, the handling process of the target service is terminated.

[0012] In a third aspect, an identity verification device is provided, which is applicable to a third-party financial platform, and the device includes: a response module configured to issue a payment instruction to the target user in response to an identity verification request initiated for the target user; the payment instruction is used to prompt the target user to transfer a specified amount of money to the verification account opened by the third-party financial platform in the bank through a designated bank account within a designated time; the designated bank account is a bank account with the same name bound to the third-party account opened by the target user on the third-party financial platform; A verification module, configured to obtain payment information of the verification account in response to the target user confirming that the payment has been made, and to verify the consistency between the payment information and the payment instruction; The determination module is configured to determine whether the identity of the target user has been verified based on the consistency verification result between the payment information and the payment instruction.

[0013] As an optional implementation manner of the device according to the third aspect, the response module is specifically used for: In response to an identity verification request initiated for the target user, an identity verification session is initiated to the target user, and based on the service to be handled by the target user, a session scenario identifier is allocated to the identity verification session; The payment instruction is issued to the target user in the identity verification session.

[0014] Specifically, the verification module is specifically used for: In response to the target user confirming that the payment has been made within the validity period of the identity verification session, the payment receipt information of the verification account within the validity period of the identity verification session is obtained, and the consistency of the payment receipt information and the payment instruction is verified; the deadline of the identity verification session is less than the specified time of the payment instruction.

[0015] Specifically, the verification module is specifically used for: If the target user does not confirm that the payment has been made within the validity period of the identity verification session, the identity verification session is terminated; the end time of the identity verification session is less than the specified time of the payment instruction; In response to the target user initiating a payment verification request, initiating a payment verification session, and allocating a session scenario identifier to the payment verification session based on the business to be handled by the target user; Acquiring payment information input by the user in the payment verification session; Match the payment information with the payment information generated by the verification account to determine the payment information corresponding to the payment information; According to the session scenario identifier of the payment verification session, searching for an identity verification session with the same session scenario identifier, and obtaining a payment instruction in the identity verification session; Verify the consistency between the payment information and the payment instruction in the identity verification session.

[0016] As an optional implementation manner of the device according to the third aspect, the verification module is specifically used for: Verify whether the payment time of the payment information is consistent with the specified time of the payment instruction; Verify whether the amount of the payment received in the payment information is consistent with the amount specified in the payment instruction; Verify whether the payment account in the payment information is consistent with the designated bank account in the payment instruction.

[0017] As an optional implementation manner of the device according to the third aspect, the verification module is further used for: Before verifying the consistency between the payment information and the payment instruction, verifying whether the payment information has been verified; If the payment information has been verified, it is determined that the identity verification of the target user has failed; If the payment information has not been verified, the consistency between the payment information and the payment instruction is verified.

[0018] In a fourth aspect, a business processing device is provided, which is applicable to a third-party financial platform, and the device includes: A data acquisition module configured to acquire a user's business processing request for a target business; a risk assessment module, configured to perform risk assessment on the target business in response to the user's request for handling the target business; an identity verification module, configured to verify the identity of the user using the above-mentioned identity verification method in response to the risk assessment module assessing that the target business has a risk; A business processing module, configured to continue the processing of the target business in response to the risk assessment module assessing that the target business does not have any risk; The business processing module is also configured to, in response to the risk assessment module assessing that the target business is risky, terminate the processing process of the target business; and to continue the processing process of the target business when the identity verification module passes the identity verification of the user; and, to terminate the processing process of the target business when the identity verification module fails the identity verification of the user.

[0019] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned identity verification method is implemented, or the above-mentioned business processing method is implemented.

[0020] In a sixth aspect, an electronic device is provided, including: One or more processors; and a memory associated with the one or more processors, the memory being used to store program instructions, and the program instructions, when read and executed by the one or more processors, execute the above-mentioned identity verification method, or execute the above-mentioned business processing method.

[0021] The beneficial effect of the identity verification method described in one or more embodiments of this specification is that the method prompts the user to use the bank account with the same name bound to the third-party account opened on the third-party financial platform to reversely transfer money to the verification account opened by the third-party financial platform in the bank. Since the transfer information is known, the user only needs to complete the transfer behavior and confirm that the transfer behavior is completed to immediately complete the verification operation. Through the above solution, the success rate of the verification operation can be improved and the user experience can be optimized.

[0022] The identity verification device, business processing method and device described in the embodiments of this specification also have the above-mentioned beneficial effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0024] Figure 1 A flowchart of an identity verification method provided for one or more embodiments of this specification.

[0025] Figure 2 A schematic diagram of the structure of a third-party financial platform provided for one or more embodiments of this specification.

[0026] Figure 3 A flowchart of a business processing method provided in one or more embodiments of this specification.

[0027] Figure 4 A schematic diagram of the structure of an identity verification device provided in one or more embodiments of this specification.

[0028] Figure 5 A schematic diagram of the structure of a business processing device provided in one or more embodiments of this specification.

[0029] Figure 6 A schematic diagram of the structure of an electronic device provided for one or more embodiments of this specification. DETAILED DESCRIPTION

[0030] First of all, it should be noted that the terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms "a", "the" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms, unless the context clearly indicates otherwise.

[0031] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Therefore, it should be recognized by those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0032] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0033] In the current field of corporate financial services, when operating financial accounts, especially when dealing with high-risk operations such as retrieving passwords, changing mobile phone numbers, and removing account restrictions, it is crucial to ensure the authenticity of the operator's identity. Therefore, the industry usually uses the positive payment method to verify the operator's identity. Positive payment means that the financial platform randomly transfers a sum of money to the bank account designated by the user. The user enters the amount of money received in the bank account on the identity verification page of the financial platform for identity verification. If the entered amount is consistent with the payment amount, the verification is passed. This process is also called positive payment verification.

[0034] However, the forward payment verification is limited by factors such as the bank's large and small amount gateways, and the verification funds may not be received in time. Especially for corporate users, the corporate bank account is usually bound to the contact information of the legal person, and the operator who handles the payment verification business may not be the legal person himself, so the operator needs to contact the legal person to obtain the arrival information of the verification funds. The above factors will cause users to be unable to verify in time, the success rate of completing the verification operation is low, and the user experience is poor.

[0035] In view of this, one or more embodiments of the present specification propose an identity verification method, a business processing method and a device, which can effectively improve the completion success rate of identity verification operations and optimize user experience.

[0036] The identity verification method, business processing method and device described in one or more embodiments of this specification will be further described in detail below in conjunction with the drawings and specific embodiments of the specification, but this detailed description does not constitute a limitation on the embodiments of this specification.

[0037] Please refer to Figure 1 , Figure 1 Flowchart of an identity verification method proposed in one or more embodiments of this specification, which is applicable to a third-party financial platform. Figure 1 As shown, the identity verification method may include steps S100 to S104.

[0038] S100: In response to an identity verification request initiated for a target user, a payment instruction is issued to the target user.

[0039] The identity verification mechanism is usually initiated when a user conducts a business or performs an operation on a third-party financial platform and the third-party financial platform confirms that the business or operation involves risks.

[0040] Please refer to Figure 2 In some implementations, the third-party financial platform may include a front-end business system and an identity verification system. When a target user handles a business or performs an operation in the front-end business system, the front-end business system conducts a risk assessment on the business or operation, and when it is confirmed that there is a risk, it initiates an identity verification request for the target user to the identity verification system.

[0041] After receiving the identity verification request, the identity verification system will issue a remittance instruction to the target user, which is used to instruct the target user to make a reverse remittance. Specifically, the remittance instruction is used to prompt the target user to remit a specified amount of money to the verification account opened by the third-party financial platform in the bank through a designated bank account within a specified time (for example, within 48 hours). The designated bank account can usually be a bank account with the same name that is bound to the third-party account opened by the target user on the third-party financial platform.

[0042] In some implementations, the identity verification system may initiate an identity verification session with the target user in response to an identity verification request initiated for the target user, and issue a payment instruction to the target user during the identity verification session.

[0043] When initiating an identity verification session, the identity verification system can also assign a unique session scenario identifier to the identity verification session. The session scenario identifier is related to the business that the user needs to handle and the user identity, and can quickly locate the originally interrupted session when the session is interrupted.

[0044] S102: In response to the target user confirming that the payment has been made, obtaining the payment information of the verification account, and verifying the consistency between the payment information and the payment instruction.

[0045] Still Figure 2 Taking the third-party financial platform shown as an example, the identity verification system responds to the identity verification request initiated for the target user and initiates an identity verification session to the target user. The identity verification session has a validity period, which is usually much shorter than the payment time window given by the third-party financial platform to the customer, that is, the validity period of the identity verification session is usually much shorter than the period required in the payment instruction. For example, the period required by the payment instruction is 48 hours, while the validity period of the identity verification session is 10 minutes. After the validity period expires, the identity verification session is closed.

[0046] In a possible scenario, the target user can complete the reverse payment operation required by the payment instruction within the validity period of the identity verification session. After the payment is completed, the target user can directly confirm to the identity verification system that the payment has been made in the identity verification session.

[0047] Since the validity period of the identity verification session is very short, there are few payment events in the verification account during this time period, so the payment information corresponding to the target user's payment operation can be quickly located.

[0048] Based on this, the identity verification system can directly obtain the payment information of the verification account within the validity period of the identity verification session, and verify the consistency of the payment information with the payment instruction of the identity verification session.

[0049] Specifically, the identity verification system needs to verify whether the payment time of the payment information is consistent with the specified time of the payment instruction; verify whether the payment amount of the payment information is consistent with the specified amount of the payment instruction; and verify whether the payment account of the payment information is consistent with the specified bank account of the payment instruction. Only when all the above three verification parameters are consistent can it be determined that the payment information is consistent with the payment instruction of the identity verification session.

[0050] In another possible scenario, the target user cannot complete the reverse payment operation required by the payment instruction within the validity period of the identity verification session. After the identity verification session reaches its validity period, the identity verification session is closed.

[0051] After the target user completes the reverse payment operation required by the payment instruction, it is necessary to initiate a payment verification request for the business to be handled in the identity verification system. In response to the payment verification request initiated by the target user, the identity verification system initiates a payment verification session, and obtains the payment information entered by the target user in the payment verification session, which includes the payment account, payment amount, remarks and other information.

[0052] The identity verification system will match the payment information with the payment information of the verification account to determine whether the target user's payment behavior exists. Specifically, the identity verification system needs to verify whether the payment account in the payment information is consistent with the payment account in the payment information, whether the payment amount in the payment information is consistent with the payment amount in the payment information, and whether the remarks in the payment information are consistent with the remarks in the payment information. Only when all the above information is consistent can it be determined that the target user's payment behavior is real.

[0053] When the identity verification system initiates a payment verification session, it will also assign a session scenario identifier to the payment verification session based on the business that the target user wants to handle. Since the session scenario identifier is related to the business that the user needs to handle and the user's identity, the session scenario identifier for the same user's session regarding the same business scenario is consistent. Based on this principle, the identity verification system can use the session scenario identifier to locate the target user's last closed identity verification session. Specifically, the identity verification system can search for identity verification sessions with the same session scenario identifier based on the session scenario identifier of the current payment verification session.

[0054] After locating the last closed identity verification session of the target user, you can get the payment instruction from the identity verification session. And compare the payment instruction with the payment information found based on the payment information entered by the target user for consistency. Specifically, it is necessary to compare whether the time specified in the payment instruction is consistent with the payment time of the payment information, that is, to determine whether the payment behavior of the target user exceeds the payment period specified in the payment instruction. It is also necessary to compare whether the payment amount of the payment information is consistent with the specified amount of the payment instruction, and whether the payment account of the payment information is consistent with the specified bank account of the payment instruction. Only when it is verified that the above information is consistent, can it be determined that the payment information is consistent with the payment instruction in the identity verification session.

[0055] In some more specific implementations, the identity verification system can also mark each verified payment information. Specifically, each time the identity verification system verifies a payment information, it will mark the payment information with a mark, which is used to indicate that the payment information has been verified, so as to avoid the same payment information being verified multiple times. Based on the mark of the payment information, the identity verification system can verify whether the payment information has been verified before verifying the consistency between the payment information and the payment instruction. If the payment information has been verified, it is determined that the identity verification of the target user has failed. If the payment information has not been verified, the consistency of the payment information and the payment instruction will continue to be verified.

[0056] S104: Determine whether the identity of the target user has been verified based on the consistency verification result between the payment information and the payment instruction.

[0057] If the verification result shows that the payment information is consistent with the payment instruction, the identity of the target user is determined to have passed this identity verification. At this time, the third-party financial platform continues the operation or business to be processed by the target user.

[0058] If the verification result is that the payment information is inconsistent with the payment instruction, it is determined that the identity of the target user has failed the identity verification. At this time, the third-party financial platform terminates the operation or business to be processed by the target user and re-initiates the identity verification process for the target user. If the number of times that the target user fails the identity verification within the preset time period reaches the preset threshold, the third-party financial platform can mark the account information of the target user to determine whether it is a malicious attack operation, so as to perform corresponding defense operations and early warning processing.

[0059] The above is Figure 1 The specific implementation process of the identity verification method shown in the figure verifies the authenticity of the reverse payment behavior by prompting the user to make a reverse payment and verifying the consistency between the payment information and the payment instruction, thereby determining whether the user's identity is credible. Since the payment information is known to the user, the user only needs to complete the payment behavior and confirm that the payment behavior is completed to complete the verification operation immediately. Through the above scheme, the success rate of the verification operation can be improved and the user experience can be optimized. In addition, during the verification process, identity verification is performed based on information that only the user knows, such as account information, payment amount, and payment timestamp, which can effectively resist malicious payment attacks.

[0060] It should be noted that the above identity verification method can be run alone to implement identity verification, or it can be combined with other identity verification methods to implement the user's identity verification function, and this embodiment does not limit this.

[0061] Based on the above-mentioned identity verification method, one or more embodiments of this specification further propose a business handling method, which is applicable to a third-party financial platform and includes steps S300 to S306.

[0062] S300: In response to a user's request for handling a target business, a risk assessment is performed on the target business.

[0063] S302: If there is no risk in the target business, continue the processing of the target business.

[0064] S304: If the target business has risks, the handling process of the target business is terminated, and the identity of the user is verified using the above-mentioned identity verification method.

[0065] S306: In response to the user identity verification being successful, the processing of the target service is continued; in response to the user identity verification being unsuccessful, the processing of the target service is terminated.

[0066] It should be noted that in the above-mentioned business handling method, the third-party financial platform can set up a risk identification scheme to identify whether an operation or business is risky according to needs, and this embodiment does not limit this.

[0067] The identity verification method used in the above-mentioned business handling method is described in detail in the above-mentioned Figure 1 The identity verification method shown in the figure is introduced and will not be repeated here.

[0068] Corresponding to the above-mentioned identity verification method, one or more embodiments of this specification also propose an identity verification device. Figure 4 , Figure 4 Schematic diagram of the structure of an identity verification device proposed in one or more embodiments of this specification. The device can be used to implement the above-mentioned identity verification method. It should be noted that the identity verification method described in one or more embodiments of this application can rely on Figure 4 The identity verification device shown is implemented, but not limited to this device.

[0069] like Figure 4 As shown, the identity verification device includes: The response module 401 is configured to respond to an identity verification request initiated for a target user and issue a payment instruction to the target user.

[0070] The verification module 402 is configured to obtain payment information of the verification account in response to the target user confirming that the payment has been made, and to verify the consistency between the payment information and the payment instruction.

[0071] The determination module 403 is configured to determine whether the identity of the target user has been verified based on the consistency verification result between the payment information and the payment instruction.

[0072] With respect to the above-mentioned response module 401, after receiving the identity verification request, the response module 401 will issue a remittance instruction to the target user, and the remittance instruction is used to instruct the target user to make a reverse remittance. Specifically, the above-mentioned remittance instruction is used to prompt the target user to remit a specified amount of money to the verification account opened by the third-party financial platform in the bank through a designated bank account within a specified time (for example, within 48 hours). The above-mentioned designated bank account can usually be a bank account with the same name that is bound to the third-party account opened by the target user on the third-party financial platform.

[0073] In some implementations, the response module 401 may initiate an identity verification session with the target user in response to an identity verification request initiated for the target user, and issue a payment instruction to the target user in the identity verification session.

[0074] When initiating an identity verification session, the response module 401 may also assign a unique session scenario identifier to the identity verification session. The session scenario identifier is related to the service to be handled by the user and the user identity, and can quickly locate the originally interrupted session when the session is interrupted.

[0075] Regarding the above-mentioned verification module 402, when the response module 401 initiates an identity verification session to the target user in response to the identity verification request initiated for the target user, the verification module 402 verifies the consistency between the payment information and the payment instruction based on the confirmation operation of the target user.

[0076] The identity verification session initiated by the response module 401 has a validity period, which is usually much shorter than the payment time window given by the third-party financial platform to the customer, that is, the validity period of the identity verification session is usually much shorter than the period required in the payment instruction. For example, the period required by the payment instruction is 48 hours, while the validity period of the identity verification session is 10 minutes. After the validity period expires, the identity verification session is closed.

[0077] In a possible scenario, the target user can complete the reverse payment operation required by the payment instruction within the validity period of the identity verification session. After the payment is completed, the target user can directly confirm to the verification module 402 that the payment has been made in the identity verification session.

[0078] Since the validity period of the identity verification session is very short, there are few payment events in the verification account during this time period, so the payment information corresponding to the target user's payment operation can be quickly located.

[0079] Based on this, the verification module 402 can directly obtain the payment information of the verification account within the validity period of the identity verification session, and verify the consistency between the payment information and the payment instruction of the identity verification session.

[0080] Specifically, the verification module 402 needs to verify whether the payment time of the payment information is consistent with the specified time of the payment instruction; verify whether the payment amount of the payment information is consistent with the specified amount of the payment instruction; and verify whether the payment account of the payment information is consistent with the specified bank account of the payment instruction. Only when all the above three verification parameters are consistent, the verification module 402 can determine that the payment information is consistent with the payment instruction of the identity verification session.

[0081] In another possible scenario, the target user cannot complete the reverse payment operation required by the payment instruction within the validity period of the identity verification session. After the identity verification session reaches its validity period, the identity verification session is closed.

[0082] After the target user completes the reverse payment operation required by the payment instruction, it is necessary to initiate a payment verification request for the business to be handled in the verification module 402. In response to the payment verification request initiated by the target user, the verification module 402 initiates a payment verification session, and obtains the payment information input by the target user in the payment verification session, which includes the payment account, payment amount, remarks and other information.

[0083] The verification module 402 matches the payment information with the payment information generated by the verification account to determine whether the payment behavior of the target user exists. Specifically, the verification module 402 needs to verify whether the payment account in the payment information is consistent with the payment account in the payment information, whether the payment amount in the payment information is consistent with the payment amount in the payment information, and whether the remark information in the payment information is consistent with the remark in the payment information. Only when all the above information is consistent, can the verification module 402 determine that the payment behavior of the target user is real.

[0084] When the verification module 402 initiates the payment verification session, it will also assign a session scenario identifier to the payment verification session based on the business that the target user needs to handle. Since the session scenario identifier is related to the business that the user needs to handle and the user identity, the session scenario identifier for the same user's session regarding the same business scenario is consistent. Based on this principle, the verification module 402 can use the session scenario identifier to locate the target user's last closed identity verification session. Specifically, the verification module 402 can search for an identity verification session with the same session scenario identifier based on the session scenario identifier of this payment verification session.

[0085] After locating the last closed identity verification session of the target user, the verification module 402 can obtain the payment instruction from the identity verification session. And compare the payment instruction with the payment information found according to the payment information input by the target user for consistency. Specifically, the verification module 402 needs to compare whether the time specified in the payment instruction is consistent with the payment time of the payment information, that is, to determine whether the payment behavior of the target user exceeds the payment period specified in the payment instruction. It is also necessary to compare whether the payment amount of the payment information is consistent with the specified amount of the payment instruction, and whether the payment account of the payment information is consistent with the specified bank account of the payment instruction. Only when it is verified that the above information is consistent, can the verification module 402 determine that the payment information is consistent with the payment instruction in the identity verification session.

[0086] In some more specific implementations, the verification module 402 can also mark each verified payment information. Specifically, each time the verification module 402 verifies a payment information, it marks the payment information with a mark, and the mark is used to indicate that the payment information has been verified, so as to avoid the same payment information being verified multiple times. Based on the mark of the payment information, the verification module 402 can verify whether the payment information has been verified before verifying the consistency between the payment information and the payment instruction. If the payment information has been verified, it is determined that the identity verification of the target user has failed. If the payment information has not been verified, the consistency of the payment information and the payment instruction continues to be verified.

[0087] With respect to the above-mentioned determination module 403, the verification module 402 may specifically determine whether the identity of the target user is verified by: If the verification result is that the payment information is consistent with the payment instruction, the target user's identity is determined to have passed the identity verification, and the third-party financial platform continues the operation or business to be processed by the target user. If the verification result is that the payment information is inconsistent with the payment instruction, the target user's identity is determined to have failed the identity verification.

[0088] When the determination module 403 determines that the identity of the target user fails the identity verification in this identity verification, the front-end business system of the third-party financial platform can be triggered to terminate the operation or business to be processed by the target user, and notify the response module 401 to re-initiate the identity verification process for the target user. If the number of times that the target user fails the identity verification within a preset time period reaches a preset threshold, the determination module 403 can also mark the account information of the target user to determine whether it is a malicious attack operation, so as to perform corresponding defense operations and early warning processing.

[0089] For the above-mentioned identity verification device, taking the module as an example of a software functional unit, the response module 401 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the response module 401 may include code running on multiple hosts / virtual machines / containers. The multiple hosts / virtual machines / containers used to run the code may be distributed in the same region (region) or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple data centers with close geographical locations. Among them, usually a region may include multiple AZs.

[0090] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

[0091] As an example of a hardware functional unit, the response module 401 may include at least one computing device, such as a server, etc. Alternatively, the response module 401 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0092] The multiple computing devices included in the response module 401 can be distributed in the same region or in different regions. The multiple computing devices included in the response module 401 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the response module 401 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0093] In other embodiments, the response module 401 can be used to execute any step in the above-mentioned identity verification method, the verification module 402 can be used to execute any step in the above-mentioned identity verification method, and the determination module 403 can be used to execute any step in the above-mentioned identity verification method.

[0094] The steps implemented by the response module 401, verification module 402 and determination module 403 can be specified as needed. The response module 401, verification module 402 and determination module 403 respectively implement different steps in the above-mentioned identity verification method to achieve all the functions of the above-mentioned identity verification device.

[0095] In this implementation, the identity verification device can also be applied to computing devices such as computers and servers, or to a computing device cluster including at least one computing device, to implement an identity verification function.

[0096] Corresponding to the above-mentioned business handling method, one or more embodiments of this specification also propose a business handling device, which is suitable for a third-party financial platform. Figure 5 , Figure 51 is a schematic diagram of the structure of a business processing device proposed in one or more embodiments of this specification. The device can be used to implement the above-mentioned business processing method. It should be noted that the business processing method described in one or more embodiments of this application can rely on Figure 5 The business processing device shown is implemented, but not limited to this device.

[0097] like Figure 5 As shown, the business processing device includes: The data acquisition module 501 is configured to acquire a user's service processing request for a target service.

[0098] The risk assessment module 502 is configured to respond to a user's service handling request for a target service and perform risk assessment on the target service.

[0099] The identity verification module 503 is configured to verify the identity of the user using the above-mentioned identity verification method in response to the risk assessment module 502 assessing that the target business has risks.

[0100] The business processing module 504 is configured to continue the processing process of the target business in response to the risk assessment module 502 assessing that the target business does not have any risk.

[0101] The business processing module 504 is also configured to terminate the processing process of the target business in response to the risk assessment module 502 assessing that the target business has risks; and to continue the processing process of the target business when the identity verification module 503 passes the identity verification of the user; and to terminate the processing process of the target business when the identity verification module 503 fails the identity verification of the user.

[0102] Regarding the above-mentioned risk assessment module 502, the risk assessment module 502 may set a risk identification scheme for identifying whether an operation or a business has risks according to needs, and this embodiment does not limit this.

[0103] Regarding the identity verification module 503, the identity verification method used in the identity verification module 503 is described in detail in the above Figure 1 The identity verification method shown in the figure is introduced in the figure, and will not be repeated here. When the identity verification module 503 fails to verify the identity of the user, the identity verification process for the target user can be re-initiated. If the number of times that the target user fails to pass the identity verification within the preset time period reaches a preset threshold, the identity verification module 503 can trigger the business processing module 504 to mark the account information of the target user to determine whether it is a malicious attack operation, so as to perform corresponding defense operations and early warning processing.

[0104] For the above-mentioned business processing device, taking a module as an example of a software functional unit, the data acquisition module 501 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the data acquisition module 501 may include code running on multiple hosts / virtual machines / containers. The multiple hosts / virtual machines / containers used to run the code may be distributed in the same region (region) or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple data centers with close geographical locations. Among them, usually a region may include multiple AZs.

[0105] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

[0106] As an example of a hardware functional unit, the data acquisition module 501 may include at least one computing device, such as a server, etc. Alternatively, the data acquisition module 501 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0107] The multiple computing devices included in the data acquisition module 501 can be distributed in the same region or in different regions. The multiple computing devices included in the data acquisition module 501 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the data acquisition module 501 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0108] In other embodiments, the data acquisition module 501 can be used to execute any step in the above-mentioned business processing method, the risk assessment module 502 can be used to execute any step in the above-mentioned business processing method, the identity verification module 503 can be used to execute any step in the above-mentioned business processing method, and the business processing module 504 can be used to execute any step in the above-mentioned business processing method.

[0109] The steps that the data acquisition module 501, risk assessment module 502, identity verification module 503 and business processing module 504 are responsible for implementing can be specified as needed. The data acquisition module 501, risk assessment module 502, identity verification module 503 and business processing module 504 respectively implement different steps in the above-mentioned business processing method to achieve all the functions of the above-mentioned business processing device.

[0110] In this implementation, the business processing apparatus may also be applied to computing devices such as computers and servers, or to a computing device cluster including at least one computing device, to implement business processing functions.

[0111] In some embodiments, a computer-readable storage medium is also provided, on which a computer program is stored. When the computer program is executed by a processor, it implements the above-mentioned identity verification method, or implements the above-mentioned business processing method.

[0112] The computer-readable storage medium may be any available medium that can be stored by the electronic device or a data storage device such as a data center that includes one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the electronic device to execute the above-mentioned identity verification method or the above-mentioned business handling method.

[0113] This embodiment also provides an electronic device, including: One or more processors; and a memory associated with the one or more processors, the memory being used to store program instructions, which, when read and executed by the one or more processors, implement one of the above-mentioned identity verification methods, or implement one of the above-mentioned business processing methods.

[0114] Please refer to Figure 6 , Figure 6 A structural schematic diagram of the above-mentioned electronic device is shown. The electronic device includes a bus 601, a processor 602, a memory 603 and a communication interface 604. The memory 603 stores a computer program. When the computer program runs on the processor 602, the processor 602 executes the specific steps in the above-mentioned identity verification method, or executes the specific steps in the above-mentioned business handling method. It should be understood that the present application does not limit the number of processors and memories in the electronic device.

[0115] The bus 601 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus 601 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 The bus 601 is represented by only one line, but it does not mean that there is only one bus or one type of bus. The bus 601 may include a path for transmitting information between various components of the terminal device (for example, the processor 602, the memory 603 and the communication interface 604).

[0116] The processor 602 may include any one or more of a processor such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0117] The memory 603 may include a volatile memory, such as a random access memory (RAM). The memory 603 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0118] The communication interface 604 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the electronic device and other devices or a communication network.

[0119] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than that here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

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

[0121] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0122] It should be noted that the above examples are only specific embodiments of the present invention. Obviously, the present invention is not limited to the above examples, and there are many similar variations. All variations directly derived or associated from the contents disclosed by the technicians in this field should fall within the protection scope of the present invention.

Claims

1. An identity verification method, applicable to a third-party financial platform, comprising: In response to the identity verification request initiated for the target user, a remittance instruction is issued to the target user; the remittance instruction is used to prompt the target user to remit a specified amount of money to the verification account opened by the third-party financial platform in the bank through a designated bank account within a designated time; the designated bank account is a bank account with the same name that is bound to the third-party account opened by the target user on the third-party financial platform; In response to the target user confirming that the payment has been made, obtaining payment information of the verification account, and verifying the consistency between the payment information and the payment instruction; Based on the consistency verification result of the payment information and the payment instruction, it is determined whether the identity of the target user has been verified.

2. The method according to claim 1, in response to an identity verification request initiated for a target user, issuing a payment instruction to the target user, specifically comprising: In response to an identity verification request initiated for the target user, an identity verification session is initiated to the target user, and based on the service to be handled by the target user, a session scenario identifier is allocated to the identity verification session; The payment instruction is issued to the target user in the identity verification session.

3. The method according to claim 2, in response to the target user confirming that the payment has been made, obtaining the payment information generated by the verification account, and verifying the consistency between the payment information and the payment instruction, specifically comprising: In response to the target user confirming that the payment has been made within the validity period of the identity verification session, the payment receipt information of the verification account within the validity period of the identity verification session is obtained, and the consistency of the payment receipt information and the payment instruction is verified; the deadline of the identity verification session is less than the specified time of the payment instruction.

4. The method according to claim 2, in response to the target user confirming that the payment has been made, obtaining the payment information generated by the verification account, and verifying the consistency between the payment information and the payment instruction, specifically comprising: If the target user does not confirm that the payment has been made within the validity period of the identity verification session, the identity verification session is terminated; The deadline of the identity verification session is less than the specified time of the payment instruction; In response to the target user initiating a payment verification request, initiating a payment verification session, and allocating a session scenario identifier to the payment verification session based on the business to be handled by the target user; Acquiring payment information input by the user in the payment verification session; Match the payment information with the payment information generated by the verification account to determine the payment information corresponding to the payment information; According to the session scenario identifier of the payment verification session, searching for an identity verification session with the same session scenario identifier, and obtaining a payment instruction in the identity verification session; Verify the consistency between the payment information and the payment instruction in the identity verification session.

5. According to the method of claim 1, verifying the consistency between the payment information and the payment instruction specifically comprises: Verify whether the payment time of the payment information is consistent with the specified time of the payment instruction; Verify whether the amount of the payment received in the payment information is consistent with the amount specified in the payment instruction; Verify whether the payment account in the payment information is consistent with the designated bank account in the payment instruction.

6. The method according to claim 1, further comprising: Before verifying the consistency between the payment information and the payment instruction, verifying whether the payment information has been verified; If the payment information has been verified, it is determined that the identity verification of the target user has failed; If the payment information has not been verified, the consistency between the payment information and the payment instruction is verified.

7. A business handling method, applicable to a third-party financial platform, comprising: In response to a user's request for handling a target business, performing a risk assessment on the target business; If the target business does not have any risk, continue the processing of the target business; If the target business is at risk, the processing of the target business is terminated, and the identity of the user is verified using the method described in any one of claims 1 to 6; In response to the identity verification of the user being passed, continuing the processing process of the target business; In response to the user's identity verification failing, the handling process of the target service is terminated.

8. An identity verification device, applicable to a third-party financial platform, comprising: a response module configured to issue a payment instruction to the target user in response to an identity verification request initiated for the target user; the payment instruction is used to prompt the target user to transfer a specified amount of money to the verification account opened by the third-party financial platform in the bank through a designated bank account within a designated time; the designated bank account is a bank account with the same name bound to the third-party account opened by the target user on the third-party financial platform; A verification module, configured to obtain payment information of the verification account in response to the target user confirming that the payment has been made, and to verify the consistency between the payment information and the payment instruction; The determination module is configured to determine whether the identity of the target user has been verified based on the consistency verification result between the payment information and the payment instruction.

9. The device according to claim 8, wherein the response module is specifically configured to: In response to an identity verification request initiated for the target user, an identity verification session is initiated to the target user, and based on the service to be handled by the target user, a session scenario identifier is allocated to the identity verification session; The payment instruction is issued to the target user in the identity verification session.

10. The device according to claim 9, wherein the verification module is specifically used for: In response to the target user confirming that the payment has been made within the validity period of the identity verification session, the payment receipt information of the verification account within the validity period of the identity verification session is obtained, and the consistency of the payment receipt information and the payment instruction is verified; the deadline of the identity verification session is less than the specified time of the payment instruction.

11. The device according to claim 9, wherein the verification module is specifically used for: If the target user does not confirm that the payment has been made within the validity period of the identity verification session, the identity verification session is terminated; the end time of the identity verification session is less than the specified time of the payment instruction; In response to the target user initiating a payment verification request, initiating a payment verification session, and allocating a session scenario identifier to the payment verification session based on the business to be handled by the target user; Acquiring payment information input by the user in the payment verification session; Match the payment information with the payment information generated by the verification account to determine the payment information corresponding to the payment information; According to the session scenario identifier of the payment verification session, searching for an identity verification session with the same session scenario identifier, and obtaining a payment instruction in the identity verification session; Verify the consistency between the payment information and the payment instruction in the identity verification session.

12. The device according to claim 8, wherein the verification module is specifically used for: Verify whether the payment time of the payment information is consistent with the specified time of the payment instruction; Verify whether the amount of the payment received in the payment information is consistent with the amount specified in the payment instruction; Verify whether the payment account in the payment information is consistent with the designated bank account in the payment instruction.

13. The device according to claim 8, wherein the verification module is further configured to: Before verifying the consistency between the payment information and the payment instruction, verifying whether the payment information has been verified; If the payment information has been verified, it is determined that the identity verification of the target user has failed; If the payment information has not been verified, the consistency between the payment information and the payment instruction is verified.

14. A business handling device, applicable to a third-party financial platform, comprising: A data acquisition module configured to acquire a user's business processing request for a target business; a risk assessment module, configured to perform risk assessment on the target business in response to the user's request for handling the target business; an identity verification module, configured to verify the identity of the user using the method according to any one of claims 1 to 6 in response to the risk assessment module assessing that the target business has a risk; A business processing module, configured to continue the processing of the target business in response to the risk assessment module assessing that the target business does not have any risk; The business processing module is also configured to, in response to the risk assessment module evaluating that the target business is risky, terminate the processing process of the target business; and continue the processing process of the target business when the identity verification module passes the identity verification of the user; and, when the identity verification module fails the identity verification of the user, terminate the processing process of the target business.

15. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements the method according to any one of claims 1 to 6, or the method according to claim 7.

16. An electronic device, comprising: one or more processors; And a memory associated with the one or more processors, the memory is used to store program instructions, and when the program instructions are read and executed by the one or more processors, the method according to any one of claims 1 to 6 is executed, or the method according to claim 7 is executed.

Images