CN111078433B - Merchant notification sending method and device and electronic equipment - Google Patents
Merchant notification sending method and device and electronic equipment Download PDFInfo
- Publication number
- CN111078433B CN111078433B CN201911272746.7A CN201911272746A CN111078433B CN 111078433 B CN111078433 B CN 111078433B CN 201911272746 A CN201911272746 A CN 201911272746A CN 111078433 B CN111078433 B CN 111078433B
- Authority
- CN
- China
- Prior art keywords
- merchant
- notification
- failure
- merchant notification
- merchant server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/085—Payment architectures involving remote charge determination or related payment systems
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/541—Client-server
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/544—Remote
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Software Systems (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a method and a device for sending merchant notification and electronic equipment, which are applied to the technical field of computers, wherein the method comprises the following steps: when the sending of the merchant notification fails, judging whether the merchant notification can be repeatedly reachable (namely, the repeatedly sent merchant notification can be successfully received by the merchant server), if the retransmission of the merchant notification is not reachable, not forwarding the merchant notification, and after the problem of failure is solved, retransmitting the merchant notification, thereby avoiding the resource waste caused by repeatedly forwarding the merchant notification under the condition of repeatedly unreachable.
Description
Technical Field
The application relates to the technical field of computers, in particular to a method and a device for sending merchant notification and electronic equipment.
Background
In China today, the traditional payment mode by physical entities such as cash, notes and the like is gradually replaced by an online payment mode, and a digital payment mode based on internet communication becomes a mainstream payment mode. The online payment transaction comprises three related parties, namely an individual client, a merchant, a payment platform for providing payment service, a third party payment mechanism such as WeChat payment treasures, a platform for providing payment service for banks and Union, and the like. In the payment transaction, after the individual client finishes online payment, the payment platform sends a merchant notification, namely order information, payment state and the like, to the merchant, and the merchant server can update the client order state after receiving the notification information of the payment platform.
The merchant notification may fail to be sent for various reasons, and the merchant notification is resent after the merchant notification is sent in the prior art, however, when the resending of the merchant notification still fails, the payment platform cannot locate and repair the problem in time, which results in a large number of single accounts.
Disclosure of Invention
The application provides a method, a device and electronic equipment for sending merchant notification, which are used for avoiding resource waste caused by repeated forwarding of merchant notification under the condition that repeated forwarding is not available, and the application adopts the following technical scheme:
in a first aspect, a method for sending a merchant notification is provided, applied to a payment platform, the method comprising,
Sending a merchant notification to a merchant server, receiving the merchant notification, sending the merchant notification to the merchant server, and receiving a network return code after the merchant notification is sent to the merchant server;
judging and receiving whether the network return code after the merchant notification is sent to the merchant server is a notification failure code or a notification success code, if the network return code after the merchant notification is received and sent to the merchant server is the notification failure code, determining and receiving whether the network return code merchant notification after the merchant notification is sent to the merchant server can be re-reachable based on the network return code analysis after the merchant notification is received and sent to the merchant server;
If the network return code merchant notification retransmission after the merchant notification is sent to the merchant server is not reachable, the network return code merchant notification retransmission after the problem of failure is solved is carried out and the network return code merchant notification retransmission after the merchant notification is sent to the merchant server is received.
Optionally, if the retransmission of the merchant notification is not reachable, retransmitting the merchant notification after the problem that causes the failure is resolved, including:
determining whether the cause of the failure is a merchant server side or a paymate side;
If the failure is caused by the merchant server side, sending prompt information for solving the problem to the merchant server side, and retransmitting the merchant notification after receiving the problem solved information fed back by the merchant server side;
And if the reason for the failure is at the payment platform side, retransmitting the merchant notification after the problem of the failure is solved by the payment platform.
Optionally, the determining whether the network return code is a notification failure code or a notification success code includes, if the network return code is a notification failure code:
judging whether the repeated forwarding times of the merchant notification reach a preset threshold value or not;
and if the repeated forwarding times of the merchant notification do not reach a preset threshold value, repeatedly forwarding the merchant notification to a merchant server side.
Optionally, the determining whether the number of times of repeated forwarding of the merchant notification reaches a predetermined threshold includes:
Acquiring the priority of the merchant server;
the predetermined threshold is determined based on the priority of the merchant server.
In a second aspect, there is provided a merchant notification transmission apparatus, the apparatus comprising,
The receiving module is used for sending the merchant notification to the merchant server and receiving a network return code after the merchant notification is sent to the merchant server;
A first judging module, configured to judge whether the network return code is a notification failure code or a notification success code, and if the network return code is the notification failure code, determine whether the merchant notification can be re-reachable based on the network return code analysis;
and the first resending module is used for resending the merchant notification after the problem of failure is solved if the resending of the merchant notification is not reachable.
Optionally, the first retransmission module includes:
a first determining unit for determining whether the cause of the failure is a merchant server side or a paymate side;
the first resending unit is used for sending prompt information for solving the problem to the merchant server side if the failure is caused by the merchant server side, and resending the merchant notification after receiving the problem solved information fed back by the merchant server side;
And the second retransmission unit is used for retransmitting the merchant notification after the problem of failure is solved by the platform to be paid if the cause of failure is at the payment platform side.
The apparatus further comprises:
the second judging module is used for judging whether the repeated forwarding times of the merchant notification reach a preset threshold value or not;
and the second retransmission module is used for repeatedly forwarding the merchant notification to the merchant server side if the repeated forwarding times of the merchant notification do not reach a preset threshold value.
The judging module comprises:
an acquisition unit, configured to acquire a priority of the merchant server;
And the second determining unit is used for determining the preset threshold value based on the priority of the merchant server.
In a third aspect, an electronic device is provided, the electronic device comprising:
One or more processors;
A memory;
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to: the merchant notification transmission method shown in the first aspect is performed.
In a fourth aspect, there is provided a computer readable storage medium storing computer instructions that, when run on a computer, cause the computer to perform the merchant notification transmission method of the first aspect.
Compared with the retransmission of the merchant notification only when the merchant notification is failed to be sent, the method and the device for sending the merchant notification are characterized in that the method and the device send the merchant notification to the merchant server, receive the network return code after the merchant notification is sent to the merchant server, judge whether the network return code is a notification failure code or a notification success code, if the network return code is the notification failure code, determine whether the merchant notification can be retransmitted or not based on the analysis of the network return code, and if the retransmission of the merchant notification cannot be achieved, retransmit the merchant notification after the problem of failure is solved. When the sending of the merchant notification fails, judging whether the merchant notification can be repeatedly reachable (namely, the repeatedly sent merchant notification can be successfully received by the merchant server), if the retransmission of the merchant notification is not reachable, not forwarding the merchant notification, and after the problem of failure is solved, retransmitting the merchant notification, thereby avoiding the resource waste caused by repeatedly forwarding the merchant notification under the condition that the repetition is not reachable.
Additional aspects and advantages of the application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application.
Drawings
The foregoing and/or additional aspects and advantages of the application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a flowchart of a method for sending merchant notification according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a merchant notification sending device according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a merchant notification sending device according to another embodiment of the application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative only and are not to be construed as limiting the application.
As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless expressly stated otherwise, as understood by those skilled in the art. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The term "and/or" as used herein includes all or any element and all combination of one or more of the associated listed items.
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
The embodiment of the application provides a method for sending merchant notification, as shown in fig. 1, which can comprise the following steps:
Step S101, sending a merchant notification to a merchant server, and receiving a network return code after the merchant notification is sent to the merchant server;
Specifically, taking a common online payment scenario as an example, online payment is a mainstream payment manner, and when an individual customer completes online payment, an online bank (payment platform) sends a merchant notification to a merchant server, which may include order information, payment status, and the like. Specifically, after sending the merchant notification to the merchant server, a corresponding network return code is received.
Step S102, judging whether the network return code is a notification failure code or a notification success code, if the network return code is the notification failure code, determining whether the merchant notification can be re-reachable based on the network return code analysis;
Specifically, whether the sending of the merchant notification is failed or successful is determined based on the received network return code, and if the received network return code indicates that the sending of the merchant notification is failed (e.g., a temporary error-free class code or a request error class status code is returned, e.g., status code 503 indicates a temporary status that the server is currently unavailable, and status code 404 indicates a web page for which the request cannot be found), then whether the sending of the merchant notification is reachable if repeated, i.e., whether the merchant server can successfully receive the merchant notification is analyzed. If the network return code is a success type code, such as a status code 2xx, the merchant server successfully processes the request, and the merchant server normally receives the merchant notification sent by the payment platform, and the merchant side can update the order status information and enter the next flow.
Step S103, if the retransmission of the merchant notification is not reachable, the retransmission of the merchant notification is performed after the problem that causes failure is solved.
Specifically, by analyzing the network return code, if repeated transmission of the merchant notification is not reachable, retransmission of the merchant notification is performed after the cause of the failure is resolved. If the repeated sending of the merchant notification is reachable, the repeated sending of the merchant notification can be directly performed.
Compared with the retransmission of the merchant notification only when the merchant notification is failed to be sent, the method provided by the embodiment of the application has the advantages that the merchant notification is sent to the merchant server, the network return code after the merchant notification is sent to the merchant server is received, then the network return code is judged to be the notification failure code or the notification success code, if the network return code is the notification failure code, the network return code analysis is used for determining whether the merchant notification can be retransmitted or not, and if the retransmission of the merchant notification cannot be achieved, the retransmission of the merchant notification is carried out after the problem of failure is solved. When the sending of the merchant notification fails, judging whether the merchant notification can be repeatedly reachable (namely, the repeatedly sent merchant notification can be successfully received by the merchant server), if the retransmission of the merchant notification is not reachable, not forwarding the merchant notification, and after the problem of failure is solved, retransmitting the merchant notification, thereby avoiding the resource waste caused by repeatedly forwarding the merchant notification under the condition that the repetition is not reachable.
The embodiment of the present application provides a possible implementation manner, specifically, step S103 includes:
step S1031 (not shown in the figure), determining whether the cause of failure is the merchant server side or the paymate side;
Step S1032 (not shown in the figure), if the cause of the failure is the merchant server side, sending prompt information for solving the problem to the merchant server side, and retransmitting the merchant notification after receiving the problem solved information fed back by the merchant server side;
step S1033 (not shown in the figure), if the cause of the failure is on the paymate side, retransmitting the merchant notification after the paymate solves the problem of the failure.
Specifically, the cause of the failure of sending the merchant notification is determined to be on the merchant server side or the payment platform side according to the network return code analysis, and if the status code 404 indicates that the requested web page cannot be found, the cause of the failure is on the merchant server side.
Specifically, if the failure is caused by the merchant server side, sending prompt information for solving the problem to the merchant server side, and retransmitting the merchant notification after receiving the problem solved information fed back by the merchant server side; the prompt information can be automatically sent by the payment platform or can be realized in a manual notification mode.
Specifically, if the cause of the failure is at the paymate side, the repayment of the merchant notification is performed after the paymate solves the problem of the failure. The payment platform can analyze the reasons for failure, and automatically resends the merchant notification after the problem is solved or after the corresponding trigger condition is met (for example, an instruction that the problem is solved is received).
For the embodiment of the application, the reason for failure is determined to be a merchant server side or a payment platform side according to the network return code, and after the problem is solved, the retransmission of the merchant notification is carried out, namely, the payment platform monitors the network return code in real time and positions the reason for failure in transmission, and the problem can be timely fed back and solved.
The embodiment of the present application provides a possible implementation manner, specifically, the determining in step S102 that the network return code is a notification failure code or a notification success code includes:
step S104 (not shown in the figure), judging whether the repeated forwarding times of the merchant notification reach a preset threshold value;
step S105 (not shown in the figure), if the number of times of repeated forwarding of the merchant notification does not reach a predetermined threshold, forwarding the merchant notification to the merchant server side repeatedly.
Specifically, if the network return code is a notification failure code, judging whether the number of times of repeatedly forwarding the merchant notification reaches a set threshold value, and if so, analyzing and positioning the failure reason. If the set threshold is not reached, retransmitting the merchant notification to the merchant server side.
For the embodiment of the application, if the repeated forwarding reaches the set threshold, the analysis and positioning of the failure cause are carried out, and if the repeated forwarding does not reach the set threshold, the merchant notification is retransmitted to the merchant server side. That is, since repetition is not available, repeated forwarding is usually successful, and when repeated transmission fails to reach a predetermined threshold, problem location and analysis are performed, where the predetermined threshold may be set to a smaller value (smaller than that of the prior art in which only retransmission within the threshold range is performed), so that resource consumption caused by transmission failure, i.e., problem location analysis, is avoided.
The embodiment of the application provides a possible implementation manner, and the judging whether the repeated forwarding times of the merchant notification reach a preset threshold value comprises the following steps:
Acquiring the priority of the merchant server;
the predetermined threshold is determined based on the priority of the merchant server.
In particular, the predetermined threshold may be set based on a priority of the merchant server, with an exemplary high priority merchant server having a higher predetermined threshold and a low priority user having a lower predetermined threshold.
According to the embodiment of the application, the data processing amount of the server at the payment platform side can be reduced based on the corresponding threshold value respectively set by the priority of the merchant server.
Fig. 2 is a schematic diagram of a merchant notification sending device according to an embodiment of the present application, where the device 20 includes: a receiving module 201, a judging module 202 and a first retransmitting module 203, wherein,
A receiving module 201, configured to send a merchant notification to a merchant server, and receive a network return code after the merchant notification is sent to the merchant server;
A first determining module 202, configured to determine whether the network return code is a notification failure code or a notification success code, and if the network return code is a notification failure code, determine whether the merchant notification is reachable again based on the network return code analysis;
And the first resending module 203 is configured to resend the merchant notification after the problem that causes the failure is solved if the resending of the merchant notification is not reachable.
Compared with the retransmission of the merchant notification only when the merchant notification is failed to be sent, the method provided by the embodiment of the application has the advantages that the merchant notification is sent to the merchant server, the network return code after the merchant notification is sent to the merchant server is received, then the network return code is judged to be the notification failure code or the notification success code, if the network return code is the notification failure code, the network return code analysis is used for determining whether the merchant notification can be retransmitted or not, and if the retransmission of the merchant notification cannot be achieved, the retransmission of the merchant notification is carried out after the problem of failure is solved. When the sending of the merchant notification fails, judging whether the merchant notification can be repeatedly reachable (namely, the repeatedly sent merchant notification can be successfully received by the merchant server), if the retransmission of the merchant notification is not reachable, not forwarding the merchant notification, and after the problem of failure is solved, retransmitting the merchant notification, thereby avoiding the resource waste caused by repeatedly forwarding the merchant notification under the condition that the repetition is not reachable.
The merchant notification sending device of the present embodiment may execute a merchant notification sending method provided in the foregoing embodiment of the present application, and the implementation principle is similar, and will not be described herein.
As shown in fig. 3, an embodiment of the present application provides another merchant notification sending apparatus, the apparatus 30 includes: a receiving module 301, a judging module 302 and a first retransmitting module 303, wherein,
A receiving module 301, configured to send a merchant notification to a merchant server, and receive a network return code after the merchant notification is sent to the merchant server;
the receiving module 301 in fig. 3 is the same as or similar to the receiving module 201 in fig. 2.
A first determining module 302, configured to determine whether the network return code is a notification failure code or a notification success code, and if the network return code is the notification failure code, determine whether the merchant notification is reachable again based on the network return code analysis;
the first determining module 302 in fig. 3 is the same as or similar to the first determining module 202 in fig. 2.
And the first resending module 303 is configured to resend the merchant notification after the problem that causes the failure is solved if the resending of the merchant notification is not reachable.
Wherein the first retransmission module 303 in fig. 3 has the same or similar function as the first retransmission module 203 in fig. 2.
The embodiment of the present application provides a possible implementation manner, specifically, the first retransmission module 303 includes:
A first determining unit 3031, configured to determine whether the cause of the failure is a merchant server side or a payment platform side;
A first resending unit 3032, configured to send a prompt message for solving a problem to a merchant server side if the cause of the failure is the merchant server side, and resend the merchant notification after receiving the problem solved message fed back by the merchant server side;
And the second retransmission unit 3033 is configured to, if the cause of the failure is on the payment platform side, perform retransmission of the merchant notification after the payment platform solves the problem of the failure.
For the embodiment of the application, the reason for failure is determined to be a merchant server side or a payment platform side according to the network return code, and after the problem is solved, the retransmission of the merchant notification is carried out, namely, the payment platform monitors the network return code in real time and positions the reason for failure in transmission, and the problem can be timely fed back and solved.
The embodiment of the application provides a possible implementation manner, and further comprises the following steps:
a second judging module 304, configured to judge whether the number of repeated forwarding of the merchant notification reaches a predetermined threshold;
and the second retransmission module 305 is configured to repeatedly forward the merchant notification to the merchant server side if the number of times of repeated forwarding of the merchant notification does not reach a predetermined threshold.
For the embodiment of the application, if the repeated forwarding reaches the set threshold, the analysis and positioning of the failure cause are carried out, and if the repeated forwarding does not reach the set threshold, the merchant notification is retransmitted to the merchant server side. That is, since repetition is not available, repeated forwarding is usually successful, and when repeated transmission fails to reach a predetermined threshold, problem location and analysis are performed, where the predetermined threshold may be set to a smaller value (smaller than that of the prior art in which only retransmission within the threshold range is performed), so that resource consumption caused by transmission failure, i.e., problem location analysis, is avoided.
The embodiment of the present application provides a possible implementation manner, and specifically, the judging module 304 includes:
an acquiring unit 3041, configured to acquire a priority of the merchant server;
A second determining unit 3042, configured to determine the predetermined threshold based on the priority of the merchant server.
According to the embodiment of the application, the data processing amount of the server at the payment platform side can be reduced based on the corresponding threshold value respectively set by the priority of the merchant server.
Compared with the retransmission of the merchant notification only when the merchant notification is failed to be sent, the method provided by the embodiment of the application has the advantages that the merchant notification is sent to the merchant server, the network return code after the merchant notification is sent to the merchant server is received, then the network return code is judged to be the notification failure code or the notification success code, if the network return code is the notification failure code, the network return code analysis is used for determining whether the merchant notification can be retransmitted or not, and if the retransmission of the merchant notification cannot be achieved, the retransmission of the merchant notification is carried out after the problem of failure is solved. When the sending of the merchant notification fails, judging whether the merchant notification can be repeatedly reachable (namely, the repeatedly sent merchant notification can be successfully received by the merchant server), if the retransmission of the merchant notification is not reachable, not forwarding the merchant notification, and after the problem of failure is solved, retransmitting the merchant notification, thereby avoiding the resource waste caused by repeatedly forwarding the merchant notification under the condition that the repetition is not reachable.
The embodiment of the application provides a merchant notification sending device, which is suitable for the method shown in the above embodiment and is not described herein.
The embodiment of the application provides an electronic device, as shown in fig. 4, an electronic device 40 shown in fig. 4 includes: a processor 401 and a memory 403. Processor 401 is connected to memory 403, such as via bus 402. Further, the electronic device 40 may also include a transceiver 404. It should be noted that, in practical applications, the transceiver 404 is not limited to one, and the structure of the electronic device 40 is not limited to the embodiment of the present application. The processor 401 is applied to the embodiment of the present application to implement the functions of the receiving module, the first judging module, and the first retransmitting module shown in fig. 2 or fig. 3, and the functions of the second judging module and the second retransmitting module shown in fig. 3. Transceiver 404 includes a receiver and a transmitter.
The processor 401 may be a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules and circuits described in connection with this disclosure. Processor 401 may also be a combination that implements computing functionality, such as a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
Bus 402 may include a path to transfer information between the components. Bus 402 may be a PCI bus, an EISA bus, or the like. Bus 402 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 4, but not only one bus or one type of bus.
The memory 403 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, optical disk storage (including compact disks, laser disks, optical disks, digital versatile disks, blu-ray disks, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
The memory 403 is used for storing application program codes for executing the inventive arrangements and is controlled to be executed by the processor 401. Processor 401 is operative to execute application code stored in memory 403 to implement the functionality of the merchant notification transmitting apparatus provided in the embodiment shown in fig. 2 or 3.
Compared with the retransmission of the merchant notification only when the transmission of the merchant notification fails, the embodiment of the application transmits the merchant notification to the merchant server, receives the network return code after the merchant notification is transmitted to the merchant server, then judges whether the network return code is the notification failure code or the notification success code, if the network return code is the notification failure code, determines whether the merchant notification can be retransmitted or not based on the analysis of the network return code, and if the retransmission of the merchant notification is not reachable, then retransmits the merchant notification after the problem of failure is solved. When the sending of the merchant notification fails, judging whether the merchant notification can be repeatedly reachable (namely, the repeatedly sent merchant notification can be successfully received by the merchant server), if the retransmission of the merchant notification is not reachable, not forwarding the merchant notification, and after the problem of failure is solved, retransmitting the merchant notification, thereby avoiding the resource waste caused by repeatedly forwarding the merchant notification under the condition that the repetition is not reachable.
The embodiment of the application provides electronic equipment which is suitable for the embodiment of the method. And will not be described in detail herein.
The embodiment of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method shown in the above embodiment.
The embodiment of the application provides a computer readable storage medium, compared with the retransmission of a merchant notification only when the transmission of the merchant notification fails, the application transmits the merchant notification to a merchant server, receives a network return code after the merchant notification is transmitted to the merchant server, then judges whether the network return code is a notification failure code or a notification success code, if the network return code is the notification failure code, determines whether the merchant notification can be retransmitted or not based on the analysis of the network return code, and if the retransmission of the merchant notification cannot be achieved, the retransmission of the merchant notification is carried out after the problem of failure is solved. When the sending of the merchant notification fails, judging whether the merchant notification can be repeatedly reachable (namely, the repeatedly sent merchant notification can be successfully received by the merchant server), if the retransmission of the merchant notification is not reachable, not forwarding the merchant notification, and after the problem of failure is solved, retransmitting the merchant notification, thereby avoiding the resource waste caused by repeatedly forwarding the merchant notification under the condition that the repetition is not reachable.
The embodiment of the application provides a computer readable storage medium suitable for the method embodiment. And will not be described in detail herein.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the flowcharts of the figures may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily being sequential, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.
The foregoing is only a partial embodiment of the present application, and it should be noted that it will be apparent to those skilled in the art that modifications and adaptations can be made without departing from the principles of the present application, and such modifications and adaptations should and are intended to be comprehended within the scope of the present application.
Claims (5)
1. The merchant notification sending method is characterized by being applied to a payment platform and comprising the following steps of:
sending a merchant notification to a merchant server, and receiving a network return code after the merchant notification is sent to the merchant server;
judging whether the network return code is a notification failure code or a notification success code, if the network return code is the notification failure code, judging whether the repeated forwarding times of the merchant notification reach a preset threshold value or not;
if the repeated forwarding times of the merchant notification do not reach a preset threshold value, repeatedly forwarding the merchant notification to a merchant server side;
if the number of repeated forwarding of the merchant notification reaches a predetermined threshold, determining whether the merchant notification is re-reachable based on the network return code analysis;
If the retransmission of the merchant notification is not reachable, retransmitting the merchant notification after the problem of failure is solved;
the step of judging whether the repeated forwarding times of the merchant notification reach a preset threshold value comprises the following steps: acquiring the priority of the merchant server; determining the predetermined threshold based on the priority of the merchant server;
The determining, based on the network return code analysis, whether the merchant notification is reachable again includes: determining whether the cause of the failure is a merchant server side or a paymate side; if the failure is caused by the merchant server side, sending prompt information for solving the problem to the merchant server side, and retransmitting the merchant notification after receiving the problem solved information fed back by the merchant server side; and if the reason for the failure is at the payment platform side, retransmitting the merchant notification after the problem of the failure is solved by the payment platform.
2. The method of claim 1, wherein if the re-sending of the merchant notification is not reachable, re-sending of the merchant notification is performed after the problem that caused the failure is resolved, comprising:
determining whether the cause of the failure is a merchant server side or a paymate side;
If the failure is caused by the merchant server side, sending prompt information for solving the problem to the merchant server side, and retransmitting the merchant notification after receiving the problem solved information fed back by the merchant server side;
And if the reason for the failure is at the payment platform side, retransmitting the merchant notification after the problem of the failure is solved by the payment platform.
3. A merchant notification transmission device, applied to a payment platform, comprising:
the receiving module is used for sending the merchant notification to the merchant server and receiving a network return code after the merchant notification is sent to the merchant server;
A first judging module, configured to judge whether the network return code is a notification failure code or a notification success code, and if the network return code is the notification failure code, determine whether the merchant notification can be re-reachable based on the network return code analysis;
the second judging module is used for judging whether the repeated forwarding times of the merchant notification reach a preset threshold value or not;
The second retransmission module is used for repeatedly forwarding the merchant notification to a merchant server side if the repeated forwarding times of the merchant notification do not reach a preset threshold value;
an acquisition unit, configured to acquire a priority of the merchant server;
A second determining unit configured to determine the predetermined threshold based on a priority of the merchant server;
the first resending module is used for resending the merchant notification after the problem of failure is solved if the merchant notification resends unreachable;
The first retransmission module includes:
a first determining unit for determining whether the cause of the failure is a merchant server side or a paymate side;
the first resending unit is used for sending prompt information for solving the problem to the merchant server side if the failure is caused by the merchant server side, and resending the merchant notification after receiving the problem solved information fed back by the merchant server side;
And the second retransmission unit is used for retransmitting the merchant notification after the problem of failure is solved by the platform to be paid if the cause of failure is at the payment platform side.
4. An electronic device, comprising:
One or more processors;
A memory;
One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to: a merchant notification transmission method according to any of claims 1 to 2 is performed.
5. A computer readable storage medium storing computer instructions which, when run on a computer, cause the computer to perform the merchant notification transmission method of any of the preceding claims 1 to 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911272746.7A CN111078433B (en) | 2019-12-12 | 2019-12-12 | Merchant notification sending method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911272746.7A CN111078433B (en) | 2019-12-12 | 2019-12-12 | Merchant notification sending method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111078433A CN111078433A (en) | 2020-04-28 |
| CN111078433B true CN111078433B (en) | 2024-07-19 |
Family
ID=70314026
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911272746.7A Active CN111078433B (en) | 2019-12-12 | 2019-12-12 | Merchant notification sending method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111078433B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105279640A (en) * | 2014-07-07 | 2016-01-27 | 世纪禾光科技发展（北京）有限公司 | System and method of cross-border payment multi-store service state notification |
| CN109039732A (en) * | 2018-07-26 | 2018-12-18 | 中国建设银行股份有限公司 | Message handling system and message treatment method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060112011A1 (en) * | 2002-09-16 | 2006-05-25 | Al-Ali Abdulhadi M | Electronic banking system |
| US10225359B2 (en) * | 2016-09-22 | 2019-03-05 | International Business Machines Corporation | Push notifications from multiple tenant servers |
| CN107770281A (en) * | 2017-11-01 | 2018-03-06 | 深圳市金立通信设备有限公司 | A kind of method, server and computer-readable recording medium for notifying trade company's reimbursement information |
| CN108038679A (en) * | 2017-12-05 | 2018-05-15 | 苏州比可网络科技有限公司 | Send the method and polymerization payment platform of payment message |
-
2019
- 2019-12-12 CN CN201911272746.7A patent/CN111078433B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105279640A (en) * | 2014-07-07 | 2016-01-27 | 世纪禾光科技发展（北京）有限公司 | System and method of cross-border payment multi-store service state notification |
| CN109039732A (en) * | 2018-07-26 | 2018-12-18 | 中国建设银行股份有限公司 | Message handling system and message treatment method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111078433A (en) | 2020-04-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8997115B2 (en) | Method for data delivery in a network | |
| US7971209B2 (en) | Shortcut in reliable communication | |
| JP6831412B2 (en) | Interfaces, systems, methods and computer program products for controlling the transfer of electronic messages | |
| CN101572598B (en) | Method and device for reliable rapid integration | |
| US9888048B1 (en) | Supporting millions of parallel light weight data streams in a distributed system | |
| CN111371892A (en) | High-concurrency distributed message pushing system and method | |
| US20110173495A1 (en) | Method and System for Reliable Intersystem Message Notification | |
| US8812711B2 (en) | Three-way communication protocol | |
| EP2541413A1 (en) | Systems and Methods for Data Integrity Checking | |
| CN110233881A (en) | Service request processing method, device, equipment and storage medium | |
| CN111651284B (en) | Method, device, system and storage medium for processing business data | |
| CN113220730B (en) | Service data processing system | |
| CN113986501A (en) | Real-time database API call method, system, storage medium and server without interruption | |
| CN113177052B (en) | A method and device for processing business data consistency in a distributed system | |
| CN108880994B (en) | Method and device for retransmitting mails | |
| CN111078433B (en) | Merchant notification sending method and device and electronic equipment | |
| CN110941622A (en) | Data processing method and device | |
| CN110650204A (en) | Data access method, device, equipment and storage medium of NAS cluster | |
| CN106921619B (en) | Associated event processing method and device | |
| US10462218B1 (en) | System and method for sending proposals within a distributed state machine replication system | |
| CN113783666B (en) | Method and device for processing business | |
| CN109347940B (en) | Method and device for processing cross-domain service request and request for cross-domain service | |
| CN106453635A (en) | Message pushing method and device | |
| CN111552907A (en) | Message processing method, device, equipment and storage medium | |
| CN111478755B (en) | Asynchronous data communication method, medium, equipment and asynchronous data communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220919 Address after: 12 / F, 15 / F, 99 Yincheng Road, Pudong New Area pilot Free Trade Zone, Shanghai, 200120 Applicant after: Jianxin Financial Science and Technology Co.,Ltd. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |