Detailed Description
Mobile payment is a service that allows users to use their mobile terminals (typically cell phones) for financial payments for goods or services consumed. The unit or the individual directly or indirectly sends a payment instruction to financial institutions such as banks through mobile equipment, the Internet or close-range sensing to generate the behaviors of money payment and fund transfer, thereby realizing the mobile payment function. The mobile payment integrates terminal equipment, the Internet, an application provider and a financial institution, and provides financial services such as currency payment and payment for a user.
However, the problem of payment failure still frequently occurs due to the stability of mobile networks and electronic payment systems. For example, due to network fluctuation, the server may not receive the payment request sent by the client, and thus cause a payment failure, and at the same time, the personal funds of the user may be damaged, for example, in the process that the user performs payment at the client, the server has completed the payment operation at the server, and the server returns the payment result to the client, but due to network fluctuation, the client does not receive the payment result returned by the server, and at this time, the client may prompt the user that the payment is failed, and the user performs payment again, and in a practical case, the payment operation is completed at the server, and the personal funds of the user are damaged, which relates to a subsequent refund operation. Therefore, under the condition of payment failure, the specific reasons causing the payment failure are urgently needed to be analyzed, different processing modes are adopted for the specific reasons causing the payment failure to process the payment failure, and support can be provided for the transformation and the upgrading of the electronic payment system subsequently.
As can be seen from the above background art, when a payment failure occurs, at present, only the operation logs of the payment systems distributed on different devices can be manually searched and analyzed afterwards, the specific reason of the payment failure is located, and a corresponding processing manner is adopted for the payment failure according to the specific reason of the payment failure. Because the operation logs are distributed on different devices, much time and energy are needed to be consumed for manually searching and analyzing specific reasons of payment failure, and therefore the payment failure cannot be processed in a corresponding processing mode in time.
In view of the above problems, embodiments of the present disclosure provide a technical solution, which can immediately locate a specific reason of a payment failure in a payment process of a user, set a corresponding processing manner for the payment failure according to a classification to which the specific reason of the payment failure belongs, and display the specific reason of the payment failure, so that an operator processes the payment failure according to the set processing manner, thereby avoiding manually searching and analyzing operation logs of payment systems distributed on different devices, saving time and energy of operation and maintenance personnel, and timely processing the payment failure.
Specifically, the technical solutions provided in the embodiments of the present specification are as follows:
monitoring the processing state of the payment process in each processing link for a plurality of processing links included in the payment process; when the processing state of the current processing link is monitored to meet a preset condition, associating the processing state of the current processing link with the processing state of a processing link before the current processing link, wherein the current processing link is any processing link included in the payment process; determining the reason of the payment failure according to the processing state of the current processing link after the association and the processing state of the processing link before the current processing link; determining a classification to which a reason for the payment failure belongs; and setting a corresponding processing mode for the payment failure according to the classification of the reason of the payment failure so that the operation and maintenance personnel can process the payment failure according to the set processing mode.
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.
As shown in fig. 1, an implementation flowchart of a payment failure processing method provided in the embodiment of the present specification may specifically include the following steps:
s101, monitoring the processing state of the payment process in each processing link for a plurality of processing links included in the payment process;
the payment process includes a plurality of processing links, and for a relatively common payment process, such as a payment interaction process between a client and a server, as shown in fig. 2, the payment process may include: a user initiates a payment operation at a client, for example, initiates the payment operation at a payer client; generating a payment request at a client; the client sends the payment request to a server, such as a payment server; the server receives a payment request sent by the client; the server processes the payment request, wherein the processing can be order generation, payment and the like; the server returns the processing result of the payment request to the client; and the client receives a processing result of the payment request returned by the server.
In the embodiment of the present specification, a monitor is disposed in each processing link of the payment flow, and can monitor the processing state of the payment flow in each processing link according to the payment identifier, generate a payment serial number corresponding to each transaction, and monitor the processing state of the payment flow in each processing link for the transaction according to the payment serial number. For example, whether a payment request is normally generated at the client is monitored according to the payment serial number, whether the payment request is sent out by the client is monitored, whether the payment request is received by the server is monitored, and the like. It means that for a plurality of processing links included in the payment process, the processing state of each transaction in each processing link can be monitored according to the payment serial number. It should be noted that the processing status may represent different meanings at each processing stage, for example, at the stage of generating the payment request, the processing status may be success or failure of generating the payment request, and at the stage of processing the payment request, the processing status may be success or failure of processing.
S102, when it is monitored that the processing state of the current processing link meets a preset condition, associating the processing state of the current processing link with the processing state of a processing link before the current processing link, wherein the current processing link is any one of the processing links included in the payment process;
through the steps in S101, in the payment processing stage, the processing state of each processing link is monitored, and when it is monitored that the processing state of the current processing link meets the preset condition, a payment failure processing mechanism is triggered. The preset condition is related to a processing link of the payment process, for example, if the current processing link is a processing link of the payment request, the preset condition may be a processing failure, for example, if the current processing link is a processing result of the payment request returned to the client link, the preset condition may be a return failure.
And after the payment failure processing mechanism is triggered, associating the processing state of the current processing link with the processing state corresponding to the processing link before the current processing link. And describing a complete payment failure scene by associating the processing state of the current processing link with the processing state corresponding to the processing link before the current processing link.
When the processing state of the current processing link is monitored to meet the preset condition, the processing state of the current processing link and the processing state of the processing link before the current processing link are associated according to the payment identifier of the current processing link. The payment identifier can be a payment serial number, which means that the processing state of the current processing link and the processing state of the previous processing link of the payment process can be connected in series according to the payment serial number, and a foundation is laid for subsequently determining the reason of payment failure.
S103, determining the reason of payment failure according to the processing state of the current processing link after correlation and the processing state of the processing link before the current processing link;
for the correlation result in S102, the reason of the payment failure may be determined according to the processing state of the current processing link and the processing state of the processing link before the current processing link.
For example, in the payment flow shown in fig. 2, in a processing link (processing result returning link) that returns a processing result of the payment request to the client, a result that the server returns the processing result of the payment request to the client is a return success, and in a processing link (processing result receiving link) that the client receives the processing result of the payment request, the client does not receive the processing result of the payment request returned by the server, and according to a processing state of the processing result receiving link and a processing state of the processing result returning link, it may be determined that a cause of the payment failure is that the client does not receive the processing result of the payment request returned by the server, and a factor of the result may be network fluctuation.
S104, determining the classification of the reason of the payment failure;
for the reason of the payment failure determined in S103, determining a classification to which the reason of the payment failure belongs, where the specific manner of determining the classification to which the reason of the payment failure belongs is: in the preset payment failure reason classification table, the reason of the payment failure is searched in each class to determine the class of the reason of the payment failure, wherein the reason of the payment failure can be classified according to the preset classification rule to generate the preset payment failure reason classification table.
The reason for the payment failure is classified according to a preset classification rule to generate a preset classification table for the reason for the payment failure, for example, as shown in the payment process shown in fig. 2, the reason for the payment failure can be classified into 3 categories, the processing result of the payment request returned by the server fails, the processing result of the payment request not received by the client is classified into C category, the payment request processing failure of the server is classified into B category, the rest of the previous links are classified into a category a, in addition, the payment process involves calling an external service (bank side), the calling failure is classified into D category, and the reason for the payment failure can be classified into 4 categories.
And in a preset payment failure reason classification table, searching the reason of the payment failure in each class to determine the class to which the reason of the payment failure belongs. For example, if the reason of the payment failure is the processing result that the client does not receive the payment request, the reason of the payment failure may be sequentially searched in the above-mentioned class a, class B, and class C, and it is determined that the reason of the payment failure belongs to the class C.
And S105, setting a corresponding processing mode for the payment failure according to the classification of the reason of the payment failure, so that the operation and maintenance personnel can process the payment failure according to the set processing mode.
And determining a processing mode corresponding to the classification to which the reason of the payment failure belongs according to the classification to which the reason of the payment failure determined in the step S104 belongs, and setting a corresponding processing mode for the payment failure so that the operation and maintenance personnel can process the payment failure according to the set processing mode.
For example, it is determined that the reason for the payment failure belongs to class C, the processing mode corresponding to class C is a refund operation, where class C includes a processing result failure that the server returns the payment request and a processing result that the client does not receive the payment request, but a deduction operation has actually occurred in the payment request processing link, and the payment failure is caused by the reason in class C, so the processing mode corresponding to class C is the refund operation, and a refund operation is correspondingly set for the payment failure, so that the operation and maintenance staff subsequently executes the refund operation.
For another example, it is determined that the reason for the payment failure belongs to class D, where the processing method corresponding to class D is a call link detection operation of the external service, and correspondingly, a call link detection operation of the external service is set for the payment failure, so that the operation and maintenance staff subsequently performs the call link detection operation of the external service.
On the basis of the above method, as shown in fig. 3, the technical solution provided by the embodiment of the present specification may further include:
and S106, displaying the reason of the payment failure and a corresponding processing mode set for the payment failure.
The reason of the payment failure and the corresponding processing mode set for the payment failure can be displayed in real time, explanation data can be provided for customer service subsequently, the specific reason of the payment failure and the corresponding processing measures can be explained, the real reason of the payment failure can be reflected to the user correspondingly in real time, the user can really know the real reason of the payment failure, and the payment experience of the user can be improved.
Through the above description of the technical solution provided by the embodiment of the present specification, the specific reason of the payment failure can be located immediately in the payment process of the user, the corresponding processing mode is set for the payment failure according to the classification to which the specific reason of the payment failure belongs, and the specific reason of the payment failure is displayed, so that the operator can process the payment failure according to the set processing mode, thereby avoiding manually searching and analyzing the operation logs of the payment systems distributed on different devices, saving the time and energy of the operation and maintenance personnel, and timely processing the payment failure.
With respect to the foregoing method embodiment, an embodiment of this specification further provides a payment failure processing apparatus, as shown in fig. 4, which may include: a status listening module 410, a status associating module 420, a reason determining module 430, a classification determining module 440, and a setting module 450.
A state monitoring module 410, configured to monitor, for multiple processing links included in the payment flow, a processing state of the payment flow in each processing link;
a state association module 420, configured to associate a processing state of a current processing link with a processing state of a processing link before the current processing link when it is monitored that the processing state of the current processing link satisfies a preset condition, where the current processing link is any processing link included in the payment flow;
a reason determining module 430, configured to determine a reason for the payment failure according to the processing state of the current processing link after the association and the processing state of the processing link before the current processing link;
a classification determination module 440, configured to determine a classification to which a reason for the payment failure belongs;
the setting module 450 is configured to set a corresponding processing mode for the payment failure according to the classification to which the reason of the payment failure belongs, so that the operation and maintenance staff can process the payment failure according to the set processing mode.
According to a specific embodiment provided in this specification, the state association module 420 is specifically configured to:
and when the processing state of the current processing link is monitored to meet the preset condition, associating the processing state of the current processing link with the processing state of the processing link before the current processing link according to the payment identifier of the current processing link.
According to a specific embodiment provided in the present specification, the classification determining module 440 is specifically configured to:
and searching the reasons of the payment failure in each class in a preset payment failure reason classification table to determine the classification of the reasons of the payment failure, wherein the reasons of the payment failure are classified according to a preset classification rule to generate the preset payment failure reason classification table.
According to a specific embodiment provided in this specification, the setting module 450 is specifically configured to:
determining a processing mode corresponding to the classification to which the reason of the payment failure belongs;
and setting the corresponding processing mode for the payment failure so that the operation and maintenance personnel can process the payment failure according to the set processing mode.
According to a specific embodiment provided in this specification, the apparatus further includes:
and the display module is used for displaying the reason of the payment failure and the corresponding processing mode set for the payment failure.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
Through the above description of the technical solution provided by the embodiment of the present specification, the specific reason of the payment failure can be located immediately in the payment process of the user, the corresponding processing mode is set for the payment failure according to the classification to which the specific reason of the payment failure belongs, and the specific reason of the payment failure is displayed, so that the operator can process the payment failure according to the set processing mode, thereby avoiding manually searching and analyzing the operation logs of the payment systems distributed on different devices, saving the time and energy of the operation and maintenance personnel, and timely processing the payment failure.
Embodiments of the present specification further provide a computer device, as shown in fig. 5, the computer device may include: a processor 510, a memory 520, an input/output interface 530, a communication interface 540, and a bus 550. Wherein processor 510, memory 520, input/output interface 530, and communication interface 540 are communicatively coupled to each other within the device via bus 550.
The processor 510 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present specification.
The Memory 520 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 520 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 520 and called by the processor 510 for execution.
The input/output interface 530 is used for connecting an input/output module to realize information input and output. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 540 is used for connecting a communication module (not shown in the figure) to realize communication interaction between the device and other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
Bus 550 includes a pathway to transfer information between various components of the device, such as processor 510, memory 520, input/output interface 530, and communication interface 540.
It should be noted that although the above-mentioned device only shows the processor 510, the memory 520, the input/output interface 530, the communication interface 540 and the bus 550, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
Embodiments of the present specification also provide a computer-readable storage medium, on which a computer program is stored, and the program, when executed by a processor, implements the foregoing payment failure processing method. The method at least comprises the following steps:
a payment failure processing method, the method comprising:
monitoring the processing state of the payment process in each processing link for a plurality of processing links included in the payment process;
when the processing state of the current processing link is monitored to meet a preset condition, associating the processing state of the current processing link with the processing state of a processing link before the current processing link, wherein the current processing link is any processing link included in the payment process;
determining the reason of the payment failure according to the processing state of the current processing link after the association and the processing state of the processing link before the current processing link;
determining a classification to which a reason for the payment failure belongs;
and setting a corresponding processing mode for the payment failure according to the classification of the reason of the payment failure so that the operation and maintenance personnel can process the payment failure according to the set processing mode.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present disclosure. And part or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is only a specific embodiment of the embodiments of the present disclosure, and it should be noted that, for those skilled in the art, a plurality of modifications and decorations can be made without departing from the principle of the embodiments of the present disclosure, and these modifications and decorations should also be regarded as the protection scope of the embodiments of the present disclosure.