Payment authorization method and apparatus

Abstract

The embodiments of the present specification provide a payment authorization method and device, wherein a payment authorization method comprises: obtaining a target user sending an authorization invitation and a payment confirmation policy configured for the target user by a first terminal associated with a user; sending authorization invitation information carrying the payment confirmation policy to a second terminal of the target user, and receiving a confirmation instruction of the authorization invitation information sent by the second terminal; based on the confirmation instruction, establishing a payment authorization relationship between the associated user and the target user, so as to perform multiple payment verification on a payment request of the target user for a target transaction according to the payment confirmation policy.

Description

TECHNICAL FIELD

[0001] The present document relates to the technical field of data processing, and in particular to a payment authorization method and device. BACKGROUND

[0002] With the continuous development of the Internet, more and more users begin to use the Internet, and the demand of users for Internet payment is increasing. In the process of using Internet payment, due to the use obstacles of the elderly to the Internet, network frauds targeting the elderly are emerging in an endless stream, and due to the lack of self-control of some teenagers or college students when facing the Internet, the Internet payment is uncontrolled. SUMMARY

[0003] One or more embodiments of the present specification provide a payment authorization method, comprising: obtaining a target user sending an authorization invitation by a first terminal of an associated user, and a payment confirmation policy configured for the target user. Sending authorization invitation information carrying the payment confirmation policy to a second terminal of the target user, and receiving a confirmation instruction of the authorization invitation information sent by the second terminal. Establishing a payment authorization relationship between the associated user and the target user based on the confirmation instruction, for performing multiple payment verification on a payment request of the target user for a target transaction according to the payment confirmation policy.

[0004] One or more embodiments of the present specification provide a payment confirmation processing method, applied to a server, comprising: receiving a payment request submitted by a second terminal of a target user for a target transaction. According to the payment confirmation policy configured for the target user by an associated user establishing a payment authorization relationship with the target user, performing associated verification on the payment request. If the associated verification result is that the payment request triggers the payment confirmation policy, send a payment confirmation reminder to the first terminal of the associated user. According to the payment confirmation instruction submitted by the associated user for the payment confirmation reminder, obtain the identity authentication information of the target user and perform payment processing on the target transaction.

[0005] One or more embodiments of the present specification provide another payment confirmation processing method, applied to a first terminal, comprising: receiving a payment confirmation reminder sent by a server for a payment request of a target user in a target transaction. Obtain the payment confirmation instruction submitted by the associated user for the payment confirmation reminder; the associated user and the target user establish a payment authorization relationship and configure a payment confirmation policy for the target user. Send the payment confirmation instruction to the server; the payment confirmation reminder is sent after the payment request triggers the payment confirmation policy, and before the identity authentication information of the target user is obtained.

[0006] One or more embodiments of the present specification provide a payment authorization apparatus, comprising: a policy obtaining module configured to obtain a target user sending an authorization invitation by a first terminal of an associated user, and a payment confirmation policy configured for the target user. An invitation information sending module configured to send authorization invitation information carrying the payment confirmation policy to a second terminal of the target user, and receive a confirmation instruction of the authorization invitation information sent by the second terminal. An authorization relationship establishing module configured to establish a payment authorization relationship between the associated user and the target user based on the confirmation instruction, for performing multiple payment verifications on a payment request of the target user for a target transaction according to the payment confirmation policy.

[0007] One or more embodiments of the present specification provide a payment confirmation processing apparatus, running on a server, comprising: a payment request receiving module configured to receive a payment request submitted by a second terminal of a target user for a target transaction. An association verification module configured to perform association verification on the payment request according to a payment confirmation policy configured for the target user by an associated user establishing a payment authorization relationship with the target user. If the association verification result is that the payment request triggers the payment confirmation policy, run a confirmation reminder sending module, the confirmation reminder sending module is configured to send a payment confirmation reminder to a first terminal of the associated user. A payment processing module configured to obtain identity authentication information of the target user and perform payment processing on the target transaction according to a payment confirmation instruction submitted by the associated user for the payment confirmation reminder.

[0008] One or more embodiments of the present specification provide another payment confirmation processing apparatus, running on a first terminal, comprising: a confirmation reminder receiving module configured to receive a payment confirmation reminder sent by a server for a payment request of a target user in a target transaction. A confirmation instruction obtaining module configured to obtain a payment confirmation instruction submitted by an associated user for the payment confirmation reminder; the associated user and the target user establish a payment authorization relationship and are configured with a payment confirmation policy for the target user. A confirmation instruction sending module configured to send the payment confirmation instruction to the server; the payment confirmation reminder is sent after the payment request triggers the payment confirmation policy, and before the identity authentication information of the target user is obtained.

[0009] One or more embodiments of the present specification provide a payment authorization device, comprising: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: acquire a target user sending an authorization invitation by a first terminal of an associated user, and a payment confirmation policy configured for the target user. Send authorization invitation information carrying the payment confirmation policy to a second terminal of the target user, and receive a confirmation instruction of the authorization invitation information sent by the second terminal. Establish a payment authorization relationship between the associated user and the target user based on the confirmation instruction, for multiple payment verification of a payment request of the target user for a target transaction according to the payment confirmation policy.

[0010] One or more embodiments of the present specification provide a payment confirmation processing device, comprising: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: receive a payment request submitted by a second terminal of a target user for a target transaction. According to the payment confirmation policy configured for the target user by an associated user establishing a payment authorization relationship with the target user, the payment request is associated with the verification. If the associated verification result is that the payment request triggers the payment confirmation policy, send a payment confirmation reminder to the first terminal of the associated user. According to the payment confirmation instruction submitted by the associated user for the payment confirmation reminder, the identity authentication information of the target user is acquired and the payment processing of the target transaction is performed.

[0011] One or more embodiments of the present specification provide another payment confirmation processing device, comprising: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: receive a payment confirmation reminder sent by a server for a payment request of a target user in a target transaction. Acquire a payment confirmation instruction submitted by an associated user for the payment confirmation reminder; the associated user establishes a payment authorization relationship with the target user and configures a payment confirmation policy for the target user. Send the payment confirmation instruction to the server; the payment confirmation reminder is sent after the payment request triggers the payment confirmation policy, and before the identity authentication information of the target user is acquired.

[0012] The one or more embodiments of the specification provide a first storage medium for storing computer executable instructions, which, when executed by a processor, implement the following processes: obtaining a target user sending an authorization invitation by a first terminal of an associated user, and a payment confirmation policy configured for the target user. Sending authorization invitation information carrying the payment confirmation policy to a second terminal of the target user, and receiving a confirmation instruction of the authorization invitation information sent by the second terminal. Based on the confirmation instruction, establishing a payment authorization relationship between the associated user and the target user, for performing multiple payment verification on a payment request of the target user for a target transaction according to the payment confirmation policy.

[0013] The one or more embodiments of the specification provide a second storage medium for storing computer executable instructions, which, when executed by a processor, implement the following processes: receiving a payment request submitted by a second terminal of a target user for a target transaction. According to a payment confirmation policy configured for the target user by an associated user establishing a payment authorization relationship with the target user, performing associated verification on the payment request. If the associated verification result is that the payment request triggers the payment confirmation policy, sending a payment confirmation reminder to a first terminal of the associated user. According to a payment confirmation instruction submitted by the associated user for the payment confirmation reminder, obtaining identity authentication information of the target user and performing payment processing on the target transaction.

[0014] The one or more embodiments of the specification provide a third storage medium for storing computer executable instructions, which, when executed by a processor, implement the following processes: receiving a payment confirmation reminder sent by a server for a payment request of a target user in a target transaction. Obtaining a payment confirmation instruction submitted by an associated user for the payment confirmation reminder; the associated user establishes a payment authorization relationship with the target user and is configured with a payment confirmation policy for the target user. Sending the payment confirmation instruction to the server; the payment confirmation reminder is sent after the payment request triggers the payment confirmation policy, and before obtaining the identity authentication information of the target user. BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the one or more embodiments of the specification or the prior art, the drawings needed in the embodiment or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments described in the specification, and those skilled in the art can also obtain other drawings according to these drawings without creative labor;

[0016] Figure 1A payment authorization method processing flowchart provided for one or more embodiments of the present specification;

[0017] Figure 2 A payment authorization method processing flowchart applied to an authorized relationship establishment scenario provided for one or more embodiments of the present specification;

[0018] Figure 3 A payment confirmation processing method processing flowchart provided for one or more embodiments of the present specification;

[0019] Figure 4 A payment confirmation processing method processing timing diagram applied to an elderly user scenario provided for one or more embodiments of the present specification;

[0020] Figure 5 A payment confirmation processing method processing timing diagram applied to a young user scenario provided for one or more embodiments of the present specification;

[0021] Figure 6 Another payment confirmation processing method processing flowchart provided for one or more embodiments of the present specification;

[0022] Figure 7 A payment authorization device schematic diagram provided for one or more embodiments of the present specification;

[0023] Figure 8 A payment confirmation processing device schematic diagram provided for one or more embodiments of the present specification;

[0024] Figure 9 Another payment confirmation processing device schematic diagram provided for one or more embodiments of the present specification;

[0025] Figure 10 A payment authorization equipment structural schematic diagram provided for one or more embodiments of the present specification;

[0026] Figure 11 A payment confirmation processing equipment structural schematic diagram provided for one or more embodiments of the present specification;

[0027] Figure 12 Another payment confirmation processing equipment structural schematic diagram provided for one or more embodiments of the present specification. DETAILED DESCRIPTION

[0028] In order for those skilled in the art to better understand the technical solutions in the one or more embodiments of the present specification, the technical solutions in the one or more embodiments of the present specification will be clearly and completely described in the present specification in conjunction with the drawings in the one or more embodiments of the present specification. Obviously, the described embodiments are only a part of the embodiments of the present specification, not all. Based on the one or more embodiments of the present specification, all other embodiments obtained by those skilled in the art without creative labor should belong to the protection scope of the present document.

[0029] An embodiment of the payment authorization method provided by the present specification is provided as follows:

[0030] Referring to Figure 1 , a payment authorization method processing flowchart provided by the present embodiment is shown, referring to Figure 2 , a payment authorization method processing flowchart applied to an authorization relationship establishment scenario provided by the present embodiment is shown.

[0031] Referring to Figure 1 , the payment authorization method provided by the present embodiment specifically includes steps S102 to S106.

[0032] Step S102, obtaining a target user invited by a first terminal of an associated user to authorize, and a payment confirmation policy configured for the target user.

[0033] The payment authorization method provided by the present embodiment obtains a target user invited by an associated user to authorize, and a payment confirmation policy configured for the target user, and then sends authorization invitation information carrying the payment confirmation policy to a terminal device of the target user. If a confirmation instruction for the authorization invitation information is received, an authorization relationship between the associated user and the target user is established, so as to perform multiple payment verification when the target user pays. Through the establishment of the authorization relationship, the payment security and the fund security of the user are ensured, the fund loss is avoided, and the user is helped to use the Internet payment reasonably. By introducing the payment confirmation policy, the consumption granularity is reduced, and the diversified payment scene demand is met.

[0034] The payment confirmation policy refers to a policy for one user to perform payment verification on a payment request initiated by another user in a payment process, such as a single consumption limit. For example, the payment confirmation policy set by the associated user is "single consumption limit 1000 yuan", and the target user sets the transfer amount to 1200 yuan when transferring. The payment request of the target user triggers the payment confirmation policy, and the associated user needs to confirm the payment request of the target user.

[0035] The multiple payment verification refers to verifying a payment request initiated by a user B in a payment process according to a payment confirmation policy constructed by a user A, and obtaining a payment confirmation of the payment request by the user A; or verifying the payment request initiated by the user A in the payment process according to a payment confirmation policy constructed by the user B, and obtaining a payment confirmation of the payment request by the user B.

[0036] It should be noted that, in the process of multiple payment verification, the associated user establishing a payment authorization relationship with the target user can be one or multiple, and therefore the payment confirmation policy configured for the target user can be one or multiple, and the process of verifying the payment request of the target user according to the payment confirmation policy can be performed once or multiple times; similarly, in the process of submitting a payment confirmation instruction and making a payment by the associated user, the associated user can be one or multiple, and therefore the payment confirmation can be performed once or multiple times.

[0037] In actual application, the elderly user cannot distinguish whether the Internet operation is safe or not in the process of using the Internet, resulting in network fraud, and the young user or the college student user lacks correct consumption concept, resulting in uncontrolled Internet payment. In this case, the corresponding consumption limit can be set by the family members of the elderly user, the family members of the young user, the family members of the college student user, or the family members of other users, the payment to the abnormal account is confirmed, which helps them to better use the Internet payment, helps the elderly user to prevent network fraud, and guides the young user to reasonably consume and establish correct consumption concept. In this process, the elderly user, the young user, the college student user, or other users who face Internet fraud or uncontrolled Internet payment are target users, the terminal device used by the target user is a second terminal, and the consumption limit is set for the target user, the payment to the abnormal account is confirmed, which helps the target user to prevent Internet fraud or guides the target user to reasonably consume, and the user who sets the consumption limit for the target user is an associated user, and the terminal device used by the associated user is a first terminal.

[0038] In specific implementation, in order to guide the consumption of the young user and prevent the elderly user from being cheated by the Internet, the payment authorization relationship between the associated user and the elderly user or the young user can be established first, and the associated user guides the consumption of the elderly user or the young user on the basis of the established payment authorization relationship. In order to establish the payment authorization relationship, the associated user first selects a target user to be guided in consumption, and the target user in the embodiment is selected in a user list of the associated user. In an optional implementation provided by the embodiment, before the target user sending an authorization invitation by the first terminal of the associated user is obtained, the following operation is performed:

[0039] receiving the payment authorization application sent by the first terminal; the payment authorization application is submitted by triggering the authorization control;

[0040] reading a user list of the associated user and returning to the first terminal.

[0041] Specifically, the associated user triggers the authorization control to submit the payment authorization application, and the first terminal sends the payment authorization application to the server after detecting the payment authorization application. The server reads a user list of the associated user and returns to the first terminal. The first terminal displays the user list, and the associated user selects a target user for authorization invitation from the user list and configures a payment confirmation strategy for the selected target user. The first terminal sends the selected target user and the payment confirmation strategy to the server, and the server obtains the target user selected by the associated user and the payment confirmation strategy configured for the target user.

[0042] In step S104, authorization invitation information carrying the payment confirmation strategy is sent to a second terminal of the target user, and a confirmation instruction of the authorization invitation information sent by the second terminal is received.

[0043] As described above, the first terminal sends the target user selected by the associated user and the payment confirmation strategy to the server, and the server obtains the target user selected by the associated user and the payment confirmation strategy configured for the target user. On this basis, the embodiment sends authorization invitation information carrying the payment confirmation strategy to the second terminal of the target user. If the confirmation instruction of the authorization invitation information sent by the second terminal is received, it indicates that the target user accepts to establish a payment authorization relationship with the associated user on the basis of the configured payment confirmation strategy. If the confirmation instruction of the authorization invitation information sent by the second terminal is not received, the payment authorization relationship between the target user and the associated user fails to be established.

[0044] In step S106, based on the confirmation instruction, a payment authorization relationship between the associated user and the target user is established for multiple payment verification of a payment request of the target user for a target transaction according to the payment confirmation strategy.

[0045] On the basis of the above sending of the authorization invitation information carrying the payment confirmation strategy to the second terminal of the target user and the receiving of the confirmation instruction of the authorization invitation information sent by the second terminal, the embodiment establishes a payment authorization relationship between the associated user and the target user based on the received confirmation instruction, for multiple payment verification based on the payment confirmation strategy when the target user makes a payment for a target transaction.

[0046] In a specific implementation, the associated user selects a target user for consumption guidance, and configures a payment confirmation policy for the target user. The first terminal submits the selected target user and the payment confirmation policy to the server. The server establishes a payment authorization relationship between the associated user and the target user based on the payment confirmation policy. Based on the payment authorization relationship, the associated user helps the target user to confirm payment when paying, effectively preventing the elderly user from being cheated and cultivating the concept of reasonable consumption of the young user. In an optional implementation of the embodiment, in the process of establishing the payment authorization relationship between the associated user and the target user based on the confirmation instruction, the following operations are performed:

[0047] The payment confirmation permission for the target user in the target transaction is opened to the associated user, and the authorization state is marked as an authorized valid state.

[0048] According to the payment confirmation permission, the authorized valid state, and the payment confirmation policy, a payment authorization record is generated and stored.

[0049] Specifically, in order to realize the payment confirmation of the associated user to the target user in the payment process, the consent of the target user is obtained, the authorization invitation information carrying the payment confirmation policy is sent to the second terminal of the target user, if the confirmation instruction of the authorization invitation information returned by the second terminal is received, the payment confirmation permission for the target user in the target transaction is opened to the associated user, the authorization state is marked as an authorized valid state, and a payment authorization record is generated and stored.

[0050] The payment authorization record is shown in Table 1 as follows:

[0051]

[0052]

[0053] Table 1

[0054] It should be noted that the user identifier in the target user identifier and the associated user identifier can be a user account, or a user identity identifier code, etc. In the process of establishing the payment authorization relationship, the payment authorization record can also be created according to one of the payment confirmation permission and the authorized valid state and the payment confirmation policy.

[0055] In actual application, when the target user uses the teenager mode to make an Internet payment, the consumption cost can be controlled to a certain extent, but the teenager mode cannot perform a payment exceeding the limit, and the consumption granularity of the teenager mode is large, which cannot meet the needs of some payment scenarios. For example, parents want to manage the amount of children in certain consumption (such as games), prevent children from buying goods exceeding the payment capacity (such as luxury goods), and the elderly user cannot identify abnormal accounts. In view of this, in order to meet the needs of diversified payment scenarios, the consumption limit of the teenager user or the elderly user is set, the payment confirmation strategy is used when the abnormal account is paid, and the payment request is verified based on the payment confirmation strategy.

[0056] In an optional implementation provided by the embodiment, in the process of verifying the target transaction of the target user according to the payment confirmation strategy, the following operations are performed:

[0057] The payment request submitted by the second terminal for the target transaction is received, and the payment confirmation strategy is read for associated verification of the payment request;

[0058] If the associated verification result is that the payment request triggers the payment confirmation strategy, a payment confirmation reminder is sent to the first terminal;

[0059] According to the payment confirmation instruction of the payment confirmation reminder, the identity authentication information of the target user is obtained and the payment processing of the target transaction is performed.

[0060] Specifically, in the process of the target user making a payment for the target transaction, the payment request submitted by the target user is obtained, and the associated user establishing a payment authorization relationship with the target user and the payment confirmation strategy set for the target user are read in the payment authorization record. The payment request is associated with the payment confirmation strategy for verification to determine whether the payment request triggers the payment confirmation strategy.

[0061] In the process of associated verification of the payment request, it is detected whether the payment amount carried in the payment request matches the corresponding payment limit in the payment confirmation strategy; if yes, no processing is performed, and if no, it is determined that the payment request triggers the payment confirmation strategy; and based on the payment confirmation strategy, it is judged whether the transfer-in account of the payment amount carried in the payment request is an abnormal account; if yes, it is determined that the payment request triggers the payment confirmation strategy, and if no, no processing is performed.

[0062] For example, the payment amount carried in the payment request is 1200 yuan, and the corresponding single consumption limit in the payment confirmation policy is 1000 yuan. The payment amount exceeds the single consumption limit, so the payment request triggers the corresponding single consumption limit in the payment confirmation policy. For another example, the payment confirmation policy requires the association user to confirm the payment when the transfer-in abnormal account is associated. The transfer-in account of the payment amount carried in the payment request is an abnormal account, so the payment request triggers the corresponding transfer-in account in the payment confirmation policy. In addition, the payment confirmation policy also includes: daily / monthly consumption limit, limit of different consumption categories (game, clothing, catering), and interception of funds into abnormal accounts.

[0063] It should be noted that in the process of verifying the payment request according to the payment confirmation policy configured by the associated user, it can also be detected whether the payment amount carried in the payment request matches the corresponding payment limit in the payment confirmation policy. If yes, no processing is performed, and if no, it is determined that the payment request triggers the payment confirmation policy. Or, based on the payment confirmation policy, it is determined whether the transfer-in account of the payment amount carried in the payment request is an abnormal account. If yes, it is determined that the payment request triggers the payment confirmation policy, and if no, no processing is performed.

[0064] If it is determined that the payment request triggers the payment confirmation policy, a payment confirmation reminder is sent to the first terminal of the associated user, and the identity authentication information of the target user is obtained and the payment processing of the target transaction is performed according to the payment confirmation instruction submitted by the associated user in response to the payment confirmation reminder.

[0065] In addition, the associated user who confirms the payment to the target user may be one or more, i.e. the associated user who establishes a payment authorization relationship with the target user may be one or more. The above describes the process of associated verification and payment processing when the associated user is one. The following will take the first associated user and the second associated user as an example to describe the process of associated verification and payment processing when the associated user is more in detail.

[0066] (1) Read the payment authorization record of the target user, and filter the authorization record with the authorization state being the authorized valid state.

[0067] (2) If the first confirmation policy configured by the first associated user and the second confirmation policy configured by the second associated user are consistent in the authorization record, the corresponding payment parameters carried in the payment request are associated verified according to the payment elements in the first confirmation policy or the second confirmation policy.

[0068] For example, the first confirmation policy configured by the first associated user in the authorization record is "single consumption limit of 1000 yuan", and the second confirmation policy configured by the second associated user is also "single consumption limit of 1000 yuan", which indicates that the first confirmation policy configured by the first associated user and the second confirmation policy configured by the second associated user are the same. The corresponding payment parameters (payment amount of 1200 yuan) carried in the payment request can be associated and verified according to the payment elements (single consumption limit of 1000 yuan) in the payment confirmation policy.

[0069] Accordingly, according to the first payment confirmation instruction submitted by the first associated user and the second payment confirmation instruction submitted by the second associated user, the identity authentication information of the target user is obtained and the target transaction is processed for payment.

[0070] Alternatively, if the first payment confirmation instruction of the first associated user or the second payment confirmation instruction of the second associated user is received, the identity authentication information of the target user is obtained and verified based on the received payment confirmation instruction. After verification, the target transaction is processed for payment.

[0071] In actual application, in order to prevent the target user from logging in to the associated user account to agree to his own payment request, the identity needs to be verified during the process of submitting the payment confirmation instruction by the associated user in response to the payment confirmation reminder, to ensure that the user performing the payment confirmation is the associated user himself. Specifically, the first terminal of the associated user performs the following operations during the process of submitting the payment confirmation instruction in response to the payment confirmation reminder:

[0072] The identity verification page returned by the receiving server after the payment confirmation reminder is triggered is received;

[0073] The biological feature information is collected through the information collection interface configured in the identity verification page.

[0074] Correspondingly, the server performs the following operations during the process of obtaining the payment confirmation instruction sent by the first terminal in response to the payment confirmation reminder:

[0075] If it is detected that the payment confirmation reminder is triggered, the identity verification page is returned to the first terminal;

[0076] The biological feature information collected by the first terminal through the information collection interface configured in the identity verification page is obtained;

[0077] It is judged whether the biological feature information matches the biological feature information of the associated user or not;

[0078] If matched, it is determined that the associated user submits the payment confirmation instruction in response to the payment confirmation reminder;

[0079] If not matched, no processing is performed.

[0080] The biometric information includes fingerprint information, face image information, and iris information.

[0081] (3) If the first confirmation policy configured by the first associated user in the authorization record is inconsistent with the second confirmation policy configured by the second associated user, the payment request is associatedly verified according to the first confirmation policy, and the payment request is associatedly verified based on the second confirmation policy.

[0082] For example, the first confirmation policy configured by the first associated user in the authorization record is "single consumption limit of 1000 yuan", and the second confirmation policy configured by the second associated user is "single consumption limit of 1500 yuan", which means that the first confirmation policy configured by the first associated user is different from the second confirmation policy configured by the second associated user. The payment amount (1600 yuan) carried in the payment request is associatedly verified according to the first confirmation policy "single consumption limit of 1000 yuan", and the payment amount (1600 yuan) carried in the payment request is associatedly verified according to the second confirmation policy "single consumption limit of 1500 yuan", so as to adapt to diversified payment scenarios.

[0083] Correspondingly, if the payment request triggers any one of the first confirmation policy and the second confirmation policy, a payment confirmation reminder is sent to the associated user terminal corresponding to the triggered payment request, and a payment confirmation instruction returned by the payment confirmation reminder is received. The identity authentication information of the target user is obtained based on the received payment confirmation instruction, and the target transaction is paid.

[0084] If the payment request triggers the first confirmation policy and the second confirmation policy, a payment confirmation reminder is sent to the terminal device of the first associated user and the second associated user. After receiving the first payment confirmation instruction of the first associated user and the second payment confirmation instruction sent by the terminal device of the second associated user, the identity authentication information of the target user is obtained and the target transaction is paid. Or, if the first payment confirmation instruction submitted by the first associated user or the second payment confirmation instruction submitted by the second associated user is detected, the identity authentication information of the target user is obtained based on the detected payment confirmation instruction and verified. After verification, the target transaction is paid.

[0085] If the payment request does not trigger the first confirmation policy and the second confirmation policy, the identity authentication information of the target user is directly obtained and the target transaction is paid.

[0086] It should be noted that in order to flexibly adjust the payment confirmation, such as reasonable arrangement of the user's funds after completing the education and participating in the work. In this case, the payment authorization relationship can be released, or after the time reaches the authorization period, the payment authorization relationship can also be released.

[0087] Specifically, in the process of canceling the payment authorization relationship, it is detected whether the authorization period recorded in the payment authorization record is expired; if yes, the payment authorization relationship between the associated user and the target user is canceled, and if no, no processing is performed.

[0088] Alternatively,

[0089] receiving the cancel request for the payment authorization relationship sent by the first terminal;

[0090] sending the cancel application for the payment authorization relationship to the second terminal;

[0091] if the cancel instruction of the cancel application submitted by the second terminal is received, canceling the payment authorization relationship between the associated user and the target user based on the cancel instruction;

[0092] Alternatively,

[0093] receiving the cancel request for the payment authorization relationship sent by the second terminal;

[0094] sending the cancel application for the payment authorization relationship to the first terminal;

[0095] if the cancel instruction of the cancel application submitted by the first terminal is received, canceling the payment authorization relationship between the associated user and the target user based on the cancel instruction;

[0096] Here, canceling the payment authorization relationship specifically means changing the authorization state recorded in the payment authorization record to an authorization invalid state.

[0097] It should be noted that in the case where the authorization period recorded in the payment authorization record is expired, after the payment authorization relationship between the associated user and the target user is canceled, a cancel reminder of the payment authorization relationship is sent to the first terminal and the second terminal to inform that the payment authorization relationship has been canceled.

[0098] The payment authorization method provided in the embodiment is applied to the authorization relationship establishment scenario, and the payment confirmation processing method provided in the embodiment is further described, as shown in Figure 2 The payment confirmation processing method applied to the authorization relationship establishment scenario specifically includes steps S202 to S226.

[0099] Step S202, receiving the payment authorization application submitted by the associated user triggering the authorization control of the first terminal of the associated user.

[0100] Step S204, reading the user list of the associated user.

[0101] Step S206, returning the user list to the first terminal.

[0102] The first terminal obtains the target user selected by the associated user from the user list for authorization invitation, as well as the payment confirmation policy configured for the target user, and sends it to the server.

[0103] Step S208: Receive the target user for the authorization invitation and the payment confirmation strategy sent by the first terminal.

[0104] Step S210: Send an authorization invitation message carrying the payment confirmation strategy to the target user's second terminal.

[0105] Step S212: Receive a confirmation instruction for the authorization invitation information sent by the second terminal.

[0106] Step S214: Grant payment confirmation permissions for the target user in the target transaction to the associated user.

[0107] Step S216: Mark the authorization status as valid.

[0108] Step S218: Generate and store a payment authorization record based on the payment confirmation permission, authorization validity status, and payment confirmation policy.

[0109] Step S220: Check whether the authorization period recorded in the payment authorization record has expired;

[0110] If so, proceed to steps S222 to S226;

[0111] If not, no action will be taken.

[0112] Step S222: Release the payment authorization relationship between the associated user and the target user.

[0113] Specifically, canceling the payment authorization relationship here means changing the authorization status recorded in the payment authorization record to an authorization invalidation status.

[0114] Step S224: Return a notification to the first terminal regarding the cancellation of the payment authorization relationship.

[0115] Step S226: Return a notification to the second terminal regarding the cancellation of the payment authorization relationship.

[0116] It should be noted that during the execution of steps S224 and S226, the notification of the cancellation of the payment authorization relationship can be returned to the second terminal first, and then the notification of the cancellation of the payment authorization relationship can be returned to the first terminal. Therefore, the execution order of steps S224 and S226 is not limited here.

[0117] Further, a release request for the payment authorization relationship sent by the first terminal can be received, a release application for the payment authorization relationship can be sent to the second terminal, and if a release instruction of the release application submitted by the second terminal is received, the payment authorization relationship between the associated user and the target user can be released based on the release instruction.

[0118] Alternatively, a release request for the payment authorization relationship sent by the second terminal can be received, a release application for the payment authorization relationship can be sent to the first terminal, and if a release instruction of the release application submitted by the first terminal is received, the payment authorization relationship between the associated user and the target user can be released based on the release instruction.

[0119] To sum up, the payment authorization method provided by the embodiment first receives a payment authorization application submitted by a first terminal of an associated user through triggering an authorization control of the associated user, reads a user list of the associated user, and returns to the first terminal to obtain a target user selected by the associated user from the user list for authorization invitation and a payment confirmation strategy configured for the target user sent by the first terminal;

[0120] Secondly, authorization invitation information carrying the payment confirmation strategy is sent to a second terminal of the target user, and a confirmation instruction of the authorization invitation information sent by the second terminal is received;

[0121] Finally, a payment authorization relationship between the associated user and the target user is established based on the confirmation instruction, so as to perform multiple payment verifications on the target user in a target transaction according to the payment confirmation strategy, detect whether an authorization period recorded in a payment authorization record is expired, if yes, release the payment authorization relationship between the associated user and the target user, and if not, do not process; or, a release request for the payment authorization relationship sent by the first terminal is received, a release application for the payment authorization relationship is sent to the second terminal, and if a release instruction of the release application submitted by the second terminal is received, the payment authorization relationship between the associated user and the target user is released based on the release instruction.

[0122] Through the establishment of the payment authorization relationship, the payment security and the fund security of the user are ensured, the fund loss is avoided, and the user is helped to use the Internet payment reasonably; through the introduction of the payment confirmation strategy, the consumption granularity is reduced, and the diversified payment scene demand is met.

[0123] The present specification provides an embodiment of a payment confirmation processing method:

[0124] Referring to Figure 3 which shows a payment confirmation processing method processing flowchart provided by the embodiment, referring to Figure 4 which shows a payment confirmation processing method processing timing diagram applied to an old user scene provided by the embodiment, referring to Figure 5Fig. 3 shows a processing timing diagram of the payment confirmation processing method applied to the youth user scenario according to the embodiment.

[0125] With reference to Figure 3 The payment confirmation processing method provided by the embodiment is applied to a server and specifically includes steps S302 to S308.

[0126] In step S302, a payment request submitted by a second terminal of a target user for a target transaction is received.

[0127] The payment confirmation processing method provided by the embodiment, in the process of payment of the target user for the target transaction, acquires the payment request submitted by the target user, finds a payment confirmation strategy configured by an associated user in a payment authorization relationship with the target user, and performs associated verification on the payment request based on the payment confirmation strategy. If the payment request triggers the payment confirmation strategy, a payment confirmation reminder is sent to the associated user. After receiving the payment confirmation instruction for the payment confirmation reminder, the identity authentication information of the target user is acquired and the target transaction is processed for payment, so as to ensure the payment security and the fund security of the target user, avoid fund loss, and help the target user to use the Internet payment reasonably. By introducing the payment confirmation strategy, the consumption granularity is reduced, and the diversified payment scene demand is met.

[0128] The payment confirmation strategy refers to a strategy for one user to perform payment verification on a payment request initiated by another user in the payment process, such as a single consumption limit. For example, the payment confirmation strategy configured by the associated user is "single consumption limit of 1000 yuan", and the target user sets the transfer amount to 1200 yuan when transferring. The payment request of the target user triggers the payment confirmation strategy, and the associated user needs to confirm the payment request of the target user.

[0129] The associated verification refers to verifying the payment request initiated by another user in the payment process according to the payment confirmation strategy constructed by one user; or verifying the payment request initiated by one user in the payment process according to the payment confirmation strategy constructed by multiple users to one user.

[0130] It should be noted that in the process of associated verification, the associated user in a payment authorization relationship with the target user can be one or multiple, so the payment confirmation strategy configured for the target user can be one or multiple, and the process of associated verification of the payment request of the target user according to the payment confirmation strategy can be performed once or multiple times. Similarly, in the process of submitting the payment confirmation instruction, the associated user can be one or multiple, and the payment confirmation can be performed once or multiple times.

[0131] In actual application, in the process of using the Internet, the old users cannot distinguish the safety of the Internet operation due to unfamiliarity with the Internet, resulting in the generation of network fraud, and the young users or college student users lack correct consumption concept, resulting in uncontrolled Internet payment. In this case, the corresponding consumption limit can be set by the family members of the old users, the family members of the young users, the family members of the college student users or the family members of other users, the payment to the abnormal account is confirmed, which helps them to better use the Internet payment, helps the old users to prevent network fraud, guides the reasonable consumption of the young users and establishes correct consumption concept. In this process, the old users, young users, college student users or other users who face Internet fraud or uncontrolled Internet payment are target users, the terminal equipment used by the target users is the second terminal, and the associated users who set the consumption limit for the target users, confirm the payment to the abnormal account, help the target users to prevent Internet fraud or guide the reasonable consumption of the target users are the associated users, and the terminal equipment used by the associated users is the first terminal.

[0132] In a specific implementation, in the process of the target user paying for the target transaction, the payment control submits a payment instruction, the second terminal generates a payment request according to the payment instruction and sends it to the server, and the server receives the payment request submitted by the second terminal for the target transaction.

[0133] In step S304, according to the payment confirmation strategy configured by the associated user for the target user, the payment request is associated with the verification.

[0134] The payment authorization relationship described in this embodiment includes a dependent relationship that the payment request of the target user for the target transaction is verified and confirmed by the payment confirmation strategy configured by the associated user for the target user. It should be noted that the payment authorization relationship is not limited between the associated user and the target user, and the payment authorization relationship can be established between any two users of the registered application. Therefore, the user who establishes the payment authorization relationship with the associated user can be one or more, and the user who establishes the payment authorization relationship with the target user can be one or more. Wherein, the registered application refers to the application program running the target transaction.

[0135] In an optional implementation provided by the embodiment, the payment authorization relationship between the associated user and the target user is established by the following method:

[0136] The authorization invitation information carrying the payment confirmation strategy is sent to the second terminal, and the payment authorization relationship between the associated user and the target user is established according to the confirmation instruction sent by the second terminal.

[0137] In the specific payment authorization relationship establishment process, the server performs the following operations: opening payment confirmation permission for the target user in the target transaction for the associated user, and marking the authorization state as an authorized valid state; generating and storing a payment authorization record according to the payment confirmation permission, the authorized valid state, and the payment confirmation policy.

[0138] Specifically, in order to realize the payment confirmation of the associated user to the target user in the payment process, the consent of the target user is obtained, the authorization invitation information carrying the payment confirmation policy is sent to the second terminal of the target user, if the confirmation instruction of the authorization invitation information returned by the second terminal is received, the payment confirmation permission for the target user in the target transaction is opened for the associated user, the authorization state is marked as an authorized valid state, and a payment authorization record is generated and stored.

[0139] Among them, the payment authorization record is shown in Table 2 as follows:

[0140]

[0141] Table 2

[0142] It should be noted that the user identifier in the target user identifier and the associated user identifier can be a user account, or a user identity identifier code, etc.; in the process of establishing a payment authorization relationship, a payment authorization record can also be created according to one of the payment confirmation permission and the authorized valid state and the payment confirmation policy.

[0143] In actual implementation, after receiving the payment request submitted by the second terminal of the target user for the target transaction, the associated user establishing a payment authorization relationship with the target user and the payment confirmation policy configured for the target user are read in the payment authorization record, and the payment request is associated with the read payment confirmation policy. Verification is performed to determine whether the payment request triggers the payment confirmation policy.

[0144] In actual application, when the target user uses the youth mode for Internet payment, the consumption cost can be controlled to a certain extent, but the youth mode cannot perform the payment problem exceeding the limit, and the consumption granularity of the youth mode is large, which cannot meet the needs of some payment scenarios, such as parents managing the amount of children in certain consumption (such as games), preventing children from buying goods exceeding the payment ability (such as luxury goods), and the elderly user cannot distinguish abnormal accounts. For this purpose, in order to meet the needs of diversified payment scenarios, the payment confirmation policy of setting the consumption limit for the youth user or the elderly user and the payment confirmation when paying to the abnormal account is set, and the payment request is associated with the payment confirmation policy. Verification is performed.

[0145] In an optional implementation of the embodiment, in the process of performing multiple payment verification on the payment request according to the payment confirmation policy configured by the associated user, the following operations are performed:

[0146] whether the payment amount carried in the payment request matches the corresponding payment limit in the payment confirmation policy;

[0147] If not, it is determined that the payment request triggers the payment confirmation policy, and if yes, no processing is performed.

[0148] And, based on the payment confirmation policy, it is determined whether the transfer-in account of the payment amount carried in the payment request is an abnormal account.

[0149] If not, no processing is performed, and if yes, it is determined that the payment request triggers the payment confirmation policy.

[0150] For example, the payment amount carried in the payment request is 1200 yuan, and the corresponding single-consumption limit in the payment confirmation policy is 1000 yuan. The payment amount exceeds the single-consumption limit, so the payment request triggers the corresponding single-consumption limit in the payment confirmation policy. For another example, the payment amount carried in the payment request is transferred to an abnormal account, and the payment confirmation policy requires the associated user to confirm the payment. Therefore, the payment request triggers the corresponding transfer-in abnormal account in the payment confirmation policy. In addition, the payment confirmation policy also includes: daily / monthly consumption limit, limit for different consumption categories (game, clothing, catering), and interception of funds transferred to abnormal accounts.

[0151] It should be noted that, in the process of performing associated verification on the payment request according to the payment confirmation policy configured by the associated user, it can also be detected whether the payment amount carried in the payment request matches the corresponding payment limit in the payment confirmation policy; if yes, no processing is performed, and if not, it is determined that the payment request triggers the payment confirmation policy; or based on the payment confirmation policy, it is determined whether the transfer-in account of the payment amount carried in the payment request is an abnormal account; if yes, it is determined that the payment request triggers the payment confirmation policy, and if not, no processing is performed.

[0152] In addition, the user who performs payment confirmation on the target user can be one or more, that is, the associated user who establishes a payment authorization relationship with the target user can be one or more. The above describes the process of associated verification when the associated user is one, and the following describes the process of associated verification when the associated user includes a first associated user and a second associated user.

[0153] In the first optional implementation provided by the embodiment, in the process of performing multiple payment verification on the payment request according to the payment confirmation strategies configured by the associated users, the following operation is performed:

[0154] read the payment authorization records for the target user, and filter the authorization records with the authorized valid state;

[0155] If the first confirmation strategy configured by the first associated user and the second confirmation strategy configured by the second associated user are consistent, the corresponding payment parameters carried in the payment request are associatedly verified according to the payment elements in the first confirmation strategy or the second confirmation strategy.

[0156] In the second optional implementation provided by the embodiment, in the process of performing multiple payment verification on the payment request according to the payment confirmation strategies configured by the associated users, the following operation is performed:

[0157] read the payment authorization records for the target user, and filter the authorization records with the authorized valid state;

[0158] If the first confirmation strategy configured by the first associated user and the second confirmation strategy configured by the second associated user are inconsistent, the payment request is associatedly verified according to the first confirmation strategy, and the payment request is associatedly verified based on the second confirmation strategy.

[0159] Specifically, since the payment authorization record of the payment authorization relationship is not deleted in the embodiment, but the authorization state is changed from the authorized valid state to the authorized invalid state, in the read payment authorization records for the target user, the authorization records with the authorized valid state can be filtered;

[0160] If the first confirmation strategy configured by the first associated user and the second confirmation strategy configured by the second associated user are the same, the corresponding payment parameters carried in the payment request are associatedly verified according to the payment elements in the first confirmation strategy or the second confirmation strategy, or the payment request is associatedly verified according to the first confirmation strategy, and the payment request is associatedly verified based on the second confirmation strategy, to adapt to diversified payment verification scenarios;

[0161] If the first confirmation strategy configured by the first associated user and the second confirmation strategy configured by the second associated user are different, after the payment request is associatedly verified according to the first confirmation strategy, the payment request needs to be associatedly verified based on the second confirmation strategy.

[0162] For example, the first confirmation policy configured by the first associated user in the authorization record is "single consumption limit of 1000 yuan", and the second confirmation policy configured by the second associated user is also "single consumption limit of 1000 yuan", which indicates that the first confirmation policy configured by the first associated user is the same as the second confirmation policy configured by the second associated user. The corresponding payment parameter (payment amount of 1200 yuan) carried in the payment request can be associated with the payment element (single consumption limit of 1000 yuan) in the payment confirmation policy for verification.

[0163] For example, the first confirmation policy configured by the first associated user in the authorization record is "single consumption limit of 1000 yuan", and the second confirmation policy configured by the second associated user is also "single consumption limit of 1000 yuan", which indicates that the first confirmation policy configured by the first associated user is the same as the second confirmation policy configured by the second associated user. The corresponding payment parameter (payment amount of 1200 yuan) carried in the payment request can be associated with the payment element (single consumption limit of 1000 yuan) in the payment confirmation policy for verification.

[0164] It should be noted that in the process of associated verification of the payment request according to the payment confirmation policy configured by the associated user, the server can also perform the following operations:

[0165] Read the payment authorization record for the target user, and filter the authorization records with the authorization state being the authorized valid state;

[0166] If the first confirmation policy configured by the first associated user in the authorization record is consistent with the second confirmation policy configured by the second associated user, the corresponding payment parameter carried in the payment request is associated with the payment element in the first confirmation policy or the second confirmation policy for verification;

[0167] If the first confirmation policy configured by the first associated user in the authorization record is inconsistent with the second confirmation policy configured by the second associated user, the payment request is associated with the first confirmation policy for verification, and the payment request is associated with the second confirmation policy for verification.

[0168] Step S306, if the associated verification result is that the payment request triggers the payment confirmation policy, a payment confirmation reminder is sent to the first terminal of the associated user.

[0169] In the payment confirmation strategy configured by the associated user in association with the target user establishing a payment authorization relationship, on the basis of the associated verification of the payment request, if the payment verification result is that the payment request triggers the payment confirmation strategy, a payment confirmation reminder for the payment request is sent to the first terminal of the associated user to enable the associated user to perform payment confirmation; if the payment verification result is that the payment request does not trigger the payment confirmation strategy, the payment processing is directly performed on the target transaction.

[0170] In a specific implementation, in the case where the associated user in association with the target user establishing a payment authorization relationship is one, the payment confirmation reminder is sent to the first terminal of the associated user.

[0171] In the case where the associated user in association with the target user establishing a payment authorization relationship includes a first associated user and a second associated user, according to the first optional implementation, if the payment request triggers the payment confirmation strategy, the payment confirmation reminder is sent to the terminal device of the first associated user and the terminal device of the second associated user; or according to the payment confirmation priority recorded in the payment authorization record, the payment confirmation reminder is first sent to the terminal device of the first associated user, if the first payment confirmation instruction sent by the terminal device of the first associated user is received, the payment confirmation reminder is not sent to the terminal device of the second associated user, if the first payment confirmation instruction sent by the terminal device of the first associated user is not received, the payment confirmation reminder is sent to the terminal device of the second associated user to obtain the second payment confirmation instruction.

[0172] According to the second optional implementation, if the payment request triggers any one of the first confirmation strategy and the second confirmation strategy, the payment confirmation reminder is sent to the terminal device of the associated user corresponding to the triggered payment request confirmation strategy to obtain the payment confirmation instruction; if the payment request triggers both the first confirmation strategy and the second confirmation strategy, the payment confirmation reminder is sent to the terminal device of the first associated user and the terminal device of the second associated user; if the payment request does not trigger the first confirmation strategy and the second confirmation strategy, the payment processing is directly performed on the target transaction.

[0173] In step S308, according to the payment confirmation instruction submitted by the associated user for the payment confirmation reminder, the identity authentication information of the target user is obtained and the payment processing is performed on the target transaction.

[0174] According to the payment confirmation strategy, if the payment verification result is that the payment request triggers the payment confirmation strategy, a payment confirmation reminder is sent to the first terminal of the associated user, the first terminal sends a payment confirmation instruction submitted by the associated user for the payment confirmation reminder to the server, and correspondingly, the server receives the payment confirmation instruction of the payment confirmation reminder sent by the first terminal, and according to the payment confirmation instruction, identity authentication information of the target user is obtained for verification, and after the verification is passed, the target transaction is processed.

[0175] In actual application, in order to prevent the target user from logging in the associated user account to agree to the payment request of himself / herself, the identity needs to be verified in the process that the associated user submits the payment confirmation instruction for the payment confirmation reminder, so as to ensure that the user who performs the payment confirmation is the associated user himself / herself. Specifically, the first terminal performs the following operations in the process that the payment confirmation instruction is submitted for the payment confirmation reminder:

[0176] receiving an identity verification page returned by the server after the payment confirmation reminder is triggered;

[0177] acquiring biological feature information through an information acquisition interface configured in the identity verification page.

[0178] Correspondingly, in an optional embodiment provided by the present embodiment, the server performs the following operations in the process that the payment confirmation instruction sent by the first terminal is acquired for the payment confirmation reminder:

[0179] if it is detected that the payment confirmation reminder is triggered, an identity verification page is returned to the first terminal;

[0180] acquiring biological feature information collected by the first terminal through an information acquisition interface configured in the identity verification page;

[0181] judging whether the biological feature information matches biological feature information of the associated user;

[0182] if the biological feature information matches the biological feature information of the associated user, it is determined that the payment confirmation instruction is submitted by the associated user for the payment confirmation reminder;

[0183] if the biological feature information does not match the biological feature information of the associated user, no processing is performed.

[0184] The biological feature information includes fingerprint information, face image information and iris information.

[0185] In actual implementation, after the associated user submits a payment confirmation instruction for the payment confirmation reminder, the first terminal sends the payment confirmation instruction to the server, the server obtains the identity authentication information of the target user according to the received payment confirmation instruction for verification, and after the verification is passed, the payment processing is performed for the target transaction. The payment processing processes corresponding to the case where the associated user is one and the case where the associated user is multiple are described in detail below.

[0186] (1) The associated user is one

[0187] In the case where the associated user who establishes the payment authorization relationship with the target user is one, the payment confirmation reminder is sent to the first terminal of the associated user, if the payment confirmation instruction for the payment confirmation reminder sent by the first terminal is obtained, the identity authentication information of the target user is obtained according to the payment confirmation instruction for verification, and after the verification is passed, the payment processing is performed for the target transaction; the identity authentication information here includes the iris information, the fingerprint information, the face image of the target user, and the payment key input by the target user.

[0188] (2) The associated user is multiple (taking the case where the first associated user and the second associated user are included as an example)

[0189] For the first optional implementation provided above, the first confirmation strategy configured by the first associated user in the authorization record is consistent with the second confirmation strategy configured by the second associated user, and the corresponding payment parameters carried in the payment request are associated and verified according to the payment elements in the first confirmation strategy or the second confirmation strategy;

[0190] In the case where the associated verification result is that the payment request triggers the payment confirmation strategy:

[0191] a. The payment confirmation reminder is sent to the terminal device of the first associated user and the terminal device of the second associated user, the identity authentication information of the target user is obtained according to the first payment confirmation instruction submitted by the first associated user and the second payment confirmation instruction submitted by the second associated user, and the payment processing is performed for the target transaction; in addition, if the first payment confirmation instruction of the first associated user or the second payment confirmation instruction of the second associated user is detected, the identity authentication information of the target user is obtained based on the detected payment confirmation instruction and is verified; after the verification is passed, the payment processing is performed for the target transaction.

[0192] b. According to the payment confirmation priority recorded in the payment authorization record, the payment confirmation reminder is first sent to the terminal device of the first associated user, if the first payment confirmation instruction sent by the terminal device of the first associated user is received, the identity authentication information of the target user is obtained and the payment processing is performed on the target transaction, and the payment confirmation reminder is no longer sent to the terminal device of the second associated user; if the first payment confirmation instruction sent by the terminal device of the first associated user is not received, the payment confirmation reminder is further sent to the terminal device of the second associated user, and according to the second payment confirmation instruction sent by the terminal device of the second associated user in response to the payment confirmation reminder, the identity authentication information of the target user is obtained and the payment processing is performed on the target transaction.

[0193] For the second optional implementation provided above, the first confirmation strategy configured by the first associated user in the authorization record is inconsistent with the second confirmation strategy configured by the second associated user, the payment request is associated with the verification according to the first confirmation strategy, and the payment request is associated with the verification based on the second confirmation strategy.

[0194] a. If the payment request triggers any one of the first confirmation strategy and the second confirmation strategy, the payment confirmation reminder is sent to the terminal device of the associated user corresponding to the triggered payment request, and the identity authentication information of the target user is obtained and the payment processing is performed on the target transaction according to the received payment confirmation instruction.

[0195] b. If the payment request triggers both the first confirmation strategy and the second confirmation strategy, the payment confirmation reminder is sent to the terminal device of the first associated user and the terminal device of the second associated user; the identity authentication information of the target user is obtained and the payment processing is performed on the target transaction according to the first payment confirmation instruction submitted by the first associated user and the second payment confirmation instruction submitted by the second associated user; in addition, the first payment confirmation instruction of the first associated user or the second payment confirmation instruction of the second associated user can be detected, and the identity authentication information of the target user is obtained and verified based on the detected payment confirmation instruction, and the payment processing is performed on the target transaction after the identity authentication information verification is passed.

[0196] c. If the payment request does not trigger the first confirmation strategy and the second confirmation strategy, the identity authentication information of the target user is directly obtained for verification, and the payment processing is performed on the target transaction after the verification is passed.

[0197] In order to flexibly adjust the payment confirmation, such as reasonable arrangement of the funds of the young user after completing the study and participating in the work, the payment authorization relationship can be released after the associated user confirms the target transaction of the target user within a certain time, or the payment authorization relationship can also be released after the time reaches the authorization period. In an optional implementation provided in the embodiment, the payment authorization relationship is released by the following manner:

[0198] detecting whether the authorization period recorded in the payment authorization record is expired;

[0199] if yes, releasing the payment authorization relationship between the associated user and the target user, and if no, not processing;

[0200] alternatively,

[0201] receiving the release request for the payment authorization relationship sent by the first terminal;

[0202] sending the release application for the payment authorization relationship to the second terminal;

[0203] if the release instruction of the release application submitted by the second terminal is received, releasing the payment authorization relationship between the associated user and the target user based on the release instruction;

[0204] alternatively,

[0205] receiving the release request for the payment authorization relationship sent by the second terminal;

[0206] sending the release application for the payment authorization relationship to the first terminal;

[0207] if the release instruction of the release application submitted by the first terminal is received, releasing the payment authorization relationship between the associated user and the target user based on the release instruction.

[0208] Here, releasing the payment authorization relationship specifically means changing the authorization state recorded in the payment authorization record to an authorization invalid state.

[0209] It should be noted that in the case where the authorization period recorded in the payment authorization record is expired, after releasing the payment authorization relationship between the associated user and the target user, the first terminal and the second terminal are sent a release reminder of the payment authorization relationship to inform that the payment authorization relationship has been released.

[0210] The payment confirmation processing method provided in the present embodiment is further described below by taking the application of the payment confirmation processing method in the elderly user scenario as an example, referring to Figure 4 The payment confirmation processing method applied in the elderly user scenario specifically includes the following steps.

[0211] Step S402, receiving the payment request submitted by the second terminal of the elderly user for the target transaction.

[0212] Step S404, reading the family members establishing the payment authorization relationship with the elderly user and the configured payment confirmation strategy.

[0213] The payment confirmation strategy is that, when the old user makes a payment, if the transfer-in account of the payment amount is an abnormal account, the family member makes an association confirmation.

[0214] In step S406, whether the transfer-in account of the payment amount carried in the payment request is an abnormal account is judged based on the payment confirmation strategy.

[0215] If yes, steps S408 to S410 and S418 are executed.

[0216] If no, no processing is performed.

[0217] In step S408, the payment request triggers the payment confirmation strategy.

[0218] In step S410, a payment confirmation reminder is sent to the first terminal of the family member.

[0219] After the payment confirmation reminder is triggered, the first terminal displays an identity verification page, acquires biological feature information through an information acquisition interface configured in the identity verification page, and uploads the acquired biological feature information to the server.

[0220] In step S418, whether the biological feature information uploaded by the first terminal matches the biological feature information of the family member is judged.

[0221] If yes, steps S420 to S424 and steps S428 to S430 are executed.

[0222] If no, no processing is performed.

[0223] In step S420, it is determined that the family member submits a payment confirmation instruction for the payment confirmation reminder, and the payment confirmation instruction is synchronized to the second terminal.

[0224] The second terminal acquires the identity authentication information of the old user according to the payment confirmation instruction, and sends the identity authentication information to the server.

[0225] In step S422, the identity authentication information sent by the second terminal is verified.

[0226] Here, the identity authentication information includes iris information, fingerprint information, a face image, and a payment key input by the old user.

[0227] In step S424, after the verification passes, the target transaction is processed.

[0228] The first terminal sends a release request for the payment authorization relationship to the server.

[0229] In step S428, the second terminal is returned a release application for the payment authorization relationship.

[0230] The second terminal submits a release instruction of the release application to the server.

[0231] At step S430, the payment authorization relationship between the family member and the elderly user is released based on the release instruction.

[0232] It should be noted that the second terminal sends a release request for the payment authorization relationship to the server. The server returns a release application for the payment authorization relationship to the first terminal. The first terminal submits a release instruction of the release application to the server. The server releases the payment authorization relationship between the family member and the elderly user based on the release instruction.

[0233] The payment confirmation processing method provided in the present embodiment is further described below by taking the application of the payment confirmation processing method provided in the present embodiment in the scenario of a young user as an example, referring to Figure 5 The payment confirmation processing method applied in the scenario of a young user specifically includes the following steps.

[0234] At step S502, a payment request submitted by a second terminal of a young user for a target transaction is received.

[0235] At step S504, a payment authorization record for the young user is read.

[0236] At step S506, in the payment authorization record, an authorization record with an authorization valid state is screened.

[0237] If the first confirmation strategy configured by the mother and the second confirmation strategy configured by the father are inconsistent, steps S508 to S510 and steps S514 to S524 are executed.

[0238] At step S508, the payment request is associated and verified according to the first confirmation strategy.

[0239] The mother and the father both establish a payment authorization relationship with the young user.

[0240] At step S510, if the payment request triggers the first confirmation strategy, a payment confirmation reminder is sent to the first terminal of the mother.

[0241] The first terminal sends a payment confirmation instruction of the payment confirmation reminder to the server.

[0242] At step S514, the payment confirmation instruction sent by the first terminal is synchronized to the second terminal.

[0243] At step S516, the payment request is associated and verified based on the second confirmation strategy.

[0244] At step S518, if the payment request triggers the second confirmation strategy, a payment confirmation reminder is sent to the third terminal of the father.

[0245] The third terminal sends a payment confirmation instruction of the payment confirmation reminder to the server.

[0246] In step S520, the payment confirmation instruction sent by the third terminal is synchronized to the second terminal.

[0247] The second terminal sends the identity authentication information of the young user to the server.

[0248] It should be noted that the payment request can also be associatedly verified according to the second confirmation strategy, and then associatedly verified according to the first confirmation strategy.

[0249] After the associated verification is completed, if the payment request triggers the first confirmation strategy and the second confirmation strategy, the payment confirmation reminder is sent to the first terminal and the third terminal at the same time, and after receiving the payment confirmation instructions of the payment confirmation reminders sent by the first terminal and the third terminal, the payment confirmation instruction is synchronized to the second terminal.

[0250] In step S522, the identity authentication information of the young user sent by the second terminal is subjected to identity verification.

[0251] In step S524, after the identity verification is passed, the target transaction is subjected to payment processing.

[0252] In summary, the payment confirmation processing method provided by the embodiment first receives a payment request submitted by a second terminal of a target user for a target transaction;

[0253] Secondly, it is detected whether the payment amount carried in the payment request matches the corresponding payment limit in the payment confirmation strategy, if yes, no processing is performed, and if no, it is determined that the payment request triggers the payment confirmation strategy; and based on the payment confirmation strategy, it is judged whether the transfer-in account of the payment amount carried in the payment request is an abnormal account, if yes, it is determined that the payment request triggers the payment confirmation strategy, and if no, no processing is performed.

[0254] Finally, in the case where the payment request triggers the payment confirmation strategy, a payment confirmation reminder is sent to a first terminal of an associated user, identity authentication information of the target user is obtained and verified according to a payment confirmation instruction submitted by the associated user for the payment confirmation reminder, and after the identity authentication information verification is passed, the target transaction is subjected to payment processing, so as to realize multiple verification and multiple payment confirmation of the transaction payment of the old user, the young user or other users, to ensure the payment safety and the fund safety of the target user, avoid fund loss, and help the target user to use the Internet payment reasonably; by introducing the payment confirmation strategy, the consumption granularity is reduced, and the diversified payment scene demand is met.

[0255] The implementation process of the payment confirmation processing method provided in the above two application scenarios of the elderly and the teenagers is executed by the server, and the implementation process of the payment confirmation processing method provided in the method embodiment below is executed by the first terminal. The two processes cooperate with each other during execution, and therefore, when reading the implementation process above, please refer to the corresponding content of the method embodiment below.

[0256] Another payment confirmation processing method embodiment provided in the specification is as follows:

[0257] Referring to Figure 6 which shows a payment confirmation processing method processing flowchart provided in the embodiment, referring to Figure 4 which shows a payment confirmation processing method processing timing diagram applied to the elderly user scenario provided in the embodiment, referring to Figure 5 which shows a payment confirmation processing method processing timing diagram applied to the teenager user scenario provided in the embodiment.

[0258] The payment confirmation processing method provided in the embodiment is applied to the first terminal, and the payment confirmation processing method provided in the method embodiment above is applied to the server. The two processes cooperate with each other during execution, and therefore, when reading the embodiment, please refer to the corresponding content of the method embodiment above, which will not be described one by one in the embodiment.

[0259] Referring to Figure 6 The payment confirmation processing method provided in the embodiment is applied to the first terminal, and specifically includes steps S602 to S606.

[0260] In step S602, a payment confirmation reminder sent by the server for a payment request of a target user in a target transaction is received.

[0261] The payment confirmation processing method provided in the embodiment receives the payment confirmation reminder sent by the server for the payment request after obtaining the payment request submitted by the target user for the payment of the target transaction, further obtains the payment confirmation instruction submitted by the associated user for the payment confirmation reminder, and sends the payment confirmation instruction to the server to process the payment of the target transaction, so as to ensure the payment safety and the fund safety of the target user, avoid the fund loss, help the target user to use the Internet payment reasonably, reduce the consumption granularity, and meet the diversified payment scene demand.

[0262] In practical applications, elderly users, due to their unfamiliarity with the internet, are unable to discern the security of online operations, leading to online fraud. Meanwhile, teenagers and university students often lack proper consumption habits, resulting in unrestrained online payments. In such cases, family members of the elderly, teenagers, university students, or other users can set corresponding spending limits and verify payments to abnormal accounts. This helps them use online payments more effectively, prevents online fraud for the elderly, and provides reasonable consumption guidance to teenagers, fostering correct consumption habits. In this process, the elderly, teenagers, university students, or other users facing online fraud or unrestrained online payments are the target users, and their devices are the secondary terminals. The users who set spending limits and verify payments to abnormal accounts for the target users, helping them prevent online fraud or providing reasonable consumption guidance, are the associated users, and their devices are the primary terminals.

[0263] In practice, when the target user makes a payment for the target transaction, the payment control is triggered to submit a payment instruction. The second terminal generates a payment request based on the payment instruction and sends it to the server. The server receives the payment request submitted by the second terminal for the target transaction and reads the associated user who has established a payment authorization relationship with the target user and the payment confirmation policy configured for the target user from the payment authorization record.

[0264] The payment request is associated with and verified according to the read payment confirmation policy to determine whether the payment request triggers the payment confirmation policy. If the payment verification result indicates that the payment request triggers the payment confirmation policy, a payment confirmation reminder is sent to the first terminal of the associated user to obtain the payment confirmation instruction submitted by the associated user. Based on the payment confirmation instruction, the identity authentication information of the target user is obtained and payment is processed for the associated user. Optionally, the payment confirmation reminder is sent after the payment request triggers the payment confirmation policy and before the identity authentication information of the target user is obtained.

[0265] The payment confirmation strategy refers to the strategy by which one user verifies the payment request initiated by another user during the payment process, such as a single transaction limit. For example, if the payment confirmation strategy set by the associated user is "single transaction limit of 1,000 yuan", and the target user sets the transfer amount to 1,200 yuan, then the target user's payment request triggers the payment confirmation strategy, and the associated user needs to confirm the target user's payment request.

[0266] The association verification refers to verifying the payment request initiated by the other party user in the payment process according to the payment confirmation policy constructed by the one party user, or verifying the payment request initiated by the one party user in the payment process according to the payment confirmation policy constructed by the multiple party users to the one party user.

[0267] The payment authorization relationship includes a reliable relationship of verifying and confirming the payment request of the target user for the target transaction according to the payment confirmation policy configured by the association user for the target user; it should be noted that the payment authorization relationship is not limited to be established between the association user and the target user, and the payment authorization relationship can be established between any two users of the registered application, so the user establishing the payment authorization relationship with the association user can be one or multiple, and similarly, the user establishing the payment authorization relationship with the target user can be one or multiple; wherein the registered application refers to an application program running the target transaction.

[0268] In addition, in the process of association verification, since the association user establishing the payment authorization relationship with the target user can be one or multiple, the payment confirmation policy configured for the target user can be one or multiple, and the process of verifying the payment request of the target user according to the payment confirmation policy can be performed once or multiple times; similarly, in the process of submitting the payment confirmation instruction, i.e. the payment confirmation, the association user can be one or multiple, and the payment confirmation can be performed once or multiple times.

[0269] In an optional implementation provided by the embodiment, the payment authorization relationship between the association user and the target user is established by the following method:

[0270] The server sends the authorization invitation information carrying the payment confirmation policy to the second terminal, and establishes the payment authorization relationship between the association user and the target user according to the confirmation instruction sent by the second terminal.

[0271] In the specific process of establishing the payment authorization relationship, the server performs the following operations: opening the payment confirmation permission of the target user in the target transaction for the association user, and marking the authorization state as an authorized valid state; generating and storing the payment authorization record according to the payment confirmation permission, the authorized valid state and the payment confirmation policy.

[0272] Specifically, in order to realize the payment confirmation of the associated user to the target user in the payment process, and obtain the consent of the target user, the server sends an authorization invitation information carrying the payment confirmation policy to the second terminal of the target user, and if the confirmation instruction of the authorization invitation information returned by the second terminal is received, the payment confirmation permission of the associated user to the target user in the target transaction is opened, the authorization state is marked as an authorized valid state, and a payment authorization record is generated and stored.

[0273] The payment authorization record is shown in Table 3 as follows:

[0274]

[0275]

[0276] Table 3

[0277] It should be noted that the user identifier in the target user identifier and the associated user identifier can be a user account or a user identity identifier code, etc. During the establishment of the payment authorization relationship, the payment authorization record can also be created according to one of the payment confirmation permission and the authorized valid state and the payment confirmation policy.

[0278] In specific implementation, after receiving the payment request submitted by the second terminal of the target user for the target transaction, the server reads the associated user establishing the payment authorization relationship with the target user and the payment confirmation policy configured for the target user in the payment authorization record, and verifies the payment request according to the read payment confirmation policy to determine whether the payment request triggers the payment confirmation policy.

[0279] In actual application, when the target user uses the youth mode for Internet payment, the consumption cost can be controlled to a certain extent, but the youth mode cannot perform the payment exceeding the limit problem, and the consumption granularity of the youth mode is large, which cannot meet the needs of some payment scenarios, such as parents managing the amount of children in certain consumption (such as games), preventing children from buying goods exceeding the payment capacity (such as luxury goods), and the elderly user cannot distinguish abnormal accounts. In view of this, in order to meet the needs of diversified payment scenarios, the payment confirmation policy of setting the consumption limit for the youth user or the elderly user and the payment confirmation when paying to the abnormal account is set, and the payment request is verified based on the payment confirmation policy.

[0280] Specifically, in the process of verifying the payment request according to the payment confirmation policy configured by the associated user, the server performs the following operations:

[0281] Detect whether the payment amount carried in the payment request matches the corresponding payment limit in the payment confirmation policy;

[0282] If no, it is determined that the payment request triggers the payment confirmation strategy, and if yes, no processing is performed.

[0283] And, based on the payment confirmation strategy, it is determined whether the transfer-in account of the payment amount carried in the payment request is an abnormal account.

[0284] If no, no processing is performed, and if yes, it is determined that the payment request triggers the payment confirmation strategy.

[0285] For example, the payment amount carried in the payment request is 1200 yuan, and the corresponding single consumption limit in the payment confirmation strategy is 1000 yuan. The payment amount exceeds the single consumption limit, so the payment request triggers the corresponding single consumption limit in the payment confirmation strategy. For another example, the payment amount carried in the payment request is transferred to an abnormal account, and the payment amount transferred to the abnormal account needs to be associated with the user for payment confirmation in the payment confirmation strategy, so the payment request triggers the corresponding transfer-in account of the abnormal account in the payment confirmation strategy.

[0286] It should be noted that in the process of performing associated verification on the payment request according to the payment confirmation strategy configured by the associated user, the server can also detect whether the payment amount carried in the payment request matches the corresponding payment limit in the payment confirmation strategy; if yes, no processing is performed, and if no, it is determined that the payment request triggers the payment confirmation strategy; or based on the payment confirmation strategy, it is determined whether the transfer-in account of the payment amount carried in the payment request is an abnormal account; if yes, it is determined that the payment request triggers the payment confirmation strategy, and if no, no processing is performed.

[0287] In addition, the user who performs payment confirmation on the target user can be one or more, i.e., the associated user who establishes a payment authorization relationship with the target user can be one or more. The above describes the process of associated verification when the associated user is one, and the following describes the process of associated verification when the associated user includes a first associated user and a second associated user in detail.

[0288] The first kind:

[0289] Read the payment authorization record for the target user, and filter the authorization record with an authorized valid state.

[0290] If the first confirmation strategy configured by the first associated user and the second confirmation strategy configured by the second associated user in the authorization record are consistent, the corresponding payment parameters carried in the payment request are associated and verified according to the payment elements in the first confirmation strategy or the second confirmation strategy.

[0291] The second kind:

[0292] read the payment authorization record for the target user, and filter the authorization record with an authorized valid state;

[0293] If the first confirmation strategy configured by the first associated user in the authorization record is inconsistent with the second confirmation strategy configured by the second associated user, the server performs associated verification on the payment request according to the first confirmation strategy, and performs associated verification on the payment request based on the second confirmation strategy.

[0294] Specifically, since the server does not delete the payment authorization record in the process of canceling the payment authorization relationship, but changes the authorization state from the authorized valid state to the authorized invalid state, in the read payment authorization record for the target user, the server can filter the authorization record with the authorized valid state;

[0295] If the first confirmation strategy configured by the first associated user in the authorization record is the same as the second confirmation strategy configured by the second associated user, the server performs associated verification on the corresponding payment parameter carried in the payment request according to the payment element in the first confirmation strategy or the second confirmation strategy, or the server performs associated verification on the payment request according to the first confirmation strategy, and performs associated verification on the payment request based on the second confirmation strategy, to adapt to diversified payment verification scenarios.

[0296] If the first confirmation strategy configured by the first associated user in the authorization record is different from the second confirmation strategy configured by the second associated user, the server needs to perform associated verification on the payment request based on the second confirmation strategy after performing associated verification on the payment request according to the first confirmation strategy.

[0297] For example, the first confirmation strategy configured by the first associated user in the authorization record is "single consumption limit of 1000 yuan", and the second confirmation strategy configured by the second associated user is also "single consumption limit of 1000 yuan", which means that the first confirmation strategy configured by the first associated user is the same as the second confirmation strategy configured by the second associated user, and the server can perform associated verification on the corresponding payment parameter (payment amount of 1200 yuan) carried in the payment request according to the payment element (single consumption limit of 1000 yuan) in the payment confirmation strategy.

[0298] For another example, the first confirmation policy configured by the first associated user in the authorization record is "single consumption limit of 1000 yuan", and the second confirmation policy configured by the second associated user is also "single consumption limit of 1500 yuan", which indicates that the first confirmation policy configured by the first associated user is different from the second confirmation policy configured by the second associated user. The server can perform associated verification on the payment amount (1600 yuan) carried in the payment request according to the first confirmation policy "single consumption limit of 1000 yuan", and perform associated verification on the payment amount (1600 yuan) carried in the payment request according to the second confirmation policy "single consumption limit of 1500 yuan".

[0299] It should be noted that in the process of performing associated verification on the payment request according to the payment confirmation policy configured by the associated user, the server can also perform the following operations:

[0300] read the payment authorization record for the target user, and filter the authorization record with the authorization state being the authorized valid state;

[0301] If the first confirmation policy configured by the first associated user in the authorization record is consistent with the second confirmation policy configured by the second associated user, the corresponding payment parameter carried in the payment request is verified according to the payment elements in the first confirmation policy or the second confirmation policy;

[0302] If the first confirmation policy configured by the first associated user in the authorization record is inconsistent with the second confirmation policy configured by the second associated user, the payment request is verified according to the first confirmation policy, and the payment request is verified based on the second confirmation policy.

[0303] On the basis of the above-mentioned server performing associated verification on the payment request according to the payment confirmation policy configured by the associated user establishing a payment authorization relationship with the target user, if the associated verification result is that the payment request triggers the payment confirmation policy, the server sends a payment confirmation reminder for the payment request to the first terminal of the associated user, and correspondingly, the first terminal receives the payment confirmation reminder sent by the server; if the associated verification result is that the payment request does not trigger the payment confirmation policy, the server directly performs payment processing for the target transaction.

[0304] In specific implementation, in the case where the associated user establishing a payment authorization relationship with the target user is one, the server can send a payment confirmation reminder to the first terminal of the associated user, and the first terminal receives the payment confirmation reminder sent by the server.

[0305] In a case where the associated user establishing the payment authorization relationship with the target user includes the first associated user and the second associated user, for the first associated verification process provided above, if the payment request triggers the payment confirmation policy, the server sends a payment confirmation reminder to the terminal device of the first associated user and the terminal device of the second associated user, the terminal device of the first associated user and the terminal device of the second associated user receive the payment confirmation reminder sent by the server, or according to the payment confirmation priority recorded in the payment authorization record, the server first sends the payment confirmation reminder to the terminal device of the first associated user, if the server receives the first payment confirmation instruction sent by the terminal device of the first associated user, the server no longer sends the payment confirmation reminder to the terminal device of the second associated user, if the server does not receive the first payment confirmation instruction sent by the terminal device of the first associated user, the server sends the payment confirmation reminder to the terminal device of the second associated user again.

[0306] For the second associated verification process provided above, if the payment request triggers any one of the first confirmation policy and the second confirmation policy, the server sends a payment confirmation reminder to the terminal device of the associated user corresponding to the confirmation policy triggering the payment request; if the payment request triggers both the first confirmation policy and the second confirmation policy, the server sends a payment confirmation reminder to the terminal device of the first associated user and the terminal device of the second associated user, the terminal device of the first associated user and the terminal device of the second associated user receive the payment confirmation reminder sent by the server; if the payment request does not trigger the first confirmation policy and the second confirmation policy, the server does not process.

[0307] In step S604, a payment confirmation instruction submitted by the associated user for the payment confirmation reminder is obtained.

[0308] As described above, after the payment request is associatedly verified according to the payment confirmation policy, if the payment verification result is that the payment request triggers the payment confirmation policy, a payment confirmation reminder is sent to the first terminal of the associated user, and the first terminal obtains a payment confirmation instruction submitted by the associated user for the payment confirmation reminder.

[0309] Optionally, the associated user establishes a payment authorization relationship with the target user and is configured with a payment confirmation policy for the target user.

[0310] In step S606, the payment confirmation instruction is sent to the server.

[0311] As described above, the first terminal obtains a payment confirmation instruction submitted by the associated user for the payment confirmation reminder, and sends the payment confirmation instruction to the server. Correspondingly, the server receives the payment confirmation instruction of the payment confirmation reminder sent by the first terminal, and according to the payment confirmation instruction, obtains the identity authentication information of the target user for verification and performs payment processing on the target transaction after the verification is passed.

[0312] In actual application, in order to prevent the target user from logging in the associated user account to agree to the payment request of the target user, the identity of the associated user needs to be verified to ensure that the user who performs the payment confirmation is the associated user himself / herself in the process that the associated user submits the payment confirmation instruction in response to the payment confirmation prompt. In an optional implementation provided by the embodiment, in the process that the server obtains the payment confirmation instruction submitted by the associated user in response to the payment confirmation prompt, the following operations are performed:

[0313] receiving an identity verification page returned by the server after the payment confirmation prompt is triggered;

[0314] acquiring biological feature information through an information acquisition interface configured in the identity verification page.

[0315] Correspondingly, in the process that the server obtains the payment confirmation instruction sent by the first terminal in response to the payment confirmation prompt, the following operations are performed:

[0316] if it is detected that the payment confirmation prompt is triggered, returning an identity verification page to the first terminal;

[0317] acquiring biological feature information uploaded by the first terminal and acquired through an information acquisition interface configured in the identity verification page;

[0318] determining whether the biological feature information matches biological feature information of the associated user;

[0319] if the biological feature information matches the biological feature information of the associated user, it is determined that the associated user submits the payment confirmation instruction in response to the payment confirmation prompt.

[0320] if the biological feature information does not match the biological feature information of the associated user, no processing is performed.

[0321] The biological feature information includes fingerprint information, face image information, and iris information.

[0322] In specific implementation, after the associated user submits the payment confirmation instruction in response to the payment confirmation prompt, the first terminal sends the payment confirmation instruction to the server, the server verifies the identity authentication information of the target user according to the received payment confirmation instruction, and performs payment processing for the target transaction after the verification is passed. The following will describe the process of the server performing payment processing for the associated user in detail.

[0323] (1) The associated user is one person

[0324] In the case that the associated user is one in the payment authorization relationship with the target user, the server sends a payment confirmation reminder to the first terminal of the associated user, and if the server obtains a payment confirmation instruction sent by the first terminal in response to the payment confirmation reminder, the server obtains the identity authentication information of the target user according to the payment confirmation instruction for verification. After the verification is passed, the server performs payment processing on the target transaction. The identity authentication information includes iris information, fingerprint information, a face image of the target user, and a payment key input by the target user.

[0325] (2) The associated user is more than one (taking the first associated user and the second associated user as an example)

[0326] For the first associated verification process provided above, the first confirmation strategy configured by the first associated user in the authorization record is consistent with the second confirmation strategy configured by the second associated user, and the server performs associated verification on the corresponding payment parameters carried in the payment request according to the payment elements in the first confirmation strategy or the second confirmation strategy.

[0327] In the case that the associated verification result is that the payment request triggers the payment confirmation strategy:

[0328] a. The server sends a payment confirmation reminder to the terminal device of the first associated user and the terminal device of the second associated user, and obtains the identity authentication information of the target user according to the first payment confirmation instruction submitted by the first associated user and the second payment confirmation instruction submitted by the second associated user, and performs payment processing on the target transaction. In addition, if the first payment confirmation instruction of the first associated user or the second payment confirmation instruction of the second associated user is detected, the server obtains the identity authentication information of the target user based on the detected payment confirmation instruction and performs verification. After the verification is passed, the target transaction is paid.

[0329] b. According to the payment confirmation priority recorded in the payment authorization record, the server first sends a payment confirmation reminder to the terminal device of the first associated user. If the first payment confirmation instruction sent by the terminal device of the first associated user is received, the server obtains the identity authentication information of the target user and performs payment processing on the target transaction, and no longer sends a payment confirmation reminder to the terminal device of the second associated user. If the first payment confirmation instruction sent by the terminal device of the first associated user is not received, the server sends a payment confirmation reminder to the terminal device of the second associated user. According to the second payment confirmation instruction sent by the terminal device of the second associated user in response to the payment confirmation reminder, the server obtains the identity authentication information of the target user and performs payment processing on the target transaction.

[0330] Regarding the second type of association verification process provided above, the first confirmation policy configured by the first associated user in the authorization record is inconsistent with the second confirmation policy configured by the second associated user. The server performs association verification on the payment request based on the first confirmation policy and on the second confirmation policy.

[0331] a. If the payment request triggers either the first confirmation strategy or the second confirmation strategy, the server sends a payment confirmation reminder to the terminal device of the associated user corresponding to the confirmation strategy that triggered the payment request. Based on the received payment confirmation instruction, the server obtains the target user's identity authentication information and processes the payment for the target transaction.

[0332] b. If both payment requests trigger the first confirmation strategy and the second confirmation strategy, the server sends a payment confirmation reminder to both the terminal devices of the first associated user and the second associated user. Based on the first payment confirmation instruction submitted by the first associated user and the second payment confirmation instruction submitted by the second associated user, the server obtains the target user's identity authentication information and processes the payment for the target transaction. In addition, the server can also receive the first payment confirmation instruction from the first associated user or the second payment confirmation instruction from the second associated user, obtain the target user's identity authentication information based on the received payment confirmation instruction, verify it, and process the payment for the target transaction after the identity authentication information is verified.

[0333] c. If the payment request does not trigger the first confirmation strategy or the second confirmation strategy, the server directly obtains the target user's identity authentication information for verification. After the verification is successful, the server processes the payment for the target transaction.

[0334] To allow for flexible adjustments to payment confirmation, such as enabling teenage users to manage their funds more effectively after completing their studies and entering the workforce, the server can terminate the payment authorization relationship after a linked user confirms payment for a target user's transaction within a certain timeframe, or after the authorization period has expired. Specifically, the payment authorization relationship can be terminated in the following ways:

[0335] Check whether the authorization period recorded in the payment authorization record has expired;

[0336] If yes, then the payment authorization relationship between the associated user and the target user will be terminated; otherwise, no action will be taken.

[0337] or,

[0338] Receive a request from the first terminal to terminate the payment authorization relationship;

[0339] Send a request to the second terminal to terminate the payment authorization relationship;

[0340] If the second terminal receives the cancellation instruction of the cancellation application, the payment authorization relationship between the associated user and the target user is cancelled based on the cancellation instruction.

[0341] Or,

[0342] The second terminal sends a cancellation request for the payment authorization relationship.

[0343] The first terminal sends a cancellation application for the payment authorization relationship.

[0344] If the first terminal receives the cancellation instruction of the cancellation application, the payment authorization relationship between the associated user and the target user is cancelled based on the cancellation instruction.

[0345] Here, the cancellation of the payment authorization relationship specifically changes the authorization state recorded in the payment authorization record to an authorization invalid state.

[0346] It should be noted that in the case where the authorization period recorded in the payment authorization record expires, after the payment authorization relationship between the associated user and the target user is cancelled, the first terminal and the second terminal are sent a cancellation reminder of the payment authorization relationship to inform that the payment authorization relationship has been cancelled.

[0347] The payment confirmation processing method provided in the present embodiment is further described below with reference to the application of the payment confirmation processing method provided in the present embodiment in the elderly user scenario. Figure 4 The payment confirmation processing method applied in the elderly user scenario specifically includes the following steps.

[0348] Step S412, after the payment confirmation reminder is triggered, an identity verification page is displayed.

[0349] Previously, the server receives a payment request submitted by the second terminal of the elderly user for a target transaction, reads the family members establishing a payment authorization relationship with the elderly user and the configured payment confirmation strategy, and determines whether the transfer-in account of the payment amount carried in the payment request is an abnormal account based on the payment confirmation strategy; if not, no processing is performed, if yes, the payment confirmation strategy is triggered to confirm the payment request, and a payment confirmation reminder is sent to the first terminal of the family member.

[0350] Step S414, biological feature information is collected through the information collection interface configured in the identity verification page.

[0351] Step S416, the collected biological feature information is uploaded to the server.

[0352] The server determines whether the biological feature information uploaded by the first terminal matches the biological feature information of the family member; if not, no processing is performed, if yes, it is determined that the family member submits a payment confirmation instruction for the payment confirmation reminder, and is synchronized to the second terminal.

[0353] The second terminal obtains the identity authentication information of the elderly user according to the payment confirmation instruction, and sends the identity authentication information to the server.

[0354] The server verifies the identity authentication information sent by the second terminal, and performs payment processing on the target transaction after verification. The identity authentication information here includes iris information, fingerprint information, a face image, and a payment key input by the elderly user.

[0355] Step S426, send a release request for the payment authorization relationship to the server.

[0356] The server returns the release application for the payment authorization relationship to the second terminal.

[0357] The second terminal submits a release instruction for the release application to the server.

[0358] The server releases the payment authorization relationship between the family member and the elderly user based on the release instruction.

[0359] The following is an example of the application of the payment confirmation processing method provided in this embodiment in the scenario of a young user, which further illustrates the payment confirmation processing method provided in this embodiment, see Figure 5 The payment confirmation processing method applied in the scenario of a young user specifically includes the following steps.

[0360] Step S512, send a payment confirmation instruction for the payment confirmation reminder to the server.

[0361] The server receives a payment request submitted by the second terminal of the young user for the target transaction, reads the payment authorization record for the young user, filters the authorization record with an authorization valid state in the payment authorization record, and if the first confirmation strategy configured by the mother is inconsistent with the second confirmation strategy configured by the father, the payment request is verified according to the first confirmation strategy, and if the payment request triggers the first confirmation strategy, the payment confirmation reminder is sent to the first terminal of the mother.

[0362] The first terminal sends a payment confirmation instruction for the payment confirmation reminder to the server.

[0363] The server synchronizes the payment confirmation instruction sent by the first terminal to the second terminal, verifies the payment request according to the second confirmation strategy, and if the payment request triggers the second confirmation strategy, sends a payment confirmation reminder to the third terminal of the father.

[0364] The third terminal sends a payment confirmation instruction for the payment confirmation reminder to the server. The server synchronizes the payment confirmation instruction sent by the third terminal to the second terminal. The second terminal obtains the identity authentication information of the young user and sends it to the server.

[0365] The server performs identity verification on the identity authentication information of the juvenile user sent by the second terminal, and performs payment processing on the target transaction after the identity verification is passed.

[0366] Among them, the mother and the father both establish a payment authorization relationship with the juvenile user.

[0367] It should be noted that the payment request can also be associated with verification according to the second confirmation strategy, and then associated with verification according to the first confirmation strategy.

[0368] After the associated verification is completed, if the payment request triggers the first confirmation strategy and the second confirmation strategy, the payment confirmation reminder is sent to the first terminal and the third terminal at the same time, and after receiving the payment confirmation instructions sent by the first terminal and the third terminal, the payment confirmation instructions are sent to the second terminal.

[0369] In summary, the payment confirmation processing method provided by the embodiment receives the payment confirmation reminder sent by the server for the payment request of the target user in the target transaction, receives the identity verification page returned by the server after the payment confirmation reminder is triggered, collects the biological feature information through the information collection interface configured by the identity verification page, and uploads the biological feature information to the server. In the case where the biological feature information is consistent with the biological feature information of the associated user, the identity authentication information of the target user is obtained and the payment processing of the target transaction is performed, so as to ensure the payment security and the fund security of the target user, avoid the loss of funds, help the target user to use the Internet payment reasonably, reduce the consumption granularity, and meet the diversified payment scene demand.

[0370] The payment authorization device provided by the present specification is implemented as follows:

[0371] In the above embodiment, a payment authorization method is provided, and a payment authorization device corresponding thereto is also provided, which will be described below with reference to the accompanying drawings.

[0372] Reference Figure 7 It shows a payment authorization device provided by the present embodiment.

[0373] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the related parts can be referred to the above-mentioned corresponding description of the method embodiment. The device embodiment described below is only illustrative.

[0374] The present embodiment provides a payment authorization device, comprising:

[0375] The policy acquisition module 702 is configured to acquire the target user sent by the first terminal of the associated user for authorization invitation, and the payment confirmation policy configured for the target user.

[0376] The invitation information sending module 704 is configured to send authorization invitation information carrying the payment confirmation policy to the second terminal of the target user, and receive a confirmation instruction of the authorization invitation information sent by the second terminal;

[0377] The authorization relationship establishing module 706 is configured to establish a payment authorization relationship between the associated user and the target user based on the confirmation instruction, so as to perform multiple payment verification on a payment request of the target user for the target transaction according to the payment confirmation policy.

[0378] The payment confirmation processing device provided in the specification implements, for example:

[0379] In the above embodiment, a payment confirmation processing method applied to a server is provided, and a payment confirmation processing device running on the server is also provided, which will be described below with reference to the accompanying drawings.

[0380] Reference Figure 8 which shows a schematic diagram of a payment confirmation processing device provided in the embodiment.

[0381] Since the device embodiment corresponds to the method embodiment, it is described more simply, and the related part can be referred to the above-mentioned corresponding description of the method embodiment. The device embodiment described below is only schematic.

[0382] The embodiment provides a payment confirmation processing device running on a server, which comprises:

[0383] The payment request receiving module 802 is configured to receive a payment request submitted by a second terminal of a target user for a target transaction;

[0384] The association verification module 804 is configured to perform association verification on the payment request according to a payment confirmation policy configured by an associated user establishing a payment authorization relationship with the target user for the target user;

[0385] If the association verification result is that the payment request triggers the payment confirmation policy, run the confirmation reminder sending module 806, and the confirmation reminder sending module 806 is configured to send a payment confirmation reminder to the first terminal of the associated user;

[0386] The payment processing module 808 is configured to obtain identity authentication information of the target user and perform payment processing on the target transaction according to a payment confirmation instruction submitted by the associated user for the payment confirmation reminder.

[0387] Another payment confirmation processing device provided in the specification implements, for example:

[0388] In the above embodiment, a payment confirmation processing method applied to a first terminal is provided, and a payment confirmation processing device running on the first terminal is also provided. The following description is made in conjunction with the accompanying drawings.

[0389] Referring to Figure 9 which shows a payment confirmation processing device provided in the embodiment.

[0390] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant part can be seen in the above provided corresponding description of the method embodiment. The device embodiment described below is only illustrative.

[0391] The embodiment provides a payment confirmation processing device running on a first terminal, which comprises:

[0392] The confirmation reminder receiving module 902 is configured to receive a payment confirmation reminder sent by a server for a target user in a target transaction;

[0393] The confirmation instruction obtaining module 904 is configured to obtain a payment confirmation instruction submitted by an associated user for the payment confirmation reminder; the associated user has a payment authorization relationship with the target user and is configured with a payment confirmation strategy for the target user;

[0394] The confirmation instruction sending module 906 is configured to send the payment confirmation instruction to the server; the payment confirmation reminder is sent after the payment request triggers the payment confirmation strategy and before the identity authentication information of the target user is obtained.

[0395] The payment authorization device provided in the specification is as follows:

[0396] Corresponding to the above described payment authorization method, based on the same technical concept, one or more embodiments of the specification also provide a payment authorization device for executing the above provided payment authorization method, Figure 10 The structure diagram of the payment authorization device provided in one or more embodiments of the specification.

[0397] The payment authorization device provided in the embodiment comprises:

[0398] As Figure 10As shown, the payment authorization device can have a large difference due to different configurations or performances, and can include one or more processors 1001 and memories 1002, and the memories 1002 can store one or more stored applications or data. Among them, the memory 1002 can be temporary storage or persistent storage. The application stored in the memory 1002 can include one or more modules (not shown in the figure), and each module can include a series of computer executable instructions in the payment authorization device. Further, the processor 1001 can be configured to communicate with the memory 1002 and execute a series of computer executable instructions in the memory 1002 on the payment authorization device. The payment authorization device can also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input / output interfaces 1005, one or more keyboards 1006, and the like.

[0399] In one specific embodiment, the payment authorization device includes a memory and one or more programs, wherein one or more programs are stored in the memory, and one or more programs can include one or more modules, and each module can include a series of computer executable instructions in the payment authorization device, and the one or more programs configured to be executed by one or more processors include computer executable instructions for:

[0400] Obtaining a target user sending an authorization invitation from a first terminal of an associated user, and a payment confirmation policy configured for the target user;

[0401] Sending authorization invitation information carrying the payment confirmation policy to a second terminal of the target user, and receiving a confirmation instruction of the authorization invitation information sent by the second terminal;

[0402] Based on the confirmation instruction, establishing a payment authorization relationship between the associated user and the target user, for performing multiple payment verification on a payment request of the target user for a target transaction according to the payment confirmation policy.

[0403] The payment confirmation processing device provided in the specification implements, for example:

[0404] According to the above description, a payment confirmation processing method applied to a server is provided based on the same technical concept. One or more embodiments of the specification also provide a payment confirmation processing device for executing the payment confirmation processing method provided above, Figure 11 A structural schematic diagram of a payment confirmation processing device provided for one or more embodiments of the specification.

[0405] This embodiment provides a payment confirmation processing device, comprising:

[0406] like Figure 11 As shown, payment confirmation processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 1101 and memory 1102, with memory 1102 storing one or more application programs or data. Memory 1102 can be temporary or persistent storage. The application programs stored in memory 1102 may include one or more modules (not shown), each module including a series of computer-executable instructions from the payment confirmation processing device. Furthermore, processor 1101 may be configured to communicate with memory 1102, executing the series of computer-executable instructions in memory 1102 on the payment confirmation processing device. The payment confirmation processing device may also include one or more power supplies 1103, one or more wired or wireless network interfaces 1104, one or more input / output interfaces 1105, one or more keyboards 1106, etc.

[0407] In one specific embodiment, the payment confirmation processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the payment confirmation processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0408] Receive payment requests submitted by the target user's second terminal for the target transaction;

[0409] The payment request is verified in association with the payment confirmation policy configured for the target user by the associated user who has established a payment authorization relationship with the target user.

[0410] If the verification result indicates that the payment request triggers the payment confirmation strategy, then a payment confirmation reminder is sent to the first terminal of the associated user.

[0411] Based on the payment confirmation instruction submitted by the associated user in response to the payment confirmation reminder, the identity authentication information of the target user is obtained and the payment is processed for the target transaction.

[0412] Another embodiment of the payment confirmation processing device provided in this manual is as follows:

[0413] Corresponding to the above description, based on the same technical concept, one or more embodiments of the present specification also provide a payment confirmation processing device for executing the payment confirmation processing method provided above, Figure 12 A structural schematic diagram of a payment confirmation processing device provided for one or more embodiments of the present specification.

[0414] The payment confirmation processing device provided in this embodiment comprises:

[0415] As Figure 12 indicated, the payment confirmation processing device can have great differences due to different configurations or performances, and can include one or more processors 1201 and memories 1202, and one or more storage applications or data can be stored in the memories 1202. Among them, the memory 1202 can be temporary storage or persistent storage. The application stored in the memory 1202 can include one or more modules (not shown in the figure), and each module can include a series of computer executable instructions in the payment confirmation processing device. Further, the processor 1201 can be configured to communicate with the memory 1202 and execute a series of computer executable instructions in the memory 1202 on the payment confirmation processing device. The payment confirmation processing device can also include one or more power supplies 1203, one or more wired or wireless network interfaces 1204, one or more input / output interfaces 1205, one or more keyboards 1206, etc.

[0416] In one specific embodiment, the payment confirmation processing device includes a memory and one or more programs, wherein one or more programs are stored in the memory, and one or more programs can include one or more modules, and each module can include a series of computer executable instructions in the payment confirmation processing device, and the one or more programs configured to be executed by the one or more processors include computer executable instructions for:

[0417] receiving a payment confirmation prompt sent by the server for a payment request of a target user in a target transaction;

[0418] obtaining a payment confirmation instruction submitted by an associated user for the payment confirmation prompt; the associated user has a payment authorization relationship with the target user and is configured with a payment confirmation strategy for the target user;

[0419] sending the payment confirmation instruction to the server;

[0420] The payment confirmation prompt is sent after the payment request triggers the payment confirmation strategy and before identity authentication information of the target user is obtained.

[0421] The first storage medium provided in the specification is implemented as follows:

[0422] Based on the same technical concept, the one or more embodiments of the specification also provide a storage medium corresponding to the payment authorization method described above.

[0423] The storage medium provided in the embodiment is used to store computer executable instructions, and the computer executable instructions implement the following processes when executed by a processor.

[0424] Obtain a target user sending an authorization invitation from a first terminal of an associated user, and a payment confirmation strategy configured for the target user;

[0425] Send authorization invitation information carrying the payment confirmation strategy to a second terminal of the target user, and receive a confirmation instruction of the authorization invitation information sent by the second terminal;

[0426] Based on the confirmation instruction, establish a payment authorization relationship between the associated user and the target user, and use the payment authorization relationship to perform multiple payment verifications on a payment request of the target user for a target transaction according to the payment confirmation strategy.

[0427] It should be noted that the embodiments of the storage medium in the specification and the embodiments of the payment authorization method in the specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0428] The second storage medium provided in the specification is implemented as follows:

[0429] Based on the same technical concept, the one or more embodiments of the specification also provide a storage medium corresponding to the payment confirmation processing method applied to the server.

[0430] The storage medium provided in the embodiment is used to store computer executable instructions, and the computer executable instructions implement the following processes when executed by a processor.

[0431] Receive a payment request submitted by a second terminal of a target user for a target transaction;

[0432] According to a payment confirmation strategy configured for the target user by an associated user establishing a payment authorization relationship with the target user, perform an associated verification on the payment request;

[0433] If the association verification result is that the payment request triggers the payment confirmation policy, a payment confirmation reminder is sent to the first terminal of the association user;

[0434] According to the payment confirmation instruction submitted by the association user for the payment confirmation reminder, identity authentication information of the target user is obtained and payment processing is performed on the target transaction.

[0435] It should be noted that the embodiments of the storage medium in the present specification are based on the same inventive concept as the embodiments of the payment confirmation processing method in the present specification, and therefore the specific implementation of this embodiment can refer to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0436] The third storage medium embodiment provided by the present specification is as follows:

[0437] According to the same technical concept, the one or more embodiments of the present specification also provide a storage medium for the payment confirmation processing method applied to the first terminal corresponding to the above description.

[0438] The storage medium provided in the present embodiment is used to store computer executable instructions, and the computer executable instructions realize the following flow when executed by a processor:

[0439] The payment confirmation reminder sent by the server for the payment request of the target user in the target transaction is received;

[0440] The payment confirmation instruction submitted by the association user for the payment confirmation reminder is obtained; the association user has a payment authorization relationship with the target user and is configured with a payment confirmation policy for the target user;

[0441] The payment confirmation instruction is sent to the server;

[0442] The payment confirmation reminder is sent after the payment request triggers the payment confirmation policy and before the identity authentication information of the target user is obtained.

[0443] It should be noted that the embodiments of the storage medium in the present specification are based on the same inventive concept as the embodiments of the payment confirmation processing method in the present specification, and therefore the specific implementation of this embodiment can refer to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0444] The above described embodiments of the present description have been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0445] In the 1930s, it was clear to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structure of diodes, transistors, switches, etc.) or in software (e.g., improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by a hardware entity module. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating an integrated circuit chip, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code to be compiled is written in a specific programming language, called a hardware description language (HDL), of which there are many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., the most commonly used being VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should be clear to those skilled in the art that, by simply logically programming a method flow in one of the above hardware description languages and programming it into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0446] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0447] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0448] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0449] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0450] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable payment confirmation processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable payment confirmation processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0451] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable payment confirmation processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0452] These computer program instructions can also be loaded onto a computer or other programmable payment confirmation processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0453] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0454] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0455] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0456] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or apparatus that comprises a list of elements does not only include those elements, but also includes other elements not explicitly listed or inherent to such a process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

[0457] One or more embodiments of the specification can be described in the general context of computer-executable instructions being executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the specification can also be practiced in a distributed computing environment, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0458] Each embodiment in the specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other, and each embodiment focuses on the difference from other embodiments. In particular, for system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

[0459] The above merely provides the example of the present document and is not intended to limit the present document. For those skilled in the art, the present document can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present document shall be included in the scope of claims of the present document.

Claims

1. A payment authorization method, comprising: The system obtains the target user for authorization invitations sent by the first terminal of multiple associated users, and the payment confirmation strategy configured for the target user to confirm payments when transferring funds to abnormal accounts. Send an authorization invitation message carrying the payment confirmation strategy to the second terminal of the target user, and receive a confirmation instruction for the authorization invitation message sent by the second terminal; Based on the confirmation instruction, payment confirmation permissions for the target user in transfer transactions are granted to the multiple associated users, and the authorization status is marked as valid. A payment authorization record is generated and stored according to the payment confirmation permissions, the valid authorization status, and the payment confirmation strategy, so as to perform multiple payment verifications on the transfer requests submitted by the second terminal for transfer transactions according to multiple payment confirmation strategies. The multi-payment verification includes: reading the payment authorization records for the target user and filtering the authorization records with an authorization status of valid; if the payment confirmation strategies configured by multiple associated users in the authorization records are inconsistent, determining whether the receiving account of the transfer amount carried in the transfer request is an abnormal account according to the multiple payment confirmation strategies; if so, sending a payment confirmation reminder to the associated user terminal corresponding to the payment confirmation strategy of the abnormal account, receiving the returned payment confirmation instruction, obtaining the identity authentication information of the target user based on the payment confirmation instruction, and processing the transfer transaction.

2. The payment authorization method according to claim 1, further comprising, after the step of granting payment confirmation permissions for the target user in transfer transactions to the plurality of associated users based on the confirmation instruction, marking the authorization status as an authorized valid status, generating and storing a payment authorization record according to the payment confirmation permissions, the authorized valid status, and the payment confirmation strategy, for use in performing multiple payment verification steps on the transfer request submitted by the second terminal for the transfer transaction according to multiple payment confirmation strategies: Check whether the authorization period recorded in the payment authorization record has expired; If so, then the payment authorization relationship between the multiple associated users and the target user shall be terminated; or, Receive a request from the first terminal to terminate the payment authorization relationship; Send a request to the second terminal to terminate the payment authorization relationship; If a release instruction is received from the second terminal regarding the release application, the payment authorization relationship between the multiple associated users and the target user is released based on the release instruction.

3. The payment authorization method according to claim 1, before executing the steps of obtaining the target user for the authorization invitation sent by the first terminal of multiple associated users, and the payment confirmation strategy configured for the target user to confirm payment when transferring funds to an abnormal account, further includes: Receive payment authorization request sent by the first terminal; The payment authorization request is submitted by triggering the authorization control; Read the user list of the multiple associated users and return it to the first terminal.

4. A payment confirmation processing method, applied to a server, comprising: Receive transfer requests submitted by the target user's second terminal for the transfer transaction; Read the payment authorization records for the target user and filter the authorization records whose authorization status is valid; If the payment confirmation strategies configured by multiple associated users who have established payment authorization relationships with the target user for the target user when transferring funds to abnormal accounts are inconsistent, it is determined whether the receiving account of the transfer amount carried by the transfer request is an abnormal account according to the multiple payment confirmation strategies. The payment authorization relationship is established after the confirmation instruction based on the authorization invitation information of the payment confirmation strategy sent by the second terminal grants the multiple associated users payment confirmation permissions for the target user in the transfer transaction, marks the authorization status as valid, generates and stores a payment authorization record based on the payment confirmation permissions, the valid authorization status and the payment confirmation strategy; The payment authorization relationship is terminated based on the termination instruction of the termination application submitted by the first terminal of the multiple associated users. The termination application is sent to the first terminal after receiving the termination request for the payment authorization relationship sent by the second terminal. If so, send a payment confirmation reminder to the associated user terminal corresponding to the payment confirmation policy for accounts whose transfers are to abnormal accounts; Based on the payment confirmation instruction submitted by the associated user terminal in response to the payment confirmation reminder, the identity authentication information of the target user is obtained and the transfer transaction is processed.

5. The payment confirmation processing method according to claim 4, further comprising: If the first confirmation strategy configured by the first associated user in the authorization record is consistent with the second confirmation strategy configured by the second associated user, then the corresponding transfer parameters carried in the transfer request are verified according to the payment elements in the first confirmation strategy or the second confirmation strategy. Accordingly, the step of obtaining the target user's identity authentication information and processing the transfer transaction based on the payment confirmation instruction submitted by the associated user terminal in response to the payment confirmation reminder includes: Based on the first payment confirmation instruction submitted by the first associated user and the second payment confirmation instruction submitted by the second associated user, the identity authentication information of the target user is obtained and the transfer transaction is processed.

6. The payment confirmation processing method according to claim 4, wherein obtaining the identity authentication information of the target user and processing the transfer transaction based on the payment confirmation instruction submitted by the associated user terminal in response to the payment confirmation reminder includes: If a first payment confirmation instruction submitted by a first associated user or a second payment confirmation instruction submitted by a second associated user is detected, the identity authentication information of the target user is obtained and verified based on the detected payment confirmation instruction; After verification, the transfer transaction will be processed.

7. The payment confirmation processing method according to claim 4, wherein the payment confirmation instruction is determined in the following manner: If the payment confirmation reminder is detected to be triggered, the identity verification page is returned to the first terminal; Obtain biometric information uploaded by the first terminal and collected through the information collection interface configured on the identity verification page; Determine whether the biometric information matches the biometric information of the multiple associated users; If a match is found, it is determined that the multiple associated users have submitted the payment confirmation instruction in response to the payment confirmation reminder.

8. The payment confirmation processing method according to claim 4, after the step of obtaining the identity authentication information of the target user and processing the transfer transaction based on the payment confirmation instruction submitted by the associated user terminal in response to the payment confirmation reminder, further includes: Check whether the authorization period recorded in the payment authorization record has expired; If so, then the payment authorization relationship between the multiple associated users and the target user shall be terminated; or, Receive a request from the first terminal to terminate the payment authorization relationship; Send a request to the second terminal to terminate the payment authorization relationship; If a release instruction is received from the second terminal regarding the release application, the payment authorization relationship between the multiple associated users and the target user is released based on the release instruction.

9. A payment confirmation processing method, applied to a first terminal, comprising: Receive payment confirmation notifications sent by the server in response to the transfer requests of the target user in a transfer transaction; The system obtains the payment confirmation instruction submitted by the associated user in response to the payment confirmation reminder; the associated user and the target user have established a payment authorization relationship; the payment authorization relationship is established by granting the associated user payment confirmation permission for the target user in transfer transactions based on the confirmation instruction of the authorization invitation information of the payment confirmation strategy sent by the target user's second terminal, and marking the authorization status as an authorized valid status; a payment authorization record is generated and stored based on the payment confirmation permission, the authorized valid status, and the payment confirmation strategy. The payment authorization relationship is terminated based on the termination instruction of the termination application submitted by the first terminal of the associated user. The termination application is sent to the first terminal after receiving the termination request for the payment authorization relationship sent by the second terminal. Send the payment confirmation instruction to the server; The payment confirmation notification is sent when the server receives the transfer request, reads the payment authorization record for the target user, and filters the authorization records with the authorization status being valid. If the payment confirmation strategies configured by multiple associated users who have established a payment authorization relationship with the target user for transferring funds to abnormal accounts are inconsistent, the server determines whether the receiving account of the transfer amount carried in the transfer request is an abnormal account based on the multiple payment confirmation strategies, and sends the notification if there is an abnormal account among the receiving accounts.

10. The payment confirmation processing method according to claim 9, wherein obtaining the payment confirmation instruction submitted by the associated user in response to the payment confirmation reminder includes: Receive the identity verification page returned by the server after the payment confirmation reminder is triggered; Biometric information is collected through the information collection interface configured on the identity verification page.

11. A payment authorization device, comprising: The strategy acquisition module is configured to acquire the target users for authorization invitations sent by the first terminal of multiple associated users, and the payment confirmation strategy configured for the target users for payment confirmation when transferring funds to abnormal accounts. The invitation information sending module is configured to send an authorization invitation information carrying the payment confirmation strategy to the second terminal of the target user, and to receive a confirmation instruction for the authorization invitation information sent by the second terminal; The authorization relationship establishment module is configured to grant payment confirmation permissions for the target user in transfer transactions to the multiple associated users based on the confirmation instruction, and mark the authorization status as valid. It generates and stores payment authorization records based on the payment confirmation permissions, the valid authorization status, and the payment confirmation strategy, for use in performing multi-payment verification on transfer requests submitted by the second terminal for transfer transactions according to multiple payment confirmation strategies. The multi-payment verification includes: reading the payment authorization records for the target user and filtering authorization records with a valid authorization status; if the payment confirmation strategies configured by the multiple associated users in the authorization records are inconsistent, determining whether the receiving account of the transfer amount carried in the transfer request is an abnormal account according to the multiple payment confirmation strategies; if so, sending a payment confirmation reminder to the associated user terminal corresponding to the payment confirmation strategy for the abnormal account and receiving the returned payment confirmation instruction; obtaining the target user's identity authentication information based on the payment confirmation instruction and processing the transfer transaction.

12. A payment confirmation processing device, operating on a server, comprising: The payment request receiving module is configured to receive transfer requests submitted by the target user's second terminal for the transfer transaction; The associated verification module is configured to read payment authorization records for the target user and filter authorization records whose authorization status is valid. If the payment confirmation strategies configured by multiple associated users who have established payment authorization relationships with the target user for the target user when transferring funds to abnormal accounts are inconsistent, it is determined whether the receiving account of the transfer amount carried by the transfer request is an abnormal account according to the multiple payment confirmation strategies. The payment authorization relationship is established after the confirmation instruction based on the authorization invitation information of the payment confirmation strategy sent by the second terminal grants the multiple associated users payment confirmation permissions for the target user in the transfer transaction, marks the authorization status as valid, generates and stores a payment authorization record based on the payment confirmation permissions, the valid authorization status and the payment confirmation strategy; The payment authorization relationship is terminated based on the termination instruction of the termination application submitted by the first terminal of the multiple associated users. The termination application is sent to the first terminal after receiving the termination request for the payment authorization relationship sent by the second terminal. If so, the confirmation reminder sending module is run. The confirmation reminder sending module is configured to send a payment confirmation reminder to the associated user terminal corresponding to the payment confirmation strategy for which the transfer-in account is an abnormal account. The payment processing module is configured to obtain the target user's identity authentication information and process the transfer transaction based on the payment confirmation instruction submitted by the associated user terminal in response to the payment confirmation reminder.

13. A payment confirmation processing device, operating in a first terminal, comprising: The confirmation notification receiving module is configured to receive payment confirmation notifications sent by the server in response to the transfer request of the target user in a transfer transaction; The confirmation instruction acquisition module is configured to acquire the payment confirmation instruction submitted by the associated user in response to the payment confirmation reminder; the associated user and the target user have established a payment authorization relationship; the payment authorization relationship is established after the confirmation instruction of the authorization invitation information of the payment confirmation strategy sent by the second terminal of the target user grants the associated user payment confirmation permission for the target user in the transfer transaction, and marks the authorization status as an authorized valid status, and generates and stores a payment authorization record based on the payment confirmation permission, the authorized valid status and the payment confirmation strategy; The payment authorization relationship is terminated based on the termination instruction of the termination application submitted by the first terminal of the associated user. The termination application is sent to the first terminal after receiving the termination request for the payment authorization relationship sent by the second terminal. The confirmation instruction sending module is configured to send the payment confirmation instruction to the server; wherein, the payment confirmation reminder is sent when the server receives the transfer request, reads the payment authorization record for the target user, and filters the authorization record with the authorization status being valid. If the payment confirmation strategies configured by multiple associated users who have established a payment authorization relationship with the target user for the target user to confirm payments to abnormal accounts are inconsistent, the system determines whether the receiving account of the transfer amount carried in the transfer request is an abnormal account according to the multiple payment confirmation strategies, and sends the confirmation instruction if there is an abnormal account among the receiving accounts.

14. A payment authorization device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: The system obtains the target user for authorization invitations sent by the first terminal of multiple associated users, and the payment confirmation strategy configured for the target user to confirm payments when transferring funds to abnormal accounts. Send an authorization invitation message carrying the payment confirmation strategy to the second terminal of the target user, and receive a confirmation instruction for the authorization invitation message sent by the second terminal; Based on the confirmation instruction, payment confirmation permissions for the target user in transfer transactions are granted to the multiple associated users, and the authorization status is marked as valid. A payment authorization record is generated and stored according to the payment confirmation permissions, the valid authorization status, and the payment confirmation strategy, so as to perform multiple payment verifications on the transfer requests submitted by the second terminal for transfer transactions according to multiple payment confirmation strategies. The multi-payment verification includes: reading the payment authorization records for the target user and filtering the authorization records with an authorization status of valid; if the payment confirmation strategies configured by multiple associated users in the authorization records are inconsistent, determining whether the receiving account of the transfer amount carried in the transfer request is an abnormal account according to the multiple payment confirmation strategies; if so, sending a payment confirmation reminder to the associated user terminal corresponding to the payment confirmation strategy of the abnormal account, receiving the returned payment confirmation instruction, obtaining the identity authentication information of the target user based on the payment confirmation instruction, and processing the transfer transaction.

15. A payment confirmation processing device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Receive transfer requests submitted by the target user's second terminal for the transfer transaction; Read the payment authorization records for the target user and filter the authorization records whose authorization status is valid; If the payment confirmation strategies configured by multiple associated users who have established payment authorization relationships with the target user for the target user when transferring funds to abnormal accounts are inconsistent, it is determined whether the receiving account of the transfer amount carried by the transfer request is an abnormal account according to the multiple payment confirmation strategies. The payment authorization relationship is established after the confirmation instruction based on the authorization invitation information of the payment confirmation strategy sent by the second terminal grants the multiple associated users payment confirmation permissions for the target user in the transfer transaction, marks the authorization status as valid, generates and stores a payment authorization record based on the payment confirmation permissions, the valid authorization status and the payment confirmation strategy; The payment authorization relationship is terminated based on the termination instruction of the termination application submitted by the first terminal of the multiple associated users. The termination application is sent to the first terminal after receiving the termination request for the payment authorization relationship sent by the second terminal. If so, send a payment confirmation reminder to the associated user terminal corresponding to the payment confirmation policy for accounts whose transfers are to abnormal accounts; Based on the payment confirmation instruction submitted by the associated user terminal in response to the payment confirmation reminder, the identity authentication information of the target user is obtained and the transfer transaction is processed.

16. A payment confirmation processing device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Receive payment confirmation notifications sent by the server in response to the transfer requests of the target user in a transfer transaction; The system obtains the payment confirmation instruction submitted by the associated user in response to the payment confirmation reminder; the associated user and the target user have established a payment authorization relationship; the payment authorization relationship is established by granting the associated user payment confirmation permission for the target user in transfer transactions based on the confirmation instruction of the authorization invitation information of the payment confirmation strategy sent by the target user's second terminal, and marking the authorization status as an authorized valid status; a payment authorization record is generated and stored based on the payment confirmation permission, the authorized valid status, and the payment confirmation strategy. The payment authorization relationship is terminated based on the termination instruction of the termination application submitted by the first terminal of the associated user. The termination application is sent to the first terminal after receiving the termination request for the payment authorization relationship sent by the second terminal. Send the payment confirmation instruction to the server; The payment confirmation notification is sent when the server receives the transfer request, reads the payment authorization record for the target user, and filters the authorization records with the authorization status being valid. If the payment confirmation strategies configured by multiple associated users who have established a payment authorization relationship with the target user for transferring funds to abnormal accounts are inconsistent, the server determines whether the receiving account of the transfer amount carried in the transfer request is an abnormal account based on the multiple payment confirmation strategies, and sends the notification if there is an abnormal account among the receiving accounts.

17. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: The system obtains the target user for authorization invitations sent by the first terminal of multiple associated users, and the payment confirmation strategy configured for the target user to confirm payments when transferring funds to abnormal accounts. Send an authorization invitation message carrying the payment confirmation strategy to the second terminal of the target user, and receive a confirmation instruction for the authorization invitation message sent by the second terminal; Based on the confirmation instruction, payment confirmation permissions for the target user in transfer transactions are granted to the multiple associated users, and the authorization status is marked as valid. A payment authorization record is generated and stored according to the payment confirmation permissions, the valid authorization status, and the payment confirmation strategy, so as to perform multiple payment verifications on the transfer requests submitted by the second terminal for transfer transactions according to multiple payment confirmation strategies. The multi-payment verification includes: reading the payment authorization records for the target user and filtering the authorization records with an authorization status of valid; if the payment confirmation strategies configured by multiple associated users in the authorization records are inconsistent, determining whether the receiving account of the transfer amount carried in the transfer request is an abnormal account according to the multiple payment confirmation strategies; if so, sending a payment confirmation reminder to the associated user terminal corresponding to the payment confirmation strategy of the abnormal account, receiving the returned payment confirmation instruction, obtaining the identity authentication information of the target user based on the payment confirmation instruction, and processing the transfer transaction.

18. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Receive transfer requests submitted by the target user's second terminal for the transfer transaction; Read the payment authorization records for the target user and filter the authorization records whose authorization status is valid; If the payment confirmation strategies configured by multiple associated users who have established payment authorization relationships with the target user for the target user when transferring funds to abnormal accounts are inconsistent, it is determined whether the receiving account of the transfer amount carried by the transfer request is an abnormal account according to the multiple payment confirmation strategies. The payment authorization relationship is established after the confirmation instruction based on the authorization invitation information of the payment confirmation strategy sent by the second terminal grants the multiple associated users payment confirmation permissions for the target user in the transfer transaction, marks the authorization status as valid, generates and stores a payment authorization record based on the payment confirmation permissions, the valid authorization status and the payment confirmation strategy; The payment authorization relationship is terminated based on the termination instruction of the termination application submitted by the first terminal of the multiple associated users. The termination application is sent to the first terminal after receiving the termination request for the payment authorization relationship sent by the second terminal. If so, send a payment confirmation reminder to the associated user terminal corresponding to the payment confirmation policy for accounts whose transfers are to abnormal accounts; Based on the payment confirmation instruction submitted by the associated user terminal in response to the payment confirmation reminder, the identity authentication information of the target user is obtained and the transfer transaction is processed.

19. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Receive payment confirmation notifications sent by the server in response to the transfer requests of the target user in a transfer transaction; The system obtains the payment confirmation instruction submitted by the associated user in response to the payment confirmation reminder; the associated user and the target user have established a payment authorization relationship; the payment authorization relationship is established by granting the associated user payment confirmation permission for the target user in transfer transactions based on the confirmation instruction of the authorization invitation information of the payment confirmation strategy sent by the target user's second terminal, and marking the authorization status as an authorized valid status; a payment authorization record is generated and stored based on the payment confirmation permission, the authorized valid status, and the payment confirmation strategy. The payment authorization relationship is terminated based on the termination instruction of the termination application submitted by the first terminal of the associated user. The termination application is sent to the first terminal after receiving the termination request for the payment authorization relationship sent by the second terminal. Send the payment confirmation instruction to the server; The payment confirmation notification is sent when the server receives the transfer request, reads the payment authorization record for the target user, and filters the authorization records with the authorization status being valid. If the payment confirmation strategies configured by multiple associated users who have established a payment authorization relationship with the target user for transferring funds to abnormal accounts are inconsistent, the server determines whether the receiving account of the transfer amount carried in the transfer request is an abnormal account based on the multiple payment confirmation strategies, and sends the notification if there is an abnormal account among the receiving accounts.

Images