Payment verification method and apparatus

Abstract

The application discloses a payment verification method and device, and relates to the technical field of computers. A specific implementation of the method comprises the following steps: receiving an order payment request based on an external payment platform and sent by a client; querying target identity authentication information according to the identifier of an order submitter, and sending a payment calling request to the external payment platform; receiving identity authentication information provided by the client, and sending the identity authentication information to the external payment platform; the identity authentication information is determined by the client after receiving a supplementary recording notification sent by the external payment platform, and the supplementary recording notification is sent by the external payment platform in the case that the target identity authentication information is inconsistent with the identity authentication information of a payer corresponding to the client of the external payment platform. The implementation can solve the payment security and compliance problems caused by inconsistent identity authentication information.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and in particular, to a payment verification method and device. BACKGROUND

[0002] At present, APP (application program of mobile terminal, hereinafter referred to as application program) involving payment function needs to perform identity authentication, and identity authentication states are generally not shared between different application programs. In actual application, when a user uses a current application program to pay, the user may use a third-party payment method supported by the current application program, that is, an external application program is called within the current application program to perform payment, but the identity authentication information of the current application program and the identity authentication information of the external application program are not subjected to consistency verification, and may not be consistent, which may cause the following problems: first, a criminal may use the loophole of not performing consistency verification to push a false link to the user to implement illegal behavior; second, identity authentication information is required to be consistent in specific scenarios such as cross-border trade, and if the identity authentication information is not consistent, a complex processing procedure needs to be performed. SUMMARY

[0003] Therefore, the embodiments of the present application provide a payment verification method and device, which can solve the payment security and compliance problems caused by inconsistent identity authentication information.

[0004] To achieve the above object, according to one aspect of the present application, a payment verification method is provided.

[0005] The payment verification method of the embodiments of the present application is executed by a server; the payment verification method comprises: receiving an order payment request based on an external payment platform and issued by a client, the order payment request carrying an identifier of an order submitter and an identifier of the external payment platform; querying corresponding target identity authentication information according to the identifier of the order submitter, and issuing a payment calling request to the external payment platform by using the identifier of the external payment platform; the payment calling request carrying the target identity authentication information; receiving supplementary identity authentication information provided by the client, and sending the supplementary identity authentication information to the external payment platform; wherein the supplementary identity authentication information is determined by the client after receiving a supplementary notification issued by the external payment platform, and the supplementary notification is issued by the external payment platform in a case that the target identity authentication information is inconsistent with identity authentication information of a payer corresponding to the client of the external payment platform.

[0006] Optionally, the payment verification method further comprises: after receiving the supplementary identity authentication information provided by the client, storing a mapping relationship between the supplementary identity authentication information and the identifier of the order submitter.

[0007] Optionally, the target identity authentication information corresponding to the order submitter is queried according to the identity of the order submitter, including: after receiving the order payment request, it is queried whether the identity authentication information of the order submitter corresponding to the supplementary record is stored in advance; if the identity authentication information of the supplementary record is not stored, the identity authentication information of the order submitter in the preset at least one attribute is determined as the target identity authentication information; if the identity authentication information of the supplementary record is stored, the identity authentication information of the order submitter in the attribute of the latest supplementary record is determined as the target identity authentication information.

[0008] Optionally, the external payment platform continues the remaining payment process when the target identity authentication information is consistent with the identity authentication information of the payer corresponding to the client of the external payment platform.

[0009] Optionally, the payment verification method further includes: after the target identity authentication information corresponding to the order submitter is queried according to the identity of the order submitter, the target identity authentication information queried is subjected to first privacy processing based on a preset privacy algorithm, and the target identity authentication information subjected to the first privacy processing is carried in the payment call request; and the external payment platform, after obtaining the target identity authentication information subjected to the first privacy processing, subjects the identity authentication information of the payer in the attribute to second privacy processing based on the privacy algorithm; and the verification of whether the target identity authentication information is consistent with the identity authentication information of the payer corresponding to the client of the external payment platform includes: verification of whether the target identity authentication information subjected to the first privacy processing is consistent with the identity authentication information of the payer in the attribute subjected to the second privacy processing.

[0010] Optionally, the external payment platform forwards the supplementary record notification to the client based on the server, or the external payment platform directly sends the supplementary record notification to the client.

[0011] Optionally, the external payment platform verifies whether the identity authentication information of the supplementary record is consistent with the identity authentication information of the payer corresponding to the client of the external payment platform; if consistent, the remaining payment process is continued; if not consistent, a re-supplementary record notification or an end of the payment process is returned to the client.

[0012] Optionally, the attribute includes at least one of the following: name, identity card number.

[0013] To achieve the above-mentioned purpose, according to another aspect of the present application, a payment verification method is provided.

[0014] The payment verification method of the embodiment of the application is executed by the client; the payment verification method comprises: sending an order payment request based on an external payment platform to a server, the order payment request carrying an identifier of an order submitter and an identifier of the external payment platform; receiving a supplementary recording notification; wherein the supplementary recording notification is sent by the external payment platform in a case that target identity authentication information is inconsistent with identity authentication information of a payment person corresponding to the client of the external payment platform, the target identity authentication information is queried by the server according to the identifier of the order submitter after receiving the order payment request, and the external payment platform obtains the target identity authentication information from a payment calling request sent by the server based on the identifier of the external payment platform; determining supplementary recorded identity authentication information and sending the supplementary recorded identity authentication information to the server to perform verification of whether the supplementary recorded identity authentication information is consistent with the identity authentication information of the payment person by the external payment platform.

[0015] To achieve the above object, according to another aspect of the application, a payment verification method is provided.

[0016] The payment verification method of the embodiment of the application is executed by the server; the payment verification method comprises: receiving an order payment request based on an external payment platform sent by a client, the order payment request carrying an identifier of an order submitter and an identifier of the external payment platform; querying corresponding target identity authentication information according to the identifier of the order submitter, and sending an identity authentication notification to the external payment platform by using the identifier of the external payment platform; receiving identity authentication information of a payment person corresponding to the client of the external payment platform sent by the external payment platform, and verifying whether the target identity authentication information is consistent with the identity authentication information of the payment person; if not, sending a supplementary recording notification to the client to obtain supplementary recorded identity authentication information provided by the client.

[0017] To achieve the above object, according to another aspect of the application, a payment verification method is provided.

[0018] The payment verification method of the embodiment of the application is executed by the client; the payment verification method comprises: sending an order payment request based on an external payment platform to a server, the order payment request carrying an identifier of an order submitter and an identifier of the external payment platform; receiving a supplementary recording notification; wherein the supplementary recording notification is sent by the external payment platform in a case that target identity authentication information is inconsistent with identity authentication information of a payment person corresponding to the client of the external payment platform, the target identity authentication information is queried by the server according to the identifier of the order submitter after receiving the order payment request, and the external payment platform obtains the target identity authentication information from a payment calling request sent by the server based on the identifier of the external payment platform; determining supplementary recorded identity authentication information and sending the supplementary recorded identity authentication information to the server to perform verification of whether the supplementary recorded identity authentication information is consistent with the identity authentication information of the payment person by the external payment platform.

[0019] To achieve the above object, according to another aspect of the present application, a payment verification device is provided.

[0020] The payment verification device of the embodiment of the present application is arranged at a server; the payment verification device comprises: a receiving unit configured to receive an order payment request based on an external payment platform sent by a client, the order payment request carrying an identifier of an order submitter and an identifier of the external payment platform; a querying unit configured to query corresponding target identity authentication information according to the identifier of the order submitter, and send a payment calling request to the external payment platform by using the identifier of the external payment platform; the payment calling request carrying the target identity authentication information; a supplementary recording unit configured to receive supplementary recorded identity authentication information provided by the client, and send the supplementary recorded identity authentication information to the external payment platform; wherein the supplementary recorded identity authentication information is determined by the client after receiving a supplementary recording notification sent by the external payment platform, and the supplementary recording notification is sent by the external payment platform in a case that the target identity authentication information is inconsistent with identity authentication information of a payer corresponding to the client of the external payment platform.

[0021] To achieve the above object, according to another aspect of the present application, a payment verification device is provided.

[0022] The payment verification device of the embodiment of the present application is arranged at a client; the payment verification device comprises: a request sending unit configured to send an order payment request based on an external payment platform to a server, the order payment request carrying an identifier of an order submitter and an identifier of the external payment platform; a notification receiving unit configured to receive a supplementary recording notification; wherein the supplementary recording notification is sent by the external payment platform in a case that target identity authentication information is inconsistent with identity authentication information of a payer corresponding to the client of the external payment platform, the target identity authentication information is queried by the server according to the identifier of the order submitter after receiving the order payment request, and the external payment platform obtains the target identity authentication information from a payment calling request sent by the server based on the identifier of the external payment platform; a supplementary recording sending unit configured to determine supplementary recorded identity authentication information and send the supplementary recorded identity authentication information to the server, so as to perform a verification of whether the supplementary recorded identity authentication information is consistent with the identity authentication information of the payer by the external payment platform.

[0023] To achieve the above object, according to another aspect of the present application, an electronic device is provided.

[0024] The electronic device of the present application comprises: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the payment verification method provided by the present application.

[0025] To achieve the above object, according to another aspect of the present application, a computer readable storage medium is provided.

[0026] The computer readable storage medium of the present application stores a computer program, and the program is executed by a processor to implement the payment verification method provided by the present application.

[0027] According to the technical solution of the present application, the embodiments of the above application have the following advantages or beneficial effects:

[0028] After the server receives the order payment request based on the external payment platform sent by the client, the target identity authentication information corresponding to the order submitter identifier carried in the request is queried, and then the consistency check of the target identity authentication information and the identity authentication information of the payer corresponding to the client of the external payment platform is performed by the server or the external payment platform. If the check is consistent, the payment process is executed; if the check is inconsistent, the client performs identity authentication information supplement, and the server or the external payment platform performs consistency check of the identity authentication information again until the check is consistent, and then the payment process is executed. In this way, through the identity authentication information supplement in the payment process, the consistency check of the identity authentication information between the current platform (client, server) and the external payment platform in the payment process is realized, thereby forming a safer third-party payment method, solving the payment security and compliance problems caused by inconsistent identity authentication information, and preventing payment loopholes and business obstruction caused by inconsistent identity authentication information.

[0029] The further effects of the above-mentioned non-conventional optional mode will be described in conjunction with the specific embodiments below. BRIEF DESCRIPTION OF DRAWINGS

[0030] The accompanying drawings serve to better understand the present application and do not constitute an improper limitation on the present application. Among them:

[0031] Figure 1 is the main step schematic diagram of the payment verification method in the first embodiment of the present application;

[0032] Figure 2 is the interaction schematic diagram of the payment verification method in the first embodiment of the present application;

[0033] Figure 3 is the flowchart of the payment verification method in the first embodiment of the present application;

[0034] Figure 4 is the main step schematic diagram of the payment verification method in the second embodiment of the present application;

[0035] Figure 5 is the interaction schematic diagram of the payment verification method in the second embodiment of the present application;

[0036] Figure 6 is the component part schematic diagram of the payment verification device in the third embodiment of the present application;

[0037] Figure 7 is a schematic diagram of a component of the payment verification device in the fourth embodiment of the present application;

[0038] Figure 8 is a schematic diagram of a component of the payment verification device in the fifth embodiment of the present application;

[0039] Figure 9 is a schematic diagram of a component of the payment verification device in the sixth embodiment of the present application;

[0040] Figure 10 is an exemplary system architecture diagram to which embodiments of the present application can be applied;

[0041] Figure 11 is a schematic diagram of an electronic device structure for implementing the payment verification method in embodiments of the present application. DETAILED DESCRIPTION

[0042] Exemplary embodiments of the present application are described below with reference to the accompanying drawings, which include various details of the embodiments of the present application to assist in understanding them. These should be considered in their context only. Thus, those of ordinary skill in the art will recognize various changes and modifications of the embodiments described herein, without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and structures are omitted in the following description for clarity and conciseness.

[0043] It should be noted that the embodiments of the present application and the technical features in the embodiments can be combined with each other without conflict.

[0044] Figure 1 is a schematic diagram of the main steps of the payment verification method in the first embodiment of the present application.

[0045] As shown in Figure 1 , the payment verification method of the embodiments of the present application can be executed by a server, and the server and the client correspond to a platform (hereinafter referred to as a current platform) currently operated by a user. The current platform can be any platform with payment function, and the following description takes an e-commerce platform as an example. The user can perform payment based on a third-party payment platform (hereinafter referred to as an external payment platform) on the client side. The payment verification method executed by the server has the following specific execution steps:

[0046] Step S101: The server receives an order payment request based on the external payment platform sent by the client. The order payment request carries the identity of the order submitter (i.e. the person who places an order) and the identity of the external payment platform.

[0047] Step S102: The server queries the corresponding target identity authentication information according to the identifier of the order submitter, and sends a payment calling request to the external payment platform by using the identifier of the external payment platform; the target identity authentication information is carried in the payment calling request.

[0048] Step S103: The server receives the supplemented identity authentication information provided by the client, and sends the supplemented identity authentication information to the external payment platform. The supplemented identity authentication information is determined by the client after receiving a supplement notification sent by the external payment platform, and the supplement notification is sent by the external payment platform in the case that the target identity authentication information is inconsistent with the identity authentication information of the payer of the client corresponding to the external payment platform.

[0049] In the technical solution of the embodiment, the consistency check of the identity authentication information is performed by the external payment platform, and if the check is successful, the payment process is performed; if the check fails (i.e., the identity authentication information is inconsistent), the client is sent a supplement notification, the client transmits the supplemented identity authentication information to the external payment platform through the server for re-checking, and only if the check is successful (i.e., the identity authentication information is consistent) does the payment process is performed, thereby solving the payment security and compliance problems caused by inconsistent identity authentication information.

[0050] Figure 2 is the interaction schematic diagram of the payment verification method in the first embodiment of the application, see Figure 2 .

[0051] Step S201: The client sends an order payment request to the server according to the payment operation of the user. In an optional manner, the user operates the client (such as a mobile terminal application) of the current platform, selects a third-party payment method corresponding to the external payment platform in the checkout, clicks the payment button, and sends an order payment request to the server. The above order can include any object (including physical goods and information objects) to which payment is directed in various transaction scenarios, such as a shopping order in an e-commerce scenario, a consultation order in an Internet medical scenario, etc., and can also represent specific goods or specific information objects to which payment is directed. In actual application, the order payment request can carry the identifier of the order submitter and the identifier of the external payment platform, and the above order submitter refers to the person who places an order.

[0052] Step S202: After receiving the order payment request, the server locally queries the corresponding target identity authentication information according to the order submitter's identifier. It can be understood that the server locally pre-stores the mapping relationship between the target identity authentication information and the order submitter identifier, and the target identity authentication information can be uploaded by the client, for example, based on the POST request of the HyperText Transfer Protocol Secure (HTTPS) interface. In this embodiment, the identity authentication information can be information of at least one preset attribute, and the above attributes can be configured as needed, for example, configured as name and ID number, or configured as name, gender and ID number. Preferably, before the client uploads the target identity authentication information, irreversible pre-privacy processing (such as using a hash algorithm) can be performed on the target identity authentication information of each attribute to avoid data leakage.

[0053] Step S203: The server sends a payment calling request to the external payment platform using the identifier of the external payment platform, and the target identity authentication information is carried in the payment calling request. In order to ensure information security, after querying the corresponding target identity authentication information according to the order submitter's identifier, the server can perform first privacy processing on the queried target identity authentication information based on a preset privacy algorithm, and send the target identity authentication information after the first privacy processing to the external payment platform in the payment calling request. For example, the target identity authentication information of the two attributes of name and ID number is pre-processed by the client using the MD5 algorithm before being sent to the server by the client, and the server can concatenate the pre-privacy processing results of the two attributes and perform the SHA256 algorithm (irreversible first privacy processing) to obtain the target identity authentication information after the first privacy processing.

[0054] Step S204: After receiving the payment calling request, the external payment platform obtains the target identity authentication information carried in the request, and locally obtains the identity authentication information of the payer of the client corresponding to the external payment platform, where the payer refers to the payer pre-configured in the external payment platform, and the identity authentication information of the payer is pre-stored in the local of the external payment platform. It can be understood that the privacy processing logic of the payer identity authentication information is consistent with that of the target identity authentication information, and the external payment platform can perform the same pre-privacy processing as the client before storing the payer identity authentication information.

[0055] Step S205: The external payment platform checks whether the payment person's identity authentication information is consistent with the target identity authentication information. It can be understood that if the target identity authentication information is pre-processed by the above first privacy processing, the external payment platform can perform irreversible second privacy processing on the payment person's identity authentication information in each attribute based on the same privacy algorithm after obtaining the target identity authentication information processed by the first privacy processing. Correspondingly, the consistency check above refers to checking whether the target identity authentication information processed by the first privacy processing is consistent with the payment person's identity authentication information in each attribute processed by the second privacy processing.

[0056] Step S206: If the check is consistent, the external payment platform returns the normal acquirers request parameter to execute the normal payment process; if the check is inconsistent, the external payment platform sends a supplementary record notice to the client. Optionally, if the check is inconsistent, the external payment platform can return a specific error code such as "userError" to the client. In actual application, the external payment platform can forward the supplementary record notice to the client through the server, and the external payment platform also sends the supplementary record notice directly to the client.

[0057] Step S207: After receiving the supplementary record notice, the client sends a prompt to the user to make the user supplement the identity authentication information. For example, the client shows the user relevant policy instructions and a supplementary record interface, and the user inputs new identity authentication information in the supplementary record interface. In a specific scenario, after the user inputs the name and ID number in the supplementary record interface, the correctness check can be performed based on the local judgment logic, and the correctness check passes only if the supplementary record is successful. For example, by checking that the name cannot be an empty character, the ID number is 15 or 18 digits, and the last digit is a number or character X. Preferably, the client can perform the same pre-privacy processing after obtaining the user's supplementary identity authentication information.

[0058] Step S208: The client sends the supplementary identity authentication information to the server. Step S209: After receiving the supplementary identity authentication information provided by the client, the server can store the mapping relationship between the supplementary identity authentication information and the identifier of the order submitter, and send the supplementary identity authentication information to the external payment platform to perform the consistency check again.

[0059] For the same order submitter, the server can store the unique identity authentication information of the order submitter (in this case, no overwriting has occurred), or can additionally store the identity authentication information of one or more overwritings (overwriting can be performed once or multiple times), therefore, in an optional technical solution, the query target identity authentication information in step S202 can be performed according to the following steps: after receiving the order payment request, the server queries whether the identity authentication information of the overwriting corresponding to the identifier of the order submitter is pre-stored; if the identity authentication information of the overwriting is not stored, the server determines the identity authentication information of the order submitter in the pre-set at least one attribute as the target identity authentication information; if the identity authentication information of the overwriting is stored, the server determines the attribute identity authentication information of the latest overwriting of the order submitter as the target identity authentication information. In this way, the latest identity authentication information can be directly queried when the user uses the third-party payment to perform consistency verification, thereby avoiding the use of invalid identity authentication information to affect the payment process.

[0060] Step S210: The external payment platform verifies whether the overwriting identity authentication information is consistent with the identity authentication information of the payer. Preferably, before consistency verification, the external payment platform can perform the same privacy processing on the two kinds of identity authentication information respectively.

[0061] Step S211: If the external payment platform verifies that the consistency is correct, it returns a normal acquirer request parameter to execute the remaining payment process; if the consistency is incorrect, it returns an overwriting notification to the client again or ends the payment process.

[0062] Through the overwriting of the identity authentication information in the payment process, the consistency verification of the identity authentication information between the local platform and the external payment platform in the payment process can be realized, thereby forming a safer third-party payment method, solving the payment security and compliance problems caused by inconsistent identity authentication information, and preventing payment loopholes and business obstructions caused by inconsistent identity authentication information.

[0063] Figure 3 is a flowchart of the payment verification method in the first embodiment of the present application. As shown in Figure 3As shown, the user selects the third-party payment method in the client to initiate an order payment request, the server responds to the request to call the third-party payment service to the external payment platform, the external payment platform first checks whether the identity authentication information is consistent: if consistent, execute the normal payment process; if not consistent, return the error code of consistency check failure to the client. After the client parses the error code, it jumps to the supplementary recording page to perform identity authentication information supplementary recording, and submits the supplementary recorded identity authentication information to the server. The server caches the supplementary recorded identity authentication information locally, returns the identity authentication information update success notification to the client, and the client continues to initiate the order payment request after receiving the notification, the server calls the latest supplementary recorded identity authentication information from the cache to continue to call the third-party payment service, and the external payment platform continues to perform the consistency check of the identity authentication information, and executes the payment process after the check is successful.

[0064] The following describes the payment verification process performed by the client in the first embodiment. The payment verification method performed by the client includes: sending an order payment request based on the external payment platform to the server, the order payment request carrying the identity of the order submitter and the identity of the external payment platform; receiving a supplementary recording notification; wherein the supplementary recording notification is sent by the external payment platform in the case that the target identity authentication information is inconsistent with the identity authentication information of the payer corresponding to the client of the external payment platform, the target identity authentication information is queried by the server according to the identity of the order submitter after receiving the order payment request, and the target identity authentication information is obtained by the external payment platform from the payment calling request sent by the server based on the identity of the external payment platform; determining the supplementary recorded identity authentication information and sending it to the server to check whether the supplementary recorded identity authentication information is consistent with the identity authentication information of the payer in the external payment platform.

[0065] Preferably, in the case that the target identity authentication information is consistent with the identity authentication information of the payer corresponding to the client of the external payment platform, the client continues the remaining payment process.

[0066] As a preferred solution, if the supplementary recorded identity authentication information is consistent with the identity authentication information of the payer corresponding to the client of the external payment platform, the client continues the remaining payment process; if not consistent, the client receives a re-supplementary recording notification or an end payment notification.

[0067] Figure 4 is the main step schematic diagram of the payment verification method in the second embodiment of the application, and the difference between the second embodiment and the first embodiment is that: the step of identity authentication information consistency check in the second embodiment is performed by the server. As shown in Figure 4 The payment verification method performed by the server in the second embodiment includes the following steps.

[0068] Step S401: The server receives an order payment request based on an external payment platform sent by the client, and the order payment request carries an identifier of an order submitter and an identifier of the external payment platform; step S402: The server queries corresponding target identity authentication information according to the identifier of the order submitter, and sends an identity authentication notification to the external payment platform by using the identifier of the external payment platform; step S403: The server receives identity authentication information of a payer corresponding to the client sent by the external payment platform, and checks whether the target identity authentication information is consistent with the identity authentication information of the payer; if not, a reentry notification is sent to the client to obtain reentry identity authentication information provided by the client.

[0069] Figure 5 is an interaction schematic diagram of the payment verification method in the second embodiment of the application, referring to Figure 5 .

[0070] Step S501: The client sends an order payment request to the server according to a payment operation of a user. In an optional manner, the user operates the client of the current platform, selects a third-party payment method corresponding to the external payment platform at a cash desk, clicks a payment button, and sends an order payment request to the server. In actual application, the order payment request can carry an identifier of an order submitter and an identifier of the external payment platform, and the above order submitter refers to an orderer.

[0071] Step S502: After receiving the order payment request, the server queries corresponding target identity authentication information according to the identifier of the order submitter locally. It can be understood that the server locally pre-stores a mapping relationship between the target identity authentication information and the identifier of the order submitter, and the target identity authentication information can be pre-uploaded by the client. In this embodiment, the identity authentication information can be information of at least one preset attribute, and the above attribute can be configured as needed, for example, configured as a name and an ID number, or configured as a name, a gender and an ID number. Preferably, before the client uploads the target identity authentication information, irreversible pre-privacy processing (such as using a hash algorithm) can be performed on the target identity authentication information of each attribute to avoid data leakage, and the first privacy processing mentioned above can also be performed on the target identity authentication information.

[0072] Step S503: The server sends an identity authentication notification to the external payment platform by using the identifier of the external payment platform. Step S504: After receiving the identity authentication notification, the external payment platform obtains pre-stored payer identity authentication information. As a preferred manner, the external payment platform can first perform the same pre-privacy processing before storing the payer identity authentication information. Step S505: The external payment platform returns the payer identity authentication information to the server. Step S506: The server receives the payer identity authentication information.

[0073] Step S507: The server verifies whether the payer's identity authentication information is consistent with the target identity authentication information. It can be understood that if the target identity authentication information has undergone the first privacy processing described above beforehand, then after obtaining the pre-privacy-processed payer identity authentication information, the server can perform the second privacy processing on the payer's identity authentication information for each attribute based on the same privacy algorithm. Accordingly, the consistency verification above refers to verifying whether the target identity authentication information processed with the first privacy processing is consistent with the payer's identity authentication information for each attribute processed with the second privacy processing.

[0074] Step S508: If the verification matches, the server interacts with the client to execute the normal payment process; if the verification fails, the server sends a supplementary information notification to the client. Optionally, if the verification fails, the server may return a specific error code such as "userError" to the client.

[0075] Step S509: The client performs identity authentication information supplementation. Step S510: The client sends the supplemented identity authentication information to the server. Step S511: After receiving the supplemented identity authentication information, the server stores the mapping relationship between the supplemented identity authentication information and the order submitter's identifier, and re-verifies the consistency between the supplemented identity authentication information and the payer's identity authentication information. Step S512: If the verification matches, the normal payment process is executed; if the verification does not match, the server instructs the client to continue entering identity authentication information or terminate the payment process.

[0076] Preferably, in step S502, after receiving the order payment request, the server queries whether there is pre-stored supplementary identity authentication information corresponding to the order submitter's identifier; if the supplementary identity authentication information is not stored, the order submitter's identity authentication information for at least one preset attribute is determined as the target identity authentication information; if the supplementary identity authentication information is stored, the latest supplementary attribute identity authentication information of the order submitter is determined as the target identity authentication information.

[0077] The following describes the payment verification method executed by the client in the second embodiment, specifically including the following steps: Sending an order payment request based on an external payment platform to the server, the order payment request carrying the identifier of the order submitter and the identifier of the external payment platform; Receiving a supplementary information notification; wherein, the supplementary information notification is issued by the server when the target identity authentication information is inconsistent with the payer's identity authentication information corresponding to the client on the external payment platform. The target identity authentication information is obtained by the server after receiving the order payment request based on the identifier of the order submitter, and the payer's identity authentication information is provided to the server by the external payment platform after receiving the identity authentication notification issued by the server. The server issues the identity authentication notification based on the identifier of the external payment platform; Determining the supplementary identity authentication information and sending it to the server, so that the server can perform a verification on whether the supplementary identity authentication information is consistent with the payer's identity authentication information.

[0078] Preferably, if the server verifies that the target's identity authentication information matches the external payment platform's identity authentication information corresponding to the payer on the client, the client continues the remaining payment process.

[0079] As a preferred option, if the server verifies that the newly entered identity authentication information matches the identity authentication information of the payer on the external payment platform corresponding to the client, the client continues the remaining payment process; if they do not match, the client receives a notification to enter the information again or a notification to end the payment process.

[0080] In the technical solution of this invention, after receiving an order payment request from a client based on an external payment platform, the server queries the corresponding target identity authentication information based on the order submitter identifier carried in the request. Then, the server or the external payment platform performs a consistency check between the target identity authentication information and the external payment platform's identity authentication information corresponding to the payer on the client. If the check matches, the payment process is executed; if the check does not match, the client performs identity authentication information supplementation, and the server or the external payment platform performs the identity authentication information consistency check again until the check matches before executing the payment process. In this way, by supplementing identity authentication information during the payment process, consistency verification of identity authentication information between the current platform (client, server) and the external payment platform is achieved, thereby forming a more secure third-party payment method. This solves payment security and compliance issues caused by inconsistent identity authentication information and prevents payment vulnerabilities and business disruptions due to inconsistent identity authentication information.

[0081] It should be noted that the technical solutions of this invention, including the collection, updating, analysis, processing, use, transmission, and storage of user personal information, all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0082] For the foregoing method embodiments, they are described as a series of actions for ease of description. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, and some steps may actually be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential for implementing the present invention.

[0083] To facilitate better implementation of the above-described solutions of the embodiments of the present invention, related apparatus for implementing the above-described solutions is also provided below.

[0084] Please see Figure 6 As shown, the payment verification device 600 provided in the third embodiment of the present invention is set on the server side and may include: a receiving unit 601, used to receive an order payment request sent by the client based on an external payment platform, wherein the order payment request carries the identifier of the order submitter and the identifier of the external payment platform; a query unit 602, used to query the corresponding target identity authentication information according to the identifier of the order submitter, and send a payment call request to the external payment platform using the identifier of the external payment platform; the payment call request carries the target identity authentication information; and a supplementary recording unit 603, used to receive supplementary identity authentication information provided by the client and send the supplementary identity authentication information to the external payment platform; wherein the supplementary identity authentication information is determined by the client after receiving a supplementary recording notification from the external payment platform, and the supplementary recording notification is issued by the external payment platform when the target identity authentication information is inconsistent with the external payment platform's identity authentication information corresponding to the payer's identity information of the client. The payment verification device of the third embodiment corresponds to the method executed by the server side in the first embodiment.

[0085] In this embodiment of the invention, the payment verification device 600 further includes a storage unit for storing the mapping relationship between the supplemented identity authentication information and the identifier of the order submitter after receiving the supplemented identity authentication information provided by the client.

[0086] Preferably, the query unit 602 is further configured to: after receiving an order payment request, query whether there is pre-stored supplementary identity authentication information corresponding to the identifier of the order submitter; if the supplementary identity authentication information is not stored, determine the identity authentication information of the order submitter in at least one preset attribute as the target identity authentication information; if the supplementary identity authentication information is stored, determine the latest supplementary attribute identity authentication information of the order submitter as the target identity authentication information.

[0087] In one embodiment, if the external payment platform verifies that the target identity authentication information matches the payer's identity authentication information corresponding to the client on the external payment platform, it continues the remaining payment process.

[0088] In one optional implementation, the payment verification device 600 further includes a privacy processing unit, used to perform a first privacy processing on the queried target identity authentication information based on a preset privacy algorithm after querying the corresponding target identity authentication information according to the identifier of the order submitter, and to carry the target identity authentication information after the first privacy processing in the payment call request; and, after obtaining the target identity authentication information after the first privacy processing, the external payment platform performs a second privacy processing on the payer's identity authentication information in each attribute based on the privacy algorithm; the consistency verification performed by the external payment platform includes: verifying whether the target identity authentication information after the first privacy processing is consistent with the payer's identity authentication information in the attribute after the second privacy processing.

[0089] In practical applications, the external payment platform forwards the supplementary information notification to the client via the server, or it sends the notification directly to the client. The external payment platform verifies whether the supplementary identity authentication information matches the payer's identity authentication information on the client. If they match, the remaining payment process continues; if they do not match, a supplementary information notification is sent back to the client, or the payment process is terminated.

[0090] Furthermore, in this embodiment of the invention, the attributes of the identity authentication information include at least one of the following: name and ID number.

[0091] Please see Figure 7As shown, the payment verification device 700 provided in the fourth embodiment of the present invention is installed on the client side and may include: a request sending unit 701, used to send an order payment request based on an external payment platform to the server, the order payment request carrying the identifier of the order submitter and the identifier of the external payment platform; a notification receiving unit 702, used to receive a supplementary recording notification; wherein, the supplementary recording notification is issued by the external payment platform when the target identity authentication information is inconsistent with the payer's identity authentication information corresponding to the client on the external payment platform, the target identity authentication information is queried by the server based on the identifier of the order submitter after receiving the order payment request, and the external payment platform obtains the target identity authentication information from the payment call request sent by the server based on the identifier of the external payment platform; a supplementary recording sending unit 703, used to determine the supplementary identity authentication information and send it to the server, so as to perform a verification on the external payment platform to see if the supplementary identity authentication information is consistent with the payer's identity authentication information. The payment verification device of the fourth embodiment corresponds to the method executed by the client in the first embodiment.

[0092] Preferably, the payment verification device 700 includes a payment processing unit for: continuing the remaining payment process if the target identity authentication information is verified by the external payment platform to be consistent with the payer's identity authentication information corresponding to the client on the external payment platform.

[0093] As a preferred embodiment, the payment processing unit is also used to: if the external payment platform verifies that the supplemented identity authentication information matches the external payment platform's identity authentication information corresponding to the payer on the client, continue the remaining payment process; if they do not match, receive a notification to supplement the information again or a notification to end the payment process.

[0094] Please see Figure 8 As shown, the payment verification device 800 provided in the fifth embodiment of the present invention is set on the server side and may include: a request receiving unit 801, used to receive an order payment request sent by the client based on an external payment platform, wherein the order payment request carries the identifier of the order submitter and the identifier of the external payment platform; an identity query unit 802, used to query the corresponding target identity authentication information according to the identifier of the order submitter, and send an identity authentication notification to the external payment platform using the identifier of the external payment platform; and a consistency verification unit 803, used to receive the identity authentication information of the payer sent by the external payment platform corresponding to the client, and verify whether the target identity authentication information is consistent with the payer's identity authentication information; if inconsistent, send a supplementary recording notification to the client to obtain the supplementary identity authentication information provided by the client. The payment verification device of the fifth embodiment corresponds to the method executed by the server in the second embodiment.

[0095] In this embodiment of the invention, the payment verification device 800 further includes a storage unit for storing the mapping relationship between the supplemented identity authentication information and the identifier of the order submitter after receiving the supplemented identity authentication information provided by the client.

[0096] Preferably, the identity query unit 802 is further configured to: after receiving an order payment request, query whether there is pre-stored supplementary identity authentication information corresponding to the identifier of the order submitter; if the supplementary identity authentication information is not stored, determine the identity authentication information of the order submitter in at least one preset attribute as the target identity authentication information; if the supplementary identity authentication information is stored, determine the latest supplementary attribute identity authentication information of the order submitter as the target identity authentication information.

[0097] In one embodiment, the payment verification device 800 further includes a payment processing unit, used to continue the remaining payment process if the verification target identity authentication information matches the identity authentication information of the payer corresponding to the client on the external payment platform.

[0098] In one optional implementation, the payment verification device 800 further includes a privacy processing unit, configured to perform a first privacy processing on the queried target identity authentication information based on a preset privacy algorithm after querying the corresponding target identity authentication information according to the identifier of the order submitter; and to perform a second privacy processing on the payer's identity authentication information in each attribute based on the privacy algorithm; the consistency verification unit 803 is further configured to: verify whether the target identity authentication information processed by the first privacy processing is consistent with the payer's identity authentication information in the attribute processed by the second privacy processing.

[0099] In practical applications, the payment processing unit is also used to: verify whether the supplemented identity authentication information is consistent with the payer's identity authentication information; if consistent, continue the remaining payment process; if inconsistent, return a notification to the client to supplement the information again or end the payment process.

[0100] Furthermore, in this embodiment of the invention, the attributes of the identity authentication information include at least one of the following: name and ID number.

[0101] Please see Figure 9As shown, the payment verification device 900 provided in the sixth embodiment of the present invention is installed on the client side and may include: a sending unit 901, used to send an order payment request based on an external payment platform to the server, wherein the order payment request carries the identifier of the order submitter and the identifier of the external payment platform; a supplementary notification receiving unit 902, used to receive a supplementary notification; wherein, the supplementary notification is sent by the server when the target identity authentication information is inconsistent with the payer's identity authentication information of the external payment platform corresponding to the client, the target identity authentication information is queried by the server based on the identifier of the order submitter after receiving the order payment request, and the payer's identity authentication information is provided by the external payment platform to the server after receiving the identity authentication notification sent by the server, and the server sends the identity authentication notification based on the identifier of the external payment platform; and a supplementary identity sending unit 903, used to determine the supplementary identity authentication information and send it to the server, so that the server can perform a verification on whether the supplementary identity authentication information is consistent with the payer's identity authentication information. The payment verification device of the sixth embodiment corresponds to the method executed by the client in the second embodiment.

[0102] Preferably, the payment verification device 900 includes a payment processing unit for: continuing the remaining payment process if the target identity authentication information is verified by the server to be consistent with the payer's identity authentication information corresponding to the client by the external payment platform.

[0103] As a preferred embodiment, the payment processing unit is also used to: if the external payment platform verifies that the supplemented identity authentication information matches the external payment platform's identity authentication information corresponding to the payer on the client, continue the remaining payment process; if they do not match, receive a notification to supplement the information again or a notification to end the payment process.

[0104] According to the technical solution of this embodiment of the invention, after receiving an order payment request from a client based on an external payment platform, the server queries the corresponding target identity authentication information based on the order submitter identifier carried in the request. Then, the server or the external payment platform performs a consistency verification between the target identity authentication information and the external payment platform's identity authentication information corresponding to the payer on the client. If the verification matches, the payment process is executed; if the verification does not match, the client performs identity authentication information supplementation, and the server or the external payment platform performs the identity authentication information consistency verification again until the verification matches before executing the payment process. In this way, by supplementing identity authentication information during the payment process, consistency verification of identity authentication information between the current platform (client, server) and the external payment platform is achieved, thereby forming a more secure third-party payment method, solving payment security and compliance issues caused by inconsistent identity authentication information, and preventing payment vulnerabilities and business disruptions due to inconsistent identity authentication information.

[0105] Figure 10 An exemplary system architecture 1000 is shown that can be applied to the payment verification method or payment verification device of the present invention.

[0106] like Figure 10 As shown, system architecture 1000 may include terminal devices 1001, 1002, and 1003, network 1004, and server 1005 (this architecture is merely an example; the components included in a specific architecture may be adjusted according to the specific application). Network 1004 serves as the medium for providing communication links between terminal devices 1001, 1002, and 1003 and server 1005. Network 1004 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0107] Users can use terminal devices 1001, 1002, and 1003 to interact with server 1005 via network 1004 to receive or send messages, etc. Various client applications, such as e-commerce applications (for example only), can be installed on terminal devices 1001, 1002, and 1003.

[0108] Terminal devices 1001, 1002, and 1003 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0109] Server 1005 can be a server that provides various services, such as an e-commerce backend server (for example only) that supports e-commerce applications operated by users using terminal devices 1001, 1002, and 1003. The e-commerce backend server can process received order payment requests and feed back the processing results (such as payment results - for example only) to terminal devices 1001, 1002, and 1003.

[0110] It should be noted that the payment verification method provided in this embodiment of the invention can be executed by server 1005, and correspondingly, the payment verification device can be set in server 1005.

[0111] It should be understood that Figure 10 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0112] The present invention also provides an electronic device. The electronic device according to an embodiment of the present invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the payment verification method provided by the present invention.

[0113] The following is for reference. Figure 11It shows a schematic diagram of the structure of a computer system 1100 suitable for implementing an electronic device according to embodiments of the present invention. Figure 11 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.

[0114] like Figure 11 As shown, the computer system 1100 includes a central processing unit (CPU) 1101, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 1102 or programs loaded from storage section 1108 into random access memory (RAM) 1103. The RAM 1103 also stores various programs and data required for the operation of the computer system 1100. The CPU 1101, ROM 1102, and RAM 1103 are interconnected via a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.

[0115] The following components are connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, etc.; an output section 1107 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN card, modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to I / O interface 1105 as needed. A removable medium 1111, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 1110 as needed so that computer programs read from it can be installed into storage section 1108 as needed.

[0116] In particular, according to the embodiments disclosed in this invention, the processes described in the above main step diagrams can be implemented as computer software programs. For example, embodiments of this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the main step diagrams. In the above embodiments, the computer program can be downloaded and installed from a network via communication section 1109, and / or installed from removable medium 1111. When the computer program is executed by central processing unit 1101, it performs the functions defined in the system of this invention.

[0117] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0118] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0119] The units described in the embodiments of the present invention can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor can be described as including a receiving unit, a querying unit, and a data entry unit. The names of these units do not necessarily limit the specific unit; for example, the receiving unit can also be described as "a unit that provides the order submitter identifier to the querying unit."

[0120] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, and when the device executes the one or more programs, the steps performed by the device include: receiving an order payment request from a client based on an external payment platform, the order payment request carrying the identifier of the order submitter and the identifier of the external payment platform; querying the corresponding target identity authentication information based on the identifier of the order submitter, and sending a payment call request to the external payment platform using the identifier of the external payment platform; the payment call request carrying the target identity authentication information; receiving supplementary identity authentication information provided by the client, and sending the supplementary identity authentication information to the external payment platform; wherein the supplementary identity authentication information is determined by the client after receiving a supplementary notification from the external payment platform, and the supplementary notification is issued by the external payment platform when verifying that the target identity authentication information is inconsistent with the external payment platform's identity authentication information corresponding to the payer's identity on the client.

[0121] In the technical solution of this invention, after receiving an order payment request from a client based on an external payment platform, the server queries the corresponding target identity authentication information based on the order submitter identifier carried in the request. Then, the server or the external payment platform performs a consistency check between the target identity authentication information and the external payment platform's identity authentication information corresponding to the payer on the client. If the check matches, the payment process is executed; if the check does not match, the client performs identity authentication information supplementation, and the server or the external payment platform performs the identity authentication information consistency check again until the check matches before executing the payment process. In this way, by supplementing identity authentication information during the payment process, consistency verification of identity authentication information between the current platform (client, server) and the external payment platform is achieved, thereby forming a more secure third-party payment method. This solves payment security and compliance issues caused by inconsistent identity authentication information and prevents payment vulnerabilities and business disruptions due to inconsistent identity authentication information.

[0122] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A payment verification method, characterized in that, Executed by the server; the method includes: Receive an order payment request from a client, based on an external payment platform, wherein the order payment request carries the identifier of the order submitter and the identifier of the external payment platform; Based on the identifier of the order submitter, the corresponding target identity authentication information is queried, and a payment call request is sent to the external payment platform using the identifier of the external payment platform; the payment call request carries the target identity authentication information; The system receives supplementary identity authentication information provided by the client and sends the supplementary identity authentication information to the external payment platform. The external payment platform verifies whether the supplementary identity authentication information is consistent with the payer's identity authentication information corresponding to the client. The supplementary identity authentication information is determined by the client after receiving a supplementary notification from the external payment platform, and the supplementary notification is issued by the external payment platform when it verifies that the target identity authentication information is inconsistent with the payer's identity authentication information corresponding to the client.

2. The method according to claim 1, characterized in that, The method further includes: After receiving the supplementary identity authentication information provided by the client, the mapping relationship between the supplementary identity authentication information and the identifier of the order submitter is stored.

3. The method according to claim 2, characterized in that, The step of querying the corresponding target identity authentication information based on the identifier of the order submitter includes: After receiving the order payment request, check whether the supplementary identity authentication information corresponding to the identifier of the order submitter is pre-stored; If the supplementary identity authentication information is not stored, the identity authentication information of at least one attribute preset by the order submitter shall be determined as the target identity authentication information; If the newly added identity authentication information is stored, the latest newly added identity authentication information of the attribute by the order submitter will be determined as the target identity authentication information.

4. The method according to claim 1, characterized in that, If the external payment platform verifies that the target identity authentication information matches the identity authentication information of the payer corresponding to the client on the external payment platform, it will continue the remaining payment process.

5. The method according to claim 3, characterized in that, The method further includes: after querying the corresponding target identity authentication information based on the identifier of the order submitter, performing a first privacy processing on the queried target identity authentication information based on a preset privacy algorithm, and carrying the first privacy-processed target identity authentication information in the payment call request; and, After obtaining the target identity authentication information that has undergone the first privacy processing, the external payment platform performs a second privacy processing on the payer's identity authentication information in the attribute based on the privacy algorithm. Verifying whether the target identity authentication information is consistent with the identity authentication information of the payer corresponding to the client on the external payment platform includes: verifying whether the target identity authentication information after the first privacy processing is consistent with the identity authentication information of the payer in the attribute after the second privacy processing.

6. The method according to claim 1, characterized in that, After the external payment platform verifies whether the supplemented identity authentication information matches the identity authentication information of the payer corresponding to the client on the external payment platform, if they match, the remaining payment process continues; If there is a discrepancy, a notification to re-enter the information will be sent to the client or the payment process will be terminated.

7. A payment verification method, characterized in that, Executed by the client; the method includes: Send an order payment request to the server based on an external payment platform. The order payment request carries the identifier of the order submitter and the identifier of the external payment platform. Receive supplementary information notification; wherein, the supplementary information notification is issued by the external payment platform when the target identity authentication information is inconsistent with the identity authentication information of the payer corresponding to the client on the external payment platform, the target identity authentication information is obtained by the server after receiving the order payment request based on the identifier of the order submitter, and the external payment platform obtains the target identity authentication information from the payment call request sent by the server based on the identifier of the external payment platform; The system determines the supplementary identity authentication information and sends it to the server so that the external payment platform can perform a verification to check whether the supplementary identity authentication information is consistent with the payer's identity authentication information.

8. A payment verification device, characterized in that, Set on the server side; the device includes: The receiving unit is used to receive an order payment request sent by the client based on an external payment platform, wherein the order payment request carries the identifier of the order submitter and the identifier of the external payment platform; The query unit is used to query the corresponding target identity authentication information based on the identifier of the order submitter, and to send a payment call request to the external payment platform using the identifier of the external payment platform; the payment call request carries the target identity authentication information. The supplementary registration unit is used to receive supplementary identity authentication information provided by the client, and send the supplementary identity authentication information to the external payment platform, so that the external payment platform can verify whether the supplementary identity authentication information is consistent with the external payment platform's identity authentication information corresponding to the payer of the client; wherein, the supplementary identity authentication information is determined by the client after receiving a supplementary registration notification from the external payment platform, and the supplementary registration notification is issued by the external payment platform when it verifies that the target identity authentication information is inconsistent with the external payment platform's identity authentication information corresponding to the payer of the client.

9. A payment verification device, characterized in that, Set on the client; the device includes: The request sending unit is used to send an order payment request based on an external payment platform to the server. The order payment request carries the identifier of the order submitter and the identifier of the external payment platform. A notification receiving unit is used to receive a supplementary recording notification; wherein, the supplementary recording notification is issued by the external payment platform when the target identity authentication information is inconsistent with the identity authentication information of the payer corresponding to the client on the external payment platform; the target identity authentication information is obtained by the server after receiving the order payment request based on the identifier of the order submitter; and the external payment platform obtains the target identity authentication information from the payment call request sent by the server based on the identifier of the external payment platform. The supplementary authentication information sending unit is used to determine the supplementary authentication information and send it to the server so that the external payment platform can perform a verification on whether the supplementary authentication information is consistent with the payer's authentication information.

10. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-7.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-7.

Images