Payment method, terminal device, server, system and medium

Abstract

The application discloses a payment method, a terminal device, a server, a system and a medium, and belongs to the field of data processing. The method comprises the following steps: in response to a received payment request message, a security verification request message is sent to a security control system, the security verification request message is used to instruct the security control system to perform security verification according to security verification information; security verification result information sent by the security control system is received; in the case that the security verification result information represents that the security verification is passed, a first notification message is sent to an SDK, the first notification message instructs the SDK to notify a host program to display a user verification page, so as to prompt a user to input first user verification input information, the first user verification input information is used for the host program server to perform user verification to obtain user verification result information; and in the case that the user verification result information represents that the user verification is passed, a payment request is initiated to complete the payment. According to the embodiment of the application, the security of payment can be improved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of data processing, and particularly relates to a payment method, a terminal device, a server, a system and a medium. BACKGROUND

[0002] With the development of payment technology, the application of electronic payment is more and more extensive. Users can realize payment through terminal devices. The terminal device is installed with an application program and a software development kit (SDK), and the SDK can be integrated in the application program to realize payment together.

[0003] The payment process involves two subjects, the application program and the SDK, in the terminal device. With the increase of the subjects involved in the payment process, the security risks of payment also increase. Therefore, there is an urgent need for a payment method capable of improving security. SUMMARY

[0004] The embodiments of the present application provide a payment method, a terminal device, a server, a system and a medium, which can improve the security of payment.

[0005] In a first aspect, the embodiments of the present application provide a payment method applied to a software development kit (SDK) server, which comprises: in response to a received payment request message, sending a security verification request message to a security control system, the security verification request message comprising security verification information, which is used to instruct the security control system to perform security verification on payment corresponding to the payment request message according to the security verification information; receiving security verification result information sent by the security control system; in the case that the security verification result information represents that the security verification is passed, sending a first notification message to an SDK in a terminal device, the terminal device having the SDK and a host program, the first notification message being used to instruct the SDK to notify the host program to display a user verification page to prompt a user to input first user verification input information, the first user verification input information being used for the host program server to perform user verification to obtain user verification result information; in the case that the user verification result information represents that the user verification is passed, initiating a payment request to complete payment.

[0006] In a second aspect, the embodiments of the present application provide a payment method applied to a terminal device, the terminal device having a software development kit (SDK) and a host program, the method comprising: obtaining, by the SDK, a first notification message sent by an SDK server, the first notification message being sent by the SDK server based on security verification result information representing that a security verification is passed, the security verification result information being obtained by a security control system based on security verification information in a security verification request message for performing security verification on a payment corresponding to a payment request message, the security verification request message being sent by the SDK server in response to the received payment request message; in response to the first notification message, notifying, by the SDK, the host program to display a user verification page to prompt a user to input first user verification input information; feeding back, by the host program, the first user verification input information to a host program server, the first user verification input information being used by the host program server to perform user verification to obtain user verification result information; and sending, by the SDK, the user verification result information obtained by the host program from the host program server to the SDK server, so that the SDK server initiates a payment request to complete the payment in a case where the user verification result information represents that the user verification is passed.

[0007] In a third aspect, the embodiments of the present application provide a payment method applied to a host program server, the method comprising: receiving first user verification input information fed back by a terminal device through a host program, the terminal device having an SDK and a host program, the first user verification input information being obtained after the SDK notifies the host program to display a user verification page in response to a first notification message, the first notification message being sent by an SDK server based on security verification result information representing that a security verification is passed, the security verification result information being obtained by a security control system based on security verification information in a security verification request message for performing security verification on a payment corresponding to a payment request message, the security verification request message being sent by the SDK server in response to the received payment request message; performing user verification according to the first user verification input information to obtain user verification result information; and sending the user verification result information to the host program in the terminal device, the user verification result information being transmitted to the SDK by the host program, so that the SDK sends the user verification result information to the SDK server, and the SDK server initiates a payment request to complete the payment in a case where the user verification result information represents that the user verification is passed.

[0008] In a fourth aspect, an embodiment of the present application provides an SDK server, comprising: a sending module configured to send, in response to a received payment request message, a security verification request message to a security control system, the security verification request message comprising security verification information, the security verification information being used to instruct the security control system to perform security verification on a payment corresponding to the payment request message according to the security verification information; a receiving module configured to receive security verification result information sent by the security control system; the sending module is further configured to send, in a case where the security verification result information indicates that the security verification is passed, a first notification message to an SDK in a terminal device, the terminal device having the SDK and a host program, the first notification message being used to instruct the SDK to notify the host program to display a user verification page, so as to prompt a user to input first user verification input information, the first user verification input information being used for the host program server to perform user verification to obtain user verification result information; and the sending module is further configured to initiate a payment request in a case where the user verification result information indicates that the user verification is passed, so as to complete the payment.

[0009] In a fifth aspect, an embodiment of the present application provides a terminal device having a software development kit (SDK) and a host program, the terminal device comprising: a receiving module configured to acquire, through the SDK, a first notification message sent by an SDK server, the first notification message being sent by the SDK server based on security verification result information indicating that security verification is passed, the security verification result information being obtained by a security control system based on security verification information in a security verification request message, the security verification request message being sent by the SDK server in response to a received payment request message; a display module configured to, in response to the first notification message, notify, through the SDK, the host program to display a user verification page, so as to prompt a user to input first user verification input information; and a sending module configured to feed back, through the host program, the first user verification input information to a host program server, the first user verification input information being used for the host program server to perform user verification to obtain user verification result information; the sending module is further configured to send, through the SDK, the user verification result information obtained by the host program from the host program server to the SDK server, so that the SDK server initiates a payment request in a case where the user verification result information indicates that the user verification is passed, so as to complete the payment.

[0010] In a sixth aspect, an embodiment of the present application provides a host program server, comprising: a receiving module configured to receive first user verification input information fed back by a terminal device through a host program, the terminal device having a software development kit (SDK) and the host program, the first user verification input information being obtained after the SDK notifies the host program to display a user verification page in response to a first notification message, the first notification message being sent by an SDK server based on security verification result information representing that a security verification is passed, the security verification result information being obtained by a security control system based on security verification information in a security verification request message for performing security verification on a payment corresponding to a payment request message, the security verification request message being sent by the SDK server in response to the received payment request message; a verification module configured to perform user verification according to the first user verification input information to obtain user verification result information; and a sending module configured to send the user verification result information to the host program in the terminal device, and transmit the user verification result information to the SDK through the host program, so that the SDK sends the user verification result information to the SDK server, and in a case where the user verification result information represents that the user verification is passed, the SDK server initiates a payment request to complete the payment.

[0011] In a seventh aspect, an embodiment of the present application provides an SDK server, comprising: a processor and a memory storing computer program instructions; and the processor implements the payment method of the first aspect when executing the computer program instructions.

[0012] In an eighth aspect, an embodiment of the present application provides a terminal device, comprising: a processor and a memory storing computer program instructions; and the processor implements the payment method of the second aspect when executing the computer program instructions.

[0013] In a ninth aspect, an embodiment of the present application provides a host program server, comprising: a processor and a memory storing computer program instructions; and the processor implements the payment method of the first aspect when executing the computer program instructions.

[0014] In a tenth aspect, an embodiment of the present application provides a payment system, comprising the SDK server of the seventh aspect, the terminal device of the eighth aspect, and the host program server of the ninth aspect.

[0015] In an eleventh aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium storing computer program instructions, and the computer program instructions are executed by a processor to implement the payment method of the first aspect, the payment method of the second aspect, and the payment method of the third aspect.

[0016] The application embodiment provides a payment method, a terminal device, a server, a system and a medium. The SDK server responds to a payment request message, sends a security verification request message to a security control system to request the security control system to perform security verification on the payment, and completes verification of security required by a party to which the SDK belongs. In the case where the security verification is passed, the SDK server sends a message to the SDK of the terminal device, the message being used to instruct the SDK to notify a host program to display a user verification page, so that the SDK can trigger the host program to actively initiate user verification, and complete verification of user identity security required by a party to which the host program belongs. The bidirectional verification of the two subjects of the party to which the SDK belongs and the party to which the host program belongs is realized in the payment process, and the security of the payment is improved. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the application embodiments, the drawings required to be used in the application embodiments will be briefly introduced. Other drawings can also be obtained by those of ordinary skill in the art without creative labor on the premise that the drawings are not creative labor.

[0018] Figure 1 An example of the application scenario of the payment method provided by the application embodiment is shown in the schematic diagram.

[0019] Figure 2 The flowchart of an embodiment of the payment method provided by the first aspect of the application is shown.

[0020] Figure 3 The flowchart of another embodiment of the payment method provided by the first aspect of the application is shown.

[0021] Figure 4 The flowchart of still another embodiment of the payment method provided by the first aspect of the application is shown.

[0022] Figure 5 The flowchart of yet another embodiment of the payment method provided by the first aspect of the application is shown.

[0023] Figure 6 The flowchart of still another embodiment of the payment method provided by the first aspect of the application is shown.

[0024] Figure 7 The flowchart of an embodiment of the payment method provided by the second aspect of the application is shown.

[0025] Figure 8 The flowchart of another embodiment of the payment method provided by the second aspect of the application is shown.

[0026] Figure 9 The flowchart of still another embodiment of the payment method provided by the second aspect of the application is shown.

[0027] Figure 10 Flow chart of yet another embodiment of the payment method provided by the second aspect of the present application;

[0028] Figure 11 Flow chart of yet another embodiment of the payment method provided by the second aspect of the present application;

[0029] Figure 12 Flow chart of an embodiment of the payment method provided by the third aspect of the present application;

[0030] Figure 13 Flow chart of another embodiment of the payment method provided by the third aspect of the present application;

[0031] Figure 14 Flow chart of an example of the payment process provided by the embodiments of the present application;

[0032] Figure 15 Flow chart of another example of the payment process provided by the embodiments of the present application;

[0033] Figure 16 Flow chart of yet another example of the payment process provided by the embodiments of the present application;

[0034] Figure 17 Structural schematic diagram of an embodiment of the SDK server provided by the fourth aspect of the present application;

[0035] Figure 18 Structural schematic diagram of an embodiment of the terminal device provided by the fifth aspect of the present application;

[0036] Figure 19 Structural schematic diagram of an embodiment of the host program server provided by the sixth aspect of the present application;

[0037] Figure 20 Structural schematic diagram of an embodiment of the SDK server provided by the seventh aspect of the present application. DETAILED DESCRIPTION

[0038] The features and exemplary embodiments of the various aspects of the present application will be described in detail below, in order to make the purposes, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in combination with the drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, but not to limit the present application. The present application can be implemented without some of these specific details by those skilled in the art. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

[0039] With the development of payment technology, the application of electronic payment is more and more extensive. Users can realize payment through terminal equipment. The terminal equipment is installed with an application program for payment, but the function of the application program is limited. In order to make the payment function more perfect, the terminal equipment can also be provided with SDK, which can be integrated in the application program and realize payment together with the application program. In this case, the payment process involves two subjects of application program and SDK, and the increase of the subjects involved in the payment process also increases the security risk of payment. Therefore, a payment method capable of improving security is urgently needed.

[0040] The embodiment of the application provides a payment method, a terminal device, a server, a system and a medium, which can take SDK and host program as subjects respectively, perform double verification, and complete payment when the verification taking SDK as subject and the verification taking host program as subject are both passed. The security of SDK related interaction and host program related interaction is ensured through the verification of SDK and host program, so that the security of the whole payment process is improved.

[0041] The payment method provided by the application is applied to a payment scene, and can mainly involve a terminal device, an SDK background system, a host program background system and a security control system. Figure 1 An example of a schematic diagram of an application scene of the payment method provided by the embodiment of the application is shown in FIG. 1. Figure 1 As shown in FIG. 1, the terminal device 11 can respectively communicate and interact with the SDK background system 12 and the host program background system 13, and the SDK background system 12 can respectively communicate and interact with the host program background system 13 and the security control system 14.

[0042] The terminal device 11 has a host program and an SDK. The payment function of the terminal device 11 needs to call the SDK together with the host program to realize. The SDK in the terminal device 11 can interact with the host program. The SDK in the terminal device 11 can communicate and interact with the SDK background system 12, and the host program in the terminal device 11 can communicate and interact with the host program background system 13. The terminal device 11 is a device used by a user to perform payment, and can specifically include a mobile phone, a tablet computer, an electronic computer, a wearable device and the like, which are not limited herein.

[0043] The SDK background system 12 is a background system of the SDK, and can include one or more SDK servers, which are not limited to the type and quantity of the SDK servers in the SDK background system 12. In the payment process, the terminal device 11 can send payment related information to the SDK background system through the SDK. The SDK background system can also prestore account information and personal information of a user for payment.

[0044] In some embodiments, the SDK background system 12 can include an SDK background subsystem and a payment code subsystem, the SDK background subsystem and the payment code subsystem can communicate with each other, the SDK background subsystem can also communicate with the SDK in the terminal device 11, and the payment code subsystem can communicate with the host program background system. The payment code subsystem stores related information of the payment code and can manage and verify the payment code. The payment code can include a collection code, a payment code, etc., and the payment code can specifically be a two-dimensional code or other forms of graphic code, which are not limited herein.

[0045] The host program background system 13 is a background system of the host program and can include one or more host program servers, and the types and number of the host program servers in the host program background system 13 are not limited herein. The terminal device 11 can interact with the host program background system 13 through the host program during the payment process. The host program background system 13 can also communicate with the SDK background system 12.

[0046] The security control system 14 can be used for security verification of the payment and can include one or more electronic devices, and the types and number of the electronic devices in the security control system 14 are not limited herein. The security control system 14 can communicate with the SDK background system 12. In the case where the SDK background system 12 includes an SDK background subsystem and a payment code subsystem, the security control system 14 can communicate with the SDK background subsystem.

[0047] In some embodiments, the information transmission between the SDK and the host program in the terminal device 11 is encrypted transmission, that is, the information interacted between the SDK and the host program in the terminal device 11 is encrypted information. The SDK and the host program each store encryption and decryption algorithms required for encryption and decryption, and the encryption and decryption algorithms in the SDK and the host program can be set according to application environment, demand, etc., for example, the encryption and decryption algorithms in the SDK and the host program can include SM2 algorithm, SM4 algorithm, data encryption standard (DES), RSA algorithm, etc., which are not limited herein. The key required for the encryption and decryption algorithm in the SDK can be stored and managed by the SDK background system 12, that is, the key for encryption and decryption in the SDK can be stored in the SDK server in the SDK background system 12, and the SDK can realize encryption and decryption by interacting with the SDK background system 12. The key required for the encryption and decryption algorithm in the host program can be stored and managed by the host program background system 13, that is, the key for encryption and decryption in the host program is stored in the host program server in the host program background system 13, and the host program can realize encryption and decryption by interacting with the host program background system 13. Through the ciphertext transmission between the SDK and the host program, the information transmitted between the SDK and the host program is not easy to be stolen, and the communication security between the SDK and the host program can be ensured.

[0048] In some embodiments, the SDK in the terminal device 11 can have a secure domain, and information in the SDK can be stored in the secure domain. The secure domain can be an encrypted data storage space, and can be implemented by hardware and / or software, such as a secure element (SE) and / or a trusted execution environment (TEE), and the like. The SDK can manage the permissions of the secure domain, such as dividing data that cannot be read openly and data that only the host program has the permission to read, and the like.

[0049] The payment method, the terminal device, the server, the system, and the medium in the present application are described in the following.

[0050] The first aspect of the present application provides a payment method, which is applied to an SDK server, that is, the payment method can be executed by the SDK server. Figure 2 An embodiment of the payment method provided by the first aspect of the present application is shown in a flowchart. As shown in the figure, the payment method can include steps S201 to S204. Figure 2

[0051] In step S201, in response to a received payment request message, a security verification request message is sent to a security control system.

[0052] The payment request message is used to initiate payment. The payment request message can be sent by the SDK in the terminal device to the SDK server, or the payment request message can be sent by the payment receiving device to the SDK server. In the case where the SDK background system includes an SDK background subsystem and a payment code subsystem, the payment can be initiated by the payment receiving device to the SDK server in the payment code subsystem, and the SDK server in the payment code subsystem sends the payment request message to the SDK server in the SDK background subsystem. The payment request message can include order information, terminal device information, payment information, and the like. The order information can include order identification, order initiator, order details, order amount, order time, and the like, which are associated with the order, and are not limited herein. The terminal device information can include the geographic location of the terminal device that performs the payment, the device identification, and the like, which are associated with the terminal device, and are not limited herein. The payment information can include payment payer information, payment payee information, payment amount, payment time, and the like, which are associated with the payment, and are not limited herein. The payment payee information can include merchant name, merchant account, and the like, and the payment payer information can include payment account, payment card information, payment identification, and the like, which are not limited herein.

[0053] ​The security verification request message includes security verification information. The security verification request message is used to instruct the security control system to perform security verification on the payment corresponding to the payment request message according to the security verification information. The security verification information can include at least part of the information sent by the SDK in the terminal device to the SDK server, and the security verification information can also include the payment payer information and the like indicated by the payment request message and pre-stored in the SDK server, which is not limited herein. For example, the security verification information can include one or more of the payment card number, the payment party login account, the mobile phone number associated with the payment party login account, the mobile phone number associated with the payment card, the terminal device identifier, the geographic position of the terminal device, the payment amount, the payment time, the historical payment information of the payment card, and the like, and the security verification information can also include other information capable of being verified in terms of security, which is not limited herein.

[0054] In some examples, in the case that the security verification request message includes the payment card number, the payment card number can be the default payment card number provided by the SDK in the terminal device. If the user switches the default payment card in the terminal device, that is, the default payment card number changes, the SDK will send a message including the new default payment card number to the SDK server, and the SDK server will be triggered to send a security verification request message including the new default payment card number to the security control system again. That is, if the user switches the default payment card on the payment details page displayed by the terminal device, the SDK server will correspondingly resend a security verification request message including the switched default payment card number to the security control system.

[0055] The security control system receives the security verification request message, and performs security verification according to the security verification information in the security verification request message. The security verification can verify the legality of the payment and the security of the login state of the terminal device for the payment. Specifically, whether the security verification passes or not can be determined by whether the security verification information meets a predetermined security judgment condition. The security judgment condition can be set according to specific scenarios, requirements, etc., and is not limited herein. For example, the security verification information includes a terminal device identifier for the current payment and historical payment information of the payment card. The historical payment information of the payment card includes a terminal device identifier in historical payment of the payment card. If the terminal device identifier for the current payment is consistent with the terminal device identifier in the historical payment of the payment card, the security verification passes. Otherwise, the security verification does not pass. For another example, the security verification information includes a geographic location of a terminal device for the current payment, a payment time, and historical payment information of the payment card. The historical payment information of the payment card includes a geographic location of a terminal device for the last payment of the payment card and a payment time. If the time length between the payment time for the last payment of the payment card and the payment time for the current payment is less than a preset time length, and the distance between the geographic location of the terminal device for the last payment of the payment card and the geographic location of the terminal device for the current payment is greater than a preset distance, the security verification does not pass. Otherwise, the security verification passes. For another example, the security verification information includes a mobile phone number associated with a payment account and a mobile phone number associated with the payment card. If the mobile phone number associated with the payment account is consistent with the mobile phone number associated with the payment card, the security verification passes. Otherwise, the security verification does not pass.

[0056] In some examples, in the case of very high security risk, such as insufficient account balance, illegal payment, etc., it is determined that the security verification does not pass. In the case of medium and low security risk, the security of the payment can be determined by subsequent user verification. For example, the security verification information includes a terminal device identifier for the current payment and historical payment information of the payment card. The historical payment information of the payment card includes a terminal device identifier in historical payment of the payment card. Since the user has the possibility of replacing the terminal device, if the terminal device identifier for the current payment is inconsistent with the terminal device identifier in the historical payment of the payment card, it can also be considered that the security verification passes. In the subsequent process, it can be determined by user verification whether the user uses the replaced terminal device to make payment. For another example, the security verification information includes a payment amount for the current payment and an account balance of the payment party. If the payment amount for the current payment is less than or equal to the account balance of the payment party, the security verification passes. Otherwise, the security verification does not pass.

[0057] In some examples, in a case where the SDK receives the payment request message, if it is detected that the currently logged-in user account is not associated with a payment card, a card binding prompt information can be issued to prompt the user to enter the card binding process to bind a payment card. After binding the payment card, the SDK sends a security verification request message to the security control system.

[0058] In step S202, the security verification result information sent by the security control system is received.

[0059] The security control system performs security verification according to the security verification information, and can obtain security verification result information for the payment indicated by the payment request message. The security verification result information is used to represent whether the security verification is passed. If the security verification result information represents that the security verification is not passed, the SDK server can send an indication message to the SDK in the terminal device to make the SDK issue a pop-up window information of aborting payment.

[0060] In some examples, after the SDK server receives the security verification result information representing that the security verification is passed, the SDK in the terminal device can call a preset query interface to transmit payment information such as payer information, order information such as order number, and the like of the current payment to the SDK server. The SDK server can further supplement other order information such as merchant number and other payment information related to payment of the current payment, and the like, and synchronize the payment information and the order information to the host program server to realize synchronization of information about the current payment between the SDK server and the host program server.

[0061] In some examples, in a case where the SDK background system includes an SDK background subsystem and a payment code subsystem, after the SDK server in the SDK background subsystem receives the security verification result information representing that the security verification is passed, the SDK server in the SDK background subsystem can call a preset query interface to transmit payment information such as payer information, order information such as order number, and the like of the current payment to the SDK server of the payment code subsystem. The SDK server of the payment code subsystem can further supplement other order information such as merchant number and other payment information related to payment of the current payment, and the like, and synchronize the payment information and the order information to the host program server to realize synchronization of information about the current payment between the SDK server in the SDK background system and the host program server.

[0062] In step S203, in a case where the security verification result information represents that the security verification is passed, a first notification message is sent to the SDK in the terminal device.

[0063] The security verification result information represents that the security verification is passed, and then the user verification process of the owner of the host program can be performed again. The first notification message is used to instruct the SDK to notify the host program to display a user verification page to prompt the user to input first user verification input information. The first user verification input information is used for the host program server to perform user verification to obtain user verification result information.

[0064] The SDK in the terminal device can send a message to the host program to instruct the host program to display a user verification page in response to the first notification message. The host program displays the user verification page in response to the message. The user verification page can include a password input area, a verification code input area, a biological feature collection area, and the like, and the manner of user verification is not limited herein. The information input by the user to the user verification page is the first user verification input information. The host program can send the first user verification input information to the host program server. The host program server can perform user verification according to the received first user verification input information and obtain user verification result information. The user verification is used to verify the identity of the user. The user verification passing indicates that the user who performs the payment operation is the legal user himself / herself. For example, the first user verification input information is a password, and the host program server verifies whether the first user verification input information is consistent with the password registered by the user in the host program server. If yes, the user verification is passed; otherwise, the user verification is not passed. For another example, the first user verification input information is a face image, and the host program server verifies whether the first user verification input information belongs to the same user as the face image reserved by the user in the host program server. If yes, the user verification is passed; otherwise, the user verification is not passed.

[0065] The user verification result information is used to represent whether the user verification is passed. The host program server can feed back the user verification result information to the host program and the SDK server respectively, and the host program also transmits the user verification result to the SDK, so that the owner of the SDK and the owner of the host program can both know whether the user verification is passed.

[0066] In some examples, when the host program displays the user verification page, the SDK can add buried point information associated with the action of displaying the user verification page, so as to analyze and troubleshoot the execution of the process of displaying the user verification page by the host program later.

[0067] In step S204, when the user verification result information represents that the user verification is passed, a payment request is initiated to complete the payment.

[0068] The user verification result information represents that the user verification is passed, indicating that the user identity has high security, and a payment request can be initiated to the payment party account management system to normally perform the payment. The user verification result information represents that the user verification is not passed, and the payment can be aborted.

[0069] In some embodiments, since the user verification result information can be stolen or tampered during transmission, in order to further ensure payment security, the consistency verification condition can be used to verify the security of the user verification result information during transmission. If the user verification result information meets the consistency verification condition, the payment request is initiated. The consistency verification condition is used to determine whether the user verification result information is safe and effective during transmission. If the user verification result information meets the consistency verification condition, it means that the user verification result information is safe and effective during transmission, and the payment request can be initiated to the payment account management system for normal payment, or the SDK server initiates the payment request to the payment account management system through the host program server for normal payment. If the user verification result information does not meet the consistency verification condition, it means that the user verification result information is not safe and effective during transmission, and the payment can be aborted.

[0070] In some examples, the consistency verification condition can include that the first user verification result information and the second user verification result information are consistent. The first user verification result information is the user verification result information transmitted by the host program server to the SDK through the host program. The second user verification result information is the user verification result information obtained from the host program server. If the first user verification result information and the second user verification result information are consistent, it means that the user verification result information is safe and effective during transmission. If the first user verification result information and the second user verification result information are not consistent, it means that the user verification result information is not safe and effective during transmission.

[0071] After the payment is successful, the SDK server can obtain the payment result information, which represents whether the payment is successful. The SDK server can transmit the payment result information to the SDK, the merchant system, etc., to display the result of whether the payment is successful to the user, the merchant, etc.

[0072] In the above payment process, after the user verification is passed, since the transmission of the user verification result information, the payment, and the transmission of the payment result information all require a certain time, the terminal device will not immediately display the payment completion page. In this case, the SDK can control the terminal device to display a payment-in-progress identifier, such as an image containing the word “loading”. When the terminal device displays the payment completion page, the display of the payment-in-progress identifier is stopped.

[0073] In the embodiments of the present application, the SDK server sends a security verification request message to the security control system in response to the payment request message, to request the security control system to perform security verification on the payment, to complete the security verification required by the SDK owner. In the case where the security verification is passed, the SDK server sends a message to the SDK of the terminal device, indicating that the SDK notifies the host program to display the user verification page, so that the SDK can trigger the host program to actively initiate user verification, to complete the user identity security verification required by the host program owner. The two-way verification of the SDK owner and the host program owner is realized in the payment process, the security of the payment is improved, and the security control requirements of the SDK owner and the host program owner are met.

[0074] In some examples, in the case where the SDK server initiates a payment request to the payment party account management system through the host program server, the SDK server can provide first payment policy information of the SDK owner, which can include discount information, payment activity information, etc. of the SDK owner, and can be used for participating in the payment amount calculation of the payment indicated by the payment request message. The host program server can provide second payment policy information of the host program owner, which can include discount information, payment activity information, etc. of the host program owner, and can be used for participating in the payment amount calculation of the payment indicated by the payment request message.

[0075] In some embodiments, the SDK server can also query the discount information, payment activity information, etc. of the payment policy information from the host program server after receiving the payment request message, directly or through the payment policy system.

[0076] In the above embodiments, the information exchanged between the SDK and the host program is encrypted information, and the SDK needs to encrypt and decrypt the information. Correspondingly, the SDK server stores a key for encrypting and decrypting the information exchanged between the SDK and the host program.

[0077] In some embodiments, the SDK server can request the user verification method from the host program server, and transmit the feedback of the host program server to the SDK, so that the SDK makes corresponding operations. Figure 3 The flowchart of another embodiment of the payment method provided by the first aspect of the present application. Figure 3 Different from Figure 2 The payment method shown in Figure 3 may further include steps S205 to S208, Figure 2 The step S203 in Figure 3 may be specifically refined as the step S2031 in

[0078] In step S205, in a case where the security verification result information represents that the security verification is passed, a user verification mode request message is sent to the host program server.

[0079] The user verification mode request message is used to request the user verification mode from the host program server, and can include one or more than two of the order information corresponding to the payment indicated by the payment request message, the terminal device information, and the payment information. The specific content of the order information, the terminal device information, and the payment information can be referred to the related description in the above embodiments, and will not be described here.

[0080] The host program server can determine the verification operation information according to the information in the user verification mode request message, and the verification operation information is used to indicate whether to perform the user verification and the mode of the user verification. The host program server can store a judgment condition used to determine whether to perform the user verification and the mode of the user verification, and can determine whether to perform the user verification and the mode of the user verification by whether the information in the user verification mode request message meets the reference condition. The judgment condition can be set according to the payment scene, demand, etc., and is not limited here. For example, the user verification mode request message can include the payment information, and the payment information includes the payment amount. The judgment condition can include the corresponding relationship between the payment amount range and whether to perform the user verification and the mode of the user verification. For example, the judgment condition includes: the payment amount is less than 100 yuan, and the user verification is not required; the payment amount is in the range of 100 yuan to 500 yuan, the user verification is required, and the mode of the user verification is password verification; the payment amount is in the range of 500 yuan to 1000 yuan, the user verification is required, and the mode of the user verification is verification code verification; and the payment amount is greater than 1000 yuan, the user verification is required, and the mode of the user verification is biometric verification. For another example, the user verification mode request message can include the order information and the payment information, the order information includes the order identifier and the order placing user account, and the payment information includes the payment party login account. The judgment condition can include: the order placing user account is inconsistent with the payment party login account, the user verification is required, and the mode of the user verification is biometric verification; and the order placing user account is consistent with the payment party login account, the user verification is required, and the mode of the user verification is password verification.

[0081] After the host program server determines the verification operation information, the host program server can send a user verification mode feedback message to the SDK server. The user verification mode feedback message includes the verification operation information.

[0082] In step S206, the user verification mode feedback message sent by the host program server is received.

[0083] In step S207, in a case where the verification operation information includes a payment rejection identifier, a second notification message is sent to the SDK.

[0084] The payment rejection identifier indicates that no user verification is needed and the payment is stopped. In response to the user verification manner feedback information, the SDK server sends second notification information to the SDK in the terminal device. The second notification message is used to instruct the SDK to send a payment rejection prompt information. In response to the second notification message, the SDK can send a prompt information to prompt the user that there is a payment risk. For example, the prompt information makes the terminal device display the text "host program risk limited" and the like. In some examples, the user verification manner feedback message can also include a payment rejection reason, and correspondingly, the second notification information can also include the payment rejection reason, the prompt information sent by the SDK in response to the second notification information can include the payment rejection reason, and the terminal device can display the payment rejection reason to inform the user. The payment rejection reason can include a reason for the user verification manner identifier failure caused by SDK exception, host program server exception and the like.

[0085] In step S208, in the case that the verification operation information includes the password-free payment identifier, a third notification message is sent to the SDK.

[0086] The password-free payment identifier indicates that no user verification is needed and the payment process can continue. In response to the user verification manner feedback information, the SDK server sends third notification information to the SDK in the terminal device. The third notification message is used to instruct the SDK to send a password-free payment prompt information. The password-free payment prompt information can prompt the user that the payment is a password-free payment.

[0087] In step S2031, in the case that the verification operation information includes the user verification manner identifier and the security verification result information indicates that the security verification is passed, a first notification message is sent to the SDK.

[0088] The first notification message includes the user verification manner identifier. The user verification manner identifier is used to indicate the manner of user verification. The first notification message is used to instruct the SDK to notify the host program to display a user verification page matched with the user verification manner identifier, so as to prompt the user to input first user verification input information matched with the user verification manner identifier. That is, in response to the first notification message, the SDK can send an instruction message including the user verification manner identifier to the host program, the host program displays a user verification page corresponding to the manner of user verification indicated by the user verification manner identifier according to the user verification manner identifier, and correspondingly, the first user verification input information input by the user also corresponds to the manner of user verification indicated by the user verification manner identifier.

[0089] For example, the user verification mode is identified as 01, the user verification mode is password verification, the user verification page displayed by the host program is a password verification page, and the first user verification input information input by the user is a password; the user verification mode is identified as 10, the user verification mode is verification code verification, the user verification page displayed by the host program is a verification code verification page, and the first user verification input information input by the user is a verification code; the user verification mode is identified as 11, the user verification mode is biometric verification, the user verification page displayed by the host program is a biometric verification page, and the first user verification input information input by the user is biometric information.

[0090] In some embodiments, the payment request message, the security verification request message, and the security verification result information can include a target host program identifier. The target host program identifier includes the host program identifier of the payment corresponding to the payment request message, that is, the target host program identifier can represent the host program associated with the payment corresponding to the payment request message.

[0091] The SDK server is preconfigured with a first correspondence relationship. The first correspondence relationship includes the relationship between the host program identifier and the user verification initiator. The host program identifier is used to identify the host program. The user verification initiator is used to indicate the subject that displays the user verification page, and the user verification initiator includes the SDK or the host program in the terminal device. After receiving the security verification result information, the SDK server can determine the target user verification initiator corresponding to the target host program identifier according to the target host program identifier and the first correspondence relationship. The target user verification initiator is the user verification initiator corresponding to the target host program identifier in the first correspondence relationship.

[0092] In the case where the target user verification initiator is the host program, the SDK server sends a first notification message to the SDK. In the case where the target user verification initiator is the SDK, the SDK server sends a fourth notification message to the SDK. The fourth notification message is used to instruct the SDK to display the user verification page to prompt the user to input the second user verification input information. The second user verification input information is used for the SDK server to perform user verification to obtain the user verification result information. The SDK in the terminal device can directly display the user verification page in response to the fourth notification message, and correspondingly, the user verification is performed by the SDK server. The SDK in the terminal device can send the second user verification input information to the SDK server. The SDK server performs user verification according to the second user verification input information to obtain the user verification result information. The specific content of the user verification can be referred to the related description of the user verification performed by the host program server in the above embodiments, which will not be described here.

[0093] Through the setting of the first correspondence relationship, the subject of the user verification in the terminal device can be set more flexibly and has more selectivity.

[0094] In some embodiments, the payment is initiated by the merchant system or through the merchant program installed in the terminal device, and the merchant system and the SDK and the SDK server need to interact on the related information of the order before the SDK server receives the payment request message. Figure 4 The flowchart of still another embodiment of the payment method provided by the first aspect of the application. Figure 4 Different from Figure 2 The payment method shown in FIG. 9 can further include steps S209 to S211. Figure 4

[0095] In step S209, an order identifier is generated in response to the order request message sent by the merchant system.

[0096] After the user places an order to generate an order, the merchant system can send an order request message to the SDK server to request the SDK server for an identifier, i.e., an order identifier, capable of identifying the order. The order identifier generated by the SDK server can be an order serial number.

[0097] In step S210, an order feedback message is sent to the merchant system to enable the merchant system to send an SDK call request message to the SDK.

[0098] The SDK server can generate an order feedback message, and the order feedback message includes an order identifier. The SDK server sends the order feedback message to the merchant system, and the order feedback message includes an order identifier. After the merchant system receives the order feedback message, the merchant system can send an SDK call request message to the SDK of the terminal device, and the SDK call request includes an order identifier. The SDK call request message is used to request to call the SDK in the terminal device. The SDK in the terminal device can collect information such as the geographic position of the terminal device and the terminal device identifier in the process of initialization.

[0099] In step S211, a first query feedback message is sent to the SDK in response to a first order query message sent by the SDK.

[0100] The SDK can send a first order query message to the SDK server to query the order information corresponding to the order identifier through the order identifier in the SDK server. The first order query message includes an order identifier. After the SDK server finds the order message corresponding to the order identifier, the SDK server feeds back the order message corresponding to the order identifier to the SDK through a first query feedback message. The first query feedback message includes the order information corresponding to the order identifier. After the SDK receives the first query feedback message, the SDK can send a payment request message to the SDK server.

[0101] ​In some embodiments, merchants can specify a particular payer for payment. The order request message includes the identity information of the specified payer, i.e., a specific payer is designated through the order request message. The payment request message sent by the SDK to the SDK server includes payer identity information such as the user's login account. If the specified payer identity information does not match the payer identity information indicated in the payment request message, the SDK server can send a payment suspension notification message to the SDK, causing the SDK to issue a payment prompt message. The payment prompt message may prompt the user to switch user login accounts and re-pay, or it may indicate the reason for the payment suspension, such as the message displayed on the terminal device: "Login account information does not match the merchant's specified information, payment cannot be made temporarily."

[0102] In some embodiments, payment may be initiated by a user scanning another person's QR code using a terminal device. Before the SDK server receives the payment request message, the SDK and the SDK server need to interact regarding order-related information. Figure 5 A flowchart of yet another embodiment of the payment method provided in the first aspect of this application. Figure 5 and Figure 2 The difference is that, Figure 5 The payment method shown may also include steps S212 and S213.

[0103] In step S212, a second order query message is received from the SDK of the terminal device.

[0104] The terminal device scans the payment code to obtain the first code information. This first code information is the code information read from the payment code. The terminal device's SDK can then send a second order query message to the SDK server. This second order query message requests the order message corresponding to the first code information from the SDK server. The second order query message includes the first code information obtained by the terminal device from scanning the payment code.

[0105] In step S213, a second query feedback message is sent to the SDK.

[0106] The SDK server uses the first code information to locate the corresponding order information. After finding the order information, the SDK server can generate a second query feedback message and send it to the SDK. The second query feedback message includes the order information corresponding to the first code information.

[0107] After receiving the second query feedback message, the SDK can determine the payment amount according to the input of the user, generate a payment request message, and send the payment request message to the SDK server. After receiving the payment request message, the SDK server can determine whether the payment card indicated by the payment request message is available, and send a security verification request message to the security control system if the payment card is available.

[0108] In some embodiments, the payment can be a payment initiated by the user using the terminal device to display a payment code and by another person using the payment terminal to scan the payment code. Before the SDK server receives the payment request message, the SDK can apply for the payment code to the SDK server. Figure 6 A flowchart of still another embodiment of the payment method according to the first aspect of the present application is shown in FIG. 14. Figure 6 Different from Figure 2 The payment method shown in FIG. 13 can further include step S214. Figure 6

[0109] In step S214, a payment code feedback message is sent to the SDK in response to the received payment code application message.

[0110] The payment code application message is sent by the SDK. That is, the SDK in the terminal device can send a payment code application message to the SDK server, and the payment code application message is used to apply for a payment code to the SDK server. The SDK server allocates a payment code for the payment code application message, and feeds back the payment code to the SDK through a payment code feedback message. The payment code feedback message includes the payment code.

[0111] In some examples, the SDK background system includes an SDK background subsystem and a payment code subsystem. The SDK can send a payment code application message to the SDK server in the SDK background subsystem, the SDK server in the SDK background subsystem forwards the payment code application message to the SDK server in the payment code subsystem, the SDK server in the payment code subsystem allocates a payment code for the payment code application message, and sends a payment code feedback message to the SDK server in the SDK background subsystem, and the SDK server in the SDK background subsystem forwards the payment code feedback message to the SDK.

[0112] The payment request message is generated by the payment terminal based on the scanned payment code. After receiving the payment code feedback message, the SDK can display the payment code during payment. The payment terminal scans the payment code to obtain second code information, which is the code information read from the payment code. The payment terminal can generate a payment request message based on the second code information, and send the payment request message to the SDK server.

[0113] ​The second aspect of the present application provides a payment method, which is applied to a terminal device, i.e., the payment method can be executed by the terminal device. The terminal device has an SDK and a host program. Figure 7 The payment method can include steps S301-S304, as shown in the flowchart of an embodiment of the payment method provided by the second aspect of the present application. Figure 7

[0114] In step S301, the SDK acquires a first notification message sent by an SDK server.

[0115] The first notification message is sent by the SDK server based on security verification result information representing that the security verification is passed. The security verification result information is obtained by a security control system based on security verification information in a security verification request message to perform security verification on a payment corresponding to a payment request message. The security verification request message is sent by the SDK server in response to a received payment request message.

[0116] In step S302, in response to the first notification message, the SDK notifies the host program to display a user verification page to prompt the user to input first user verification input information.

[0117] In step S303, the host program feeds back the first user verification input information to a host program server.

[0118] The first user verification input information is used by the host program server to perform user verification to obtain user verification result information.

[0119] In step S304, the SDK sends the user verification result information obtained by the host program from the host program server to the SDK server, so that the SDK server initiates a payment request in the case that the user verification result information represents that the user verification is passed, to complete the payment.

[0120] In some embodiments, the user verification result information is also used to make the SDK server initiate the payment request in the case that the user verification result information satisfies a consistency verification condition.

[0121] In some examples, the consistency verification condition includes that the first user verification result information and second user verification result information are consistent, the first user verification result information is user verification result information transmitted by the host program server to the SDK through the host program, and the second user verification result information is the user verification result information obtained from the host program server.

[0122] The specific content of steps S301-S304 can be referred to the related description in the above embodiments, which will not be repeated here.

[0123] ​In the embodiment of the present application, the SDK server sends a security verification request message to the security control system in response to the payment request message, to request the security control system to perform security verification on the payment, to complete the security verification required by the SDK owner. In the case where the security verification is passed, the SDK in the terminal device receives the message sent by the SDK server, which is used to instruct the SDK to notify the host program to display the user verification page, and the SDK responds to the message to trigger the host program to actively initiate user verification, to complete the user identity security verification required by the host program owner. The two-way verification of the SDK owner and the host program owner is realized in the payment process, the security of the payment is improved, and the security control requirements of the SDK owner and the host program owner are met.

[0124] In some embodiments, the SDK server can request the user verification method from the host program server, the SDK can obtain the feedback of the host program server through the SDK server, and make corresponding operations. Figure 8 The flowchart of another embodiment of the payment method provided by the second aspect of the present application. Figure 8 Different from Figure 7 The difference is that Figure 8 The payment method shown in FIG. 5 can further include steps S305 and S306.

[0125] In step S305, the SDK sends a rejection prompt information in response to the second notification message received by the SDK.

[0126] The second notification message is sent by the SDK server in the case where the verification operation information includes the rejection payment identifier.

[0127] In step S306, the SDK sends a password-free payment prompt information in response to the third notification message received by the SDK.

[0128] The third notification message is sent by the SDK server in the case where the verification operation information includes the password-free payment identifier.

[0129] The user verification method feedback message includes the verification operation information. The user verification method feedback message is sent by the host server in response to the user verification method request message. The user verification method request message is sent by the SDK server to the host program server in the case where the security verification result information indicates that the security verification is passed. The user verification method request message includes one or more than two of the order information corresponding to the payment indicated by the payment request message, the terminal device information and the payment information.

[0130] In some embodiments, the first notification message is sent by the SDK server in a case where the verification operation information comprises a user verification manner identifier. The first notification message comprises the user verification manner identifier, which is used to instruct the SDK to notify the host program to display a user verification page matching the user verification manner identifier, so as to prompt the user to input first user verification input information matching the user verification manner identifier.

[0131] The specific content of steps S305 and S306 can be referred to the related description in the above embodiments, which will not be repeated here.

[0132] In some embodiments, the security verification result information comprises a target host program identifier. The target host program identifier comprises a host program identifier of a payment corresponding to the payment request message. The first notification message is sent by the SDK server in a case where the target user verification initiator is a host program. The target user verification initiator is a user verification initiator matching the target host program identifier in the first correspondence relationship, and the target host program identifier comprises a host program identifier of a payment corresponding to the payment request message. The first correspondence relationship comprises a relationship between a host program identifier and a user verification initiator.

[0133] In some embodiments, in a case where the target user verification initiator is the SDK, the terminal device acquires the fourth notification message sent by the SDK server through the SDK. The fourth notification message is sent by the SDK server in a case where the target user verification initiator is the SDK. The terminal device displays a user verification page through the SDK in response to the fourth notification message, so as to prompt the user to input second user verification input information. The terminal device feeds back the second user verification input information to the SDK server through the SDK. The second user verification input information is used for the SDK server to perform user verification to obtain user verification result information.

[0134] In some embodiments, the payment is initiated by a merchant system or through a merchant program installed in the terminal device. Before the SDK server receives the payment request message, the merchant system and the SDK, and the SDK and the SDK server need to interact on the related information of the order. Figure 9 The flowchart of still another embodiment of the payment method provided by the second aspect of the application. Figure 9 Different from Figure 7 The difference is that Figure 9 The payment method shown in FIG. 7 further comprises steps S307 to S309.

[0135] In step S307, the SDK receives a SDK call request message through the SDK. The SDK call request message is generated by the merchant system in response to the order feedback message.

[0136] The order feedback message and the SDK calling request message include an order identifier. The order identifier is generated by the SDK server in response to an order request message sent by the merchant system.

[0137] In step S308, a first order query message is sent to the SDK server through the SDK in response to the SDK calling request message.

[0138] In step S309, a first query feedback message sent by the SDK server in response to the first order query message is received through the SDK.

[0139] The first query feedback message includes order information corresponding to the order identifier.

[0140] In some embodiments, the order request message includes specified payer identity information. In response to a payment suspension notification message received through the SDK, the terminal device can send payment prompt information through the SDK. The payment suspension notification message is sent by the SDK server in a case where the specified payer identity information is inconsistent with the payer identity information of the payment indicated by the payment request message.

[0141] The specific content of steps S307 to S309 described above can be referred to the related description in the above embodiments, which will not be repeated here.

[0142] In some embodiments, the payment can be a payment initiated by a user using the terminal device to scan a payment code of another person. Before the SDK server receives the payment request message, the SDK and the SDK server need to interact on the related information of the order. Figure 10 The flowchart of still another embodiment of the payment method provided by the second aspect of the present application. Figure 10 Different from Figure 7 The difference is that Figure 10 The payment method shown in FIG. 10 can further include steps S310 to S312.

[0143] In step 310, a payment code is scanned to obtain first code information.

[0144] In step 311, a second order query message is sent to the SDK server through the SDK.

[0145] The second order query message includes the first code information.

[0146] In step 312, a second query feedback message sent by the SDK server is received through the SDK.

[0147] The second query feedback message includes order information corresponding to the first code information.

[0148] The specific content of steps S310 to S312 described above can be referred to the related description in the above embodiments, which will not be repeated here.

[0149] In some embodiments, the payment can be a payment initiated by the user displaying a payment code by using the terminal device and scanned by a payment receiving terminal by using a person. Before the SDK server receives the payment request message, the SDK can apply for the payment code to the SDK server. Figure 11 A flowchart of still another embodiment of the payment method provided by the second aspect of the present application. Figure 11 Different from Figure 7 , the payment method shown in Figure 11 may further include steps S313-S315.

[0150] In step S313, a payment code application message is sent to the SDK server by the SDK.

[0151] In step S314, a payment code feedback message sent by the SDK server is received by the SDK.

[0152] The payment code feedback message includes a payment code.

[0153] In step S315, the payment code is displayed.

[0154] The payment code is used to be scanned by a payment receiving device to generate a payment request message.

[0155] The specific content of steps S313-S315 can be referred to the related description in the above embodiments, which will not be repeated here.

[0156] The third aspect of the present application provides a payment method applied to a host program server, i.e., the payment method can be executed by the host program server. Figure 12 A flowchart of an embodiment of the payment method provided by the third aspect of the present application. As shown in Figure 12 , the payment method can include steps S401-S403.

[0157] In step S401, first user verification input information fed back by the terminal device through the host program is received.

[0158] The first user verification input information is obtained after the SDK notifies the host program to display a user verification page in response to a first notification message. The first notification message is sent by the SDK server based on security verification result information representing that the security verification is passed. The security verification result information is obtained by the security control system based on security verification information in a security verification request message to perform security verification on a payment corresponding to the payment request message. The security verification request message is sent by the SDK server in response to the received payment request message.

[0159] In step S402, user verification is performed according to the first user verification input information to obtain user verification result information.

[0160] In step S403, the user verification result information is sent to the host program in the terminal device, the user verification result information is transmitted to the SDK by the host program, the SDK is caused to send the user verification result information to the SDK server, and in a case where the user verification result information indicates that the user verification is passed, the SDK server is caused to initiate a payment request to complete the payment.

[0161] In some embodiments, after step S403 is performed, the host program server can also send the user verification result information to the SDK server, so that the SDK server initiates a payment request to complete the payment in a case where the user verification result information indicates that the user verification is passed and the user verification result information satisfies a consistency verification condition.

[0162] In some examples, the consistency verification condition includes that the first user verification result information and the second user verification result information are consistent. The first user verification result information is user verification result information transmitted to the SDK by the host program server through the host program, and the second user verification result information is user verification result information obtained from the host program server.

[0163] The specific content of steps S401 to S403 described above can be referred to the related description in the above embodiments, which will not be repeated here.

[0164] In the embodiments of the present application, the SDK server sends a security verification request message to the security control system in response to the payment request message, to request the security control system to perform security verification on the payment, to complete the security verification required by the SDK owner. In a case where the security verification is passed, the SDK server sends a message to the SDK of the terminal device, the message being used to instruct the SDK to notify the host program to display a user verification page, so that the SDK can trigger the host program to actively initiate user verification. The terminal device can receive first user verification input information input by a user, and send the first user verification input information to the host program server, and the host program server can complete the user identity security verification required by the host program owner. The two-way verification of the SDK owner and the host program owner is realized in the payment process, the security of the payment is improved, and the security control requirements of the SDK owner and the host program owner are also met.

[0165] In the above embodiments, the host program server stores a key used for encrypting and decrypting information exchanged between the host program and the SDK, and the specific content can be referred to the related description in the above embodiments, which will not be repeated here.

[0166] In some embodiments, the host program server can accept the request of the SDK server, provide the user verification mode to the SDK server, the SDK can obtain the feedback of the host program server through the SDK server, and make corresponding operation. Figure 13 The flowchart of another embodiment of the payment method provided in the third aspect of the application. Figure 13 Different from Figure 12 The payment method shown in FIG. 4 can further include steps S404 and S405. Figure 13

[0167] In step S404, a user verification mode request message sent by the SDK server in the case that the security verification result information represents that the security verification is passed is received.

[0168] The user verification mode request message includes one or more than two of the order information, the terminal device information and the payment information corresponding to the payment indicated by the payment request message.

[0169] In step S405, according to the user verification mode request message, a user verification mode feedback message is sent to the SDK server.

[0170] The user verification mode feedback message includes verification operation information.

[0171] In the case that the verification operation information includes a payment rejection identifier, the SDK server sends a second notification message to the SDK, and the second notification message is used to instruct the SDK to send a payment rejection prompt information. In the case that the verification operation information includes a password-free payment identifier, the SDK server sends a third notification message to the SDK, and the third notification message is used to instruct the SDK to send a password-free payment prompt information.

[0172] In some embodiments, the first notification message is sent by the SDK server in the case that the verification operation information includes a user verification mode identifier. The first notification message includes the user verification mode identifier, which is used to instruct the SDK to notify the host program to display a user verification page matched with the user verification mode identifier, so as to prompt the user to input first user verification input information matched with the user verification mode identifier.

[0173] The specific content of the above steps S404 and S405 can be referred to the related description in the above embodiments, which will not be repeated here.

[0174] ​In some examples, the security verification result information includes a target host program identifier. The target host program identifier includes a host program identifier of a payment corresponding to the payment request message. The first notification message is sent by the SDK server in a case where the target user verification trigger is a host program. The target user verification trigger is a user verification trigger that matches the target host program identifier in the first correspondence relationship. The target host program identifier includes a host program identifier of a payment corresponding to the payment request message. The first correspondence relationship includes a relationship between a host program identifier and a user verification trigger.

[0175] For ease of illustration, the following describes the payment process between the terminal device, the system, and the server in three scenarios, i.e., a payment initiated by a merchant system or through a merchant program installed in a terminal device, a payment initiated by a terminal device scanning a payment code of another person, and a payment initiated by a payment terminal scanning a payment code.

[0176] In this example, the payment is initiated by a merchant system or through a merchant program installed in a terminal device. Figure 14 A flowchart of an example of the payment process provided by the embodiments of the present application. The terminal device includes an SDK and a host program. As shown in Figure 14 The payment process includes steps S501 to S522.

[0177] In step S501, after the user places an order, the merchant system sends an order request message to the SDK server.

[0178] In step S502, the SDK server sends an order feedback message to the merchant system in response to the order request message. The order feedback message can include an order identifier generated by the SDK server.

[0179] In step S503, the merchant system sends an SDK call request message to the SDK in the terminal device.

[0180] In step S504, the SDK collects terminal device information.

[0181] In step S505, the SDK sends a first order query message to the SDK server.

[0182] In step S506, the SDK server feeds back a first query feedback message to the SDK.

[0183] In step S507, the SDK sends a payment request message to the SDK server.

[0184] In step S508, the SDK server sends a security verification request message to the security control system.

[0185] In step S509, the security control system performs security verification on the payment indicated by the payment request message.

[0186] In step S510, the security control system sends the security verification result information back to the SDK server.

[0187] In step S511, if the security verification result information indicates that the security verification has passed, the SDK server sends a user verification method request message to the host program server.

[0188] In step S512, the host program server responds to the user authentication method request message by sending a user authentication method feedback message to the SDK server. The user authentication method feedback message includes a user authentication method identifier.

[0189] In step S513, the SDK server sends a first notification message to the SDK. The first notification message includes a user authentication method identifier.

[0190] In step S514, the SDK transmits the user authentication method identifier to the host program.

[0191] In step S515, the host program is triggered to display a user verification page that matches the user verification method identifier.

[0192] In step S516, the host program receives the first user authentication input information from the user and sends the first user authentication input information to the host program server.

[0193] In step S517, the host program server performs user verification based on the first user verification input information and obtains user verification result information.

[0194] In step S518, the SDK server obtains user authentication result information from the host program server. For ease of explanation, the user authentication result information obtained directly from the host server by the SDK server is referred to as the second user authentication result information.

[0195] In step S519, the host program server sends user verification result information to the host program.

[0196] In step S520, the host program sends the user verification result information back to the SDK.

[0197] In step S521, the SDK sends the user authentication result information back to the SDK server. For ease of explanation, the user authentication result information obtained by the SDK server from the SDK is referred to as the first user authentication result information.

[0198] In step S522, if the first user verification result information and the second user verification result information are consistent, the SDK server initiates a payment request to complete the payment.

[0199] The specific content of the steps S501 to S522 can be referred to the related description in the above embodiments, which will not be repeated here.

[0200] In this example, the payment is initiated by the terminal device scanning the collection code of others. Figure 15 Another example of the payment process provided by the embodiments of the present application is shown in the flowchart. The terminal device includes SDK and host program. As shown, the payment process can include steps S601 to S621. Figure 15

[0201] In step S601, the terminal device scans the collection code to obtain first code information, and the SDK sends a second order query message to the SDK server. The second order query message includes the first code information.

[0202] In step S602, the SDK server sends a second query feedback message to the SDK.

[0203] In step S603, the SDK receives user input to determine the payment amount.

[0204] In step S604, the SDK sends a payment request message to the SDK server.

[0205] In step S605, the SDK server determines whether there is an available payment card.

[0206] In step S606, in the case where there is an available payment card, the SDK server sends a security verification request message to the security control system.

[0207] In step S607, the security control system performs security verification on the payment indicated by the payment request message.

[0208] In step S608, the security control system feeds back security verification result information to the SDK server.

[0209] In step S609, in the case where the security verification result information represents that the security verification is passed, the SDK server sends a user verification method request message to the host program server.

[0210] In step S610, the host program server sends a user verification method feedback message to the SDK server in response to the user verification method request message. The user verification method feedback message includes a user verification method identifier.

[0211] In step S611, the SDK server sends a first notification message to the SDK. The first notification message includes the user verification method identifier.

[0212] In step S612, the SDK transmits the user verification method identifier to the host program.​

[0213] In step S613, the host program is triggered to display a user authentication page matching the user authentication mode identifier.

[0214] In step S614, the host program receives the first user authentication input information input by the user and sends the first user authentication input information to the host program server.

[0215] In step S615, the host program server performs user authentication according to the first user authentication input information to obtain user authentication result information.

[0216] In step S616, the SDK server obtains the user authentication result information from the host program server. For ease of illustration, the user authentication result information obtained by the SDK server directly from the host server is referred to as second user authentication result information.

[0217] In step S617, the host program server sends the user authentication result information to the host program.

[0218] In step S618, the host program feeds back the user authentication result information to the SDK.

[0219] In step S619, the SDK feeds back the user authentication result information to the SDK server. For ease of illustration, the user authentication result information obtained by the SDK server from the SDK is referred to as first user authentication result information.

[0220] In step S620, when the first user authentication result information and the second user authentication result information are consistent, the SDK server initiates a payment request to the host program server.

[0221] In step S621, the host program server initiates a payment request to the payment party account management system to complete the payment.

[0222] The specific content of steps S601 to S621 can be referred to the related description in the above embodiments, which will not be repeated here.

[0223] In this example, the payment is initiated by the payment receiving terminal scanning the payment code displayed by the terminal device. The terminal device includes the SDK and the host program. Here, the SDK background system is taken as an example including the SDK background subsystem and the payment code subsystem. For ease of illustration, the SDK server in the SDK background subsystem is referred to as the first SDK server, and the SDK server in the payment code subsystem is referred to as the second SDK server. Figure 16 A flowchart of another example of the payment process provided by the embodiments of the present application. As shown in the figure, the payment process can include steps S701 to S723. Figure 16 ​

[0224] In step S701, the SDK in the terminal device sends a payment code application message to the second SDK server through the first SDK server.

[0225] In step S702, the second SDK server allocates a payment code and sends a payment code feedback message to the SDK through the first SDK server. The payment code feedback message includes the payment code.

[0226] In step S703, the payment receiving terminal scans the payment code displayed by the terminal device to obtain second code information and sends a payment request message to the second SDK server.

[0227] In step S704, the second SDK server can send a payment policy query message to the host program server through the payment policy system.

[0228] In step S705, the host program server feeds back payment policy information to the second SDK server through the payment policy system.

[0229] In step S706, the second SDK server sends an additional processing request message to the first SDK server. The additional processing request message includes the payment policy information.

[0230] In step S707, the first SDK server sends a security verification request message to the security control system.

[0231] In step S708, the security control system performs security verification on the payment indicated by the payment request message.

[0232] In step S709, the security control system feeds back security verification result information to the first SDK server.

[0233] In step S710, the first SDK server synchronizes payment information, order information and other information to the host program server through the second SDK server.

[0234] In step S711, the first SDK server sends a user verification method request message to the host program server through the second SDK server.

[0235] In step S712, the host program server sends a user verification method feedback message to the first SDK server through the second SDK server. The user verification method feedback message includes a user verification method identifier.

[0236] In step S713, the first SDK server sends a first notification message to the SDK. The first notification message includes the user verification method identifier.

[0237] In step S714, the SDK transmits the user authentication mode identifier to the host program.

[0238] In step S715, the host program is triggered to display a user authentication page matching the user authentication mode identifier.

[0239] In step S716, the host program receives first user authentication input information input by the user and sends the first user authentication input information to the host program server.

[0240] In step S717, the host program server performs user authentication according to the first user authentication input information to obtain user authentication result information.

[0241] In step S718, the first SDK server obtains the user authentication result information from the host program server through the second SDK server. For ease of illustration, the user authentication result information obtained by the SDK server from the host server through the second SDK server is referred to as second user authentication result information.

[0242] In step S719, the host program server sends the user authentication result information to the host program.

[0243] In step S720, the host program feeds back the user authentication result information to the SDK.

[0244] In step S721, the SDK feeds back the user authentication result to the first SDK server. For ease of illustration, the user authentication result information obtained by the first SDK server from the SDK is referred to as first user authentication result information. If the host program belongs to the same party as the payment card, step S724 is skipped; if the host program belongs to a different party from the payment card, step S725 is skipped.

[0245] In step S722, when the first user authentication result information and the second user authentication result information are consistent, the first SDK server initiates a payment request to the payer account management system through the second SDK server and the host program server to complete the payment.

[0246] In step S723, when the first user authentication result information and the second user authentication result information are consistent, the first SDK server initiates a payment request to the payer account management system through the second SDK server to complete the payment.

[0247] Before the above steps S722 and S723, if the payment uses payment policy information, the second SDK server can also interact with the payment policy system to honor the payment policy information.

[0248] The specific content of the steps S701 to S723 can be referred to the related description in the above embodiments, and will not be repeated here.

[0249] The fourth aspect of the present application provides an SDK server. Figure 17 An embodiment of the SDK server provided by the fourth aspect of the present application is shown in the structure diagram. As shown in the figure, the SDK server 800 can include a sending module 801 and a receiving module 802. Figure 17 The sending module 801 can be configured to send a security verification request message to a security control system in response to a received payment request message.

[0250] The security verification request message includes security verification information, which is used to instruct the security control system to perform security verification on a payment corresponding to the payment request message according to the security verification information.

[0251] The receiving module 802 can be configured to receive security verification result information sent by the security control system.

[0252] The sending module 801 can also be configured to send a first notification message to an SDK in a terminal device in a case where the security verification result information indicates that the security verification is passed.

[0253] The terminal device has the SDK and a host program. The first notification message is used to instruct the SDK to notify the host program to display a user verification page to prompt a user to input first user verification input information. The first user verification input information is used for the host program server to perform user verification to obtain user verification result information.

[0254] The sending module 801 can also be configured to initiate a payment request to complete the payment in a case where the user verification result information indicates that the user verification is passed.

[0255] In some embodiments, the sending module 801 can be configured to initiate the payment request in a case where the user verification result information satisfies a consistency verification condition.

[0256] In some examples, the consistency verification condition includes that the first user verification result information and second user verification result information are consistent.

[0257] The first user verification result information is user verification result information transmitted by the host program server to the SDK through the host program. The second user verification result information is user verification result information obtained from the host program server.

[0258] The first user verification result information is user verification result information transmitted by the host program server to the SDK through the host program. The second user verification result information is user verification result information obtained from the host program server.

[0259] In the embodiment of the present application, the SDK server sends a security verification request message to the security control system in response to the payment request message, to request the security control system to perform security verification on the payment, to complete the security verification required by the SDK owner. In the case where the security verification is passed, the SDK server sends a message to the SDK of the terminal device, to instruct the SDK to notify the host program to display a user verification page, to enable the SDK to trigger the host program to actively initiate user verification, to complete the user identity security verification required by the host program owner. The two-way verification of the SDK owner and the host program owner is realized in the payment process, the security of the payment is improved, and the security control requirements of the SDK owner and the host program owner are met.

[0260] In some examples, the SDK server stores a key for encrypting and decrypting information of interaction between the SDK and the host program.

[0261] In some embodiments, the sending module 801 can also be configured to send a user verification method request message to the host program server in the case where the security verification result information indicates that the security verification is passed.

[0262] The user verification method request message includes one or more than two of the order information corresponding to the payment indicated by the payment request message, the terminal device information, and the payment information.

[0263] The receiving module 802 can also be configured to receive a user verification method feedback message sent by the host program server.

[0264] The user verification method feedback message includes verification operation information.

[0265] The sending module 801 can also be configured to send a second notification message to the SDK in the case where the verification operation information includes a payment rejection identifier.

[0266] The second notification message is used to instruct the SDK to send a payment rejection prompt information.

[0267] The receiving module 802 can also be configured to send a third notification message to the SDK in the case where the verification operation information includes a password-free payment identifier.

[0268] The third notification message is used to instruct the SDK to send a password-free payment prompt information.

[0269] In some embodiments, the sending module 801 can be configured to send a first notification message to the SDK in the case where the verification operation information includes a user verification method identifier.

[0270] The first notification message includes a user verification mode identifier, which is used to instruct the SDK to notify the host program to display a user verification page matching the user verification mode identifier, so as to prompt the user to input first user verification input information matching the user verification mode identifier.

[0271] In some embodiments, the SDK server can further include a query module.

[0272] The query module can be configured to determine a target user verification initiator corresponding to the target host program identifier according to a preset first correspondence relationship.

[0273] The first correspondence relationship includes a relationship between a host program identifier and a user verification initiator.

[0274] The sending module 801 can be configured to send a first notification message to the SDK in a case where the target user verification initiator is the host program.

[0275] In some embodiments, the sending module 801 can be further configured to send a fourth notification message to the SDK in a case where the target user verification initiator is the SDK.

[0276] The fourth notification message is used to instruct the SDK to display a user verification page to prompt the user to input second user verification input information. The second user verification input information is used for the SDK server to perform user verification to obtain user verification result information.

[0277] In some embodiments, the SDK server 800 can further include an order identifier generation module.

[0278] The order identifier generation module can be configured to generate an order identifier in response to an order request message sent by a merchant system.

[0279] The sending module 801 can be further configured to send an order feedback message to the merchant system, so that the merchant system sends an SDK invocation request message to the SDK.

[0280] The order feedback message and the SDK invocation request message include the order identifier.

[0281] The sending module 801 can be further configured to send a first query feedback message to the SDK in response to a first order query message sent by the SDK.

[0282] The first query feedback message includes order information corresponding to the order identifier.

[0283] In some embodiments, the order request message includes specified payer identity information.

[0284] The sending module 801 can also be configured to send, to the SDK, a payment termination notification message to make the SDK send a payment prompt message in a case where the designated payer identity information is inconsistent with the payer identity information of the payment indicated by the payment request message.

[0285] In some embodiments, the receiving module 802 can also be configured to receive a second order query message sent by the SDK of the terminal device.

[0286] The second order query message includes first code information obtained by the terminal device by scanning a collection code.

[0287] The sending module 801 can also be configured to send a second query feedback message to the SDK.

[0288] The second query feedback message includes order information corresponding to the first code information.

[0289] In some embodiments, the sending module 801 can also be configured to send, to the SDK, a payment code feedback message in response to the received payment code application message.

[0290] The payment code application message is sent by the SDK. The payment code feedback message includes a payment code. Correspondingly, the payment request message is generated by the payment processing device based on the scanned payment code.

[0291] The fifth aspect of the present application provides a terminal device. The terminal device has an SDK and a host program. Figure 18 An embodiment of the terminal device provided by the fifth aspect is shown in a structural schematic diagram. As shown in the diagram, the terminal device 900 can include a receiving module 901, a display module 902, and a sending module 903. Figure 18

[0292] The receiving module 901 can be configured to acquire, by the SDK, a first notification message sent by an SDK server.

[0293] The first notification message is sent by the SDK server based on security verification result information representing a successful security verification. The security verification result information is obtained by a security control system based on security verification information in a security verification request message to perform security verification on a payment corresponding to the payment request message. The security verification request message is sent by the SDK server in response to the received payment request message.

[0294] The display module 902 can be configured to notify, by the SDK, the host program to display a user verification page to prompt the user to input first user verification input information in response to the first notification message.

[0295] The sending module 903 can be configured to feed back, by the host program, the first user verification input information to a host program server.

[0296] ​The first user verification input information is used for the host program server to perform user verification to obtain user verification result information.

[0297] The sending module 903 is further configured to send, by the SDK, the user verification result information obtained by the host program from the host program server to the SDK server, so that the SDK server initiates a payment request to complete payment when the user verification result information indicates that the user verification is passed.

[0298] In some embodiments, the user verification result information is further used to cause the SDK server to initiate the payment request when the user verification result information satisfies a consistency verification condition.

[0299] In some examples, the consistency verification condition comprises that the first user verification result information and the second user verification result information are consistent. The first user verification result information is user verification result information transmitted by the host program server to the SDK through the host program, and the second user verification result information is user verification result information obtained from the host program server.

[0300] In the embodiments of the present application, the SDK server sends a security verification request message to the security control system in response to the payment request message, to request the security control system to perform security verification on the payment, to complete the security verification required by the SDK owner. When the security verification is passed, the SDK in the terminal device receives a message sent by the SDK server, which is used to instruct the SDK to notify the host program to display a user verification page, and the SDK responds to the message to trigger the host program to actively initiate user verification, to complete the user identity security verification required by the host program owner. The two-way verification of the SDK owner and the host program owner is realized in the payment process, the security of the payment is improved, and the security control requirements of the SDK owner and the host program owner are met.

[0301] In some examples, the SDK has a security domain, and information in the SDK is stored in the security domain.

[0302] The information exchanged between the SDK and the host program is encrypted information. The encryption and decryption keys in the SDK are stored in the SDK server, and the encryption and decryption keys in the host program are stored in the host program server.

[0303] In some embodiments, the display module 902 is further configured to respond to the second notification message received by the SDK, and send a rejection prompt information by the SDK.

[0304] The second notification message is sent by the SDK server when the verification operation information comprises a payment rejection identifier.

[0305] The display module 902 can also be configured to send, by the SDK, the prompt information of the password-free payment in response to a third notification message received by the SDK.

[0306] The third notification message is sent by the SDK server in a case where the verification operation information includes the password-free payment identifier.

[0307] The user verification mode feedback message includes the verification operation information. The user verification mode feedback message is sent by the host server in response to the user verification mode request message. The user verification mode request message is sent by the SDK server to the host program server in a case where the security verification result information indicates that the security verification is passed. The user verification mode request message includes one or more than two of the order information corresponding to the payment indicated by the payment request message, the terminal device information, and the payment information.

[0308] In some embodiments, the first notification message is sent by the SDK server in a case where the verification operation information includes the user verification mode identifier. The first notification message includes the user verification mode identifier, and is used to instruct the SDK to notify the host program to display a user verification page matched with the user verification mode identifier, so as to prompt the user to input first user verification input information matched with the user verification mode identifier.

[0309] In some embodiments, the security verification result information includes a target host program identifier. The target host program identifier includes a host program identifier of a payment corresponding to the payment request message. The first notification message is sent by the SDK server in a case where the target user verification initiator is the host program. The target user verification initiator is a user verification initiator matched with the target host program identifier in a first correspondence relationship. The target host program identifier includes a host program identifier of a payment corresponding to the payment request message. The first correspondence relationship includes a relationship between the host program identifier and the user verification initiator.

[0310] In some embodiments, the receiving module 901 can also be configured to acquire, by the SDK, a fourth notification message sent by the SDK server. The fourth notification message is sent by the SDK server in a case where the target user verification initiator is the SDK.

[0311] The display module 902 can also be configured to call, by the SDK, the user verification page to prompt the user to input second user verification input information in response to the fourth notification message.

[0312] The sending module 903 can also be configured to feed back, by the SDK, the second user verification input information to the SDK server.

[0313] The second user verification input information is used for the SDK server to perform user verification to obtain user verification result information.

[0314] In some embodiments, the receiving module 901 can also be configured to receive an SDK call request message through the SDK.

[0315] The SDK call request message is generated by the merchant system in response to an order feedback message. The order feedback message and the SDK call request message comprise an order identifier. The order identifier is generated by the SDK server in response to an order request message sent by the merchant system.

[0316] The sending module 903 can also be configured to send a first order query message to the SDK server through the SDK in response to the SDK call request message.

[0317] The receiving module 901 can also be configured to receive a first query feedback message sent by the SDK server in response to the first order query message through the SDK.

[0318] The first query feedback message comprises order information corresponding to the order identifier.

[0319] In some embodiments, the order request message comprises specified payer identity information.

[0320] The display module 902 can also be configured to send payment prompt information through the SDK in response to a payment suspension notification message received through the SDK.

[0321] The payment suspension notification message is sent by the SDK server in a case where the specified payer identity information is inconsistent with the payer identity information of the payment indicated by the payment request message.

[0322] In some embodiments, the terminal device 900 can further comprise a scanning module.

[0323] The scanning module can be configured to scan a payment code to obtain first code information.

[0324] The sending module 903 can also be configured to send a second order query message to the SDK server through the SDK.

[0325] The second order query message comprises the first code information.

[0326] The receiving module 901 can also be configured to receive a second query feedback message sent by the SDK server through the SDK.

[0327] The second query feedback message comprises order information corresponding to the first code information.

[0328] In some embodiments, the sending module 903 can also be configured to send a payment code application message to the SDK server through the SDK.

[0329] The receiving module 901 can also be configured to receive a payment code feedback message sent by the SDK server through the SDK, the payment code feedback message comprising a payment code.

[0330] The display module 902 can also be configured to display the payment code.

[0331] The payment code is configured to be scanned by the payment receiving device to generate the payment request message.

[0332] The sixth aspect of the present application provides a host program server. Figure 19 An embodiment of the host program server provided by the sixth aspect is shown in the structural diagram. As shown in the diagram, the host program server 1000 can include a receiving module 1001, a verification module 1002, and a sending module 1003. Figure 19

[0333] The receiving module 1001 can be configured to receive the first user verification input information fed back by the host program of the terminal device.

[0334] The terminal device has a software development kit (SDK) and a host program. The first user verification input information is obtained after the SDK notifies the host program to display a user verification page in response to a first notification message. The first notification message is sent by the SDK server based on security verification result information representing that the security verification is passed. The security verification result information is obtained by the security control system based on security verification information in a security verification request message to perform security verification on a payment corresponding to the payment request message. The security verification request message is sent by the SDK server in response to the received payment request message.

[0335] The verification module 1002 can be configured to perform user verification based on the first user verification input information to obtain user verification result information.

[0336] The sending module 1003 can be configured to send the user verification result information to the host program in the terminal device, transmit the user verification result information to the SDK through the host program, and send the user verification result information to the SDK server to make the SDK server initiate a payment request to complete the payment in the case where the user verification result information represents that the user verification is passed.

[0337] In some embodiments, the sending module 1003 can also be configured to send the user verification result information to the SDK server to make the SDK server initiate a payment request to complete the payment in the case where the user verification result information represents that the user verification is passed and the user verification result information satisfies a consistency verification condition.

[0338] In some examples, the consistency verification condition includes that the first user verification result information and second user verification result information are consistent.

[0339] ​The first user verification result information is user verification result information transmitted by the host program server to the SDK through the host program. The second user verification result information is user verification result information obtained from the host program server.

[0340] In the embodiment of the present application, the SDK server sends a security verification request message to the security control system in response to the payment request message, to request the security control system to perform security verification on the payment, to complete the security verification required by the SDK owner. In the case where the security verification is passed, the SDK server sends a message to the SDK of the terminal device, indicating that the SDK notifies the host program to display the user verification page, so that the SDK can trigger the host program to actively initiate user verification. The terminal device can receive the first user verification input information input by the user, and send the first user verification input information to the host program server, and the host program server can complete the user identity security verification required by the host program owner. The two-way verification of the SDK owner and the host program owner is realized in the payment process, which improves the security of the payment, and also meets the security control needs of the SDK owner and the host program owner.

[0341] In some examples, the host program server stores a key for encrypting and decrypting information of interaction between the host program and the SDK.

[0342] In some embodiments, the receiving module 1001 can also be used to receive a user verification method request message sent by the SDK server in the case where the security verification result information indicates that the security verification is passed.

[0343] The user verification method request message includes one or more of the order information corresponding to the payment indicated by the payment request message, the terminal device information, and the payment information.

[0344] The sending module 1003 can also be used to send a user verification method feedback message to the SDK server according to the user verification method request message.

[0345] The user verification method feedback message includes verification operation information.

[0346] In the case where the verification operation information includes a payment rejection identifier, the SDK server sends a second notification message to the SDK, and the second notification message is used to instruct the SDK to send a payment rejection prompt information. In the case where the verification operation information includes a password-free payment identifier, the SDK server sends a third notification message to the SDK, and the third notification message is used to instruct the SDK to send a password-free payment prompt information.

[0347] In some embodiments, the first notification message is sent by the SDK server in a case where the verification operation information includes a user verification manner identifier. The first notification message includes the user verification manner identifier, which is used to instruct the SDK to notify the host program to display a user verification page matching the user verification manner identifier, so as to prompt the user to input first user verification input information matching the user verification manner identifier.

[0348] In some embodiments, the security verification result information includes a target host program identifier. The target host program identifier includes a host program identifier of a payment corresponding to the payment request message.

[0349] The first notification message is sent by the SDK server in a case where the target user verification initiator is a host program. The target user verification initiator is a user verification initiator matching the target host program identifier in the first correspondence relationship. The target host program identifier includes a host program identifier of a payment corresponding to the payment request message. The first correspondence relationship includes a relationship between a host program identifier and a user verification initiator.

[0350] The seventh aspect of the present application provides an SDK server. Figure 20 An embodiment of the SDK server provided by the seventh aspect of the present application is shown in a structural schematic diagram. As shown in the figure, the SDK server 1100 includes a memory 1101, a processor 1102, and a computer program stored in the memory 1101 and executable on the processor 1102. Figure 20

[0351] In one example, the processor 1102 described above can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured as one or more integrated circuits that implement one or more embodiments of the present application.

[0352] The memory 1101 can include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions and, when the software is executed (e.g., by one or more processors), is operable to perform the operations described with reference to the payment method according to the first aspect of the present application.

[0353] ​The processor 1102 runs a computer program corresponding to the executable program code stored in the memory 1101 to implement the payment method in the above-described embodiments of the first aspect by reading the executable program code.

[0354] In some examples, the SDK server 1100 can further include a communication interface 1103 and a bus 1104. As shown, the memory 1101, the processor 1102, and the communication interface 1103 are connected through the bus 1104 and complete communication with each other. Figure 20

[0355] The communication interface 1103 is mainly used to realize the communication between various modules, devices, units and / or equipment in the embodiments of the present application. The input device and / or the output device can also be accessed through the communication interface 1103.

[0356] The bus 1104 includes hardware, software or both to couple components of the SDK server 1100 to each other. By way of example, and not limitation, the bus 1104 can include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or another suitable bus or a combination of two or more of these. Where appropriate, the bus 1104 can include one or more buses. Although the present application describes and illustrates a particular bus, the present application contemplates any suitable bus or interconnect.

[0357] ​The eighth aspect of the present application provides a terminal device, which can include a memory, a processor, and a computer program stored in the memory and executable on the processor. The types and relationships of the memory and the processor can refer to the related descriptions of the memory and the processor in the SDK server described above. The differences from the SDK server described above include that when the software in the memory is executed, it can be operated to perform the operations described with reference to the payment method in the embodiment of the second aspect of the present application; and the processor runs the computer program corresponding to the executable program code in the memory by reading the executable program code, to implement the payment method in the embodiment of the second aspect described above. In some examples, the terminal device can also include a communication interface and a bus. The memory, the processor, and the communication interface can be connected through the bus and complete communication with each other. The communication connection between the memory, the processor, the communication interface, and the bus in the SDK server shown in FIG. 8 will not be repeated here. Figure 20 The communication connection between the memory, the processor, the communication interface, and the bus in the SDK server shown in FIG. 8 will not be repeated here.

[0358] The ninth aspect of the present application provides a host program server, which can include a memory, a processor, and a computer program stored in the memory and executable on the processor. The types and relationships of the memory and the processor can refer to the related descriptions of the memory and the processor in the SDK server described above. The differences from the SDK server described above include that when the software in the memory is executed, it can be operated to perform the operations described with reference to the payment method in the embodiment of the third aspect of the present application; and the processor runs the computer program corresponding to the executable program code in the memory by reading the executable program code, to implement the payment method in the embodiment of the third aspect described above. In some examples, the host program server can also include a communication interface and a bus. The memory, the processor, and the communication interface can be connected through the bus and complete communication with each other. The communication connection between the memory, the processor, the communication interface, and the bus in the SDK server shown in FIG. 8 will not be repeated here. Figure 20 The communication connection between the memory, the processor, the communication interface, and the bus in the SDK server shown in FIG. 8 will not be repeated here.

[0359] The tenth aspect of the present application provides a payment system, which can include the SDK server, the terminal device, and the host program server in the embodiments described above. The specific content of the SDK server, the terminal device, and the host program server can refer to the related descriptions in the embodiments described above, and will not be repeated here.

[0360] The eleventh aspect of the present application further provides a computer readable storage medium, which stores computer program instructions. The computer program instructions are executed by a processor to implement the payment method of the first aspect, the payment method of the second aspect and / or the payment method of the third aspect, and achieve the same technical effects. To avoid repetition, details are not described herein. The computer readable storage medium can include a non-transitory computer readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disc or an optical disc, and the like, which is not limited herein.

[0361] The embodiments of the present application can also provide a computer program product, instructions in the computer program product can be executed by a processor of an SDK server, a terminal device and a host program server, so that the SDK server, the terminal device and the host program server execute the payment method in the embodiments of the first aspect, the payment method in the embodiments of the second aspect and the payment method in the embodiments of the third aspect.

[0362] It should be noted that each embodiment in the specification is described in a progressive manner, and the same or similar parts of each embodiment can be referred to each other. Each embodiment mainly describes the difference from other embodiments. For the SDK server embodiment, the terminal device embodiment, the host program server embodiment, the system embodiment, the computer readable storage medium embodiment and the computer program product embodiment, the related parts can be referred to the description of the method embodiment. The present application is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art can make various changes, modifications and additions, or change the order of the steps, after understanding the spirit of the present application. Moreover, to be brief, the detailed description of the known method technology is omitted herein.

[0363] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. Alternatively, computer program implemented steps can be

[0364] Those skilled in the art will understand that the embodiments described above are merely exemplary and not limiting. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Those skilled in the art will understand and appreciate other variations of the disclosed embodiments upon studying the drawings, the specification and the claims. In the claims, the term "comprising" does not exclude other devices or steps; the term "one" does not exclude a plurality; the term "first", "second" etc. do not imply any order; the terms "first", "second" etc. are used to name the names and not to indicate any specific order. Any reference signs in the claims should not be construed as limiting the scope of the claims. The functions of a plurality of parts can be carried out by a single hardware or software module. The fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A payment method, characterized in that, The method applied to a software development kit (SDK) server comprises the following steps: In response to a received payment request message, a security verification request message is sent to a security control system, the security verification request message comprising security verification information for instructing the security control system to perform security verification on a payment corresponding to the payment request message according to the security verification information; Security verification result information sent by the security control system is received; In a case where the security verification result information indicates that the security verification is passed, a first notification message is sent to an SDK in a terminal device, the terminal device comprising the SDK and a host program, the first notification message being used to instruct the SDK to instruct the host program to display a user verification page to prompt a user to input first user verification input information, the first user verification input information being used for the host program server to perform user verification to obtain user verification result information; In a case where the user verification result information indicates that the user verification is passed, a payment request is initiated to complete the payment; The initiation of the payment request comprises initiating the payment request in a case where the user verification result information satisfies a consistency verification condition; The consistency verification condition comprises that first user verification result information and second user verification result information are consistent, the first user verification result information being the user verification result information transmitted by the host program server to the SDK through the host program, and the second user verification result information being the user verification result information obtained from the host program server.

2. The method of claim 1, wherein, After the security verification result information sent by the security control system is received, the following steps are further included: In a case where the security verification result information indicates that the security verification is passed, a user verification mode request message is sent to the host program server, the user verification mode request message comprising one or more than two of order information corresponding to the payment indicated by the payment request message, terminal device information and payment information; User verification mode feedback information sent by the host program server is received, the user verification mode feedback information comprising verification operation information; In a case where the verification operation information comprises a payment rejection identifier, a second notification message is sent to the SDK, the second notification message being used to instruct the SDK to issue payment rejection prompt information; In a case where the verification operation information comprises a password-free payment identifier, a third notification message is sent to the SDK, the third notification message being used to instruct the SDK to issue password-free payment prompt information.

3. The method of claim 2, wherein, The sending of the first notification message to the SDK in the terminal device comprises the following steps: In a case where the verification operation information comprises the user verification mode identifier, the first notification message is sent to the SDK, the first notification message comprising the user verification mode identifier and being used to instruct the SDK to instruct the host program to display a user verification page matched with the user verification mode identifier to prompt the user to input the first user verification input information matched with the user verification mode identifier.

4. The method according to any one of claims 1 to 3, characterized in that, The security verification result information includes a target host program identifier, and the target host program identifier includes a host program identifier of a payment corresponding to the payment request message, Before the first notification message is sent to the SDK in the terminal device, the method further includes: According to the target host program identifier and a preset first correspondence relationship, a target user verification trigger corresponding to the target host program identifier is determined, and the first correspondence relationship includes a relationship between a host program identifier and a user verification trigger. The first notification message is sent to the SDK in the terminal device, including: In the case that the target user verification trigger is the host program, the first notification message is sent to the SDK.

5. The method of claim 4, wherein, After the target user verification trigger corresponding to the target host program identifier is determined according to the target host program identifier and the preset first correspondence relationship, the method further includes: In the case that the target user verification trigger is the SDK, a fourth notification message is sent to the SDK, and the fourth notification message is used to instruct the SDK to display a user verification page to prompt a user to input second user verification input information, and the second user verification input information is used for the SDK server to perform user verification to obtain user verification result information.

6. The method of claim 1, wherein, The SDK server stores a key used for encryption and decryption of information exchanged between the SDK and the host program.

7. The method of claim 1, wherein, Before the security verification request message is sent to the security control system in response to the received payment request message, the method further includes: An order identifier is generated in response to an order request message sent by a merchant system; An order feedback message is sent to the merchant system, so that the merchant system sends an SDK calling request message to the SDK, and the order feedback message and the SDK calling request message include the order identifier; A first query feedback message is sent to the SDK in response to a first order query message sent by the SDK, and the first query feedback message includes order information corresponding to the order identifier.

8. The method of claim 7, wherein, The order request message includes specified payer identity information, The method further includes: In the case that the specified payer identity information is inconsistent with payer identity information indicated by the payment request message, a payment suspension notification message is sent to the SDK, so that the SDK sends a payment prompt message.

9. The method of claim 1, wherein, Before the security verification request message is sent to the security control system in response to the received payment request message, the method further includes: A second order query message is received from the SDK of the terminal device, and the second order query message includes first code information obtained by the terminal device by scanning a payment code; A second query feedback message is sent to the SDK, and the second query feedback message includes order information corresponding to the first code information.

10. The method of claim 1, wherein, Before the security verification request message is sent to the security control system in response to the received payment request message, the method further includes: A payment code feedback message is sent to the SDK in response to a received payment code application message, the payment code application message is sent by the SDK, and the payment code feedback message includes a payment code; The payment request message is generated by the payment receiving device based on the scanned payment code.

11. A payment method, characterized by The method is applied to a terminal device having a software development kit (SDK) and a host program, and includes: obtaining, by the SDK, a first notification message sent by an SDK server, the first notification message being sent by the SDK server based on security verification result information representing successful security verification, the security verification result information being obtained by a security control system based on security verification information in a security verification request message for security verification of a payment corresponding to a payment request message, the security verification request message being sent by the SDK server in response to the received payment request message; in response to the first notification message, notifying, by the SDK, the host program to display a user verification page to prompt a user to input first user verification input information; feeding back, by the host program, the first user verification input information to a host program server, the first user verification input information being used by the host program server to perform user verification to obtain user verification result information; sending, by the SDK, the user verification result information obtained by the host program from the host program server to the SDK server, so that the SDK server initiates a payment request in a case where the user verification result information represents successful user verification, to complete the payment; wherein the user verification result information is also used to make the SDK server initiate the payment request in a case where the user verification result information satisfies a consistency verification condition; the consistency verification condition includes that the first user verification result information and second user verification result information are consistent, the first user verification result information being the user verification result information transmitted by the host program server to the SDK through the host program, and the second user verification result information being the user verification result information obtained from the host program server.

12. The method of claim 11, wherein, Further comprising: in response to a second notification message received by the SDK, issuing, by the SDK, a rejection prompt information, the second notification message being sent by the SDK server in a case where the verification operation information includes a payment rejection identifier; or, in response to a third notification message received by the SDK, issuing, by the SDK, a password-free payment prompt information, the third notification message being sent by the SDK server in a case where the verification operation information includes a password-free payment identifier; wherein the user verification mode feedback message includes the verification operation information, the user verification mode feedback message being sent by the host program server in response to a user verification mode request message, the user verification mode request message being sent by the SDK server to the host program server in a case where the security verification result information represents successful security verification, the user verification mode request message including one or more than two of order information corresponding to a payment indicated by the payment request message, terminal device information, and payment information.

13. The method of claim 12, wherein, The first notification message is sent by the SDK server when the verification operation information includes the user verification mode identifier, and the first notification message includes the user verification mode identifier, which is used to instruct the SDK to instruct the host program to display a user verification page matching the user verification mode identifier to prompt a user to input the first user verification input information matching the user verification mode identifier.

14. The method of any one of claims 11-13, wherein, The security verification result information includes a target host program identifier, and the target host program identifier includes a host program identifier of a payment corresponding to the payment request message. The first notification message is sent by the SDK server when the target user verification initiator is the host program, the target user verification initiator is a user verification initiator matching a target host program identifier in a first correspondence relationship, the target host program identifier includes a host program identifier of a payment corresponding to the payment request message, and the first correspondence relationship includes a relationship between a host program identifier and a user verification initiator.

15. The method of claim 14, wherein, Further comprising: Obtaining, by the SDK, a fourth notification message sent by the SDK server, the fourth notification message being sent by the SDK server when the target user verification initiator is the SDK; In response to the fourth notification message, calling the SDK to display a user verification page to prompt a user to input second user verification input information; Feeding back, by the SDK, the second user verification input information to the SDK server, the second user verification input information being used by the SDK server to perform user verification to obtain user verification result information.

16. The method of claim 11, wherein, The SDK has a secure domain, and information in the SDK is stored in the secure domain; Information exchanged between the SDK and the host program is encrypted information, and keys for encryption and decryption in the SDK are stored in the SDK server, and keys for encryption and decryption in the host program are stored in the host program server.

17. The method of claim 11, wherein, Before the first notification message sent by the SDK server is obtained by the SDK, further comprising: Receiving, by the SDK, a SDK calling request message, the SDK calling request message being generated by a merchant system in response to an order feedback message, the order feedback message and the SDK calling request message including an order identifier, the order identifier being generated by the SDK server in response to an order request message sent by the merchant system; In response to the SDK calling request message, sending, by the SDK, a first order query message to the SDK server; Receiving, by the SDK, a first query feedback message sent by the SDK server in response to the first order query message, the first query feedback message including order information corresponding to the order identifier.

18. The method of claim 17, wherein, The order request message includes specified payer identity information, The method further comprises: In response to a payment abort notification message received by the SDK, the SDK sends a payment prompt message, the payment abort notification message being sent by the SDK server when the specified payer identity information does not match the payer identity information indicated by the payment request message.

19. The method of claim 11, wherein, Before the first notification message sent by the SDK server is obtained by the SDK, the method further includes: scanning the payer code to obtain first code information; sending a second order query message to the SDK server through the SDK, the second order query message including the first code information; receiving a second query feedback message sent by the SDK server through the SDK, the second query feedback message including order information corresponding to the first code information.

20. The method of claim 11, wherein, Before the first notification message sent by the SDK server is obtained by the SDK, the method further includes: sending a payer code application message to the SDK server through the SDK; receiving a payer code feedback message sent by the SDK server through the SDK, the payer code feedback message including a payer code; displaying the payer code, the payer code being used to be scanned by a payment receiving device to generate the payment request message.

21. A method of payment, characterized by The method applied to a host program server includes: receiving first user verification input information fed back by a terminal device through a host program, the terminal device having a software development kit (SDK) and the host program, the first user verification input information being obtained after the SDK notifies the host program to display a user verification page in response to a first notification message, the first notification message being sent by the SDK server based on security verification result information representing successful security verification, the security verification result information being obtained by a security control system based on security verification information in a security verification request message for security verification of a payment corresponding to a payment request message, the security verification request message being sent by the SDK server in response to the received payment request message; performing user verification according to the first user verification input information to obtain user verification result information; sending the user verification result information to the host program in the terminal device, and transmitting the user verification result information to the SDK through the host program, so that the SDK sends the user verification result information to the SDK server, and initiates a payment request to complete the payment when the user verification result information represents successful user verification; sending the user verification result information to the SDK server, so that the SDK server initiates a payment request to complete the payment when the user verification result information represents successful user verification and the user verification result information meets consistency verification conditions. The consistency verification condition comprises: the first user verification result information and the second user verification result information are consistent, the first user verification result information is the user verification result information transmitted by the host program server to the SDK through the host program, and the second user verification result information is the user verification result information obtained from the host program server.

22. The method of claim 21, wherein, Before the receiving terminal device feeds back the first user verification input information through the host program, the method further comprises: receiving a user verification mode request message sent by the SDK server in the case that the security verification result information represents that the security verification is passed, the user verification mode request message comprising one or more than two of order information corresponding to the payment indicated by the payment request message, terminal device information, and payment information; According to the user verification mode request message, the user verification mode feedback message is sent to the SDK server, and the user verification mode feedback message comprises verification operation information; Wherein, in the case that the verification operation information comprises a payment rejection identifier, the SDK server sends a second notification message to the SDK, and the second notification message is used to instruct the SDK to issue a payment rejection prompt information; in the case that the verification operation information comprises a password-free payment identifier, the SDK server sends a third notification message to the SDK, and the third notification message is used to instruct the SDK to issue a password-free payment prompt information.

23. The method of claim 22, wherein, The first notification message is sent by the SDK server in the case that the verification operation information comprises the user verification mode identifier, and the first notification message comprises the user verification mode identifier, which is used to instruct the SDK to notify the host program to display a user verification page matched with the user verification mode identifier, so as to prompt the user to input the first user verification input information matched with the user verification mode identifier.

24. The method of any one of claims 21 to 23, wherein: The security verification result information comprises a target host program identifier, and the target host program identifier comprises a host program identifier of a payment corresponding to the payment request message, The first notification message is sent by the SDK server in the case that the target user verification initiator is the host program, the target user verification initiator is a user verification initiator matched with the target host program identifier in a first corresponding relationship, the target host program identifier comprises a host program identifier of a payment corresponding to the payment request message, and the first corresponding relationship comprises a relationship between a host program identifier and a user verification initiator.

25. The method of claim 21, wherein, The host program server stores a key for encrypting and decrypting information exchanged between the host program and the SDK.

26. A software development kit (SDK) server, comprising: The method comprises: The sending module is configured to, in response to the received payment request message, send a security verification request message to the security control system, the security verification request message comprising security verification information, which is used to instruct the security control system to perform security verification on a payment corresponding to the payment request message according to the security verification information; The receiving module is configured to receive security verification result information sent by the security control system. The sending module is further configured to send a first notification message to an SDK in a terminal device in a case where the security verification result information indicates that security verification is passed, the terminal device having the SDK and a host program, the first notification message being used to instruct the SDK to instruct the host program to display a user verification page to prompt a user to input first user verification input information, the first user verification input information being used for user verification by a host program server to obtain user verification result information. The sending module is further configured to initiate a payment request to complete payment in a case where the user verification result information indicates that user verification is passed. The initiating of the payment request includes initiating the payment request in a case where the user verification result information satisfies a consistency verification condition, and the consistency verification condition includes that first user verification result information and second user verification result information are consistent, the first user verification result information being the user verification result information transmitted by the host program server to the SDK through the host program, and the second user verification result information being the user verification result information obtained from the host program server.

27. A terminal device, comprising: The terminal device has a software development kit (SDK) and a host program, and the terminal device includes: The receiving module is configured to obtain a first notification message sent by an SDK server through the SDK, the first notification message being sent by the SDK server based on security verification result information indicating that security verification is passed, the security verification result information being obtained by a security control system based on security verification information in a security verification request message for security verification of payment corresponding to a payment request message, the security verification request message being sent by the SDK server in response to the received payment request message. The display module is configured to display a user verification page to prompt a user to input first user verification input information by instructing the host program to display the user verification page through the SDK in response to the first notification message. The sending module is configured to feed back first user verification input information to a host program server through the host program, the first user verification input information being used for user verification by the host program server to obtain user verification result information. The sending module is further configured to send the user verification result information obtained from the host program server through the host program to the SDK server, so that the SDK server initiates a payment request to complete payment in a case where the user verification result information indicates that user verification is passed. The payment request initiation includes initiating the payment request when the user verification result information meets consistency verification conditions. The consistency verification conditions include that the first user verification result information and the second user verification result information are consistent. The first user verification result information is the user verification result information transmitted by the host program server to the SDK through the host program. The second user verification result information is the user verification result information obtained from the host program server.

28. A host program server, characterized by The payment method comprises: The receiving module is configured to receive first user verification input information fed back by a terminal device through a host program. The terminal device has a software development kit (SDK) and the host program. The first user verification input information is obtained after the SDK notifies the host program to display a user verification page in response to a first notification message. The first notification message is sent by an SDK server based on security verification result information representing security verification success. The security verification result information is obtained by a security control system based on security verification information in a security verification request message for security verification of a payment corresponding to a payment request message. The security verification request message is sent by the SDK server in response to the received payment request message. The verification module is configured to perform user verification based on the first user verification input information to obtain user verification result information. The sending module is configured to send the user verification result information to the host program in the terminal device, transmit the user verification result information to the SDK through the host program, and enable the SDK to send the user verification result information to the SDK server. When the user verification result information represents user verification success, the SDK server initiates a payment request to complete payment. The sending module is further configured to send the user verification result information to the SDK server to enable the SDK server to initiate a payment request to complete payment when the user verification result information represents user verification success and the user verification result information meets consistency verification conditions. The consistency verification conditions include that the first user verification result information and the second user verification result information are consistent. The first user verification result information is the user verification result information transmitted by the host program server to the SDK through the host program. The second user verification result information is the user verification result information obtained from the host program server.

29. A software development kit (SDK) server, comprising: The payment method comprises: A processor and a memory storing computer program instructions. The processor executes the computer program instructions to implement the payment method according to any one of claims 1 to 10.

30. A terminal device, comprising: The payment method comprises: A processor and a memory storing computer program instructions. The processor executes the computer program instructions to implement the payment method according to any one of claims 11 to 20.

31. A host program server, characterized by The payment method comprises: A processor and a memory storing computer program instructions. The processor implements the payment method as claimed in any one of claims 21 to 25 when executing the computer program instructions.

32. A payment system, characterized by The software development kit (SDK) server as claimed in claim 29, the terminal device as claimed in claim 30, and the host program server as claimed in claim 31.

33. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by a processor to implement the payment method as claimed in any one of claims 1 to 25.

Images