An exception handling method, device, electronic device and computer-readable medium

Abstract

The present application discloses an exception handling method, apparatus, electronic device, and computer-readable medium, relating to the technical field of the Internet of Things. A specific implementation manner includes: in response to an exception handling request, obtaining a corresponding user identifier and an exception type identifier; in response to the exception type identifier corresponding to insufficient balance, obtaining the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identifier, and in response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, calling a financing program to perform a financing payment based on the amount to be deducted; in response to the successful financing payment, determining a gate identifier, and then calling a gate opening program to perform a gate opening processing process based on the gate identifier; in response to the successful gate opening, generating a supplementary payment prompt message based on the amount to be deducted and outputting it. It improves the intelligent exception handling method, reduces the situations that need to be manually processed when the payment fails, reduces the pressure on customer service, and improves the gate opening speed and passing efficiency when there is a deduction exception.

Description

Technical Field

[0001] This application relates to the field of Internet of Things technology, and in particular, to an exception handling method, apparatus, electronic device, and computer-readable medium. Background Art

[0002] Judging abnormal wallet balance accounts, etc. before face swiping to open the gate will lead to a long transaction link, and it is easy to cause problems such as slow gate opening speed and low passing efficiency due to network jitter, insufficient wallet balance, account anomalies, etc. For face swiping to travel and deducting fees after passing through the gate, a series of abnormal deductions will occur due to account anomalies, insufficient wallet balance, response timeouts, etc., resulting in slow gate opening speed and low passing efficiency. Summary of the Invention

[0003] In view of this, embodiments of the present application provide an exception handling method, apparatus, electronic device, and computer-readable medium, which can solve the problems of slow gate opening speed and low passing efficiency caused by existing abnormal deductions.

[0004] To achieve the above object, according to one aspect of the embodiments of the present application, an exception handling method is provided, including:

[0005] In response to an exception handling request, obtain the corresponding user identifier and exception type identifier;

[0006] In response to the exception type identifier corresponding to insufficient balance, obtain the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identifier. In response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, call the advance payment program to perform advance payment based on the amount to be deducted;

[0007] In response to the successful advance payment, determine the gate identifier, and then call the gate opening program to perform the gate opening process based on the gate identifier;

[0008] In response to the successful gate opening, generate a supplementary payment prompt message based on the amount to be deducted and output it.

[0009] Optionally, after obtaining the corresponding user identifier and exception type identifier, the method further includes:

[0010] Obtain the order identifier corresponding to the user identifier. In response to the exception type identifier corresponding to an order repetition, determine whether the time interval for initiating the repeated order is within a preset time period. If so, return an order repetition error message. If not, call the successful transaction record. In response to the order identifier being in the successful transaction record, return an order payment success message. In response to the order identifier not being in the successful transaction record, initiate a payment transaction based on the order identifier to the backend.

[0011] Optionally, after obtaining the corresponding user identifier and exception type identifier, the method further includes:

[0012] Obtain the amount to be deducted corresponding to the exception handling request, and set the retry time interval and number of retries in response to the exception type identifier corresponding to the payment response timeout or network jitter;

[0013] Execute the transaction retry process based on the retry interval, number of retries, and amount to be deducted.

[0014] Optionally, after obtaining the corresponding user identifier and exception type identifier, the method further includes:

[0015] In response to the abnormal type identification corresponding to the system failure or batch payment failure, an alarm message is generated, and then the alarm message is sent to a preset processing node.

[0016] Optionally, after obtaining the corresponding user identifier and exception type identifier, the method further includes:

[0017] In response to the abnormal type identifier corresponding to the user corresponding to the user identifier having an account cancellation or the user information corresponding to the user identifier being abnormal, a freezing procedure for the account corresponding to the user identifier is executed.

[0018] Optionally, after obtaining the corresponding user identifier and exception type identifier, the method further includes:

[0019] In response to the abnormal type identifier corresponding to the user corresponding to the user identifier having an account cancelled or the user information corresponding to the user identifier being abnormal, executing a facial recognition blacklisting procedure for the user corresponding to the user identifier;

[0020] In response to receiving a facial recognition recovery request of a user corresponding to the user identifier, a corresponding service processing node is displayed according to the abnormal type identifier.

[0021] Optionally, after obtaining the corresponding user identifier and exception type identifier, the method further includes:

[0022] In response to the abnormal type identification corresponding to the facial recognition timeout, a pop-up window displays an alternative verification method;

[0023] Determine the alternative verification method selected by the user corresponding to the user identifier as the target verification method;

[0024] Execute the corresponding verification process based on the target verification method.

[0025] In addition, the present application also provides an exception handling device, including:

[0026] A first acquisition unit is configured to acquire a corresponding user identifier and an exception type identifier in response to an exception handling request;

[0027] A second acquisition unit is configured to, in response to the exception type identifier corresponding to insufficient balance, acquire the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identifier, and in response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, call the advance payment program to perform advance payment based on the amount to be deducted;

[0028] A gate opening unit, configured to determine a gate identifier in response to a successful advance payment, and then call a gate opening program to execute a gate opening process based on the gate identifier;

[0029] The supplementary payment unit is configured to generate and output supplementary payment prompt information based on the amount to be deducted in response to the gate opening being successful.

[0030] Optionally, the exception handling device further includes a duplicate order processing unit configured to:

[0031] Get the order ID corresponding to the user ID, and in response to the exception type ID corresponding to the order duplication, determine whether the time interval for initiating the repeated order is within the preset time period. If so, return the order duplication error information. Otherwise, call the successful transaction record. In response to the order ID being in the successful transaction record, return the order payment success information. In response to the order ID not being in the successful transaction record, initiate a payment transaction based on the order ID to the backend.

[0032] Optionally, the exception handling device further includes a retry unit configured to:

[0033] Obtain the amount to be deducted corresponding to the exception handling request, and set the retry time interval and number of retries in response to the exception type identifier corresponding to the payment response timeout or network jitter;

[0034] Execute the transaction retry process based on the retry interval, number of retries, and amount to be deducted.

[0035] Optionally, the exception handling device further includes an alarm unit configured to:

[0036] In response to the abnormal type identification corresponding to the system failure or batch payment failure, an alarm message is generated, and then the alarm message is sent to a preset processing node.

[0037] Optionally, the exception handling device further includes a freezing unit configured to:

[0038] In response to the abnormal type identifier corresponding to the user corresponding to the user identifier having an account cancellation or the user information corresponding to the user identifier being abnormal, a freezing procedure for the account corresponding to the user identifier is executed.

[0039] Optionally, the exception handling device further includes a blacklisting unit configured to:

[0040] In response to the abnormal type identifier corresponding to the user corresponding to the user identifier having been deregistered or the user information corresponding to the user identifier being abnormal, executing a facial recognition blacklisting procedure for the user corresponding to the user identifier;

[0041] In response to receiving a facial recognition recovery request of a user corresponding to the user identifier, a corresponding service processing node is displayed according to the abnormal type identifier.

[0042] Optionally, the exception handling device further includes a pop-up window unit configured to:

[0043] In response to the abnormal type identification corresponding to the facial recognition timeout, a pop-up window displays an alternative verification method;

[0044] Determine the alternative verification method selected by the user corresponding to the user identifier as the target verification method;

[0045] Execute the corresponding verification process based on the target verification method.

[0046] In addition, the present application also provides an exception handling electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the one or more processors implement the exception handling method as described above.

[0047] In addition, the present application also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned exception handling method is implemented.

[0048] To achieve the above objective, according to another aspect of the embodiments of the present application, a computer program product is provided.

[0049] A computer program product according to an embodiment of the present application includes a computer program, and when the program is executed by a processor, the exception handling method provided by the embodiment of the present application is implemented.

[0050] One embodiment of the above invention has the following advantages or beneficial effects: the present application obtains the corresponding user identification and exception type identification in response to the exception handling request; in response to the exception type identification corresponding to insufficient balance, obtains the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identification; in response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, calls the advance payment program to perform advance payment based on the amount to be deducted; in response to the success of the advance payment, determines the gate identification, and then calls the gate opening program to perform the gate opening process based on the gate identification; in response to the success of the gate opening, generates and outputs the supplementary payment prompt information based on the amount to be deducted. Perfect the intelligent exception handling method, reduce the need for manual processing when payment fails, reduce customer service pressure, and improve the gate opening speed and traffic efficiency when deduction is abnormal.

[0051] The further effects of the above non-conventional optional methods will be described below in conjunction with specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The drawings are used to better understand the present application and do not constitute an improper limitation of the present application. Among them:

[0053] Figure 1 is a schematic diagram of the main process of an exception handling method according to an embodiment of the present application;

[0054] Figure 2 is a schematic diagram of the main process of an exception handling method according to an embodiment of the present application;

[0055] Figure 3 is a schematic diagram of the main process of an exception handling method according to an embodiment of the present application;

[0056] Figure 4 is a schematic diagram of the main units of an exception handling device according to an embodiment of the present application;

[0057] Figure 5 is an exemplary system architecture diagram to which an embodiment of the present application can be applied;

[0058] Figure 6 is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0059] The following describes exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for clarity and conciseness, descriptions of well-known functions and structures are omitted below. It should be noted that in the technical solutions of the present application, in terms of the collection, analysis, use, transmission, storage, etc. of user personal information, they all comply with the provisions of relevant laws and regulations, are used for legal and reasonable purposes, are not shared, leaked, or sold outside these legal uses, etc., and are subject to the supervision and management of regulatory authorities. Necessary measures should be taken for user personal information to prevent illegal access to such personal information data, ensure that personnel with the right to access personal information data comply with the provisions of relevant laws and regulations, and ensure the security of user personal information. Once these user personal information data are no longer needed, the risk should be minimized by restricting or even prohibiting data collection and / or deleting the data.

[0060] When used, including in certain related applications, user privacy is protected by de-identifying data, such as by removing specific identifiers when used, controlling the amount or specificity of data stored, controlling how data is stored, and / or other methods of de-identification.

[0061] Figure 1 is a schematic diagram of the main process of the exception handling method according to an embodiment of the present application, such as Figure 1 As shown, the exception handling method includes:

[0062] Step S101, in response to an exception handling request, obtaining a corresponding user identifier and an exception type identifier.

[0063] In this embodiment, the execution subject of the exception handling method (for example, it can be a server) can detect whether an exception handling request is received by means of a wired connection or a wireless connection. When the execution subject detects the exception handling request, the user identifier carried in the request can be obtained. For example, the exception handling request can be a subway face recognition exception handling request. The user identifier can be a user account, user name or user nickname corresponding to the user entering and exiting the subway, and the embodiment of the present application does not specifically limit the user identifier. After obtaining the user identifier corresponding to the exception handling request, the execution subject can obtain the exception type identifier. The exception type identifier can be obtained by obtaining and analyzing the exception data corresponding to the exception handling request. Specifically, the exception information library can be called to match the exception data corresponding to the obtained exception handling request with the historical exception data in the exception information library, and then obtain the corresponding exception type identifier. For example, the exception information library can store the corresponding relationship between the historical exception data and the exception type identifier.

[0064] Specifically, after obtaining the corresponding user identifier and exception type identifier, the exception handling method further includes: in response to the exception type identifier corresponding to a system failure or batch payment failure, generating an alarm message, and then sending the alarm message to a preset processing node.

[0065] When there is a clear system failure error, or a large number of payment failures, the execution entity can send an email or SMS alert and handle the emergency immediately. The preset processing node can be an emergency processing node, such as the node corresponding to the on-duty personnel or customer service personnel.

[0066] Specifically, after obtaining the corresponding user identifier and exception type identifier, the method further includes: in response to the exception type identifier corresponding to the user identifier having cancelled the account or the user information corresponding to the user identifier being abnormal, executing a freezing procedure for the account corresponding to the user identifier.

[0067] In case of failed deductions due to business reasons such as the account being closed or abnormal customer information, the executing entity can automatically freeze the account. If it receives feedback from the user that they need to continue using it, it prompts the user to consult the customer service for corresponding handling based on the business error message.

[0068] Step S102, in response to the exception type identifier corresponding to insufficient balance, obtain the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identifier. In response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, call the capital advance program to perform a capital advance payment based on the amount to be deducted.

[0069] When the exception type identifier corresponds to insufficient balance, the balance can be the wallet balance, the balance of a bank card under the user's name, etc. The embodiments of the present application do not make specific limitations on the balance. The executing entity can deduct from other bound bank cards. When it detects that the balances of other bank cards under the user's name are also insufficient, it calls the capital advance program to advance funds for the user based on the amount to be deducted, thereby assisting the user to pass through the gate. Subsequently, it prompts the user to manually make up the payment or recharge, and the background makes up the payment regularly.

[0070] Step S103, in response to the successful capital advance payment, determine the gate identifier, and then call the gate opening program to perform the gate opening processing process based on the gate identifier.

[0071] After successfully advancing funds for the user, obtain the gate identifier corresponding to the gate where the user swipes their face, and then call the gate opening program to open the gate corresponding to the gate identifier for the user to pass through.

[0072] Step S104, in response to the successful gate opening, generate a reminder message for making up the payment based on the amount to be deducted and output it.

[0073] When it detects that the user passes through the gate after the capital advance processing, call the information generation unit to generate a reminder message for making up the payment according to the amount to be deducted and output it to the user terminal corresponding to the user identifier.

[0074] In this embodiment, by responding to the exception handling request, obtaining the corresponding user identifier and exception type identifier; in response to the exception type identifier corresponding to insufficient balance, obtaining the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identifier, in response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, calling the capital advance program to perform a capital advance payment based on the amount to be deducted; in response to the successful capital advance payment, determining the gate identifier, and then calling the gate opening program to perform the gate opening processing process based on the gate identifier; in response to the successful gate opening, generating a reminder message for making up the payment based on the amount to be deducted and outputting it. It improves the intelligent way of handling exceptions, reduces the situations that need to be manually processed when the payment fails, reduces the pressure on the customer service, and improves the gate opening speed and passing efficiency when the deduction is abnormal.

[0075] Figure 2 is a schematic diagram of the main flow of an exception handling method according to an embodiment of the present application, such as Figure 2 As shown, the exception handling method includes:

[0076] Step S201, in response to an exception handling request, obtain a corresponding user identifier and an exception type identifier.

[0077] Specifically, after obtaining the corresponding user identifier and exception type identifier, the exception handling method further includes:

[0078] In response to the abnormal type identification corresponding to the user corresponding to the user identification having been cancelled or the user information corresponding to the user identification being abnormal, the facial recognition blacklisting procedure for the user corresponding to the user identification is executed. For deduction failures caused by business reasons such as account cancellation and customer information abnormalities, the execution subject can automatically blacklist the face corresponding to the user identification. In response to receiving a facial recognition recovery request from the user corresponding to the user identification, the corresponding business processing node (such as a customer service node) is displayed according to the abnormal type identification. If user feedback is received that the facial recognition access gate needs to continue to be used, the user is prompted to contact customer service to perform corresponding processing according to the business error report. This provides users with multiple channels to solve the generated anomalies, facilitates user passage, and increases the gate's traffic flow to avoid congestion.

[0079] Step S202, obtain the order identifier corresponding to the user identifier, and in response to the exception type identifier corresponding to the order duplication, determine whether the time interval for initiating the repeated order is within the preset time period. If so, return the order duplication error information. If not, call the successful transaction record. In response to the order identifier being in the successful transaction record, return the order payment success information. In response to the order identifier not being in the successful transaction record, initiate a payment transaction based on the order identifier to the back end.

[0080] For example, the order identifier can be an order number. For duplicate order processing, the Remote Dictionary Server (Redis) is used to save the order number in the cache. The order resent within n seconds will be directly and quickly returned with a failure error message for duplicate order numbers, and the subsequent back-end payment transactions will not be executed, avoiding repeated deductions, reducing system pressure, and improving payment system performance. If it exceeds n seconds, the execution entity can first check whether the corresponding successful transaction record already exists in the cache. If there is a corresponding successful transaction record, the order number corresponds to an order that has been successfully paid. Redis is used to achieve idempotence and return the processing result, and the payment transaction will not be initiated on the back end. Avoid repeated deductions, reduce system pressure, and improve payment system performance.

[0081] Figure 3 is a schematic diagram of the main flow of an exception handling method according to an embodiment of the present application, such as Figure 3As shown, the exception handling method includes:

[0082] Step S301: In response to an exception handling request, obtain the corresponding user identifier and exception type identifier.

[0083] Specifically, after obtaining the corresponding user identifier and exception type identifier, the method further includes: in response to the exception type identifier corresponding to facial recognition timeout, pop up a window to display replaceable verification methods; determine the replaceable verification method selected by the user corresponding to the user identifier as the target verification method; and execute the corresponding verification process based on the target verification method.

[0084] For example, when the exception type identifier corresponds to timeout of invoking face water flow verification, etc., perform degradation processing using other verification methods, such as pop up a window to display verification methods such as mobile phone verification code verification or graphic verification that can be selected, and obtain the verification method information selected by the user to determine the corresponding verification method as the target verification method, and perform verification according to the target verification method. For example, if the user selects SMS verification code verification, send a dynamic verification code to the terminal held by the user, and display a verification passed message after obtaining the correct dynamic verification code input by the user.

[0085] In the embodiment of the present application, when there is an exception timeout for calling a card of another bank, the execution entity can perform advance payment processing to ensure normal deduction as much as possible, ensure smooth passage, and improve the user experience.

[0086] Step S302: Obtain the amount to be deducted corresponding to the exception handling request, and in response to the exception type identifier corresponding to payment response timeout or network jitter, set the retry time interval and the number of retries.

[0087] Step S303: Based on the retry time interval, the number of retries, and the amount to be deducted, execute the transaction retry process.

[0088] When the exception type identifier corresponds to payment exceptions caused by reasons such as payment response timeout or network jitter, it is saved in the resend pool at the subway end and resent regularly a specified number of times. For example, resend after an interval of more than five minutes, and the number of resends does not exceed 10 times. Resending can be performed during low-traffic hours at night, which can reduce the daytime transaction pressure and achieve the purpose of peak shaving and flow limiting.

[0089] In the embodiments of the present application, on the abnormal order processing page of the management console, payment abnormal orders can be regularly displayed for processors to process and analyze regularly. The embodiments of the present application can ensure the decoupling of payment and gate opening, achieve fast travel, ensure normal payment deduction, perform peak shaving and current limiting, and use retransmission to handle the problem of payment timeout during peak periods. Avoid risks, and be able to detect and handle payment failures caused by system failures in a timely manner. Reduce the impact on the customer experience caused by deduction failures due to network jitter or peaks. Improve the intelligent processing of exceptions, reduce the situations that require manual processing when payment fails, and reduce the pressure on customer service. Cooperate with face brushing for travel to achieve high-efficiency travel. Solve the problem of payment exceptions during peak periods. Detect system problems in a timely manner and ensure smooth travel deduction.

[0090] Figure 4 is a schematic diagram of the main units of the abnormal processing device according to the embodiments of the present application. As Figure 4 shown, the abnormal processing device 400 includes a first acquisition unit 401, a second acquisition unit 402, a gate opening unit 403, and a supplementary payment unit 404.

[0091] The first acquisition unit 401 is configured to acquire the corresponding user identifier and abnormal type identifier in response to an abnormal processing request.

[0092] The second acquisition unit 402 is configured to, in response to the abnormal type identifier corresponding to insufficient balance, acquire the amount to be deducted corresponding to the abnormal processing request and the bound card information corresponding to the user identifier, and in response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, call a financing program to perform financing payment based on the amount to be deducted.

[0093] The gate opening unit 403 is configured to, in response to the successful financing payment, determine the gate identifier, and then call a gate opening program to perform a gate opening processing process based on the gate identifier.

[0094] The supplementary payment unit 404 is configured to, in response to the successful gate opening, generate and output a supplementary payment prompt message based on the amount to be deducted.

[0095] In some embodiments, the abnormal processing device further includes Figure 4 a duplicate order processing unit (not shown in the figure), which is configured to: acquire the order identifier corresponding to the user identifier, and in response to the abnormal type identifier corresponding to an order duplication, determine whether the time interval for initiating the duplicate order is within a preset time period. If so, return an order duplication error message; if not, call the successful transaction record. In response to the order identifier being in the successful transaction record, return an order payment success message; in response to the order identifier not being in the successful transaction record, initiate a payment transaction based on the order identifier to the backend.

[0096] In some embodiments, the abnormal processing device further includes Figure 4The retry unit not shown in the figure is configured to: obtain the amount to be deducted corresponding to the exception handling request, and set the retry time interval and the number of retries in response to the exception type identifier corresponding to the payment response timeout or network jitter; based on the retry time interval, the number of retries and the amount to be deducted, execute the transaction retry process.

[0097] In some embodiments, the exception handling device further includes Figure 4 The alarm unit not shown in the figure is configured to: generate an alarm message in response to the abnormal type identifier corresponding to a system failure or batch payment failure, and then send the alarm message to a preset processing node.

[0098] In some embodiments, the exception handling device further includes Figure 4 The freezing unit not shown in the figure is configured to: in response to the abnormal type identifier corresponding to the user corresponding to the user identifier having cancelled the account or the user information corresponding to the user identifier being abnormal, execute a freezing procedure for the account corresponding to the user identifier.

[0099] In some embodiments, the exception handling device further includes Figure 4 The blacklisting unit not shown in the figure is configured to: in response to the exception type identifier corresponding to the user corresponding to the user identifier having cancelled the account or the user information corresponding to the user identifier being abnormal, execute the facial recognition blacklisting procedure for the user corresponding to the user identifier; in response to receiving a facial recognition recovery request from the user corresponding to the user identifier, display the corresponding business processing node according to the exception type identifier.

[0100] In some embodiments, the exception handling device further includes Figure 4 The pop-up unit not shown in the figure is configured to: in response to the abnormal type identifier corresponding to the facial recognition timeout, display an alternative verification method in a pop-up window; determine the alternative verification method selected by the user corresponding to the user identifier as the target verification method; and execute the corresponding verification process based on the target verification method.

[0101] It should be noted that the exception handling method and the exception handling device of the present application have a corresponding relationship in terms of specific implementation contents, so the repeated contents will not be described again.

[0102] Figure 5 An exemplary system architecture 500 to which the exception handling method or exception handling device according to the embodiment of the present application can be applied is shown.

[0103] like Figure 5 As shown, system architecture 500 may include terminal devices 501, 502, 503, a network 504 and a server 505. Network 504 is used to provide a medium for communication links between terminal devices 501, 502, 503 and server 505. Network 504 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0104] Users can use terminal devices 501, 502, and 503 to interact with server 505 through network 504 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 501, 502, and 503, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0105] Terminal devices 501, 502, and 503 can be various electronic devices with an exception handling screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, and desktop computers, etc.

[0106] Server 505 can be a server that provides various services, such as a background management server that provides support for exception handling requests submitted by users using terminal devices 501, 502, and 503 (only as an example). The background management server can, in response to an exception handling request, obtain the corresponding user identifier and exception type identifier; in response to the exception type identifier corresponding to insufficient balance, obtain the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identifier, and in response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, call a financing program to perform a financing payment based on the amount to be deducted; in response to the successful financing payment, determine a gate identifier, and then call a gate opening program to perform a gate opening process based on the gate identifier; in response to the successful gate opening, generate a supplementary payment prompt message based on the amount to be deducted and output it. Improve the intelligent way of handling exceptions, reduce the situations that need to be manually processed when payment fails, reduce the pressure on customer service, and improve the gate opening speed and passing efficiency when there is a deduction exception.

[0107] It should be noted that the exception handling method provided by the embodiments of the present application is generally executed by server 505. Correspondingly, the exception handling device is generally set in server 505.

[0108] It should be understood that Figure 5 the numbers of terminal devices, networks, and servers in

[0109] are merely illustrative. According to actual needs, there can be any number of terminal devices, networks, and servers. Figure 6 shown in Figure 6 is a schematic structural diagram of a computer system 600 of a terminal device suitable for implementing the embodiments of the present application.

[0110] As Figure 6As shown, computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage section 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the computer system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0111] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed so that a computer program read from it can be installed into the storage section 608 as needed.

[0112] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in this application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from the removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the above functions defined in the system of this application are executed.

[0113] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can, for example, include but is not limited to an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium can include but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this application, a computer-readable storage medium can be any tangible medium that contains or stores a program, which can be used by or in conjunction with an instruction execution system, apparatus, or device. And in this application, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0114] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram can represent a module, a program segment, or a part of code, and the above-mentioned module, program segment, or part of code contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, as well as the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0115] The units involved in the embodiments described in this application can be implemented in software or in hardware. The described units can also be provided in a processor. For example, it can be described as: a processor includes a first acquisition unit, a second acquisition unit, a gate-opening unit, and a payment supplement unit. Among them, the names of these units do not constitute a limitation on the unit itself in some cases.

[0116] As another aspect, this application also provides a computer-readable medium. This computer-readable medium can be included in the device described in the above embodiments; it can also exist separately without being assembled into the device. The above computer-readable medium carries one or more programs. When the above one or more programs are executed by such a device, the device, in response to an exception handling request, acquires the corresponding user identification and exception type identification; in response to the exception type identification corresponding to insufficient balance, acquires the amount to be deducted corresponding to the exception handling request and the binding card information corresponding to the user identification, and in response to the balance in the binding card corresponding to the binding card information being insufficient to pay the amount to be deducted, invokes a financing program to perform a financing payment based on the amount to be deducted; in response to the successful financing payment, determines a gate identification, and then invokes a gate-opening program to perform a gate-opening processing process based on the gate identification; in response to the successful gate-opening, generates a payment supplement prompt message based on the amount to be deducted and outputs it.

[0117] The computer program product of this application includes a computer program, and the computer program implements the exception handling method in the embodiments of this application when executed by a processor.

[0118] According to the technical solution of the embodiments of this application, the intelligent exception handling method can be improved, the situations that need to be manually processed when the payment fails can be reduced, the pressure on customer service can be reduced, and the gate-opening speed and passing efficiency during abnormal deduction can be improved.

[0119] The above specific implementation manners do not constitute a limitation on the protection scope of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent replacements, and improvements made within the spirit and principle of this application shall be included within the protection scope of this application.

Claims

1. An exception handling method, characterized in that, Including: Upon receiving an exception handling request, obtain the corresponding user identifier and exception type identifier; wherein, in response to the exception type identifier corresponding to payment response timeout or network jitter, utilize the resend pool to execute a transaction retry process during low trading volumes; in response to the exception type identifier corresponding to order duplication, use a remote dictionary service to save the order number in the cache, return an order duplication error message for orders to be resent within a preset time period, and do not execute the payment transaction; in response to the exception type identifier corresponding to system failure or batch payment failure, generate an alarm message and then send the alarm message to a preset processing node; in response to the exception type identifier corresponding to the user corresponding to the user identifier having their account closed or the user information corresponding to the user identifier being abnormal, execute a freezing procedure for the account corresponding to the user identifier. In response to the exception type identifier corresponding to insufficient balance, obtain the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identifier, and in response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, call a financing procedure to perform a financing payment based on the amount to be deducted. In response to successful financing payment, determine a gate identifier and then call a gate opening procedure to perform a gate opening process based on the gate identifier. In response to successful gate opening, generate and output a supplementary payment prompt message based on the amount to be deducted.

2. The method according to claim 1, wherein After obtaining the corresponding user identifier and exception type identifier, the method further includes: Obtain the order identifier corresponding to the user identifier, and in response to the exception type identifier corresponding to order duplication, determine whether the time interval for initiating the duplicate order is within a preset time range. If so, return an order duplication error message; if not, call the successful transaction record. In response to the order identifier being in the successful transaction record, return an order payment success message; in response to the order identifier not being in the successful transaction record, initiate a payment transaction based on the order identifier to the backend.

3. The method according to claim 1, characterized in that, After obtaining the corresponding user identifier and exception type identifier, the method further includes: Obtain the amount to be deducted corresponding to the exception handling request, and in response to the exception type identifier corresponding to payment response timeout or network jitter, set a retry time interval and a number of retry attempts. Execute a transaction retry process based on the retry time interval, the number of retry attempts, and the amount to be deducted.

4. The method according to claim 1, wherein After obtaining the corresponding user identifier and exception type identifier, the method further includes: In response to the exception type identifier corresponding to the user corresponding to the user identifier having their account closed or the user information corresponding to the user identifier being abnormal, execute a facial recognition blacklisting procedure for the user corresponding to the user identifier. In response to receiving a facial recognition restoration request for the user corresponding to the user identifier, display the corresponding business processing node according to the exception type identifier.

5. The method according to claim 1, characterized in that, After obtaining the corresponding user identifier and exception type identifier, the method further includes: In response to the exception type identifier corresponding to facial recognition timeout, pop up and display alternative verification methods. Determine the replaceable verification mode selected by the user corresponding to the user identifier as the target verification mode; Execute a corresponding verification process based on the target verification method.

6. An exception handling device, characterized in that, include: A first acquisition unit is configured to acquire a corresponding user identifier and an exception type identifier in response to an exception handling request; A second acquisition unit is configured to, in response to the exception type identifier corresponding to insufficient balance, acquire the amount to be deducted corresponding to the exception handling request and the bound card information corresponding to the user identifier, and in response to the balance in the bound card corresponding to the bound card information being insufficient to pay the amount to be deducted, call a payment program to perform payment based on the amount to be deducted; A gate opening unit, configured to determine a gate identifier in response to a successful advance payment, and then call a gate opening program to execute a gate opening process based on the gate identifier; A supplementary payment unit is configured to generate and output supplementary payment prompt information based on the amount to be deducted in response to the gate opening being successful; A retry unit is configured to execute a transaction retry process using a retransmission pool when the transaction volume is small in response to the abnormal type identifier corresponding to a payment response timeout or a network jitter; a duplicate order processing unit configured to, in response to the abnormal type identifier corresponding to an order duplicate, use a remote dictionary service to save the order number in a cache, return an order duplicate error message to an order reissued within a preset time period, and not execute a payment transaction; an alarm unit, configured to generate an alarm message in response to the abnormal type identifier corresponding to a system failure or a batch payment failure, and then send the alarm message to a preset processing node; The freezing unit is configured to execute a freezing procedure for the account corresponding to the user identifier in response to the abnormal type identifier corresponding to the user corresponding to the user identifier having cancelled the account or the user information corresponding to the user identifier being abnormal.

7. The device according to claim 6, wherein The device also includes a repeat order processing unit configured to: Obtain the order identifier corresponding to the user identifier, and in response to the exception type identifier corresponding to the order duplication, determine whether the time interval for initiating the repeated order is within a preset time period. If so, return order duplication error information; otherwise, call the successful transaction record, and in response to the order identifier being in the successful transaction record, return order payment success information; in response to the order identifier not being in the successful transaction record, initiate a payment transaction based on the order identifier to the back end.

8. The device according to claim 6, characterized in that, The device further comprises a retry unit configured to: Obtaining the amount to be deducted corresponding to the exception handling request, and setting a retry time interval and a retry count in response to the exception type identifier corresponding to a payment response timeout or network jitter; Based on the retry time interval, the number of retries and the amount to be deducted, a transaction retry process is executed.

9. The device according to claim 6, wherein The device also includes a blacklisting unit configured to: In response to the abnormal type identifier corresponding to the user corresponding to the user identifier having cancelled the account or the user information corresponding to the user identifier being abnormal, executing a facial recognition blacklisting procedure for the user corresponding to the user identifier; In response to receiving a facial recognition restoration request of a user corresponding to the user identifier, display a corresponding service processing node according to the exception type identifier.

10. An abnormal handling electronic device, characterized in that, Including: One or more processors; A storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1-5.

11. A computer-readable medium having a computer program stored thereon, characterized in that, The program, when executed by a processor, implements the method according to any one of claims 1-5.

12. A computer program product, comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the method according to any one of claims 1-5.

Images