Transaction payment method and device, computer equipment and storage medium
By generating payment orders on behalf of others and determining the payment priority of candidate payment users, and automatically selecting the target payment user, the payment function during online payment is realized, the transaction failure caused by insufficient balance of payment account is solved, and payment efficiency is improved .
Patent Information
- Application Number
- CN202411043657.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-12-20
Smart Images

Figure CN119168634A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of artificial intelligence technology, and in particular to a transaction payment method, apparatus, computer equipment and storage medium. Background Art
[0002] With the rapid development of the Internet and smart terminal technology, payment methods have gradually shifted from offline payment to online payment, and cashlessness has become a very common phenomenon.
[0003] While online payment brings convenience, it also has certain drawbacks. For example, when making online scan code payments, if the balance in the payment account is insufficient, the payment cannot be completed normally, resulting in the inability to complete the transaction normally. Summary of the invention
[0004] Based on this, it is necessary to provide a transaction payment method, device, computer equipment and storage medium that can realize transaction payment on behalf of others in response to the above technical problems.
[0005] In a first aspect, the present application provides a transaction payment method. The method comprises:
[0006] In response to the payment request sent by the payee, a payment order is generated according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0007] Determine candidate payment users for the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0008] The proxy payment order is sent to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0009] In one embodiment, determining a target proxy payment user from among candidate proxy payment users includes:
[0010] Sort the candidate payment users according to their payment priorities;
[0011] According to the ranking result and the account balance of each candidate payment user, a target payment user is determined from among the candidate payment users.
[0012] In one embodiment, the method further comprises:
[0013] The payment priority of each candidate agent payment user is determined according to the number of agent payment interactions between each candidate agent payment user and the payable user within a preset period of time, and / or the number of non-payment interactions between each candidate agent payment user and the payable user within a preset period of time.
[0014] In one embodiment, the payment priority of each candidate payment user is determined according to the number of payment interactions between each candidate payment user and the payable user within a preset period of time and the number of non-payment interactions between each candidate payment user and the payable user within the preset period of time, including:
[0015] Determine a first priority score for each candidate payment agent user according to the relationship between the number of payment agent interactions between each candidate payment agent user and the payable user within a preset period and the first interaction threshold;
[0016] Determine the second priority score of each candidate payment user according to the relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and the second interaction threshold;
[0017] According to the payment interaction weight and the non-payment interaction weight, the first priority score and the second priority score are weighted and summed to obtain the payment priority score of each candidate payment user;
[0018] The payment priority of each candidate payment user is determined according to the payment priority score of each candidate payment user.
[0019] In one embodiment, determining a target proxy payment user from among the candidate proxy payment users according to the ranking result and the account balance of each candidate proxy payment user includes:
[0020] Determine a preliminary payment agent user from among the candidate payment agents based on the ranking results and the account balances of the candidate payment agents;
[0021] Each preliminarily selected proxy payment user is sent to the user terminal of the payable user, so that the paying user can determine the target proxy payment user from among the preliminarily selected proxy payment users through the user terminal.
[0022] In one embodiment, the method further comprises:
[0023] Receive a transaction payment request sent by the payee; wherein the transaction payment request carries the identity of the payee and the amount to be paid;
[0024] Determine the account balance of the payable user according to the payable user's identity identifier;
[0025] If the account balance is less than the amount to be paid, a prompt message is sent to the payee to enable the paying user to send a proxy payment request through the proxy payment confirmation component in the prompt message output by the payee; wherein the prompt message carries the proxy payment confirmation component.
[0026] In a second aspect, the present application also provides a transaction payment device. The device includes:
[0027] A generation module, configured to generate a payment order in response to a payment request sent by a payee, according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0028] A first determination module is used to determine candidate payment users of the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0029] The first sending module is used to send an agent payment order to a user terminal of a target agent payment user, so that the target agent payment user can process the order to be paid through the user terminal.
[0030] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:
[0031] In response to the payment request sent by the payee, a payment order is generated according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0032] Determine candidate payment users for the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0033] The proxy payment order is sent to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0034] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:
[0035] In response to the payment request sent by the payee, a payment order is generated according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0036] Determine candidate payment users for the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0037] The proxy payment order is sent to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0038] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:
[0039] In response to the payment request sent by the payee, a payment order is generated according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0040] Determine candidate payment users for the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0041] The proxy payment order is sent to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0042] The above-mentioned transaction payment method, device, computer equipment and storage medium, the present application can send a payment request carrying the amount to be paid and the identity of the payee user to the server side through the payee, the server side generates a payment order based on the amount to be paid and the identity of the payee user, and the server side then determines the candidate payment users of the payee user based on the identity of the payee user, and determines the target payment user from the candidate payment users; the payment order is sent to the user side of the target payment user, so that the target payment user can process the payment order through the user side. The present application can not only determine the target payment user through the interaction between the payee and the server side, but also complete the payment operation by the target payment user when the payee user cannot complete the payment normally, and there is no need to interact with the user side of the payee user in the process of determining the target payment, while realizing the payment function, it also improves the efficiency of determining the target payment user, and effectively solves the problem that when the balance in the payment account is insufficient and the transaction cannot be completed normally using the traditional transaction payment method. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] FIG1 is a diagram showing an application environment of a transaction payment method provided in this embodiment;
[0044] Figure 2 A schematic diagram of the process flow of the first transaction payment method provided in this embodiment;
[0045] Figure 3 A schematic diagram of a process for determining a target proxy payment user from among candidate proxy payment users provided in this embodiment;
[0046] Figure 4 A schematic diagram of a process for determining the payment priority of each candidate payment agent user provided in this embodiment;
[0047] Figure 5 A schematic diagram of the process of sending a payment request provided in this embodiment;
[0048] Figure 6A schematic diagram of the flow of the second transaction payment method provided in this embodiment;
[0049] Figure 7 A structural block diagram of the transaction payment device provided in this embodiment;
[0050] FIG8 is a diagram showing the internal structure of the computer device provided in this embodiment. DETAILED DESCRIPTION
[0051] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0052] The transaction payment method provided in the embodiment of the present application can be applied in the application environment shown in FIG1 . The server 104 receives the payment request sent by the payee 102 carrying the amount to be paid and the identity of the payee user, and the server 104 generates a payment order based on the amount to be paid and the identity of the payee user. The server 104 determines the candidate payment users of the payee user based on the identity of the payee user, and determines the target payment user from the candidate payment users; the server 104 sends the payment order to the user terminal 106 of the target payment user, so that the target payment user can process the order to be paid through the user terminal 106.
[0053] Among them, the payee in this embodiment refers to the device used for smart payment collection set by the merchant during offline transactions, such as a smart terminal such as a mobile phone, a computer, or a customized terminal device. The terminal device may have a code scanning function, and obtains the item information of the transaction item (such as the name of the item, the price of the item, etc.) by scanning the barcode or QR code of the transaction item, forms an order to be paid, and can also obtain the identity of the payee. The service end refers to the payment platform corresponding to the payment software associated with the payee, such as the backend server corresponding to the payment software. The user end refers to the user's smart terminal, such as a mobile phone, a computer, or other terminal devices, or it can be a smart wearable device such as a smart bracelet or a smart watch.
[0054] In one embodiment, a transaction payment method is provided, and the method is applied to the server in FIG. 1 as an example for explanation. Figure 2 As shown, the following steps are included:
[0055] S201, in response to a payment request sent by a payee, generating a payment order according to the amount to be paid and the identity of the payee, wherein the payment request carries the amount to be paid and the identity of the payee.
[0056] Among them, the pending payment request refers to the request instruction sent by the payee to the server side for other users to make payment on his behalf when the payee user cannot complete the payment normally, wherein the payment request carries the amount to be paid and the identity of the payee user. The pending payment amount refers to the amount that needs to be paid but has not been paid. The payee user refers to the user who should pay the pending payment amount, that is, the buyer among the buyers and sellers. The identity identifier refers to the unique identifier used to characterize the identity of the payee user, such as ID number, name, etc., or it can be the biometric feature of the payee user, such as fingerprint, facial image features, etc. The payment on behalf order refers to an order generated based on the pending payment amount and the payee user's identity identifier, and is sent to the user end of the target payment on behalf user.
[0057] Optionally, in this embodiment, after receiving the payment request sent by the payee, the server parses the payment request to obtain the amount to be paid and the identity of the payee carried in the payment request, and generates a payment order based on the amount to be paid and the identity of the payee.
[0058] In this embodiment, an optional implementation method for generating a payment order based on the amount to be paid and the identity identifier of the user who should pay is: pre-create an order template, the order template has an amount area and an identification area, when generating the payment order, add the amount to be paid to the amount area, and add the identity identifier of the user who should pay to the identification area, thereby forming an order to be paid.
[0059] S202, determining candidate proxy payment users of the payable user according to the identity identifier of the payable user, and determining a target proxy payment user from among the candidate proxy payment users.
[0060] The candidate user to be paid refers to a user who is selected to replace the payee user to perform the payment operation of this transaction. The target payment user refers to a user who is determined from the candidate users to be paid and finally performs the payment operation of this transaction.
[0061] In this embodiment, an optional implementation method for determining each candidate payment user of the payable user according to the identity identifier of the payable user is: according to the identity identifier of the payable user, obtain the payment user list corresponding to the identity identifier, and use the users in the payment user list as candidate users to be paid. Among them, the users in the list of users to be paid are pre-set by the payable user. On this basis, an optional implementation method for determining the target payment user from each candidate payment user is: a user can be randomly selected from the payment user list as the target payment user. It is also possible to set a priority order for the users in the payment user list in advance, and select the user with the highest priority as the target payment user.
[0062] In this embodiment, another optional implementation method for determining candidate payment users of the payable user according to the identity identifier of the payable user is: according to the identity identifier of the payable user, select users who interact with the payable user more frequently within a preset period as candidate payment users. On this basis, an optional implementation method for determining the target payment user from the candidate payment users is: select the candidate payment user with the most interactions as the target payment user.
[0063] S203, sending the proxy payment order to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0064] An optional implementation of this embodiment is: sending an order link of the proxy payment order to the user terminal of the target proxy payment user in the form of a text message, so that the target proxy payment user can complete the pending payment operation through the order link.
[0065] Another optional implementation of this embodiment is: the user terminal of the target payment user pre-installs a client application corresponding to the server, and sends a payment order to the user terminal of the target payment user through the client application, so that the target payment user can process the order to be paid through the user terminal.
[0066] In this embodiment, the payment request carrying the amount to be paid and the identity of the payee user can be sent to the server side through the payee. The server generates a payment order based on the amount to be paid and the identity of the payee user. The server then determines the candidate payment users of the payee user based on the identity of the payee user, and determines the target payment user from the candidate payment users; the payment order is sent to the user side of the target payment user so that the target payment user can process the payment order through the user side. This application can not only determine the target payment user through the interaction between the payee and the server, but also complete the payment operation by the target payment user when the payee user cannot complete the payment normally. In the process of determining the target payment, there is no need to interact with the user side of the payee user. While realizing the payment function, it also improves the efficiency of determining the target payment user, and effectively solves the problem of not being able to complete the transaction normally when the balance in the payment account is insufficient using the traditional transaction payment method.
[0067] In one embodiment, in order to more quickly determine the target payment agent user from the candidate payment agents, such as Figure 3 As shown, an optional implementation of determining a target proxy payment user from among the candidate proxy payment users in S202 includes:
[0068] S301, sorting candidate payment users according to their payment priorities.
[0069] Among them, payment priority refers to the priority of making payments on behalf of the corresponding payment user.
[0070] Optionally, in this embodiment, the payment priority of each candidate user to be paid may be preset, and then the candidate payment users may be sorted according to the payment priority of each candidate payment user in descending or ascending order.
[0071] S302: Determine a target proxy payment user from among the candidate proxy payment users according to the ranking result and the account balance of each candidate proxy payment user.
[0072] The account balance may be the account balance of a bound bank card or the account balance of a payment software.
[0073] Optionally, in this embodiment, a preliminary payment user is determined from each candidate payment user according to the ranking result and the account balance of each candidate payment user. Each preliminary payment user is sent to the user terminal of the payable user, so that the paying user can determine the target payment user from each preliminary payment user through the user terminal.
[0074] In this embodiment, an optional implementation method for determining the preliminary payment user from the candidate payment users based on the sorting results and the account balance of each candidate payment user is: if the sorting rule is descending, the candidate payment user with the highest sorting position in the sorting result and an account balance greater than or equal to the amount to be paid is selected as the target payment user.
[0075] In this embodiment, another optional implementation method for determining the preliminary payment user from the candidate payment users based on the sorting results and the account balance of each candidate payment user is: if the sorting rule is ascending, the candidate payment user with the last sorting position in the sorting result and whose account balance is greater than or equal to the amount to be paid is selected as the target payment user.
[0076] Optionally, in this embodiment, the payment priority of each candidate payment agent user can be pre-set by the payable user, or it can be determined in the following way: according to the number of payment interactions between each candidate payment agent user and the payable user within a preset period, and / or the number of non-payment interactions between each candidate payment agent user and the payable user within a preset period, the payment priority of each candidate payment agent user is determined. Among them, the preset period refers to a preset period, for example, it can be the past week or the past month. The number of interactions to be paid refers to the number of times the payable user pays on behalf of each candidate payment agent user, and the number of times each candidate payment agent pays on behalf of the payable user. The number of non-payment interactions refers to the number of interactions between the payable user and each candidate payment agent user other than payment, such as the frequency of chats, the frequency of voice communication, etc. Optionally, in this embodiment, the payment priority of each candidate payment agent user can be determined according to the number of payment interactions between each candidate payment agent user and the payable user within a preset period. For example, according to the number of payment interactions between each candidate payment agent and the payable user in the past month, each candidate payment agent is sorted, and the payment priority of each candidate payment agent is determined according to the sorting result, for example, the more payment interactions, the higher the payment priority. Optionally, in this embodiment, the payment priority of each candidate payment agent is determined by the number of non-payment interactions between each candidate payment agent and the payable user within a preset period of time. For example, according to the number of non-payment interactions between each candidate payment agent and the payable user in the past month, each candidate payment agent is sorted, and the payment priority of each candidate payment agent is determined according to the sorting result, for example, the more non-payment interactions, the higher the payment priority.
[0077] In this embodiment, a preliminary payment user is determined from each candidate payment user according to the ranking result and the account balance of each candidate payment user. Each preliminary payment user is sent to the user terminal of the payable user, so that the payee can determine the target payment user from each preliminary payment user through the user terminal, which can facilitate the rapid determination of the target payment user.
[0078] In one embodiment, in order to more accurately determine the payment priority of each candidate payment agent user, such as Figure 4 As shown, an optional implementation method of determining the payment priority of each candidate payment user according to the number of payment interactions between each candidate payment user and the payable user within a preset period of time and the number of non-payment interactions between each candidate payment user and the payable user within the preset period of time includes:
[0079] S401, determining a first priority score for each candidate payment agent user according to a relationship between the number of payment agent interactions between each candidate payment agent user and the payable user within a preset period and a first interaction threshold.
[0080] The first interaction threshold is a threshold used to define the range of the number of payment-on-behalf-of interactions, and the number of the first interaction thresholds may be more than two.
[0081] Optionally, in this embodiment, the number of first interaction thresholds is more than two, and a threshold interval is formed between adjacent first interaction thresholds. A corresponding priority score is set for each threshold interval. According to the number of payment on behalf of each candidate payment user and the payable user within a preset time period, the threshold interval to which the number of payment on behalf of the user belongs is determined, and the priority score corresponding to the threshold interval is used as the first priority score of the corresponding candidate payment user.
[0082] S402, determining a second priority score for each candidate payment user according to a relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and a second interaction threshold.
[0083] The second interaction threshold refers to a threshold used to define the range of the number of non-payment interactions, and the number of the second interaction threshold may be more than two.
[0084] Optionally, in this embodiment, the number of second interaction thresholds is more than two, and a threshold interval is formed between adjacent second interaction thresholds. Two corresponding priority scores are set for each threshold interval. According to the number of non-payment interactions between each candidate payment user and the payable user within a preset time period, the threshold interval to which the non-payment interaction number belongs is determined, and the priority score corresponding to the threshold interval is used as the second priority score of the corresponding candidate payment user.
[0085] S403 , performing weighted sum processing on the first priority score and the second priority score according to the payment interaction weight and the non-payment interaction weight, to obtain the payment priority score of each candidate payment agent user.
[0086] Among them, the payment interaction weight refers to the weight value corresponding to the payment interaction. The non-payment interaction weight refers to the weight value corresponding to the non-payment interaction.
[0087] Optionally, in this embodiment, the payment interaction weight and the non-payment interaction weight are predetermined, and then the product result of the first priority score and the payment interaction weight is calculated as the first product result, and the product result of the second priority score and the non-payment interaction weight is calculated as the second product result, and the first product result and the second product result are summed to obtain the payment priority score of each candidate payment user.
[0088] S404: Determine the payment priority of each candidate payment user according to the payment priority score of each candidate payment user.
[0089] An optional implementation of this embodiment is: sorting the candidate payment users according to their payment priority scores, and determining the payment priority of each candidate payment user according to the sorting results. For example, the higher the ranking, the higher the payment priority, and so on.
[0090] Another optional implementation of this embodiment is: determine the payment priority of each candidate payment user according to the payment priority score and priority score interval of each candidate payment user. The priority score interval is pre-set and has a score interval with a maximum priority score and a minimum priority score. There are multiple priority score intervals, and each priority score interval corresponds to a priority.
[0091] In this embodiment, the first priority score of each candidate payment user is determined based on the relationship between the number of payment interactions between each candidate payment user and the payable user within a preset period and the first interaction threshold. The second priority score of each candidate payment user is determined based on the relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and the second interaction threshold. The first priority score and the second priority score are weighted and summed according to the payment interaction weight and the non-payment interaction weight to obtain the payment priority score of each candidate payment user. The payment priority of each candidate payment user is determined based on the payment priority score of each candidate payment user, so that the payment priority of each candidate payment user can be determined more accurately.
[0092] In one embodiment, in order to automatically send a payment request, such as Figure 5 As shown, an optional implementation of a transaction payment method includes:
[0093] S501, receiving a transaction payment request sent by a payee; wherein the transaction payment request carries the identity of the payee and the amount to be paid.
[0094] The transaction payment request refers to the payment request sent by the payee to the server when making a transaction payment.
[0095] S502, determining the account balance of the payable user according to the identity identifier of the payable user.
[0096] Optionally, in this embodiment, the account information of the payable user may be determined according to the identity identifier of the payable user, and the account balance of the payable user may be determined according to the account information of the payable user.
[0097] S503, if the account balance is less than the amount to be paid, a prompt message is sent to the payee, so that the paying user can send a proxy payment request through the proxy payment confirmation component in the prompt message output by the payee. The prompt message carries the proxy payment confirmation component.
[0098] The prompt message refers to a message sent by the server to the payee when the account balance is less than the amount to be paid, and the prompt message carries a proxy payment confirmation component. The proxy payment confirmation component refers to a component that can provide the payee with confirmation of proxy payment through the payee, such as a proxy payment confirmation button.
[0099] In this embodiment, a transaction payment request sent by a payee is received; wherein the transaction payment request carries the identity identifier of the payee user and the amount to be paid; based on the identity identifier of the payee user, the account balance of the payee user is determined; if the account balance is less than the amount to be paid, a prompt message is sent to the payee to enable the paying user to send a proxy payment request through a proxy payment confirmation component in the prompt message output by the payee; wherein the prompt message carries the proxy payment confirmation component to facilitate the payee user to confirm the sending of the proxy payment request.
[0100] In one embodiment, if Figure 6 As shown, an optional implementation of a transaction payment method includes:
[0101] S601, receiving a transaction payment request sent by a payee, wherein the transaction payment request carries the identity of the payee and the amount to be paid.
[0102] S602, determining the account balance of the payable user according to the identity identifier of the payable user.
[0103] S603, if the account balance is less than the amount to be paid, a prompt message is sent to the payee, so that the paying user can send a proxy payment request through the proxy payment confirmation component in the prompt message output by the payee. The prompt message carries the proxy payment confirmation component.
[0104] S604, in response to the payment request sent by the payee, generating a payment order according to the amount to be paid and the identity of the payee, wherein the payment request carries the amount to be paid and the identity of the payee.
[0105] S605, determining candidate payment users for the payable user according to the identity identifier of the payable user.
[0106] S606: Determine a first priority score for each candidate payment agent user according to the relationship between the number of payment agent interactions between each candidate payment agent user and the payable user within a preset period and a first interaction threshold.
[0107] S607, determining a second priority score for each candidate payment user according to the relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and the second interaction threshold.
[0108] S608 , performing weighted sum processing on the first priority score and the second priority score according to the payment interaction weight and the non-payment interaction weight, to obtain a payment priority score for each candidate payment agent user.
[0109] S609: Determine the payment priority of each candidate payment user according to the payment priority score of each candidate payment user.
[0110] S6010: Sort the candidate payment users according to their payment priorities.
[0111] S6011, determining a preliminary payment agent user from among the candidate payment agents based on the ranking result and the account balance of each candidate payment agent user.
[0112] S6012, sending each preliminarily selected proxy payment user to the user terminal of the payee user, so that the payee user can determine the target proxy payment user from among the preliminarily selected proxy payment users through the user terminal.
[0113] S6013, sending the proxy payment order to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0114] In this embodiment, a payment request carrying the amount to be paid and the identity of the payee user can be sent to the server side through the payee. The server generates a payment order based on the amount to be paid and the identity of the payee user. The server then determines the candidate payment users of the payee user based on the identity of the payee user, and determines the target payment user from the candidate payment users; the payment order is sent to the user side of the target payment user so that the target payment user can process the payment order through the user side. This application can not only determine the target payment user through the interaction between the payee and the server, but also complete the payment operation by the target payment user when the payee user cannot complete the payment normally. In addition, there is no need to interact with the user side of the payee user in the process of determining the target payment. While realizing the payment function, it also improves the efficiency of determining the target payment user, and effectively solves the problem of not being able to complete the transaction normally when the balance in the payment account is insufficient using the traditional transaction payment method.
[0115] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0116] Based on the same inventive concept, the embodiment of the present application also provides a transaction payment device for implementing the transaction payment method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more transaction payment device embodiments provided below can refer to the limitations on the transaction payment method above, and will not be repeated here.
[0117] In one embodiment, if Figure 7 As shown, a transaction payment device 1 is provided, comprising: a generating module 10, a first determining module 20 and a first sending module 30, wherein:
[0118] The generating module 10 is used to generate a payment order in response to the payment request sent by the payee according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0119] The first determination module 20 is used to determine candidate payment users of the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0120] The first sending module 30 is used to send an agent payment order to a user terminal of a target agent payment user, so that the target agent payment user can process the order to be paid through the user terminal.
[0121] The transaction payment device in this embodiment can send a payment request carrying the amount to be paid and the identity of the payee user to the server side through the payee, and the server side generates a payment order based on the amount to be paid and the identity of the payee user. The server side then determines the candidate payment users of the payee user based on the identity of the payee user, and determines the target payment user from the candidate payment users; the payment order is sent to the user side of the target payment user, so that the target payment user can process the payment order through the user side. This application can not only determine the target payment user through the interaction between the payee and the server, but also complete the payment operation by the target payment user when the payee user cannot complete the payment normally, and there is no need to interact with the user side of the payee user in the process of determining the target payment. While realizing the payment function, it also improves the efficiency of determining the target payment user, and effectively solves the problem of not being able to complete the transaction normally when the balance in the payment account is insufficient using the traditional transaction payment method.
[0122] In one embodiment, the Figure 7 The first determining module 20 further comprises:
[0123] The sorting unit is used to sort the candidate payment users according to their payment priorities.
[0124] The first determining unit is used to determine a target proxy payment user from among the candidate proxy payment users according to the ranking result and the account balance of each candidate proxy payment user.
[0125] Based on the above embodiments, Figure 7 The transaction payment device further comprises:
[0126] The second determination module is used to determine the payment priority of each candidate payment user according to the number of payment interactions between each candidate payment user and the payable user within a preset time period and / or the number of non-payment interactions between each candidate payment user and the payable user within a preset time period.
[0127] In one embodiment, the second determining module further comprises:
[0128] The second determining unit is used to determine the first priority score of each candidate payment agent user according to the relationship between the number of payment agent interactions between each candidate payment agent user and the payable user within a preset time period and the first interaction threshold.
[0129] The third determining unit is used to determine the second priority score of each candidate payment user according to the relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and the second interaction threshold.
[0130] The processing unit is used to perform weighted sum processing on the first priority score and the second priority score according to the payment interaction weight and the non-payment interaction weight to obtain the payment priority score of each candidate payment user.
[0131] The fourth determining unit is used to determine the payment priority of each candidate payment user according to the payment priority score of each candidate payment user.
[0132] In one embodiment, the first determining unit further comprises:
[0133] The fifth determining unit is used to determine a preliminary selected proxy payment user from among the candidate proxy payment users according to the ranking result and the account balance of each candidate proxy payment user.
[0134] The sending unit is used to send each preliminarily selected proxy payment user to the user terminal of the payable user, so that the paying user can determine the target proxy payment user from among the preliminarily selected proxy payment users through the user terminal.
[0135] In one embodiment, the Figure 7 The transaction payment device further comprises:
[0136] The receiving module receives a transaction payment request sent by the payee; wherein the transaction payment request carries the identity identifier of the payee and the amount to be paid.
[0137] The third determining module determines the account balance of the payable user according to the identity identifier of the payable user.
[0138] The second sending module is used to send a prompt message to the payee if the account balance is less than the amount to be paid, so as to enable the paying user to send a proxy payment request through the proxy payment confirmation component in the prompt message output by the payee; wherein the prompt message carries the proxy payment confirmation component.
[0139] Each module in the transaction payment device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.
[0140] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG8. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store payment information. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a transaction payment method is implemented.
[0141] Those skilled in the art will understand that the structure shown in FIG. 8 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.
[0142] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:
[0143] In response to the payment request sent by the payee, a payment order is generated according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0144] Determine candidate payment users for the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0145] The proxy payment order is sent to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0146] In one embodiment, when the processor executes the computer program, the following steps are further implemented: determining a target proxy payment user from among the candidate proxy payment users, including:
[0147] Sort the candidate payment users according to their payment priority;
[0148] According to the ranking result and the account balance of each candidate payment user, a target payment user is determined from among the candidate payment users.
[0149] In one embodiment, when the processor executes the computer program, the following steps are also implemented: the method further includes:
[0150] The payment priority of each candidate agent payment user is determined according to the number of agent payment interactions between each candidate agent payment user and the payable user within a preset period of time, and / or the number of non-payment interactions between each candidate agent payment user and the payable user within a preset period of time.
[0151] In one embodiment, when the processor executes the computer program, the following steps are further implemented: according to the number of proxy payment interactions between each candidate proxy payment user and the payable user within a preset period, and the number of non-payment interactions between each candidate proxy payment user and the payable user within the preset period, the payment priority of each candidate proxy payment user is determined, including:
[0152] Determine a first priority score for each candidate payment agent user according to the relationship between the number of payment agent interactions between each candidate payment agent user and the payable user within a preset period and the first interaction threshold;
[0153] Determine the second priority score of each candidate payment user according to the relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and the second interaction threshold;
[0154] According to the payment interaction weight and the non-payment interaction weight, the first priority score and the second priority score are weighted and summed to obtain the payment priority score of each candidate payment user;
[0155] The payment priority of each candidate payment user is determined according to the payment priority score of each candidate payment user.
[0156] In one embodiment, when the processor executes the computer program, the following steps are further implemented: determining a target payment agent user from each candidate payment agent user according to the ranking result and the account balance of each candidate payment agent user, including:
[0157] Determine a preliminary payment agent user from among the candidate payment agents based on the ranking results and the account balances of the candidate payment agents;
[0158] Each preliminarily selected proxy payment user is sent to the user terminal of the payable user, so that the paying user can determine the target proxy payment user from among the preliminarily selected proxy payment users through the user terminal.
[0159] In one embodiment, when the processor executes the computer program, the following steps are also implemented: the method further includes:
[0160] Receive a transaction payment request sent by the payee; wherein the transaction payment request carries the identity of the payee and the amount to be paid;
[0161] Determine the account balance of the payable user according to the payable user's identity identifier;
[0162] If the account balance is less than the amount to be paid, a prompt message is sent to the payee to enable the paying user to send a proxy payment request through the proxy payment confirmation component in the prompt message output by the payee; wherein the prompt message carries the proxy payment confirmation component.
[0163] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
[0164] In response to the payment request sent by the payee, a payment order is generated according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0165] Determine candidate payment users for the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0166] The proxy payment order is sent to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0167] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: determining a target proxy payment user from among the candidate proxy payment users, including:
[0168] Sort the candidate payment users according to their payment priorities;
[0169] According to the ranking result and the account balance of each candidate payment user, a target payment user is determined from among the candidate payment users.
[0170] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: the method further includes:
[0171] The payment priority of each candidate agent payment user is determined according to the number of agent payment interactions between each candidate agent payment user and the payable user within a preset period of time, and / or the number of non-payment interactions between each candidate agent payment user and the payable user within a preset period of time.
[0172] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: according to the number of proxy payment interactions between each candidate proxy payment user and the payable user within a preset period of time, and the number of non-payment interactions between each candidate proxy payment user and the payable user within the preset period of time, the payment priority of each candidate proxy payment user is determined, including:
[0173] Determine a first priority score for each candidate payment agent user according to the relationship between the number of payment agent interactions between each candidate payment agent user and the payable user within a preset period and the first interaction threshold;
[0174] Determine the second priority score of each candidate payment user according to the relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and the second interaction threshold;
[0175] According to the payment interaction weight and the non-payment interaction weight, the first priority score and the second priority score are weighted and summed to obtain the payment priority score of each candidate payment user;
[0176] The payment priority of each candidate payment user is determined according to the payment priority score of each candidate payment user.
[0177] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: determining a target payment agent user from each candidate payment agent user according to the ranking result and the account balance of each candidate payment agent user, including:
[0178] Determine a preliminary payment agent user from among the candidate payment agents based on the ranking results and the account balances of the candidate payment agents;
[0179] Each preliminarily selected proxy payment user is sent to the user terminal of the payable user, so that the paying user can determine the target proxy payment user from among the preliminarily selected proxy payment users through the user terminal.
[0180] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: the method further includes:
[0181] Receive a transaction payment request sent by the payee; wherein the transaction payment request carries the identity of the payee and the amount to be paid;
[0182] Determine the account balance of the payable user according to the payable user's identity identifier;
[0183] If the account balance is less than the amount to be paid, a prompt message is sent to the payee to enable the paying user to send a proxy payment request through the proxy payment confirmation component in the prompt message output by the payee; wherein the prompt message carries the proxy payment confirmation component.
[0184] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:
[0185] In response to the payment request sent by the payee, a payment order is generated according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user;
[0186] Determine candidate payment users for the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users;
[0187] The proxy payment order is sent to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
[0188] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: determining a target proxy payment user from among the candidate proxy payment users, including:
[0189] Sort the candidate payment users according to their payment priorities;
[0190] According to the ranking result and the account balance of each candidate payment user, a target payment user is determined from among the candidate payment users.
[0191] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: the method further includes:
[0192] The payment priority of each candidate agent payment user is determined according to the number of agent payment interactions between each candidate agent payment user and the payable user within a preset period of time, and / or the number of non-payment interactions between each candidate agent payment user and the payable user within a preset period of time.
[0193] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: according to the number of proxy payment interactions between each candidate proxy payment user and the payable user within a preset period of time, and the number of non-payment interactions between each candidate proxy payment user and the payable user within the preset period of time, the payment priority of each candidate proxy payment user is determined, including:
[0194] Determine a first priority score for each candidate payment agent user according to the relationship between the number of payment agent interactions between each candidate payment agent user and the payable user within a preset period and the first interaction threshold;
[0195] Determine the second priority score of each candidate payment user according to the relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and the second interaction threshold;
[0196] According to the payment interaction weight and the non-payment interaction weight, the first priority score and the second priority score are weighted and summed to obtain the payment priority score of each candidate payment user;
[0197] The payment priority of each candidate payment user is determined according to the payment priority score of each candidate payment user.
[0198] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: determining a target payment agent user from each candidate payment agent user according to the ranking result and the account balance of each candidate payment agent user, including:
[0199] Determine a preliminary payment agent user from among the candidate payment agents based on the ranking results and the account balances of the candidate payment agents;
[0200] Each preliminarily selected proxy payment user is sent to the user terminal of the payable user, so that the paying user can determine the target proxy payment user from among the preliminarily selected proxy payment users through the user terminal.
[0201] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: the method further includes:
[0202] Receive a transaction payment request sent by the payee; wherein the transaction payment request carries the identity of the payee and the amount to be paid;
[0203] Determine the account balance of the payable user according to the payable user's identity identifier;
[0204] If the account balance is less than the amount to be paid, a prompt message is sent to the payee to enable the paying user to send a proxy payment request through the proxy payment confirmation component in the prompt message output by the payee; wherein the prompt message carries the proxy payment confirmation component.
[0205] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.
[0206] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0207] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A transaction payment method, It is characterized in that The method comprises: In response to the payment request sent by the payee, a payment order is generated according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user; Determine candidate proxy payment users of the payable user according to the identity identifier of the payable user, and determine a target proxy payment user from among the candidate proxy payment users; The proxy payment order is sent to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
2. The method according to claim 1, It is characterized in that The step of determining a target proxy payment user from among the candidate proxy payment users comprises: Sort the candidate payment users according to their payment priority; According to the ranking result and the account balance of each candidate payment user, a target payment user is determined from among the candidate payment users.
3. The method according to claim 2, It is characterized in that The method further comprises: The payment priority of each candidate agent payment user is determined according to the number of agent payment interactions between each candidate agent payment user and the payable user within a preset period, and / or the number of non-payment interactions between each candidate agent payment user and the payable user within a preset period.
4. The method according to claim 3, It is characterized in that The step of determining the payment priority of each candidate payment user on behalf of another according to the number of payment interactions between each candidate payment user on behalf of another and the payable user within a preset period of time and the number of non-payment interactions between each candidate payment user on behalf of another and the payable user within a preset period of time includes: Determine a first priority score for each candidate payment agent user according to the relationship between the number of payment agent interactions between each candidate payment agent user and the payable user within a preset period and a first interaction threshold; Determine a second priority score for each candidate payment user according to the relationship between the number of non-payment interactions between each candidate payment user and the payable user within a preset period and a second interaction threshold; According to the payment interaction weight and the non-payment interaction weight, the first priority score and the second priority score are weighted and summed to obtain the payment priority score of each candidate payment agent user; The payment priority of each candidate payment user is determined according to the payment priority score of each candidate payment user.
5. The method according to claim 2, It is characterized in that The step of determining a target proxy payment user from among the candidate proxy payment users according to the ranking result and the account balance of each candidate proxy payment user comprises: Determine a preliminary payment agent user from among the candidate payment agents based on the ranking results and the account balances of the candidate payment agents; Each preliminarily selected proxy payment user is sent to the user terminal of the payable user, so that the paying user can determine the target proxy payment user from among the preliminarily selected proxy payment users through the user terminal.
6. The method according to claim 1, It is characterized in that The method further comprises: Receiving a transaction payment request sent by the payee; wherein the transaction payment request carries the identity identifier of the payee and the amount to be paid; Determining the account balance of the payable user according to the identity identifier of the payable user; If the account balance is less than the amount to be paid, a prompt message is sent to the payee to enable the paying user to send the proxy payment request through the proxy payment confirmation component in the prompt message output by the payee; wherein the prompt message carries the proxy payment confirmation component.
7. A transaction payment device, It is characterized in that The device comprises: A generation module, configured to generate a payment order in response to a payment request sent by a payee, according to the amount to be paid and the identity identifier of the payee user; wherein the payment request carries the amount to be paid and the identity identifier of the payee user; A first determination module is used to determine candidate payment users of the payable user according to the identity identifier of the payable user, and determine a target payment user from among the candidate payment users; The first sending module is used to send the proxy payment order to the user terminal of the target proxy payment user, so that the target proxy payment user can process the order to be paid through the user terminal.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program. It is characterized in that When the processor executes the computer program, the steps of the transaction payment method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the steps of the transaction payment method according to any one of claims 1 to 6 are implemented.
10. A computer program product comprising a computer program, It is characterized in that When the computer program is executed by a processor, the steps of the transaction payment method described in any one of claims 1 to 6 are implemented.
