Payment method, apparatus, device, medium and product

Abstract

The application discloses a payment method, device, equipment, medium and product. The payment method comprises the following steps: receiving a first input of triggering a target order in a merchant client; in response to the first input, sending a target order identifier corresponding to the target order from the merchant client to a payment client; and sending a first payment request for the target order to a clearing agency server through the payment client, wherein the first payment request comprises a target payment identifier and the target order identifier, and the target payment identifier is a unique identity identifier of the user in a target payment agency; wherein the first payment request is used to instruct the clearing agency server to send a second payment request to a payment server corresponding to the target payment agency, so that the payment server performs payment processing on the target order according to the target payment identifier and the target order identifier. According to the embodiment of the application, the risk of malicious interception of transaction sensitive information can be reduced, and the security of information transmission in the payment process can be improved.

Description

Technical Field

[0001] This application belongs to the field of payment technology, and in particular relates to a payment method, device, equipment, medium and product. Background Technology

[0002] When a user makes an online purchase and pays for an order using a merchant client installed on their terminal device, they typically need to select a payment method from several available options to complete the payment through the corresponding payment client.

[0003] During the process of switching from the merchant client to the payment client for payment, the merchant client on the terminal device needs to transmit transaction-sensitive information such as the merchant name, payment amount, and the payment account selected by the user to the payment client in a front-end manner so that the payment can be processed.

[0004] Therefore, the current technology of transmitting sensitive transaction information between different clients through the front end poses a risk of malicious interception of information, reducing the security of information transmission during the payment process. Summary of the Invention

[0005] This application provides a payment method, apparatus, device, medium, and product that can reduce the risk of malicious interception of transaction sensitive information and improve the security of information transmission during the payment process.

[0006] In a first aspect, embodiments of this application provide a payment method applied to a terminal device, wherein the terminal device is equipped with a merchant client and a payment client corresponding to a target payment institution, and the method includes:

[0007] Receive the first input from the user in the merchant client that triggers the payment target order;

[0008] In response to the first input, the merchant client sends a target order identifier corresponding to the target order to the payment client;

[0009] The payment client sends a first payment request for the target order to the clearing institution's server. The first payment request includes a target payment identifier and a target order identifier. The target payment identifier is the user's unique identity identifier in the target payment institution.

[0010] The first payment request is used to instruct the clearing institution server to send a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and obtain a payment result.

[0011] Secondly, embodiments of this application provide a payment method applied to a clearing institution's server, the method comprising:

[0012] Receive a first payment request for a target order sent by a payment client corresponding to the target payment institution. The first payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identity identifier of the user in the target payment institution.

[0013] In response to the first payment request, a second payment request is sent to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and to obtain a payment result.

[0014] Thirdly, embodiments of this application provide a payment method applied to a payment server, the method comprising:

[0015] The system receives a second payment request for a target order from a clearing institution server. The second payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identifier of the user in the target payment institution, and the target payment institution is the payment institution corresponding to the payment server.

[0016] In response to the second payment request, the target order is processed for payment based on the target payment identifier and the target order identifier to obtain a payment result.

[0017] Fourthly, embodiments of this application provide a payment device configured in a terminal device, wherein the terminal device is equipped with a merchant client and a payment client corresponding to a target payment institution, and the device includes:

[0018] The first receiving module is used to receive the first input from the user in the merchant client that triggers the payment target order;

[0019] The first sending module is configured to, in response to the first input, send a target order identifier corresponding to the target order from the merchant client to the payment client;

[0020] The first request module is used to send a first payment request for the target order to the clearing institution server through the payment client. The first payment request includes a target payment identifier and the target order identifier. The target payment identifier is the user's unique identity identifier in the target payment institution.

[0021] The first payment request is used to instruct the clearing institution server to send a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and obtain a payment result.

[0022] Fifthly, embodiments of this application provide a payment device configured on a clearing institution server, the device comprising:

[0023] The second receiving module is used to receive a first payment request for a target order sent by a payment client corresponding to the target payment institution. The first payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identity identifier of the user in the target payment institution.

[0024] The second request module is used to respond to the first payment request by sending a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and obtain a payment result.

[0025] Sixthly, embodiments of this application provide a payment device configured on a payment server, the device comprising:

[0026] The third receiving module is used to receive a second payment request for a target order sent by the clearing institution server. The second payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identifier of the user in the target payment institution. The target payment institution is the payment institution corresponding to the payment server.

[0027] The payment processing module is used to respond to the second payment request by performing payment processing on the target order according to the target payment identifier and the target order identifier, and obtaining a payment result.

[0028] In a seventh aspect, embodiments of this application provide an electronic device, which includes: a processor and a memory storing computer program instructions;

[0029] When the processor executes the computer program instructions, it implements the steps of the payment method as described in any of the embodiments of the first, second, or third aspects.

[0030] Eighthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the steps of the payment method as described in any of the embodiments of the first, second, or third aspects.

[0031] Ninthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform the steps of the payment method as described in any one of the embodiments of the first, second, or third aspects.

[0032] The payment method, apparatus, device, medium, and product in this application embodiment, when a user triggers a payment target order, the merchant client sends a target order identifier corresponding to the target order to the payment client. The payment client then sends a first payment request for the target order to the clearing institution server. This first payment request includes the user's unique identifier within the target payment institution, i.e., the target payment identifier, and the target order identifier. This prompts the clearing institution server to further initiate a second payment request to the payment server corresponding to the target payment institution. The target payment institution can then obtain sensitive transaction information in the background based on the target payment identifier and the target order identifier, thereby processing the payment for the target order. In this way, since the merchant client and payment client in the terminal device only transmit the target order identifier corresponding to the target order through a front-end mechanism, without transmitting other sensitive transaction information, the risk of malicious interception of sensitive transaction information can be reduced, improving the security of information transmission during the payment process. Attached Figure Description

[0033] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a flowchart illustrating the payment method based on the payment system provided in this application;

[0035] Figure 2 This is a schematic flowchart of the payment method provided in the first aspect of this application;

[0036] Figure 3 This is a schematic diagram of the payment interaction interface provided in this application;

[0037] Figure 4 This is a schematic diagram of the payment interface in the payment client provided in this application;

[0038] Figure 5This is a schematic diagram of the payment result interface in the merchant client provided in this application;

[0039] Figure 6 This is a schematic flowchart of the payment method provided in the second aspect of this application;

[0040] Figure 7 This is a schematic flowchart of the payment method provided in the third aspect embodiment of this application;

[0041] Figure 8 This is a flowchart illustrating an exemplary payment method provided in this application;

[0042] Figure 9 This is a schematic diagram of the structure of the payment device provided in the first aspect embodiment of this application;

[0043] Figure 10 This is a schematic diagram of the structure of the payment device provided in the second aspect embodiment of this application;

[0044] Figure 11 This is a schematic diagram of the structure of the payment device provided in the third aspect embodiment of this application;

[0045] Figure 12 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0046] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0047] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0048] To address the problems of existing technologies, embodiments of this application provide a payment method, apparatus, device, medium, and product. This payment method can be applied to online payment scenarios. The following is an overall introduction to the payment method provided in this application embodiment, in conjunction with the payment system architecture.

[0049] Figure 1 This is a flowchart illustrating the payment method based on a payment system provided in this application. This payment method can be applied to a payment system that may include terminal devices, a clearinghouse server, and a payment server. The terminal devices may have a merchant client and a payment client installed. Furthermore, the payment server and payment client may be provided by the target payment institution.

[0050] Based on the architecture of the aforementioned payment system, such as Figure 1 As shown in the embodiments of this application, the payment method may include: a terminal device receiving a first input from a user in a merchant client triggering a payment target order; the terminal device responding to the first input sending a target order identifier corresponding to the target order from the merchant client to the payment client; the terminal device sending a first payment request for the target order to a clearing institution server through the payment client; the clearing institution server responding to the first payment request sending a second payment request to a payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier; and the payment server responding to the second payment request processing the payment for the target order based on the target payment identifier and the target order identifier to obtain a payment result. Both the first payment request and the second payment request include a target payment identifier and a target order identifier, whereby the target payment identifier is a unique identifier for the user within the target payment institution.

[0051] The payment methods used at each end are explained in detail below.

[0052] Figure 2 This is a schematic flowchart of a payment method provided in one embodiment of this application. The payment method can be applied to a terminal device, which includes a merchant client and a payment client corresponding to the target payment institution.

[0053] like Figure 2 As shown, this payment method may specifically include the following steps:

[0054] S210, Receive the first input from the user in the merchant client that triggers the payment target order;

[0055] S220. In response to the first input, the merchant client sends a target order identifier corresponding to the target order to the payment client;

[0056] S230. Send a first payment request for the target order to the clearing institution's server through the payment client. The first payment request includes a target payment identifier and a target order identifier. The target payment identifier is the user's unique identity identifier in the target payment institution.

[0057] In this embodiment of the application, the first payment request is used to instruct the clearing institution server to send a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and obtain the payment result.

[0058] Therefore, when a user triggers a payment for a target order, the merchant client sends a target order identifier corresponding to that target order to the payment client. The payment client then sends a first payment request for the target order to the clearing institution's server. This first payment request includes the user's unique identifier within the target payment institution, i.e., the target payment identifier, as well as the target order identifier. This prompts the clearing institution's server to initiate a second payment request to the payment server corresponding to the target payment institution. This allows the target payment institution to obtain sensitive transaction information in the background based on the target payment identifier and the target order identifier, thereby processing the payment for the target order. In this way, since the merchant client and payment client on the terminal device only transmit the target order identifier corresponding to the target order through a front-end mechanism, without transmitting other sensitive transaction information, the risk of malicious interception of sensitive transaction information can be reduced, improving the security of information transmission during the payment process.

[0059] The specific implementation methods for each of the above steps are described below.

[0060] In some implementations, in S210, the first input may be the input from the user clicking the payment button for the target order in the merchant client.

[0061] For example, after a user selects and places an order in the merchant's client, the user can click the payment button on the order details page to trigger the payment process for the order.

[0062] In some implementations, in S220, after the merchant client receives the first input from the user triggering the payment of the target order, it can send the target order identifier corresponding to the target order to the payment client. The target order identifier can be a unique identifier assigned to the target order by the clearing institution, such as the TN (Transaction Number) of the target order.

[0063] Unlike existing technologies where the merchant client directly sends order information to the payment client via a front-end mechanism, in this embodiment, the merchant client sends a target order identifier to the payment client. The payment client then uses the target order identifier to retrieve order information from different back-end servers and processes the order payment. Since the target order identifier is not sensitive information, even if it is maliciously intercepted by the front-end, sensitive transaction information cannot be obtained, thereby improving the security of information transmission during the payment process.

[0064] In some examples, prior to S220 above, the payment method provided in this application embodiment may further include:

[0065] When a user selects a target payment method for a target order in the merchant client, the merchant client sends the order information corresponding to the target order to the clearing institution server, so that the clearing institution server generates a target order identifier corresponding to the target order based on the order information. Here, the target payment method is the payment method corresponding to the target payment platform, and the target payment platform is a platform that can provide the payment method corresponding to the target payment institution.

[0066] Receive the target order identifier returned by the clearinghouse server.

[0067] Here, order information includes, but is not limited to, merchant name, payment amount, and order number. The target payment method can be the payment method corresponding to the target payment platform, which can be the payment platform corresponding to the clearing institution's server, and this target payment platform can provide the payment method corresponding to the target payment institution.

[0068] For example, such as Figure 3As shown, the merchant client offers multiple optional primary payment methods. After a user triggers a target payment order, several optional primary payment methods can be displayed in the merchant client. If the target payment platform provides payment method A (31), when the user selects payment method A (31), the payment control set in the target payment platform in the merchant client can be invoked. This payment control will then display the online payment checkout interface 30 corresponding to the target payment platform. This online payment checkout interface 30 can display multiple secondary payment methods, including payment method A (32), allowing the user to further select which payment institution's payment method to use. Based on this, when the user selects payment method A (31), the merchant client can send the order information corresponding to the target order to the acquiring institution through the backend server. The acquiring institution then sends this order information to the clearing institution's server. The order information includes, but is not limited to, the merchant name, payment amount, and order number. After receiving the order information, the clearing institution's server can return the TN number corresponding to the target order to the merchant through the acquiring institution and associate the order information and the TN number for storage.

[0069] In some implementations, in step S230, after receiving the target order identifier sent by the merchant client, the payment client can obtain the user's unique identifier within the target payment institution, i.e., the target payment identifier, and send it to the clearing institution's server. The target payment identifier can, for example, be the user's payment client token.

[0070] To ensure users' right to know and right to choose, the target payment identifiers involved in the above process require users to apply for and activate the relevant services through the payment institution before the corresponding payment client token can be assigned to the user.

[0071] For example, after receiving a first payment request carrying a target order identifier and a target payment identifier, the clearing institution server can obtain the corresponding order information based on the target order identifier and send the order information and the target payment identifier together to the payment server. The payment server will then perform user authentication, query the user's payment account, and deduct funds from the user's payment account based on the order information to pay for the target order.

[0072] In other examples, after receiving a first payment request carrying a target order identifier and a target payment identifier, the clearing server may also verify the user's identity and check the order information. After successful verification, the clearing server may directly send a second payment request carrying the target order identifier and the target payment identifier to the payment server. The payment server will then use the sent information to reconstruct the payment information selected by the user when making the payment in the payment client, and based on this payment information, determine the order information of the target order and the user's payment account, and deduct funds from the user's payment account to pay for the target order.

[0073] Furthermore, in some implementations, a payment control may be provided in the merchant client, which may be a payment control provided by a clearing institution. Based on this, after S210 above, the payment method provided in this application embodiment may further include:

[0074] The payment control is invoked by the merchant's client.

[0075] The payment control invokes the payment client and displays the payment interface within the payment client.

[0076] For example, such as Figure 3 As shown, when a user selects payment method 32 (a) in the online payment checkout interface 30, the payment client corresponding to payment method 32 can be invoked through the payment control installed in the merchant client. During this process, the merchant client only transmits the TN number of the target order to the payment client. After the payment client is invoked, as shown... Figure 4 As shown, the payment interface of the payment client can be displayed on the terminal device.

[0077] In this way, by using the payment control installed in the merchant client to uniformly invoke the third-party payment client, the differences in invocation methods between payment clients of different payment institutions can be shielded from the merchant client, reducing the development difficulty of the merchant client.

[0078] Based on this, in order to facilitate the display of order-related information on the payment interface, in some possible implementations, after S220 and before S230, the payment method provided in this application embodiment may further include:

[0079] The payment client sends a first query request for the target order to the payment server. The first query request includes a target order identifier and is used to instruct the payment server to obtain the order information corresponding to the target order from the clearing institution server based on the target order identifier.

[0080] Receive order information corresponding to the target order returned by the payment server;

[0081] The order information is displayed on the payment interface.

[0082] For example, after receiving a target order identifier from a merchant client, the payment client can retrieve order information about the target order through a backend query from the payment institution. Specifically, the payment client can send a first query request carrying the target order identifier to the payment server. Upon receiving this first query request, the payment server can send a second query request carrying the target order identifier to the clearing institution's server through a backend query, thereby retrieving the order information corresponding to the target order from the clearing institution's server. After receiving the order information returned by the clearing institution's server, the payment server can forward the order information to the payment client. Thus, when displaying the payment interface, the payment client can display the order information of the target order on the payment interface.

[0083] In this way, compared with the existing technology of directly transmitting order information while redirecting through the front-end client, the embodiments of this application can effectively reduce the risk of transaction sensitive information being intercepted or leaked during the redirection process between clients.

[0084] In addition, in some embodiments, after the step of displaying order information on the payment interface described above, the payment method provided in this application embodiment may further include:

[0085] Receive a second input from the user based on the payment interface;

[0086] In response to the second input, the system obtains the payment information confirmed by the user, sends the payment information to the payment server through the payment client so that the payment server records the payment information, and upon receiving the second payment request, queries and obtains the payment information based on the target payment identifier and the target order identifier, processes the payment for the target order based on the payment information, and obtains the payment result.

[0087] Here, payment information may include the information of the payment account selected by the user. Correspondingly, the second input may include the user's input of payment information such as the payment account selected in the payment interface, as well as the user's input of identity verification information. Of course, it may also include the user's input of confirming payment intention.

[0088] For example, after a user selects a payment account for a target order in the payment client, enters identity verification information, and clicks the confirmation button, the payment client can send the user-confirmed payment account and other payment information to the backend payment server for registration. Upon receiving the payment information from the payment client, the payment server can associate and store the payment information with the user's target payment identifier and the target order identifier. This allows the server to reconstruct the user-selected payment information based on the target payment identifier and the target order identifier when it receives a second payment request from the clearing institution's server, and then pay the target order based on that payment information.

[0089] Furthermore, in some embodiments, after S230 described above, the payment method provided in this application embodiment may further include:

[0090] Poll the clearinghouse server for payment results corresponding to the target order;

[0091] If a payment result is obtained through polling, the system will redirect from the payment interface to the payment result interface in the merchant's client, where the payment result will be displayed.

[0092] Here, after sending the first payment request to the clearing institution's server, the payment client can poll the clearing institution's server for the payment result. After receiving the payment result, the payment client can trigger a front-end redirection.

[0093] For example, after the payment client polls for the payment result, it can notify the payment control installed in the merchant client to perform a redirection. Upon receiving the redirection notification from the payment client's foreground, the payment control can control the redirection to the payment result interface in the merchant client, such as... Figure 5 As shown, the payment result is displayed in the payment result interface, such as payment success or payment failure.

[0094] In addition, the clearing institution's server can also return the payment results to the merchant's back-end server through the acquiring institution.

[0095] In this way, by returning the payment result and then jumping back, the payment result interface can be automatically switched, as well as the interface can be automatically switched between different clients, simplifying the user operation process.

[0096] Figure 6 This is a schematic flowchart of a payment method provided in one embodiment of this application. This payment method can be applied to a clearing institution's server.

[0097] like Figure 6 As shown, this payment method may specifically include the following steps:

[0098] S610. Receive a first payment request for a target order sent by a payment client corresponding to the target payment institution. The first payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identifier of the user in the target payment institution.

[0099] S620. In response to the first payment request, a second payment request is sent to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and to obtain the payment result.

[0100] Here, the second payment request mentioned above may include a target payment identifier and a target order identifier. The specific explanations of the target payment identifier and the target order identifier can be found in the relevant parts of the foregoing embodiments, and will not be repeated here.

[0101] For example, after receiving the first payment request, the clearing institution server can perform user authentication and order information verification on the payment client that sent the request. After the verification is successful, it can send a second payment request carrying a target payment identifier and a target order identifier to the payment server of the same payment institution as the payment client, so that the payment client can use the target payment identifier and the target order identifier to complete the payment processing of the target order.

[0102] Therefore, by using tokenization technology to mark sensitive information such as user identity information and order information, user identity information is marked with a target payment identifier and order information is marked with a target order identifier. During the payment process, the target payment identifier and target order identifier are used to replace the sensitive transaction information for transmission. In this way, the risk of sensitive transaction information being maliciously intercepted can be further reduced, and the security of information transmission during the payment process can be improved.

[0103] Based on this, prior to S610 above, the payment method provided in this application embodiment may further include:

[0104] Receive order information corresponding to the target order sent by the merchant's client;

[0105] Generate a target order identifier corresponding to the target order based on the order information;

[0106] Return the target order identifier to the merchant's client.

[0107] For an explanation of the above steps, please refer to the relevant parts of the foregoing embodiments, which will not be repeated here.

[0108] Based on this, after the above steps of generating a target order identifier corresponding to the target order based on the order information, the payment method provided in this application embodiment may further include:

[0109] The target order identifier is associated with and stored with the order information.

[0110] In addition, after associating and storing the target order identifier with the order information as described above, and before step S610, the payment method provided in this application embodiment may further include:

[0111] Receive a second query request for the target order sent by the payment server, the second query request including the target order identifier;

[0112] In response to the second query request, query and retrieve the order information corresponding to the target order based on the target order identifier;

[0113] Return order information to the payment server.

[0114] For an explanation of the above steps, please refer to the relevant parts of the foregoing embodiments, which will not be repeated here.

[0115] Figure 7 This is a schematic flowchart of a payment method provided in one embodiment of this application. The payment method can be applied to a payment server, which may be a server corresponding to the aforementioned payment client.

[0116] like Figure 7 As shown, this payment method may specifically include the following steps:

[0117] S710. Receive a second payment request for the target order sent by the clearing institution server. The second payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is the user's unique identity identifier in the target payment institution. The target payment institution is the payment institution corresponding to the payment server.

[0118] S720. In response to the second payment request, process the payment for the target order based on the target payment identifier and the target order identifier to obtain the payment result.

[0119] Here, when the payment server receives a payment request from the clearing institution's server, it can use the target payment identifier and target order identifier carried in the request to determine the user's corresponding payment account and the order information of the target order to be paid. Then, based on this order information, it deducts funds from the user's payment account to complete the payment process for the target order. The payment result can include payment success or payment failure.

[0120] Therefore, by using tokenization technology to mark sensitive information such as user identity information and order information, user identity information is marked with a target payment identifier and order information is marked with a target order identifier. During the payment process, the target payment identifier and target order identifier are used to replace the sensitive transaction information for transmission. In this way, the risk of sensitive transaction information being maliciously intercepted can be further reduced, and the security of information transmission during the payment process can be improved.

[0121] Based on this, prior to S710 above, the payment method provided in this application embodiment may further include:

[0122] Receive a first query request for the target order sent by the payment client corresponding to the target payment institution. The first query request includes the target order identifier.

[0123] In response to the first query request, a second query request for the target order is sent to the clearing institution server. The second query request is used to instruct the clearing institution server to query and obtain the order information corresponding to the target order based on the target order identifier.

[0124] Receive order information returned by the clearing institution's server and forward the order information to the payment client.

[0125] For an explanation of the above steps, please refer to the relevant parts of the foregoing embodiments, which will not be repeated here.

[0126] In addition to forwarding the order information to the payment client as described above, the method also includes:

[0127] Receive and save payment information sent by the payment client.

[0128] Based on this, the aforementioned S720 may specifically include:

[0129] Query and retrieve payment information based on the target payment identifier and the target order identifier;

[0130] The payment is processed based on the payment information to obtain the payment result.

[0131] For an explanation of the above steps, please refer to the relevant parts of the foregoing embodiments, which will not be repeated here.

[0132] To better describe the overall solution, some specific examples are given based on the above embodiments.

[0133] For example, such as Figure 8 The flowchart shown illustrates the payment method. This payment method may include S801-S816, which will be discussed below. Figure 8 This will be explained in detail.

[0134] S801, Initiate an order payment request.

[0135] In some examples, when a user selects a target payment method for a target order within the merchant client on the terminal device and triggers payment for the target order, the merchant client can initiate an order payment request to the acquiring institution, which can carry the order information of the target order.

[0136] S802, Initiate an order payment request.

[0137] In some examples, after receiving the order information of the target order, the acquiring institution can send an order payment request to the clearing institution server corresponding to the target payment method. The order payment request can also carry the order information of the target order.

[0138] S803, Return order acceptance result.

[0139] In some examples, the clearinghouse server may return the TN number corresponding to the target order.

[0140] S804, Return order processing result.

[0141] In some examples, the acquiring institution can return the TN number corresponding to the target order to the merchant client.

[0142] S805, Inquire about payment results.

[0143] In some examples, the merchant client can poll the acquiring institution for payment results.

[0144] S806. Invoke the payment client through the payment control and send the TN number.

[0145] In some examples, after obtaining the TN number, the merchant client can invoke the embedded payment control and, based on the payment method further selected by the user in the online cashier payment interface corresponding to the payment control, activate the corresponding payment client and send the TN number to the payment client.

[0146] S807, Inquire about order information.

[0147] In some examples, after the payment client is invoked, it can send a query request to the payment server to retrieve the order information of the target order. This query request may include the TN number.

[0148] S808, Inquire about order information.

[0149] In some examples, the payment server may further send a query request to the clearing institution server based on the TN number to query and obtain the corresponding order information.

[0150] S809, Return order information.

[0151] In some examples, the clearinghouse server can return the retrieved order information to the payment server in the background.

[0152] S810, Return order information.

[0153] In some examples, the payment server can further return the retrieved order information to the payment client so that the user can verify the amount and confirm their payment intention based on the order information.

[0154] S811, Send payment information;

[0155] In some examples, after a user completes identity authentication and payment intention confirmation in the payment client, the payment client can send the user's selected payment account and other payment information to the payment server for recording.

[0156] S812, Send a payment request and poll for payment results.

[0157] In some examples, the payment client can send a payment request carrying the user's payment token and TN number to the clearinghouse server.

[0158] S813, Send payment request.

[0159] In some examples, the clearinghouse server sends the received user payment token and TN number to the payment server via a relay system and sends a payment request.

[0160] S814. Process payment for the target order.

[0161] In some examples, the payment server reconstructs the payment information selected by the user in the payment client based on the user's payment token and TN number sent by the clearing institution's server, and processes the payment for the target order based on this payment information to obtain the payment result.

[0162] S815, Return payment result.

[0163] In some examples, the payment server can return the payment result of the target order to the clearing server.

[0164] S816, Return payment result.

[0165] In some examples, the clearinghouse server returns the payment result to the acquiring institution in the background. Thus, the merchant client can query the payment result from the acquiring institution, and the payment client can also query the payment result from the clearinghouse server. The payment client can trigger a foreground redirection based on the polled payment result. Upon receiving the foreground redirection notification from the payment client, the payment control in the merchant client controls the terminal device to redirect back to the payment result interface in the merchant client.

[0166] It should be noted that the application scenarios described in the above embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0167] Based on the same inventive concept, this application also provides a payment device. (Specifically combined with...) Figures 9 to 11 Please provide a detailed explanation.

[0168] Figure 9 This is a schematic diagram of a payment device provided in one embodiment of this application. The payment device can be configured in a terminal device, which includes a merchant client and a payment client corresponding to the target payment institution.

[0169] like Figure 9 As shown, the payment device 900 may include:

[0170] The first receiving module 901 is used to receive the first input from the user in the merchant client that triggers a payment target order;

[0171] The first sending module 902 is used to respond to the first input by sending a target order identifier corresponding to the target order from the merchant client to the payment client.

[0172] The first request module 903 is used to send a first payment request for the target order to the clearing institution server through the payment client. The first payment request includes a target payment identifier and the target order identifier. The target payment identifier is the user's unique identity identifier in the target payment institution.

[0173] The first payment request is used to instruct the clearing institution server to send a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and obtain a payment result.

[0174] The payment device 900 described above is explained in detail below:

[0175] In some embodiments, the merchant client includes payment controls;

[0176] The payment device 900 may also include:

[0177] The control invocation module is used to invoke the payment control by the merchant client after receiving the first input from the user in the merchant client to trigger a payment target order;

[0178] The wake-up display module is used to wake up the payment client through the payment control and display the payment interface in the payment client.

[0179] In some embodiments, the payment device 900 further includes:

[0180] The third request module is used to send a first query request for the target order to the payment server through the payment client after the merchant client sends the target order identifier corresponding to the target order to the payment client and before the payment client sends the first payment request for the target order to the clearing institution server. The first query request includes the target order identifier and is used to instruct the payment server to obtain the order information corresponding to the target order from the clearing institution server based on the target order identifier.

[0181] The fourth receiving module is used to receive the order information corresponding to the target order returned by the payment server;

[0182] The first display module is used to display the order information in the payment interface.

[0183] In some embodiments, the payment device 900 may further include:

[0184] The fifth receiving module is used to receive a second input from the user based on the payment interface after the order information is displayed on the payment interface;

[0185] The second sending module is used to respond to the second input, obtain the payment information confirmed by the user, send the payment information to the payment server through the payment client so that the payment server records the payment information, and upon receiving the second payment request, query and obtain the payment information based on the target payment identifier and the target order identifier, process the payment for the target order based on the payment information, and obtain the payment result.

[0186] In some embodiments, the payment device 900 may further include:

[0187] The result polling module is used to poll the clearing institution server for the payment result corresponding to the target order after sending the first payment request for the target order to the clearing institution server through the payment client;

[0188] The second display module is used to, upon obtaining the payment result through polling, redirect from the payment interface to the payment result interface in the merchant client and display the payment result in the payment result interface.

[0189] In some embodiments, the payment device 900 may further include:

[0190] The third sending module is used to send order information corresponding to the target order to the clearing institution server before the merchant client sends the target order identifier corresponding to the target order to the payment client. This is done when the user selects a target payment method for the target order in the merchant client. The clearing institution server then generates the target order identifier corresponding to the target order based on the order information. The target payment method is the payment method corresponding to the target payment platform, which is a platform capable of providing the payment method corresponding to the target payment institution.

[0191] The sixth receiving module is used to receive the target order identifier returned by the clearing institution server.

[0192] Therefore, when a user triggers a payment for a target order, the merchant client sends a target order identifier corresponding to that target order to the payment client. The payment client then sends a first payment request for the target order to the clearing institution's server. This first payment request includes the user's unique identifier within the target payment institution, i.e., the target payment identifier, as well as the target order identifier. This prompts the clearing institution's server to initiate a second payment request to the payment server corresponding to the target payment institution. This allows the target payment institution to obtain sensitive transaction information in the background based on the target payment identifier and the target order identifier, thereby processing the payment for the target order. In this way, since the merchant client and payment client on the terminal device only transmit the target order identifier corresponding to the target order through a front-end mechanism, without transmitting other sensitive transaction information, the risk of malicious interception of sensitive transaction information can be reduced, improving the security of information transmission during the payment process.

[0193] Figure 10 This is a schematic diagram of a payment device provided in one embodiment of this application. The payment device can be configured on a clearing institution server.

[0194] like Figure 10 As shown, the payment device 1000 may include:

[0195] The second receiving module 1001 is used to receive a first payment request for a target order sent by a payment client corresponding to the target payment institution. The first payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identity identifier of the user in the target payment institution.

[0196] 1002 is used to respond to the first payment request by sending a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and to obtain a payment result.

[0197] The payment device 1000 described above will be explained in detail below:

[0198] In some embodiments, the payment device 1000 may further include:

[0199] The seventh receiving module is used to receive order information corresponding to the target order sent by the merchant client before receiving the first payment request for the target order sent by the payment client corresponding to the target payment institution;

[0200] The identifier generation module is used to generate a target order identifier corresponding to the target order based on the order information;

[0201] The identifier return module is used to return the target order identifier to the merchant client.

[0202] In some embodiments, the payment device 1000 may further include:

[0203] The first storage module is used to associate and store the target order identifier with the order information after generating the target order identifier corresponding to the target order based on the order information.

[0204] In some embodiments, the payment device 1000 may further include:

[0205] The fourth request module is used to receive a second query request for the target order sent by the payment server before receiving a first payment request for the target order sent by the payment client corresponding to the target payment institution after associating and storing the target order identifier with the order information. The second query request includes the target order identifier.

[0206] The information query module is used to respond to the second query request by querying and obtaining the order information corresponding to the target order based on the target order identifier;

[0207] The information return module is used to return the order information to the payment server.

[0208] Therefore, by using tokenization technology to mark sensitive information such as user identity information and order information, user identity information is marked with a target payment identifier and order information is marked with a target order identifier. During the payment process, the target payment identifier and target order identifier are used to replace the sensitive transaction information for transmission. In this way, the risk of sensitive transaction information being maliciously intercepted can be further reduced, and the security of information transmission during the payment process can be improved.

[0209] Figure 11 This is a schematic diagram of a payment device provided in one embodiment of this application. The payment device can be configured on a payment server.

[0210] like Figure 11 As shown, the payment device 1100 may include:

[0211] The third receiving module 1101 is used to receive a second payment request for a target order sent by the clearing institution server. The second payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identity identifier of the user in the target payment institution. The target payment institution is a payment institution corresponding to the payment server.

[0212] The payment processing module 1102 is used to respond to the second payment request by performing payment processing on the target order according to the target payment identifier and the target order identifier, and obtaining a payment result.

[0213] The payment device 1100 described above will be explained in detail below:

[0214] In some embodiments, the payment device 1100 may further include:

[0215] The eighth receiving module is used to receive, before receiving the second payment request for the target order sent by the clearing institution server, a first query request for the target order sent by the payment client corresponding to the target payment institution, wherein the first query request includes the target order identifier;

[0216] The fifth request module is used to respond to the first query request by sending a second query request for the target order to the clearing institution server. The second query request is used to instruct the clearing institution server to query and obtain the order information corresponding to the target order based on the target order identifier.

[0217] The information forwarding module is used to receive the order information returned by the clearing institution's server and forward the order information to the payment client.

[0218] In some embodiments, the payment device 1100 may further include:

[0219] The second storage module is used to receive and save the payment information sent by the payment client after the order information is forwarded to the payment client;

[0220] The aforementioned payment processing module 1102 may specifically include:

[0221] The query submodule is used to query and obtain the payment information based on the target payment identifier and the target order identifier;

[0222] The payment submodule is used to process the payment for the target order based on the payment information and obtain the payment result.

[0223] Therefore, by using tokenization technology to mark sensitive information such as user identity information and order information, user identity information is marked with a target payment identifier and order information is marked with a target order identifier. During the payment process, the target payment identifier and target order identifier are used to replace the sensitive transaction information for transmission. In this way, the risk of sensitive transaction information being maliciously intercepted can be further reduced, and the security of information transmission during the payment process can be improved.

[0224] Figure 12 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application.

[0225] The electronic device 1200 may include a processor 1201 and a memory 1202 storing computer program instructions.

[0226] Specifically, the processor 1201 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0227] Memory 1202 may include mass storage for data or instructions. For example, and not limitingly, memory 1202 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 1202 may include removable or non-removable (or fixed) media. Where appropriate, memory 1202 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 1202 is non-volatile solid-state memory.

[0228] In certain embodiments, the memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Thus, typically, 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), it is operable to perform the operations described with reference to the method according to one aspect of this application.

[0229] The processor 1201 implements any of the payment methods described in the above embodiments by reading and executing computer program instructions stored in the memory 1202.

[0230] In some examples, the electronic device 1200 may also include a communication interface 1203 and a bus 1210. For example, Figure 12 As shown, the processor 1201, memory 1202, and communication interface 1203 are connected through bus 1210 and complete communication with each other.

[0231] The communication interface 1203 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0232] Bus 1210 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not as a limitation, bus 1210 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth 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-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 1210 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0233] For example, the electronic device 1200 can be a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.

[0234] The electronic device 1200 can execute the payment method in the embodiments of this application, thereby achieving a combination Figures 1 to 11 The payment methods and devices described.

[0235] Furthermore, in conjunction with the payment methods in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the payment methods in the above embodiments. Examples of computer-readable storage media include non-transitory computer-readable storage media, such as portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, etc.

[0236] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0237] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0238] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0239] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0240] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A payment method applied to a terminal device, wherein the terminal device is equipped with a merchant client and a payment client corresponding to a target payment institution, characterized in that, The method includes: Receive the first input from the user in the merchant client that triggers the payment target order; In response to the first input, the merchant client sends a target order identifier corresponding to the target order to the payment client. The target order identifier is generated by the clearing server based on the order information corresponding to the target order sent by the merchant client to the clearing server, and is returned to the merchant client. The payment client sends a first payment request for the target order to the clearing institution's server. The first payment request includes a target payment identifier and a target order identifier. The target payment identifier is the user's unique identity identifier in the target payment institution. Wherein, the first payment request is used to instruct the clearing institution server to send a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier, and the second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and obtain a payment result; Before sending the first payment request for the target order to the clearing institution server via the payment client, the method further includes: Receive a second input from the user based on the payment interface in the payment client; In response to the second input, the payment information confirmed by the user is obtained, and the payment information is sent to the payment server through the payment client so that the payment server records the payment information. Upon receiving the second payment request, the payment information is queried and obtained according to the target payment identifier and the target order identifier, and the payment is processed for the target order according to the payment information to obtain the payment result.

2. The method according to claim 1, characterized in that, The merchant client includes a payment control. After receiving the user's first input in the merchant client to trigger a payment target order, the method further includes: The payment control is invoked by the merchant client; The payment control invokes the payment client and displays the payment interface within the payment client.

3. The method according to claim 2, characterized in that, After the merchant client sends the target order identifier corresponding to the target order to the payment client, and before receiving the user's second input based on the payment interface in the payment client, the method further includes: The payment client sends a first query request for the target order to the payment server. The first query request includes the target order identifier and is used to instruct the payment server to obtain the order information corresponding to the target order from the clearing institution server based on the target order identifier. Receive the order information corresponding to the target order returned by the payment server; The order information is displayed on the payment interface.

4. The method according to claim 2, characterized in that, After sending a first payment request for the target order to the clearing institution server via the payment client, the method further includes: The system polls the clearing institution's server for the payment results corresponding to the target order. If the payment result is obtained through polling, the user is redirected from the payment interface to the payment result interface in the merchant client, where the payment result is displayed.

5. The method according to claim 1, characterized in that, Before the merchant client sends the target order identifier corresponding to the target order to the payment client, the method further includes: When the user selects a target payment method for the target order in the merchant client, the merchant client sends order information corresponding to the target order to the clearing institution server, so that the clearing institution server generates a target order identifier corresponding to the target order based on the order information. The target payment method is the payment method corresponding to the target payment platform, and the target payment platform is a platform that can provide the payment method corresponding to the target payment institution. Receive the target order identifier returned by the clearing institution's server.

6. A payment method applied to a clearing institution's server, characterized in that, The method includes: The system receives a first payment request for a target order sent by a payment client corresponding to the target payment institution. The first payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identifier of the user in the target payment institution. The target order identifier is generated by the clearing institution server based on the order information corresponding to the target order sent by the merchant client to the clearing institution server and returned to the merchant client. The target order identifier is sent by the merchant client to the payment client in response to the user's first input that triggers payment for the target order in the merchant client. In response to the first payment request, a second payment request is sent to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and to obtain a payment result. The payment server receives and records the payment information sent by the payment client, and upon receiving the second payment request, queries and obtains the payment information based on the target payment identifier and the target order identifier, processes the payment for the target order based on the payment information, and obtains the payment result. The payment information is obtained by the payment client in response to the user's second input based on the payment interface in the payment client.

7. The method according to claim 6, characterized in that, Before receiving the first payment request for the target order sent by the payment client corresponding to the target payment institution, the method further includes: Receive order information sent by the merchant client that corresponds to the target order; Generate a target order identifier corresponding to the target order based on the order information; Return the target order identifier to the merchant client.

8. The method according to claim 7, characterized in that, After generating the target order identifier corresponding to the target order based on the order information, the method further includes: The target order identifier is associated with and stored with the order information.

9. The method according to claim 8, characterized in that, After associating and storing the target order identifier with the order information, and before the payment client receives the user's second input based on the payment interface in the payment client, the method further includes: Receive a second query request for the target order sent by the payment server, wherein the second query request includes the target order identifier; In response to the second query request, the order information corresponding to the target order is queried and obtained based on the target order identifier; The order information is returned to the payment server.

10. A payment method applied to a payment server, characterized in that, The method includes: The system receives a second payment request for a target order from a clearing institution server. The second payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identifier for the user within a target payment institution, which is the payment institution corresponding to the payment server. The second payment request is sent by the clearing institution server in response to a first payment request for the target order sent by a payment client corresponding to the target payment institution, based on the target payment identifier and the target order identifier. The first payment request includes the target payment identifier and the target order identifier. The target order identifier is generated by the clearing institution server based on order information corresponding to the target order sent by the merchant client to the clearing institution server and returned to the merchant client. The target order identifier is sent by the merchant client to the payment client in response to the user's first input triggering payment for the target order on the merchant client. In response to the second payment request, the target order is processed for payment based on the target payment identifier and the target order identifier to obtain a payment result; The method further includes: Receive and save payment information sent by the payment client, the payment information being obtained by the payment client in response to a second input from the user based on the payment interface in the payment client; The step of processing the payment for the target order based on the target payment identifier and the target order identifier to obtain the payment result includes: The payment information is retrieved based on the target payment identifier and the target order identifier; The target order is processed for payment based on the payment information to obtain the payment result.

11. The method according to claim 10, characterized in that, Before receiving the second payment request for the target order from the clearinghouse server, the method further includes: Receive a first query request for the target order sent by a payment client corresponding to the target payment institution, wherein the first query request includes the target order identifier; In response to the first query request, a second query request for the target order is sent to the clearing institution server. The second query request is used to instruct the clearing institution server to query and obtain the order information corresponding to the target order based on the target order identifier. The system receives the order information returned by the clearing institution's server and forwards the order information to the payment client.

12. A payment device, configured in a terminal device, wherein the terminal device includes a merchant client and a payment client corresponding to a target payment institution, characterized in that, The device includes: The first receiving module is used to receive the first input from the user in the merchant client that triggers the payment target order; The first sending module is configured to respond to the first input by sending a target order identifier corresponding to the target order from the merchant client to the payment client. The target order identifier is generated by the clearing server based on the order information corresponding to the target order sent from the merchant client to the clearing server and returned to the merchant client. The first request module is used to send a first payment request for the target order to the clearing institution server through the payment client. The first payment request includes a target payment identifier and the target order identifier. The target payment identifier is the user's unique identity identifier in the target payment institution. Wherein, the first payment request is used to instruct the clearing institution server to send a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier, and the second payment request is used to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, and obtain a payment result; The fifth receiving module is used to receive a second input from the user based on the payment interface in the payment client before the first payment request for the target order is sent to the clearing institution server through the payment client; The second sending module is configured to, in response to the second input, obtain the payment information confirmed by the user before sending the first payment request for the target order to the clearing institution server through the payment client, send the payment information to the payment server through the payment client so that the payment server records the payment information, and upon receiving the second payment request, query and obtain the payment information based on the target payment identifier and the target order identifier, process the payment for the target order based on the payment information, and obtain the payment result.

13. A payment device configured on a clearing institution's server, characterized in that, The device includes: The second receiving module is used to receive a first payment request for a target order sent by a payment client corresponding to the target payment institution. The first payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identifier of the user in the target payment institution. The target order identifier is generated by the clearing institution server based on the order information corresponding to the target order sent by the merchant client to the clearing institution server and returned to the merchant client. The target order identifier is sent by the merchant client to the payment client in response to the user's first input that triggers payment for the target order in the merchant client. The second request module is configured to respond to the first payment request by sending a second payment request to the payment server corresponding to the target payment institution based on the target payment identifier and the target order identifier. The second payment request is configured to instruct the payment server to process the payment for the target order based on the target payment identifier and the target order identifier, thereby obtaining a payment result. The payment server receives and records the payment information sent by the payment client, and upon receiving the second payment request, queries and obtains the payment information based on the target payment identifier and the target order identifier, processes the payment for the target order based on the payment information, and obtains the payment result. The payment information is obtained by the payment client in response to the user's second input based on the payment interface in the payment client.

14. A payment device configured on a payment server, characterized in that, The device includes: The third receiving module is used to receive a second payment request for a target order sent by a clearing institution server. The second payment request includes a target payment identifier and a target order identifier corresponding to the target order. The target payment identifier is a unique identifier of the user in the target payment institution. The target payment institution is the payment institution corresponding to the payment server. The second payment request is sent by the clearing institution server in response to a first payment request for the target order sent by a payment client corresponding to the target payment institution, based on the target payment identifier and the target order identifier. The first payment request includes the target payment identifier and the target order identifier. The target order identifier is generated by the clearing institution server based on the order information corresponding to the target order sent by the merchant client to the clearing institution server and returned to the merchant client. The target order identifier is sent by the merchant client to the payment client in response to the user's first input triggering payment for the target order on the merchant client. The payment processing module is configured to respond to the second payment request by performing payment processing on the target order based on the target payment identifier and the target order identifier, and obtaining a payment result; The second storage module is used to receive and save payment information sent by the payment client, which is obtained by the payment client in response to a second input by the user based on the payment interface in the payment client; The payment processing module includes: The query submodule is used to query and obtain the payment information based on the target payment identifier and the target order identifier; The payment submodule is used to process the payment for the target order based on the payment information and obtain the payment result.

15. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the steps of the payment method as described in any one of claims 1-5, 6-9, or 10-11.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the steps of the payment method as described in any one of claims 1-5, 6-9, or 10-11.

17. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device causes the electronic device to perform the steps of the payment method as described in any one of claims 1-5, 6-9, or 10-11.

Images