Quick payment error report data processing method, device, equipment, medium and product

Abstract

The invention provides a quick payment error report data processing method, device and equipment, a medium and a product, which can be applied to the technical field of financial science and technology. The method comprises the following steps: in response to a quick payment error in a payment page of a user, performing data analysis on error data of the quick payment error to obtain an error identifier, and matching an error coefficient according to the error identifier to determine error type data corresponding to the error coefficient, the error type data being used for representing a reason for the quick payment error; screening out an error solving scheme corresponding to the error report type data from a preset error response library, and performing error management and control processing according to an error solving process corresponding to the error report type data based on the error solving scheme; and filling the debugging scheme into a preset debugging command template to obtain a debugging link which can be used as a quick debugging processing entry, and guiding a user to carry out a debugging process once the debugging link is triggered.

Description

Technical Field

[0001] This application relates to the field of financial technology, specifically to a method, apparatus, equipment, medium, and product for processing error data in quick payment. Background Technology

[0002] In the current era of rapid development in digital finance, bank quick payment has become an important payment method in daily life. However, with the surge in transaction volume and the diversification of payment scenarios, payment error problems caused by control or tiered limits have become increasingly prominent. This issue has become a key obstacle restricting user experience and industry development, especially in large transactions and emergency payments.

[0003] Banks set limits for quick payment to control risk and ensure fund security. These limits are customized based on factors such as account type, transaction history, and credit status to meet daily payment needs. However, in practice, this mechanism has exposed many problems. For example, when customers initiate transactions through third-party payment institutions, errors caused by limits directly impact the payment experience. There is a lack of effective online guidance and mechanisms to assist in resolving these errors. Even if solutions exist, current methods only provide a statement regarding the error cause, failing to analyze the cause and type of the error in depth, and unable to provide timely solutions based on the cause and type. This leads to untimely responses to payment error processing. Furthermore, payment errors negatively impact the data processing of financial institutions' intermediary business revenue layers, such as increasing the data processing burden and causing data bottlenecks. Therefore, current methods for handling quick payment errors are not only ineffective and slow, but also unnecessarily increase the burden on financial institutions' computing systems, causing system bottlenecks. In other words, they not only fail to resolve errors effectively and promptly but also create new financial data processing problems. Summary of the Invention

[0004] In view of the above problems, this application provides a method, apparatus, device, medium and product for processing error data in quick payment.

[0005] According to the first aspect of this application, a method for processing quick payment error data is provided, comprising: responding to a quick payment error appearing on a user's payment page, parsing the error data of the quick payment error to obtain an error identifier, the error identifier including at least one of a limit release code indicating a need to release payment limit control and a limit error code indicating a limit error; matching an error coefficient according to the error identifier to determine the error type data corresponding to the error coefficient, the error type data indicating the reason for the quick payment error; filtering out a solution corresponding to the error type data from a preset error response library, and performing error control processing based on the solution according to the solution process corresponding to the error type data; filling the solution into a preset solution command template to obtain a solution link that can be used as a quick solution processing entry point, and once the solution link is triggered, guiding the user to perform the solution process.

[0006] According to an embodiment of this application, error data of quick payment errors is parsed to obtain error identifiers, including: extracting key fields from the error data, where the key fields include at least one of the following: payment channel identifier, payment amount, user account status, error timestamp, and return code field; standardizing the format of the key fields, removing invalid characters and duplicate data to obtain valid fields; and matching the error identifiers corresponding to the valid fields based on a preset identifier mapping table, where the identifier mapping table pre-stores the correspondence between the return code field, the number of key fields, and the limit unlock code and limit error code, respectively.

[0007] According to embodiments of this application, matching an error coefficient based on an error identifier includes: in response to an error identifier being a limit decontrol code, the error coefficient is a preset limit decontrol weight, the value of which belongs to a preset first interval; in response to an error identifier being a limit error code, the error coefficient is a preset limit error weight, the value of which belongs to a preset second interval, the second interval being mutually exclusive with the first interval; in response to an error identifier being a combination of a limit error code and a limit decontrol code, the error coefficient is a preset combination weight, the combination weight being the sum of the limit error code and the limit error weight, and the value of which belongs to a preset third interval.

[0008] According to embodiments of this application, determining the error type data corresponding to the error coefficient includes: responding to the error coefficient value belonging to a first interval, determining the error type as either an account control type or a demand release type; if the error type is an account control type, calling the user's account signing information; if the account signing information indicates the absence of account control hard indicators, then attaching a control description indicating whether or not there are account control hard indicators as the error type data; if the error type is a demand release type, calling the user's account signing information, triggering a limit verification process based on the account signing information and mobile banking signing information, to verify the increase in limit based on the user's current payment account's single transaction limit, daily limit, and cumulative consumption amount, generating verification result data, and... The verification result data is used as the error type data. If the error coefficient value falls within the second range, the user's account signing information is retrieved. Based on the account signing information and mobile banking signing information, a limit verification process is triggered to classify the account according to the user's current payment account's single transaction limit, daily limit, and cumulative consumption amount, generating limit level data, which is then used as the error type data. If the error coefficient value falls within the third range, the user's account signing information is retrieved, and an account level activation request is generated for the user based on the account signing information, which is then used as the error type data. If the error coefficient value falls within the preset fourth range, the verification failure data, which indicates the failure of the basic parameter verification, is used as the error type data.

[0009] According to an embodiment of this application, the error response library stores the association between error resolution schemes and error type data. The association is a many-to-one mapping relationship, which is used to represent that one type of error data corresponds to at least two error resolution schemes.

[0010] According to an embodiment of this application, the preset error-solving command template includes fixed fields and variable fields. The fixed fields are error-solving operation guidance messages, and the variable fields are error-solving operation links, verification entry points, and parameter configuration entry points.

[0011] According to an embodiment of this application, filling the error resolution scheme into a preset error resolution command template includes: extracting the core operation path and entry address from the error resolution scheme, filling the core operation path and entry address into the variable fields of the error resolution command template to obtain the error resolution template; performing format validation on the error resolution template, and in response to passing the validation, performing linking processing on the error resolution template to obtain an error resolution link that can be used as a quick error resolution processing entry point.

[0012] According to an embodiment of this application, after generating the error resolution link, the method further includes: storing the error data, error type data, error resolution scheme, and error resolution link into a preset log database; monitoring the user's triggering status of the error resolution link in real time; if the user does not trigger the error resolution link within the time limit, then re-matching the error coefficient, updating the error type data, and matching a new error resolution scheme.

[0013] This also includes: Responding to error type data that includes control instructions regarding whether or not there are hard indicators for account management, extracting the user's mobile banking contract information; if the mobile banking contract information indicates that the user meets the requirements for self-service de-control via mobile banking or remote de-control via manual processing, then the remote de-control solution will be used as the error resolution solution; Responding to error type data that includes verification result data, if the verification result data indicates that the credit limit increase verification has passed, extracting the user's mobile banking contract information; if the mobile banking contract information indicates that the user meets the requirements for self-service credit limit increase via mobile banking or remote credit limit increase via manual processing, then the remote credit limit increase solution will be used as the error resolution solution; Responding to error type data that includes credit limit level data, extracting the user's mobile banking contract information; if the mobile banking contract information indicates that the user meets the requirements for self-service credit limit increase via mobile banking or remote credit limit increase via manual processing, then the remote level change solution will be used as the error resolution solution; Responding to error type data that includes account tiered activation requests, using the guidance process guide to help users activate their accounts offline as the error resolution solution; Responding to error type data that includes verification failure data, using the statement explaining the data error as the error resolution solution.

[0014] The second aspect of this application provides a quick payment error data processing device, comprising: a data parsing module, used to respond to a quick payment error appearing on a user's payment page, parse the error data of the quick payment error to obtain an error identifier, the error identifier including at least one of a limit release code indicating the need to release payment limit control and a limit error code indicating the existence of a limit error; a type matching module, used to match an error coefficient according to the error identifier to determine the error type data corresponding to the error coefficient, the error type data being used to indicate the reason for the quick payment error; a solution matching module, used to filter out the solution corresponding to the error type data from a preset error response library, and to perform error control processing according to the solution process corresponding to the error type data based on the solution; and a link generation module, used to fill the solution into a preset solution command template to obtain a solution link that can be used as a quick solution processing entry point, and once the solution link is triggered, it guides the user through the solution process.

[0015] A third aspect of this application provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the method described above.

[0016] A fourth aspect of this application also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods described above.

[0017] The fifth aspect of this application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0018] According to the quick payment error data processing method, apparatus, equipment, medium, and product provided in this application, the error data of quick payment errors is parsed to obtain an error identifier. An error coefficient is matched based on the error identifier to determine the error type data corresponding to the error coefficient. Since the error identifier can be directly parsed to obtain the error data, and the error coefficient can be matched to determine the error type data, the cause of the quick payment error can be quickly found, improving the response efficiency of quick payment errors. Furthermore, since the error resolution process is followed according to the error type to obtain the resolution solution, it is easy to quickly obtain the resolution solution, improving the efficiency and relevance of error resolution. Moreover, the error solution is integrated into the error resolution link, which can be directly pushed to the user's end to achieve real-time online error resolution. This not only improves the effectiveness and relevance of quick payment error resolution but also shortens the response time and improves the resolution efficiency. Attached Figure Description

[0019] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0020] Figure 1 The illustration shows an application scenario of the quick payment error data processing method, apparatus, device, medium, and program product according to embodiments of this application;

[0021] Figure 2 A flowchart illustrating a quick payment error data processing method according to an embodiment of this application is shown in the schematic diagram.

[0022] Figure 3 This illustration shows a schematic diagram of the data processing flow involved in the quick payment error data processing method according to an embodiment of this application;

[0023] Figure 4 This illustration schematically shows a solution diagram involved in the quick payment error data processing method according to an embodiment of this application;

[0024] Figure 5 This schematic diagram illustrates the structural block diagram of a quick payment error data processing device according to an embodiment of this application;

[0025] Figure 6 A block diagram schematically illustrates an electronic device suitable for implementing a quick payment error data processing method according to an embodiment of this application. Detailed Implementation

[0026] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0027] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0028] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0029] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0030] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, they do not mean that the applicant has used or necessarily used the solution.

[0031] In the technical solution of this application, the collection, storage, use, processing, transmission, provision, disclosure and application of user personal information all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0032] In the technical solution of this application, the acquisition, collection, storage, use, processing, transmission, provision, disclosure and application of data all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0033] Figure 1 The illustration shows an application scenario diagram of the quick payment error data processing method according to an embodiment of this application.

[0034] like Figure 1 As shown, application scenario 100 according to this embodiment may include terminal devices 101, 102, and 103, network 104, and server 105. Network 104 is used as a medium to provide a communication link between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0035] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0036] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0037] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0038] It should be noted that the quick payment error data processing method provided in this application embodiment can generally be executed by server 105. Correspondingly, the quick payment error data processing device provided in this application embodiment can generally be located in server 105. The quick payment error data processing method provided in this application embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the quick payment error data processing device provided in this application embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0039] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0040] The following will be based on Figure 1 The described scene, through Figures 2-4 The method for processing error data in quick payment according to the application embodiment is described in detail.

[0041] Figure 2 A flowchart illustrating a quick payment error data processing method according to an embodiment of this application is shown.

[0042] like Figure 2 As shown, the quick payment error data processing method of this embodiment includes operations S210 to S240.

[0043] In operation S210, in response to a quick payment error appearing on the user's payment page, the error data of the quick payment error is parsed to obtain an error identifier. The error identifier includes at least one of the following: a limit release code indicating a need to release payment limit control, and a limit error code indicating a limit error. In operation S220, an error coefficient is matched according to the error identifier to determine the error type data corresponding to the error coefficient. The error type data is used to indicate the reason for the quick payment error. In operation S230, a solution corresponding to the error type data is selected from the preset error response library, and error management is performed based on the solution according to the error resolution process corresponding to the error type data. In operation S240, the solution is filled into the preset error resolution command template to obtain an error resolution link that can be used as a quick error resolution processing entry. Once the error resolution link is triggered, the user is guided to the error resolution process.

[0044] As an example, when making quick payments through social applications, quick payment applications, etc., error messages often appear, such as "payment limit exceeded." In this example, the situation of exceeding the payment limit can be divided into two types. One is that the payment account has a payment limit control, such as the account being frozen and not allowed to make payments, so its limit is zero yuan, or the account is under control, meaning that the amount that can be used for expenditure is within a preset limit, such as a risk account, where daily transfers or payments are limited to 10,000 yuan. The other is that the limit is different depending on the account classification level. For example, if the user's account is a medium-level account, its daily transfer limit is 500,000 yuan, which means that its account level restricts its payment limit to 500,000 yuan. For a basic account, its daily transfer limit is 100,000 yuan, which means that its account level restricts its payment limit to 100,000 yuan. Therefore, when the quick payment exceeds the limit, a quick payment error message will appear on the quick payment terminal.

[0045] In this example, after recognizing the instruction or identifier of a quick payment error, the error data of quick payment first needs to be parsed to obtain the error identifier. This error identifier is a pre-set symbol used to represent different error types. For example, the symbol could be a limit release code representing a request to release payment limit control, or a limit error code representing a limit error. Then, the error coefficient is calculated based on the error identifier. This error coefficient is a data or numerical range, which can also represent different error types, but in a different way than the symbol. The symbol is used for identification, while the data or numerical range facilitates quick determination by the program or engine. The system identifies the error type and its corresponding error type data. Based on the error coefficient, the error type data can be determined. Then, based on the error type data, a solution corresponding to the error type data is selected from a preset error response library. Different solutions represent different solutions and implementation methods, such as directly increasing or lifting the limit, or guiding the user to apply for a limit increase or lifting the limit themselves. The solution is then filled into a preset solution command template to obtain a solution link that can be used as a quick solution entry point. Based on this solution link, the error can be directly and specifically resolved or the user can be guided to resolve it according to the solution process.

[0046] Based on this, since error data can be directly parsed to obtain an identifier, an error coefficient can be corresponding to the error identifier, and the error type data can be determined based on the error coefficient. This allows for the rapid identification of the cause of quick payment errors, improving the response efficiency of quick payment errors. The error resolution process is then carried out according to the error type to obtain a solution, facilitating the rapid acquisition of a solution and improving the efficiency and relevance of error resolution. The error solution is integrated into the error resolution link and directly pushed to the user's end, enabling real-time online error resolution. This not only improves the effectiveness and relevance of quick payment error resolution but also shortens the response time and increases the efficiency of error resolution.

[0047] Figure 3 This illustration shows a schematic diagram of the data processing flow involved in the quick payment error data processing method according to an embodiment of this application.

[0048] exist Figure 3 In the illustrated embodiment, the error data of the quick payment error is parsed to obtain the error identifier, including: extracting key fields from the error data, the key fields including at least one of the payment channel identifier, payment amount, user account status, error timestamp, and return code field; standardizing the format of the key fields, removing invalid characters and duplicate data to obtain valid fields; and matching the error identifier corresponding to the valid field based on a preset identifier mapping table, the identifier mapping table pre-stores the correspondence between the return code field, the number of key fields, and the limit unlock code and limit error code, respectively.

[0049] As an example, a user purchases goods worth 5,000 yuan through a bank card quick payment on an e-commerce platform. The payment page displays an error message: "Quick payment failed (error code: E1001)". First, the error data is parsed: After responding to the error, key fields are extracted from the error data, such as payment channel identifier: UnionPay; payment amount: 5,000 yuan; user account status: normal; error timestamp: 202X-XX-XX 14:35:22; return code: E1001. After standardization, based on the identifier mapping table, the "credit limit unlocking code (K001)" corresponding to E1001 is matched, and the error identifier is obtained as the credit limit unlocking code K001.

[0050] Based on this, key fields such as the timestamp return field are quickly obtained, and then the error flag corresponding to the key field is matched in the preset flag mapping table, thereby improving the objectivity and accuracy of error flag matching.

[0051] In this embodiment, matching the error coefficient according to the error identifier includes: in response to the error identifier being a limit decontrol code, the error coefficient is a preset limit decontrol weight, the value of which belongs to a preset first interval; in response to the error identifier being a limit error code, the error coefficient is a preset limit error weight, the value of which belongs to a preset second interval, the second interval being mutually exclusive with the first interval; in response to the error identifier being a combination of a limit error code and a limit decontrol code, the error coefficient is a preset combination weight, the combination weight being the sum of the limit error code and the limit error weight, and the value of which belongs to a preset third interval.

[0052] As an example, the error coefficient is the data or value corresponding to the pre-set error identifier. It is equivalent to digitizing the error identifier, that is, converting the symbol into data / value. When calculating the error coefficient, for example, the preset weight value of the limit decontrol code K001 is 0.7. There are no other error identifiers, so the error coefficient is 0.7. The error type is determined: 0.7 belongs to the first interval (0.6-0.8], and the corresponding error type data is "Payment limit exceeded and decontrol required". That is, the first interval (0.6-0.8] corresponds to the "Payment limit exceeded and decontrol required" type, the second interval (0.4-0.6] can correspond to the "Limit parameter configuration error" type, the third interval (1-1.4], and the fourth interval (0-0.4) correspond to the "Basic parameter verification failed" type. The numerical interval relationships are all preset. The first interval and the second interval are mutually exclusive, that is, the two intervals have no intersection.

[0053] Based on this, the error flag data representing the error classification can be valued, so that the built-in program of the error resolution system can quickly determine the specific error type represented by the error flag based on the error coefficient.

[0054] In this embodiment, determining the error type data corresponding to the error coefficient includes: responding to the error coefficient value belonging to the first interval, determining the error type as either account control type or demand release type; if the error type is account control type, calling the user's account signing information; if the account signing information indicates the absence of account control hard indicators, then attaching a control description indicating whether or not there are account control hard indicators as the error type data; if the error type is demand release type, calling the user's account signing information, triggering a limit verification process based on the account signing information and mobile banking signing information, to verify the increase in limit based on the user's current payment account's single transaction limit, daily limit, and cumulative consumption amount, generating verification result data, and then... The verification result data is used as the error type data. If the error coefficient value falls within the second range, the user's account signing information is retrieved. Based on the account signing information and mobile banking signing information, a limit verification process is triggered to classify the account according to the user's current payment account's single transaction limit, daily limit, and cumulative consumption amount, generating limit level data, which is then used as the error type data. If the error coefficient value falls within the third range, the user's account signing information is retrieved, and an account level activation request is generated for the user based on the account signing information, which is then used as the error type data. If the error coefficient value falls within the preset fourth range, the verification failure data, which indicates the failure of the basic parameter verification, is used as the error type data.

[0055] As an example, the first interval (0.6-0.8) corresponds to "Payment limit exceeded, control needs to be lifted". The error type is divided into two categories: account control type and demand-based de-control type. When the error type is account control, it means the account is under financial institution control. In this case, the user's account signing information needs to be checked to determine if there are any indicators requiring continued control. If so, control continues, and the reason for control is reported to the payment end, such as displaying the reason for account control on the payment page. If the account signing information indicates the absence of hard account control indicators, a control explanation with or without hard account control indicators will be attached as the error type data, and a corresponding de-control solution will be developed based on this error type data. When the error type is demand-based de-control, it means the user has actively requested de-control. In this case, the user's account signing information also needs to be checked. Based on the account signing information and mobile banking signing information, a credit limit verification process is triggered. When the verification process passes, the credit limit can be increased according to the user's request. This involves verifying the credit limit increase based on the user's current payment account's single transaction limit, daily limit, and cumulative spending amount, generating verification result data, and using this verification result data as the error type data.

[0056] The second range (0.4-0.6) corresponds to the "limit parameter configuration error" type. This type means that the amount paid by the user does not match their account level. For example, if the limit of their account level is 30,000 per day, but they need to pay 35,000, an error message about "limit parameter configuration error" will be issued. In response, it is necessary to call the user's account signing information, trigger the limit verification process based on the account signing information and mobile banking signing information, classify the account according to the user's current payment account's single transaction limit, single day limit, and cumulative consumption amount, generate limit level data, and use the limit level data as the error type data, so that subsequent solutions for increasing the limit can be developed based on the limit level data.

[0057] The third interval (1-1.4) represents situations where there is both account control and a user's need to actively de-control. In this case, it is necessary to first determine whether de-control can be achieved, and then determine the credit limit level after de-control. Therefore, for this type of user, it is necessary to call the user's account contract information and generate an account-level activation request based on the account contract information. The account-level activation request is used as the error type data. In the subsequent selection of de-control solutions, the activation request is used to determine whether to activate de-control and re-classify the account.

[0058] The fourth interval (0-0.4) corresponds to the "Basic parameter verification failed" type. This type represents an error that is unrelated to the user and is a parameter or setting error in the financial system. Therefore, the verification failure data used to represent the failure of basic parameter verification is used as the error type data, and the financial system should be repaired as soon as possible.

[0059] Based on this, in short, if the error type data is "Payment limit exceeded, needs to be deregulated," then the limit verification process is triggered: query the user's current payment account's single transaction limit, daily limit, and cumulative consumption amount to determine if there are any temporary or permanent limit trigger conditions; if the error type data is "Limit parameter configuration error," then the parameter verification process is triggered: verify the consistency of the payment channel-side limit configuration, user account-side limit settings, and system default limit parameters to locate parameter mismatches; if the error type data is "Basic parameter verification failed," then the basic information verification process is triggered: verify basic parameters such as user identity information, bank card binding status, and payment terminal legality. In this way, the error types corresponding to the values ​​of each error coefficient can be obtained in a categorized manner, thereby outputting the error type data corresponding to the error type, so as to carry out different targeted error processing in the future, improving the efficiency and accuracy of error resolution.

[0060] In this embodiment, the error response library stores the association between error resolution schemes and error type data. The association is a many-to-one mapping relationship, which is used to represent that one type of error data corresponds to at least two error resolution schemes.

[0061] As an example, if the query shows that the user's linked bank card has a single transaction limit of 3,000 yuan and a daily limit of 5,000 yuan (3,000 yuan has already been spent), it is determined that the single transaction limit has been temporarily exceeded. When filtering the error resolution solutions, the error response database can be used to select the corresponding error resolution solutions for exceeding the payment limit, including "adjusting the single payment amount", "temporarily increasing the single transaction limit", and "split payment into multiple transactions". Considering the current online shopping scenario and the payment amount of 5,000 yuan, the highest priority solution, "temporarily increasing the single transaction limit", can be selected as the error resolution solution.

[0062] The error handling library stores the association between error resolution solutions and error type data, which facilitates the output of corresponding error resolution solutions for error type data, thereby improving the pertinence and effectiveness of error resolution.

[0063] In this embodiment, the preset error-solving command template includes fixed fields and variable fields. The fixed fields are the error-solving operation guidance scripts, and the variable fields are the error-solving operation links, verification entry points, and parameter configuration entry points.

[0064] As an example, the error resolution operation link, verification entry, and parameter configuration entry are all pre-set. The error resolution solution is filled into the error resolution command template, and after format verification, an error resolution link that users can click to enter can be generated. Based on the error resolution command template, the above error resolution solution can be quickly and intuitively carried out, so that users can quickly execute the error resolution solution after clicking the error resolution link, thereby improving the overall error resolution efficiency.

[0065] In this embodiment, filling the error resolution scheme into a preset error resolution command template includes: extracting the core operation path and entry address from the error resolution scheme, filling the core operation path and entry address into the variable fields of the error resolution command template to obtain the error resolution template; performing format validation on the error resolution template, and in response to passing the validation, performing linking processing on the error resolution template to obtain an error resolution link that can be used as a quick error resolution processing entry point.

[0066] As an example, when generating the error resolution link, the error resolution solution needs to be filled into the error resolution command template. For example, the core operation path and operation entry point of the specific solution for "temporarily increasing the single transaction limit" (https: / / pay.xxx.com / limit-upgrade?user=xxx&error=K001) need to be filled into the error resolution command template to obtain the error resolution template. The error resolution template is then validated for format. If it meets the format requirements, an error resolution link is generated for "Your current single transaction limit is insufficient. Click to immediately increase the temporary limit (valid for 15 minutes): (https: / / pay.xxx.com / limit-upgrade?user=xxx&error=K001)". This error resolution link is then pushed to the user's payment page so that the user can click to increase the limit or get guidance on increasing the limit.

[0067] Therefore, format validation is required when filling the error resolution solution into the error resolution command template to avoid the output error resolution link being unusable due to format errors. After the validation is passed, a guide that users can click directly to enable real-time credit limit increase or receive guidance on increasing credit limit is generated, thereby improving the effectiveness and pertinence of error resolution.

[0068] In this embodiment, after generating the error resolution link, the method further includes: storing the error data, error type data, error resolution scheme, and error resolution link into a preset log database; monitoring the user's triggering status of the error resolution link in real time; if the user does not trigger the error resolution link within the time limit, re-matching the error coefficient, updating the error type data, and matching a new error resolution scheme.

[0069] As an example, if the error resolution link is "Your current payment limit is insufficient. Click to immediately increase your temporary limit (valid for 15 minutes): (https: / / pay.xxx.com / limit-upgrade?user=xxx&error=K001)", and the user has not clicked it after 15 minutes, the error coefficient will be rematched, the error type data will be updated, and a new error resolution solution will be matched. The error resolution link with the new solution will be sent to the user again until the user has not clicked the link after a preset number of times. Then, the user can be contacted by customer service, and the sending of error resolution links will be stopped. The error resolution link can be sent through a public account, bank application, or SMS.

[0070] Therefore, if the error resolution link is not triggered, the error type data and error resolution solution need to be updated again to avoid the error resolution solution becoming ineffective due to time delays, and to improve the effectiveness of error resolution.

[0071] Figure 4 The illustration shows a schematic diagram of the error resolution scheme involved in the quick payment error data processing method according to an embodiment of this application.

[0072] exist Figure 4 The illustrated embodiment further includes: responding to error type data as a control description with or without account control hard indicators, extracting the user's mobile banking contract information; if the mobile banking contract information indicates that the user meets the mobile banking self-service decontrol requirements or manual remote decontrol requirements, then using the remote decontrol solution as the error resolution solution; responding to error type data as verification result data, if the verification result data indicates that the credit limit increase verification has passed, extracting the user's mobile banking contract information; if the mobile banking contract information indicates that the user meets the mobile banking self-service credit limit increase requirements or manual remote credit limit increase requirements, then using the remote credit limit increase solution as the error resolution solution; responding to error type data as limit level data, extracting the user's mobile banking contract information; if the mobile banking contract information indicates that the user meets the mobile banking self-service credit limit increase requirements or manual remote credit limit increase requirements, then using the remote level change solution as the error resolution solution; responding to error type data as an account tiered activation request, using the guidance process guide to help the user activate the account offline as the error resolution solution; responding to error type data as verification failure data, using the statement explaining the data error as the error resolution solution.

[0073] As an example, if the error message includes a control description specifying whether there are any hard indicators for account control, it means that the user does not have any mandatory account control indicators. In this case, the user's mobile banking registration information is extracted. If the mobile banking registration information indicates that the user meets the requirements for self-service account deregulation via mobile banking or remote deregulation via manual processing, then the remote deregulation solution is used as the error resolution solution. The specific remote deregulation method is not restricted. For example, for users who can be deregulated, the payment institution can bypass the process or notify the customer via message, guiding them to deregulate and increase their credit limit on mobile banking. If the account meets the deregulation conditions and the customer has already registered for mobile banking, the relevant functions of the anti-fraud component can be called to determine whether deregulation is possible. If the account meets the conditions for self-service or manual account deregulation via mobile banking and the branch where the account was opened has enabled the deregulation switch, then deregulation is considered possible, and online deregulation can be performed directly.

[0074] If the error report data is verification result data, and the verification result data indicates that the credit limit increase verification has passed, the user's mobile banking contract information is extracted. If the mobile banking contract information indicates that the user meets the requirements for mobile banking self-service credit limit increase or manual remote credit limit increase, then the remote credit limit increase plan is used as the error resolution plan. When executing the remote credit limit increase plan, the anti-fraud judgment conditions must be met, such as having a non-counter limit, the account meeting the conditions for mobile banking self-service or manual credit limit increase, and the branch where the account opening institution is located having the credit limit increase switch turned on. In this case, the credit limit can be increased directly.

[0075] If the error message is related to a credit limit, extract the user's mobile banking account information. If the mobile banking account information indicates that the user meets the requirements for self-service credit limit increase via mobile banking or remote credit limit increase via manual processing, then use the remote level change solution as the solution. Executing this remote level change solution requires the customer to meet the upgrade guidance conditions. Then, send a notification to guide the customer to enter mobile banking to upgrade and increase the credit limit according to the following priority: if the customer has already followed the bank's WeChat official account and bound a savings card or credit card, send an official account message and a bank-to-bank message notification; otherwise, send a bank-to-bank message.

[0076] If the error message is for an account tiered activation request, the solution is to send a guide to help users activate their accounts offline. This situation is more complex than the previous two, as it requires both de-escalation and credit limit increase. Therefore, users need to activate and upgrade their accounts offline. So, send the guide to help users activate their accounts offline.

[0077] If the error message indicates a validation failure, it means there is a parameter problem in the financial system. This situation is irrelevant to the user, so it is sufficient to send a statement explaining the data error to the user.

[0078] Based on this, targeted remote troubleshooting or remote guided troubleshooting not only improves the relevance and effectiveness of troubleshooting, but also enhances its efficiency and user-friendliness.

[0079] As described above, the quick payment error data processing method provided in this application can directly parse the error data to obtain an error identifier. Based on the error identifier, an error coefficient can be obtained, and based on the error coefficient, an error type can be determined. This allows for the rapid identification of the cause of quick payment errors and improves the response efficiency of quick payment errors. Furthermore, by following the error resolution process corresponding to the error type to obtain a resolution solution, it is easier to quickly obtain a resolution solution, improving the efficiency and relevance of error resolution. Moreover, by integrating the error resolution solution into the error resolution link, the link can be directly pushed to the user's end for real-time online error resolution. This not only improves the effectiveness and relevance of quick payment error resolution but also shortens the response time and increases the efficiency of error resolution.

[0080] Based on the above-mentioned quick payment error data processing method, this application also provides a quick payment error data processing device. The following will be combined with... Figure 5 The device is described in detail.

[0081] Figure 5 A schematic block diagram of a quick payment error data processing device according to an embodiment of this application is shown.

[0082] like Figure 5 As shown, the quick payment error data processing device 500 in this embodiment includes a data parsing module 510, a type matching module 520, a scheme matching module 530, and a link generation module 540.

[0083] The data parsing module 510 is used to respond to the quick payment error on the user's payment page by parsing the error data of the quick payment error to obtain an error identifier. The error identifier includes at least one of the following: a limit release code indicating the need to release the payment limit control, and a limit error code indicating the existence of a limit error. The type matching module 520 is used to match the error coefficient according to the error identifier to determine the error type data corresponding to the error coefficient. The error type data is used to indicate the reason for the quick payment error. The solution matching module 530 is used to filter out the solution corresponding to the error type data from the preset error response library, and to perform error management and processing according to the solution process corresponding to the error type data based on the solution. The link generation module 540 is used to fill the solution into the preset solution command template to obtain a solution link that can be used as a quick solution processing entry. Once the solution link is triggered, it guides the user to perform the solution process.

[0084] In this embodiment, the data parsing module 510 parses the error data of the quick payment error to obtain error identifiers, including: extracting key fields from the error data, the key fields including at least one of the payment channel identifier, payment amount, user account status, error timestamp, and return code field; performing format standardization processing on the key fields, removing invalid characters and duplicate data to obtain valid fields; and matching the error identifiers corresponding to the valid fields based on a preset identifier mapping table, the identifier mapping table pre-stores the correspondence between the return code field, the number of key fields, and the limit unlock code and limit error code, respectively.

[0085] The type matching module 520 matches error coefficients based on error identifiers, including: In response to an error identifier being a credit limit de-control code, the error coefficient is a preset credit limit de-control weight, the value of which belongs to a preset first interval; in response to an error identifier being a limit error code, the error coefficient is a preset limit error weight, the value of which belongs to a preset second interval, the second interval being mutually exclusive with the first interval; in response to an error identifier being a combination of a limit error code and a credit limit de-control code, the error coefficient is a preset combination weight, the combination weight being the sum of the limit error code and the limit error weight, and the value of which belongs to a preset third interval; determining error type data corresponding to the error coefficient, including: in response to an error coefficient value belonging to the first interval, determining the error type as an account control type or a demand de-control type; in the case of an error type being an account control type, calling the user's account signing information; in response to the account signing information indicating the absence of account control hard indicators, then attaching a control description indicating whether or not there are account control hard indicators as the error type data; in the case of an error type In the case of a demand-driven deregulation type, the system retrieves the user's account signing information and triggers a credit limit verification process based on the account signing information and mobile banking signing information. This process verifies the credit limit increase based on the user's current payment account's single transaction limit, daily limit, and cumulative spending amount, generating verification result data, which is then used as error type data. If the error coefficient value falls within the second range, the system retrieves the user's account signing information and triggers a credit limit verification process based on the account signing information and mobile banking signing information. This process categorizes the account based on the user's current payment account's single transaction limit, daily limit, and cumulative spending amount, generating limit level data, which is then used as error type data. If the error coefficient value falls within the third range, the system retrieves the user's account signing information and generates an account tier activation request based on this information, which is then used as error type data. If the error coefficient value falls within the preset fourth range, the system uses verification failure data, which indicates a failure in basic parameter verification, as error type data.

[0086] The error handling library involved in module 530 of the solution stores the association between error resolution solutions and error type data. The association is a many-to-one mapping relationship, which is used to represent that one type of error data corresponds to at least two error resolution solutions. For error resolution solutions, if the error type data is a control description with or without account control hard indicators, the user's mobile banking signing information is extracted. If the mobile banking signing information indicates that the user meets the requirements for mobile banking self-service deregulation or manual remote deregulation, then the remote deregulation solution is used as the error resolution solution. If the error type data is verification result data, and the verification result data indicates that the credit limit increase verification has passed, the user's mobile banking signing information is extracted. For mobile banking account signing information, if the information indicates that the user meets the requirements for self-service credit limit increase via mobile banking or remote credit limit increase via manual processing, then the remote credit limit increase solution will be used as the solution. If the error type data is credit limit level data, the user's mobile banking account signing information will be extracted. If the information indicates that the user meets the requirements for self-service credit limit increase via mobile banking or remote credit limit increase via manual processing, then the remote credit limit level change solution will be used as the solution. If the error type data is an account tiered activation request, the guidance process for users to activate their accounts offline will be used as the solution. If the error type data is a verification failure, the statement explaining the data error will be used as the solution.

[0087] The error-solving command template involved in the link generation module 540 includes fixed fields and variable fields. The fixed fields are the error-solving operation guidance scripts, and the variable fields are the error-solving operation links, verification entry points, and parameter configuration entry points.

[0088] The link generation module 540 fills the error resolution solution into the preset error resolution command template, including: extracting the core operation path and entry address from the error resolution solution, filling the core operation path and entry address into the variable fields of the error resolution command template to obtain the error resolution template; performing format validation on the error resolution template, and in response to passing the validation, performing linking processing on the error resolution template to obtain an error resolution link that can be used as a quick error resolution processing entry.

[0089] In this embodiment, a storage monitoring unit is also included. This storage monitoring unit is used to store the error data, error type data, error resolution scheme and error resolution link to a preset log database after generating the error resolution link; monitor the user's triggering status of the error resolution link in real time; if the user does not trigger the error resolution link within the time limit, the error coefficient is rematched, the error type data is updated and a new error resolution scheme is matched.

[0090] According to embodiments of this application, any multiple modules among the data parsing module 510, type matching module 520, scheme matching module 530, and link generation module 540 can be merged into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module. According to embodiments of this application, at least one of the data parsing module 510, type matching module 520, scheme matching module 530, and link generation module 540 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in a suitable combination of any of these. Alternatively, at least one of the data parsing module 510, type matching module 520, scheme matching module 530, and link generation module 540 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0091] Figure 6 A block diagram schematically illustrates an electronic device suitable for implementing a quick payment error data processing method according to an embodiment of this application.

[0092] like Figure 6 As shown, an electronic device 600 according to an embodiment of this application includes a processor 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 portion 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this application.

[0093] RAM 603 stores various programs and data required for the operation of electronic device 600. Processor 601, ROM 602, and RAM 603 are interconnected via bus 604. Processor 601 executes various operations of the method flow according to embodiments of this application by executing programs in ROM 602 and / or RAM 603. It should be noted that the programs may also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 may also execute various operations of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0094] According to embodiments of this application, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to a bus 604. The electronic device 600 may also include one or more of the following components connected to the I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), 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, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 610 as needed so that computer programs read from it can be installed into the storage section 608 as needed.

[0095] This application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0096] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include ROM 602 and / or RAM 603 and / or one or more memories other than ROM 602 and RAM 603 described above.

[0097] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to enable the computer system to implement the item recommendation method provided in the embodiments of this application.

[0098] When the computer program is executed by the processor 601, it performs the functions defined in the system / apparatus of this application embodiment. According to the embodiments of this application, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0099] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 609, and / or installed from the removable medium 611. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0100] 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 processor 601, it performs the functions defined in the system of this application embodiment. According to the embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0101] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0102] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations 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 may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0103] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this application can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments and / or claims of this application can be combined or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

[0104] The embodiments of this application have been described above. However, these embodiments are merely illustrative and not intended to limit the scope of this application. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this application is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this application, and all such substitutions and modifications should fall within the scope of this application.

Claims

1. A method for processing error data of fast payment, characterized in that, The method comprises the following steps: In response to a quick payment error occurring on a user payment page, performing data analysis on error data of the quick payment error to obtain an error identifier, the error identifier including at least one of a quota control code for indicating that there is a need to cancel payment quota control and a limit error code for indicating that there is a limit quota error; Matching an error coefficient according to the error identifier to determine error type data corresponding to the error coefficient, the error type data being used to indicate the cause of the quick payment error; Filtering an error solution corresponding to the error type data from a preset error solution library to perform error management processing according to the error solution and the error solution process corresponding to the error type data; Filling the error solution into a preset error solution command template to obtain an error solution link that can be used as a quick error solution processing entry, the error solution link being triggered to guide the user to perform the error solution process. 2.The fast payment error reporting data processing method of claim 1, wherein, Performing data analysis on error data of the quick payment error to obtain an error identifier, comprising: Extracting key fields in the error data, the key fields including at least one of a payment channel identifier, a payment amount, a user account status, an error timestamp, and a return code field; Performing format standardization processing on the key fields to remove invalid characters and duplicate data to obtain valid fields; Matching an error identifier corresponding to the valid fields based on a preset identifier mapping table, the identifier mapping table pre-storing a correspondence between the return code field, the number of key fields, and the quota control code and the limit error code. 3.The shortcut payment error data processing method of claim 2, wherein, Matching an error coefficient according to the error identifier, comprising: In response to the error identifier being the quota control code, the error coefficient is a preset quota control weight, the value of the quota control weight belonging to a preset first interval; In response to the error identifier being the limit error code, the error coefficient is a preset limit error weight, the value of the limit error weight belonging to a preset second interval, the second interval being mutually exclusive with the first interval; In response to the error identifier being a combination of the limit error code and the quota control code, the error coefficient is a preset combination weight, the combination weight being a sum of the limit error code and the limit error weight, and the value of the combination weight belonging to a preset third interval. 4.The shortcut payment error data processing method of claim 3, wherein, Determining error type data corresponding to the error coefficient, comprising: In response to the value of the error coefficient belonging to the first interval, it is determined that the error type is an account management type or a demand control type, in the case of the error type being an account management type, the account subscription information of the user is called, and in response to the account subscription information representing the absence of an account management hard indicator, the management instruction with the absence of the account management hard indicator is taken as the error type data; in the case of the error type being a demand control type, the account subscription information of the user is called, and the quota verification process is triggered according to the account subscription information and the mobile bank subscription information, so as to perform the quota verification according to the single limit, the single-day limit and the cumulative consumption amount of the current payment account of the user, generate verification result data, and take the verification result data as the error type data; In response to the value of the error coefficient belonging to the second interval, the account subscription information of the user is called, and the quota verification process is triggered according to the account subscription information and the mobile bank subscription information, so as to perform account hierarchical classification according to the single limit, the single-day limit and the cumulative consumption amount of the current payment account of the user, generate limit level data, and take the limit level data as the error type data; In response to the value of the error coefficient belonging to the third interval, the account subscription information of the user is called, and the account hierarchical activation request is generated for the user based on the account subscription information, and the account hierarchical activation request is taken as the error type data; In response to the value of the error coefficient belonging to a preset fourth interval, the verification failure data representing the failure of the basic parameter verification is taken as the error type data.

5. The fast payment error data processing method of claim 4, wherein the error handling library stores an association relationship between error resolution schemes and error type data, the association relationship is a many-to-one mapping relationship, and the many-to-one mapping relationship represents that one error type data corresponds to at least two error resolution schemes. The preset error resolution command template includes a fixed field and a variable field, the fixed field is an error resolution operation guide phrase, and the variable field is an error resolution operation link, a verification entry and a parameter configuration entry. 6.The fast payment error reporting data processing method of claim 1, wherein, The filling of the error resolution scheme into the preset error resolution command template includes: 7.The shortcut payment error reporting data processing method of claim 6, wherein, extracting a core operation path and an entry address in the error resolution scheme, filling the core operation path and the entry address into the variable field of the error resolution command template to obtain an error resolution template; performing format verification on the error resolution template, and in response to the verification passing, performing link processing on the error resolution template to obtain an error resolution link which can be used as a fast error resolution processing entry. After the error resolution link is generated, further comprising: 8.The shortcut payment error reporting data processing method of claim 7, wherein, storing the error data, the error type data, the error resolution scheme and the error resolution link into a preset log database; monitoring the trigger state of the error resolution link by the user in real time, and if the user does not trigger the error resolution link within the time limit, re-matching the error coefficient, updating the error type data and matching a new error resolution scheme. Further comprising: 9.The shortcut payment error reporting data processing method of claim 5, wherein, ​ In response to the error type data being the management instruction with no account management hard indicator, mobile bank subscription information of the user is extracted, and if the mobile bank subscription information indicates that the user meets the mobile bank self-service control requirement or the manual acceptance remote control requirement, a remote control solution is taken as the error solution; In response to the error type data being the verification result data, in the case that the verification result data indicates that the limit amount verification is passed, mobile bank subscription information of the user is extracted, and if the mobile bank subscription information indicates that the user meets the mobile bank self-service limit amount requirement or the manual acceptance remote limit amount requirement, a remote limit amount solution is taken as the error solution; In response to the error type data being the limit amount level data, mobile bank subscription information of the user is extracted, and if the mobile bank subscription information indicates that the user meets the mobile bank self-service limit amount requirement or the manual acceptance remote limit amount requirement, a remote level change solution is taken as the error solution; In response to the error type data being the account classification activation request, a guide flow guide for guiding the user to activate the account offline is taken as the error solution; In response to the error type data being the verification failure data, a statement for explaining the data error is taken as the error solution.

10. A quick payment error data processing apparatus, comprising: a data analysis module configured to, in response to a quick payment error occurring on a user payment page, analyze error data of the quick payment error to obtain an error identifier, the error identifier including at least one of a limit amount control code used to indicate that there is a need to cancel the payment amount control and a limit error code used to indicate that there is a limit amount error; a type matching module configured to match an error coefficient according to the error identifier to determine error type data corresponding to the error coefficient, the error type data being used to indicate a reason for the quick payment error; a solution corresponding module configured to filter, in a preset error handling library, an error solution corresponding to the error type data to handle the error according to an error handling process corresponding to the error type data based on the error solution; a link generation module configured to fill the error solution into a preset error solution command template to obtain an error solution link that can be used as a quick error handling entry, the error solution link, once triggered, guiding the user to perform the error handling process.

11. An electronic device, comprising: one or more processors; a storage device configured to store one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method according to any one of claims 1-9.

12. A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1-9.

13. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-9.

Images