Payment processing method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a payment processing method, a payment processing device, payment processing equipment and a storage medium, which can relate to the mobile payment technology in the Internet technology. The method comprises at least two of the following items: the first item: sending a first order inquiry request for a target payment item to a payment server corresponding to an instant messaging client; receiving a first order inquiry response sent by the payment server; and determining a payment result of the target payment item based on the first order inquiry response. And 2, receiving a payment success notification generated and sent by the payment server based on the payment result of the target payment item. And a third item: receiving a payment success notification forwarded by the payment server from a third-party payment server. Therefore, the probability that the payment success notification is successfully received can be improved, and then it is ensured that the payee can receive the payment success notification and collect money as much as possible, so that the experience feeling of the payer and the payee is improved.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of Internet technologies, and in particular, to a payment processing method, apparatus, device, and storage medium. Background Art

[0002] Instant messaging clients currently provide convenient payment functions, such as red envelope forwarding, money transfer, and face-to-face payment.

[0003] Currently, when the payer successfully makes a payment through the instant messaging client, the third-party payment server sends a payment success notification to the payment server corresponding to the instant messaging client, and the payment server then sends a payment success notification to the merchant server corresponding to the instant messaging client. After the merchant server receives the payment success notification, for face-to-face payment, the merchant server can send a payment success notification to the terminal device corresponding to the payee. For red envelope forwarding and money transfer, the merchant server can trigger the terminal device corresponding to the payee to display a receipt bubble message so that the payee can receive the payment as soon as possible.

[0004] However, currently, the merchant server can only obtain the payment success notification through the above-mentioned one link. When this link is abnormal, it cannot obtain the payment success notification, which in turn causes the payee not to receive the payment success notification and cannot receive the payment, thereby reducing the experience of the payer and the payee. Summary of the Invention

[0005] Embodiments of the present application provide a payment processing method, apparatus, device, and storage medium, which can improve the probability of successfully receiving the payment success notification, and further ensure that the payee can receive the payment success notification and receive the payment as much as possible, so as to improve the experience of the payer and the payee.

[0006] In a first aspect, embodiments of the present application provide a payment processing method, which is applied to a merchant server corresponding to an instant messaging client. The method includes at least two of the following:

[0007] Send a first order inquiry request for a target payment item to the payment server corresponding to the instant messaging client; and receive a first order inquiry response sent by the payment server; determine the payment result of the target payment item based on the first order inquiry response;

[0008] Receive a payment success notification generated and sent by the payment server based on the payment result of the target payment item;

[0009] Receive a payment success notification from the third-party payment server forwarded by the payment server.

[0010] In a second aspect, embodiments of the present application provide a payment processing method, which is applied to a payment server corresponding to an instant messaging client. The method includes at least two of the following:

[0011] Receive a first order inquiry request for a target payment item sent by the merchant server corresponding to the instant messaging client; and send the first order inquiry request to the third-party payment server; receive a first order inquiry response sent by the third-party server; and send the first order inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order inquiry response;

[0012] Generate a payment success notification based on the payment result of the target payment item, and send the payment success notification to the merchant server;

[0013] Receive a payment success notification from the third-party payment server; and forward the payment success notification to the merchant server.

[0014] Thirdly, an embodiment of the present application provides a payment processing device, which includes: a communication module and a processing module;

[0015] The communication module is used for: sending a first order inquiry request for a target payment item to the payment server corresponding to the instant messaging client; and receiving a first order inquiry response sent by the payment server; the processing module is used for determining the payment result of the target payment item based on the first order inquiry response; the communication module is also used for receiving a payment success notification generated and sent by the payment server based on the payment result of the target payment item; or,

[0016] The communication module is used for: sending a first order inquiry request for a target payment item to the payment server corresponding to the instant messaging client; and receiving a first order inquiry response sent by the payment server; the processing module is used for determining the payment result of the target payment item based on the first order inquiry response; the communication module is also used for receiving a payment success notification forwarded by the payment server from the third-party payment server; or,

[0017] The communication module is used for: receiving a payment success notification generated and sent by the payment server based on the payment result of the target payment item; receiving a payment success notification forwarded by the payment server from the third-party payment server; or,

[0018] The communication module is used for: sending a first order inquiry request for a target payment item to the payment server corresponding to the instant messaging client; and receiving a first order inquiry response sent by the payment server; the processing module is used for determining the payment result of the target payment item based on the first order inquiry response; the communication module is also used for: receiving a payment success notification generated and sent by the payment server based on the payment result of the target payment item; receiving a payment success notification forwarded by the payment server from the third-party payment server.

[0019] In some implementable manners, the communication module is specifically configured to: send a first order query request to the payment server by using at least one of an asynchronous order query manner based on MQ and an asynchronous order query manner based on an event center.

[0020] In some implementable manners, the communication module is specifically configured to: send a first order query request to the payment server simultaneously by using an asynchronous order query manner based on MQ and an asynchronous order query manner based on an event center.

[0021] In some implementable manners, the communication module is specifically configured to: send a first order query request to the payment server by using an asynchronous order query manner based on MQ; when the order query fails by using the asynchronous order query manner based on MQ, send a first order query request to the payment server by using an asynchronous order query manner based on an event center.

[0022] In some implementable manners, the communication module is specifically configured to: send a first order query request to the payment server by using an asynchronous order query manner based on an event center; when the order query fails by using the asynchronous order query manner based on an event center, send a first order query request to the payment server by using an asynchronous order query manner based on MQ.

[0023] In some implementable manners, the communication module is specifically configured to: receive a payment success notification sent by the payment server by using at least one of a real-time notification manner and an asynchronous notification manner when the payment result is payment success; receive a payment success notification sent by the payment server when the payment result is payment status uncertain and a bill is processed for the target payment item.

[0024] In a fourth aspect, an embodiment of the present application provides a payment processing apparatus, and the apparatus includes: a communication module and a processing module;

[0025] The communication module is configured to: receive a first order query request for a target payment item sent by a merchant server corresponding to an instant messaging client; send the first order query request to a third-party payment server; receive a first order query response sent by the third-party server; and send the first order query response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order query response; the processing module is configured to generate a payment success notification based on the payment result of the target payment item, and the communication module is further configured to send the payment success notification to the merchant server; or,

[0026] The communication module is used to: receive a first bill inquiry request for a target payment item sent by a merchant server corresponding to an instant messaging client; and send the first bill inquiry request to a third-party payment server; receive a first bill inquiry response sent by the third-party server; and send the first bill inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first bill inquiry response; receive a payment success notification from the third-party payment server; and forward the payment success notification to the merchant server; or,

[0027] The processing module is used to generate a payment success notification based on the payment result of the target payment item. The communication module is used to: send a payment success notification to the merchant server; receive a payment success notification from the third-party payment server; and forward the payment success notification to the merchant server; or,

[0028] The communication module is used to: receive a first bill inquiry request for a target payment item sent by a merchant server corresponding to an instant messaging client; and send the first bill inquiry request to a third-party payment server; receive a first bill inquiry response sent by the third-party server; and send the first bill inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first bill inquiry response. The processing module is used to generate a payment success notification based on the payment result of the target payment item. The communication module is also used to: send a payment success notification to the merchant server; receive a payment success notification from the third-party payment server; and forward the payment success notification to the merchant server.

[0029] In some implementable ways, the communication module is specifically used to: receive a first bill inquiry request sent by the merchant server in at least one of an asynchronous bill inquiry method based on MQ and an asynchronous bill inquiry method based on an event center.

[0030] In some implementable ways, the communication module is specifically used to: when the payment result is a payment success, send a payment success notification to the merchant server in at least one of a real-time notification method and an asynchronous notification method; when the payment result is an uncertain payment status, send a payment success notification to the merchant server in the case of bill processing for the target payment item.

[0031] In some implementable ways, the communication module is specifically used to: send a payment success notification to the merchant server in both a real-time notification method and an asynchronous notification method at the same time.

[0032] In some implementable ways, the communication module is specifically used to: send a payment success notification to the merchant server in a real-time notification method; when the sending of the payment success notification fails in the real-time notification method, send a payment success notification to the merchant server in an asynchronous notification method.

[0033] In some implementable manners, the communication module is further configured to perform at least one of the following before sending a payment success notification to the merchant server when processing the bill for the target payment item:

[0034] Send an indication message for indicating that the payment status is uncertain to the terminal device that initiated the target payment item; and receive a re-payment request for the target payment item sent by the terminal device; when the re-payment request is the first payment request for the target payment item received by the payment server, send the re-payment request to the third-party payment server and receive a payment response sent by the third-party payment server; when the re-payment request is not the first payment request for the target payment item received by the payment server, send a second bill inquiry request for the target payment item to the third-party payment server and receive a second bill inquiry response sent by the third-party payment server;

[0035] Send a bill closing or bill supplementing request for the target payment item to the third-party payment server; receive a bill closing or bill supplementing response sent by the third-party payment server.

[0036] In some implementable manners, the communication module is specifically configured to perform at least one of the following:

[0037] When it is determined that the target payment item has been successfully paid based on the payment response or the second bill inquiry response, send a payment success notification to the merchant server;

[0038] When it is determined that the target payment item has been successfully paid based on the bill closing or bill supplementing response, send a payment success notification to the merchant server.

[0039] In some implementable manners, the communication module is specifically configured to: when it is determined that the target payment item has been successfully paid based on the payment response or the second bill inquiry response, send a payment success notification to the merchant server by using at least one of a real-time notification manner and an asynchronous notification manner.

[0040] In some implementable manners, the communication module is specifically configured to: send a bill closing or bill supplementing request for the target payment item to the third-party payment server by using an asynchronous bill closing or bill supplementing manner.

[0041] In a fifth aspect, an electronic device is provided, including: a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in any one of the first aspect to the second aspect or its various implementable manners.

[0042] In a sixth aspect, a computer-readable storage medium is provided, which is used to store a computer program, and the computer program causes a computer to execute the method in any one of the first aspect to the second aspect or its various implementable manners.

[0043] In a seventh aspect, there is provided a computer program product including computer program instructions that cause a computer to execute the method according to any one of the first aspect to the second aspect or its various implementations.

[0044] In an eighth aspect, there is provided a computer program that causes a computer to execute the method according to any one of the first aspect to the second aspect or its various implementations.

[0045] Through the technical solution provided in this application, the merchant server can obtain payment success notifications through multiple links, thereby increasing the probability of successfully receiving payment success notifications, and further ensuring that the payee can receive payment success notifications and conduct collections as much as possible, so as to improve the experience of both the payer and the payee. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0047] Figure 1 It is a schematic diagram of a system architecture related to an embodiment of this application;

[0048] Figure 2 It is an interaction flowchart of a payment processing method provided in an embodiment of this application;

[0049] Figure 3 It is a flowchart of an asynchronous order query process provided in an embodiment of this application;

[0050] Figure 4 It is a flowchart of the process of issuing a payment success notification provided in an embodiment of this application;

[0051] Figure 5 It is a schematic diagram of a payment processing device 500 provided in an embodiment of this application;

[0052] Figure 6 It is a schematic diagram of a payment processing device 600 provided in an embodiment of this application;

[0053] Figure 7 It is a schematic block diagram of an electronic device provided in an embodiment of this application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0054] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0055] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances, so that the embodiments of the present invention described here can be implemented in an order other than those illustrated or described here. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or server comprising a series of steps or units does not necessarily need to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0056] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of the overall module or unit that includes the function of the module or unit.

[0057] The embodiments of the present application may relate to mobile payment in Internet technology.

[0058] Among them, Internet technology refers to an information technology developed on the basis of computer technology. It connects individual computers or networks together to form a specific network system and realizes the transmission and sharing of information.

[0059] Mobile payment refers to the use of mobile clients such as mobile phones and other electronic products to conduct electronic currency payment. Mobile payment effectively combines the Internet, terminal devices, and financial institutions to form a new payment system. Mobile payment has created a new payment method and made electronic currency begin to become popular.

[0060] Among them, in the embodiments of the present application, the instant messaging client can use terminal devices such as mobile phones and tablet computers to achieve mobile payment.

[0061] It should be understood that an instant messaging client is a communication tool based on Internet technology that allows users to communicate with each other in real time through text, voice, video, etc. Common instant messaging clients include WeChat, QQ, WeChat for Business, etc., but are not limited to these. These communication tools usually provide functions such as instant messaging, voice calls, video calls, file transfers, etc., allowing users to communicate and collaborate conveniently.

[0062] The following is an explanation of the relevant knowledge involved in this application:

[0063] 1. Asynchronous call is a program calling method. In this calling method, after the caller initiates a request, it does not need to wait for the callee to return the response result immediately, but can continue to perform other operations. When the callee completes the processing, it will notify the caller through a callback function (callback service) or other methods, and return the response result.

[0064] 2. Message Queue (MQ) is used for message delivery between different applications and services. By putting messages into MQ, producers (i.e. manufacturers or publishers) and consumers (i.e. subscribers) can be decoupled, that is, producers do not need to wait for consumers to process messages, and consumers can get messages when needed. This model can improve the scalability and reliability of the system, while also reducing the coupling of applications.

[0065] It should be understood that the asynchronous order query method based on MQ is actually an asynchronous call method based on MQ, in which the producer can put the order query request into MQ, the consumer reads the order query request in MQ, and triggers the order query process based on the read order query request. In which, the producer can be understood as the caller and the consumer can be understood as the callee.

[0066] It should be understood that the asynchronous notification method in the embodiment of the present application can also be an asynchronous call method based on MQ, wherein the producer can put the payment success notification into MQ, the consumer reads the payment success notification in MQ, and implements the payment success notification based on the payment success notification read. Among them, the producer can be understood as the caller, and the consumer can be understood as the callee.

[0067] It should be understood that the asynchronous order closing or order supplementing method in the embodiment of the present application can also be an asynchronous call method based on MQ, wherein the producer can put the order closing or order supplementing request into MQ, the consumer reads the order closing or order supplementing request in MQ, and implements the order closing or order supplementing based on the read order closing or order supplementing request. Among them, the producer can be understood as the caller, and the consumer can be understood as the callee.

[0068] III. The asynchronous order query method based on the event center, also known as the asynchronous order query method based on publishing events, is also a common asynchronous call pattern. Among them, the event publisher publishes the order query event to an event center, and the event subscriber subscribes to the event and triggers the order query process. This processing method realizes the decoupling of the event publisher and the event subscriber. Among them, the event publisher here can be understood as the calling party, and the event subscriber can be understood as the called party.

[0069] It should be understood that the asynchronous notification method in the embodiments of the present application can also be an asynchronous call method based on the event center. Among them, the event publisher publishes the payment success notification to an event center, and the event subscriber subscribes to the event and makes the corresponding payment success notification.

[0070] It should be understood that the asynchronous order closing or order supplementing method in the embodiments of the present application can also be an asynchronous call method based on the event center. Among them, the event publisher publishes the order closing or order supplementing request to an event center, and the event subscriber subscribes to the event and makes the corresponding order closing or order supplementing.

[0071] IV. The five 9s of the merchant notification (i.e., the payment success notification sent to the merchant server) are specifically as follows: security, stability, timeliness, scalability, and maintainability.

[0072] The technical problems to be solved, inventive concepts, and system architectures of the embodiments of the present application will be elaborated below:

[0073] As described above, currently, the merchant server can only obtain the payment success notification through one link. When this link has an abnormality, it causes the merchant server to be unable to obtain the payment success notification, and further causes the payee to be unable to receive the payment success notification and conduct collection, thereby reducing the experience of the payer and the payee.

[0074] To solve the above technical problems, the embodiments of the present application propose that the merchant server can obtain the payment success notification through multiple links, thereby increasing the probability of successfully receiving the payment success notification, and further ensuring that the payee can receive the payment success notification and conduct collection as much as possible, so as to improve the experience of the payer and the payee.

[0075] In some implementable ways, the system architecture of the embodiments of the present application is as Figure 1 shown.

[0076] Figure 1 This is a schematic diagram of a system architecture related to the embodiments of the present application, including a terminal device 110, a merchant server 120 corresponding to the instant messaging client, a payment server 130 corresponding to the instant messaging client, and a third-party payment server 140.

[0077] Among them, the terminal device 110 can be installed with an instant messaging client to perform mobile payments through the instant messaging client, such as red envelope forwarding, money transfer, face-to-face payment, etc.

[0078] It should be understood that the instant messaging client can be any communication tool based on Internet technology that allows users to communicate in real time through text, voice, video, etc. For example, it can be WeChat, QQ, Enterprise WeChat, etc., but not limited to this.

[0079] In some implementable ways, the terminal device 110 can be a smart phone, a tablet computer, a smart watch, Virtual Reality (VR), Augmented Reality (AR), etc., but not limited thereto.

[0080] The terminal device 110 and the merchant server 120 can be directly or indirectly connected through wired or wireless communication methods, and this application does not make any restrictions here.

[0081] The terminal device 110 and the payment server 130 can be directly or indirectly connected through wired or wireless communication methods, and this application does not make any restrictions here.

[0082] The merchant server 120 and the payment server 130 can be directly or indirectly connected through wired or wireless communication methods, and this application does not make any restrictions here.

[0083] The payment server 130 and the third-party payment server 140 can be directly or indirectly connected through wired or wireless communication methods, and this application does not make any restrictions here.

[0084] In some implementable ways, for any one of the merchant server 120, the payment server 130, and the third-party payment server 140, it can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms.

[0085] It should be understood that in the embodiments of this application, the merchant server 120 is also referred to as a social business system, and the social business can be a red envelope forwarding business, a money transfer business, a face-to-face payment business, etc. The payment server 130 is also referred to as a social payment system. The third-party payment server 140 is also referred to as a merchant platform or a merchant payment platform. For example, it can be the merchant payment platform Fit.

[0086] It should be noted that Figure 1 This is only a schematic diagram of a system architecture provided by the embodiments of the present application. The system architecture involved in the embodiments of the present application is not limited to Figure 1 the system architecture shown. For example, in some implementable ways, based on Figure 1 the system architecture shown, the system architecture involved in the embodiments of the present application may further include: a terminal device corresponding to the payee, and this terminal device may be connected to the merchant server 120 and the payment server 130.

[0087] The embodiments of the present application will be elaborated in detail below:

[0088] Figure 2 This is an interaction flowchart of a payment processing method provided by the embodiments of the present application. The execution entities involved in this method include: the merchant server corresponding to the instant messaging client, the payment server corresponding to the instant messaging client, and the third-party payment server, but are not limited thereto. Among them, for any one of the merchant server, the payment server, and the third-party payment server, it may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. As Figure 2 shown, this method includes at least two of the following:

[0089] (The first item, optionally):

[0090] S210-A: The merchant server sends a first order query request for a target payment item to the payment server;

[0091] S220-A: The payment server sends the first order query request to the third-party payment server;

[0092] S230-A: The third-party payment server performs an order query for the target payment item in response to the first order query request;

[0093] S240-A: The third-party payment server sends a first order query response to the payment server;

[0094] S250-A: The payment server sends the first order query response to the merchant server;

[0095] S260-A: The merchant server determines the payment result of the target payment item based on the first order query response;

[0096] (The second item, optionally):

[0097] S210-B: The payment server generates a payment success notification based on the payment result of the target payment item;

[0098] S220-B: The payment server sends the payment success notification to the merchant server;

[0099] (The third item, optionally):

[0100] S210-C: The third-party payment server sends a payment success notification to the payment server;

[0101] S220-C: The payment server forwards the payment success notification to the merchant server.

[0102] The following elaborates on S210-A:

[0103] It should be understood that the target payment item can be any payment made by any user using an instant messaging client. The target payment item can be a payment item initiated by any of the following payment methods, but not limited to: red envelope forwarding method, transfer method, face-to-face payment method.

[0104] In some implementable ways, the merchant server can send the first order query request to the payment server by at least one of an MQ-based asynchronous order query method and an event center-based asynchronous order query method.

[0105] In other words, the merchant server can send the first order query request to the payment server by an MQ-based asynchronous order query method. Or, the merchant server can send the first order query request to the payment server by an event center-based asynchronous order query method. Or, the merchant server can send the first order query request to the payment server by an MQ-based asynchronous order query method and an event center-based asynchronous order query method.

[0106] It should be understood that if the merchant server sends the first order query request to the payment server by an MQ-based asynchronous order query method, then the merchant server can act as a producer to put the first order query request into the MQ, and the merchant server can also act as a consumer to read the first order query request in the MQ. After reading the first order query request, it can send the first order query request to the payment server.

[0107] It should be understood that if the merchant server sends the first order query request to the payment server by an event center-based asynchronous order query method, then the merchant server can act as an event publisher to publish the first order query request to an event center, and the merchant server can also act as an event subscriber to subscribe to the event. After the merchant server reads the first order query request as an event subscriber, it can send the first order query request to the payment server.

[0108] In the embodiments of the present application, the merchant server sends a first order query request to the payment server by using an asynchronous order query method based on MQ and an asynchronous order query method based on an event center, including, but not limited to:

[0109] Implementation method one: The merchant server sends a first order query request to the payment server by using an asynchronous order query method based on MQ and an asynchronous order query method based on an event center simultaneously.

[0110] In other words, the merchant server can send a first order query request to the payment server based on the asynchronous order query method based on MQ and the asynchronous order query method based on an event center respectively, and these two asynchronous order query methods are independent of each other.

[0111] Implementation method two: The merchant server sends a first order query request to the payment server by using an asynchronous order query method based on MQ; when the order query fails using the asynchronous order query method based on MQ, the merchant server sends a first order query request to the payment server by using an asynchronous order query method based on an event center.

[0112] On the contrary, when the order query is successful using the asynchronous order query method based on MQ, the merchant server does not need to send a first order query request to the payment server by using an asynchronous order query method based on an event center.

[0113] Implementation method three: The merchant server sends a first order query request to the payment server by using an asynchronous order query method based on an event center; when the order query fails using the asynchronous order query method based on an event center, the merchant server sends a first order query request to the payment server by using an asynchronous order query method based on MQ.

[0114] On the contrary, when the order query is successful using the asynchronous order query method based on an event center, the merchant server does not need to send a first order query request to the payment server by using an asynchronous order query method based on MQ.

[0115] The following is an elaboration on S220-A and S230-A:

[0116] It should be understood that as a merchant payment platform, the third-party payment server can generate a payment bill for the target payment item. Based on this, the payment server needs to send a first order query request to the third-party payment server so that the third-party payment server can perform an order query for the target payment item in response to the first order query request.

[0117] The following is an elaboration on S240-A to S260-A:

[0118] It should be understood that the first order query response includes the following situations:

[0119] Situation one: The order query for the target payment item is successful, and the query result indicates that the payment result of the target payment item is payment success;

[0120] Case 2: The single - order query for the target payment item is successful, and the query result indicates that the payment result of the target payment item is of uncertain payment status;

[0121] Case 3: The single - order query for the target payment item is successful, and the query result indicates that the payment result of the target payment item is payment failure;

[0122] Case 4: The single - order query for the target payment item fails.

[0123] It should be understood that if the merchant server sends the first single - order query request to the payment server using the MQ - based asynchronous single - order query method or the event - center - based asynchronous single - order query method, then there is only one first single - order query request, and correspondingly, there is also only one first single - order response.

[0124] If the merchant server sends the first single - order query request to the payment server using both the MQ - based asynchronous single - order query method and the event - center - based asynchronous single - order query method simultaneously, then there are two first single - order query requests, and correspondingly, there are also two first single - order responses.

[0125] If the merchant server sends the first single - order query request to the payment server using the MQ - based asynchronous single - order query method; when the single - order query using the MQ - based asynchronous single - order query method fails, it sends the first single - order query request to the payment server using the event - center - based asynchronous single - order query method. In this case, there may be one or two first single - order query requests, and correspondingly, there are also one or two first single - order responses.

[0126] If the merchant server sends the first single - order query request to the payment server using the event - center - based asynchronous single - order query method; when the single - order query using the event - center - based asynchronous single - order query method fails, it sends the first single - order query request to the payment server using the MQ - based asynchronous single - order query method. In this case, there may be one or two first single - order query requests, and correspondingly, there are also one or two first single - order responses.

[0127] Based on this, the merchant server determines the payment result of the target payment item based on the first single - order response, including:

[0128] When the merchant server receives one first single - order response, the merchant server can determine the payment result of the target payment item based on the above - mentioned four cases corresponding to this first single - order response.

[0129] When the merchant server receives two first single - order responses, then there are the following three cases:

[0130] Case 1: If the merchant server sends a first order query request to the payment server simultaneously using both the MQ-based asynchronous order query method and the event center-based asynchronous order query method, and there is at least one successful order query based on these two first order query requests, then any one of the successful order query cases can be used as the criterion; or, if the merchant server sends a first order query request to the payment server simultaneously using both the MQ-based asynchronous order query method and the event center-based asynchronous order query method, and both of these first order query requests result in failed order queries, then the merchant server will be unable to determine the payment result for the target payment item.

[0131] For example, assume that the merchant server sends a first order query request to the payment server simultaneously using both the MQ-based asynchronous order query method and the event center-based asynchronous order query method, and receives a first order query response corresponding to the MQ-based asynchronous order query method. This first order query response indicates that the order query for the target payment item is successful, and the query result shows that the payment result for the target payment item is a successful payment; and the merchant server also receives a first order query response corresponding to the event center-based asynchronous order query method. This first order query response indicates that the order query for the target payment item is successful, and the query result shows that the payment result for the target payment item is a successful payment; based on this, the merchant server determines that the payment result for the target payment item is a successful payment.

[0132] Another example, assume that the merchant server sends a first order query request to the payment server simultaneously using both the MQ-based asynchronous order query method and the event center-based asynchronous order query method, and receives a first order query response corresponding to the MQ-based asynchronous order query method. This first order query response indicates that the order query for the target payment item fails; and the merchant server also receives a first order query response corresponding to the event center-based asynchronous order query method. This first order query response indicates that the order query for the target payment item is successful, and the query result shows that the payment result for the target payment item is a successful payment; based on this, the merchant server determines that the payment result for the target payment item is a successful payment.

[0133] Another example, assume that the merchant server sends a first order query request to the payment server simultaneously using both the MQ-based asynchronous order query method and the event center-based asynchronous order query method, and receives a first order query response corresponding to the MQ-based asynchronous order query method. This first order query response indicates that the order query for the target payment item fails; and the merchant server also receives a first order query response corresponding to the event center-based asynchronous order query method. This first order query response indicates that the order query for the target payment item fails; based on this, the merchant server is unable to determine the payment result for the target payment item.

[0134] Case 2: If the merchant server sends a first order query request to the payment server in an asynchronous order query manner based on MQ; when the order query fails in the asynchronous order query manner based on MQ, it sends a first order query request to the payment server in an asynchronous order query manner based on the event center, then the first order query response corresponding to the asynchronous order query manner based on MQ or the event center can be used as the basis.

[0135] For example, assume that the merchant server sends a first order query request to the payment server in an asynchronous order query manner based on MQ; when the order query fails in the asynchronous order query manner based on MQ, it sends a first order query request to the payment server in an asynchronous order query manner based on the event center. The first order query response corresponding to the asynchronous order query manner based on the event center indicates that the order query for the target payment item is successful, and the order query result shows that the payment result of the target payment item is successful; based on this, the merchant server determines that the payment result of the target payment item is successful.

[0136] Case 3: If the merchant server sends a first order query request to the payment server in an asynchronous order query manner based on the event center; when the order query fails in the asynchronous order query manner based on the event center, it sends a first order query request to the payment server in an asynchronous order query manner based on MQ, then the first order query response corresponding to the asynchronous order query manner based on MQ or the event center can be used as the basis.

[0137] For example, assume that the merchant server sends a first order query request to the payment server in an asynchronous order query manner based on the event center; when the order query fails in the asynchronous order query manner based on the event center, it sends a first order query request to the payment server in an asynchronous order query manner based on MQ. The first order query response corresponding to the asynchronous order query manner based on MQ indicates that the order query for the target payment item is successful, and the order query result shows that the payment result of the target payment item is successful; based on this, the merchant server determines that the payment result of the target payment item is successful.

[0138] The following combines Figure 3 to exemplarily elaborate on the asynchronous order query process provided in the first item above:

[0139] Figure 3 is a flowchart of the asynchronous order query process provided in an embodiment of the present application. As Figure 3 shown, this process includes:

[0140] S310: The terminal device corresponding to the payer sends a payment order request to the merchant server;

[0141] S320: The merchant server sends a payment order request to the payment server;

[0142] S330: The merchant server sends a payment order request to the third-party payment server;

[0143] The following will be described in conjunction with S310 to S330:

[0144] It should be understood that the payment order request is a payment order request for the target payment item. After the payer enters the payment amount on their corresponding terminal device, the terminal device can generate a payment order request for the target payment item.

[0145] It should be understood that as a merchant payment platform, the third-party payment server can generate a payment bill for the target payment item. Based on this, the payment order request ultimately needs to be sent to the third-party payment server.

[0146] S340: The merchant server sends a first order inquiry request for the target payment item to the payment server;

[0147] S350: The payment server sends the first order inquiry request to the third-party payment server;

[0148] S360: In response to the first order inquiry request, the third-party payment server conducts an order inquiry for the target payment item;

[0149] S370: The third-party payment server sends a first order inquiry response to the payment server;

[0150] S380: The payment server sends the first order inquiry response to the merchant server;

[0151] S390: The merchant server determines the payment result of the target payment item based on the first order inquiry response;

[0152] It is worth mentioning that after the merchant server sends a payment order request to the third-party payment server, it can send a first order inquiry request for the target payment item to the payment server. In other words, the payment order request sent by the merchant server to the third-party payment server can trigger it to send this first order inquiry request to the payment server.

[0153] It should be understood that S340 to S390 are the same as S210-A to S260-A. For the explanation of S340 to S390, reference can be made to the above text, and this application embodiment will not elaborate on it here.

[0154] It is worth mentioning that if the merchant server sends the first order inquiry request to the payment server using the asynchronous order inquiry method based on MQ and the asynchronous order inquiry method based on the event center, then it is equivalent to the merchant server being able to send the first order inquiry request to the payment server in two ways, thereby achieving order inquiry. Based on this, the success rate of asynchronous order inquiry can be improved, and thus it is possible to ensure that the payee can receive a payment success notification and conduct collection as much as possible, so as to improve the experience of the payer and the payee.

[0155] The following will be described in conjunction with S210-B and S220-B:

[0156] It should be understood that the payment result of the target payment item includes the following three cases:

[0157] Case 1: Payment is successful;

[0158] Case 2: The payment status is uncertain;

[0159] Case 3: Payment fails.

[0160] In some implementable ways, when the payment result is that the payment is successful, the payment server can send a payment success notification to the merchant server by at least one of the real-time notification method and the asynchronous notification method; when the payment result is that the payment status is uncertain, the payment server sends a payment success notification to the merchant server when processing the bill for the target payment item. When the payment result is that the payment fails, the payment server does not perform any processing or sends a payment failure notification to the terminal device.

[0161] In some implementable ways, the payment server can receive the payment result of the target payment item sent by the third-party payment server.

[0162] It should be understood that the payment success notification is used to notify the merchant server that the target payment item has been successfully paid.

[0163] The following will be described for Case 1 of the payment result:

[0164] It should be understood that when the payment result is that the payment is successful, the payment server can send a payment success notification to the merchant server by the real-time notification method; or, the payment server can send a payment success notification to the merchant server by the asynchronous notification method; or, the payment server can send a payment success notification to the merchant server by the real-time notification method and the asynchronous notification method.

[0165] In the embodiments of the present application, the payment server sending a payment success notification to the merchant server by the real-time notification method and the asynchronous notification method can be implemented by any of the following implementable ways, but not limited thereto:

[0166] Implementable Way 1: The payment server sends a payment success notification to the merchant server by the real-time notification method and the asynchronous notification method simultaneously.

[0167] In other words, the merchant server can send a payment success notification to the merchant server by the real-time notification method and the asynchronous notification method respectively, and these two notification methods are independent of each other.

[0168] Implementable approach 2: The payment server sends a payment success notification to the merchant server in real-time notification mode; when the real-time notification mode fails to send the payment success notification, the payment server sends the payment success notification to the merchant server in asynchronous notification mode.

[0169] Conversely, when the real-time notification mode successfully sends the payment success notification, the merchant server does not need to send the payment success notification to the merchant server in asynchronous notification mode.

[0170] It is worth mentioning that when the payment is successful, if the payment server sends the payment success notification to the merchant server in both real-time notification mode and asynchronous notification mode, it is equivalent to the payment server sending the payment success notification to the merchant server through two notification modes. Based on this, the success rate of sending the payment success notification can be improved, and then it is possible to ensure that the payee can receive the payment success notification and conduct collection as much as possible, so as to improve the experience of the payer and the payee.

[0171] In some implementable approaches, the above asynchronous notification mode can be an asynchronous notification mode based on MQ or an asynchronous notification mode based on the event center.

[0172] In some implementable approaches, if the payment server adopts an asynchronous notification mode based on MQ, the payment server can act as a producer, put the payment success notification into MQ, and the payment server can also act as a consumer to read the payment success notification in MQ and send the read payment success notification to the merchant server.

[0173] It should be understood that in this implementable approach, the payment server actively sends the payment success notification to the merchant server.

[0174] In some other implementable approaches, if the payment server adopts an asynchronous notification mode based on MQ, the payment server can act as a producer, put the payment success notification into MQ, and the merchant server can act as a consumer to read the payment success notification in MQ.

[0175] It should be understood that in this implementable approach, the merchant server acts as a message consumer, that is, a subscriber to obtain the payment success notification from the merchant server.

[0176] In some implementable approaches, if the payment server adopts an asynchronous notification mode based on the event center, the payment server can act as an event publisher, put the payment success notification into the event center, and the payment server can also act as an event subscriber to read the payment success notification in the event center and send the read payment success notification to the merchant server.

[0177] It should be understood that in this implementable manner, the payment server actively sends a payment success notification to the merchant server.

[0178] In some other implementable manners, if the payment server adopts an asynchronous notification method based on an event center, then the payment server can act as an event publisher, put the payment success notification into the event center, and the merchant server can act as an event subscriber to read the payment success notification in the event center.

[0179] It should be understood that in this implementable manner, the merchant server, as an event subscriber, obtains the payment success notification from the merchant server.

[0180] In some implementable manners, if the payment server successfully sends a payment success notification to the merchant server, then the payment server can indicate to the third-party payment server that the payment success notification has been successfully sent down, so that the third-party payment server does not need to use the third item mentioned below to send down the payment success notification, thereby achieving the purpose of saving communication resources.

[0181] In some implementable manners, if the payment server fails to send a payment success notification to the merchant server, then the payment server can indicate to the third-party payment server that the payment success notification has been sent down unsuccessfully, so that the third-party payment server can use the third item mentioned below to send down the payment success notification, thereby achieving the purpose of compensating for the sending down of the payment success notification.

[0182] The following elaborates on the second case of the payment result:

[0183] In some implementable manners, before sending a payment success notification to the merchant server in the case of processing a bill for a target payment item, the payment processing method further includes at least one of the following:

[0184] (1) The payment server sends an indication message for indicating that the payment status is uncertain to the terminal device that initiated the target payment item; and receives a re-payment request for the target payment item sent by the terminal device; when the re-payment request is the first payment request for the target payment item received by the payment server, sends the re-payment request to the third-party payment server and receives a payment response sent by the third-party payment server; when the re-payment request is not the first payment request for the target payment item received by the payment server, sends a second bill inquiry request for the target payment item to the third-party payment server and receives a second bill inquiry response sent by the third-party payment server;

[0185] (2) The payment server sends a bill closing or bill supplementing request for the target payment item to the third-party payment server; and receives a bill closing or bill supplementing response sent by the third-party payment server.

[0186] Correspondingly, when processing the bill for the target payment item, a payment success notification is sent to the merchant server, including at least one of the following:

[0187] When it is determined that the target payment item has been successfully paid based on the payment response or the second bill inquiry response, a payment success notification is sent to the merchant server;

[0188] When it is determined that the target payment item has been successfully paid based on the bill closing or bill supplement response, a payment success notification is sent to the merchant server.

[0189] The following elaborates on point (1):

[0190] It should be understood that the terminal device initiating the target payment item is the terminal device corresponding to the above-mentioned payer.

[0191] It should be understood that since the payment server indicates that the payment status of the target payment item is uncertain to the terminal device, the terminal device can initiate a re-payment for the target payment item. For the payment server, it may not have received a payment request for the target payment item before, or it has received a payment request for the target payment item before. Based on this, the payment server can detect whether the re-payment request is the first payment request for the target payment item received by the payment server. When the re-payment request is the first payment request for the target payment item received by the payment server, based on this, the payment server sends the re-payment request to the third-party payment server and receives the payment response sent by the third-party payment server; when the re-payment request is not the first payment request for the target payment item received by the payment server, the payment server sends a second bill inquiry request for the target payment item to the third-party payment server and receives the second bill inquiry response sent by the third-party payment server.

[0192] In some implementation manners, the payment response includes the following situations:

[0193] Situation 1: The payment for the target payment item is successful;

[0194] Situation 2: The payment for the target payment item is uncertain;

[0195] Situation 3: The payment for the target payment item fails.

[0196] In some realizable manners, the second bill inquiry response includes the following situations:

[0197] Situation 1: The bill inquiry for the target payment item is successful, and the inquiry result indicates that the payment result of the target payment item is successful;

[0198] In Case 2, the order inquiry for the target payment item is successful, and the inquiry result indicates that the payment result of the target payment item is of uncertain payment status;

[0199] In Case 3, the order inquiry for the target payment item is successful, and the inquiry result indicates that the payment result of the target payment item is payment failure;

[0200] In Case 4, the order inquiry for the target payment item fails.

[0201] In some implementable ways, the terminal device that initiates the target payment item can send a re-payment request to the payment server under the trigger of the above indication message. Based on this, when the payment response or the second order inquiry response indicates that the payment result is payment success, the payment server sends a payment success notification to the merchant server.

[0202] In some implementable ways, the terminal device that initiates the target payment item can send a re-payment request to the payment server under the trigger of the above indication message. Based on this, when the payment response or the second order inquiry response indicates payment failure for the target payment item, the payment server can do nothing, or the payment server can send a payment failure notification to the terminal device.

[0203] In some implementable ways, the terminal device that initiates the target payment item can send a re-payment request to the payment server under the trigger of the above indication message. Based on this, when the payment response or the second order inquiry response indicates that the payment status of the target payment item is uncertain, the payment server can do nothing, or report an error to the terminal device, causing the payer to initiate the payment again.

[0204] In some implementable ways, the terminal device that initiates the target payment item can send multiple re-payment requests to the payment server under the trigger of the above indication message. Based on this, when there is at least one payment response or second order inquiry response indicating that the payment result is payment success, the payment server sends a payment success notification to the merchant server.

[0205] In some implementable ways, the terminal device that initiates the target payment item can send multiple re-payment requests to the payment server under the trigger of the above indication message. Based on this, when there is no payment response or second order inquiry response indicating that the payment result is payment success, the payment server can do nothing, or report an error to the terminal device, causing the payer to initiate the payment again.

[0206] In some implementable ways, the terminal device periodically sends a re-payment request to the payment server. For example, the terminal device can send a re-payment request to the payment server every 5 seconds, where the upper limit of the number of re-payment requests can be 3 times.

[0207] In some implementable manners, when it is determined that the target payment item has been successfully paid based on the payment response or the second order inquiry response, the payment server sends a payment success notification to the merchant server by at least one of a real-time notification method and an asynchronous notification method.

[0208] It should be understood that for the specific method of the payment server sending a payment success notification to the merchant server by at least one of a real-time notification method and an asynchronous notification method, reference can be made to the specific method of the payment server sending a payment success notification to the merchant server by at least one of a real-time notification method and an asynchronous notification method when the payment is successful. This application embodiment will not elaborate on this any further.

[0209] The following elaborates on point (2):

[0210] It should be understood that the order closing or order replenishment request for the target payment item is used to trigger the third-party payment server to replenish the order or inquire about the order. For example, when the third-party payment server receives an order closing request, the third-party payment server first inquires about the order. If the bill of the target payment item can be found, then the payment result can be determined based on the order inquiry situation, such as payment success or payment failure. If the bill of the target payment item cannot be found, then the target payment item can be replenished first, and then the order can be inquired about, and the payment result can be determined based on the order inquiry situation.

[0211] In some implementable manners, the order closing or order replenishment response includes the following situations:

[0212] Situation 1: The order closing or order replenishment for the target payment item is successful, and the triggered order inquiry result indicates that the payment result of the target payment item is payment success;

[0213] Situation 2: The order closing or order replenishment for the target payment item is successful, and the triggered order inquiry result indicates that the payment result of the target payment item is an uncertain payment status;

[0214] Situation 3: The order closing or order replenishment for the target payment item is successful, and the triggered order inquiry result indicates that the payment result of the target payment item is payment failure;

[0215] Situation 4: The order closing or order replenishment for the target payment item fails.

[0216] In some implementable manners, the payment server can send an order closing or order replenishment request for the target payment item to the third-party payment server once. Based on this, when the order closing or order replenishment response indicates that the payment result is payment success, the payment server sends a payment success notification to the merchant server.

[0217] In some implementable manners, the payment server may send a single closing or replenishing order request for a target payment item to a third-party payment server. Based on this, when the closing or replenishing order response indicates that the payment for the target payment item fails, the payment server may not perform any processing, or the payment server may send a payment failure notice to the terminal device that initiated the target payment item.

[0218] In some implementable manners, the payment server may send a single closing or replenishing order request for a target payment item to a third-party payment server. Based on this, when the closing or replenishing order response indicates that the payment status for the target payment item is uncertain, the payment server may not perform any processing, or report an error to the terminal device, causing the payer to initiate the payment again.

[0219] In some implementable manners, the payment server may send multiple closing or replenishing order requests for a target payment item to a third-party payment server. Based on this, when at least one closing or replenishing order response indicates that the payment result is a successful payment, the payment server sends a payment success notice to the merchant server.

[0220] In some implementable manners, the payment server may send multiple closing or replenishing order requests for a target payment item to a third-party payment server. Based on this, when no closing or replenishing order response indicates that the payment result is a successful payment, the payment server may not perform any processing, or report an error to the terminal device, causing the payer to initiate the payment again.

[0221] In some implementable manners, the payment server may periodically send multiple closing or replenishing order requests for a target payment item to a third-party payment server. For example, the payment server may send a closing or replenishing order request to the third-party payment server every 5 seconds, where the upper limit of the number of such closing or replenishing order requests may be 3 times.

[0222] In some implementable manners, when it is determined that the payment for the target payment item is successfully made based on the payment response or the second order inquiry response, the payment server sends a payment success notice to the merchant server by using at least one of a real-time notification method and an asynchronous notification method.

[0223] In some implementable manners, the payment server may send a closing or replenishing order request for a target payment item to a third-party payment server by using an asynchronous closing or replenishing order method.

[0224] In some implementable manners, the asynchronous closing or replenishing order method may be a closing or replenishing order method based on MQ, or may be a closing or replenishing order method based on an event center. The embodiments of the present application do not limit this.

[0225] In some implementable ways, when the payment server sends a closing or replenishing order request for a target payment item to a third-party payment server in an MQ-based closing or replenishing order manner, the payment server can act as a message producer to put the closing or replenishing order request into MQ. The payment server can also act as a consumer to read the closing or replenishing order request in MQ and send the closing or replenishing order request to the third-party payment server.

[0226] It should be understood that in this implementable way, the payment server actively sends a closing or replenishing order request to the third-party payment server.

[0227] In some implementable ways, when the payment server sends a closing or replenishing order request for a target payment item to a third-party payment server in an MQ-based closing or replenishing order manner, the payment server can act as a message producer to put the closing or replenishing order request into MQ, and the third-party payment server can act as a consumer to read the closing or replenishing order request in MQ.

[0228] It should be understood that in this implementable way, the third-party payment server acts as a message consumer, that is, a subscriber to obtain the closing or replenishing order request from the payment server.

[0229] In some implementable ways, when the payment server sends a closing or replenishing order request for a target payment item to a third-party payment server in an event center-based closing or replenishing order manner, the payment server can act as an event publisher to publish the closing or replenishing order request to an event center, and the payment server can also act as an event subscriber to subscribe to the event and send the closing or replenishing order request to the third-party payment server.

[0230] It should be understood that in this implementable way, the payment server actively sends a closing or replenishing order request to the third-party payment server.

[0231] In some implementable ways, when the payment server sends a closing or replenishing order request for a target payment item to a third-party payment server in an event center-based closing or replenishing order manner, the payment server can act as an event publisher to publish the closing or replenishing order request to an event center, and the third-party payment server can act as an event subscriber to subscribe to the event to obtain the closing or replenishing order request.

[0232] It should be understood that in this implementable way, the third-party payment server acts as an event subscriber to obtain the closing or replenishing order request from the payment server.

[0233] It is worth mentioning that when the payment status is uncertain, the terminal device can initiate the payment again so that the merchant server can obtain the payment success notification, and the payment server uses the order closing or order supplementing method so that the merchant server can obtain the payment success notification. Based on this, the sending success rate of the payment success notification can be improved, and then it is possible to ensure that the payee can receive the payment success notification and conduct the collection as much as possible, so as to improve the experience of the payer and the payee.

[0234] The following will Figure 4 exemplarily elaborate on the process of issuing the payment success notification provided in the second item above:

[0235] Figure 4 is the flowchart of the process of issuing the payment success notification provided by the embodiment of the present application. As Figure 4 shown, this process includes:

[0236] S401: The terminal device corresponding to the payer sends a payment request for the target payment item to the payment server;

[0237] S402: The payment server sends the payment request to the third-party payment server;

[0238] S403: The third-party payment server sends the payment result corresponding to the payment request to the payment server;

[0239] The following will be elaborated in combination with S401 to S403:

[0240] It should be understood that after the payer selects a payment method on the corresponding terminal device and enters the password to initiate the payment, the terminal device can generate a payment request for the target payment item.

[0241] It should be understood that as the merchant payment platform, the third-party payment server generates a payment result in response to the payment request. Based on this, the payment order request ultimately needs to be sent to the third-party payment server.

[0242] S404: When the payment result is a payment success, the payment server can send a payment success notification to the merchant server by at least one of the real-time notification method and the asynchronous notification method;

[0243] It should be understood that the specific method for the payment server to send a payment success notification to the merchant server by at least one of the real-time notification method and the asynchronous notification method can refer to the above text, and the embodiments of the present application will not elaborate on this again.

[0244] S405-1a: When the payment status is uncertain, the payment server sends an indication message for indicating that the payment status is uncertain to the terminal device that initiated the target payment item;

[0245] S405-2a: The terminal device sends a re-payment request for the target payment item to the payment server;

[0246] S405-3a: When the re-payment request is the first payment request for the target payment item received by the payment server, the payment server sends the re-payment request to the third-party payment server;

[0247] S405-4a: The third-party payment server sends a payment response to the payment server;

[0248] S405-5a: When the re-payment request is not the first payment request for the target payment item received by the payment server, the payment server sends a second inquiry request for the target payment item to the third-party payment server;

[0249] S405-6a: The third-party payment server sends a second inquiry response to the payment server;

[0250] S405-7a: When it is determined that the payment for the target payment item has been successfully made based on the payment response or the second inquiry response, the payment server sends a payment success notification to the merchant server;

[0251] It should be understood that S405-1a to S405-7a are payment success notifications issued in the case where the terminal device re-initiates a payment. For the explanations of each step in this process, reference can be made to the above text, and the embodiments of this application will not elaborate on this again.

[0252] S405-1b: When the payment status is uncertain, the payment server sends a closing or replenishing order request for the target payment item to the third-party payment server;

[0253] S405-2b: The third-party payment server sends a closing or replenishing order response to the payment server;

[0254] S405-3b: When it is determined that the payment for the target payment item has been successfully made based on the closing or replenishing order response, the payment server sends a payment success notification to the merchant server;

[0255] It should be understood that S405-1b to S405-3b are payment success notifications issued in the case of closing or replenishing an order. For the explanations of each step in this process, reference can be made to the above text, and the embodiments of this application will not elaborate on this again.

[0256] S406: When the payment result is payment failure, the payment server sends a payment failure notification to the terminal device.

[0257] The following will be elaborated in combination with S210-C and S220-C:

[0258] It should be understood that the distribution link for the payment success notification provided in the third item is the currently adopted distribution link, which can form a multi-link with the distribution links provided in the first item and / or the second item, or it can be used as a compensation link for the distribution link provided in the first item or the second item to ensure the success rate of distributing the payment success notification.

[0259] An embodiment of the present application provides a payment processing method, which includes at least two of the following: (1) The merchant server sends a first order query request for a target payment item to the payment server corresponding to the instant messaging client; and receives the first order query response sent by the payment server; determines the payment result of the target payment item based on the first order query response; (2) The merchant server receives the payment success notification generated and sent by the payment server based on the payment result of the target payment item; (3) The merchant server receives the payment success notification forwarded by the payment server from the third-party payment server. Since the merchant server can obtain the payment success notification through multiple links, the probability of successfully receiving the payment success notification can be increased, and thus it is possible to ensure that the payee can receive the payment success notification and conduct collection as much as possible, so as to improve the experience of the payer and the payee.

[0260] In addition, through the payment processing method provided by the embodiment of the present application, the availability of 5 nines for merchant notifications can be achieved, ensuring the stability and smoothness of merchant notifications.

[0261] The preferred embodiments of the present application have been described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the scope of the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application, and these simple modifications all fall within the protection scope of the present application. For example, in the various specific technical features described in the above specific embodiments, they can be combined in any appropriate manner without contradiction. To avoid unnecessary repetition, the present application will not separately describe various possible combination methods. Again, any combination can be made between various different embodiments of the present application as long as it does not violate the idea of the present application, and it should also be regarded as the content disclosed by the present application.

[0262] It should also be understood that in various method embodiments of the present application, the magnitudes of the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0263] The method provided by the embodiment of the present application has been described above. Next, the payment processing device provided by the embodiment of the present application will be described.

[0264] Figure 5 Schematic diagram of a payment processing device 500 provided for an embodiment of the present application, asFigure 5 As shown, the device 500 includes: a communication module 510 and a processing module 520;

[0265] The communication module 510 is configured to: send a first order query request for a target payment item to the payment server corresponding to the instant messaging client; and receive a first order query response sent by the payment server; the processing module 520 is configured to determine the payment result of the target payment item based on the first order query response; the communication module 510 is further configured to receive a payment success notification generated and sent by the payment server based on the payment result of the target payment item; or,

[0266] The communication module 510 is configured to: send a first order query request for a target payment item to the payment server corresponding to the instant messaging client; and receive a first order query response sent by the payment server; the processing module 520 is configured to determine the payment result of the target payment item based on the first order query response; the communication module 510 is further configured to receive a payment success notification forwarded by the payment server from a third-party payment server; or,

[0267] The communication module 510 is configured to: receive a payment success notification generated and sent by the payment server based on the payment result of the target payment item; receive a payment success notification forwarded by the payment server from a third-party payment server; or,

[0268] The communication module 510 is configured to: send a first order query request for a target payment item to the payment server corresponding to the instant messaging client; and receive a first order query response sent by the payment server; the processing module 520 is configured to determine the payment result of the target payment item based on the first order query response; the communication module 510 is further configured to: receive a payment success notification generated and sent by the payment server based on the payment result of the target payment item; receive a payment success notification forwarded by the payment server from a third-party payment server.

[0269] In some implementable ways, the communication module 510 is specifically configured to: send the first order query request to the payment server by using at least one of an asynchronous order query method based on MQ and an asynchronous order query method based on an event center.

[0270] In some implementable ways, the communication module 510 is specifically configured to: send the first order query request to the payment server simultaneously by using an asynchronous order query method based on MQ and an asynchronous order query method based on an event center.

[0271] In some implementable ways, the communication module 510 is specifically configured to: send the first order query request to the payment server by using an asynchronous order query method based on MQ; when the order query fails by using the asynchronous order query method based on MQ, send the first order query request to the payment server by using an asynchronous order query method based on an event center.

[0272] In some implementable manners, the communication module 510 is specifically configured to: send a first order query request to the payment server by using an asynchronous order query method based on an event center; when the order query fails by using the asynchronous order query method based on the event center, send the first order query request to the payment server by using an asynchronous order query method based on MQ.

[0273] In some implementable manners, the communication module 510 is specifically configured to: receive a payment success notification sent by the payment server by using at least one of a real-time notification method and an asynchronous notification method when the payment result is payment success; receive a payment success notification sent by the payment server when the payment result is payment status uncertain and the bill processing is performed on the target payment item.

[0274] It should be understood that the device embodiments and the method embodiments can correspond to each other, and similar descriptions can refer to the method embodiments. To avoid repetition, they will not be elaborated here. Specifically, Figure 5 The illustrated device can execute the method embodiments corresponding to the merchant server, and the foregoing and other operations and / or functions of each module in the device respectively implement the corresponding processes in the foregoing various methods. For the sake of brevity, they will not be elaborated here.

[0275] In the foregoing, the device of the embodiments of the present application has been described from the perspective of functional modules. It should be understood that the functional module can be implemented in the form of hardware, can also be implemented by instructions in the form of software, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the embodiments of the present application can be completed by the integrated logic circuit in the hardware in the processor and / or instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by a combination of the hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps in the foregoing method embodiments.

[0276] Figure 6 FIG. is a schematic diagram of a payment processing device 600 provided by an embodiment of the present application. As Figure 6 shown, the device 600 includes: a communication module 610 and a processing module 620;

[0277] The communication module 610 is configured to: receive a first order inquiry request for a target payment item sent by a merchant server corresponding to an instant messaging client; and send the first order inquiry request to a third-party payment server; receive a first order inquiry response sent by the third-party server; and send the first order inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order inquiry response; the processing module 620 is configured to generate a payment success notification based on the payment result of the target payment item, and the communication module 610 is further configured to send the payment success notification to the merchant server; or,

[0278] The communication module 610 is configured to: receive a first order inquiry request for a target payment item sent by a merchant server corresponding to an instant messaging client; and send the first order inquiry request to a third-party payment server; receive a first order inquiry response sent by the third-party server; and send the first order inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order inquiry response; receive a payment success notification from the third-party payment server; and forward the payment success notification to the merchant server; or,

[0279] The processing module 620 is configured to generate a payment success notification based on the payment result of the target payment item, and the communication module 610 is configured to: send the payment success notification to the merchant server; receive a payment success notification from the third-party payment server; and forward the payment success notification to the merchant server; or,

[0280] The communication module 610 is configured to: receive a first order inquiry request for a target payment item sent by a merchant server corresponding to an instant messaging client; and send the first order inquiry request to a third-party payment server; receive a first order inquiry response sent by the third-party server; and send the first order inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order inquiry response; the processing module 620 is configured to generate a payment success notification based on the payment result of the target payment item, and the communication module 610 is further configured to: send the payment success notification to the merchant server; receive a payment success notification from the third-party payment server; and forward the payment success notification to the merchant server.

[0281] In some implementable manners, the communication module 610 is specifically configured to: receive the first order inquiry request sent by the merchant server by using at least one of an asynchronous order inquiry manner based on MQ and an asynchronous order inquiry manner based on an event center.

[0282] In some implementable manners, the communication module 610 is specifically configured to: when the payment result is payment success, send the payment success notification to the merchant server by using at least one of a real-time notification manner and an asynchronous notification manner; when the payment result is that the payment status is uncertain, send the payment success notification to the merchant server in the case of performing bill processing on the target payment item.

[0283] In some implementable ways, the communication module 610 is specifically configured to: send a payment success notification to the merchant server by using both a real-time notification method and an asynchronous notification method.

[0284] In some implementable ways, the communication module 610 is specifically configured to: send a payment success notification to the merchant server by using a real-time notification method; when the sending of the payment success notification fails by using the real-time notification method, send a payment success notification to the merchant server by using an asynchronous notification method.

[0285] In some implementable ways, the communication module 610 is further configured to perform at least one of the following before sending a payment success notification to the merchant server in the case of performing bill processing for a target payment item:

[0286] Send an indication message for indicating an uncertain payment status to the terminal device that initiated the target payment item; and receive a re-payment request for the target payment item sent by the terminal device; when the re-payment request is the first payment request for the target payment item received by the payment server, send the re-payment request to the third-party payment server and receive a payment response sent by the third-party payment server; when the re-payment request is not the first payment request for the target payment item received by the payment server, send a second order inquiry request for the target payment item to the third-party payment server and receive a second order inquiry response sent by the third-party payment server;

[0287] Send a close order or reissue order request for the target payment item to the third-party payment server; receive a close order or reissue order response sent by the third-party payment server.

[0288] In some implementable ways, the communication module 610 is specifically configured to perform at least one of the following:

[0289] When it is determined based on the payment response or the second order inquiry response that the target payment item has been successfully paid, send a payment success notification to the merchant server;

[0290] When it is determined based on the close order or reissue order response that the target payment item has been successfully paid, send a payment success notification to the merchant server.

[0291] In some implementable ways, the communication module 610 is specifically configured to: when it is determined based on the payment response or the second order inquiry response that the target payment item has been successfully paid, send a payment success notification to the merchant server by using at least one of a real-time notification method and an asynchronous notification method.

[0292] In some implementable ways, the communication module 610 is specifically configured to: send a close order or reissue order request for the target payment item to the third-party payment server by using an asynchronous close order or reissue order method.

[0293] It should be understood that the device embodiments and the method embodiments can correspond to each other, and similar descriptions can refer to the method embodiments. To avoid repetition, they will not be elaborated here. Specifically, Figure 6 The device shown can execute the corresponding method embodiments of the above payment server, and the foregoing and other operations and / or functions of each module in the device respectively implement the corresponding processes in the above respective methods. For the sake of brevity, they will not be elaborated here.

[0294] In the foregoing, the device of the embodiments of the present application has been described from the perspective of functional modules. It should be understood that the functional modules can be implemented in the form of hardware, can also be implemented by instructions in the form of software, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the embodiments of the present application can be completed by the integrated logic circuit in the hardware in the processor and / or instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by a combination of the hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps in the above method embodiments.

[0295] Figure 7 is a schematic block diagram of an electronic device provided by the embodiments of the present application. The electronic device can be the above merchant server or payment server.

[0296] As Figure 7 shown, the electronic device may include:

[0297] A memory 710 and a processor 720. The memory 710 is used to store a computer program and transmit the program code to the processor 720. In other words, the processor 720 can call and run the computer program from the memory 710 to implement the method in the embodiments of the present application.

[0298] For example, the processor 720 can be used to execute the above method embodiments according to the instructions in the computer program.

[0299] In some embodiments of the present application, the processor 720 may include but is not limited to:

[0300] General-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.

[0301] In some embodiments of the present application, the memory 710 includes, but is not limited to:

[0302] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synch link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0303] In some embodiments of the present application, the computer program may be divided into one or more modules, and the one or more modules are stored in the memory 710 and executed by the processor 720 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0304] As Figure 7 shown, the electronic device may further include:

[0305] A transceiver 730, which can be connected to the processor 720 or the memory 710.

[0306] Among them, the processor 720 can control the transceiver 730 to communicate with other devices. Specifically, it can send information or data to other devices, or receive information or data sent by other devices. The transceiver 730 can include a transmitter and a receiver. The transceiver 730 can further include an antenna, and the number of antennas can be one or more.

[0307] It should be understood that each component in the electronic device is connected through a bus system. Among them, the bus system includes not only a data bus, but also a power bus, a control bus, and a status signal bus.

[0308] This application also provides a computer storage medium, on which a computer program is stored. When the computer program is executed by the computer, the computer can execute the method in the above method embodiment. Or rather, this application embodiment also provides a computer program product containing instructions. When the instructions are executed by the computer, the computer executes the method in the above method embodiment.

[0309] When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function according to this application embodiment is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a server, or a data center to another website, computer, server, or data center in a wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that the computer can access, or a data storage device such as a server or a data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0310] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of this application.

[0311] In several embodiments provided by this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or modules can be in electrical, mechanical, or other forms.

[0312] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they can be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, in each embodiment of this application, the functional modules can be integrated into one processing module, or each module can exist physically alone, or two or more modules can be integrated into one module.

[0313] The above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application, and all of them should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A payment processing method, characterized in that, The method is applied to a merchant server corresponding to an instant messaging client, and the method includes at least two of the following: Send a first order inquiry request for a target payment item to a payment server corresponding to the instant messaging client; and receive a first order inquiry response sent by the payment server; determine the payment result of the target payment item based on the first order inquiry response; Receive a payment success notification generated and sent by the payment server based on the payment result of the target payment item; Receive the payment success notification forwarded by the payment server from a third-party payment server.

2. The method according to claim 1, wherein The sending of the first order inquiry request for a target payment item to a payment server corresponding to the instant messaging client includes: Send the first order inquiry request to the payment server by using at least one of an asynchronous order inquiry method based on a message queue MQ and an asynchronous order inquiry method based on an event center.

3. The method according to claim 2, characterized in that The sending of the first order inquiry request to the payment server by using at least one of an asynchronous order inquiry method based on a message queue MQ and an asynchronous order inquiry method based on an event center includes: Send the first order inquiry request to the payment server by using the asynchronous order inquiry method based on MQ and the asynchronous order inquiry method based on the event center simultaneously.

4. The method according to claim 2, wherein The sending of the first order inquiry request to the payment server by using at least one of an asynchronous order inquiry method based on a message queue MQ and an asynchronous order inquiry method based on an event center includes: Send the first order inquiry request to the payment server by using the asynchronous order inquiry method based on MQ; When the order inquiry fails by using the asynchronous order inquiry method based on MQ, send the first order inquiry request to the payment server by using the asynchronous order inquiry method based on the event center.

5. The method according to claim 2, characterized in that, The sending of the first order inquiry request to the payment server by using at least one of an asynchronous order inquiry method based on a message queue MQ and an asynchronous order inquiry method based on an event center includes: Send the first order inquiry request to the payment server by using the asynchronous order inquiry method based on the event center; When the order inquiry fails by using the asynchronous order inquiry method based on the event center, send the first order inquiry request to the payment server by using the asynchronous order inquiry method based on MQ.

6. The method according to any one of claims 1-5, characterized in that The receiving of the payment success notification sent by the payment server based on the payment result of the target payment item includes: Receive the payment success notification sent by the payment server by using at least one of a real-time notification method and an asynchronous notification method when the payment result is a payment success; Receive the payment success notification sent by the payment server when the payment result is an uncertain payment status and when the bill for the target payment item is being processed.

7. A payment processing method, characterized in that, The method is applied to a payment server corresponding to an instant messaging client, and the method includes at least two of the following: Receive a first order inquiry request for a target payment item sent by a merchant server corresponding to the instant messaging client; and send the first order inquiry request to a third-party payment server; Receive the first order inquiry response sent by the third-party server; and send the first order inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order inquiry response; Generate a payment success notification based on the payment result of the target payment item, and send the payment success notification to the merchant server; Receive the payment success notification from the third-party payment server; and forward the payment success notification to the merchant server.

8. The method according to claim 7, wherein The receiving the first order inquiry request for the target payment item sent by the merchant server corresponding to the instant messaging client includes: Receive the first order inquiry request sent by the merchant server by using at least one of the asynchronous order inquiry method based on MQ and the asynchronous order inquiry method based on the event center.

9. The method according to claim 7 or 8, characterized in that, The sending the payment success notification to the merchant server based on the payment result of the target payment item includes: When the payment result is payment success, send the payment success notification to the merchant server by using at least one of the real-time notification method and the asynchronous notification method; When the payment result is that the payment status is uncertain, send the payment success notification to the merchant server in the case of processing the bill for the target payment item.

10. The method according to claim 9, wherein The sending the payment success notification to the merchant server by using at least one of the real-time notification method and the asynchronous notification method includes: Send the payment success notification to the merchant server by using the real-time notification method and the asynchronous notification method at the same time.

11. The method according to claim 9, characterized in that, The sending the payment success notification to the merchant server by using at least one of the real-time notification method and the asynchronous notification method includes: Send the payment success notification to the merchant server by using the real-time notification method; When the sending of the payment success notification fails by using the real-time notification method, send the payment success notification to the merchant server by using the asynchronous notification method.

12. The method according to claim 9, characterized in that, Before sending the payment success notification to the merchant server in the case of processing the bill for the target payment item, the method further includes at least one of the following: Send an indication message for indicating that the payment status is uncertain to the terminal device that initiated the target payment item; and receive a re-payment request for the target payment item sent by the terminal device; when the re-payment request is the first payment request for the target payment item received by the payment server, send the re-payment request to the third-party payment server, and receive a payment response sent by the third-party payment server; when the re-payment request is not the first payment request for the target payment item received by the payment server, send a second order inquiry request for the target payment item to the third-party payment server, and receive a second order inquiry response sent by the third-party payment server; Send a close order or reissue order request for the target payment item to the third-party payment server; receive a close order or reissue order response sent by the third-party payment server.

13. The method according to claim 12, characterized in that, Sending the payment success notice to the merchant server in the case of processing the bill for the target payment item includes at least one of the following: When it is determined that the target payment item has been successfully paid based on the payment response or the second bill inquiry response, sending the payment success notice to the merchant server; When it is determined that the target payment item has been successfully paid based on the closing bill or supplementary bill response, sending the payment success notice to the merchant server.

14. The method according to claim 13, characterized in that, Sending the payment success notice to the merchant server when it is determined that the target payment item has been successfully paid based on the payment response or the second bill inquiry response includes: When it is determined that the target payment item has been successfully paid based on the payment response or the second bill inquiry response, sending the payment success notice to the merchant server by using at least one of the real-time notification method and the asynchronous notification method.

15. The method according to claim 12, characterized in that Sending a closing bill or supplementary bill request for the target payment item to the third-party payment server includes: Sending a closing bill or supplementary bill request for the target payment item to the third-party payment server by using the asynchronous closing bill or supplementary bill method.

16. A payment processing device, characterized in that, Includes: A communication module and a processing module; The communication module is configured to: send a first bill inquiry request for the target payment item to the payment server corresponding to the instant messaging client; and receive the first bill inquiry response sent by the payment server; the processing module is configured to determine the payment result of the target payment item based on the first bill inquiry response; the communication module is further configured to receive the payment success notice generated and sent by the payment server based on the payment result of the target payment item; or, The communication module is configured to: send a first bill inquiry request for the target payment item to the payment server corresponding to the instant messaging client; and receive the first bill inquiry response sent by the payment server; the processing module is configured to determine the payment result of the target payment item based on the first bill inquiry response; the communication module is further configured to receive the payment success notice forwarded by the payment server from the third-party payment server; or, The communication module is configured to: receive the payment success notice generated and sent by the payment server based on the payment result of the target payment item; receive the payment success notice forwarded by the payment server from the third-party payment server; or, The communication module is configured to: send a first bill inquiry request for the target payment item to the payment server corresponding to the instant messaging client; and receive the first bill inquiry response sent by the payment server; the processing module is configured to determine the payment result of the target payment item based on the first bill inquiry response; the communication module is further configured to: receive the payment success notice generated and sent by the payment server based on the payment result of the target payment item; receive the payment success notice forwarded by the payment server from the third-party payment server.

17. A payment processing device, characterized in that, Includes: A communication module and a processing module; The communication module is configured to: receive a first bill inquiry request for the target payment item sent by the merchant server corresponding to the instant messaging client And send the first order inquiry request to a third-party payment server; Receive the first order inquiry response sent by the third-party server; and send the first order inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order inquiry response; the processing module is used to generate a payment success notification based on the payment result of the target payment item, and the communication module is further used to send the payment success notification to the merchant server; or, The communication module is used to: receive the first order inquiry request for a target payment item sent by the merchant server corresponding to the instant messaging client; and send the first order inquiry request to a third-party payment server; Receive the first order inquiry response sent by the third-party server; and send the first order inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order inquiry response; receive the payment success notification from the third-party payment server; and forward the payment success notification to the merchant server; or, The processing module is used to generate a payment success notification based on the payment result of the target payment item, and the communication module is used to: send the payment success notification to the merchant server; receive the payment success notification from the third-party payment server; and forward the payment success notification to the merchant server; or, The communication module is used to: receive the first order inquiry request for a target payment item sent by the merchant server corresponding to the instant messaging client; and send the first order inquiry request to a third-party payment server; Receive the first order inquiry response sent by the third-party server; and send the first order inquiry response to the merchant server, so that the merchant server determines the payment result of the target payment item based on the first order inquiry response; the processing module is used to generate a payment success notification based on the payment result of the target payment item, and the communication module is further used to: send the payment success notification to the merchant server; receive the payment success notification from the third-party payment server; and forward the payment success notification to the merchant server.

18. An electronic device, characterized in that, Comprising: A processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 15.

19. A computer-readable storage medium, characterized in that, For storing a computer program, the computer program causes a computer to execute the method according to any one of claims 1 to 15.

Images