CN116071063A - Abnormality processing method, abnormality processing device, electronic equipment and computer readable medium - Google Patents

Abnormality processing method, abnormality processing device, electronic equipment and computer readable medium Download PDF

Info

Publication number
CN116071063A
CN116071063A CN202310062281.2A CN202310062281A CN116071063A CN 116071063 A CN116071063 A CN 116071063A CN 202310062281 A CN202310062281 A CN 202310062281A CN 116071063 A CN116071063 A CN 116071063A
Authority
CN
China
Prior art keywords
user
identifier
response
identification
deducted
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.)
Pending
Application number
CN202310062281.2A
Other languages
Chinese (zh)
Inventor
刘承忠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Construction Bank Corp
CCB Finetech Co Ltd
Original Assignee
China Construction Bank Corp
CCB Finetech Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Construction Bank Corp, CCB Finetech Co Ltd filed Critical China Construction Bank Corp
Priority to CN202310062281.2A priority Critical patent/CN116071063A/en
Publication of CN116071063A publication Critical patent/CN116071063A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/30—Individual registration on entry or exit not involving the use of a pass
    • G07C9/32—Individual registration on entry or exit not involving the use of a pass in combination with an identity check
    • G07C9/37—Individual registration on entry or exit not involving the use of a pass in combination with an identity check using biometric data, e.g. fingerprints, iris scans or voice recognition
    • 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/22—Payment schemes or models
    • G06Q20/24—Credit schemes, i.e. "pay after"
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/308—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using the Internet of Things
    • 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/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G06Q20/40145—Biometric identity checks

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The application discloses an exception handling method, an exception handling device, electronic equipment and a computer readable medium, and relates to the technical field of the Internet of things; acquiring the to-be-deducted amount corresponding to the abnormal processing request and the binding card information corresponding to the user identifier in response to the fact that the balance is insufficient, and calling a money filling program in response to the fact that the balance in the binding card corresponding to the binding card information is insufficient to pay the to-be-deducted amount so as to execute money filling payment based on the to-be-deducted amount; determining a gate identifier in response to successful payment of the pad resource, and further calling a gate opening program to execute a gate opening processing process based on the gate identifier; and generating and outputting compensation prompt information based on the amount to be deducted in response to successful opening of the gate. The intelligent abnormal handling mode is perfected, the condition that manual handling is needed when payment fails is reduced, customer service pressure is reduced, and the opening speed and the passing efficiency when fee deduction is abnormal are improved.

Description

Abnormality processing method, abnormality processing device, electronic equipment and computer readable medium
Technical Field
The present disclosure relates to the field of internet of things, and in particular, to an exception handling method, an exception handling device, an electronic device, and a computer readable medium.
Background
Judging that the wallet balance account is abnormal before opening the gate by brushing the face can lead to long transaction link, and the problems of slow gate opening speed, low passing efficiency and the like are easily caused by network jitter, insufficient wallet balance, abnormal account and the like. And when the user brushes the face to go out and charges after passing the gate, a series of charges are deducted abnormally due to account abnormity, insufficient wallet balance, overtime response and the like, so that the gate opening speed is low and the passing efficiency is low.
Disclosure of Invention
In view of this, the embodiments of the present application provide an anomaly processing method, apparatus, electronic device, and computer readable medium, which can solve the problems of slow opening speed and low traffic efficiency caused by the existing fee deduction anomaly.
To achieve the above object, according to one aspect of the embodiments of the present application, there is provided an exception handling method, including:
responding to the exception handling request, and acquiring a corresponding user identifier and an exception type identifier;
acquiring the to-be-deducted amount corresponding to the abnormal processing request and the binding card information corresponding to the user identifier in response to the fact that the balance is insufficient, and calling a money filling program in response to the fact that the balance in the binding card corresponding to the binding card information is insufficient to pay the to-be-deducted amount so as to execute money filling payment based on the to-be-deducted amount;
determining a gate identifier in response to successful payment of the pad resource, and further calling a gate opening program to execute a gate opening processing process based on the gate identifier;
and generating and outputting compensation prompt information based on the amount to be deducted in response to successful opening of the gate.
Optionally, after acquiring the corresponding user identifier and the anomaly type identifier, the method further includes:
acquiring an order identifier corresponding to the user identifier, responding to the abnormal type identifier to correspond to the order repetition, judging whether the time interval for initiating repeated orders is within a preset time interval range, if so, returning order repeated error reporting information, if not, calling a successful transaction record, responding to the order identifier in the successful transaction record, returning order payment success information, responding to the order identifier not in the successful transaction record, and initiating a payment transaction based on the order identifier to the rear end.
Optionally, after acquiring the corresponding user identifier and the anomaly type identifier, the method further includes:
obtaining the amount to be deducted corresponding to the exception handling request, responding to the response time-out of the exception type identification corresponding to the payment response or the network jitter, and setting a retry time interval and retry times;
and executing a transaction retry process based on the retry time interval, the retry number and the amount to be deducted.
Optionally, after acquiring the corresponding user identifier and the anomaly type identifier, the method further includes:
and generating alarm information in response to the abnormal type identification corresponding to the system fault or batch payment failure, and further sending the alarm information to a preset processing node.
Optionally, after acquiring the corresponding user identifier and the anomaly type identifier, the method further includes:
and responding to the abnormality type identification corresponding to the user sold by the user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing the freezing program of the account corresponding to the user identification.
Optionally, after acquiring the corresponding user identifier and the anomaly type identifier, the method further includes:
responding to the abnormality type identification corresponding to the user sold user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing a face identification blacking program for the user corresponding to the user identification;
and responding to the face recognition recovery request of the user corresponding to the received user identifier, and displaying the corresponding service processing node according to the abnormal type identifier.
Optionally, after acquiring the corresponding user identifier and the anomaly type identifier, the method further includes:
responsive to the anomaly type identification corresponding to a facial recognition timeout, the popup exhibiting an alternative verification;
determining an alternative verification mode selected by a user and corresponding to the user identifier as a target verification mode;
and executing a corresponding verification process based on the target verification mode.
In addition, the application also provides an exception handling device, which comprises:
the first acquisition unit is configured to respond to the exception handling request and acquire a corresponding user identifier and an exception type identifier;
the second acquisition unit is configured to respond to the fact that the balance is insufficient corresponding to the abnormal type identification, acquire the to-be-deducted amount corresponding to the abnormal processing request and the binding card information corresponding to the user identification, and call the fund filling program to execute fund filling payment based on the to-be-deducted amount in response to the fact that the balance in the binding card corresponding to the binding card information is insufficient to pay the to-be-deducted amount;
the gate opening unit is configured to determine a gate identifier in response to successful payment of the pad resource, and further call a gate opening program to execute a gate opening processing process based on the gate identifier;
and the compensation unit is configured to respond to the success of opening the gate, generate compensation prompt information based on the amount to be deducted and output the compensation prompt information.
Optionally, the exception handling device further comprises a repeat order handling unit configured to:
acquiring an order identifier corresponding to the user identifier, responding to the abnormal type identifier to correspond to the order repetition, judging whether the time interval for initiating repeated orders is within a preset time interval range, if so, returning order repeated error reporting information, if not, calling a successful transaction record, responding to the order identifier in the successful transaction record, returning order payment success information, responding to the order identifier not in the successful transaction record, and initiating a payment transaction based on the order identifier to the rear end.
Optionally, the exception handling device further comprises a retry unit configured to:
obtaining the amount to be deducted corresponding to the exception handling request, responding to the response time-out of the exception type identification corresponding to the payment response or the network jitter, and setting a retry time interval and retry times;
and executing a transaction retry process based on the retry time interval, the retry number and the amount to be deducted.
Optionally, the abnormality processing device further includes an alarm unit configured to:
and generating alarm information in response to the abnormal type identification corresponding to the system fault or batch payment failure, and further sending the alarm information to a preset processing node.
Optionally, the abnormality processing apparatus further includes a freezing unit configured to:
and responding to the abnormality type identification corresponding to the user sold by the user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing the freezing program of the account corresponding to the user identification.
Optionally, the exception handling device further comprises a blackening unit configured to:
responding to the abnormality type identification corresponding to the user sold user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing a face identification blacking program for the user corresponding to the user identification;
and responding to the face recognition recovery request of the user corresponding to the received user identifier, and displaying the corresponding service processing node according to the abnormal type identifier.
Optionally, the exception handling device further comprises a popup unit configured to:
responsive to the anomaly type identification corresponding to a facial recognition timeout, the popup exhibiting an alternative verification;
determining an alternative verification mode selected by a user and corresponding to the user identifier as a target verification mode;
and executing a corresponding verification process based on the target verification mode.
In addition, the application also provides an exception handling electronic device, which comprises: one or more processors; and a storage device for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the exception handling method as described above.
In addition, the application also provides a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the exception handling method as described above.
To achieve the above object, according to yet another aspect of the embodiments of the present application, a computer program product is provided.
A computer program product of an embodiment of the present application includes a computer program, which when executed by a processor implements an exception handling method provided by the embodiment of the present application.
One embodiment of the above invention has the following advantages or benefits: the method comprises the steps of responding to an exception handling request to obtain a corresponding user identifier and an exception type identifier; acquiring the to-be-deducted amount corresponding to the abnormal processing request and the binding card information corresponding to the user identifier in response to the fact that the balance is insufficient, and calling a money filling program in response to the fact that the balance in the binding card corresponding to the binding card information is insufficient to pay the to-be-deducted amount so as to execute money filling payment based on the to-be-deducted amount; determining a gate identifier in response to successful payment of the pad resource, and further calling a gate opening program to execute a gate opening processing process based on the gate identifier; and generating and outputting compensation prompt information based on the amount to be deducted in response to successful opening of the gate. The intelligent abnormal handling mode is perfected, the condition that manual handling is needed when payment fails is reduced, customer service pressure is reduced, and the opening speed and the passing efficiency when fee deduction is abnormal are improved.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the present application and are not to be construed as unduly limiting the present application. Wherein:
FIG. 1 is a schematic diagram of the main flow of an exception handling method according to one embodiment of the present application;
FIG. 2 is a schematic diagram of the main flow of an exception handling method according to one embodiment of the present application;
FIG. 3 is a main flow diagram of an exception handling method according to one embodiment of the present application;
FIG. 4 is a schematic diagram of the main units of an exception handling apparatus according to an embodiment of the present application;
FIG. 5 is an exemplary system architecture diagram in which embodiments of the present application may be applied;
fig. 6 is a schematic diagram of a computer system suitable for use in implementing the terminal device or server of the embodiments of the present application.
Detailed Description
Exemplary embodiments of the present application are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness. In the technical scheme of the application, the aspects of acquisition, analysis, use, transmission, storage and the like of the related user personal information all meet the requirements of related laws and regulations, are used for legal and reasonable purposes, are not shared, leaked or sold outside the aspects of legal use and the like, and are subjected to supervision and management of a supervision department. Necessary measures should be taken for the personal information of the user to prevent illegal access to such personal information data, ensure that personnel having access to the personal information data comply with the regulations of the relevant laws and regulations, and ensure the personal information of the user. Once these user personal information data are no longer needed, the risk should be minimized by limiting or even prohibiting the data collection and/or deletion.
User privacy is protected by de-identifying data when used, including in some related applications, such as by removing a particular identifier, controlling the amount or specificity of stored data, controlling how data is stored, and/or other methods.
FIG. 1 is a schematic diagram of the main flow of an exception handling method according to one embodiment of the present application, as shown in FIG. 1, the exception handling method includes:
step S101, responding to an exception handling request, and acquiring a corresponding user identifier and an exception type identifier.
In this embodiment, the execution body (for example, may be a server) of the exception handling method may detect whether an exception handling request is received by means of a wired connection or a wireless connection. When the executing body detects the exception handling request, the user identifier carried in the request can be obtained. By way of example, the exception handling request may be a subway face-brushing exception handling request. The user identifier may be a user account number, a user name, a user nickname, or the like corresponding to a user entering or exiting the subway, and the embodiment of the present application does not specifically limit the user identifier. After the executing body obtains the user identifier corresponding to the exception handling request, the executing body can obtain the exception type identifier. The exception type identifier may be obtained by acquiring and analyzing exception data corresponding to the exception handling request. The exception information base can be specifically called to match the obtained exception data corresponding to the exception processing request with the historical exception data in the exception information base, so as to obtain a corresponding exception type identifier. For example, the correspondence between the historical anomaly data and the anomaly type identifier may be stored in the anomaly information base.
Specifically, after the corresponding user identifier and the abnormality type identifier are acquired, the abnormality processing method further includes: and generating alarm information in response to the abnormal type identification corresponding to the system fault or batch payment failure, and further sending the alarm information to a preset processing node.
When the fault of the system is explicitly reported and the mass payment fails, the execution body can give an alarm through mails and short messages, and emergency treatment is carried out at the first time. The preset processing node may be an emergency processing node, for example, a node corresponding to an attendant or customer service person.
Specifically, after the corresponding user identifier and the anomaly type identifier are acquired, the method further comprises the steps of: and responding to the abnormality type identification corresponding to the user sold by the user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing the freezing program of the account corresponding to the user identification.
Aiming at the deduction failure caused by business reasons such as account sales, abnormal customer information and the like, the execution main body can automatically freeze the account, and if user feedback is received and the user needs to continue to use, the user is prompted to consult customer service to carry out corresponding processing according to business errors.
Step S102, in response to the abnormal type identification corresponding to the insufficient balance, acquiring the amount to be deducted corresponding to the abnormal processing request and the binding card information corresponding to the user identification, and in response to the insufficient balance in the binding card corresponding to the binding card information to pay the amount to be deducted, invoking the fund-filling program to execute fund-filling payment based on the amount to be deducted.
When the balance is insufficient corresponding to the abnormal type identifier, the balance can be wallet balance, a bank card balance under a user name and the like, and the balance is not particularly limited in the embodiment of the application. The execution body can clamp fees from other banks which are bound, and when detecting that the balance of other bank cards under the user name is insufficient, the execution body invokes a fund-filling program to fill funds for the user based on the amount to be deducted, so that the user is assisted to pass through the gate. And prompting the user to manually make-up or make-up at background timing.
Step S103, in response to successful payment of the pad, determining a gate identifier, and further calling a gate opening program to execute a gate opening process based on the gate identifier.
After successful user funding, gate identifiers corresponding to gates of the user brushing faces are obtained, and then a gate opening program is called to open gates corresponding to the gate identifiers for the user to pass through.
And step S104, generating and outputting compensation prompt information based on the amount to be deducted in response to successful brake opening.
When the user passes through the gate after the money filling processing is detected, the information generating unit is called to generate the compensation prompt information according to the amount to be deducted and output the compensation prompt information to the user terminal corresponding to the user identifier.
In the embodiment, corresponding user identification and anomaly type identification are obtained by responding to an anomaly handling request; acquiring the to-be-deducted amount corresponding to the abnormal processing request and the binding card information corresponding to the user identifier in response to the fact that the balance is insufficient, and calling a money filling program in response to the fact that the balance in the binding card corresponding to the binding card information is insufficient to pay the to-be-deducted amount so as to execute money filling payment based on the to-be-deducted amount; determining a gate identifier in response to successful payment of the pad resource, and further calling a gate opening program to execute a gate opening processing process based on the gate identifier; and generating and outputting compensation prompt information based on the amount to be deducted in response to successful opening of the gate. The intelligent abnormal handling mode is perfected, the condition that manual handling is needed when payment fails is reduced, customer service pressure is reduced, and the opening speed and the passing efficiency when fee deduction is abnormal are improved.
FIG. 2 is a main flow diagram of an exception handling method according to an embodiment of the present application, as shown in FIG. 2, the exception handling method includes:
step S201, responding to the exception handling request, and acquiring a corresponding user identifier and an exception type identifier.
Specifically, after the corresponding user identifier and the abnormality type identifier are acquired, the abnormality processing method further includes:
and executing a face recognition blackout program for the user corresponding to the user identification in response to the abnormality type identification corresponding to the user sold by the user corresponding to the user identification or the abnormality of the user information corresponding to the user identification. Aiming at the deduction failure caused by business reasons such as account sales, abnormal customer information and the like, the execution main body can automatically blacken the face corresponding to the user identification. And responding to the face recognition recovery request of the user corresponding to the received user identification, and displaying the corresponding service processing node (such as a customer service node) according to the abnormal type identification. If the user feedback is received and the face recognition gate needs to be used continuously, prompting the user to contact customer service to carry out corresponding processing according to the business error reporting. Therefore, the system provides multiple channels for users to solve the generated abnormality, is convenient for the users to pass, and improves the passing flow of the gate to avoid congestion.
Step S202, an order mark corresponding to the user mark is obtained, whether the time interval for initiating repeated orders is within a preset time period range is judged in response to the abnormal type mark corresponding to the order repetition, if yes, order repeated error reporting information is returned, if not, a successful transaction record is called, order payment success information is returned in response to the order mark in the successful transaction record, and a payment transaction based on the order mark is initiated to the rear end in response to the order mark not in the successful transaction record.
For example, the order identifier may be an order number, for repeated order processing, remote dictionary service (Remote Dictionary Server, dis) is used to store the order number in a cache, and the repeated failure report of the order number is directly and quickly returned to the order within n seconds, so that subsequent back-end payment transaction is not continuously executed, repeated fee deduction is avoided, system pressure is reduced, and performance of the payment system is improved. The executing body can firstly check whether the corresponding successful transaction record exists in the cache or not after n seconds, if the corresponding successful transaction record exists, the order number corresponds to the order which is paid successfully, the idempotent return processing result is realized by using Redis, and the payment transaction is not continuously initiated at the back end. Repeated fee deduction is avoided, system pressure is reduced, and performance of the payment system is improved.
FIG. 3 is a main flow diagram of an exception handling method according to an embodiment of the present application, as shown in FIG. 3, the exception handling method includes:
step S301, in response to the exception handling request, obtains a corresponding user identifier and an exception type identifier.
Specifically, after the corresponding user identifier and the anomaly type identifier are acquired, the method further comprises the steps of: responsive to the anomaly type identification corresponding to a facial recognition timeout, the popup exhibiting an alternative verification; determining an alternative verification mode selected by a user and corresponding to the user identifier as a target verification mode; and executing a corresponding verification process based on the target verification mode.
For example, when the abnormal type identifier corresponds to invoking a face pipelining verification timeout or the like, performing degradation processing by using other verification modes, for example, a popup window displays verification modes such as alternative mobile phone verification code verification or graphic verification, and the like, and acquires verification mode information selected by a user, so that the corresponding verification mode is determined as a target verification mode, and verification is performed according to the target verification mode. For example, if the user selects the verification of the short message verification code, the user sends the dynamic verification code to the terminal held by the user, and after the user inputs the correct dynamic verification code, verification passing information is displayed.
In this embodiment, when invoking his line card exception overtime, the execution subject can carry out the money-filling processing to guarantee as much as possible that the fee deduction is normal, guarantee that the traffic is smooth and easy, promote user experience.
Step S302, the amount to be deducted corresponding to the exception handling request is obtained, and a retry time interval and a retry number are set in response to the exception type identification corresponding to the payment response timeout or the network jitter.
Step S303, executing transaction retry process based on the retry time interval, the retry times and the amount to be deducted.
When the abnormal type identifier corresponds to the abnormal payment caused by overtime of payment response or network jitter, the abnormal type identifier is stored in a retransmission pool at the subway end, and is retransmitted at specified times, for example, retransmission is carried out at intervals of more than five minutes, and the retransmission times are not more than 10 times. Can be retransmitted when the transaction amount is small at night, can reduce the transaction pressure in the daytime, and achieves the purposes of peak clipping and current limiting.
In the embodiment of the application, the abnormal order processing page of the management platform can periodically display the abnormal payment order for the processor to periodically process and analyze. According to the embodiment of the application, the payment and the opening decoupling can be guaranteed, and the quick trip is realized. And ensuring the normal payment deduction. Peak clipping and limiting, and using retransmission to process the problem of overtime payment in peak period. The risk is avoided, and payment failure caused by system faults can be timely found and processed. And the fee deduction failure caused by network jitter or peak and other reasons is reduced, and the customer experience is affected. The intelligent abnormal handling mode is perfected, the condition that manual handling is needed when payment fails is reduced, and customer service pressure is reduced. High-efficiency travel is realized by matching with face brushing travel. The problem of abnormal payment in the peak period is solved. And the system problems are found in time, so that smooth trip fee deduction is ensured.
Fig. 4 is a schematic diagram of main units of the abnormality processing apparatus according to the embodiment of the present application. As shown in fig. 4, the abnormality processing apparatus 400 includes a first acquisition unit 401, a second acquisition unit 402, a brake opening unit 403, and a compensation unit 404.
The first obtaining unit 401 is configured to obtain, in response to the exception handling request, a corresponding user identifier and an exception type identifier.
The second obtaining unit 402 is configured to obtain the amount to be deducted corresponding to the exception handling request and the binding card information corresponding to the user identifier in response to the exception type identifier corresponding to the insufficient balance, and call the fund filling program in response to the balance in the binding card corresponding to the binding card information being insufficient to pay the amount to be deducted, so as to perform the fund filling payment based on the amount to be deducted.
And a gate opening unit 403 configured to determine a gate identifier in response to successful payment of the mat, and further to invoke a gate opening procedure to perform a gate opening process based on the gate identifier.
And the compensation unit 404 is configured to generate and output compensation prompt information based on the amount to be deducted in response to successful brake opening.
In some embodiments, the exception handling apparatus further comprises a repeat order processing unit, not shown in fig. 4, configured to: acquiring an order identifier corresponding to the user identifier, responding to the abnormal type identifier to correspond to the order repetition, judging whether the time interval for initiating repeated orders is within a preset time interval range, if so, returning order repeated error reporting information, if not, calling a successful transaction record, responding to the order identifier in the successful transaction record, returning order payment success information, responding to the order identifier not in the successful transaction record, and initiating a payment transaction based on the order identifier to the rear end.
In some embodiments, the exception handling apparatus further comprises a retry unit, not shown in fig. 4, configured to: obtaining the amount to be deducted corresponding to the exception handling request, responding to the response time-out of the exception type identification corresponding to the payment response or the network jitter, and setting a retry time interval and retry times; and executing a transaction retry process based on the retry time interval, the retry number and the amount to be deducted.
In some embodiments, the exception handling apparatus further comprises an alert unit, not shown in fig. 4, configured to: and generating alarm information in response to the abnormal type identification corresponding to the system fault or batch payment failure, and further sending the alarm information to a preset processing node.
In some embodiments, the exception handling apparatus further comprises a freezing unit, not shown in fig. 4, configured to: and responding to the abnormality type identification corresponding to the user sold by the user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing the freezing program of the account corresponding to the user identification.
In some embodiments, the exception handling apparatus further comprises a blackening unit, not shown in fig. 4, configured to: responding to the abnormality type identification corresponding to the user sold user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing a face identification blacking program for the user corresponding to the user identification; and responding to the face recognition recovery request of the user corresponding to the received user identifier, and displaying the corresponding service processing node according to the abnormal type identifier.
In some embodiments, the exception handling apparatus further comprises a pop-up window unit, not shown in fig. 4, configured to: responsive to the anomaly type identification corresponding to a facial recognition timeout, the popup exhibiting an alternative verification; determining an alternative verification mode selected by a user and corresponding to the user identifier as a target verification mode; and executing a corresponding verification process based on the target verification mode.
The exception handling method and the exception handling apparatus of the present application have a corresponding relationship in terms of implementation, and therefore, the description is not repeated.
FIG. 5 illustrates an exemplary system architecture 500 in which the exception handling method or exception handling apparatus of embodiments of the present application may be applied.
As shown in fig. 5, the system architecture 500 may include terminal devices 501, 502, 503, a network 504, and a server 505. The network 504 is used as a medium to provide communication links between the terminal devices 501, 502, 503 and the server 505. The network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 505 via the network 504 using the terminal devices 501, 502, 503 to receive or send messages or the like. Various communication client applications may be installed on the terminal devices 501, 502, 503, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 501, 502, 503 may be various electronic devices with an exception handling screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 505 may be a server providing various services, such as a background management server (by way of example only) that provides support for exception handling requests submitted by users using the terminal devices 501, 502, 503. The background management server can respond to the exception handling request to acquire the corresponding user identifier and the exception type identifier; acquiring the to-be-deducted amount corresponding to the abnormal processing request and the binding card information corresponding to the user identifier in response to the fact that the balance is insufficient, and calling a money filling program in response to the fact that the balance in the binding card corresponding to the binding card information is insufficient to pay the to-be-deducted amount so as to execute money filling payment based on the to-be-deducted amount; determining a gate identifier in response to successful payment of the pad resource, and further calling a gate opening program to execute a gate opening processing process based on the gate identifier; and generating and outputting compensation prompt information based on the amount to be deducted in response to successful opening of the gate. The intelligent abnormal handling mode is perfected, the condition that manual handling is needed when payment fails is reduced, customer service pressure is reduced, and the opening speed and the passing efficiency when fee deduction is abnormal are improved.
It should be noted that, the exception handling method provided in the embodiment of the present application is generally executed by the server 505, and accordingly, the exception handling apparatus is generally disposed in the server 505.
It should be understood that the number of terminal devices, networks and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 6, a schematic diagram of a computer system 600 suitable for use in implementing the terminal device of an embodiment of the present application is shown. The terminal device shown in fig. 6 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiments of the present application.
As shown in fig. 6, the 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 RAM603, various programs and data required for the operation of the computer system 600 are also stored. The CPU601, ROM602, and RAM603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a liquid crystal credit authorization query processor (LCD), and the like, and a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments disclosed herein include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 601.
It should be noted that the computer readable medium shown in the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may include, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware. The described units may also be provided in a processor, for example, described as: the processor comprises a first acquisition unit, a second acquisition unit, a brake opening unit and a compensation unit. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
As another aspect, the present application also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by one of the devices, cause the device to obtain a corresponding user identification and exception type identification in response to an exception handling request; acquiring the to-be-deducted amount corresponding to the abnormal processing request and the binding card information corresponding to the user identifier in response to the fact that the balance is insufficient, and calling a money filling program in response to the fact that the balance in the binding card corresponding to the binding card information is insufficient to pay the to-be-deducted amount so as to execute money filling payment based on the to-be-deducted amount; determining a gate identifier in response to successful payment of the pad resource, and further calling a gate opening program to execute a gate opening processing process based on the gate identifier; and generating and outputting compensation prompt information based on the amount to be deducted in response to successful opening of the gate.
The computer program product of the present application includes a computer program which, when executed by a processor, implements the exception handling method in the embodiments of the present application.
According to the technical scheme of the embodiment of the application, an intelligent abnormal handling mode can be perfected, the condition that manual handling is needed when payment fails is reduced, customer service pressure is reduced, and the opening speed and the passing efficiency when fee deduction is abnormal are improved.
The above embodiments do not limit the scope of the application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims (16)

1. An exception handling method, comprising:
responding to the exception handling request, and acquiring a corresponding user identifier and an exception type identifier;
acquiring the amount to be deducted corresponding to the abnormal processing request and the binding card information corresponding to the user identifier in response to the fact that the balance is insufficient, and calling a fund-filling program in response to the fact that the balance in the binding card corresponding to the binding card information is insufficient to pay the amount to be deducted so as to execute fund-filling payment based on the amount to be deducted;
determining a gate identifier in response to successful payment of the pad resource, and calling a gate opening program to execute a gate opening processing process based on the gate identifier;
and generating and outputting compensation prompt information based on the amount to be deducted in response to successful opening of the gate.
2. The method of claim 1, wherein after the obtaining the corresponding user identification and anomaly type identification, the method further comprises:
acquiring an order identifier corresponding to the user identifier, responding to the abnormal type identifier to correspond to order repetition, judging whether the time interval for initiating repeated orders is within a preset time interval range, if so, returning order repeated error reporting information, if not, calling a successful transaction record, responding to the order identifier in the successful transaction record, returning order payment success information, responding to the order identifier not in the successful transaction record, and initiating a payment transaction based on the order identifier to the rear end.
3. The method of claim 1, wherein after the obtaining the corresponding user identification and anomaly type identification, the method further comprises:
acquiring the amount to be deducted corresponding to the exception handling request, and setting a retry time interval and retry times in response to the exception type identifier corresponding to the overtime of the payment response or the network jitter;
and executing a transaction retry process based on the retry time interval, the retry times and the amount to be deducted.
4. The method of claim 1, wherein after the obtaining the corresponding user identification and anomaly type identification, the method further comprises:
and generating alarm information in response to the abnormal type identification corresponding to the system fault or batch payment failure, and further sending the alarm information to a preset processing node.
5. The method of claim 1, wherein after the obtaining the corresponding user identification and anomaly type identification, the method further comprises:
and responding to the abnormality type identification corresponding to the user sold user corresponding to the user identification or the abnormality of the user information corresponding to the user identification, and executing a freezing program of the account corresponding to the user identification.
6. The method of claim 1, wherein after the obtaining the corresponding user identification and anomaly type identification, the method further comprises:
responding to the abnormality type identification corresponding to the user sold user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing a face identification blacking program of the user corresponding to the user identification;
and responding to the face recognition recovery request of the user corresponding to the user identifier, and displaying the corresponding service processing node according to the abnormal type identifier.
7. The method of claim 1, wherein after the obtaining the corresponding user identification and anomaly type identification, the method further comprises:
responsive to the anomaly type identification corresponding to a facial recognition timeout, the popup exhibiting an alternative verification;
determining an alternative verification mode selected by a user and corresponding to the user identifier as a target verification mode;
and executing a corresponding verification process based on the target verification mode.
8. An abnormality processing apparatus, comprising:
the first acquisition unit is configured to respond to the exception handling request and acquire a corresponding user identifier and an exception type identifier;
a second obtaining unit configured to obtain, in response to the abnormality type identifier corresponding to the balance deficiency, a to-be-deducted amount corresponding to the abnormality processing request and binding card information corresponding to the user identifier, and in response to the balance in the binding card corresponding to the binding card information being insufficient to pay the to-be-deducted amount, call a fund-making program to perform fund-making payment based on the to-be-deducted amount;
the gate opening unit is configured to determine a gate identifier in response to successful payment of the fund, and call a gate opening program to execute a gate opening processing process based on the gate identifier;
and the compensation unit is configured to respond to the success of opening the gate, generate compensation prompt information based on the amount to be deducted and output the compensation prompt information.
9. The apparatus of claim 8, further comprising a repeat order processing unit configured to:
acquiring an order identifier corresponding to the user identifier, responding to the abnormal type identifier to correspond to order repetition, judging whether the time interval for initiating repeated orders is within a preset time interval range, if so, returning order repeated error reporting information, if not, calling a successful transaction record, responding to the order identifier in the successful transaction record, returning order payment success information, responding to the order identifier not in the successful transaction record, and initiating a payment transaction based on the order identifier to the rear end.
10. The apparatus of claim 8, further comprising a retry unit configured to:
acquiring the amount to be deducted corresponding to the exception handling request, and setting a retry time interval and retry times in response to the exception type identifier corresponding to the overtime of the payment response or the network jitter;
and executing a transaction retry process based on the retry time interval, the retry times and the amount to be deducted.
11. The apparatus of claim 8, further comprising an alert unit configured to:
and generating alarm information in response to the abnormal type identification corresponding to the system fault or batch payment failure, and further sending the alarm information to a preset processing node.
12. The apparatus of claim 8, further comprising a freezing unit configured to:
and responding to the abnormality type identification corresponding to the user sold user corresponding to the user identification or the abnormality of the user information corresponding to the user identification, and executing a freezing program of the account corresponding to the user identification.
13. The apparatus of claim 8, further comprising a blacking unit configured to:
responding to the abnormality type identification corresponding to the user sold user corresponding to the user identification or the user information corresponding to the user identification is abnormal, and executing a face identification blacking program of the user corresponding to the user identification;
and responding to the face recognition recovery request of the user corresponding to the user identifier, and displaying the corresponding service processing node according to the abnormal type identifier.
14. An exception handling electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-7.
15. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-7.
16. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any of claims 1-7.
CN202310062281.2A 2023-01-18 2023-01-18 Abnormality processing method, abnormality processing device, electronic equipment and computer readable medium Pending CN116071063A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310062281.2A CN116071063A (en) 2023-01-18 2023-01-18 Abnormality processing method, abnormality processing device, electronic equipment and computer readable medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310062281.2A CN116071063A (en) 2023-01-18 2023-01-18 Abnormality processing method, abnormality processing device, electronic equipment and computer readable medium

Publications (1)

Publication Number Publication Date
CN116071063A true CN116071063A (en) 2023-05-05

Family

ID=86181653

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310062281.2A Pending CN116071063A (en) 2023-01-18 2023-01-18 Abnormality processing method, abnormality processing device, electronic equipment and computer readable medium

Country Status (1)

Country Link
CN (1) CN116071063A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117974127A (en) * 2024-03-29 2024-05-03 成都智元汇信息技术股份有限公司 Method and system for generating maintenance indication based on reconciliation abnormality

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117974127A (en) * 2024-03-29 2024-05-03 成都智元汇信息技术股份有限公司 Method and system for generating maintenance indication based on reconciliation abnormality

Similar Documents

Publication Publication Date Title
CN112334933B (en) Blockchain transaction processing
CN111861437A (en) Payment processing method and device
CN110033280B (en) Payment anti-shake method and device
CN109034603B (en) Business process execution method, device and computer readable storage medium
CN116071063A (en) Abnormality processing method, abnormality processing device, electronic equipment and computer readable medium
CN109933508B (en) Method and apparatus for transmitting information
CN111861745A (en) Service wind control method and device
CN117911159A (en) Real-time data processing method, device, equipment, storage medium and program product
US9264532B2 (en) Technology for combating mobile phone criminal activity
CN111767535A (en) Method and device for resetting bank card password online
US8271360B1 (en) System and method for automatic approval of direct deposit payroll limit increases
CN111275542A (en) Loan request processing method, device and system
CN114596088A (en) Digital currency transaction method and system and digital currency card application device
US20150178696A1 (en) System and method for performing callbacks in an automated clearing house network
CN114841815A (en) Transaction analysis method and device, electronic equipment and computer-readable storage medium
CN112330323A (en) Method for generating token seed and two-dimensional code, payment method and payment device
CN113283814A (en) Business processing efficiency determination method and device, electronic equipment and readable storage medium
CN112132692A (en) Policy data processing method and device, storage medium and electronic equipment
CN117495568A (en) Transaction method, apparatus, device, medium and program product
CN116188154A (en) Method, apparatus, electronic device and computer readable medium for processing payment request
CN111105315B (en) Policy request processing method, policy request processing device, policy request processing medium and electronic equipment
CN116629874A (en) Account monitoring method, device, equipment, medium and program product
CN117314613A (en) Method and device for processing information
CN116527363A (en) Method, device, equipment, medium and program product for safety authentication of internet banking
CN117455469A (en) Resource processing method and device, storage medium and electronic equipment

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