CN116151816A - Payment method, device, equipment, medium and product - Google Patents

Abstract

The application discloses a payment method, a payment device, a payment equipment, a payment medium and a payment product. The payment method includes receiving a first input from a user triggering a payment target order in a merchant client; responsive to the first input, sending, by the merchant client to the payment client, a target order identification corresponding to the target order; sending a first payment request aiming at a target order to a clearing mechanism server through a payment client, wherein the first payment request comprises a target payment identifier and a target order identifier, and the target payment identifier is a unique identity identifier of a user in a target payment mechanism; the first payment request is used for indicating the clearing institution server to send a second payment request to a payment server corresponding to the target payment institution, so that the payment server carries out 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 that transaction sensitive information is intercepted maliciously can be reduced, and the information transmission safety in the payment process is improved.

Description

Payment method, device, equipment, medium and product

technical field

This application belongs to the technical field of payment, and in particular relates to a payment method, device, equipment, medium and product.

Background technique

When the user uses the merchant client installed in the terminal device to make online shopping and pay for the order, it is usually necessary to select the payment method used to pay the current order from multiple optional payment methods, so as to pay the customer through the corresponding payment method The terminal completes the order payment.

In the process of jumping from the merchant client to the payment client for payment, the merchant client in the terminal device needs to pass transaction sensitive information such as the merchant name, payment amount, and the payment account selected by the user to the payment client in the way of front-end transmission. client to process payment for the order.

In this way, in the prior art, transaction-sensitive information is transmitted between different clients through the front-end method, there is a risk of information being maliciously intercepted, which reduces the security of information transmission during the payment process.

Contents of the invention

Embodiments of the present application provide a payment method, device, device, medium, and product, which can reduce the risk of malicious interception of transaction sensitive information and improve the security of information transmission during the payment process.

In the first aspect, an embodiment of the present application provides a payment method, which is applied to a terminal device, and the terminal device is provided with a merchant client and a payment client corresponding to a target payment institution. The method includes:

receiving the user's first input of triggering a payment target order in the merchant client;

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

The first payment request for the target order is sent to the clearing institution server through the payment client, the first payment request includes the target payment ID and the target order ID, and the target payment ID is the user’s The unique 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 according to the target payment identifier and the target order identifier, and the second payment The request is used to instruct the payment server to perform payment processing on the target order according to the target payment ID and the target order ID to obtain a payment result.

In the second aspect, the embodiment of the present application provides a payment method, which is applied to the clearing institution server, and the method includes:

Receive the first payment request for the target order sent by the payment client corresponding to the target payment institution, the first payment request includes the target payment identifier and the target order identifier corresponding to the target order, and the target payment identifier is The unique identity of the user in the target payment institution;

In response to the first payment request, sending a second payment request to a payment server corresponding to the target payment institution according to the target payment ID and the target order ID, the second payment request is used to indicate the payment The server performs payment processing on the target order according to the target payment identifier and the target order identifier, and obtains a payment result.

In a third aspect, the embodiment of the present application provides a payment method, which is applied to a payment server, and the method includes:

Receive the second payment request for the target order sent by the clearing institution server, the second payment request includes the target payment ID and the target order ID corresponding to the target order, and the target payment ID is the target payment ID of the user in the target payment institution The unique identity of the target payment institution is the payment institution corresponding to the payment server;

In response to the second payment request, perform payment processing on the target order according to the target payment identifier and the target order identifier, and obtain a payment result.

In a fourth aspect, the embodiment of the present application provides a payment device, which is configured in a terminal device, and the terminal device is provided with a merchant client and a payment client corresponding to a target payment institution, and the device includes:

The first receiving module is used to receive the first input of the user triggering the payment target order in the merchant client;

A first sending module, configured to send, by the merchant client to the payment client, a target order identifier corresponding to the target order in response to the first input;

The first request module is configured to send a first payment request for the target order to the clearing institution server through the payment client, where the first payment request includes the target payment identifier and the target order identifier, and the target The payment ID is the unique identity of the user 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 according to the target payment identifier and the target order identifier, and the second payment The request is used to instruct the payment server to perform payment processing on the target order according to the target payment ID and the target order ID to obtain a payment result.

In the fifth aspect, the embodiment of the present application provides a payment device configured on a clearing institution server, and the device includes:

The second receiving module is configured to receive the first payment request for the target order sent by the payment client corresponding to the target payment institution, and the first payment request includes the target payment identifier and the target order identifier corresponding to the target order , the target payment identifier is the unique identity of the user in the target payment institution;

The second request module is configured to, in response to the first payment request, send a second payment request to the payment server corresponding to the target payment institution according to the target payment identifier and the target order identifier, and the second payment request The request is used to instruct the payment server to perform payment processing on the target order according to the target payment ID and the target order ID to obtain a payment result.

In a sixth aspect, the embodiment of the present application provides a payment device configured on a payment server, and the device includes:

The third receiving module is configured to receive the second payment request for the target order sent by the clearing institution server, the second payment request includes the target payment identifier and the target order identifier corresponding to the target order, and the target payment identifier is the unique identity of the user in the target payment institution, and the target payment institution is the payment institution corresponding to the payment server;

The payment processing module is configured to, in response to the second payment request, perform payment processing on the target order according to the target payment identifier and the target order identifier, and obtain a payment result.

In a seventh aspect, the embodiment of the present application provides an electronic device, which includes: a processor and a memory storing computer program instructions;

When the processor executes the computer program instructions, the steps of the payment method described in any one embodiment of the first aspect, the second aspect or the third aspect are implemented.

In an eighth aspect, the embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the first aspect, the second aspect or the third aspect can be realized. The steps of the payment method described in any embodiment of the aspect.

In the ninth aspect, the embodiment of the present application provides a computer program product. When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device executes the method according to the first aspect, the second aspect or the third aspect. The steps of the payment method described in any one of the embodiments.

In the payment method, device, device, medium, and product in the embodiments of the present application, when the user triggers the payment target order, the merchant client sends the target order identifier corresponding to the target order to the payment client, and then the payment client Send the first payment request for the target order to the clearing institution server, and the first payment request includes the unique identity of the user's target payment institution, that is, the target payment identifier, and the target order identifier, so that the clearing institution server can further send The payment server corresponding to the target payment institution initiates a second payment request, so that the target payment institution can obtain transaction-sensitive information in the background based on the target payment ID and the target order ID, so as to perform payment processing on the target order. In this way, because only the target order identifier corresponding to the target order is transmitted between the merchant client and the payment client in the terminal device through the front-end method, and other transaction sensitive information is not transmitted, therefore, the risk of transaction sensitive information being maliciously intercepted can be reduced. Improve the security of information transmission in the payment process.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the accompanying drawings that need to be used in the embodiments of the present application. Additional figures can be derived from these figures.

Fig. 1 is a schematic flow diagram of the payment method based on the payment system provided by this application;

Fig. 2 is a schematic flow diagram of the payment method provided by the embodiment of the first aspect of the application;

Fig. 3 is a schematic diagram of the payment interaction interface provided by this application;

Fig. 4 is a schematic diagram of the payment interface in the payment client provided by the present application;

Fig. 5 is a schematic diagram of the payment result interface in the merchant client provided by this application;

Fig. 6 is a schematic flowchart of the payment method provided by the embodiment of the second aspect of the present application;

Fig. 7 is a schematic flowchart of the payment method provided by the embodiment of the third aspect of the present application;

Fig. 8 is a schematic flow chart of an exemplary payment method provided by this application;

Fig. 9 is a schematic structural diagram of the payment device provided by the embodiment of the first aspect of the present application;

Fig. 10 is a schematic structural diagram of the payment device provided by the embodiment of the second aspect of the application;

Fig. 11 is a schematic structural diagram of the payment device provided by the embodiment of the third aspect of the present application;

Fig. 12 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

The characteristics and exemplary embodiments of various aspects of the application will be described in detail below. In order to make the purpose, technical solution and advantages of the application clearer, the application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described here are only intended to explain the present application rather than limit the present application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is a relationship between these entities or operations. There is no such actual relationship or order between them. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the statement "comprising..." does not exclude the presence of additional same elements in the process, method, article or device comprising said element.

In order to solve the problems of the prior art, the embodiment of the present application provides a payment method, device, equipment, medium and product. This payment method can be applied to the scene of online payment. The payment method provided by the embodiment of the present application is firstly introduced in combination with the payment system architecture.

Fig. 1 is a schematic flowchart of the payment method based on the payment system provided by this application. The payment method can be applied to a payment system, and the payment system can include a terminal device, a clearing institution server, and a payment server. Wherein, a merchant client and a payment client may be installed in the terminal device. In addition, the payment server and payment client may be provided by the target payment institution.

Based on the architecture of the above payment system, as shown in Figure 1, the payment method provided by the embodiment of the present application may include: the terminal device receives the first input of the user triggering the payment target order in the merchant client; the terminal device responds to the first input, The merchant client sends the target order identifier corresponding to the target order to the payment client; the terminal device sends the first payment request for the target order to the clearing institution server through the payment client; the clearing institution server responds to the first payment request, according to the target order The payment ID and the target order ID send a second payment request to the payment server corresponding to the target payment institution; in response to the second payment request, the payment server performs payment processing on the target order according to the target payment ID and the target order ID, and obtains the payment result. Wherein, both the first payment request and the second payment request include a target payment ID and a target order ID, and the target payment ID is the user's unique identity in the target payment institution.

The payment methods implemented by each end are described in detail below.

Fig. 2 is a schematic flowchart of a payment method provided by an embodiment of the present application. The payment method can be applied to a terminal device, and the terminal device is provided with a merchant client and a payment client corresponding to a target payment institution.

As shown in Figure 2, the payment method may specifically include the following steps:

S210. Receive the user's first input of triggering the payment target order in the merchant client;

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

S230. Send the first payment request for the target order to the clearing institution server through the payment client. The first payment request includes the target payment ID and the target order ID, and the target payment ID is the unique identity of the user in the target payment institution.

In this embodiment of the application, the first payment request is used to instruct the clearing institution server to send the second payment request to the payment server corresponding to the target payment institution according to the target payment ID and the target order ID, and the second payment request is used to instruct the payment server to send the second payment request according to the target The payment identifier and the target order identifier perform payment processing on the target order to obtain a payment result.

Thus, when the user triggers the payment target order, the merchant client sends the target order identifier corresponding to the target order to the payment client, and then sends the first payment request for the target order to the clearing institution server through the payment client, And the first payment request includes the unique identity of the user's target payment institution, that is, the target payment identifier, and the target order identifier, so that the clearing institution server can further initiate a second payment request to the payment server corresponding to the target payment institution, so that The target payment institution can obtain transaction sensitive information in the background based on the target payment ID and the target order ID, so as to process the payment of the target order. In this way, because only the target order identifier corresponding to the target order is transmitted between the merchant client and the payment client in the terminal device through the front-end method, and other transaction sensitive information is not transmitted, therefore, the risk of transaction sensitive information being maliciously intercepted can be reduced. Improve the security of information transmission in the payment process.

The specific implementation of each of the above steps is introduced below.

In some implementations, in S210, the first input may be an input in which the user clicks a payment button for the target order in the merchant client.

Exemplarily, after the user purchases commodities and places an order in the merchant client, the user may click a payment button on the order details page of the order, thereby triggering the payment process for the order.

In some implementations, in S220, after the merchant client receives the user's first input to trigger the payment target order, it may send the target order identifier corresponding to the target order to the payment client. Wherein, the target order identifier may be a unique identifier assigned to the target order by the clearing institution, for example, it may be a TN (Transaction Number, order identifier) number of the target order.

Different from the merchant client in the prior art that directly sends the order information to the payment client through the front-end method, in the embodiment of this application, the merchant client sends the target order ID to the payment client, and the payment client then uses the target order ID in the payment client. Obtain order information between different back-end servers and process order payment. Since the target order ID is not sensitive information, even if it is maliciously intercepted by the front-end in time, the sensitive information of the transaction cannot be obtained, which can improve the security of information transmission during the payment process.

In some examples, before the above S220, the payment method provided in this embodiment of the application may further include:

When the user selects the target payment method for the 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 the target order corresponding to the target order according to the order information. Order identification, where 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 ID returned by the clearing institution server.

Here, the order information includes but not limited to merchant name, payment amount, order number and other information. The target payment method may be the payment method corresponding to the target payment platform, the target payment platform may be the payment platform corresponding to the clearing institution server, and the target payment platform can provide the payment method corresponding to the target payment institution.

Exemplarily, as shown in Figure 3, multiple optional primary payment methods can be provided in the merchant client, and multiple optional primary payment methods can be displayed in the merchant client after the user triggers the payment target order . If the payment method provided by the target payment platform is A payment method 31, when the user selects A payment method 31, the payment control of the target payment platform set in the merchant client can be invoked, and the payment control will arouse and display the payment method corresponding to the target payment platform. The online payment cash register interface 30 can display multiple secondary payment methods including a payment method 32 in the online payment cash register interface 30, so that the user can further choose which payment method to use provided by the payment institution. 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 acquirer through the background server, and the acquirer can send the order information corresponding to the target order to the acquirer. to the clearing institution server. Wherein, the order information includes but not limited to merchant name, payment amount, order number and other information. After receiving the order information, the clearing institution server can return the TN number corresponding to the target order to the merchant through the acquiring institution, and store the order information and the TN number in association.

In some implementations, in S230, after the payment client receives the target order ID sent by the merchant client, it can obtain the unique identity of the user in the target payment institution, that is, the target payment ID, and send it together to the clearing institution server. Wherein, the target payment identifier may be, for example, the user's payment client Token.

In order to protect the user's right to know and right to choose, the target payment identification involved in the above process requires the user to apply for opening the relevant business through the payment institution before assigning the corresponding payment client Token to the user.

Exemplarily, after receiving the first payment request carrying the target order identifier and the target payment identifier, the clearing institution server can obtain the corresponding order information according to the target order identifier, and send the order information together with the target payment identifier to the payment request. The server, where the payment server performs user identity verification, querying the user's payment account, etc. according to the target payment ID, and debits the user's payment account according to the order information to pay for the target order.

In other examples, after the clearing institution server receives the first payment request carrying the target order identifier and the target payment identifier, the clearing institution server can also verify the identity of the user and check the order information. Directly send the second payment request carrying the target order ID and the target payment ID to the payment server, and the payment server restores the payment information selected by the user when performing the payment operation on the payment client based on the sent information, and determines the target based on the payment information The order information of the order and the user's payment account are debited from the user's payment account to pay for the target order.

In addition, in some embodiments, a payment control may be set in the merchant client, and the payment control may be a payment control provided by a clearing institution. Based on this, after the above S210, the payment method provided in the embodiment of the present application may further include:

Call the payment control by the merchant client;

Evoke the payment client through the payment control, and display the payment interface in the payment client.

Exemplarily, as shown in FIG. 3 , when the user selects a payment method 32 in the online payment cash register interface 30, the payment client corresponding to a 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 awakened, as shown in FIG. 4 , the payment interface of the payment client can be displayed on the terminal device.

In this way, by uniformly invoking the third-party payment client through the payment control installed in the merchant client, it is possible to shield the merchant client from the differences in the payment client activation methods of different payment institutions, and reduce the development difficulty of the merchant client.

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

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 the first query request is used to instruct the payment server to obtain the target order corresponding to the target order from the clearing institution server according to the target order identifier. order information;

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

Display order information in the payment interface.

Exemplarily, after the payment client receives the target order identifier sent by the merchant client, the payment client can acquire the order information about the target order through the background query of the payment institution. Specifically, the payment client may send a first query request carrying the target order identifier to the payment server, and after receiving the first query request, the payment server may send a query request carrying the target order identifier to the clearing institution server in the background. The second query request is to query and obtain the order information corresponding to the target order from the clearing institution server. After the payment server receives the order information returned by the clearing institution server, it can forward the order information to the payment client. In this way, when the payment client displays the payment interface, the order information of the target order can be displayed on the payment interface.

In this way, compared with the prior art in which the order information is directly delivered while jumping through the foreground client, the embodiment of the present application can effectively reduce the risk of transaction sensitive information being intercepted and leaked during the jumping process between clients.

In addition, in some implementations, after the above step of displaying the order information on the payment interface, the payment method provided in the embodiment of the present application may further include:

receiving a second input from the user based on the payment interface;

In response to the second input, obtain the payment information that the user confirms the input, send the payment information to the payment server through the payment client, so that the payment server records the payment information, and when receiving the second payment request, according to the target payment identifier and The target order ID is queried and the payment information is obtained, and the target order is paid according to the payment information, and the payment result is obtained.

Here, the 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, and may also include the user's input of identity verification information. Input by the user confirming willingness to pay may be included.

Exemplarily, after the user selects the payment account for paying the target order on the payment client, enters and completes a series of operations such as identity verification information, and clicks the confirmation button, the payment client can upload the payment information such as the payment account that the user confirms to the input. Send to the payment server in the background for registration. After receiving the payment information sent by the payment client, the payment server can associate and store the payment information with the user's target payment ID and the target order ID of the target order, so that when receiving the second payment request sent by the clearing institution server , restore the payment information selected by the user according to the target payment identifier and the target order identifier, and pay the target order based on the payment information.

In addition, in some implementations, after the above S230, the payment method provided in the embodiment of the present application may further include:

Inquire the clearing institution server for the payment result corresponding to the target order;

When the payment result is obtained by polling, the payment interface jumps back to the payment result interface in the merchant client, and the payment result is displayed on the payment result interface.

Here, after the payment client sends the first payment request to the clearing institution server, it may poll the clearing institution server for the payment result. After the payment client polls the payment result, it can trigger the front-end bounce.

Exemplarily, after the payment client polls the payment result, it can notify the payment control installed in the merchant client to perform a rebound, and the payment control can control the rebound to the merchant client The payment result interface in , as shown in FIG. 5 , displays the payment result on the payment result interface, such as payment success or payment failure.

In addition, the clearing institution server can also return the payment result to the merchant's background server through the acquiring institution.

In this way, by returning the payment result and jumping back, automatic switching of the payment result interface and automatic switching between different clients can be realized, thereby simplifying the user operation process.

Fig. 6 is a schematic flowchart of a payment method provided by an embodiment of the present application. This payment method can be applied to the clearing house server.

As shown in Figure 6, the payment method may specifically include the following steps:

S610. Receive the first payment request for the target order sent by the payment client corresponding to the target payment institution. The first payment request includes the target payment identifier and the target order identifier corresponding to the target order. unique identifier within the institution;

S620. In response to the first payment request, send a second payment request to the payment server corresponding to the target payment institution according to the target payment ID and the target order ID, and the second payment request is used to instruct the payment server to make payment according to the target payment ID and the target order ID. The target order is processed for payment, and the payment result is obtained.

Here, the above-mentioned second payment request may include a target payment identifier and a target order identifier. For specific explanations of the target payment identifier and the target order identifier, reference may be made to relevant parts in the foregoing embodiments, and details are not repeated here.

Exemplarily, after receiving the first payment request, the clearing institution server can perform operations such as user identity verification and order information check on the payment client that sent the request, and after the verification and verification is passed, send the payment client to the payment client that belongs to the same payment client. The payment server of the payment institution sends the second payment request carrying the target payment identifier and the target order identifier, so that the payment client can use the target payment identifier and the target order identifier to complete the payment process for the target order.

Therefore, by using tokenization technology to mark sensitive information such as user identity information and order information, the user identity information is marked with the target payment ID, the order information is marked with the target order ID, and the target payment ID and the target order ID are used during the payment process. In this way, the risk of malicious interception of transaction sensitive information can be further reduced, and the security of information transmission during the payment process can be improved.

Based on this, before the above S610, the payment method provided in this embodiment of the application may further include:

Receive the order information corresponding to the target order sent by the merchant client;

Generate a target order identifier corresponding to the target order according to the order information;

Return the target order ID to the merchant client.

Here, for explanations about the above steps, reference may be made to relevant parts in the foregoing embodiments, and details are not repeated here.

Based on this, after the above step of generating the target order identifier corresponding to the target order according to the order information, the payment method provided in the embodiment of the present application may further include:

Associate and store the target order ID with the order information.

In addition, after the above-mentioned associative storage of the target order identifier and the order information, and before the above-mentioned S610, the payment method provided by the embodiment of the present application may further include:

receiving a second query request sent by the payment server for the target order, where the second query request includes the target order identifier;

In response to the second query request, query and obtain order information corresponding to the target order according to the target order identifier;

Return order information to the payment server.

Here, for explanations about the above steps, reference may be made to relevant parts in the foregoing embodiments, and details are not repeated here.

Fig. 7 is a schematic flowchart of a payment method provided by an embodiment of the present application. The payment method can be applied to a payment server, and the payment server can be a server corresponding to the aforementioned payment client.

As shown in Figure 7, the payment method may specifically include the following steps:

S710. Receive the second payment request for the target order sent by the server of the clearing institution. The second payment request includes the target payment identifier and the target order identifier corresponding to the target order, and the target payment identifier is the unique identity of the user in the target payment institution. , the target payment institution is the payment institution corresponding to the payment server;

S720. In response to the second payment request, perform payment processing on the target order according to the target payment identifier and the target order identifier, and obtain a payment result.

Here, when the payment server receives the payment request sent by the clearing institution server, it can determine the payment account corresponding to the user and the order information of the target order to be paid by using the target payment ID and the target order ID carried in it, and then according to For the order information, the user's payment account is debited to complete the payment process for the target order. Wherein, the payment result may include payment success or payment failure.

Therefore, by using tokenization technology to mark sensitive information such as user identity information and order information, the user identity information is marked with the target payment ID, the order information is marked with the target order ID, and the target payment ID and the target order ID are used during the payment process. In this way, the risk of malicious interception of transaction sensitive information can be further reduced, and the security of information transmission during the payment process can be improved.

Based on this, before the above S710, the payment method provided in the embodiment of this application may also include:

receiving a first query request for the target order sent by a payment client corresponding to the target payment institution, where the first query request includes the target order identifier;

In response to the first query request, send a second query request for the target order to the clearing institution server, and the second query request is used to instruct the clearing institution server to query and obtain order information corresponding to the target order according to the target order identifier;

Receive the order information returned by the clearing institution server, and forward the order information to the payment client.

Here, for explanations about the above steps, reference may be made to relevant parts in the foregoing embodiments, and details are not repeated here.

In addition, after the aforementioned order information is forwarded to the payment client, the method further includes:

Receive and save the payment information sent by the payment client.

Based on this, the above S720 may specifically include:

Query and obtain payment information according to the target payment ID and target order ID;

Perform payment processing on the target order according to the payment information, and obtain the payment result.

Here, for explanations about the above steps, reference may be made to relevant parts in the foregoing embodiments, and details are not repeated here.

In order to better describe the whole solution, some specific examples are given based on the foregoing embodiments.

For example, the payment method flowchart shown in FIG. 8 . The payment method may include S801-S816, which will be described in detail below in conjunction with FIG. 8 .

S801. Initiate an order payment request.

In some examples, when the user selects the target payment method for the target order in the merchant client in the terminal device and triggers the payment of the target order, the merchant client can initiate an order payment request to the acquirer. The order information of the target order can be carried in the request.

S802. Initiate an order payment request.

In some examples, after receiving the order information of the target order, the acquirer may send an order payment request to the clearing institution server corresponding to the target payment method, and the order payment request may also carry the order information of the target order.

S803. Return the order acceptance result.

In some examples, the clearing institution server may return the TN number corresponding to the target order.

S804. Return the order acceptance result.

In some examples, the acquirer may return the TN number corresponding to the target order to the merchant client.

S805. Query the payment result.

In some examples, the merchant client may poll the acquirer for payment results.

S806. Arouse the payment client through the payment control, and send the TN number.

In some examples, after obtaining the TN number, the merchant client can call the embedded payment control, and invoke the corresponding payment client according to the payment method further selected by the user in the online cash register payment interface corresponding to the payment control, And send the TN number to the payment client.

S807. Query order information.

In some examples, the payment client may send a query request to the payment server after being awakened, to query the order information of the target order, and the query request may carry a TN number.

S808. Query order information.

In some examples, the payment server may further send a query request to the clearing institution server according to the TN number, so as to query and obtain corresponding order information according to the TN number.

S809. Return order information.

In some examples, the clearing institution server may return the queried order information to the payment server in a background manner.

S810. Return order information.

In some examples, the payment server can further return the queried order information to the payment client, so that the user can check the amount and confirm the willingness to pay according to the order information.

S811. Send payment information;

In some examples, after the user completes identity authentication and willingness to pay confirmation operations in the payment client, the payment client can send the payment information such as the payment account selected by the user to the payment server for recording in the payment server.

S812. Send a payment request and poll the payment result.

In some examples, the payment client can send the payment request carrying the user's payment Token and TN number to the clearing institution server.

S813. Send a payment request.

In some examples, the clearing institution server sends the received user payment Token and TN number to the payment server through the transfer system, and sends a payment request.

S814. Perform payment processing on the target order.

In some examples, the payment server restores the payment information selected by the user on the payment client according to the user's payment Token and TN number sent by the clearing institution server, and performs payment processing on the target order based on the payment information to obtain the payment result.

S815. Return the payment result.

In some examples, the payment server may return the payment result of the target order to the clearinghouse server.

S816. Return the payment result.

In some examples, the clearing institution server returns the payment result to the acquirer in the background, so that the merchant client can query the payment result from the acquirer, and the payment client can also query the payment result from the clearing institution server. The payment client can trigger the foreground bounce back according to the polled payment result, and the payment control in the merchant client will control the terminal device to jump back to the payment result interface in the merchant client after receiving the foreground bounce notification from the payment client.

It should be noted that the application scenarios described in the above-mentioned embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art know that, With the emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

Based on the same inventive concept, the present application also provides a payment device. It will be described in detail with reference to FIG. 9 to FIG. 11 .

Fig. 9 is a schematic structural diagram of a payment device provided by an embodiment of the present application. The payment device may be configured in a terminal device, and the terminal device is provided with a merchant client and a payment client corresponding to a target payment institution.

As shown in Figure 9, the payment device 900 may include:

The first receiving module 901 is configured to receive the first input of the user triggering the payment target order in the merchant client;

The first sending module 902 is configured to send, by the merchant client to the payment client, a target order identifier corresponding to the target order in response to the first input;

The first request module 903 is configured to send a first payment request for the target order to the clearing institution server through the payment client, where the first payment request includes the target payment identifier and the target order identifier, the The target payment ID is the unique identity of the user 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 according to the target payment identifier and the target order identifier, and the second payment The request is used to instruct the payment server to perform payment processing on the target order according to the target payment ID and the target order ID to obtain a payment result.

The above-mentioned payment device 900 will be described in detail below, specifically as follows:

In some of these embodiments, the merchant client is provided with a payment control;

The payment device 900 may also include:

A control calling module, configured to call the payment control by the merchant client after receiving the user's first input of triggering a payment target order in the merchant client;

The calling display module is used to wake up the payment client through the payment control, and display the payment interface in the payment client.

In some of these embodiments, the payment device 900 also includes:

The third request module is configured to send the target order identifier corresponding to the target order to the clearing institution server through the payment client after the merchant client sends the target order identifier to the payment client. Before the first payment request, 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 the first query request uses Instructing the payment server to obtain order information corresponding to the target order from the clearing institution server according to the target order identifier;

A fourth receiving module, configured to receive the order information corresponding to the target order returned by the payment server;

A first display module, configured to display the order information on the payment interface.

In some of these embodiments, the payment device 900 may also include:

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

The second sending module is configured to, in response to the second input, obtain the payment information that the user confirms input, and send the payment information to the payment server through the payment client, so that the payment server records the The payment information, and in the case of receiving the second payment request, query and obtain the payment information according to the target payment ID and the target order ID, and pay the target order according to the payment information Process and get the payment result.

In some of these embodiments, the payment device 900 may also include:

A result polling module, configured to poll the clearing institution server for a 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;

The second display module is configured to jump back from the payment interface to the payment result interface in the merchant client when the payment result is obtained by polling, and display the payment in the payment result interface result.

In some of these embodiments, the payment device 900 may also include:

The third sending module is configured to, before the merchant client sends the target order identifier corresponding to the target order to the payment client, before the user selects for the target order in the merchant client In the case of a target payment method, the merchant client sends the order information corresponding to the target order to the clearing institution server, so that the clearing institution server generates an order corresponding to the target order according to the order information The target order identifier, wherein 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;

The sixth receiving module is configured to receive the target order identifier returned by the clearing institution server.

Thus, when the user triggers the payment target order, the merchant client sends the target order identifier corresponding to the target order to the payment client, and then sends the first payment request for the target order to the clearing institution server through the payment client, And the first payment request includes the unique identity of the user's target payment institution, that is, the target payment identifier, and the target order identifier, so that the clearing institution server can further initiate a second payment request to the payment server corresponding to the target payment institution, so that The target payment institution can obtain transaction sensitive information in the background based on the target payment ID and the target order ID, so as to process the payment of the target order. In this way, because only the target order identifier corresponding to the target order is transmitted between the merchant client and the payment client in the terminal device through the front-end method, and other transaction sensitive information is not transmitted, therefore, the risk of transaction sensitive information being maliciously intercepted can be reduced. Improve the security of information transmission in the payment process.

Fig. 10 is a schematic structural diagram of a payment device provided by an embodiment of the present application. The payment device can be configured on the clearing institution server.

As shown in Figure 10, the payment device 1000 may include:

The second receiving module 1001 is configured to receive the first payment request for the target order sent by the payment client corresponding to the target payment institution, the first payment request includes the target payment identifier and the target order corresponding to the target order ID, the target payment ID is the unique identity of the user in the target payment institution;

1002. In response to the first payment request, send a second payment request to a payment server corresponding to the target payment institution according to the target payment identifier and the target order identifier, where the second payment request is used for Instructing the payment server to perform payment processing on the target order according to the target payment ID and the target order ID to obtain a payment result.

The above-mentioned payment device 1000 will be described in detail below, specifically as follows:

In some of these embodiments, the payment device 1000 may also include:

The seventh receiving module is used to receive the 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;

An identification generating module, configured to generate the target order identification corresponding to the target order according to the order information;

An identifier returning module, configured to return the target order identifier to the merchant client.

In some of these embodiments, the payment device 1000 may also include:

A first storage module, configured to associate and store the target order identifier with the order information after the target order identifier corresponding to the target order is generated according to the order information.

In some of these embodiments, the payment device 1000 may also include:

The fourth request module is configured to receive the payment before receiving the first payment request for the target order sent by the payment client corresponding to the target payment institution after the target order identifier is associated and stored with the order information A second query request sent by the server for the target order, where the second query request includes the target order identifier;

An information query module, configured to query and obtain order information corresponding to the target order according to the target order identifier in response to the second query request;

An information returning module, configured to return the order information to the payment server.

Therefore, by using tokenization technology to mark sensitive information such as user identity information and order information, the user identity information is marked with the target payment ID, the order information is marked with the target order ID, and the target payment ID and the target order ID are used during the payment process. In this way, the risk of malicious interception of transaction sensitive information can be further reduced, and the security of information transmission during the payment process can be improved.

Fig. 11 is a schematic structural diagram of a payment device provided by an embodiment of the present application. The payment device can be configured in a payment server.

As shown in Figure 11, the payment device 1100 may include:

The third receiving module 1101 is configured to receive the second payment request for the target order sent by the clearing institution server, the second payment request includes the target payment identifier and the target order identifier corresponding to the target order, and the target payment The identifier is the unique identity of the user in the target payment institution, and the target payment institution is the payment institution corresponding to the payment server;

The payment processing module 1102 is configured to, in response to the second payment request, perform payment processing on the target order according to the target payment identifier and the target order identifier, and obtain a payment result.

The above-mentioned payment device 1100 will be described in detail below, specifically as follows:

In some of these embodiments, the payment device 1100 may also include:

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

A fifth request module, configured to send a second query request for the target order to the clearing institution server in response to the first query request, and the second query request is used to instruct the clearing institution server to Query the target order identifier and obtain the order information corresponding to the target order;

An information forwarding module, configured to receive the order information returned by the clearing institution server, and forward the order information to the payment client.

In some of these embodiments, the payment device 1100 may also include:

The second storage module is configured to receive and save the payment information sent by the payment client after forwarding the order information to the payment client;

The above-mentioned payment processing module 1102 may specifically include:

A query submodule, configured to query and obtain the payment information according to the target payment identifier and the target order identifier;

The payment sub-module is configured to perform payment processing on the target order according to the payment information, and obtain a payment result.

Therefore, by using tokenization technology to mark sensitive information such as user identity information and order information, the user identity information is marked with the target payment ID, the order information is marked with the target order ID, and the target payment ID and the target order ID are used during the payment process. In this way, the risk of malicious interception of transaction sensitive information can be further reduced, and the security of information transmission during the payment process can be improved.

Fig. 12 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

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

Specifically, the above-mentioned processor 1201 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

Memory 1202 may include mass storage for data or instructions. By way of example and not limitation, the memory 1202 may include a hard disk drive (Hard Disk Drive, HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a Universal Serial Bus (Universal Serial Bus, USB) drive or two or more Combinations of multiple of the above. Storage 1202 may include removable or non-removable (or fixed) media, where appropriate. Under appropriate circumstances, the storage 1202 can be inside or outside the comprehensive gateway disaster recovery device. In a particular embodiment, memory 1202 is a non-volatile solid-state memory.

In particular embodiments, memory may 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. Thus, in general, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions, and when the software is executed (e.g., by one or multiple processors) operable to perform the operations described with reference to the method according to an aspect of the present application.

The processor 1201 reads and executes the computer program instructions stored in the memory 1202 to implement any payment method in the above-mentioned embodiments.

In some examples, the electronic device 1200 may further include a communication interface 1203 and a bus 1210 . Wherein, as shown in FIG. 12 , a processor 1201 , a memory 1202 , and a communication interface 1203 are connected through a bus 1210 to complete mutual communication.

The communication interface 1203 is mainly used to implement communication between various modules, devices, units and/or devices in the embodiments of the present application.

The bus 1210 includes hardware, software or both, and couples the components of the online data traffic charging device to each other. By way of example and not limitation, bus 1210 may include Accelerated Graphics Port (AGP) or other graphics bus, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), HyperTransport (HT) interconnect, Industry Standard Architecture (ISA ) bus, InfiniBand Interconnect, Low Pin Count (LPC) bus, memory bus, Micro Channel Architecture (MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced A Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable bus or a combination of two or more of these. Bus 1210 may comprise one or more buses, where appropriate. Although the embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.

Exemplarily, the electronic device 1200 may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle electronic device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA) wait.

The electronic device 1200 can execute the payment method in the embodiment of the present application, so as to implement the payment method and device described in conjunction with FIG. 1 to FIG. 11 .

In addition, in combination with the payment methods in the foregoing embodiments, the embodiments of the present application may provide a computer-readable storage medium for implementation. Computer program instructions are stored on the computer-readable storage medium; when the computer program instructions are executed by a processor, any payment method in the above-mentioned embodiments is realized. 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 disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, etc.

It is to be understood that the application is not limited to the specific configurations and processes described above and shown in the figures. For conciseness, 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 the present application is not limited to the specific steps described and shown, and those skilled in the art may make various changes, modifications and additions, or change the order of the steps after understanding the spirit of the present application.

The functional blocks shown in the structural block diagrams described above may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an application specific integrated circuit (ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the present application are the programs or code segments employed to perform the required tasks. Programs or code segments can be stored in machine-readable media, or transmitted over transmission media or communication links by data signals carried in carrier waves. "Machine-readable medium" may include any medium that can store or transmit 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, and the like. Code segments may be downloaded via a computer network such as the Internet, an Intranet, or the like.

It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above steps, that is, the steps may be performed in the order mentioned in the embodiment, or may be different from the order in the embodiment, or several steps may be performed simultaneously.

Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present application. It will be understood that each block of the flowchart and/or block diagrams, and combinations of blocks in the flowchart and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that execution of these instructions via the processor of the computer or other programmable data processing apparatus enables Implementation of the functions/actions specified in one or more blocks of the flowchart and/or block diagrams. Such processors may be, but are not limited to, general purpose processors, special purpose processors, application specific processors, or field programmable logic circuits. It can also be 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 realized by dedicated hardware for performing specified functions or actions, or can be implemented by dedicated hardware and Combination of computer instructions to achieve.

The above is only a specific implementation of the present application, and those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described systems, modules and units can refer to the foregoing method embodiments The corresponding process in , will not be repeated here. It should be understood that the protection scope of the present application is not limited thereto, and any person familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the application, and these modifications or replacements should cover all Within the protection scope of this application.

Claims (19)

1. A payment method applied to a terminal device, wherein a merchant client and a payment client corresponding to a target payment mechanism are arranged in the terminal device, the method comprising:

receiving a first input of a user triggering a payment target order in the merchant client;

responsive to the first input, sending, by the merchant client, a target order identification corresponding to the target order to the payment client;

sending a first payment request aiming at the target order to a clearing mechanism 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 the target payment mechanism;

the first payment request is used for indicating the clearing mechanism server to send a second payment request to a payment server corresponding to the target payment mechanism according to the target payment identifier and the target order identifier, and the second payment request is used for indicating the payment server to pay for the target order according to the target payment identifier and the target order identifier, so that a payment result is obtained.

2. The method of claim 1, wherein a payment control is provided in the merchant client;

after receiving a first input by a user triggering a payment target order in the merchant client, the method further comprises:

invoking, by the merchant client, the payment control;

and calling the payment client through the payment control, and displaying a payment interface in the payment client.

3. The method of claim 2, wherein after sending, by the merchant client to the payment client, a target order identification corresponding to the target order, before sending, by the payment client to a clearinghouse server, a first payment request for the target order, the method further comprises:

sending a first query request aiming at the target order to the payment server through the payment client, wherein the first query request comprises the target order identifier, and the first query request is used for indicating the payment server to acquire order information corresponding to the target order from the clearing house server according to the target order identifier;

receiving order information corresponding to the target order returned by the payment server;

And displaying the order information in the payment interface.

4. A method according to claim 3, wherein after displaying the order information in the payment interface, the method further comprises:

receiving a second input by a user based on the payment interface;

and responding to the second input, acquiring payment information confirmed by the user, sending the payment information to the payment server through the payment client so that the payment server records the payment information, inquiring and acquiring the payment information according to the target payment identifier and the target order identifier under the condition that the second payment request is received, and carrying out payment processing on the target order according to the payment information to obtain a payment result.

5. The method of claim 2, wherein after sending a first payment request for the target order to a clearinghouse server via the payment client, the method further comprises:

polling the clearing house server for a payment result corresponding to the target order;

and under the condition that the payment result is obtained through polling, the payment interface is jumped back to a payment result interface in the merchant client, and the payment result is displayed in the payment result interface.

6. The method of claim 1, wherein prior to sending, by the merchant client to the payment client, a target order identification corresponding to the target order, the method further comprises:

when the user selects a target payment mode for the target order in the merchant client, sending order information corresponding to the target order to the clearing mechanism server by the merchant client so that the clearing mechanism server generates the target order identifier corresponding to the target order according to the order information, wherein the target payment mode is a payment mode corresponding to a target payment platform, and the target payment platform is a platform capable of providing the payment mode corresponding to the target payment mechanism;

and receiving the target order identification returned by the clearing house server.

7. A payment method applied to a clearing house server, the method comprising:

receiving a first payment request for a target order sent by a payment client corresponding to a target payment mechanism, wherein the first payment request comprises a target payment identifier corresponding to the target order and a target order identifier, and the target payment identifier is a unique identity identifier of a user in the target payment mechanism;

Responding to the first payment request, sending a second payment request to a payment server corresponding to the target payment mechanism according to the target payment identifier and the target order identifier, wherein the second payment request is used for indicating the payment server to pay the target order according to the target payment identifier and the target order identifier, and obtaining a payment result.

8. The method of claim 7, wherein prior to receiving the first payment request for the target order sent by the payment client corresponding to the target payment mechanism, the method further comprises:

receiving order information corresponding to the target order sent by a merchant client;

generating the target order identification corresponding to the target order according to the order information;

and returning the target order identification to the merchant client.

9. The method of claim 8, wherein after generating the target order identification corresponding to the target order from the order information, the method further comprises:

and storing the target order identification and the order information in a correlated way.

10. The method of claim 9, wherein after storing the target order identification in association with the order information, the method further comprises, prior to receiving a first payment request for a target order sent by a payment client corresponding to a target payment mechanism:

Receiving a second query request for the target order sent by the payment server, wherein the second query request comprises the target order identifier;

responding to the second query request, querying and acquiring order information corresponding to the target order according to the target order identification;

and returning the order information to the payment server.

11. A payment method applied to a payment server, the method comprising:

receiving a second payment request for a target order sent by a clearing mechanism server, wherein the second payment request comprises a target payment identifier corresponding to the target order and a target order identifier, the target payment identifier is a unique identity identifier of a user in a target payment mechanism, and the target payment mechanism is a payment mechanism corresponding to the payment server;

and responding to the second payment request, and carrying out payment processing on the target order according to the target payment identifier and the target order identifier to obtain a payment result.

12. The method of claim 11, wherein prior to receiving the second payment request for the target order sent by the clearinghouse server, the method further comprises:

Receiving a first query request for the target order sent by a payment client corresponding to the target payment mechanism, wherein the first query request comprises the target order identifier;

responding to the first query request, and sending a second query request for the target order to the clearing mechanism server, wherein the second query request is used for indicating the clearing mechanism server to query according to the target order identifier and acquire order information corresponding to the target order;

and receiving the order information returned by the clearing house server and forwarding the order information to the payment client.

13. The method of claim 12, wherein after forwarding the order information to the payment client, the method further comprises:

receiving and storing payment information sent by the payment client;

the payment processing is carried out on the target order according to the target payment identifier and the target order identifier to obtain a payment result, and the method comprises the following steps:

inquiring and acquiring the payment information according to the target payment identifier and the target order identifier;

and carrying out payment processing on the target order according to the payment information to obtain a payment result.

14. A payment apparatus configured in a terminal device, where a merchant client and a payment client corresponding to a target payment mechanism are provided, the apparatus comprising:

the first receiving module is used for receiving a first input of a user triggering a payment target order in the merchant client;

a first sending module, configured to send, by the merchant client, a target order identifier corresponding to the target order to the payment client in response to the first input;

the first request module is used for sending a first payment request aiming at the target order to a clearing mechanism 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 the target payment mechanism;

the first payment request is used for indicating the clearing mechanism server to send a second payment request to a payment server corresponding to the target payment mechanism according to the target payment identifier and the target order identifier, and the second payment request is used for indicating the payment server to pay for the target order according to the target payment identifier and the target order identifier, so that a payment result is obtained.

15. A payment device configured at a clearing house server, the device comprising:

the second receiving module is used for receiving a first payment request for a target order sent by a payment client corresponding to a target payment mechanism, wherein the first payment request comprises a target payment identifier and a target order identifier corresponding to the target order, and the target payment identifier is a unique identity identifier of a user in the target payment mechanism;

the second request module is used for responding to the first payment request, sending a second payment request to a payment server corresponding to the target payment mechanism according to the target payment identifier and the target order identifier, and the second payment request is used for indicating the payment server to pay the target order according to the target payment identifier and the target order identifier so as to obtain a payment result.

16. A payment device configured in a payment server, the device comprising:

the third receiving module is used for receiving a second payment request for the target order sent by the clearing mechanism server, wherein the second payment request comprises a target payment identifier corresponding to the target order and a target order identifier, the target payment identifier is a unique identity identifier of a user in a target payment mechanism, and the target payment mechanism is a payment mechanism corresponding to the payment server;

And the payment processing module is used for responding to the second payment request, and performing payment processing on the target order according to the target payment identifier and the target order identifier to obtain a payment result.

17. An electronic device, the device comprising: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements the steps of the payment method as claimed in any one of claims 1-6 or 7-10 or 11-13.

18. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon computer program instructions which, when executed by a processor, implement the steps of the payment method according to any of claims 1-6 or 7-10 or 11-13.

19. A computer program product, characterized in that instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to perform the steps of the payment method according to any of claims 1-6 or 7-10 or 11-13.

Images