CN111078433A - Merchant notification sending method and device and electronic equipment - Google Patents
Merchant notification sending method and device and electronic equipment Download PDFInfo
- Publication number
- CN111078433A CN111078433A CN201911272746.7A CN201911272746A CN111078433A CN 111078433 A CN111078433 A CN 111078433A CN 201911272746 A CN201911272746 A CN 201911272746A CN 111078433 A CN111078433 A CN 111078433A
- Authority
- CN
- China
- Prior art keywords
- merchant
- notification
- failure
- code
- merchant notification
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 230000005540 biological transmission Effects 0.000 claims description 17
- 239000002699 waste material Substances 0.000 abstract description 8
- 230000006870 function Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000005034 decoration Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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; CALCULATING OR 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; CALCULATING OR 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; CALCULATING OR 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; CALCULATING OR 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 merchant notification sending method, a merchant notification sending device 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 merchant notification which is repeatedly sent can be successfully received by the merchant server), if the merchant notification is not retransmitted, retransmitting the merchant notification, and retransmitting the merchant notification after the problem of failure is solved, so that the waste of resources caused by repeated retransmission of the merchant notification under the condition of repeated unreachability is avoided.
Description
Technical Field
The application relates to the technical field of computers, in particular to a method and a device for sending a merchant notification and an electronic device.
Background
In China today, the traditional payment method through cash, bills and other physical entities is gradually replaced by an online payment method, and a digital payment method based on internet communication becomes a mainstream payment method. The process of generating an online payment transaction comprises three related parties, namely an individual customer, a merchant and a payment platform for providing payment services, such as a third party payment mechanism like a WeChat Payment treasure, and a platform for providing payment services for a bank and a Unionpay. In the payment transaction, after the personal customer completes the online payment, the payment platform sends a merchant notification, namely order information, a payment state and the like to the merchant, and the merchant server can update the order state of the customer after receiving the notification information of the payment platform.
Due to various reasons, the merchant notification may be failed to be sent, in the prior art, the merchant notification is sent again after the merchant notification is failed to be sent, however, when the merchant notification is still failed to be sent again, the payment platform cannot timely locate and repair the problem, and a large amount of single-side accounts are generated.
Disclosure of Invention
The application provides a merchant notification sending method, a merchant notification sending device and electronic equipment, which are used for avoiding resource waste caused by repeated forwarding of merchant notifications under the condition of repeated inaccessibility, and the technical scheme adopted by the application is as follows:
in a first aspect, a merchant notification sending method is provided, which is applied to a payment platform, the method includes,
sending a merchant notification to a merchant server, receiving a network return code after the merchant notification is sent to the merchant server and receiving the network return code after the merchant notification is sent to the merchant server;
judging and receiving a network return code sent by the merchant notification to the merchant server as a notification failure code or a notification success code, if the network return code received and sent by the merchant notification to the merchant server is the notification failure code, determining and receiving whether the network return code merchant notification sent by the merchant notification to the merchant server can be retransmitted and reached 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 receiving the merchant notification and sending the merchant notification to the merchant server is not reachable, the retransmission of the network return code merchant notification after receiving the merchant notification and sending the merchant notification to the merchant server is performed after the problem of failure is solved.
Optionally, if the merchant notification is not reachable by retransmission, the retransmitting the merchant notification after the problem that caused the failure is solved includes:
determining whether the failure is caused by the merchant server side or the payment platform side;
if the failure reason is at the merchant server side, sending problem-solving prompt information to the merchant server side, and after receiving the problem-solved information fed back by the merchant server side, retransmitting the merchant notification;
and if the reason causing the failure is on the payment platform side, after the problem causing the failure is solved by the payment platform, the merchant notification is retransmitted.
Optionally, the determining 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, then includes:
judging whether the number of times of repeated forwarding of the merchant notification reaches a preset threshold value;
and if the repeated forwarding times of the merchant notification do not reach a preset threshold value, the merchant notification is repeatedly forwarded to a merchant server side.
Optionally, the determining whether the number of times of the repeated forwarding of the merchant notification reaches a predetermined threshold includes:
acquiring the priority of the merchant server;
determining the predetermined threshold based on a 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 a merchant notification to the merchant server and receiving a network return code after the merchant notification is sent to the merchant server;
the first judgment module is used for judging 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, whether the merchant notification can be retransmitted and reached is determined based on the analysis of the network return code;
and the first retransmission module is used for retransmitting the merchant notification after the problem of failure is solved if the merchant notification is unreachable for retransmission.
Optionally, the first retransmission module includes:
a first determination unit configured to determine whether a cause of the failure is at a merchant server side or a payment platform side;
a first retransmission unit, configured to send problem-solving prompt information to a merchant server side if a failure cause is the merchant server side, and perform retransmission of the merchant notification after receiving 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 reason of failure is at the side of the payment platform.
The device also includes:
the second judgment 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 retransmitting the merchant notification to the merchant server side repeatedly if the repeated retransmission times of the merchant notification do not reach a preset threshold value.
The judging module comprises:
an obtaining unit, configured to obtain a priority of the merchant server;
a second determination unit for determining the predetermined threshold based on the priority of the merchant server.
In a third aspect, an electronic device is provided, which includes:
one or more processors;
a memory;
one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to: the merchant notification sending method shown in the first aspect is performed.
In a fourth aspect, a computer-readable storage medium is provided, which is used for storing computer instructions, when the computer instructions are run on a computer, the computer can execute the merchant notification sending method shown in the first aspect.
Compared with the method that only merchant notification retransmission is carried out when merchant notification transmission fails, the method that merchant notification is sent to a merchant server, network return codes after the merchant notification is sent to the merchant server are received, whether the network return codes are notification failure codes or notification success codes are judged, if the network return codes are the notification failure codes, whether the merchant notification retransmission can be achieved or not is determined based on analysis of the network return codes, and if the merchant notification retransmission cannot be achieved, the merchant notification retransmission is carried out after the problem of failure is solved. That is, when the sending of the merchant notification fails, it is determined whether the merchant notification can be repeatedly reachable (that is, the merchant notification repeatedly sent can be successfully received by the merchant server), if the merchant notification is not retransmitted, the merchant notification is not forwarded, and the merchant notification is retransmitted after the problem that causes the failure is solved, so that the waste of resources caused by the repeated forwarding of the merchant notification under the condition that the merchant notification is repeatedly unreachable is avoided.
Additional aspects and advantages of the present 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 present application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic flowchart of a method for sending a merchant notification according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a merchant notification sending apparatus according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of another merchant notification sending apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.
As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. 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. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
An embodiment of the present application provides a method for sending a merchant notification, as shown in fig. 1, the method may include 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 method, and after an individual customer completes online payment, an online bank (payment platform) sends a merchant notification to a merchant server, which may specifically include order information and a payment status. Specifically, after sending the merchant notification to the merchant server, the 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, analyzing and determining whether the merchant notification can be retransmitted and reached based on the network return code;
specifically, it is determined whether the sending of the merchant notification is failed or successful based on the received network return code, and if the received network return code indicates that the sending of the merchant notification is failed (for example, a temporary error-free status code or a request error-like status code is returned, for example, the status code 503 indicates a temporary status that the server cannot be used at present, and the status code 404 indicates that the requested web page cannot be found), it is analyzed whether the merchant notification is reachable if the merchant notification is repeatedly sent, that is, whether the merchant server can successfully receive the merchant notification. If the network return code is a success code, such as the status code 2xx, it indicates that the merchant server has successfully processed the request, and at this time, the merchant server has normally received the merchant notification sent by the payment platform, and the merchant side can update the order status information and proceed to the next process.
Step S103, if the merchant notification retransmission is not reachable, the merchant notification retransmission is performed after the problem causing failure is solved.
Specifically, by analyzing the network return code, if the repeated sending of the merchant notification is not reachable, the merchant notification is retransmitted 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 may be directly performed.
Compared with the method that only merchant notification is retransmitted when merchant notification transmission fails, the method that merchant notification is transmitted to a merchant server and a network return code after the merchant notification is transmitted to the merchant server is received, whether the network return code is a notification failure code or a notification success code is judged, if the network return code is the notification failure code, whether the merchant notification can be retransmitted and reached is determined based on analysis of the network return code, and if the merchant notification is retransmitted and reached, the merchant notification is retransmitted after a problem causing failure is solved. That is, when the sending of the merchant notification fails, it is determined whether the merchant notification can be repeatedly reachable (that is, the merchant notification repeatedly sent can be successfully received by the merchant server), if the merchant notification is not retransmitted, the merchant notification is not forwarded, and the merchant notification is retransmitted after the problem that causes the failure is solved, so that the waste of resources caused by the repeated forwarding of the merchant notification under the condition that the merchant notification is repeatedly unreachable is avoided.
The embodiment of the present application provides a possible implementation manner, and specifically, step S103 includes:
step S1031 (not shown in the figure), determining whether the cause of the failure is on the merchant server side or the payment platform side;
step S1032 (not shown in the figure), if the failure is caused by the merchant server side, sending a prompt message for solving the problem to the merchant server side, and after receiving the problem solved information fed back by the merchant server side, retransmitting the merchant notification;
step S1033 (not shown in the figure), if the reason causing the failure is on the payment platform side, after the payment platform solves the problem causing the failure, the merchant notification is retransmitted.
Specifically, whether the reason causing the failure of sending the merchant notification is the merchant server side or the payment platform side is determined according to the analysis of the network return code, and if the status code 404 indicates that the requested webpage cannot be found, the reason of the failure is the merchant server side.
Specifically, if the failure is caused by the merchant server side, sending a problem-solving prompt message to the merchant server side, and after receiving the problem-solved message fed back by the merchant server side, retransmitting the merchant notification; the prompt message may be automatically sent by the payment platform or may be implemented in a manual notification manner.
Specifically, if the reason causing the failure is on the payment platform side, the merchant notification is retransmitted after the problem causing the failure is solved by the payment platform. The payment platform may analyze the reason causing the failure, and automatically resend the merchant notification after the problem is solved or after a corresponding trigger condition is met (for example, an instruction that the problem has been solved is received).
For the embodiment of the application, the reason causing the failure is determined to be the merchant server side or the payment platform side according to the network return code, the merchant notification is retransmitted after the problem is solved, namely, the payment platform monitors the network return code in real time, positions the reason of the failure transmission, and can timely feed back and solve the problem.
The embodiment of the present application provides a possible implementation manner, specifically, the determining, in step S102, 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, then the method includes:
step S104 (not shown in the figure), determining whether the number of times of repeated forwarding of the merchant notification reaches a predetermined threshold;
step S105 (not shown in the figure), if the number of times of the repeated forwarding of the merchant notification does not reach the predetermined threshold, repeatedly forwarding the merchant notification to the merchant server side.
Specifically, if the network return code is a notification failure code, it is determined whether the number of times of repeatedly forwarding the merchant notification reaches a set threshold, and if the number of times of repeatedly forwarding the merchant notification reaches the set threshold, the failure reason is analyzed and located. If the merchant notification does not reach the set threshold value, the merchant notification is retransmitted and forwarded to the merchant server side.
For the embodiment of the application, if repeated forwarding reaches the set threshold, analysis and positioning of the failure reason are carried out, and if the repeated forwarding does not reach the set threshold, the merchant notification is retransmitted and forwarded to the merchant server side. That is, because the number of times of repeated inaccessibility is small, repeated forwarding can be successfully carried out, and when the repeated transmission failure reaches a predetermined threshold, problem location and analysis are carried out, wherein the predetermined threshold can be set to a small value (compared with the prior art that only retransmission within the threshold range is carried out), so that resource consumption caused by the problem location analysis which is carried out when the transmission failure is carried out is avoided.
The embodiment of the present application provides a possible implementation manner, where the determining whether the number of times of the repeated forwarding of the merchant notification reaches a predetermined threshold includes:
acquiring the priority of the merchant server;
determining the predetermined threshold based on a priority of the merchant server.
Specifically, the predetermined threshold may be set based on the 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.
For 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 values respectively set by the priority of the merchant server.
Fig. 2 is a device for sending a merchant notification according to an embodiment of the present application, where the device 20 includes: a receiving module 201, a determining 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 the notification failure code, determine whether the merchant notification can be retransmitted and reached based on analysis of the network return code;
a first retransmission module 203, configured to perform retransmission of the merchant notification after the problem that causes failure is solved if the merchant notification is unreachable for retransmission.
Compared with the situation that only merchant notification retransmission is carried out when merchant notification transmission fails, the merchant notification transmission device sends merchant notification to a merchant server, receives a network return code after the merchant notification is sent to the merchant server, judges whether the network return code is a notification failure code or a notification success code, determines whether the merchant notification retransmission can be achieved based on the network return code analysis if the network return code is the notification failure code, and then carries out the merchant notification retransmission after the problem causing failure is solved if the merchant notification retransmission is not achieved. That is, when the sending of the merchant notification fails, it is determined whether the merchant notification can be repeatedly reachable (that is, the merchant notification repeatedly sent can be successfully received by the merchant server), if the merchant notification is not retransmitted, the merchant notification is not forwarded, and the merchant notification is retransmitted after the problem that causes the failure is solved, so that the waste of resources caused by the repeated forwarding of the merchant notification under the condition that the merchant notification is repeatedly unreachable is avoided.
The merchant notification sending apparatus of this embodiment may execute the merchant notification sending method provided in the above embodiments of this application, and the implementation principles thereof are similar, and are not described herein again.
As shown in fig. 3, another merchant notification sending apparatus is provided in the embodiment of the present application, where the apparatus 30 includes: a receiving module 301, a determining 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;
wherein, the receiving module 301 in fig. 3 has the same or similar function as 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 can be retransmitted and reached based on analysis of the network return code;
the first determining module 302 in fig. 3 has the same or similar function as the first determining module 202 in fig. 2.
A first retransmission module 303, configured to perform retransmission of the merchant notification after the problem that causes the failure is solved if the merchant notification is unreachable for retransmission.
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, and specifically, the first retransmission module 303 includes:
a first determination unit 3031 configured to determine whether the cause of the failure is on the merchant server side or the payment platform side;
a first retransmission unit 3032, configured to send problem-solving prompt information to a merchant server side if the failure cause is the merchant server side, and perform retransmission of the merchant notification after receiving the problem-solved information fed back by the merchant server side;
a second retransmission unit 3033, configured to, if the reason for the failure is on the payment platform side, perform retransmission of the merchant notification after the problem that the failure is solved by the payment platform.
For the embodiment of the application, the reason causing the failure is determined to be the merchant server side or the payment platform side according to the network return code, the merchant notification is retransmitted after the problem is solved, namely, the payment platform monitors the network return code in real time, positions the reason of the failure transmission, and can timely feed back and solve the problem.
The embodiment of the present application provides a possible implementation manner, and further, the apparatus further includes:
a second determining module 304, configured to determine whether the number of times that the merchant notification is repeatedly forwarded reaches a predetermined threshold;
a second retransmission module 305, configured to repeat forwarding the merchant notification to the merchant server side if the number of times of repeat forwarding of the merchant notification does not reach a predetermined threshold.
For the embodiment of the application, if repeated forwarding reaches the set threshold, analysis and positioning of the failure reason are carried out, and if the repeated forwarding does not reach the set threshold, the merchant notification is retransmitted and forwarded to the merchant server side. That is, because the number of times of repeated inaccessibility is small, repeated forwarding can be successfully carried out, and when the repeated transmission failure reaches a predetermined threshold, problem location and analysis are carried out, wherein the predetermined threshold can be set to a small value (compared with the prior art that only retransmission within the threshold range is carried out), so that resource consumption caused by the problem location analysis which is carried out when the transmission failure is carried out is avoided.
The embodiment of the present application provides a possible implementation manner, and specifically, the determining module 304 includes:
an obtaining unit 3041, configured to obtain 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.
For 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 values respectively set by the priority of the merchant server.
Compared with the situation that only merchant notification retransmission is carried out when merchant notification transmission fails, the merchant notification transmission device sends merchant notification to a merchant server, receives a network return code after the merchant notification is sent to the merchant server, judges whether the network return code is a notification failure code or a notification success code, determines whether the merchant notification retransmission can be achieved based on the network return code analysis if the network return code is the notification failure code, and then carries out the merchant notification retransmission after the problem causing failure is solved if the merchant notification retransmission is not achieved. That is, when the sending of the merchant notification fails, it is determined whether the merchant notification can be repeatedly reachable (that is, the merchant notification repeatedly sent can be successfully received by the merchant server), if the merchant notification is not retransmitted, the merchant notification is not forwarded, and the merchant notification is retransmitted after the problem that causes the failure is solved, so that the waste of resources caused by the repeated forwarding of the merchant notification under the condition that the merchant notification is repeatedly unreachable is avoided.
The embodiment of the present application provides a merchant notification sending apparatus, which is suitable for the method shown in the foregoing embodiment, and is not described herein again.
An embodiment of the present 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. Wherein the processor 401 is coupled to the memory 403, such as via a bus 402. Further, the electronic device 40 may also include a transceiver 404. It should be noted that the transceiver 404 is not limited to one in practical applications, and the structure of the electronic device 40 is not limited to the embodiment of the present application. In the embodiment of the present application, the processor 401 is applied to implement the functions of the receiving module, the first determining module, and the first retransmitting module shown in fig. 2 or fig. 3, and the functions of the second determining module and the second retransmitting module shown in fig. 3. The 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 component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 401 may also be a combination of computing functions, e.g., comprising one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
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 disk, laser disk, optical disk, digital versatile disk, blu-ray disk, 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 scheme of the application, and the execution is controlled by the processor 401. Processor 401 is configured to execute application program code stored in memory 403 to implement the functionality of the merchant notification sending means provided by the embodiments shown in fig. 2 or fig. 3.
Compared with the method that only merchant notification retransmission is carried out when merchant notification transmission fails, merchant notification is transmitted to a merchant server, a network return code sent to the merchant server by the merchant notification is received, whether the network return code is a notification failure code or a notification success code is judged, if the network return code is the notification failure code, whether the merchant notification retransmission can be achieved or not is determined based on analysis of the network return code, and if the merchant notification retransmission cannot be achieved, the merchant notification retransmission is carried out after the problem causing failure is solved. That is, when the sending of the merchant notification fails, it is determined whether the merchant notification can be repeatedly reachable (that is, the merchant notification repeatedly sent can be successfully received by the merchant server), if the merchant notification is not retransmitted, the merchant notification is not forwarded, and the merchant notification is retransmitted after the problem that causes the failure is solved, so that the waste of resources caused by the repeated forwarding of the merchant notification under the condition that the merchant notification is repeatedly unreachable is avoided.
The embodiment of the application provides an electronic device suitable for the method embodiment. And will not be described in detail herein.
The present application provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the method shown in the above embodiments is implemented.
Compared with the method that only merchant notification retransmission is carried out when merchant notification transmission fails, merchant notification is transmitted to a merchant server, a network return code after the merchant notification is transmitted to the merchant server is received, whether the network return code is a notification failure code or a notification success code is judged, if the network return code is the notification failure code, whether the merchant notification retransmission can be achieved or not is determined based on analysis of the network return code, and if the merchant notification retransmission cannot be achieved, the merchant notification retransmission is carried out after the problem causing failure is solved. That is, when the sending of the merchant notification fails, it is determined whether the merchant notification can be repeatedly reachable (that is, the merchant notification repeatedly sent can be successfully received by the merchant server), if the merchant notification is not retransmitted, the merchant notification is not forwarded, and the merchant notification is retransmitted after the problem that causes the failure is solved, so that the waste of resources caused by the repeated forwarding of the merchant notification under the condition that the merchant notification is repeatedly unreachable is avoided.
The embodiment of the application provides a computer-readable storage medium which is 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, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.
Claims (10)
1. A method for sending a merchant notification is applied to a payment platform and comprises the following steps:
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, and if the network return code is the notification failure code, analyzing and determining whether the merchant notification can be retransmitted and reached based on the network return code;
and if the merchant notification retransmission is not reachable, retransmitting the merchant notification after solving the problem causing failure.
2. The method of claim 1, wherein the re-sending the merchant notification after the problem causing the failure is resolved if the merchant notification re-sending is not reachable comprises:
determining whether the failure is caused by the merchant server side or the payment platform side;
if the failure reason is at the merchant server side, sending problem-solving prompt information to the merchant server side, and after receiving the problem-solved information fed back by the merchant server side, retransmitting the merchant notification;
and if the reason causing the failure is on the payment platform side, after the problem causing the failure is solved by the payment platform, the merchant notification is retransmitted.
3. The method of claim 1, wherein determining 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, then comprising:
judging whether the number of times of repeated forwarding of the merchant notification reaches a preset threshold value;
and if the repeated forwarding times of the merchant notification do not reach a preset threshold value, the merchant notification is repeatedly forwarded to a merchant server side.
4. The method of claim 3, wherein the determining whether the number of times the merchant notification is repeatedly forwarded reaches a predetermined threshold comprises:
acquiring the priority of the merchant server;
determining the predetermined threshold based on a priority of the merchant server.
5. A merchant notification sending device applied to a payment platform comprises:
the receiving module is used for sending a merchant notification to the merchant server and receiving a network return code after the merchant notification is sent to the merchant server;
the first judgment module is used for judging 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, whether the merchant notification can be retransmitted and reached is determined based on the analysis of the network return code;
and the first retransmission module is used for retransmitting the merchant notification after the problem of failure is solved if the merchant notification is unreachable for retransmission.
6. The apparatus of claim 5, wherein the first retransmission module comprises:
a first determination unit configured to determine whether a cause of the failure is at a merchant server side or a payment platform side;
a first retransmission unit, configured to send problem-solving prompt information to a merchant server side if a failure cause is the merchant server side, and perform retransmission of the merchant notification after receiving 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 reason of failure is at the side of the payment platform.
7. The apparatus of claim 5, further comprising:
the second judgment 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 retransmitting the merchant notification to the merchant server side repeatedly if the repeated retransmission times of the merchant notification do not reach a preset threshold value.
8. The apparatus of claim 7, wherein the determining module comprises:
an obtaining unit, configured to obtain a priority of the merchant server;
a second determination unit for determining the predetermined threshold based on the priority of the merchant server.
9. 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 programs configured to: executing the merchant notification transmission method according to any one of claims 1 to 4.
10. A computer-readable storage medium for storing computer instructions which, when executed on a computer, cause the computer to perform the merchant notification transmission method of any one of the preceding claims 1 to 4.
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 true CN111078433A (en) | 2020-04-28 |
| CN111078433B 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 (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1703706A (en) * | 2002-09-16 | 2005-11-30 | 沙特阿拉伯石油公司 | Electronic banking system |
| CN105279640A (en) * | 2014-07-07 | 2016-01-27 | 世纪禾光科技发展（北京）有限公司 | System and method of cross-border payment multi-store service state notification |
| 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 |
| US20180084071A1 (en) * | 2016-09-22 | 2018-03-22 | International Business Machines Corporation | Push notifications from multiple tenant servers |
| CN108038679A (en) * | 2017-12-05 | 2018-05-15 | 苏州比可网络科技有限公司 | Send the method and polymerization payment platform of payment message |
| CN109039732A (en) * | 2018-07-26 | 2018-12-18 | 中国建设银行股份有限公司 | Message handling system and message treatment method |
-
2019
- 2019-12-12 CN CN201911272746.7A patent/CN111078433B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1703706A (en) * | 2002-09-16 | 2005-11-30 | 沙特阿拉伯石油公司 | Electronic banking system |
| CN105279640A (en) * | 2014-07-07 | 2016-01-27 | 世纪禾光科技发展（北京）有限公司 | System and method of cross-border payment multi-store service state notification |
| US20180084071A1 (en) * | 2016-09-22 | 2018-03-22 | 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 |
| CN109039732A (en) * | 2018-07-26 | 2018-12-18 | 中国建设银行股份有限公司 | Message handling system and message treatment method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111078433B (en) | 2024-07-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8959180B1 (en) | Proxy for tolerating faults in high-security systems | |
| CN111371892A (en) | High-concurrency distributed message pushing system and method | |
| CN110413424B (en) | Configurable third-party message callback method, device, server and storage medium | |
| CN112446786A (en) | Abnormal transaction processing method and device, electronic equipment and readable storage medium | |
| CN111245900A (en) | Distributed message sending processing system and processing method thereof | |
| CN109379445A (en) | A kind of sending method and device of PUSH message | |
| US10642585B1 (en) | Enhancing API service schemes | |
| CN107645476B (en) | Request processing method and device | |
| CN112068973A (en) | Asynchronous information processing method and device of policy mode, server and storage medium | |
| CN111090532A (en) | Application service calling method and device, electronic equipment and computer storage medium | |
| CN111414263A (en) | Information processing method, device, server and storage medium | |
| CN110287267A (en) | A kind of data processing method and device of cross-node | |
| US11704229B1 (en) | Auto-intrusive data pattern and test case generation for system validation | |
| CN111367934A (en) | Data consistency checking method, device, server and medium | |
| US10929237B2 (en) | Error handling tool | |
| CN111371586B (en) | Log data transmission method, device and equipment | |
| CN111078433A (en) | Merchant notification sending method and device and electronic equipment | |
| CN110543360A (en) | Task processing method and system | |
| US20220276901A1 (en) | Batch processing management | |
| CN106921619B (en) | Associated event processing method and device | |
| CN109510816B (en) | Service request validity verification method, client and server | |
| CN114793232A (en) | Service processing method and device, electronic equipment and storage medium | |
| CN109862091B (en) | Content publishing processing method and device for community | |
| CN112950171A (en) | Bank business processing system and method | |
| CN112181686A (en) | Data processing method, device and system, electronic equipment and storage medium |
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 |