CN110706069B - Exception handling method, device, server and system for order payment request - Google Patents
Exception handling method, device, server and system for order payment request Download PDFInfo
- Publication number
- CN110706069B CN110706069B CN201910914132.8A CN201910914132A CN110706069B CN 110706069 B CN110706069 B CN 110706069B CN 201910914132 A CN201910914132 A CN 201910914132A CN 110706069 B CN110706069 B CN 110706069B
- Authority
- CN
- China
- Prior art keywords
- order
- payment
- request
- record
- 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
Images
Classifications
-
- 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]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/407—Cancellation of a transaction
Abstract
The invention discloses an exception handling method, equipment, a server and a system for an order payment request, which relate to the field of electronic information and comprise the following steps: receiving an order form correcting request triggered by payment management equipment when determining that the sent order form payment request is abnormal, and acquiring an order form identifier contained in the order form correcting request; inquiring whether an order record matched with the order mark is stored in a preset order database; if so, acquiring the payment state recorded by the order; when the payment state of the order record is determined to be paid, a revocation request containing an order identifier is sent to a payment server, so that the payment server executes revocation processing aiming at the order record; and when a revocation success message returned by the payment server is received, marking the order record stored in the order database as a revoked state. The method solves the problem of overlong waiting time of the user caused by the fact that the order cannot be paid in time due to network abnormity.
Description
Technical Field
The invention relates to the field of electronic information, in particular to an exception handling method, equipment, a server and a system for an order payment request.
Background
In electronic payment, network transmission is required, and interaction of multiple servers is required to complete processing of payment data. In the process, once the network environment is poor or a packet loss phenomenon occurs between servers, the payment data processing is abnormal. In order to solve the problem of abnormal processing of payment data, patent application No. 2017106225996 discloses an order processing method and device, wherein the payment state of a corresponding payment order is updated according to payment success information sent by a payment platform: if the payment state of the payment order is unpaid, generating an alarm for the abnormity of the payment order; and if the state of the payment order is paid, updating the payment state of the consumption order corresponding to the payment order, so that the business problem caused by the fact that the state of the payment order cannot be updated in time after the user pays can be prevented.
However, the inventor finds that the above mode in the prior art has at least the following defects in the process of implementing the invention: in the above manner, the abnormal situation caused by the fact that the user has finished paying and the order state is not updated in time can be processed only. However, in practical situations, there may be a problem that the user still does not complete the payment data processing for a long time due to the abnormal network transmission, and in this case, in order to avoid the user to wait endlessly, it is necessary to perform the correction processing for the order in which the payment data processing is not completed for a long time. In the prior art, no reliable punching treatment mode can solve the problems. In short, in the prior art, the problem that data transmission is abnormal due to various factors such as network reasons and equipment reasons when order payment data is transmitted among a plurality of network equipment cannot be solved.
Disclosure of Invention
In view of the above, the present invention has been made to provide an exception handling method, apparatus, server and system for an order payment request that overcomes or at least partially solves the above mentioned problems.
According to an aspect of the present invention, there is provided an exception handling method for an order payment request, including:
receiving an order form correcting request triggered by payment management equipment when determining that the sent order form payment request is abnormal, and acquiring an order form identifier contained in the order form correcting request;
inquiring whether an order record matched with the order mark is stored in a preset order database; if so, acquiring the payment state of the order record;
when the payment state of the order record is determined to be paid, sending a revocation request containing the order identification to a payment server, so that the payment server executes revocation processing aiming at the order record;
and when a revocation success message returned by the payment server is received, marking the order record stored in the order database as a revoked state.
Optionally, after sending the revocation request including the order identifier to the payment server, the method further includes:
marking the order record as a state to be cancelled; and storing the order identifier into a preset interception list to intercept a payment success message returned by the payment server for the order identifier.
Optionally, after sending the revocation request including the order identifier to the payment server, the method further includes:
the payment server inquires whether an order payment record corresponding to the order identification is stored in a preset order payment data table;
if not, creating a revocation list record corresponding to the order identification, and executing revocation processing aiming at the revocation list record;
and the revocation list record is used for intercepting an order payment request which is forwarded by an order processing server and contains the order identification.
Optionally, the creating a revocation list record corresponding to the order identifier includes: creating a revocation list record corresponding to the order identification in a preset cache space;
and executing elimination processing aiming at the revocation list records stored in the preset cache space when a preset elimination period arrives.
Optionally, after the payment server queries whether an order payment record corresponding to the order identifier is stored in a preset order payment data table, the method further includes:
if yes, inquiring the payment state of the order payment record corresponding to the order identification;
closing the order transaction corresponding to the order payment record when the payment state of the order payment record corresponding to the order identification is determined to be unpaid;
and when the payment state of the order payment record corresponding to the order identification is determined to be paid, executing refund processing aiming at the order payment record.
Optionally, before the receiving the order correction request triggered by the payment management device when determining that the sent order payment request is processed abnormally, the receiving payment management device further includes:
receiving an order polling request triggered by the payment management equipment aiming at the sent order payment request;
polling the processing state of the order payment request according to the order identification contained in the order polling request, and returning a polling result to the payment management equipment, so that the payment management equipment can judge whether the sent order payment request is processed abnormally or not according to the polling result.
Optionally, after the order record stored in the order database is marked as a cancelled state, the method further includes:
and sending a revocation success notification to the payment management device, so that the payment management device displays a prompt page corresponding to the revocation success notification.
According to still another aspect of the present invention, there is provided an exception handling method for an order payment request, including:
generating an order payment request according to the payment code, and sending the order payment request to an order processing server;
judging whether the sent order payment request is processed abnormally or not;
if yes, sending an order form updating request to the order form processing server, so that the order form processing server inquires whether an order form record matched with the order form identification is stored in a preset order form database according to the order form identification contained in the order form updating request, and sending a cancellation request containing the order form identification to a payment server when the inquiry result is yes and the payment state of the order form record is to be paid.
Optionally, if so, after sending the order query request to the order processing server, the method further includes:
and receiving a revocation success notification returned by the order processing server, and displaying a corresponding prompt page according to the revocation success notification.
Optionally, the determining whether the sent order payment request is abnormal includes:
judging whether a payment success notice returned by aiming at the sent order payment request is received or not;
if not, triggering an order polling request aiming at the sent order payment request, so that the order processing server polls the processing state of the order payment request according to an order mark contained in the order polling request;
and determining whether the sent order payment request is processed abnormally according to the processing state returned by the order processing server.
According to still another aspect of the present invention, there is provided an order processing server including:
the order-making request receiving module is suitable for receiving an order-making request triggered by payment management equipment when determining that the sent order payment request is abnormal to process, and acquiring an order identifier contained in the order-making request;
the order record query module is suitable for querying whether an order record matched with the order identification is stored in a preset order database; if so, acquiring the payment state of the order record;
the revocation module is suitable for sending a revocation request containing the order mark to a payment server when the payment state of the order record is determined to be paid, so that the payment server can execute revocation processing on the order record;
and the marking module is suitable for marking the order record stored in the order database as a cancelled state when receiving a cancellation success message returned by the payment server.
Optionally, the revocation module is further adapted to:
marking the order record as a state to be cancelled; and storing the order identifier into a preset interception list to intercept a payment success message returned by the payment server for the order identifier.
Optionally, the forward collision request receiving module is further adapted to:
receiving an order polling request triggered by the payment management equipment aiming at the sent order payment request;
polling the processing state of the order payment request according to the order identification contained in the order polling request, and returning a polling result to the payment management equipment, so that the payment management equipment can judge whether the sent order payment request is processed abnormally or not according to the polling result.
Optionally, the marking module is further adapted to:
and sending a revocation success notification to the payment management device, so that the payment management device displays a prompt page corresponding to the revocation success notification.
According to still another aspect of the present invention, there is provided a payment management apparatus including:
the payment request generation module is suitable for generating an order payment request according to the payment code and sending the order payment request to the order processing server;
the judging module is suitable for judging whether the sent order payment request is processed abnormally or not;
and if so, sending an order correction request to the order processing server, so that the order processing server inquires whether an order record matched with the order identifier exists in a preset order database according to the order identifier contained in the order correction request, and sends a cancellation request containing the order identifier to a payment server when the inquiry result is yes and the payment state of the order record is to be paid.
Optionally, the punching module is further adapted to:
and receiving a revocation success notification returned by the order processing server, and displaying a corresponding prompt page according to the revocation success notification.
Optionally, the determining module is specifically adapted to:
judging whether a payment success notice returned by aiming at the sent order payment request is received or not;
if not, triggering an order polling request aiming at the sent order payment request, so that the order processing server polls the processing state of the order payment request according to an order mark contained in the order polling request;
and determining whether the sent order payment request is processed abnormally according to the processing state returned by the order processing server.
According to still another aspect of the present invention, there is provided an exception handling system for an order payment request, including: the order processing server and the payment management device.
Optionally, the system further comprises a payment server;
the payment server is used for inquiring whether an order payment record corresponding to the order identification is stored in a preset order payment data table or not; if not, creating a revocation list record corresponding to the order identification, and executing revocation processing aiming at the revocation list record;
and the revocation list record is used for intercepting an order payment request which is forwarded by an order processing server and contains the order identification.
Optionally, the payment server is specifically configured to create a revocation list record corresponding to the order identifier in a preset cache space;
and executing elimination processing aiming at the revocation list records stored in the preset cache space when a preset elimination period arrives.
Optionally, the payment server is specifically configured to, when an order payment record corresponding to the order identifier is stored in a preset order payment data table, query a payment state of the order payment record corresponding to the order identifier; closing the order transaction corresponding to the order payment record when the payment state of the order payment record corresponding to the order identification is determined to be unpaid; and when the payment state of the order payment record corresponding to the order identification is determined to be paid, executing refund processing aiming at the order payment record.
According to still another aspect of the present invention, there is provided an electronic apparatus including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the exception handling method of the order payment request.
According to still another aspect of the present invention, there is provided a computer storage medium, in which at least one executable instruction is stored, and the executable instruction causes a processor to execute operations corresponding to the exception handling method for the order payment request.
In the order payment request exception processing method, device, server and system provided by the invention, the order identifier included in the order correction request triggered by the payment management device when the sent order payment request is determined to be in exception processing can be obtained, and when the order record matched with the order identifier is stored in the preset order database and the payment state of the order record is to be paid, the cancellation request including the order identifier is sent to the payment server, so that the payment server executes cancellation processing aiming at the order record. Therefore, the method can cancel the order payment request when the order payment request is not processed successfully for a long time, so that the user is prevented from waiting endlessly, and the problem of overlong waiting time of the user caused by the fact that the order cannot be paid in time due to network abnormity is solved. The method can reliably process the abnormal condition of the order payment data caused by various factors such as network reasons or equipment reasons when the order payment data are transmitted among a plurality of network equipment. The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flow chart illustrating an exception handling method for an order payment request according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating an exception handling method for an order payment request according to a second embodiment of the present invention;
fig. 3 is a block diagram illustrating an order processing server according to a third embodiment of the present invention;
fig. 4 shows a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Example one
Fig. 1 is a flowchart illustrating an exception handling method for an order payment request according to an embodiment of the present invention. As shown in fig. 1, the method includes:
step S110: receiving an order correction request triggered by the payment management equipment when determining that the sent order payment request is abnormal, and acquiring an order identification contained in the order correction request.
Wherein the payment managing device, which may also be referred to as merchant managing device, is adapted to generate and send the order payment request. For example, it may be a point of sale (POS) machine or other terminal equipment. Specifically, after the payment management device sends the order payment request, the processing state of the order payment request is continuously tracked, and if it is determined that the sent order payment request is abnormal in processing according to the tracking result, the order correction request is further triggered to perform correction processing for the order. Accordingly, an execution subject, such as an order processing server, in the present invention receives the order correction request, and then obtains an order identifier contained therein, where the order identifier is used to uniquely identify an order.
Step S120: and inquiring whether an order record matched with the order identification is stored in a preset order database.
The preset order database is used for creating corresponding order records according to the received order payment requests. Specifically, each time an order payment request is received, an order identifier included in the order payment request is obtained, and then an order record including the order identifier is created in an order database to manage the state of the order. Correspondingly, in this step, whether an order record matched with the order identifier is stored in a preset order database is inquired according to the order identifier.
Step S130: if so, acquiring the payment state recorded by the order; and when the payment state of the order record is determined to be paid, sending a revocation request containing the order identification to the payment server, so that the payment server executes revocation processing aiming at the order record.
And when the query result is yes, the order processing server is explained to receive and process the order payment request corresponding to the order identification sent by the payment management equipment. Accordingly, the payment status of the order record is further queried, and specifically, a status field may be included in the order record, so as to determine whether the order has completed payment according to a value of the field. When the payment state of the order record is determined to be paid, the order is not paid yet, and at this time, in order to avoid long-time waiting of the user, a cancellation request containing an order identifier is sent to the payment server, so that the payment server executes cancellation processing according to the order record.
Step S140: and when a revocation success message returned by the payment server is received, marking the order record stored in the order database as a revoked state.
And the payment server executes revocation processing according to the received revocation request, and returns a revocation success message after the revocation is successful. Correspondingly, when the execution main body in the invention receives the revocation success message returned by the payment server, the order record stored in the order database is marked as the revoked state, thereby completing the revocation process of the order.
Therefore, in the order payment request exception processing method provided by the invention, the order identifier included in the order correction request triggered by the payment management device when the sent order payment request is determined to be exception is obtained, and when the order record matched with the order identifier is stored in the preset order database and the payment state of the order record is to be paid, the cancellation request including the order identifier is sent to the payment server, so that the payment server executes cancellation processing on the order record. Therefore, the method can cancel the order payment request when the order payment request is not processed successfully for a long time, so that the user is prevented from waiting endlessly, and the problem of overlong waiting time of the user caused by the fact that the order cannot be paid in time due to network abnormity is solved. The method can reliably process the abnormal condition of the order payment data caused by various factors such as network reasons or equipment reasons when the order payment data are transmitted among a plurality of network equipment.
Example II,
Fig. 2 is a flowchart illustrating an exception handling method for an order payment request according to a second embodiment of the present invention. As shown in fig. 2, the method includes:
step S210: and the payment management equipment generates an order payment request according to the payment code, sends the order payment request to the order processing server, and judges whether the sent order payment request is processed abnormally or not.
Specifically, the payment management device generates an order payment request by scanning a payment code presented by the user terminal, and transmits the generated order payment request to the order processing server. The order payment request comprises an order mark, and the order mark runs through each life cycle of the corresponding order and is used for uniquely marking one order.
After the payment management device sends the order payment request, the sending time of the order payment request is recorded. And polling the processing state of the order payment request according to a preset polling strategy. The polling strategy is used for setting information such as polling time interval, polling times, polling total duration and the like. Specifically, after the payment management device sends the order payment request, it is determined whether a payment success notification returned for the sent order payment request is received. Specifically, each time a preset polling time interval is reached, whether a payment success notification returned for the sent order payment request is received or not is judged. If not, triggering an order polling request aiming at the sent order payment request so that the order processing server polls the processing state of the order payment request according to an order mark contained in the order polling request; correspondingly, whether the sent order payment request is processed abnormally is determined according to the processing state returned by the order processing server. When the payment success notification returned by aiming at the sent order payment request is judged not to be received, whether the current polling frequency reaches the upper limit of the preset polling frequency can be further judged, and if not, the order polling request is triggered again aiming at the sent order payment request; if yes, directly determining that the order payment request is abnormal in processing.
In addition, after receiving an order polling request triggered by the payment management device for the sent order payment request, the order processing server polls the processing state of the order payment request according to an order identifier contained in the order polling request, and returns a polling result to the payment management device, so that the payment management device can judge whether the sent order payment request is abnormal or not according to the polling result. After receiving the order polling request, the order processing server can inquire whether a corresponding order record exists in a preset order database according to an order identifier in the order polling request, and returns a payment success notification when the payment state of the corresponding order record is successful; and if the corresponding order record does not exist in the preset order database, or the payment state is unpaid although the corresponding order record exists, returning a polling result of the type of unsuccessful payment. Correspondingly, if the payment management device still does not receive the payment success notification when the preset upper limit of the polling times or the upper limit of the total polling duration is reached, it is determined that the order payment request is processed abnormally.
Of course, the payment management device may also determine whether the sent order payment request is abnormal through other various manners, as long as the user can be prevented from waiting for a long time, which is not limited in the present invention.
Step S220: when the payment management device judges that the sent order payment request is processed abnormally, the order correction request is sent to an order processing server, and the order processing server receives the order correction request triggered by the payment management device and acquires an order identifier contained in the order correction request.
The order correcting request is used for executing processes such as account checking, error correction and the like aiming at the order. And the order processing server receives and acquires the order identification contained in the order correction request. The order payment request and the order correction request contain the same order identification for the same order.
In addition, optionally, in this embodiment, in order to improve the accuracy of the punching process, a punching timing expiration period is further provided, which may be 10 minutes, for example. Correspondingly, after the order processing server receives the order form correcting request, whether the order form correcting time period exceeds the order form correcting time period is further judged according to the current time and the order form generating time contained in the order form correcting request, and if yes, a prompt message of correcting failure is returned; if not, the order form correcting request is processed normally.
Step S230: and inquiring whether an order record matched with the order identification is stored in a preset order database.
The preset order database may be integrated inside the order processing server or may be independent of the order processing server. The order database is used for creating corresponding order records according to the received order payment requests. Specifically, each time the order processing server receives an order payment request, the order identifier included in the order payment request is obtained, and then an order record including the order identifier is created in an order database to manage the state of the order. Wherein, the order can be tracked and managed through the order record. Correspondingly, in this step, whether an order record matched with the order identifier is stored in a preset order database is inquired according to the order identifier.
Step S240: if so, acquiring the payment state recorded by the order; and when the payment state of the order record is determined to be paid, sending a revocation request containing the order identification to the payment server, so that the payment server executes revocation processing aiming at the order record.
And when the query result is yes, the order processing server is explained to receive and process the order payment request corresponding to the order identification sent by the payment management equipment. Accordingly, the payment status of the order record is further queried. In particular, a status field may be included in the order record to determine whether the order has completed payment based on the value of the field. Wherein, the value of the status field is determined by the following method: and after the order processing server creates a corresponding order record according to the order payment request, setting the value of the state field contained in the order record as 'to be paid'. And then, the order processing server forwards the order payment request to the payment server for payment processing by the payment server, and when receiving a payment success message returned by the payment server, the order processing server updates the value of the status field in the order record to be 'paid'. It can be seen that when the order processing server does not receive the payment success message from the payment server, the value of the field is "to be paid". Correspondingly, when the payment state of the order record is determined to be paid, the order record indicates that the order is not yet paid, and at this time, in order to avoid long-time waiting of the user, the order processing server sends a cancellation request containing an order identifier to the payment server, so that the payment server performs cancellation processing on the order record.
Step S250: marking the order record as a state to be cancelled; and storing the order identification into a preset interception list to intercept a payment success message returned by the payment server aiming at the order identification.
Specifically, after the order processing server sends a revocation request including an order identifier to the payment server, the order record is further marked as a to-be-revoked state, which may be specifically implemented by updating a value of the state field, or a tag may be set for the order record.
The inventor finds that due to the network delay problem, after a revocation request containing an order identifier is sent to a payment server, a payment success message from the payment server still can be received. At this time, in order to avoid repeated processing, a payment success message returned by the payment server in a delayed mode needs to be intercepted. Therefore, when the payment success message from the payment server is received, whether to intercept the payment success message is determined according to the order identification stored in the interception list. The interception list can be stored in a cache, and the data of the interception list in the cache is periodically eliminated, so that the system overhead is saved.
Step S260: the payment server performs revocation processing for the order record according to the received revocation request.
The payment server can be various network devices such as a third-party payment platform. After receiving the cancellation request, the payment server acquires an order identifier contained in the cancellation request, and inquires whether an order payment record corresponding to the order identifier is stored in a preset order payment data table. The order payment data table is used for storing order payment data, and when the payment server receives an order payment request forwarded by the order processing server, a corresponding order payment record is created in the order payment data table according to the order payment request so as to record the payment state of the order. The order mark contained in the order payment record of the payment server side is consistent with the order mark contained in the order record of the order processing server side, so that each processing link of an order is tracked according to the order mark. Specifically, the following two cases can be classified according to the query result:
in a first case, when the order payment record corresponding to the order identifier is not stored in the preset order payment data table, it indicates that the payment server has not received the order payment request forwarded by the order processing server, or the payment server has just received the order payment request forwarded by the order processing server and has not created a corresponding order payment record, in which case, the payment server creates a revocation list record corresponding to the order identifier to perform revocation processing on the revocation list record. The revocation list record is different from the order payment record in the order payment data table, and is mainly used for executing revocation processing aiming at the order.
In addition, the revocation list record is also used for intercepting order payment requests which are forwarded by the order processing server and contain the order identification. Since in this case, the order payment request containing the order identifier forwarded by the order processing server may arrive at the payment server after the request is cancelled due to the problem of network delay, at this time, the order payment request arriving with delay needs to be intercepted to prevent repeated processing. Specifically, when revocation processing is performed on a revocation list record, the revocation list record is mainly set to a revocation state. Correspondingly, when the order payment request which is forwarded by the order processing server and contains the order identification is subsequently received, the order payment request can be intercepted according to the revocation list record so as to prevent repeated processing. In specific implementation, the process of setting the revocation list record and executing the revocation processing can also be understood as a process of revoking the pipelining, and by revoking the pipelining, the state of the order can be accurately recorded. In addition, in this embodiment, the order identifier may include various information, such as: the payment management equipment comprises equipment identification of the payment management equipment, user identification of the payment user, order generation time, order numbers, business item details corresponding to the orders and the like.
In specific implementation, in order to save overhead, the order processing server creates a revocation list record corresponding to the order identifier in a preset cache space. Since the revocation list record belongs to the temporary record and does not need to be stored for a long time unlike the content in the order database, in the present embodiment, the revocation list record is stored in the preset cache space. In addition, in order to further save space and reduce subsequent processing overhead, in this embodiment, the revocation list records stored in the cache space are further subjected to the elimination processing according to a preset elimination policy. For example, whenever a preset eviction period arrives, eviction processing is performed for a revocation list record that has been stored in a preset cache space. The elimination period may be set according to a regular time period for order processing, for example, may be set to 2 hours. Accordingly, deletion processing is performed for the revocation list records stored in the cache space every 2 hours, so as to save space. In specific implementation, whether the generation time of each revocation list record reaches 2 hours can be judged respectively, and if yes, the revocation list record is deleted; alternatively, in order to improve efficiency, the revocation lists in the cache space may be deleted in batches every 2 hours. In a word, the revocation list records in the cache space can automatically fail after exceeding the preset time period through the elimination strategy.
In a second case, when the order payment record corresponding to the order identifier is already stored in the preset order payment data table, it indicates that the payment server has received and processed the order payment request forwarded by the order processing server, in this case, the order server further queries the payment status of the order payment record corresponding to the order identifier:
and closing the order transaction corresponding to the order payment record when the payment state of the order payment record corresponding to the order identification is determined to be unpaid. And the payment state of the order payment record is used for indicating whether the order has finished the deduction operation, if not, the payment state is unpaid, and at the moment, the order transaction corresponding to the order payment record is directly closed to finish the cancellation operation. This may be the case because the order was intercepted by the wind control server or for other reasons, resulting in a payment failure.
When the payment state of the order payment record corresponding to the order identification is determined to be paid, a refund process is performed for the order payment record. This case shows that the payment server has already been cooperated with a payment device such as a bank server and completed the deduction operation, but has not yet successfully returned a payment success message to the order processing server. At this time, in order to avoid an account error, it is necessary to perform a refund process for the completed deduction operation, thereby implementing a withdrawal operation of the order payment request.
In addition, in the first case, since the order payment request forwarded by the order processing server has not been received yet, there is still a possibility that the order payment request is received in a delayed manner in a subsequent process due to problems such as network delay, and in order to prevent repeated processing problems caused by this, in this embodiment, when the order payment request forwarded by the order processing server is received, the order identifier included in the order payment request received this time is obtained; and matching the order mark contained in the received order payment request with the order mark contained in the established revocation list record in the cache space, and judging whether to intercept the order payment request received this time from the order processing server according to the matching result. In particular implementation, the matching operation may be performed for each received order payment request. Or, when the created revocation list record in the preset cache space is small, in order to save system overhead, a monitoring thread may be started for the revocation list record after every new revocation list record is added in the preset cache space, where the monitoring thread is configured to monitor each subsequently received order payment request after the revocation list record is created, and match the order identifier therein with the order identifier in the newly added revocation list record. The life cycle of the monitoring thread can be flexibly set, for example, the life cycle can be set to exist within 1 hour after the revocation list record is created, and the monitoring thread is automatically destroyed after 1 hour.
In addition, considering that the number of order payment requests is large, it takes a lot of time to match each order payment request one by one, resulting in processing delay. In order to solve the above problem, in this embodiment, the received order payment request is further filtered, and only the filtered order payment request is matched, so that the processing delay is reduced. In the specific screening, the screening can be performed according to the equipment identifier of the order processing server, and/or the order generation time and other information. Specifically, the order identifier further includes an equipment identifier of the order processing server and/or an order generation time, and the cancellation record further includes the order identifier and the equipment identifier of the order processing server and/or the order generation time included in the order identifier. Correspondingly, screening the received order payment request according to the equipment identifier of the order processing server and/or the order generation time in the order identifier contained in the created revocation list record; and matching the order identification contained in the screened order payment request with the order identification contained in the created revocation list record. For example, after receiving the order payment request, the device identifier of the order processing server included in the order payment request is obtained, the device identifier is used for identifying the sender of the request, and only when the device identifier included in the order payment request matches the device identifier included in the revocation list record, the order identifiers included in the order payment request and the revocation list record are further compared. Since the order payment request which is not received and corresponds to the revocation list record is necessarily sent by the same order processing server, the order payment requests sent by other order processing servers can be quickly filtered through the equipment identification, and therefore unnecessary matching processes are avoided. For another example, after receiving the order payment request, the order generation time included in the order generation time is obtained first, and only the order payment request whose order generation time meets the preset delay time period can pass the screening, so that the request whose order generation time obviously does not match the generation time of the order payment request corresponding to the revocation list is prevented from being matched. The preset time delay period can be set according to the creation time of the revocation list record, and the preset time period which is earlier than the creation time of the revocation list record is determined as the time delay period so as to screen order payment requests which are delayed and received possibly due to disorder problems.
Step S270: and when a revocation success message returned by the payment server is received, marking the order record stored in the order database as a revoked state.
And the payment server executes revocation processing according to the received revocation request, and returns a revocation success message after the revocation is successful. Correspondingly, when the order processing server receives the revocation success message returned by the payment server, the order record stored in the order database is marked as a revoked state, so that the order revocation process is completed.
Step S280: and the order processing server sends a revocation success notification to the payment management equipment, so that the payment management equipment displays a prompt page corresponding to the revocation success notification.
Specifically, when the payment management device receives a revocation success notification returned by the order processing server, the payment management device displays a corresponding prompt page according to the revocation success notification to prompt the user that the order is successfully revoked, so that the user is prevented from waiting for a long time.
In conclusion, the method can cancel the order payment request when the order payment request is not processed successfully for a long time, so that the user is prevented from waiting endlessly, and the problem of overlong waiting time of the user caused by the fact that the order cannot be paid in time due to network abnormity is solved. In addition, in this embodiment, the revocation list record is stored in the cache space, so that the revocation list record can be automatically eliminated, thereby saving overhead.
EXAMPLE III
Fig. 3 is a schematic structural diagram of an order processing server according to a third embodiment of the present invention, including:
the order-making request receiving module 31 is adapted to receive an order-making request triggered by the payment management device when determining that the sent order payment request is abnormal, and obtain an order identifier included in the order-making request;
the order record query module 32 is adapted to query whether an order record matched with the order identifier is stored in a preset order database; if so, acquiring the payment state of the order record;
the revocation module 33 is adapted to send a revocation request including the order identifier to a payment server when the payment status of the order record is determined to be paid, so that the payment server executes revocation processing on the order record;
the marking module 34 is adapted to mark the order record stored in the order database as a cancelled state when receiving a cancellation success message returned by the payment server.
Optionally, the revocation module is further adapted to:
marking the order record as a state to be cancelled; and storing the order identifier into a preset interception list to intercept a payment success message returned by the payment server for the order identifier.
Optionally, the forward collision request receiving module is further adapted to:
receiving an order polling request triggered by the payment management equipment aiming at the sent order payment request;
polling the processing state of the order payment request according to the order identification contained in the order polling request, and returning a polling result to the payment management equipment, so that the payment management equipment can judge whether the sent order payment request is processed abnormally or not according to the polling result.
Optionally, the marking module is further adapted to:
and sending a revocation success notification to the payment management device, so that the payment management device displays a prompt page corresponding to the revocation success notification.
In addition, another embodiment of the present invention further provides a payment management apparatus, including:
the payment request generation module is suitable for generating an order payment request according to the payment code and sending the order payment request to the order processing server;
the judging module is suitable for judging whether the sent order payment request is processed abnormally or not;
and if so, sending an order correction request to the order processing server, so that the order processing server inquires whether an order record matched with the order identifier exists in a preset order database according to the order identifier contained in the order correction request, and sends a cancellation request containing the order identifier to a payment server when the inquiry result is yes and the payment state of the order record is to be paid.
Optionally, the punching module is further adapted to:
and receiving a revocation success notification returned by the order processing server, and displaying a corresponding prompt page according to the revocation success notification.
Optionally, the determining module is specifically adapted to:
judging whether a payment success notice returned by aiming at the sent order payment request is received or not;
if not, triggering an order polling request aiming at the sent order payment request, so that the order processing server polls the processing state of the order payment request according to an order mark contained in the order polling request;
and determining whether the sent order payment request is processed abnormally according to the processing state returned by the order processing server.
In addition, another embodiment of the present invention further provides an exception handling system for an order payment request, including: the order processing server and the payment management device are provided.
Optionally, the system further comprises a payment server; the payment server is used for inquiring whether an order payment record corresponding to the order identification is stored in a preset order payment data table or not; if not, creating a revocation list record corresponding to the order identification, and executing revocation processing aiming at the revocation list record; and the revocation list record is used for intercepting an order payment request which is forwarded by an order processing server and contains the order identification.
Optionally, the payment server is specifically configured to create a revocation list record corresponding to the order identifier in a preset cache space;
and executing elimination processing aiming at the revocation list records stored in the preset cache space when a preset elimination period arrives.
Optionally, the payment server is specifically configured to, when an order payment record corresponding to the order identifier is stored in a preset order payment data table, query a payment state of the order payment record corresponding to the order identifier; closing the order transaction corresponding to the order payment record when the payment state of the order payment record corresponding to the order identification is determined to be unpaid; and when the payment state of the order payment record corresponding to the order identification is determined to be paid, executing refund processing aiming at the order payment record.
The specific structure and operation principle of each module described above may refer to the description of the corresponding part in the method embodiment, and are not described herein again.
Example four
An embodiment of the present application provides a non-volatile computer storage medium, where the computer storage medium stores at least one executable instruction, and the computer executable instruction may execute the exception handling method for the order payment request in any method embodiment. The executable instructions may be specifically configured to cause a processor to perform respective operations corresponding to the above-described method embodiments.
EXAMPLE five
Fig. 4 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.
As shown in fig. 4, the electronic device may include: a processor (processor)402, a Communications Interface 404, a memory 406, and a Communications bus 408.
Wherein:
the processor 402, communication interface 404, and memory 406 communicate with each other via a communication bus 408.
A communication interface 404 for communicating with network elements of other devices, such as clients or other servers.
The processor 402 is configured to execute the program 410, and may specifically execute relevant steps in the foregoing exception handling method embodiment for an order payment request.
In particular, program 410 may include program code comprising computer operating instructions.
The processor 402 may be a central processing unit CPU or an application Specific Integrated circuit asic or one or more Integrated circuits configured to implement embodiments of the present invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And a memory 406 for storing a program 410. Memory 406 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The program 410 may specifically be configured to enable the processor 402 to perform the respective operations in the above-described method embodiments.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a voice input information based lottery system according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Claims (19)
1. An exception processing method for an order payment request is applicable to an order processing server and comprises the following steps:
receiving an order form correcting request triggered by payment management equipment when determining that the sent order form payment request is abnormal, and acquiring an order form identifier contained in the order form correcting request;
inquiring whether an order record matched with the order mark is stored in a preset order database; if so, acquiring the payment state of the order record;
when the payment state of the order record is determined to be paid, sending a revocation request containing the order identification to a payment server, so that the payment server executes revocation processing aiming at the order record;
when a revocation success message returned by the payment server is received, marking the order record stored in the order database as a revoked state; wherein, after sending the revocation request including the order identifier to the payment server, the method further includes: marking the order record as a state to be cancelled; storing the order identification into a preset interception list; when a payment success message from the payment server is received, determining whether to intercept the payment success message according to an order mark stored in an interception list; the interception list is stored in the cache and periodically eliminates the interception list data in the cache;
before the receiving of the order correction request triggered by the payment management device when determining that the sent order payment request is processed abnormally, the method further includes:
receiving an order polling request triggered by the payment management equipment aiming at the sent order payment request;
polling the processing state of the order payment request according to the order identification contained in the order polling request, and returning a polling result to the payment management equipment, so that the payment management equipment can judge whether the sent order payment request is processed abnormally or not according to the polling result.
2. The method of claim 1, wherein after sending the revocation request including the order identification to the payment server, further comprising:
the payment server inquires whether an order payment record corresponding to the order identification is stored in a preset order payment data table;
if not, creating a revocation list record corresponding to the order identification, and executing revocation processing aiming at the revocation list record;
and the revocation list record is used for intercepting an order payment request which is forwarded by an order processing server and contains the order identification.
3. The method of claim 2, wherein the creating a revocation list record corresponding to the order identification comprises: creating a revocation list record corresponding to the order identification in a preset cache space;
and executing elimination processing aiming at the revocation list records stored in the preset cache space when a preset elimination period arrives.
4. The method according to claim 2, wherein after the payment server queries whether an order payment record corresponding to the order identifier is stored in a preset order payment data table, the method further comprises:
if yes, inquiring the payment state of the order payment record corresponding to the order identification;
closing the order transaction corresponding to the order payment record when the payment state of the order payment record corresponding to the order identification is determined to be unpaid;
and when the payment state of the order payment record corresponding to the order identification is determined to be paid, executing refund processing aiming at the order payment record.
5. The method of any of claims 1-4, wherein after marking the order record stored in the order database as cancelled, further comprising:
and sending a revocation success notification to the payment management device, so that the payment management device displays a prompt page corresponding to the revocation success notification.
6. An exception processing method for order payment requests is applicable to payment management equipment and comprises the following steps:
generating an order payment request according to the payment code, and sending the order payment request to an order processing server;
judging whether the sent order payment request is processed abnormally or not;
if yes, sending an order form updating request to the order form processing server, so that the order form processing server inquires whether an order form record matched with the order form identifier already exists in a preset order form database according to the order form identifier contained in the order form updating request, and when the inquiry result is yes and the payment state of the order form record is to be paid, sending a cancellation request containing the order form identifier to a payment server and marking the order form record as a state to be cancelled; storing the order identification into a preset interception list; when the order processing server receives a payment success message from the payment server, whether the payment success message is intercepted or not is determined according to an order mark stored in the interception list; the interception list is stored in the cache and periodically eliminates the interception list data in the cache;
wherein the judging whether the sent order payment request is abnormal includes:
judging whether a payment success notice returned by aiming at the sent order payment request is received or not;
if not, triggering an order polling request aiming at the sent order payment request, so that the order processing server polls the processing state of the order payment request according to an order mark contained in the order polling request;
and determining whether the sent order payment request is processed abnormally according to the processing state returned by the order processing server.
7. The method of claim 6, wherein if the request is received, after sending the order query request to the order processing server, further comprising:
and receiving a revocation success notification returned by the order processing server, and displaying a corresponding prompt page according to the revocation success notification.
8. An order processing server comprising:
the order-making request receiving module is suitable for receiving an order-making request triggered by payment management equipment when determining that the sent order payment request is abnormal to process, and acquiring an order identifier contained in the order-making request;
the order record query module is suitable for querying whether an order record matched with the order identification is stored in a preset order database; if so, acquiring the payment state of the order record;
the revocation module is suitable for sending a revocation request containing the order mark to a payment server when the payment state of the order record is determined to be paid, so that the payment server can execute revocation processing on the order record;
the marking module is suitable for marking the order record stored in the order database as a cancelled state when receiving a cancellation success message returned by the payment server; wherein the revocation module is further adapted to:
marking the order record as a state to be cancelled; storing the order identification into a preset interception list; when a payment success message from the payment server is received, determining whether to intercept the payment success message according to an order mark stored in an interception list; the interception list is stored in the cache and periodically eliminates the interception list data in the cache;
wherein the forward request receiving module is further adapted to: receiving an order polling request triggered by the payment management equipment aiming at the sent order payment request; polling the processing state of the order payment request according to the order identification contained in the order polling request, and returning a polling result to the payment management equipment, so that the payment management equipment can judge whether the sent order payment request is processed abnormally or not according to the polling result.
9. The order processing server of claim 8, wherein the marking module is further adapted to:
and sending a revocation success notification to the payment management device, so that the payment management device displays a prompt page corresponding to the revocation success notification.
10. A payment management apparatus comprising:
the payment request generation module is suitable for generating an order payment request according to the payment code and sending the order payment request to the order processing server;
the judging module is suitable for judging whether the sent order payment request is processed abnormally or not;
the order processing server is suitable for inquiring whether an order record matched with the order identifier exists in a preset order database according to the order identifier contained in the order correcting request, and sending a cancellation request containing the order identifier to a payment server and marking the order record as a to-be-cancelled state when the inquiry result is yes and the payment state of the order record is to-be-paid; storing the order identification into a preset interception list; when the order processing server receives a payment success message from the payment server, whether the payment success message is intercepted or not is determined according to an order mark stored in the interception list; the interception list is stored in the cache and periodically eliminates the interception list data in the cache;
wherein the judging module is specifically adapted to:
judging whether a payment success notice returned by aiming at the sent order payment request is received or not;
if not, triggering an order polling request aiming at the sent order payment request, so that the order processing server polls the processing state of the order payment request according to an order mark contained in the order polling request;
and determining whether the sent order payment request is processed abnormally according to the processing state returned by the order processing server.
11. The payment management apparatus of claim 10, wherein the correction module is further adapted to:
and receiving a revocation success notification returned by the order processing server, and displaying a corresponding prompt page according to the revocation success notification.
12. An exception handling system for order payment requests, comprising: the order processing server of any of claims 8-9 and the payment management apparatus of any of claims 10-11.
13. The system of claim 12, wherein the system further comprises a payment server;
the payment server is used for inquiring whether an order payment record corresponding to the order identification is stored in a preset order payment data table or not; if not, creating a revocation list record corresponding to the order identification, and executing revocation processing aiming at the revocation list record;
and the revocation list record is used for intercepting an order payment request which is forwarded by an order processing server and contains the order identification.
14. The system of claim 13, wherein the payment server is specifically configured to create a revocation list record corresponding to the order identification in a preset cache space;
and executing elimination processing aiming at the revocation list records stored in the preset cache space when a preset elimination period arrives.
15. The system according to claim 13, wherein the payment server is specifically configured to query a payment status of the order payment record corresponding to the order identifier when the order payment record corresponding to the order identifier is stored in a preset order payment data table; closing the order transaction corresponding to the order payment record when the payment state of the order payment record corresponding to the order identification is determined to be unpaid; and when the payment state of the order payment record corresponding to the order identification is determined to be paid, executing refund processing aiming at the order payment record.
16. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the exception handling method of the order payment request in any one of claims 1-5.
17. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the exception handling method of the order payment request in any one of claims 6-7.
18. A computer storage medium having stored therein at least one executable instruction for causing a processor to perform operations corresponding to a method of exception handling for an order payment request according to any one of claims 1 to 5.
19. A computer storage medium having stored therein at least one executable instruction for causing a processor to perform operations corresponding to a method of exception handling for an order payment request according to any one of claims 6 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910914132.8A CN110706069B (en) | 2019-09-25 | 2019-09-25 | Exception handling method, device, server and system for order payment request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910914132.8A CN110706069B (en) | 2019-09-25 | 2019-09-25 | Exception handling method, device, server and system for order payment request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110706069A CN110706069A (en) | 2020-01-17 |
| CN110706069B true CN110706069B (en) | 2021-03-02 |
Family
ID=69198085
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910914132.8A Active CN110706069B (en) | 2019-09-25 | 2019-09-25 | Exception handling method, device, server and system for order payment request |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110706069B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111488236B (en) * | 2020-04-16 | 2023-09-05 | 北京思特奇信息技术股份有限公司 | Order exception processing method, server, storage medium and processing device |
| CN111680990A (en) * | 2020-05-09 | 2020-09-18 | 苏州中仑网络科技有限公司 | Payment method and device, cash register and storage medium in weak network environment |
| CN112633968A (en) * | 2020-12-14 | 2021-04-09 | 深圳市智莱科技股份有限公司 | Order processing method of vending machine, vending machine and readable storage medium |
| CN112907237B (en) * | 2021-01-11 | 2023-05-12 | 重庆三果云科技有限公司 | Consumption management system, method and background server |
| CN113852663A (en) * | 2021-08-18 | 2021-12-28 | 北京达佳互联信息技术有限公司 | Network request processing method and device and network request processing system |
| CN113807923B (en) * | 2021-09-23 | 2024-02-09 | 杭州右文网络科技有限公司 | Order processing method and device, electronic equipment and readable storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107392620A (en) * | 2017-06-02 | 2017-11-24 | 口碑控股有限公司 | A kind of method of payment, equipment and device |
| CN107392722A (en) * | 2017-07-27 | 2017-11-24 | 福建中金在线信息科技有限公司 | Order processing method, apparatus, electronic equipment and storage medium |
| CN108280640A (en) * | 2018-01-11 | 2018-07-13 | 口碑(上海)信息技术有限公司 | The payment result page shows method and device |
| CN109074608A (en) * | 2018-07-11 | 2018-12-21 | 威富通科技有限公司 | A kind of reimbursement rushes the method and device of positive hanging pin account clearing |
| CN109255704A (en) * | 2018-08-14 | 2019-01-22 | 阿里巴巴集团控股有限公司 | Information processing method, device, server and computer readable storage medium |
| CN109583873A (en) * | 2017-09-28 | 2019-04-05 | 北京三快在线科技有限公司 | Transaction communications method, server, POS machine and electronic equipment |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2001229321A (en) * | 2000-02-16 | 2001-08-24 | Nec Corp | Method for receiving and sending merchandise orders, system therefor and merchandise order-receiving device |
| US20130275241A1 (en) * | 2012-04-16 | 2013-10-17 | Wal-Mart Stores, Inc. | Processing Online Transactions |
| US10817878B2 (en) * | 2015-06-09 | 2020-10-27 | Mastercard International Incorporated | Systems and methods for verifying users, in connection with transactions using payment devices |
| CN109711846A (en) * | 2018-11-26 | 2019-05-03 | 平安科技（深圳）有限公司 | Payment request processing method, device, computer equipment and storage medium |
-
2019
- 2019-09-25 CN CN201910914132.8A patent/CN110706069B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107392620A (en) * | 2017-06-02 | 2017-11-24 | 口碑控股有限公司 | A kind of method of payment, equipment and device |
| CN107392722A (en) * | 2017-07-27 | 2017-11-24 | 福建中金在线信息科技有限公司 | Order processing method, apparatus, electronic equipment and storage medium |
| CN109583873A (en) * | 2017-09-28 | 2019-04-05 | 北京三快在线科技有限公司 | Transaction communications method, server, POS machine and electronic equipment |
| CN108280640A (en) * | 2018-01-11 | 2018-07-13 | 口碑(上海)信息技术有限公司 | The payment result page shows method and device |
| CN109074608A (en) * | 2018-07-11 | 2018-12-21 | 威富通科技有限公司 | A kind of reimbursement rushes the method and device of positive hanging pin account clearing |
| CN109255704A (en) * | 2018-08-14 | 2019-01-22 | 阿里巴巴集团控股有限公司 | Information processing method, device, server and computer readable storage medium |
Non-Patent Citations (3)
| Title |
|---|
| WCF服务编程;洛伊;《WCF服务编程》;20110630;第567-568页 * |
| 全家-支付宝移动支付系统研究与实现;贺星河;《中国优秀硕士学位论文全文数据库 信息科技辑》;20180415;第I138-412页 * |
| 大学信息技术基础;唐建军等;《大学信息技术基础》;20180831;第132-133页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110706069A (en) | 2020-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110706069B (en) | Exception handling method, device, server and system for order payment request | |
| CN110706071B (en) | Exception handling method, device, server and system for order payment request | |
| CN107392722B (en) | Order processing method and device, electronic equipment and storage medium | |
| US11250395B2 (en) | Blockchain-based transaction processing methods and apparatuses and electronic devices | |
| CN110968478B (en) | Log acquisition method, server and computer storage medium | |
| CN111639965B (en) | Integral updating method and device | |
| CN108428074A (en) | A kind of processing method and processing device cancelled an order in order honours an agreement flow | |
| CN110633977A (en) | Payment exception processing method and device and terminal equipment | |
| JP2020064590A (en) | Information processor, information processing method and program | |
| CN110941622A (en) | Data processing method and device | |
| CN109714214B (en) | Server exception handling method and management equipment | |
| CN107819855B (en) | Message distribution method and device | |
| CN110765392A (en) | Data loading method and device, storage medium and terminal | |
| CN111538602A (en) | Message forwarding method and device for message queue | |
| CN109245941B (en) | Service compensation method and device | |
| CN111367921A (en) | Data object refreshing method and device | |
| CN114896337A (en) | Data uplink method, system, equipment and computer readable storage medium | |
| CN110764697B (en) | Data management method and device | |
| CN110782380B (en) | Aviation change information management method and device and storage medium | |
| CN111061744B (en) | Graph data updating method and device, computer equipment and storage medium | |
| WO2020079896A1 (en) | Information processing device, information processing method, and program | |
| CN110489694A (en) | For handling the method and system of high concurrent request | |
| CN111367860A (en) | File refreshing method and device | |
| CN110674156B (en) | Multi-machine room data synchronization method, computing equipment and computer storage medium | |
| CN111639089B (en) | Transaction processing method, transaction processing device, electronic equipment and computer readable 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |