Payment error processing method, related device, equipment and storage medium

Abstract

The invention discloses a payment error processing method, a related device, equipment and a storage medium. The method comprises the steps of receiving a payment request sent by a first terminal for a target order; according to the payment request, executing payment processing operation to obtain a payment processing result; under the condition that the payment processing result meets the payment error reporting condition, payment error reporting information for the target order is generated, the payment error reporting information is used for prompting a payment error reporting party with an abnormal condition, and the payment error reporting party belongs to at least one of the first user account, the second user account and a payment system; and sending payment error information for the target order to the first terminal, so that the first terminal displays the payment error information for the target order. On one hand, the user can be promoted to solve the abnormal problem in a targeted manner, and on the other hand, the user can clearly know the reason of the abnormal condition, so that the anxiety of the user is relieved, and the user experience is enhanced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet, and particularly relates to a payment error processing method, related device, equipment and storage medium. BACKGROUND

[0002] In recent years, mobile payment has penetrated into our daily life, and payment application has become an essential product in our daily life. Among these payment applications, there is a function called "relative card", which can help users conveniently transfer money to their relatives or friends, helping users realize a kind of accompaniment to the daily life of their relatives and meet the emotional needs of being cared for and needed.

[0003] At present, in the related art, when the relative card is used for payment by the card holder, the payment needs to be completed through the account and payment method of the card donor. In this process, if there is a payment explicit failure or a payment non-explicit failure, etc., the original error information will be directly displayed to the card holder of the relative card, that is, the card holder of the relative card is informed that the payment is wrong.

[0004] However, the inventors have found that the current scheme at least has the following problems: for the card holder of the relative card, it is difficult to understand the error condition according to the original error information, thereby causing poor user experience. In view of the above problems, no effective solution has been proposed so far. SUMMARY

[0005] The embodiments of the present application provide a payment error processing method, related device, equipment and storage medium, which can on the one hand promote users to solve abnormal problems in a targeted manner, and on the other hand, enable users to clearly understand the reason for the abnormal condition, thereby helping to alleviate user anxiety and enhance user experience.

[0006] Therefore, the present application provides a payment error processing method, comprising:

[0007] receiving a payment request sent by a first terminal for a target order, wherein the first terminal has logged in a first user account, the payment request carries the first user account, a second user account and a payment amount, the first user account is an account initiating the payment request, and the second user account is an account to be deducted based on the payment request; payment amount;

[0008] According to the payment request, a payment processing operation is performed to obtain a payment processing result;

[0009] In the case that the payment processing result meets the payment error condition, a payment error information for the target order is generated, wherein the payment error information is used to prompt a payment error party in an abnormal condition, and the payment error party belongs to at least one of the first user account, the second user account and the payment system.

[0010] The sending module is configured to send the payment error information for the target order to the first terminal, so that the first terminal displays the payment error information for the target order.

[0011] Another aspect of the present application provides a payment error processing apparatus, comprising:

[0012] The receiving module is configured to receive a payment request sent by a first terminal for a target order, wherein the first terminal has logged in a first user account, the payment request carries the first user account, a second user account and a payment amount, the first user account is an account initiating the payment request, and the second user account is an account to be deducted by the payment amount based on the payment request;

[0013] The processing module is configured to perform a payment processing operation according to the payment request, and obtain a payment processing result;

[0014] The generating module is configured to generate payment error information for the target order in a case where the payment processing result satisfies a payment error condition, wherein the payment error information is used to prompt a payment error party in an abnormal situation, and the payment error party belongs to at least one of the first user account, the second user account and a payment system.

[0015] The sending module is configured to send the payment error information for the target order to the first terminal, so that the first terminal displays the payment error information for the target order.

[0016] In a possible design, in another implementation manner of the other aspect of the embodiment of the present application, the payment processing result comprises a payment verification result.

[0017] The processing module is specifically configured to perform payment verification processing on related information of the first user account according to the payment request, and obtain a payment verification result.

[0018] In a case where the payment verification result is a verification failure, it is determined that the payment processing result satisfies the payment error condition.

[0019] In a possible design, in another implementation manner of the other aspect of the embodiment of the present application,

[0020] The generating module is specifically configured to obtain a verification error reason in a case where the payment processing result satisfies the payment error condition.

[0021] If the verification error reason indicates that the related information of the first user account is in an abnormal situation, the payment error information for the target order is generated according to the abnormal situation of the first user account, wherein the payment error information is used to prompt the first user account in the abnormal situation.

[0022] In a possible design, in another implementation manner of another aspect of the embodiment of the present application,

[0023] The generating module is specifically configured to acquire a reason for the verification error in a case where the payment processing result satisfies the payment error condition.

[0024] If the reason for the verification error indicates that the payment system is in an abnormal condition, the payment error information for the target order is generated according to the abnormal condition of the payment system, where the payment error information is used to prompt the abnormal condition of the payment system.

[0025] In a possible design, in another implementation manner of another aspect of the embodiment of the present application, the payment processing result includes a payment deduction result.

[0026] The processing module is specifically configured to perform payment deduction processing on a payment round card list associated with the second user account according to the payment request, to obtain a payment deduction result, where the payment round card list includes at least one payment account arranged in sequence.

[0027] In a case where the payment deduction result is a deduction failure, it is determined that the payment processing result satisfies the payment error condition.

[0028] In a possible design, in another implementation manner of another aspect of the embodiment of the present application, the payment round card list includes only the target payment account.

[0029] The processing module is specifically configured to determine the target payment account from the payment round card list associated with the second user account according to the payment request.

[0030] The target payment account is subjected to payment deduction processing, to obtain a payment deduction result for the target payment account.

[0031] In a possible design, in another implementation manner of another aspect of the embodiment of the present application,

[0032] The generating module is specifically configured to acquire a deduction error reason of the target payment account in a case where the payment processing result satisfies the payment error condition.

[0033] If the deduction error reason indicates that the target payment account is in an abnormal condition, the payment error information for the target order is generated according to the abnormal condition corresponding to the target payment account, where the payment error information is used to prompt the abnormal condition of the second user account.

[0034] In a possible design, in another implementation manner of another aspect of the embodiment of the present application,

[0035] The generating module is specifically configured to acquire a deduction error reason of the target payment account in a case where the payment processing result satisfies the payment error reporting condition.

[0036] If the deduction error reason indicates that the payment system is in an abnormal condition, payment error information for the target order is generated according to the abnormal condition of the payment system, wherein the payment error information is used to prompt the abnormal condition of the payment system.

[0037] In a possible design, in another implementation manner of another aspect of the embodiment of the present application, the payment round card list includes a first payment account and a second payment account arranged in sequence.

[0038] The processing module is specifically configured to determine the first payment account from the payment round card list associated with the second user account according to the payment request.

[0039] The first payment account is subjected to payment deduction processing, and a processing result for the first payment account is obtained.

[0040] If the processing result of the first payment account indicates processing failure, the second payment account is subjected to payment deduction processing, and a processing result for the second payment account is obtained.

[0041] If the processing result of the second payment account indicates processing failure, a payment deduction result is acquired according to the payment round card list.

[0042] In a case where the payment deduction result is deduction failure, it is determined that the payment processing result satisfies the payment error reporting condition.

[0043] In a possible design, in another implementation manner of another aspect of the embodiment of the present application,

[0044] The generating module is specifically configured to acquire a deduction error reason of the target payment account in a case where the payment processing result satisfies the payment error reporting condition.

[0045] If the deduction error reason of the first payment account indicates that the first payment account is in an abnormal condition, and the deduction error reason of the second payment account indicates that the second payment account is in an abnormal condition, payment error information for the target order is generated according to the abnormal conditions of the first payment account and the second payment account, wherein the payment error information is used to prompt the abnormal condition of the second user account.

[0046] In a possible design, in another implementation manner of another aspect of the embodiment of the present application,

[0047] The generating module is specifically configured to acquire a first error code according to the deduction error reason of the first payment account.

[0048] According to the deduction error reason of the second payment account, a second error code is obtained;

[0049] The first error code and the second error code are converted into a gift card party error code;

[0050] According to the gift card party error code, payment error information for the target order is generated.

[0051] In a possible design, in another implementation manner of another aspect of the embodiment of the application,

[0052] The generation module is specifically configured to obtain the deduction error reason of the first payment account and the deduction error reason of the second payment account in a case where the payment processing result meets the payment error condition.

[0053] If the deduction error reason of the first payment account indicates that the payment system is in an abnormal condition, and the deduction error reason of the second payment account indicates that the payment system is in an abnormal condition, payment error information for the target order is generated according to the abnormal condition of the payment system, wherein the payment error information is used to prompt the abnormal condition of the payment system.

[0054] In a possible design, in another implementation manner of another aspect of the embodiment of the application,

[0055] The generation module is specifically configured to obtain a third error code according to the deduction error reason of the first payment account.

[0056] According to the deduction error reason of the second payment account, a fourth error code is obtained.

[0057] The third error code and the fourth error code are converted into a system party error code.

[0058] According to the system party error code, payment error information for the target order is generated.

[0059] In a possible design, in another implementation manner of another aspect of the embodiment of the application,

[0060] The generation module is specifically configured to obtain the deduction error reason of the first payment account and the deduction error reason of the second payment account in a case where the payment processing result meets the payment error condition.

[0061] If the deduction error reason of the first payment account indicates that the first payment account is in an abnormal condition, and the deduction error reason of the second payment account indicates that the payment system is in an abnormal condition, payment error information for the target order is generated according to the abnormal condition of the first payment account and the abnormal condition of the payment system; or

[0062] If the first payment account deduction error cause indicates that the payment system is abnormal, and the second payment account deduction error cause indicates that the second payment account is abnormal, the payment error information for the target order is generated according to the abnormality of the second payment account and the abnormality of the payment system.

[0063] In a possible design, in another implementation manner of the other aspect of the embodiment of the present application,

[0064] The generation module is specifically configured to acquire a fifth error code according to the first payment account deduction error cause.

[0065] acquire a sixth error code according to the second payment account deduction error cause.

[0066] convert the fifth error code and the sixth error code into a comprehensive error code.

[0067] generate the payment error information for the target order according to the comprehensive error code.

[0068] In a possible design, in another implementation manner of the other aspect of the embodiment of the present application,

[0069] The sending module is further configured to, if the payment error side belongs to the second user account, send the payment error information for the target order to the second terminal to enable the second terminal to display the payment error information for the target order, after the payment error information for the target order is generated in the case that the payment processing result satisfies the payment error condition, wherein the second terminal has logged in the second user account.

[0070] Another aspect of the present application provides a computer device, comprising a memory and a processor, the memory stores a computer program, and the processor implements the method of the above aspects when executing the computer program.

[0071] Another aspect of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method of the above aspects.

[0072] Another aspect of the present application provides a computer program product, comprising a computer program, and the computer program is executed by a processor to implement the method of the above aspects.

[0073] From the above technical solutions, it can be seen that the embodiment of the present application has the following advantages:

[0074] In the embodiment of the present application, a payment error processing method is provided. First, the server responds to the payment request sent by the first terminal for the target order, and then starts to perform the payment processing operation, so as to obtain the payment processing result. In the case that the payment processing result meets the payment error condition, the payment error information for the target order is generated. Finally, the payment error information for the target order is sent to the first terminal, so that the first terminal displays the payment error information for the target order. In the above manner, for the card taking party of the relative card, the payment error party in the abnormal situation can be clearly determined through the payment error information, so as to effectively distinguish whether the abnormality is caused by the card taking party of the relative card, or the abnormality is caused by the card giving party of the relative card, or the abnormality is caused by the payment system. Therefore, on the one hand, the user can solve the abnormal problem in a targeted manner, and on the other hand, the user can clearly determine the cause of the abnormal situation, thereby helping to reduce user anxiety and enhance user experience. BRIEF DESCRIPTION OF DRAWINGS

[0075] Figure 1 A set of related schematic diagrams of the relative card giving process in the embodiment of the present application;

[0076] Figure 2 A set of related schematic diagrams of the relative card taking process in the embodiment of the present application;

[0077] Figure 3 A set of related schematic diagrams of the relative card payment process in the embodiment of the present application;

[0078] Figure 4 An implementation environment schematic diagram of the payment error processing method in the embodiment of the present application;

[0079] Figure 5 A flowchart of the payment error processing method in the embodiment of the present application;

[0080] Figure 6 An interface schematic diagram based on the card taking party error in the embodiment of the present application;

[0081] Figure 7 An interface schematic diagram based on the payment system error in the embodiment of the present application;

[0082] Figure 8 An interface schematic diagram based on the card giving party error in the embodiment of the present application;

[0083] Figure 9 Another interface schematic diagram based on the payment system error in the embodiment of the present application;

[0084] Figure 10 Another interface schematic diagram based on the card giving party error in the embodiment of the present application;

[0085] Figure 11 FIG. 1 is a schematic diagram of an interface for reporting an error based on an escape function according to an embodiment of the present application;

[0086] Figure 12 FIG. 2 is a schematic diagram of another interface for reporting an error based on a payment system according to an embodiment of the present application;

[0087] Figure 13 FIG. 3 is a schematic diagram of an interface for reporting an error based on an escape function according to an embodiment of the present application;

[0088] Figure 14 FIG. 4 is a schematic diagram of an interface for reporting an error based on a gift card provider and a payment system according to an embodiment of the present application;

[0089] Figure 15 FIG. 5 is a schematic diagram of another interface for reporting an error based on an escape function according to an embodiment of the present application;

[0090] Figure 16 FIG. 6 is a schematic diagram of an interface for providing payment error information to a gift card provider according to an embodiment of the present application;

[0091] Figure 17 FIG. 7 is a schematic diagram of an interaction flow for payment error processing according to an embodiment of the present application;

[0092] Figure 18 FIG. 8 is a schematic diagram of a device for payment error processing according to an embodiment of the present application;

[0093] Figure 19 FIG. 9 is a schematic diagram of a server according to an embodiment of the present application. DETAILED DESCRIPTION

[0094] The embodiments of the present application provide a payment error processing method, related device, equipment and storage medium, which can help users to solve abnormal problems and find the reasons for the abnormal problems, thereby reducing user anxiety and enhancing user experience.

[0095] The terms "first", "second", "third", "fourth" and the like in the description and claims of the present application and above drawings (if any) are used to distinguish between similar objects, not necessarily in an ordinal sense or in a sequential sense. It should be understood that the use of such terms is interchangeable under appropriate circumstances such that the embodiments of the present application described herein are capable of operating in other sequences than illustrated or described herein. Moreover, the terms "comprise" and "comprising" and their any variations, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or apparatus that comprises a list of steps or units is not necessarily limited to those steps or units which are clearly recited, but can include other not expressly recited steps or units without departing from the process, method, product, or apparatus.

[0096] The "family card" function provided in the payment application is a new type of payment method with the advantage of consumption transparency. The family card is designed to make it more convenient for family members to transfer funds and provide consumption support. Therefore, when the card holder uses the family card for consumption, the system will automatically notify the card giver of the consumption information, ensuring that both parties have a clear understanding of the consumption. The consumption transparency of the family card provides a more secure and convenient payment method. Through real-time notification, detailed record, and quota management, it not only helps better understand and manage one's own consumption, but also enhances the emotional connection and trust between family members.

[0097] However, the card holder may encounter various error situations when using the family card for payment. But for the card holder, it is difficult to distinguish the error reporting party, which leads to unclear and difficult-to-understand error reporting, thus easily causing the card holder to feel anxious and panicked.

[0098] Based on this, in the embodiments of the present application, a payment error processing method is provided, which can distinguish and classify the error information of the family card, thereby clearly identifying the responsible party and making relevant processing, thereby improving the user experience of using the family card for payment. The payment error processing method provided in the present application includes at least one of the following scenarios when applied.

[0099] I. Electronic red envelope;

[0100] There are usually two forms of electronic red envelope distribution. The first is ordinary equal red envelope, which is sent one-to-one or one-to-many. The second is "lucky group red envelope", that is, the user sets the total amount and the number of red envelopes, and then randomly generates red envelopes of different amounts. Taking user A sending an electronic red envelope as an example, user A needs to input the amount and click on the red envelope. At this time, user A can use the family card given by the card giver to pay, and the payment will be deducted from the payment method set by the card giver.

[0101] II. Face-to-face payment;

[0102] Face-to-face code scanning payment has become one of the most convenient payment methods in modern society. Through smart phones and other devices, code scanning payment can quickly and conveniently complete the payment process. Taking user A's code scanning payment as an example, user A uses a mobile phone to scan the two-dimensional code provided by the merchant, and after inputting the payment amount, can use the family card given by the card giver to pay, and the payment will be deducted from the payment method set by the card giver.

[0103] It should be noted that the above application scenarios are only examples, and the payment error processing method provided in the present application can also be applied to other scenarios (such as electronic transfer, etc.), which are not limited here.

[0104] For the convenience of understanding, the relevant operation processes of the relative card will be described respectively.

[0105] I. Relative card gifting process;

[0106] Specifically, please refer to Figure 1 , Figure 1 A set of related schematic diagrams of the relative card gifting process in the embodiments of the present application are shown in Figure 1 Fig. (A), after the card gifter enters the payment application, enters the "wallet" interface, and clicks the "relative card" control indicated by A1, an interface as shown in Figure 1 Fig. (B) is displayed. The user can click the "gift relative card" control indicated by A2, and an interface as shown in Figure 1 Fig. (C) is displayed. The user selects a certain gift object (for example, clicks the gift object "child" indicated by A3), and an interface as shown in Figure 1 Fig. (D) is displayed. Based on this, the user needs to set the monthly consumption upper limit in the area indicated by A4, for example, 200 yuan. After payment, an interface as shown in Figure 1 Fig. (E) is displayed, and the user needs to input the payment password in the area indicated by A5. After the payment password verification is successful, an interface as shown in Figure 1 Fig. (F) is displayed. Then, the user can click the preferred payment method indicated by A6, and thus can select a payment method as the preferred payment method in the interface as shown in Figure 1 Fig. (G). After the selection is completed, the user can view the information related to the card gifting of the user through the interface as shown in Figure 1 Fig. (H).

[0107] II. Relative card receiving process;

[0108] Specifically, please refer to Figure 2 , Figure 2 A set of related schematic diagrams of the relative card receiving process in the embodiments of the present application are shown in Figure 2 Fig. (A), a friend receives a relative card through the chat interface provided by the payment application. Based on this, the card gifter can modify the consumption upper limit or modify the preferred payment method through the interface as shown in Figure 2 Fig. (B). In addition, the card gifter can also view the consumption situation of the card receiver through the interface as shown in Figure 2 Fig. (C).

[0109] III. Relative card payment process;

[0110] Specifically, please refer to Figure 3 , Figure 3 A set of related schematic diagrams of the relative card payment process in the embodiments of the present application are shown inFigure 3 As shown in FIG. A, after the user receives the relative card, the user can use the relative card to pay when receiving the electronic red packet. As shown in FIG. Figure 3 As shown in FIG. B, during the payment process, the payment method set by the gift card provider is used to deduct the payment, for example, the payment is deducted from the change.

[0111] The method provided by the present application can be applied to Figure 4 As shown in the implementation environment, the implementation environment includes a terminal 110 and a server 120, and the terminal 110 and the server 120 can communicate through a communication network 130. The communication network 130 uses standard communication technology and / or protocol, and is usually the Internet, but can also be any network, including but not limited to any combination of Bluetooth, local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, private network, or virtual private network. In some embodiments, the above-mentioned data communication technology can be replaced or supplemented by customized or dedicated data communication technology.

[0112] The terminal 110 involved in the present application includes but is not limited to a mobile phone, a tablet computer, a notebook computer, a desktop computer, a smart voice interaction device, a virtual reality device, a smart home appliance, a vehicle-mounted terminal, an aircraft, etc. The client is deployed on the terminal 110, and the client can run on the terminal 110 in the form of a browser, or run on the terminal 110 in the form of an independent application (APP) or a mini program, etc.

[0113] The server 120 involved in the present application can be a stand-alone physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and basic cloud computing services such as big data and artificial intelligence (AI) platforms.

[0114] In combination with the above implementation environment, in step B1, the terminal 110 sends a payment request for a target order to the server 120 through the communication network 130. In step B2, the server 120 performs a payment processing operation according to the payment request, and obtains a payment processing result. In step B3, in the case where the payment processing result satisfies a payment error condition, the server 120 generates payment error information, wherein the payment error information describes a payment error party in the abnormal situation. In step B4, the server 120 sends the payment error information to the terminal 110 through the communication network 130. In step B5, the terminal 110 displays the payment error information.

[0115] In view of the fact that the present application involves some terms related to the professional field, in order to facilitate understanding, the following will be explained.

[0116] (1) Relative card: a payment "relative card" can be conveniently opened for friends on the payment application, realizing the purpose of "friend consumption, I pay the bill", focusing on solving the problem that relatives and friends have no available payment methods. After receiving the relative card sent by the friend, the relative card can be used as a payment channel when paying.

[0117] (2) Gift card party (or, relative card gift party): the user can give a relative card to a friend, including his or her parents, children, etc.

[0118] (3) Card receiving party (or, relative card receiving party): after receiving the application message sent by the gift card party, the card receiving party can receive the relative card given by the gift card party.

[0119] (4) Relative card limit: when the gift card party gives the relative card to the card receiving party, the card receiving party can set the upper limit of the relative card consumption per month, and the card receiving party can use the relative card within the limit of the upper limit of the relative card consumption. For example, the gift card party gives the card receiving party a relative card with a consumption limit of 3000 yuan per month, so the card receiving party can consume within the limit of 3000 yuan.

[0120] (5) Relative card payment: after receiving the relative card given by the gift card party, the card receiving party can use the relative card for electronic payment.

[0121] (6) Priority deduction method: the deduction is made from the payment method set by the gift card party. After the deduction is successful, the gift card party will receive a deduction message reminder.

[0122] (7) Payment explicit error: refers to the fact that the payment result has an explicit error, and the process can be terminated, for example, payment password error, or insufficient balance error information.

[0123] (8) Payment non-explicit error: refers to the payment result is not explicit, that is, the payment may have been successful, at this time it can be checked or re-paid, for example, the error information of timeout, network exception, etc.

[0124] (9) Round card: refers to using polling to deduct the card information of the card donor. For example, the card donor has three cards, the first card fails to deduct, then the second card is polled, the second card fails to deduct, then the third card is polled, until the deduction is successful or all the polling is completed, that is, the polling is terminated.

[0125] (10) Escaping: refers to making a more explicit explanation of the error code, so that the user can understand. In addition, escaping can also refer to converting into a multilingual version, for example, the language set by the customer service is Chinese, then it is displayed in Chinese, and for example, the language set by the customer service is English, then it is displayed in English.

[0126] In combination with the above introduction, the payment error processing method in the present application will be introduced below, please refer to Figure 5 The payment error processing method in the embodiment of the present application can be completed independently by the server, or can be completed by the server in cooperation with the terminal, and the method provided by the present application comprises:

[0127] 210. Receive a payment request sent by a first terminal for a target order, wherein the first terminal has logged in a first user account, the payment request carries the first user account, a second user account and a payment amount, the first user account is the account initiating the payment request, and the second user account is the account to be deducted based on the payment request;

[0128] In one or more embodiments, the card recipient uses the first user account, and the card donor uses the second user account. Wherein the card recipient logs in the first user account on the first terminal, and the card donor logs in the second user account on the second terminal. Based on this, the card recipient can trigger a payment request for the target order through the first terminal to the server, and the target order can be a face-to-face payment order, or a transfer order, or a red envelope sending order, which is not limited here.

[0129] Specifically, when the card recipient selects to use the relative card to pay for the target order, the first user account, the second user account and the payment amount will be carried in the payment request. Based on this, the server can know from the payment request that the corresponding payment amount needs to be deducted from the account corresponding to the second user account, so as to complete the target order triggered by the first user account.

[0130] It can be understood that the server involved in the present application can be a server integrating payment function, asynchronous processing function and account in-out function, or can be multiple servers with different functions, which is not limited here.

[0131] 220、according to the payment request, performing a payment processing operation to obtain a payment processing result;

[0132] In one or more embodiments, the server responds to the payment request sent by the first terminal, and starts to perform a corresponding payment processing operation to obtain a corresponding payment processing result.

[0133] Specifically, the server first detects whether the card-receiving party has an error, and then detects whether the card-giving party has an error. Alternatively, the server first detects whether the card-giving party has an error, and then detects whether the card-receiving party has an error. In this way, the server can obtain the payment processing result according to the error condition.

[0134] 230、in a case where the payment processing result satisfies a payment error condition, generating payment error information for the target order, wherein the payment error information is used to prompt a payment error party in an abnormal situation, and the payment error party belongs to at least one of the first user account, the second user account, and the payment system;

[0135] In one or more embodiments, if the payment processing result satisfies the payment error condition, the server generates payment error information corresponding to the target order according to the error reason. In the payment error information, the payment error party in an abnormal situation is explicitly prompted, for example, the first user account is prompted to be in an abnormal situation, or the second user account is prompted to be in an abnormal situation, or the payment system is prompted to be in an abnormal situation.

[0136] 240、sending the payment error information for the target order to the first terminal, so that the first terminal displays the payment error information for the target order.

[0137] In one or more embodiments, after generating the payment error information, the server sends the payment error information for the target order to the first terminal used by the card-receiving party, so that the first terminal displays the payment error information.

[0138] In the embodiments of the present application, a payment error processing method is provided. Through the above-mentioned manner, for the card-receiving party of the relative card, the payment error party in an abnormal situation can be explicitly prompted through the payment error information, so as to effectively distinguish whether the card-receiving party of the relative card is in an abnormal situation, or the card-giving party of the relative card is in an abnormal situation, or the payment system is in an abnormal situation. In this way, on the one hand, the user can solve the abnormal problem in a targeted manner, and on the other hand, the user can clearly know the reason for the abnormal situation, thereby reducing the user's anxiety and enhancing the user experience.

[0139] Optionally, in the above-mentioned Figure 5According to one or more embodiments, the payment processing result includes a payment verification result.

[0140] According to the payment request, the payment processing operation is performed to obtain a payment processing result, which can specifically include:

[0141] According to the payment request, the payment verification processing is performed on the related information of the first user account to obtain a payment verification result.

[0142] In a case where the payment verification result is a verification failure, it is determined that the payment processing result satisfies a payment error reporting condition.

[0143] In one or more embodiments, a payment verification processing method for a cardholder is introduced. As known from the foregoing embodiments, the cardholder triggers a payment operation using a first user account, and based on this, the server needs to perform payment verification processing on the related information of the first user account to obtain a payment verification result.

[0144] Illustratively, the related information of the first user account can include a payment password input by the cardholder during the payment process. Based on this, the server needs to compare the payment password with a pre-stored password, and if the comparison is inconsistent, the verification fails, i.e., the payment verification result is a verification failure. If the related information of the first user account is all verified successfully, the payment verification result is a verification success.

[0145] Illustratively, the related information of the first user account can include biological information (e.g., fingerprint, face, palm print, etc.) collected by the cardholder during the payment process. Based on this, the server needs to compare the biological information with pre-stored biological information, and if the comparison is inconsistent, the verification fails, i.e., the payment verification result is a verification failure. If the related information of the first user account is all verified successfully, the payment verification result is a verification success.

[0146] Illustratively, the related information of the first user account can include an account status. Based on this, the server needs to query the account status corresponding to the first user account, and if the account status is a frozen state, the verification fails, i.e., the payment verification result is a verification failure. If the related information of the first user account is all verified successfully, the payment verification result is a verification success.

[0147] It should be noted that when the server performs payment verification processing (e.g., password comparison, biological information comparison, account status query, etc.), network anomalies, request timeouts, system failures, etc. may also occur. And these conditions will also cause the payment verification result to be a verification failure.

[0148] Secondly, in the embodiment of the application, a payment verification processing method for the cardholder is provided. Through the above method, the server needs to verify the processing flow of the cardholder, and if the cardholder has an error, there is no need to perform card rotation. Thus, the corresponding payment error information can be directly sent to the cardholder, thereby saving the resources required for card rotation.

[0149] Optionally, in the above Figure 5 Based on one or more embodiments, in another optional embodiment of the application, if the payment processing result meets the payment error condition, the payment error information for the target order is generated, which can specifically include:

[0150] In the case where the payment processing result meets the payment error condition, the reason for the verification error is obtained.

[0151] If the reason for the verification error indicates that the information related to the first user account is in an abnormal condition, the payment error information for the target order is generated according to the abnormal condition of the first user account, wherein the payment error information is used to prompt the abnormal condition of the first user account.

[0152] In one or more embodiments, a payment error processing method is introduced. As known from the foregoing embodiments, if the payment verification result is verification failure, the server determines that the payment processing result meets the payment error condition. Based on this, the server needs to obtain the reason for the verification error and further make a corresponding prompt according to the reason. In the following, the reason for the verification error is taken as an example of the cardholder inputting an incorrect payment password.

[0153] Specifically, for ease of understanding, taking the use of a relative card to pay an electronic red packet as an example, please refer to Figure 6 , Figure 6 An interface based on the cardholder error in the embodiment of the application is shown in FIG. A of Figure 6 When the user uses a relative card to pay and inputs a payment password, a payment control indicated by C1 is clicked, that is, a payment request for a target order is triggered. The server responds to the payment request and performs payment verification processing on the information related to the first user account. Assuming that the payment verification result is verification failure and the reason for the verification error is that the payment password does not match the pre-stored password, the interface shown in FIG. B of Figure 6 is displayed. C2 is used to indicate the payment error information, for example, the payment error information is "incorrect payment password, please input the payment password again", and it can be seen that the payment error information is used to prompt the abnormal condition of the cardholder.

[0154] Again, in the embodiment of the present application, a payment error processing mode is provided. Through the above mode, the server generates corresponding payment error information according to the reason for verifying the error, and based on this, if the related information of the first user account is in an abnormal condition, the card holder can clearly understand from the payment error information that the reason why the relative card cannot be used for payment is that the card holder himself. Therefore, the card holder can actively solve the problem, thereby effectively improving the user experience of using the relative card for payment.

[0155] Optionally, in the above Figure 5 Based on one or more embodiments, in another optional embodiment of the present application, if the payment processing result meets the payment error condition, the payment error information for the target order is generated, which can specifically include:

[0156] In the case where the payment processing result meets the payment error condition, the reason for verifying the error is obtained.

[0157] If the reason for verifying the error indicates that the payment system is in an abnormal condition, the payment error information for the target order is generated according to the abnormal condition of the payment system, wherein the payment error information is used to prompt the abnormal condition of the payment system.

[0158] In one or more embodiments, another payment error processing mode is introduced. As known from the foregoing embodiment, if the payment verification result is verification failure, the server determines that the payment processing result meets the payment error condition. Based on this, the server needs to obtain the reason for verifying the error and further make corresponding prompts according to the reason. In the following, the reason for verifying the error is taken as an example of the abnormal condition of the payment system.

[0159] Specifically, for ease of understanding, taking the use of a relative card to pay an electronic red packet as an example, please refer to Figure 7 , Figure 7 An interface diagram based on the payment system error in the embodiment of the present application is shown in Figure 7 (A) of FIG. 1. When the user uses a relative card to pay, the payment password is input. When the payment control indicated by D1 is clicked, that is, the payment request for the target order is triggered. The server responds to the payment request and performs payment verification processing on the related information of the first user account. In this process, if the payment system is abnormal, the interface shown in Figure 7 (B) of FIG. 1 is displayed. Wherein, D2 is used to indicate the payment error information, for example, the payment error information is "payment system failure in the verification process, being repaired, please try later", it can be seen that the payment error information is used to prompt the abnormal condition of the payment system.

[0160] Again, in the embodiments of the present application, another payment error processing mode is provided. Through the above mode, the server generates corresponding payment error information according to the reason for verifying the error, and based on this, if the payment system has an abnormal situation, the cardholder can clearly understand the reason why the relative card cannot be used for payment through the payment error information. Therefore, the cardholder can wait for the payment system to be repaired, thereby improving the feasibility of the scheme.

[0161] Optionally, in the above Figure 5 Based on one or more embodiments, in another optional embodiment provided by the embodiments of the present application, the payment processing result includes a payment deduction result.

[0162] According to the payment request, the payment processing operation is performed to obtain a payment processing result, which can specifically include:

[0163] According to the payment request, the payment deduction processing is performed on the payment round card list associated with the second user account to obtain a payment deduction result, wherein the payment round card list includes at least one payment account arranged in order.

[0164] In the case of a payment deduction failure, it is determined that the payment processing result meets the payment error condition.

[0165] In one or more embodiments, a payment verification processing mode for the gift card party is introduced. As known from the foregoing embodiments, the cardholder triggers the payment operation using the first user account, based on which the server needs to perform payment deduction processing on the payment round card list associated with the second user account to obtain a payment deduction result.

[0166] Specifically, the server needs to first obtain the payment round card list associated with the second user account, wherein the payment round card list includes at least one payment account arranged in order. For ease of understanding, please refer to Table 1, which is an illustration of the payment round card list.

[0167] Table 1

[0168] Wheel card sequence Payment account First Change Second A bank savings card (tail number 0451) Third B bank credit card (tail number 7382)

[0169] Based on this, the server first performs payment deduction processing on the payment account "change", if the deduction is successful, no need to perform the round card processing, that is, the payment deduction result is deduction success. If the deduction fails due to some reasons (for example, account exception, insufficient balance, etc.), continue to perform the round card processing, that is, perform payment deduction processing on the payment account "A bank savings card (tail number 0451)". Similarly, if the deduction is successful, no need to perform the round card processing, that is, the payment deduction result is deduction success. If the deduction fails, continue to perform the round card processing, that is, perform payment deduction processing on the payment account "B bank credit card (tail number 7382)". If the deduction is successful, no need to perform the round card processing, that is, the payment deduction result is deduction success. If the deduction fails, determine that the payment deduction result is deduction failure.

[0170] It should be noted that when the server performs the payment deduction processing, network exception, request timeout, system failure and the like may also occur. And these conditions will also cause the payment deduction result to be verification failure.

[0171] Secondly, in the embodiment of the application, a payment verification processing method for the card donor is provided. Through the above method, the server needs to verify the processing flow of the card donor. If the card donor has an error, the corresponding payment error information is directly sent to the card holder, so that the card holder can timely understand the payment error party, thereby helping to reduce user anxiety and enhance user experience.

[0172] Optionally, in the above Figure 5 Based on one or more embodiments, in another optional embodiment provided by the embodiment of the application, the payment round card list only includes the target payment account;

[0173] According to the payment request, the payment deduction processing is performed on the payment round card list associated with the second user account, and the payment deduction result is obtained, which can specifically include:

[0174] According to the payment request, the target payment account is determined from the payment round card list associated with the second user account;

[0175] The target payment account is subjected to payment deduction processing, and the payment deduction result for the target payment account is obtained.

[0176] In one or more embodiments, a round card implementation method based on a single payment account is introduced. As known from the foregoing embodiments, there can be only one payment account in the payment round card list associated with the second user account, at this time, the payment account is referred to as the target payment account.

[0177] Specifically, the server performs a payment deduction process on the target payment account (e.g., "A Bank Savings Card (last four digits 0451)"), and if the deduction is successful, it means that the payment deduction result is a successful deduction. If the deduction of the target payment account fails due to some reason (e.g., account abnormality, insufficient balance, etc.), it is determined that the payment deduction result is a failed deduction.

[0178] Again, in the embodiments of the present application, a method for implementing a round card based on a single payment account is provided. Through the above method, if there is only one payment account in the payment round card list associated with the second user account, the payment deduction result can be obtained after performing a payment deduction process on the payment account. Thus, the feasibility and operability of the scheme are improved.

[0179] Optionally, in the above Figure 5 Based on one or more embodiments, in another optional embodiment of the present application, in the case where the payment processing result satisfies the payment error condition, payment error information for the target order is generated, which can specifically include:

[0180] In the case where the payment processing result satisfies the payment error condition, the deduction error reason of the target payment account is obtained.

[0181] If the deduction error reason indicates that the target payment account has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation corresponding to the target payment account, wherein the payment error information is used to prompt that the second user account has an abnormal situation.

[0182] In one or more embodiments, another payment error processing method is introduced. As known from the foregoing embodiments, if the payment deduction result is a failed deduction, the server determines that the payment processing result satisfies the payment error condition. Based on this, the server needs to obtain the reason for the deduction error of the target payment account, and further make a corresponding prompt according to the reason. In the following, the reason for the deduction error is taken as an example of insufficient balance of the target payment account.

[0183] Specifically, for ease of understanding, taking the use of a relative card to pay an electronic red packet as an example, please refer to Figure 8 , Figure 8 An interface diagram based on a gift card error in the embodiments of the present application is shown in Figure 8 When the payment control indicated by E1 is clicked, that is, a payment request for the target order is triggered. The server responds to the payment request and performs a payment deduction process on the target payment account used by the second user account. Assuming that the payment deduction process is a failed deduction, and the reason for the failed deduction is that the target payment account has insufficient balance, a display as shown in Figure 8The interface shown in Figure (B) is shown in Figure 1. E2 is used to indicate a payment error message. For example, the payment error message is "The gifter's balance is insufficient, and the transaction cannot be completed temporarily." This indicates that the payment error message is used to inform the gifter of an abnormal situation.

[0184] Furthermore, an embodiment of the present application provides another method for handling payment errors. Using this method, the server generates corresponding payment error information based on the reason for the deduction error. Based on this, if the relevant information of the second user account is abnormal, the card recipient can clearly understand from the payment error information that the reason for the inability to use the Family Card payment is the gift of the card. This allows the card recipient to contact the gift of the card to resolve the issue, thereby improving the user experience of the Family Card.

[0185] Optionally, in the above Figure 5 On the basis of one or more corresponding embodiments, in another optional embodiment provided by the embodiments of the present application, when the payment processing result meets the payment error reporting condition, generating payment error information for the target order may specifically include:

[0186] If the payment processing result meets the payment error conditions, obtain the deduction error reason of the target payment account;

[0187] If the deduction error reason indicates that an abnormality has occurred in the payment system, a payment error message for the target order is generated based on the abnormality in the payment system, wherein the payment error message is used to prompt that an abnormality has occurred in the payment system.

[0188] In one or more embodiments, another method for handling payment errors is described. As can be seen from the aforementioned embodiments, if the payment deduction result indicates a payment failure, the server determines that the payment processing result meets the payment error conditions. Based on this, the server needs to obtain the reason for the payment error and further provide a corresponding prompt based on the reason. The following example describes a payment error caused by an abnormality in the payment system.

[0189] Specifically, for ease of understanding, take the example of using a relative card to pay for an electronic red envelope, please refer to Figure 9 , Figure 9 This is another interface diagram based on the payment system error in the embodiment of the present application, such as Figure 9 As shown in Figure (A), the user uses a relative card when making a payment. When the payment control indicated by F1 is clicked, a payment request for the target order is triggered. The server responds to the payment request and deducts the payment from the target payment account used by the second user account. During this process, if the payment system encounters an abnormality, the following message will be displayed: Figure 9The interface shown in Figure (B) is shown in Figure 1. F2 is used to indicate a payment error message. For example, the payment error message is "The payment system failed during the deduction process and is being repaired. Please try again later." This indicates that the payment error message is used to indicate an abnormality in the payment system.

[0190] Furthermore, the present embodiment provides another method for handling payment errors. With this method, the server generates corresponding payment error information based on the reason for the deduction error. Therefore, if an anomaly occurs in the payment system, the cardholder can clearly understand the reason why they cannot use the relative card for payment through the payment error information. This allows the cardholder to wait for the payment system to be repaired, thereby improving the feasibility of the solution.

[0191] Optionally, in the above Figure 5 On the basis of one or more corresponding embodiments, in another optional embodiment provided by the embodiment of the present application, the payment card list includes a first payment account and a second payment account arranged in order;

[0192] According to the payment request, payment deduction processing is performed on the payment card list associated with the second user account to obtain a payment deduction result, which may specifically include:

[0193] Determining, based on the payment request, the first payment account from a list of payment cards associated with the second user account;

[0194] Perform payment deduction processing on the first payment account and obtain a processing result for the first payment account;

[0195] If the processing result of the first payment account indicates that the processing has failed, then the payment deduction process is performed on the second payment account to obtain the processing result for the second payment account;

[0196] If the processing result of the second payment account indicates that the processing failed, the payment deduction result is obtained according to the payment card list;

[0197] Wherein, when the payment deduction result is a deduction failure, it is determined that the payment processing result meets the payment error reporting condition.

[0198] In one or more embodiments, a method of implementing a rotation card based on multiple payment accounts is introduced. It can be seen from the aforementioned embodiments that the payment rotation card list may include multiple payment accounts arranged in sequence. For the sake of convenience, this application takes the first payment account (for example, "A Bank Savings Card (last number 0451)") and the second payment account (for example, "B Bank Credit Card (last number 7382)") as an example. It should be noted that, in actual applications, multiple payment accounts may also include other payment accounts, which are not limited here.

[0199] Specifically, the server first acquires a first payment account (e.g., "A bank savings card (tail number 0451)") from the payment round card list, where the first payment account can be a payment account ranked first in the payment round card list. Then, the server performs a payment deduction process on the first payment account, and if the deduction fails, the server continues to acquire a next payment account (e.g., "B bank credit card (tail number 7382)") in the payment round card list. The second payment account is a payment account adjacent to the first payment account in the payment round card list. Based on this, the server performs a payment deduction process on the second payment account, and if the deduction fails, the server continues to poll the payment accounts in the payment round card list until all the payment accounts fail to be deducted, and determines that the payment deduction result is a deduction failure.

[0200] Again, in the embodiments of the present application, a method for implementing a round card based on multiple payment accounts is provided. Through the above method, if there are multiple payment accounts in the payment round card list associated with the second user account, the payment accounts can be polled, thereby maximizing the success rate of the deduction.

[0201] Optionally, in the above Figure 5 Based on one or more embodiments, in another optional embodiment of the present application, in the case that the payment processing result satisfies the payment error condition, payment error information for the target order is generated, which can specifically include:

[0202] In the case that the payment processing result satisfies the payment error condition, the deduction error reason of the first payment account and the deduction error reason of the second payment account are acquired.

[0203] If the deduction error reason of the first payment account indicates that the first payment account has an abnormal situation, and the deduction error reason of the second payment account indicates that the second payment account has an abnormal situation, the payment error information for the target order is generated according to the abnormal situations of the first payment account and the second payment account, respectively, where the payment error information is used to prompt that the second user account has an abnormal situation.

[0204] In one or more embodiments, another payment error processing method is introduced. As known from the foregoing embodiments, if the payment deduction result is a deduction failure, the server determines that the payment processing result satisfies the payment error condition. Based on this, the server needs to acquire the deduction error reasons of the payment accounts, and further make corresponding prompts according to these reasons. In the following, taking the case that both the first payment account and the second payment account have insufficient balance as an example.

[0205] Specifically, for ease of understanding, taking the use of a relative card to pay an electronic red packet as an example, please refer to Figure 10 ,Figure 10 As another interface schematic based on the error of the card giver in the embodiments of the present application, as shown in Figure 10 As shown in (A) of FIG. 5, the user uses the relative card when making payment. When clicking the payment control indicated by G1, that is, triggering the payment request for the target order. The server responds to the payment request, first performs payment deduction processing on the first payment account, if the deduction fails, then continues to perform payment deduction processing on the second payment account. Based on this, assuming that the payment deduction processing is deduction failure, and the reason for the deduction failure is that the first payment account and the second payment account both have insufficient balance, an interface as shown in Figure 10 (B) of FIG. 5 is displayed. Wherein, G2 is used to indicate the payment error information, for example, the payment error information is "the A bank savings card and the B bank credit card of the card giver are both insufficient, and the transaction cannot be completed temporarily", it can be seen that the payment error information is used to prompt the abnormal situation of the card giver.

[0206] Further, in the embodiments of the present application, another processing mode of payment error is provided. Through the above mode, the server generates the corresponding payment error information according to the abnormal situation of each payment account. Based on this, the card receiver can understand the specific reason why the card giver cannot provide payment service, so as to make the card receiver obtain more detailed information, and further improve the use experience of the relative card of the card receiver.

[0207] Optionally, on the basis of one or more embodiments described above, Figure 5 In another optional embodiment provided by the embodiments of the present application based on one or more embodiments, the payment error information for the target order is generated according to the abnormal situation of the first payment account and the second payment account, which can specifically include:

[0208] According to the deduction error reason of the first payment account, a first error code is obtained;

[0209] According to the deduction error reason of the second payment account, a second error code is obtained;

[0210] The first error code and the second error code are converted into a card giver error code;

[0211] The payment error information for the target order is generated according to the card giver error code.

[0212] In one or more embodiments, a way of generating payment error information based on error code escape is introduced. As known from the foregoing embodiments, the deduction error reason of the first payment account indicates that the first payment account has an abnormal situation, and the deduction error reason of the second payment account indicates that the second payment account has an abnormal situation. At this time, the payment error information is used to prompt the abnormal situation of the card giver.

[0213] Specifically, the following will take the first payment account as "A Bank Savings Card (ending number 0451)" and the second payment account as "B Bank Credit Card (ending number 7382)" as examples. For ease of understanding, please refer to Table 2, which is an illustration of the error codes corresponding to the payment accounts.

[0214] Table 2

[0215] Payment account Error reason for deduction Error code A bank savings card (tail number 0451) Insufficient balance 0001 B bank credit card (tail number 7382) Account frozen 0002

[0216] As shown in Table 2, the first error code is "0001" and the second error code is "0002." Because both deduction errors are caused by an abnormality in the gifting party's payment account, the first and second error codes can be converted into a unified gifting party error code (for example, 0101). Based on this, the gifting party error code is translated to obtain payment error information for the target order.

[0217] For easier understanding, see Figure 11 , Figure 11 This is a schematic diagram of an interface for reporting errors based on the escape function in an embodiment of the present application, such as Figure 11 As shown in Figure (A), the user uses a relative card when making a payment. When the payment control indicated by H1 is clicked, a payment request for the target order is triggered. In response to the payment request, the server first deducts the payment from the first payment account. If the deduction fails, the server continues to deduct the payment from the second payment account. Assuming that the payment deduction fails and the deduction error is caused by an abnormality in the payment account of the card donor, the following is displayed: Figure 11 The interface shown in Figure (B) is shown in Figure 2. H2 indicates a payment error message. For example, the payment error message reads, "There is an abnormality in the card giver's account. The transaction cannot be completed temporarily. If you have any questions, please contact the card giver for consultation or try another payment method." This payment error message is used to inform the card giver of an abnormality and is obtained by escaping the card giver's error code.

[0218] Furthermore, in an embodiment of the present application, a method for generating payment error information based on error code translation is provided. Through this method, if an error occurs on the part of the card giver, the error content can also be translated. That is, the error content is converted into a unified error code for the card giver, and the corresponding payment error information based on the error code is displayed to the card recipient. This, on the one hand, protects the privacy of the card giver. On the other hand, because error codes are highly technical and difficult to understand, converting the error code into payment error information can help the card recipient understand the error, thereby improving the user experience of using the Family Card.

[0219] Optionally, in the above Figure 5Based on one or more embodiments corresponding, in another optional embodiment provided by the embodiments of the present application, in the case that the payment processing result satisfies the payment error condition, the payment error information for the target order is generated, which can specifically include:

[0220] In the case that the payment processing result satisfies the payment error condition, the first payment account's deduction error reason and the second payment account's deduction error reason are obtained.

[0221] If the first payment account's deduction error reason indicates that the payment system has an abnormal condition, and the second payment account's deduction error reason indicates that the payment system has an abnormal condition, the payment error information for the target order is generated according to the abnormal condition of the payment system, wherein the payment error information is used to prompt the abnormal condition of the payment system.

[0222] In one or more embodiments, another payment error processing method is introduced. As known from the foregoing embodiments, if the payment deduction result is deduction failure, the server determines that the payment processing result satisfies the payment error condition. Based on this, the server needs to obtain the deduction error reasons of each payment account, and further make corresponding prompts according to these reasons. In the following, the case that the first payment account and the second payment account both have request timeout in the payment deduction process will be introduced.

[0223] Specifically, for ease of understanding, taking the payment of electronic red packets using a relative card as an example, please refer to Figure 12 , Figure 12 Another interface diagram based on the payment system error in the embodiments of the present application is shown in FIG. (A) of Figure 12 , when the user uses a relative card to make payment. When the payment control indicated by I1 is clicked, that is, the payment request for the target order is triggered. The server responds to the payment request, first performs payment deduction processing on the first payment account, if the deduction fails, continues to perform payment deduction processing on the second payment account. Based on this, assuming that the payment deduction processing is deduction failure, and the reason for the deduction failure is that the first payment account and the second payment account both have request timeout during deduction, the interface shown in FIG. (B) of Figure 12 is displayed. Wherein, I2 is used to indicate the payment error information, for example, the payment error information is "the A bank savings card and the B bank credit card of the gift card party both have request timeout during the deduction process, please try again later", it can be seen that the payment error information is used to prompt the abnormal condition of the payment system.

[0224] Further, in the embodiments of the present application, another payment error processing mode is provided. Through the above mode, the server generates corresponding payment error information according to the abnormal situation of the payment system. Based on this, the card holder can understand the specific reason why the payment system cannot provide payment services, so that the card holder obtains more detailed information, thereby improving the use experience of the card holder's relative card.

[0225] Optionally, in the above Figure 5 Based on one or more embodiments, in another optional embodiment provided by the embodiments of the present application, the payment error information for the target order is generated according to the abnormal situation of the payment system, which can specifically include:

[0226] According to the deduction error reason of the first payment account, a third error code is obtained;

[0227] According to the deduction error reason of the second payment account, a fourth error code is obtained;

[0228] The third error code and the fourth error code are converted into a system error code;

[0229] The system error code is used to generate payment error information for the target order.

[0230] In one or more embodiments, another way of generating payment error information based on error code escape is introduced. As known from the foregoing embodiments, the deduction error reason of the first payment account indicates that the payment system has an abnormal situation in the deduction process, and the deduction error reason of the second payment account indicates that the payment system has an abnormal situation in the deduction process. At this time, the payment error information is used to prompt the abnormal situation of the payment system.

[0231] Specifically, the first payment account will be taken as "A bank savings card (tail number 0451)" and the second payment account will be taken as "B bank credit card (tail number 7382)" as an example for introduction. For ease of understanding, please refer to Table 3, which is an illustration of error codes corresponding to payment accounts.

[0232] Table 3

[0233] Payment account Error reason for deduction Error code A bank savings card (tail number 0451) Request timeout 1000 B bank credit card (tail number 7382) Network exception 2000

[0234] As can be seen from Table 3, the third error code is "1000" and the fourth error code is "2000". Since the deduction error reason is that the payment system has an abnormal situation in the payment process of the card holder, the third error code and the fourth error code can be converted into a unified system error code (for example, 0202). Based on this, the system error code is escaped to obtain payment error information for the target order.

[0235] For ease of understanding, please refer to Figure 13 ,Figure 13 FIG. 1 is a schematic diagram of an interface for reporting an error based on the escape function according to an embodiment of the present application. As shown in FIG. 1, the interface includes a payment control J1 and a payment error information J2. The payment control J1 is used to trigger a payment request for a target order. The payment error information J2 is used to display the payment error information of the payment system. Figure 13 As shown in FIG. 1A, a user uses a relative card to make a payment. When the user clicks the payment control J1, the payment request for the target order is triggered. The server responds to the payment request by performing a payment deduction process on the first payment account. If the payment deduction process fails, the server continues to perform a payment deduction process on the second payment account. Assuming that the payment deduction process fails and the error causes of the payment deduction process are both request timeouts, the interface shown in FIG. 1B is displayed. In FIG. 1B, the payment error information J2 is used to indicate the payment error information, for example, “The payment process is abnormal, and the transaction cannot be completed temporarily. Please try again later.” It can be seen that the payment error information is used to prompt the abnormal situation of the payment system, and the payment error information is obtained by escaping the system error code. Figure 13

[0236] Further, in an embodiment of the present application, another way of generating payment error information based on error code escape is provided. Through the above way, if the payment system has an error, the content of the error can also be escaped. That is, the error content is converted into a unified system error code, and the corresponding payment error information is displayed to the cardholder based on the system error code. Thus, after the error code is converted into the payment error information, the cardholder can understand the error, thereby improving the experience of using the relative card.

[0237] Optionally, based on one or more embodiments of the above Figure 5 In another optional embodiment of the present application, in the case where the payment processing result satisfies the payment error condition, the payment error information for the target order is generated, which can specifically include the following steps.

[0238] In the case where the payment processing result satisfies the payment error condition, the error causes of the first payment account and the error causes of the second payment account are obtained.

[0239] If the error causes of the first payment account indicate that the first payment account has an abnormal situation, and the error causes of the second payment account indicate that the payment system has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation of the first payment account and the abnormal situation of the payment system; or

[0240] If the error causes of the first payment account indicate that the payment system has an abnormal situation, and the error causes of the second payment account indicate that the second payment account has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation of the second payment account and the abnormal situation of the payment system. ​

[0241] In one or more embodiments, another payment error processing mode is introduced. As known from the foregoing embodiments, if the payment deduction result is a deduction failure, the server determines that the payment processing result meets the payment error condition. Based on this, the server needs to obtain the reasons for the deduction error of each payment account, and further make corresponding prompts according to these reasons. The following will take the case of insufficient balance of the first payment account and request timeout of the second payment account in the payment deduction process as an example for introduction.

[0242] Specifically, for ease of understanding, taking the use of a relative card to pay an electronic red packet as an example, please refer to Figure 14 , Figure 14 is an interface schematic diagram based on the gift card party and the payment system error in the embodiments of the present application, as shown in FIG. (A) of Figure 14 , the user uses a relative card when making a payment. When clicking the payment control indicated by K1, that is, triggering a payment request for the target order. The server responds to the payment request, first performs payment deduction processing on the first payment account, if the deduction fails, continues to perform payment deduction processing on the second payment account. Based on this, assuming that the payment deduction processing is a deduction failure, and the reason for the deduction failure is that the first payment account is insufficient, and the second payment account has a request timeout during deduction, an interface as shown in FIG. (B) of Figure 14 is displayed. Among them, K2 is used to indicate the payment error information, for example, the payment error information is "the A bank savings card of the gift card party is insufficient, the B bank credit card has a request timeout during the deduction process, and the transaction cannot be completed temporarily, please try again later", it can be seen that the payment error information is used to prompt that both the payment account and the payment system have abnormal situations.

[0243] Further, in the embodiments of the present application, another payment error processing mode is provided. Through the above-mentioned mode, the server generates corresponding payment error information according to the abnormal situation of the payment account and the abnormal situation of the payment system. Based on this, the card holder can understand the specific reasons why the gift card party and the payment system cannot provide payment services, so that the card holder obtains more detailed information, and further improves the use experience of the relative card of the card holder.

[0244] Optionally, on the basis of one or more embodiments corresponding to the above Figure 5 , in another optional embodiment provided by the embodiments of the present application, the payment error information for the target order is generated according to the abnormal situation of the second user account and the abnormal situation of the payment system, which can specifically include:

[0245] obtain a fifth error code according to the deduction error reason of the first payment account;

[0246] obtain a sixth error code according to the deduction error reason of the second payment account;

[0247] convert the fifth error code and the sixth error code into a comprehensive error code;

[0248] generate payment error information for the target order according to the comprehensive error code.

[0249] In one or more embodiments, another way of generating payment error information based on error code escape is introduced. As known from the foregoing embodiments, the first payment account deduction error reason indicates that the first payment account is abnormal, and the second payment account deduction error reason indicates that the payment system is abnormal during the deduction process. Alternatively, the first payment account deduction error reason indicates that the payment system is abnormal during the deduction process, and the second payment account deduction error reason indicates that the second payment account is abnormal. At this time, the payment error information is used to prompt that both the gift card party and the payment system are abnormal.

[0250] Specifically, the following will take the first payment account as "A bank savings card (tail number 0451)" and the second payment account as "B bank credit card (tail number 7382)" as examples for introduction. For ease of understanding, please refer to Table 4, which is an illustration of error codes corresponding to payment accounts.

[0251] Table 4

[0252] Payment account Error reason for deduction Error code A bank savings card (tail number 0451) Insufficient balance 0001 B bank credit card (tail number 7382) Network exception 2000

[0253] As known from Table 4, the fifth error code is "0001", and the sixth error code is "2000". Since the deduction error reason is that both the gift card party's payment account and the payment system are abnormal, the fifth error code and the sixth error code can be converted into a unified comprehensive error code (for example, 0303). Based on this, the comprehensive error code is escaped to obtain payment error information for the target order.

[0254] For ease of understanding, please refer to Figure 15 , Figure 15 Another interface diagram for error reporting based on the escape function in the embodiments of the present application is shown in FIG. (A) of Figure 15 When the payment control indicated by L1 is clicked, that is, a payment request for the target order is triggered. The server responds to the payment request by first performing payment deduction processing on the first payment account. If the deduction fails, it continues to perform payment deduction processing on the second payment account. Assuming that the payment deduction processing fails, and the deduction error reason is that both the gift card party's payment account and the payment system are abnormal, a display as shown in Figure 15The interface shown in Figure (B) is shown in Figure 2. L2 is used to indicate payment error information. For example, the payment error message is "There is an abnormality in the card giver's account, and the deduction is abnormal. The transaction cannot be completed temporarily. Please try again later." This payment error message is used to inform both the card giver and the payment system that an abnormality has occurred. The payment error message is obtained by escaping the comprehensive error code.

[0255] Furthermore, in an embodiment of the present application, another method for generating payment error information based on error code escape is provided. Through the above method, if both the card donor and the payment system report an error, the error content can also be escaped. That is, the error content is converted into a unified system error code, and the corresponding payment error information is displayed to the card recipient based on the system error code. In this way, on the one hand, the privacy of the card donor can be protected. On the other hand, since error codes are highly technical and difficult to understand, converting the error code into payment error information can help the card recipient understand the error, thereby improving the user experience of using the relative card.

[0256] Optionally, in the above Figure 5 On the basis of one or more corresponding embodiments, in another optional embodiment provided by the embodiments of the present application, when the payment processing result meets the payment error reporting condition, after generating the payment error reporting information for the target order, the following may also be included:

[0257] If the payment error reporting party belongs to the second user account, the payment error information for the target order is sent to the second terminal, so that the second terminal displays the payment error information for the target order, wherein the second terminal has logged in to the second user account.

[0258] In one or more embodiments, a method for providing payment error information to the card donor is described. As can be seen from the aforementioned embodiments, after the card recipient uses the relative card to make a payment, the card donor receives corresponding feedback, regardless of whether the payment is successful. The card donor logs into the second terminal using a second user account.

[0259] Specifically, for easier understanding, see Figure 16 , Figure 16 This is a schematic diagram of an interface for providing payment error information to the card donor in an embodiment of the present application, such as Figure 16 As shown in (A), if the recipient uses a relative card to pay and the payment is successful, a payment success message indicated by M1 will be displayed on the second terminal used by the card donor. If the recipient uses a relative card to pay but the payment fails due to the card donor's fault, a payment error message indicated by M2 will be displayed on the second terminal used by the card donor.

[0260] Secondly, in the embodiments of the present application, a method for feeding back payment error information to the card giver is provided. Through the above method, in the case that the card giver is a payment error party, the server will also push the payment error information to the card giver. Thus, the card giver can be reminded to perform relevant operations in time, so as to maintain the continuity of the business.

[0261] In combination with the above embodiments, the following will be described by taking Figure 17 the processing flow of the payment error as an example. For the convenience of understanding, please refer to Figure 17 , Figure 17 Fig. 1 is a schematic diagram of an interaction flow of the payment error processing in the embodiments of the present application, and specifically:

[0262] In step S1, the card taker logs in the terminal by using the first user account, selects the relative card through the application client on the terminal, and then inputs the payment password to perform the payment.

[0263] In step S2, the terminal calls the application client to send a payment request to the social payment server.

[0264] In step S3, the social payment server requests the bank server to place an order for the payment.

[0265] In step S4, the social payment server requests the bank server to query the payment method list owned by the card giver, and based on the payment method list, the payment method owned by the card giver can be known.

[0266] In step S5, the social payment server prepares the relative card payment round card information, and filters the available payment round card list of the card giver, wherein the payment round card information refers to the payment card information owned by the card giver, including but not limited to the information such as the change, the bank card, the change pass, etc.

[0267] In step S6, the social payment server uses the payment method of the card giver to request the bank server to perform the payment deduction. After the round card, the payment processing result is obtained.

[0268] In step S7, if the payment of the round card is successful, the payment flow is ended, and the social payment server returns the payment result to the application client. In the case of the successful payment, the payment error information does not need to be returned.

[0269] In step S8, if the payment is failed, the bank server returns the payment error information to the social payment server

[0270] In step S9, the relative card taking party itself reports an error. The explicit payment error includes two cases. The first case is explicit blocking payment, for example, password error, account freezing and the like. In this case, an error is directly returned, and there is no need to continue to round the card. The second case is that the payment can continue to round, for example, the first payment method is change payment. If the balance is insufficient, the card is continued to round, and the second payment method is to use the A bank savings card to pay. In this way, the payment is continued to round until the payment is successful, or all payment methods are polled and an error is reported.

[0271] In step S10, the social payment server feeds back the payment error information to the application server, and no longer rounds the card, and the process ends.

[0272] In step S11, the payment account of the card gifting party is reported. For example, the payment account state of the card gifting party is abnormal. At this time, the bank server side may have frozen the payment account of the card gifting party, but the error code returned is the same as that of the payment account of the card taking party being frozen. Therefore, the card taking party is disturbed, and needs to be converted into an error code before being returned. That is, assuming that error code A indicates that the payment account is frozen, and then it is converted into error code B. Error code B is converted into “the payment account of the relative card gifting party is abnormal, and the transaction cannot be completed temporarily. If there is any doubt, please contact the card gifting party for consultation, or replace other payment methods to perform the transaction”. Based on this, the payment failure caused by the card gifting party is converted into a unified error code, and is displayed to the card taking party. In this way, the privacy and the like of the card gifting party can also be protected.

[0273] In step S12, if the payment is not explicitly failed, it indicates that the payment is not explicit. Therefore, the card cannot be continued to round, the repeated deduction is prevented, and the single closing operation is performed.

[0274] In step S13, the social payment server sends a notification of payment non-explicit failure to a social payment message queue (MQ) server. In this way, the social payment MQ server sends a payment single closing request to the bank server.

[0275] In step S14, the social payment server returns a notification of payment non-explicit failure to the application server. Based on this, the application client attempts to perform payment single query.

[0276] In step S15, the application client sends a payment single query request to the social payment server.

[0277] In step S16, the social payment server sends the payment single query request to the bank server.

[0278] In step S17, the bank server performs a check based on the payment check request, and if the check result is a payment success, the social payment server returns a notification of payment success to the application client.

[0279] In step S18, the bank server performs a check based on the payment check request, and if the check result is a payment failure, the social payment server returns a notification of payment failure to the application client. At this time, since the error uses the error code X corresponding to the current payment method, if conversion is needed, the error code Y is converted, and finally, according to the error code corresponding to each payment method, a unified error code is escaped.

[0280] The payment error processing device in the present application will be described in detail below. Please refer to Figure 18 , Figure 18 An embodiment of the payment error processing device in the present application is shown in the figure. The payment error processing device 30 comprises:

[0281] The receiving module 310 is configured to receive a payment request sent by a first terminal for a target order, wherein the first terminal has logged in a first user account, the payment request carries the first user account, a second user account and a payment amount, the first user account is an account initiating the payment request, and the second user account is an account to be deducted by the payment amount based on the payment request;

[0282] The processing module 320 is configured to perform a payment processing operation according to the payment request to obtain a payment processing result.

[0283] The generating module 330 is configured to generate payment error information for the target order in a case where the payment processing result meets a payment error condition, wherein the payment error information is used to prompt a payment error party in an abnormal situation, and the payment error party belongs to at least one of the first user account, the second user account and a payment system.

[0284] The sending module 340 is configured to send the payment error information for the target order to the first terminal, so that the first terminal displays the payment error information for the target order.

[0285] In the present application, a payment error processing device is provided. By using the above device, on the one hand, the user can solve the abnormal problem in a targeted manner, and on the other hand, the user can clearly know the reason for the abnormal situation, thereby reducing the user's anxiety and enhancing the user experience.

[0286] Optionally, on the basis of the above Figure 18 corresponding embodiment, in another embodiment of the payment error processing device 30 provided by the present application, the payment processing result comprises a payment verification result.

[0287] The processing module 320 is specifically configured to perform payment verification processing on the information related to the first user account according to the payment request, and obtain a payment verification result.

[0288] In a case where the payment verification result is a verification failure, it is determined that the payment processing result satisfies a payment error condition.

[0289] In the embodiments of the present application, a payment error processing device is provided. By using the device, the server needs to verify the processing flow of the card holder, and if the card holder has an error, the card rotation is not needed. Thus, the corresponding payment error information can be directly sent to the card holder, thereby saving the resources required for card rotation.

[0290] Optionally, in the above Figure 18 Based on the corresponding embodiments, in another embodiment of the payment error processing device 30 provided by the embodiments of the present application,

[0291] The generating module 330 is specifically configured to acquire a verification error reason in a case where the payment processing result satisfies the payment error condition.

[0292] If the verification error reason indicates that the information related to the first user account has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation of the first user account, wherein the payment error information is used to prompt that the first user account has an abnormal situation.

[0293] In the embodiments of the present application, a payment error processing device is provided. By using the device, the server will generate corresponding payment error information according to the verification error reason, and based on this, if the information related to the first user account has an abnormal situation, the card holder can clearly understand from the payment error information that the reason why the relative card cannot be used for payment is due to itself. Thus, the card holder can actively solve the problem, thereby effectively improving the user experience of using the relative card for payment.

[0294] Optionally, in the above Figure 18 Based on the corresponding embodiments, in another embodiment of the payment error processing device 30 provided by the embodiments of the present application,

[0295] The generating module 330 is specifically configured to acquire a verification error reason in a case where the payment processing result satisfies the payment error condition.

[0296] If the verification error reason indicates that the payment system has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation of the payment system, wherein the payment error information is used to prompt that the payment system has an abnormal situation.

[0297] In the embodiment of the present application, a payment error processing device is provided. By using the above device, the server generates corresponding payment error information according to the reason for verifying the error, and based on this, if the payment system has an abnormal condition, the card holder can clearly understand the reason why the relative card cannot be used for payment through the payment error information. Therefore, the card holder can wait for the payment system to be repaired, thereby improving the feasibility of the scheme.

[0298] Optionally, in the above Figure 18 Based on the corresponding embodiment, in another embodiment of the payment error processing device 30 provided by the present application, the payment processing result includes a payment deduction result.

[0299] The processing module 320 is specifically configured to perform payment deduction processing on the payment round card list associated with the second user account according to the payment request, to obtain a payment deduction result, wherein the payment round card list includes at least one payment account arranged in order.

[0300] In the case of a payment deduction failure, it is determined that the payment processing result meets the payment error condition.

[0301] In the embodiment of the present application, a payment error processing device is provided. By using the above device, the server needs to verify the processing flow of the card giver. If the card giver has an error, the corresponding payment error information is directly sent to the card holder, so that the card holder can timely understand the payment error party, thereby helping to alleviate user anxiety and enhancing user experience.

[0302] Optionally, in the above Figure 18 Based on the corresponding embodiment, in another embodiment of the payment error processing device 30 provided by the present application, the payment round card list only includes a target payment account.

[0303] The processing module 320 is specifically configured to determine a target payment account from the payment round card list associated with the second user account according to the payment request.

[0304] The target payment account is subjected to payment deduction processing to obtain a payment deduction result for the target payment account.

[0305] In the embodiment of the present application, a payment error processing device is provided. By using the above device, if there is only one payment account in the payment round card list associated with the second user account, the payment deduction result can be obtained after the payment deduction processing of the payment account. Therefore, the feasibility and operability of the scheme are improved.

[0306] Optionally, in the above Figure 18 Based on the corresponding embodiment, in another embodiment of the payment error processing device 30 provided by the present application,

[0307] The generating module 330 is specifically configured to, in the case that the payment processing result meets the payment error condition, acquire a deduction error reason of the target payment account.

[0308] If the deduction error reason indicates that the target payment account is in an abnormal situation, payment error information for the target order is generated according to the abnormal situation corresponding to the target payment account, wherein the payment error information is used to prompt that the second user account is in an abnormal situation.

[0309] In the embodiment of the application, a payment error processing device is provided. By using the device, the server generates corresponding payment error information according to the reason for the deduction error. Based on this, if the related information of the second user account is in an abnormal situation, the card receiver can clearly understand from the payment error information that the reason why the relative card cannot be used for payment is that the card giver. Therefore, the card receiver can solve the problem with the card giver, thereby improving the use experience of the relative card.

[0310] Optionally, in the above Figure 18 based on the corresponding embodiment, in another embodiment of the payment error processing device 30 provided by the embodiment of the application,

[0311] The generating module 330 is specifically configured to, in the case that the payment processing result meets the payment error condition, acquire a deduction error reason of the target payment account.

[0312] If the deduction error reason indicates that the payment system is in an abnormal situation, payment error information for the target order is generated according to the abnormal situation of the payment system, wherein the payment error information is used to prompt that the payment system is in an abnormal situation.

[0313] In the embodiment of the application, a payment error processing device is provided. By using the device, the server generates corresponding payment error information according to the reason for the deduction error. Based on this, if the related information of the second user account is in an abnormal situation, the card receiver can clearly understand from the payment error information that the reason why the relative card cannot be used for payment is that the card giver. Therefore, the card receiver can solve the problem with the card giver, thereby improving the use experience of the relative card.

[0314] Optionally, in the above Figure 18 based on the corresponding embodiment, in another embodiment of the payment error processing device 30 provided by the embodiment of the application, the payment round card list includes a first payment account and a second payment account arranged in order;

[0315] The processing module 320 is specifically configured to determine the first payment account from the payment round card list associated with the second user account according to the payment request.

[0316] The first payment account is subjected to payment deduction processing, and a processing result for the first payment account is acquired.

[0317] If the processing result of the first payment account indicates that the processing has failed, then the payment deduction process is performed on the second payment account to obtain the processing result for the second payment account;

[0318] If the processing result of the second payment account indicates that the processing failed, the payment deduction result is obtained according to the payment card list;

[0319] Wherein, when the payment deduction result is a deduction failure, it is determined that the payment processing result meets the payment error reporting condition.

[0320] In an embodiment of the present application, a payment error processing device is provided. Using the above device, if there are multiple payment accounts in the payment card list associated with the second user account, these payment accounts can be polled, thereby maximizing the deduction success rate.

[0321] Optionally, in the above Figure 18 On the basis of the corresponding embodiment, in another embodiment of the payment error processing device 30 provided in the embodiment of the present application,

[0322] A generation module 330 is specifically configured to obtain a deduction error reason for the first payment account and a deduction error reason for the second payment account when the payment processing result satisfies the payment error reporting condition;

[0323] If the deduction error reason of the first payment account indicates that an abnormality has occurred in the first payment account, and the deduction error reason of the second payment account indicates that an abnormality has occurred in the second payment account, then payment error information is generated for the target order based on the abnormalities in the first payment account and the second payment account respectively, wherein the payment error information is used to prompt that an abnormality has occurred in the second user account.

[0324] In one embodiment of the present application, a payment error processing device is provided. Using this device, a server generates corresponding payment error information based on the anomalies encountered in each payment account. This allows the recipient to understand the specific reason why the gifting party is unable to provide payment services, providing the recipient with more detailed information and improving their experience using the Family Card.

[0325] Optionally, in the above Figure 18 On the basis of the corresponding embodiment, in another embodiment of the payment error processing device 30 provided in the embodiment of the present application,

[0326] A generating module 330 is specifically configured to obtain a first error code according to a deduction error reason of the first payment account;

[0327] Obtain a second error code based on the deduction error reason of the second payment account;

[0328] convert the first error code and the second error code into a gift card error code;

[0329] generate payment error information for the target order according to the gift card error code.

[0330] In the embodiments of the present application, a payment error processing device is provided. If an error occurs in the gift card, the content of the error can be processed by using the device. That is, the error content is converted into a unified gift card error code, and the corresponding payment error information is displayed to the card holder based on the gift card error code. In this way, on the one hand, the privacy of the gift card can be protected. On the other hand, since the error code is technically strong and not easy to understand, the card holder can understand the error after the error code is converted into payment error information, thereby improving the experience of using the relative card of the user.

[0331] Optionally, in the above Figure 18 based on the corresponding embodiments, another embodiment of the payment error processing device 30 provided by the embodiments of the present application is provided,

[0332] The generation module 330 is specifically configured to acquire the deduction error reason of the first payment account and the deduction error reason of the second payment account in the case that the payment processing result meets the payment error condition.

[0333] If the deduction error reason of the first payment account indicates that an abnormal condition occurs in the payment system, and the deduction error reason of the second payment account also indicates that an abnormal condition occurs in the payment system, the payment error information for the target order is generated according to the abnormal condition of the payment system, wherein the payment error information is used to prompt the abnormal condition of the payment system.

[0334] In the embodiments of the present application, a payment error processing device is provided. By using the device, the server generates the corresponding payment error information according to the abnormal condition of the payment system. Based on this, the card holder can understand the specific reason why the payment system cannot provide payment services, so that the card holder obtains more detailed information, thereby improving the experience of using the relative card of the card holder.

[0335] Optionally, in the above Figure 18 based on the corresponding embodiments, another embodiment of the payment error processing device 30 provided by the embodiments of the present application is provided,

[0336] The generation module 330 is specifically configured to acquire a third error code according to the deduction error reason of the first payment account.

[0337] A fourth error code is acquired according to the deduction error reason of the second payment account.

[0338] The third error code and the fourth error code are converted into a system error code.

[0339] generating payment error information for the target order according to the system error code.

[0340] In the embodiments of the present application, a payment error processing device is provided. If an error occurs in the payment system, the content of the error can be processed by using the device. That is, the error content is converted into a unified system error code, and the corresponding payment error information is displayed to the cardholder based on the system error code. Thus, the error code is converted into payment error information, which can help the cardholder understand the error and improve the experience of using the relative card.

[0341] Optionally, in the above Figure 18 On the basis of the corresponding embodiments, another embodiment of the payment error processing device 30 provided by the embodiments of the present application is provided.

[0342] The generating module 330 is specifically configured to acquire the deduction error reason of the first payment account and the deduction error reason of the second payment account if the payment processing result meets the payment error condition.

[0343] If the deduction error reason of the first payment account indicates that the first payment account has an abnormal condition, and the deduction error reason of the second payment account indicates that the payment system has an abnormal condition, the payment error information for the target order is generated according to the abnormal condition of the first payment account and the abnormal condition of the payment system; or

[0344] If the deduction error reason of the first payment account indicates that the payment system has an abnormal condition, and the deduction error reason of the second payment account indicates that the second payment account has an abnormal condition, the payment error information for the target order is generated according to the abnormal condition of the second payment account and the abnormal condition of the payment system.

[0345] In the embodiments of the present application, a payment error processing device is provided. By using the device, the server generates the corresponding payment error information according to the abnormal condition of the payment account and the abnormal condition of the payment system. Based on this, the cardholder can understand the specific reasons why the cardholder and the payment system cannot provide payment services, so that the cardholder obtains more detailed information and the experience of using the relative card is improved.

[0346] Optionally, in the above Figure 18 On the basis of the corresponding embodiments, another embodiment of the payment error processing device 30 provided by the embodiments of the present application is provided.

[0347] The generating module 330 is specifically configured to acquire the fifth error code according to the deduction error reason of the first payment account.

[0348] According to the deduction error report reason of the second payment account, a sixth error code is obtained;

[0349] The fifth error code and the sixth error code are converted into a comprehensive error code;

[0350] According to the comprehensive error code, payment error information for the target order is generated.

[0351] In the embodiments of the present application, a payment error processing device is provided. If the error occurs in the card giver and the payment system, the content of the error can be processed by using the device. That is, the error content is converted into a unified system error code, and the corresponding payment error information is displayed to the card receiver based on the system error code. In this way, on the one hand, the privacy of the card giver can be protected. On the other hand, since the error code is technically strong and not easy to understand, the card receiver can understand the error after the error code is converted into the payment error information, thereby improving the experience of using the relative card.

[0352] Optionally, in the above Figure 19 Based on the embodiments corresponding to the above, in another embodiment of the payment error processing device 30 provided by the embodiments of the present application,

[0353] The sending module 340 is further configured to, if the payment processing result meets the payment error condition, after generating the payment error information for the target order, send the payment error information for the target order to the second terminal if the payment error party belongs to the second user account, so that the second terminal displays the payment error information for the target order, wherein the second terminal has logged in the second user account.

[0354] In the embodiments of the present application, a payment error processing device is provided. If the card giver belongs to the payment error party, the server will also push the payment error information to the card giver by using the device. In this way, the card giver can be reminded to perform the related operation in time, thereby maintaining the continuity of the business.

[0355] Figure 19Fig. 4 is a schematic diagram of a server structure according to an embodiment of the present application. The server 400 can have a great difference due to different configurations or performances, and can include one or more central processing units (CPUs) 422 (e.g., one or more processors) and a memory 432, one or more storage media 430 (e.g., one or more mass storage devices) storing applications 442 or data 444. The memory 432 and the storage media 430 can be temporary or persistent storage. The programs stored in the storage media 430 can include one or more modules (not shown in the figure), each of which can include a series of instructions operated in the server. Further, the central processing unit 422 can be configured to communicate with the storage media 430 to execute the series of instructions operated in the storage media 430 on the server 400.

[0356] The server 400 can further include one or more power supplies 426, one or more wired or wireless network interfaces 450, one or more input / output interfaces 458, and / or one or more operating systems 441, such as Windows Server TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM , etc.

[0357] The steps performed by the server in the above embodiments can be based on the server structure shown in Fig. 4. ​

[0358] The embodiments of the present application further provide a computer device, which includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, the steps of the method described in the above various embodiments are implemented.

[0359] The embodiments of the present application further provide a computer readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the method described in the above various embodiments are implemented.

[0360] The embodiments of the present application further provide a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of the method described in the above various embodiments are implemented.

[0361] ​It can be understood that in the specific embodiments of the present application, data related to biological information, account information, etc. are involved, and when the above embodiments are applied to specific products or technologies, user permission or consent needs to be obtained, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of countries and regions.

[0362] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0363] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined target, and can be implemented entirely or partially by using software, hardware (such as a processing circuit or a memory) or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of an overall module or unit that includes the functions of the module or unit.

[0364] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division, and actual implementation can have another division manner. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0365] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, i.e. they can be located in one place, or can be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0366] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0367] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or the entire or part of the technical solutions that essentially contribute to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a server or a terminal device, etc.) to execute all or part of the steps of the method described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various computer program storage media.

[0368] The above-described embodiments are merely used to illustrate the technical solutions of the present application, rather than limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements for some of the technical features; and these modifications or replacements do not cause the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for handling payment of a bug, characterized in that, The method comprises: receiving a payment request sent by a first terminal for a target order, wherein the first terminal has logged in a first user account, the payment request carries the first user account, a second user account and a payment amount, the first user account is an account initiating the payment request, and the second user account is an account to be deducted by the payment amount based on the payment request; performing a payment processing operation according to the payment request to obtain a payment processing result; generating payment error information for the target order in a case where the payment processing result meets a payment error condition, wherein the payment error information is used to prompt a payment error party in an abnormal situation, and the payment error party belongs to at least one of the first user account, the second user account and a payment system; sending the payment error information for the target order to the first terminal to enable the first terminal to display the payment error information for the target order.

2. The processing method according to claim 1, characterized in that The payment processing result comprises a payment verification result. The method comprises: performing payment verification processing on related information of the first user account according to the payment request to obtain the payment verification result; wherein, in a case where the payment verification result is a verification failure, it is determined that the payment processing result meets the payment error condition.

3. The treatment method according to claim 2, characterized in that, The method comprises: in a case where the payment processing result meets the payment error condition, obtaining a verification error reason; if the verification error reason indicates that the related information of the first user account is in an abnormal situation, generating the payment error information for the target order according to the abnormal situation of the first user account, wherein the payment error information is used to prompt the first user account in the abnormal situation.

4. The treatment method of claim 2, wherein The method comprises: in a case where the payment processing result meets the payment error condition, obtaining a verification error reason; if the verification error reason indicates that the payment system is in an abnormal situation, generating the payment error information for the target order according to the abnormal situation of the payment system, wherein the payment error information is used to prompt the payment system in the abnormal situation.

5. The processing method according to claim 1, characterized in that The payment processing result comprises a payment deduction result. The method comprises: performing payment deduction processing on a payment round card list associated with the second user account according to the payment request to obtain the payment deduction result, wherein the payment round card list comprises at least one payment account arranged in order; wherein, in a case where the payment deduction result is a deduction failure, it is determined that the payment processing result meets the payment error condition.

6. The processing method according to claim 5, characterized in that, The payment round card list only comprises a target payment account. The payment deduction processing is performed on the payment round card list associated with the second user account according to the payment request, and the payment deduction result is obtained. The target payment account is determined from the payment round card list associated with the second user account according to the payment request. The payment deduction processing is performed on the target payment account, and the payment deduction result of the target payment account is obtained.

7. The treatment method according to claim 6, characterized in that, The payment error information for the target order is generated when the payment processing result meets the payment error condition. The deduction error reason of the target payment account is obtained when the payment processing result meets the payment error condition. If the deduction error reason indicates that the target payment account has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation corresponding to the target payment account, wherein the payment error information is used to prompt that the second user account has an abnormal situation.

8. The treatment method of claim 6, wherein, The payment error information for the target order is generated when the payment processing result meets the payment error condition. The deduction error reason of the target payment account is obtained when the payment processing result meets the payment error condition. If the deduction error reason indicates that the payment system has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation of the payment system, wherein the payment error information is used to prompt that the payment system has an abnormal situation.

9. The processing method according to claim 5, wherein The payment round card list includes a first payment account and a second payment account arranged in sequence. The payment deduction processing is performed on the payment round card list associated with the second user account according to the payment request, and the payment deduction result is obtained. The first payment account is determined from the payment round card list associated with the second user account according to the payment request. The payment deduction processing is performed on the first payment account, and the processing result of the first payment account is obtained. If the processing result of the first payment account indicates that the processing fails, the payment deduction processing is performed on the second payment account, and the processing result of the second payment account is obtained. If the processing result of the second payment account indicates that the processing fails, the payment deduction result is obtained according to the payment round card list. If the payment deduction result is a deduction failure, it is determined that the payment processing result meets the payment error condition.

10. The treatment method according to claim 9, characterized in that, The payment error information for the target order is generated when the payment processing result meets the payment error condition. The deduction error reason of the first payment account and the deduction error reason of the second payment account are obtained when the payment processing result meets the payment error condition. If the first payment account error reason indicates that the first payment account has an abnormal situation, and the second payment account error reason indicates that the second payment account has an abnormal situation, the payment error information for the target order is generated according to the abnormal situations of the first payment account and the second payment account, respectively, wherein the payment error information is used to prompt that the second user account has an abnormal situation.

11. The treatment method according to claim 10, characterized in that, The payment error information for the target order is generated according to the abnormal situations of the first payment account and the second payment account, respectively, and includes: The first error code is obtained according to the first payment account error reason; The second error code is obtained according to the second payment account error reason; The first error code and the second error code are converted into a gift card party error code; The payment error information for the target order is generated according to the gift card party error code.

12. The treatment method of claim 9, wherein, The payment error information for the target order is generated when the payment processing result meets the payment error condition, and includes: The first payment account error reason and the second payment account error reason are obtained when the payment processing result meets the payment error condition; If the first payment account error reason indicates that the payment system has an abnormal situation, and the second payment account error reason indicates that the payment system has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation of the payment system, wherein the payment error information is used to prompt that the payment system has an abnormal situation.

13. The treatment method according to claim 12, characterized in that, The payment error information for the target order is generated according to the abnormal situation of the payment system, and includes: The third error code is obtained according to the first payment account error reason; The fourth error code is obtained according to the second payment account error reason; The third error code and the fourth error code are converted into a system error code; The payment error information for the target order is generated according to the system error code.

14. The processing method of claim 9, wherein, The payment error information for the target order is generated when the payment processing result meets the payment error condition, and includes: The first payment account error reason and the second payment account error reason are obtained when the payment processing result meets the payment error condition; If the first payment account error reason indicates that the first payment account has an abnormal situation, and the second payment account error reason indicates that the payment system has an abnormal situation, the payment error information for the target order is generated according to the abnormal situation of the first payment account and the abnormal situation of the payment system; or, If the first payment account indicates that the payment system is abnormal, and the second payment account indicates that the second payment account is abnormal, the payment error information for the target order is generated according to the abnormality of the second payment account and the abnormality of the payment system.

15. The processing method according to claim 14, characterized in that, The payment error information for the target order is generated according to the abnormality of the second user account and the abnormality of the payment system, including: According to the error reason of the first payment account, a fifth error code is obtained; According to the error reason of the second payment account, a sixth error code is obtained; The fifth error code and the sixth error code are converted into a comprehensive error code; The payment error information for the target order is generated according to the comprehensive error code.

16. The treatment method according to any one of claims 1 to 15, characterized in that, After the payment error information for the target order is generated when the payment processing result meets the payment error condition, the method further includes: If the payment error party belongs to the second user account, the payment error information for the target order is sent to a second terminal to make the second terminal display the payment error information for the target order, wherein the second terminal has logged in the second user account.

17. A payment error reporting processing apparatus characterized by comprising: Including: The receiving module is configured to receive a payment request sent by a first terminal for a target order, wherein the first terminal has logged in a first user account, the payment request carries the first user account, a second user account, and a payment amount, the first user account is an account initiating the payment request, and the second user account is an account to be deducted by the payment amount based on the payment request; The processing module is configured to perform a payment processing operation according to the payment request to obtain a payment processing result; The generating module is configured to generate payment error information for the target order when the payment processing result meets a payment error condition, wherein the payment error information is used to prompt a payment error party with abnormality, and the payment error party belongs to at least one of the first user account, the second user account, and a payment system; The sending module is configured to send the payment error information for the target order to the first terminal to make the first terminal display the payment error information for the target order. 18.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-17. The processor executes the computer program to implement the steps of the processing method of any one of claims 1 to 16.

19. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the processing method of any one of claims 1 to 16.

20. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the processing method of any one of claims 1 to 16.

Images