CN112837053B

CN112837053B - Payment processing method and device

Info

Publication number: CN112837053B
Application number: CN202110128250.3A
Authority: CN
Inventors: 刘婧; 王储; 王哲歆
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2021-01-29
Filing date: 2021-01-29
Publication date: 2022-08-09
Anticipated expiration: 2041-01-29
Also published as: CN115330380A; CN112837053A

Abstract

The embodiment of the specification provides a payment processing method and a payment processing device, wherein the payment processing method comprises the following steps: inputting the information to be paid obtained after the code scanning component scans the codes into a risk identification algorithm to identify the payment risk, and outputting the payment risk level; if the payment risk level is a preset risk level, determining a reminding time length corresponding to the preset risk level, and generating reminding content based on the information to be paid; sending the reminding time length and the reminding content to a user terminal so that the user terminal performs countdown display on the reminding content according to the reminding time length; and carrying out payment processing on the information to be paid when the countdown display is finished.

Description

Payment processing method and device

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a payment processing method and apparatus.

Background

With the continuous development of the technology level, the payment by scanning the two-dimensional code is generally applied in life, and the two-dimensional code payment is a new generation wireless payment scheme based on the account system. Under the payment scheme, a merchant can compile transaction information such as account numbers, commodity prices and the like into a two-dimensional code, and print the two-dimensional code on carriers such as various newspapers, magazines, advertisements and books for release, and in addition, the merchant can also carry out payment transaction by scanning payment two-dimensional codes of customers.

Disclosure of Invention

One or more embodiments of the present specification provide a payment processing method. The payment processing method comprises the following steps: and inputting the information to be paid obtained after the code scanning component scans the codes into a risk identification algorithm to identify the payment risk, and outputting the payment risk level. And if the payment risk level is a preset risk level, determining a reminding time length corresponding to the preset risk level, and generating reminding content based on the information to be paid. And sending the reminding time length and the reminding content to a user terminal so that the user terminal performs countdown display on the reminding content according to the reminding time length. And carrying out payment processing on the information to be paid when the countdown display is finished.

One or more embodiments of the present specification provide a payment reminder processing method, including: and receiving the reminding time length and the reminding content which are sent by the server after the payment risk identification is carried out on the information to be paid. And displaying a reminding layer carrying the reminding content, and performing countdown display on the reminding layer by taking the reminding time length as a countdown time length. And if the user operation instruction input aiming at the reminding layer is not detected under the condition that the countdown display is finished, synchronizing a detection result to the server.

One or more embodiments of the present specification provide a payment processing apparatus, including: and the identification module is configured to input the information to be paid obtained after the code scanning component scans the codes into a risk identification algorithm to carry out payment risk identification, and output a payment risk level. And the generating module is configured to determine a reminding time length corresponding to a preset risk level if the payment risk level is the preset risk level, and generate reminding content based on the information to be paid. And the sending module is configured to send the reminding time length and the reminding content to a user terminal so that the user terminal performs countdown display on the reminding content according to the reminding time length. The processing module is configured to perform payment processing on the information to be paid when the countdown display is finished.

One or more embodiments of the present specification provide a payment advice processing apparatus, including: the receiving module is configured to receive the reminding duration and the reminding content which are sent by the server after the payment risk identification is carried out on the information to be paid. And the display module is configured to display a reminding layer carrying the reminding content, and perform countdown display on the reminding layer by taking the reminding time length as the countdown time length. And the synchronization module is configured to synchronize a detection result to the server if the user operation instruction input for the reminding layer is not detected under the condition that the countdown display is finished.

One or more embodiments of the present specification provide a payment processing apparatus comprising: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: and inputting the information to be paid obtained after the code scanning component scans the codes into a risk identification algorithm to identify the payment risk, and outputting the payment risk level. And if the payment risk level is a preset risk level, determining a reminding time length corresponding to the preset risk level, and generating reminding content based on the information to be paid. And sending the reminding time length and the reminding content to a user terminal so that the user terminal performs countdown display on the reminding content according to the reminding time length. And carrying out payment processing on the information to be paid when the countdown display is finished.

One or more embodiments of the present specification provide a payment advice processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and receiving the reminding duration and the reminding content which are sent by the server after the payment risk identification is carried out on the information to be paid. And displaying a reminding layer carrying the reminding content, and performing countdown display on the reminding layer by taking the reminding time length as a countdown time length. And if the user operation instruction input aiming at the reminding layer is not detected under the condition that the countdown display is finished, synchronizing a detection result to the server.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following: and inputting the information to be paid obtained after the code scanning component scans the codes into a risk identification algorithm to identify the payment risk, and outputting the payment risk level. And if the payment risk level is a preset risk level, determining a reminding time length corresponding to the preset risk level, and generating reminding content based on the information to be paid. And sending the reminding time length and the reminding content to a user terminal so that the user terminal performs countdown display on the reminding content according to the reminding time length. And carrying out payment processing on the information to be paid when the countdown display is finished.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following flow: and receiving the reminding duration and the reminding content which are sent by the server after the payment risk identification is carried out on the information to be paid. And displaying a reminding layer carrying the reminding content, and performing countdown display on the reminding layer by taking the reminding time length as a countdown time length. And if the user operation instruction input aiming at the reminding layer is not detected under the condition that the countdown display is finished, synchronizing a detection result to the server.

Drawings

In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, the drawings that are needed in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and that other drawings can be obtained by those skilled in the art without inventive exercise.

Fig. 1 is a process flow diagram of a payment processing method according to one or more embodiments of the present disclosure;

fig. 2 is a process flow diagram of a payment processing method applied to a cross-currency payment scenario according to one or more embodiments of the present disclosure;

fig. 3 is a process flow diagram of a payment processing method applied to a delayed reminder scenario according to one or more embodiments of the present specification;

FIG. 4 is a process flow diagram of a payment reminder processing method according to one or more embodiments of the present disclosure;

fig. 5 is a flowchart of a payment reminder processing method applied to a cross-currency payment scenario according to one or more embodiments of the present disclosure;

fig. 6 is a flowchart of a payment reminder processing method applied to a delayed reminder scenario according to one or more embodiments of the present disclosure;

FIG. 7 is a schematic diagram of a payment processing apparatus according to one or more embodiments of the present disclosure;

FIG. 8 is a schematic diagram of a payment reminder processing apparatus according to one or more embodiments of the present disclosure;

fig. 9 is a schematic structural diagram of a payment processing apparatus according to one or more embodiments of the present disclosure;

fig. 10 is a schematic structural diagram of a payment reminder processing apparatus according to one or more embodiments of the present disclosure.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step, shall fall within the scope of protection of this document.

An embodiment of a payment processing method provided in this specification:

referring to fig. 1, which shows a processing flow chart of a payment processing method provided in this embodiment, referring to fig. 2, which shows a processing flow chart of a payment processing method applied to a cross-currency payment scenario provided in this embodiment, referring to fig. 3, which shows a processing flow chart of a payment processing method applied to a delayed reminder scenario provided in this embodiment.

An execution main body of the payment processing method provided by the embodiment is a server, an execution main body of an embodiment of the payment reminding processing method provided by the specification is a user terminal, and the payment processing method applied to the server provided by the embodiment is matched with the payment reminding processing method applied to the user terminal provided by the method embodiment in the following execution process, so that the contents corresponding to the method embodiment in the following embodiment are read.

Referring to fig. 1, the payment processing method provided in this embodiment specifically includes steps S102 to S108 described below.

And S102, inputting the information to be paid obtained after the code scanning component scans the codes into a risk identification algorithm to carry out payment risk identification, and outputting the payment risk level.

In practical application, in the process of payment by a user through a payment code, a merchant can finish payment by scanning the payment code displayed by a user terminal by using a code scanning component, the user cannot confirm the amount and information of payment in advance in the process, the process has insecurity feeling, and if the payment code is scanned and then high-risk information to be paid is acquired, the payment process is interrupted and the actual reason of interruption is not displayed to the user.

According to the payment processing method provided by the embodiment, the reminding contents with different reminding durations are displayed to the user according to different payment risk levels in the payment process, so that the user can sense the payment details in the payment process; specifically, after information to be paid is acquired, payment risk recognition is carried out on the information to be paid, corresponding reminding time length is determined according to payment risk levels output by the payment risk recognition, reminding content is generated according to payment identifiers, collection identifiers and collection amounts contained in the information to be paid, a reminding layer containing the reminding content is regenerated, when a user accesses an application program, the reminding layer is displayed in a countdown mode on an application page, countdown time is displayed on the reminding layer, and finally payment processing is carried out on the information to be paid when the countdown display is finished, so that the safety of the user is improved by displaying the collection amount of a merchant and the payment amount of the user to the user, different reminding time lengths are determined according to different payment risk levels, the perception degree of the user on payment data is improved, and the reliability of payment and the safety of the user are further improved, in addition, the user can more visually perceive specific payment information by prolonging the reminding time under the condition that the payment risk level is high risk, and the high-risk information to be paid is deducted under the condition that the user does not submit the user operation instruction, so that the use experience of the user is ensured.

The code scanning assembly comprises an assembly or equipment capable of scanning the payment two-dimensional code. Such as a code scanning gun, a user terminal. In addition, the system can also comprise a characteristic acquisition device for acquiring the human face to confirm payment. In practice, the code scanning gun is generally connected to a PC of a counter, so that the PC and the code scanning gun can be regarded as a code scanning assembly.

Taking a shopping scene of a user as an example, when the user shows a payment code of the user during payment, a code scanning gun of a merchant scans the payment code of the user and then uploads payment information of the user, payment information of the merchant and transaction details as information to be paid to a server. The payment risk identification is used for identifying the payment risk of the information to be paid so as to obtain the payment risk level; the payment risk level comprises a first risk level, a second risk level and a third risk level; the first risk level is a level corresponding to low risk, the second risk level is a level corresponding to high risk, and the third risk level is a level corresponding to abnormal information to be paid.

In specific implementation, after the code scanning component scans the payment code of the user, the information to be paid is submitted to the server, in order to ensure the safety of the information to be paid, the information to be paid is input into the risk identification algorithm for payment risk identification, and then the payment risk level output by the risk identification algorithm is obtained.

In practical application, the risk level of the information to be paid is determined, risk identification is mainly performed from three aspects, in order to make the payment risk level output by a risk identification algorithm more accurate and more effective and ensure resource security of a payer, identification needs to be performed on the information of the payer and the information of a payee, and whether the information of the payee and the information of the payer are marked as blacklists is determined, meanwhile, in order to avoid the distrust of a user caused by an excessively large amount of money received by the payee, identification needs to be performed on the amount of money received, in order to improve the trust degree of the user and ensure the resource security of the user, in an optional implementation manner provided by this embodiment, after the information to be paid is input into the risk identification algorithm, the risk identification algorithm identifies whether the payee identification and the payer identification included in the information to be paid exist in an abnormal identification list, and identifying whether the amount of collection contained in the information to be paid is larger than a preset risk amount by using the risk identification algorithm. It should be noted that the risk identification algorithm may also output the payment risk level by identifying one or two of the payee identifier, the payer identifier and the amount to be collected, or may output the payment risk level by identifying other information included in the information to be paid.

For example, when a user shops in a supermarket, a merchant scans a payment code displayed by a user terminal by using a code scanning gun of the merchant when the user checks out, acquires a merchant identifier submitted by a PC (personal computer) of the merchant after the code scanning gun scans the payment code, a user identifier and the order details of the user shopping at this time, judges whether the user identifier is a blacklist, judges whether the merchant identifier is the blacklist, judges whether the amount of money received in the shopping order of the user shopping at this time is greater than a preset risk amount, and outputs a payment risk level according to a judgment result.

And step S104, if the payment risk level is a preset risk level, determining a reminding time length corresponding to the preset risk level, and generating reminding content based on the information to be paid.

The reminding duration refers to the reminding duration corresponding to the payment risk level, which is determined according to the payment risk level, and specifically, the higher the payment risk level is, the longer the corresponding reminding duration is; for example, if the payment risk level is low risk, the corresponding reminding duration is 3 seconds, and if the payment risk level is high risk, the corresponding reminding duration is 10 seconds. The reminding content comprises actual collection information of a collection party and actual payment information of a user (a payment party).

In practical application, after the payment risk identification, high-risk information to be paid is controlled, when the information of a payer or a payee is abnormal or the amount of the payment exceeds a certain amount, the process of displaying a payment code by the payer for payment is interrupted, the user needs to manually confirm the amount of the payment and the payment information, the subsequent deduction operation can be carried out under the condition of confirmation by the user, the payment process is interrupted, and the user cannot sense the actual reason of the interruption.

In specific implementation, in order to ensure consistency of payment experience of a user in a payment process, in an optional implementation manner provided in this embodiment, after information to be paid is input into a risk identification algorithm to perform payment risk identification, the risk identification algorithm outputs the information to be paid as high risk or low risk, when it is detected that a payee identifier or a payer identifier exists in an abnormal identifier list, a reminder of a blacklist is output, when an output payment risk level is high risk or low risk, the payment risk level is determined to be a preset risk level, and when it is determined that the payment risk level is the preset risk level, the reminder duration is specifically determined in the following manner:

if the payment risk level is a first risk level, determining that the reminding time length corresponding to the first risk level is the reminding time length;

if the payment risk level is a second risk level, determining that the reminding time length corresponding to the second risk level is the reminding time length;

wherein the preset risk level comprises: a first risk level and a second risk level.

Specifically, if the payment risk level is a low risk level, determining a reminding time corresponding to the low risk level, if the payment risk level is a high risk level, determining a reminding time corresponding to the high risk level, and if the information to be paid is a blacklist after the payment risk is identified, interrupting the payment process; the third risk level is that the state of the payee and/or the state of the payer are abnormal; and sending a cancel prompt carrying the abnormal details to the user terminal.

For example, the acquired information to be paid submitted by the PC of the merchant is input into a risk identification algorithm for payment risk identification, if the payment risk level is low risk, the corresponding reminding time is determined to be 3 seconds, if the payment risk level is high risk, the corresponding reminding time is determined to be 10 seconds, if the output payment risk level is a blacklist, the payment process is terminated, and a cancellation reminding that the payment is cancelled is sent to a user terminal corresponding to the payer identification included in the information to be paid, wherein the information to be paid is abnormal.

In addition, in order to further improve the trust degree of the user and improve the protection of user resources, only the low risk may be set as a preset risk level, that is, the first risk level is set as the preset risk level, the reminding duration corresponding to the first risk level is determined under the condition that the payment risk level is the first risk level, the user is made to submit a confirmation instruction to determine the security of the information to be paid under the condition that the payment risk level is the second risk level, the instruction to be confirmed is sent to the user terminal, and the payment instruction submitted by the user terminal under the condition that the user triggers a confirmation control configured on the reminding layer or inputs a confirmation operation instruction is obtained. In an optional implementation manner provided by this embodiment, in the process of determining the reminding duration, if the payment risk level is a first risk level, determining that the reminding duration corresponding to the first risk level is the reminding duration; and if the payment risk level is a second risk level, sending payment reminding content and a command to be confirmed to the user terminal so that the user terminal displays a confirmation control on a reminding layer displaying the payment reminding content.

In practical application, after the reminding duration is determined, the user terminal displays the reminding content according to the reminding duration, but the money receiving currency type of the payee is inconsistent with the money paying currency type of the payer, so that the payment code of the user is directly deducted after being scanned, the user is not trusted to the actual payment amount, the use experience of the user is reduced, and in order to avoid the problem that the user can sense the actual payment amount in the process of cross-currency payment and can also sense the actual payment amount of a merchant, in an optional implementation manner provided by the embodiment, the reminding content is determined according to the information to be paid in the following manner:

judging whether the money receiving type contained in the information to be paid is consistent with the payment type of the payer or not;

if yes, generating the reminding content according to the amount of collection, the identification of the collection party and/or the identification of the payment party in the information to be paid;

if not, calculating a payment amount corresponding to the collection amount contained in the information to be paid according to a currency conversion algorithm between the collection currency and the payment currency;

generating the reminder based on the collection amount, the collection currency, the payment amount, and/or the payment currency.

Specifically, the corresponding reminding duration is determined according to the payment of the information to be paid in a level mode, whether a money receiving currency type contained in the information to be paid is consistent with a payment currency type corresponding to a payer identification contained in the information to be paid is judged, if yes, reminding content is generated according to any one or two of a money receiving amount, a merchant identification and a user identification, and if not, reminding content is generated according to any one or more of the money receiving amount, the money receiving currency type, the payment amount and the payment currency type.

For example, determining that the money receiving type in the information to be paid is Japanese, but the money payment type corresponding to the payer is RMB, inquiring the exchange rate between the Japanese and the RMB, calculating the amount of the RMB to be paid by the payer according to the amount of money received in the information to be paid, and generating a text prompt of a prompt content according to the amount of money received in the Japanese, wherein the text prompt is 'Merchant Collection, JPYxxx'; soon to pay, CNYxxx ".

In addition, there may be a voucher in the account information of the payer, such as a discount, which can discount the payment amount of the user, in order to improve the perception degree of the user under the preferential condition, and also in order to ensure that the payee can notify the actual payment amount from the user terminal of the payer, in an optional implementation manner provided in this embodiment, in the process of determining the reminding content, the payment account of the payer is determined according to the payer identifier included in the to-be-paid information; inquiring whether a coupon exists in the payment account; if yes, judging whether the payment type corresponding to the payment identifier meets the use condition of the coupon; if yes, calculating the payment amount of the payer based on the preferential amount and the collection amount of the coupon; generating the reminder based on the collection amount and the payment amount; if not, directly determining the reminding content, and if not, directly determining the reminding content. Wherein the information to be paid comprises at least one of: the payment identifier, the collection amount, the information of the collection party, the information of the payment party and the collection currency.

Step S106, sending the reminding time length and the reminding content to a user terminal so that the user terminal displays the reminding content in a countdown mode according to the reminding time length.

In specific implementation, the user terminal performs countdown display by displaying a reminding layer generated based on the reminding content, the reminding layer displays countdown time, and the countdown display is finished when the countdown time is zero.

After the reminding time and the reminding content are determined, the reminding time and the reminding content are sent to a user terminal, the user terminal is enabled to display the reminding content according to the reminding time, a server can directly send the reminding time and the reminding content to the user terminal, the user terminal generates a reminding layer or a reminding pop-up window according to the reminding content, or generates a reminding page according to the reminding content, the reminding page and the reminding time are sent to the user terminal, the user terminal displays the reminding page through the layer or the pop-up window according to the reminding time, it needs to be noted that the user terminal needs to display a payment code before receiving the reminding time and the reminding content, and the user terminal displays the reminding layer on the upper layer of the payment code page under the condition that the payment code is scanned. When the user terminal performs countdown display on the reminding content through the reminding layer, a countdown time is displayed on the reminding layer, the countdown time takes the reminding time length as a timing starting point, and zero as a timing end point to perform countdown display; in addition, the reminding layer is located above the application page, and the reminding layer is displayed above the application page of the application program under the condition that the application program is accessed.

For example, when a payment code of the user terminal is scanned, the payment risk level output after payment risk identification is carried out on the acquired information to be paid is low risk, the reminding duration corresponding to the low risk is determined to be 3 seconds, and the text reminding of the reminding content is determined to be 'merchant cash collection, JPYxxx' according to the amount of the cash in the information to be paid; and sending the 3 seconds and the reminding content to a user terminal, and generating a reminding layer by the user terminal according to the reminding content to perform countdown display for 3 seconds on the upper layer of the pay code page.

And step S108, carrying out payment processing on the information to be paid when the countdown display is finished.

And the payment processing refers to deduction processing, namely deducting resources corresponding to the amount of collection from an account corresponding to the identifier of the payer according to the amount of collection contained in the information to be paid, and transferring the resources to the account corresponding to the identifier of the payee.

In a specific implementation, if a user does not submit a request for terminating a payment process during countdown display, after countdown display is finished, deducting the payment according to information to be paid, specifically, when it is detected that countdown display is finished, that is, when countdown time of countdown display is zero, deducting the payment according to the information to be paid, or when it is detected that a default payment instruction submitted by a user terminal when countdown display is finished, deducting the payment according to the default payment instruction, in an optional implementation manner provided in this embodiment, in a process of performing payment processing on the information to be paid when countdown display is finished, the payment processing is performed through two manners, and if countdown display is detected to be finished, the payment processing is performed on the information to be paid; or if a default payment instruction submitted by the user terminal when the countdown display is finished is detected, performing payment processing on the information to be paid according to the default payment instruction.

In practical applications, there may be a case where the amount of money collected by the payee shown in the reminding layer is abnormal and is inconsistent with the amount of payment notified under the subscriber line, or there may be a case where the user gives up shopping and the like and needs to terminate the payment flow, and in order to enable the user to autonomously select termination of the payment flow in specific implementation, in an optional implementation manner provided in this embodiment, if it is detected that the user terminal submits a first operation instruction input for the reminding layer, or if it is detected that the user terminal submits a second operation instruction, the payment processing is cancelled; and sending a cancellation notice that the payment processing has been cancelled to the user terminal. The user operation instruction refers to an operation instruction of the reminding layer for the user according to the operation reminding rendered on the reminding layer; the user operation instruction includes a first operation instruction for canceling payment submitted according to a cancellation prompt, a second operation instruction for canceling payment by triggering an objection control configured on the reminding layer, a third operation instruction for submitting a payment instruction by triggering a confirmation control, and a delay instruction corresponding to a delay request submitted by triggering a delay control or according to a delay operation prompt, where it should be noted that the user operation instruction may include the above four instructions, and may also include any one or more of the four instructions.

Specifically, the operation reminding text for terminating the payment process can be rendered on the reminding layer, such as "is the amount wrong? And double-clicking the page to stop payment ", when the user terminal detects that the user submits a corresponding instruction according to a prompt, receiving a first operation instruction submitted by the user terminal, or configuring an objection control for canceling payment on a reminding layer, receiving a second operation instruction submitted by the user terminal under the condition that the objection control is triggered, and canceling payment processing according to the first operation instruction or the second operation instruction.

For example, when a reminding layer is displayed to a user through a user terminal, the user finds that a collection amount set by a merchant is inconsistent with an offline-known collection amount, and finds that a text reminder "is incorrect in amount? And double-clicking the page to stop payment ", acquiring an operation instruction for canceling payment submitted by the user terminal after detecting that the user double-clicks the page of the reminding layer, canceling payment operation according to the operation instruction, and sending a reminder that the payment is cancelled to the user terminal.

In addition, the user cannot confirm the reminding content within the reminding duration, and needs to prolong the reminding time, for example, in the process that the user terminal displays a reminding layer carrying the reminding content to the user, a delay button is configured on the reminding layer; for another example, the user terminal renders a text reminder "press screen for 10 seconds again" on the reminder layer. In order to enable a user to extend a reminding time as required, in an optional implementation manner provided in this embodiment, if it is detected that the user terminal submits a delay instruction input for the reminding layer, a preset delay time is sent to the user terminal, so that the user terminal displays the reminding layer according to the preset delay time when the countdown display is finished; or, the user terminal suspends the countdown time according to the preset delay time. Specifically, the preset delay time is sent to the user terminal, and the user terminal can pause the countdown time displayed currently, and can display the countdown time according to the preset delay time after the current countdown is finished. It should be noted that, in order to prevent the user from extending maliciously, the delay right of the user is cancelled when the user delay time exceeds the preset delay time.

The following describes the payment processing method provided in this embodiment by taking an application of the payment processing method provided in this embodiment in a cross-currency payment scenario as an example, with reference to fig. 2. Referring to fig. 2, the payment processing method applied to the cross-currency payment scenario specifically includes step S202 to step S216.

And S202, inputting the information to be paid, which is obtained after the code scanning component scans the payment code, into a risk identification algorithm to identify the payment risk, and outputting the payment risk level.

Before that, the user terminal presents a payment code page carrying a payment code.

Step S204, judging whether the payment risk level is a preset risk level;

if yes, go to step S206 to step S208;

and if not, canceling the payment processing and sending a cancellation prompt carrying the abnormal details to the user terminal.

And step S206, determining the reminding time length corresponding to the payment risk level.

Step S208, judging whether the money receiving type contained in the information to be paid is consistent with the payment type of the payer;

if not, executing step S210 to step S216;

if yes, generating reminding content according to the collection amount contained in the information to be paid and sending the reminding content to the user terminal.

Step S210, calculating the payment corresponding to the amount of money according to the money conversion algorithm between the money type and the payment money.

Step S212, generating reminding content based on the collection amount, the collection currency, the payment currency and the payment amount.

Step S214, sending the reminding time length and the reminding content to the user terminal so that the user terminal can display the reminding content in a countdown mode according to the reminding time length.

The user terminal receives the reminding time length and the reminding content, generates a reminding layer according to the reminding content, performs countdown display above the payment code page according to the reminding time length, and submits a default payment instruction to the server under the condition that the countdown display is finished and the user operation instruction is not detected.

And step S216, receiving a default payment instruction submitted by the user terminal, and carrying out deduction processing on the information to be paid.

The following describes the payment processing method provided in this embodiment by taking an application of the payment processing method provided in this embodiment in a delayed reminding scenario as an example, with reference to fig. 3. Referring to fig. 3, the payment processing method applied to the delayed reminding scenario specifically includes steps S302 to S312.

Step S302, inputting the information to be paid acquired by scanning the payment code by the code scanning component into a risk identification algorithm to identify the payment risk, and outputting the payment risk level.

Step S304, judging whether the payment risk level is a first risk level;

if yes, go to step S306 to step S312;

if not, if the payment risk level is the second risk level, generating a command to be determined and payment reminding content, sending the command and the payment reminding content to the user terminal, and performing payment processing under the condition that the confirmation command submitted by the user terminal is obtained; and if the payment risk level is the third risk level, canceling the payment processing and sending a cancellation prompt carrying abnormal details to the user terminal.

Step S306, determining the reminding duration corresponding to the first risk level, and determining the reminding content according to the information to be paid.

And step S308, sending the reminding time length and the reminding content to the user terminal so that the user terminal can display the reminding content in a countdown mode according to the reminding time length.

The user terminal receives the reminding time and the reminding content, generates a reminding layer according to the reminding content, performs countdown display above the pay code page according to the reminding time, and configures a delay control on the reminding layer.

Step S310, receiving a delay instruction submitted by the user terminal, and sending a preset delay duration to the user terminal according to the delay instruction.

The user terminal receives the preset delay time and displays the reminding content according to the preset delay time when the countdown display is finished; and the user terminal submits a default payment instruction to the server under the condition that the preset delay time length is over and the user operation instruction is not detected.

Step S312, receiving a default payment instruction submitted by the user terminal, and carrying out deduction processing on the information to be paid.

In summary, in the payment processing method provided in this embodiment, first, information to be paid, which is obtained after a code scanning component scans a code, is input into a risk identification algorithm to identify a payment risk, and a payment risk level is output, then, under the condition that the payment risk level is a preset risk level, a reminding duration corresponding to the payment risk level is determined, a reminding content is generated based on the information to be paid, and then, the reminding duration and the reminding content are sent to a user terminal, so that the user terminal can perform countdown display on the reminding content according to the reminding duration, and finally, payment processing is performed on the information to be paid when the countdown display is finished, so that the trust of a user on payment is improved, and protection on user resources is further improved.

An embodiment of a payment reminder processing method provided in this specification:

referring to fig. 4, which shows a processing flow chart of a payment reminder processing method provided in this embodiment, referring to fig. 5, which shows a processing flow chart of a payment reminder processing method applied to a cross-currency payment scenario provided in this embodiment, referring to fig. 6, which shows a processing flow chart of a payment reminder processing method applied to a delayed reminder scenario provided in this embodiment.

Referring to fig. 4, the payment reminder processing method provided in this embodiment specifically includes the following steps S402 to S406.

Step S402, receiving the reminding time length and the reminding content which are sent by the server after the payment risk identification is carried out on the information to be paid.

In practical application, in the process of payment by displaying the payment code by the user, the merchant can finish payment by scanning the payment code by using the code scanning component, the user cannot confirm the amount and information of payment in advance in the process, the insecurity feeling exists in mind, and if the payment code is scanned and then the high-risk information to be paid is acquired, the payment process is interrupted and the actual reason of the interruption is not displayed to the user.

Taking a shopping scene of a user as an example, the user shows a payment code of the user when paying, and after a code scanning gun of a merchant scans the payment code of the user, payment information of the merchant and transaction details are uploaded to a server as information to be paid, so that in an optional implementation manner provided by the embodiment, before receiving the reminding duration and the reminding content, a payment code page carrying the payment code is displayed to the merchant; after the server acquires the information to be paid submitted by the user terminal, inputting the information to be paid into a risk identification algorithm for payment risk identification, outputting a payment risk level, judging whether the payment risk level is a preset risk level, if so, determining a reminding duration corresponding to the payment risk level, and generating reminding content according to the information to be paid.

For example, when a user shops in a supermarket and settles accounts, a payment code is displayed to a merchant, the merchant scans the payment code by using a code scanning gun of the merchant and submits a merchant identifier obtained by scanning the code, a user identifier and order details of the user in the shopping to a server, the server judges whether the user identifier is a blacklist, judges whether the merchant identifier is the blacklist, judges whether the amount of money received in a shopping order of the user in the shopping is greater than a preset risk amount, and outputs a payment risk level according to a judgment result.

In specific implementation, in order to ensure consistency of payment experience of a user in a payment process, after a server inputs information to be paid into a risk identification algorithm for payment risk identification, the risk identification algorithm outputs the information to be paid as high risk or low risk, when detecting that a payee identifier or a payer identifier exists in an abnormal identifier list, a reminder of a blacklist is output, when the output payment risk level is high risk or low risk, the payment risk level is determined to be a preset risk level, and under the condition that the payment risk level is determined to be the preset risk level, the server specifically determines the reminding duration in the following manner: if the payment risk level is a first risk level, determining that the reminding time length corresponding to the first risk level is the reminding time length; if the payment risk level is a second risk level, determining that the reminding time length corresponding to the second risk level is the reminding time length; wherein the preset risk level comprises: a first risk level and a second risk level.

Specifically, if the payment risk level is a low risk, determining a reminding time corresponding to the low risk, if the payment risk level is a high risk, determining a reminding time corresponding to the high risk, if the information to be paid after the payment risk identification is a blacklist, interrupting the payment process, and if the payment risk level is a third risk level, generating abnormal details and canceling the payment processing by the server; the third risk level is that the state of the payee and/or the state of the payer are abnormal; and receiving a cancel prompt carrying the abnormal details sent by the server.

For example, the server inputs the acquired information to be paid submitted by the PC of the merchant into a risk identification algorithm for payment risk identification, if the payment risk level is low risk, the corresponding reminding time length is determined to be 3 seconds, if the payment risk level is high risk, the corresponding reminding time length is determined to be 10 seconds, if the output payment risk level is a blacklist, the payment process is terminated, and a cancellation reminder that the information to be paid sent by the server is abnormal and the payment has been cancelled is received.

In addition, in order to further improve the trust level of the user and improve the protection on user resources, only the low risk may be set as a preset risk level, and when the payment risk level is a low risk, the reminding duration corresponding to the low risk is determined, and when the payment risk level is a high risk, the user is allowed to submit a confirmation instruction to determine the security of the information to be paid; if the payment risk level is a second risk level, receiving payment reminding content and a to-be-confirmed instruction which are sent by the server under the condition that the payment risk level of the to-be-paid information is the second risk level; and generating and displaying a reminding layer which contains the payment reminding content and is provided with a confirmation control.

Step S404, displaying a reminding layer carrying the reminding content, and performing countdown display on the reminding layer by taking the reminding time length as a countdown time length.

In specific implementation, the user terminal performs countdown display by displaying a reminding layer generated based on the reminding content, the reminding layer displays countdown time, and the countdown display is finished when the countdown time is zero. Optionally, the reminding content is displayed by counting down through the reminding layer, and the reminding layer displays counting down time; the reminding layer is located above an application page, the reminding layer is displayed above the application page of the application program under the condition that the application program is accessed, the countdown display is finished under the condition that the countdown time is zero, and the reminding layer can be displayed on the upper layer of a payment code page with payment codes.

It should be noted that, the reminding map layer may be generated by the user terminal according to the reminding content sent by the server, or may be generated and sent by the server based on the reminding content.

For example, under the condition that the payment code is scanned, the server identifies the payment risk level of the acquired information to be paid, then outputs the information to be paid, determines that the reminding duration corresponding to the low risk is 3 seconds, and determines that the text reminding of the reminding content is 'merchant collection, JPYxxx' according to the collection amount in the information to be paid; and receiving the 3 seconds and the reminding content sent by the server, and generating a reminding layer according to the reminding content to perform countdown display for 3 seconds on the upper layer of the pay code page.

In practical application, there may be a case that the amount of money collected by the payee shown in the reminding map layer is abnormal and is not consistent with the payment amount notified under the subscriber line, or there may be a case that the user gives up shopping and the like and needs to terminate the payment flow, and in specific implementation, in order to enable the user to autonomously select to terminate the payment flow, in an optional implementation manner provided in this embodiment,

if a first operation instruction input aiming at the reminding layer is detected under the condition that the countdown display is not finished, sending the first operation instruction to the server and terminating the countdown; alternatively, the first and second electrodes may be,

if the objection control configured by the reminding layer is detected to be triggered under the condition that the countdown display is not finished, sending a second operation instruction to the server and terminating the countdown;

and receiving and displaying a cancellation prompt sent by the server after the payment processing is cancelled.

Specifically, the operation reminding text for terminating the payment process can be rendered on the reminding layer, such as "is the amount wrong? And double-clicking the page to stop payment ", submitting a first operation instruction to a server when detecting that a user submits a corresponding instruction according to a prompt, or configuring a cancellation control for canceling payment on a reminding layer, sending a second operation instruction to the server under the condition that the cancellation control is triggered, canceling payment processing by the server according to the second operation instruction or the first operation instruction, receiving a cancellation prompt sent after the payment processing is canceled by the server, and displaying the cancellation prompt.

For example, when the reminding layer is displayed to the user, the user finds that the amount of money collected by the merchant is inconsistent with the amount known offline, and finds that a text reminder "is incorrect in amount? And double-clicking the page to stop payment, submitting a cancellation operation instruction to the server after detecting that the user double-clicks the page of the reminding image layer, and then receiving and displaying a reminder that the payment is cancelled, which is sent by the server after the payment operation is cancelled according to the cancellation operation instruction.

In addition, a user cannot confirm the reminding content within the reminding time, and needs to prolong the reminding time, so that in the process of displaying a reminding layer carrying the reminding content to the user, a delay button is configured on the reminding layer, and in order to enable the user to prolong the reminding time as required, in an optional implementation manner provided by this embodiment, when the triggering of the delay button is detected, a delay instruction is submitted to the server and a preset delay time sent by the server is received; pausing the countdown time displayed on the reminding layer according to the preset delay time; or, under the condition that the countdown time displayed by the countdown is zero, displaying the reminding layer according to the preset delay time. Specifically, after receiving the preset delay time, the countdown time of the current display may be suspended, or the display may be performed according to the preset delay time after the current countdown is finished. It should be noted that, in order to prevent the user from extending maliciously, the non-delayable reminder is sent to the user when the user delay times exceed the preset delay times.

Step S406, if the user operation instruction input for the reminding layer is not detected when the countdown display is finished, synchronizing a detection result with the server.

The user operation instruction refers to an operation instruction of the reminding layer for the user according to the operation reminding rendered on the reminding layer; the user operation instruction includes a first operation instruction for canceling payment submitted according to a cancellation prompt, a second operation instruction for canceling payment by triggering an objection control configured on the reminding layer, a third operation instruction for submitting a payment instruction by triggering a confirmation control, and a delay instruction corresponding to a delay request submitted by triggering a delay control or according to a delay operation prompt, where it should be noted that the user operation instruction may include the above four instructions, and may also include any one or more of the four instructions.

In specific implementation, in order to ensure consistency of user experience, if a user does not submit a request for terminating a payment process during countdown display, after countdown display is finished, a deduction operation is performed according to information to be paid, specifically, the deduction operation may be performed on the information to be paid when it is detected that countdown display is finished, that is, when countdown time of the countdown display is zero, or when it is detected that a default payment instruction submitted by a user terminal when countdown display is finished, the deduction operation may be performed according to a default payment instruction, in an optional implementation manner provided in this embodiment, if a user operation instruction input for the reminder layer is not detected when the countdown display is finished, the detection result is synchronized to the server in a process of synchronizing the detection result specifically in the following manner: and if the user operation instruction input aiming at the reminding layer is not detected under the condition that the countdown display is finished, submitting a default payment instruction to the server.

Specifically, when the displayed countdown timing time is zero and a user instruction input aiming at the reminding layer is not detected or a disagreement control configured in the reminding layer is not triggered, information of countdown ending is synchronized to the server, the server carries out money deduction on the information to be paid according to the information, or when the displayed countdown timing time is zero and a user instruction input aiming at the reminding layer is not detected or a disagreement control configured in the reminding layer is not triggered, a default payment instruction is submitted to the server, and the server carries out money deduction on the information to be paid according to the default payment instruction.

In specific implementation, after the server deducts money from information to be paid, the payment details generated by the server based on the payment are received, and the payment details and the payment completion prompt are displayed for the user.

For example, a prompt layer generated according to the prompt content is displayed on the upper layer of a pay code page for 3 seconds in a countdown mode, when the countdown display timing time is detected to be 0, a default payment instruction is submitted to the server, then payment details generated after the server performs payment processing based on the default payment instruction are received, and a payment completion prompt carrying the payment details is displayed.

The following describes the payment reminder processing method provided in this embodiment by taking an application of the payment reminder processing method provided in this embodiment in a payment scenario as an example, with reference to fig. 5. Referring to fig. 5, the payment reminding processing method applied to the payment scenario specifically includes steps S502 to S512.

Step S502, the payment code page with the payment code is displayed.

The server inputs information to be paid obtained after the code scanning component scans the payment code into a risk identification algorithm to carry out payment risk identification, outputs a payment risk level, judges whether the payment risk level is a preset risk level, and receives and displays a cancellation prompt carrying abnormal details and sent by the server for canceling payment processing if the payment risk level is not the preset risk level; if so, the server determines the reminding time length corresponding to the payment risk level and judges whether the money receiving type contained in the information to be paid is consistent with the payment type of the payer; if the information is consistent with the information to be paid, the server generates reminding content according to the collection amount contained in the information to be paid, if the information is inconsistent with the information to be paid, the server calculates the payment amount corresponding to the collection amount according to a currency conversion algorithm between the collection currency and the payment currency, and then the reminding content is generated based on the collection amount, the collection currency, the payment currency and the payment amount.

Step S504, receiving the reminding time length and the reminding content which are sent by the server after the payment risk identification is carried out on the information to be paid.

And S506, generating a reminding layer based on the reminding content, and displaying the reminding layer above the payment code page in a countdown mode according to the reminding duration.

Step S508, if the user operation instruction input for the reminding layer is not detected when the countdown display is finished, submitting a default payment instruction to the server.

Step S510, receiving the payment details and the payment result sent by the server after performing payment processing on the information to be paid.

And the server carries out payment processing on the information to be paid based on the default payment instruction.

And S512, generating a payment success prompt according to the payment details and displaying the payment success prompt.

The following describes the payment reminding processing method provided by this embodiment further by taking an application of the payment reminding processing method provided by this embodiment in a delayed reminding scene as an example, with reference to fig. 6. Referring to fig. 6, the payment alert processing method applied to the delayed alert scenario specifically includes steps S602 to S614.

Step S602, displaying the payment code page carrying the payment code.

The method comprises the steps that a server inputs information to be paid obtained after a code scanning component scans a payment code into a risk identification algorithm to carry out payment risk identification, outputs a payment risk level, judges whether the payment risk level is a first risk level, receives a command to be determined and payment reminding content generated by the server if the payment risk level is a second risk level if the payment risk level is not the first risk level, and generates a reminding layer which is rendered with the payment reminding content and is provided with a confirmation control to carry out countdown display; and if the payment risk level is the third risk level, receiving and displaying a cancellation prompt which is sent by the server and carries abnormal details and cancels the payment processing. If yes, the server determines the reminding duration corresponding to the first risk level, and determines the reminding content according to the information to be paid.

Step S604, receiving the reminding duration and the reminding content sent by the server after the server identifies the payment risk of the information to be paid.

And step S606, generating a reminding layer configured with a delay control based on the reminding content, and performing countdown display on the reminding layer above the pay code page according to the reminding duration.

Step S608, submitting a delay instruction to the server when detecting that the delay control is triggered, and receiving a preset delay duration sent by the server based on the delay instruction.

And step S610, when the countdown display is finished, carrying out countdown display on the reminding image layer according to the preset delay time.

Step S612, if the user operation instruction input for the reminding layer is not detected when the countdown display is finished, submitting a default payment instruction to the server.

And step S614, receiving and displaying the payment details and the payment result which are sent by the server after the payment processing is carried out on the information to be paid.

In summary, in the payment reminding processing method provided in this embodiment, first, a reminding time and a reminding content sent by a server after identifying payment risks of information to be paid are received, then, a reminding layer carrying the reminding content is displayed, and countdown display is performed on the reminding layer according to the reminding time, if a user operation instruction input to the reminding layer is not detected when the countdown display is finished, a detection result is synchronized to the server, so that differences are set according to different reminding times, but the user maintains consistency on the whole payment experience.

An embodiment of a payment processing apparatus provided in this specification is as follows:

in the above embodiments, a payment processing method is provided, and a payment processing apparatus is provided, which is described below with reference to the accompanying drawings.

Referring to fig. 7, a schematic diagram of a payment processing apparatus provided in this embodiment is shown.

Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions only need to refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.

The present embodiment provides a payment processing apparatus, including:

the identification module 702 is configured to input the information to be paid, which is obtained after the code scanning component scans the code, into a risk identification algorithm to perform payment risk identification, and output a payment risk level;

a generating module 704, configured to determine a reminding duration corresponding to a preset risk level if the payment risk level is the preset risk level, and generate a reminding content based on the information to be paid;

a sending module 706, configured to send the reminding duration and the reminding content to a user terminal, so that the user terminal performs countdown display on the reminding content according to the reminding duration;

a processing module 708 configured to perform payment processing on the information to be paid when the countdown display is over.

Optionally, the identifying module 702 includes:

and the risk identification submodule is configured to identify whether the payee identification and/or the payer identification contained in the information to be paid exist in the abnormal identification list by using the risk identification algorithm, and/or identify whether the amount of collection contained in the information to be paid is larger than a preset risk amount by using the risk identification algorithm.

Optionally, the generating module 704 includes:

a currency type judgment submodule configured to judge whether a collection currency type contained in the information to be paid is consistent with a payment currency type of a payer;

if not, operating a currency conversion sub-module, wherein the currency conversion sub-module is configured to calculate a payment amount corresponding to a collection amount contained in the information to be paid according to a currency conversion algorithm between the collection currency and the payment currency;

a reminder content generation sub-module configured to generate the reminder content based on the collection amount, the collection currency, the payment amount, and/or the payment currency.

Optionally, the user terminal performs the countdown display by displaying a reminding layer generated based on the reminding content, and the reminding layer displays the countdown time.

Optionally, the payment processing apparatus further includes:

a cancellation module configured to cancel the payment processing if it is detected that the user terminal submits a first operation instruction input for the reminding layer, or if it is detected that a second operation instruction submitted by the user terminal is provided; and sending a cancellation prompt that the payment processing is cancelled to the user terminal.

Optionally, the generating module 704 includes:

the first determining submodule is configured to determine that the reminding time length corresponding to the first risk level is the reminding time length if the payment risk level is the first risk level;

the second determining submodule is configured to determine that the reminding time length corresponding to the second risk level is the reminding time length if the payment risk level is the second risk level;

Optionally, the generating module 704 is specifically configured to determine that a reminding duration corresponding to the first risk level is the reminding duration if the payment risk level is the first risk level;

correspondingly, the payment processing device further comprises:

and the module to be confirmed is configured to send payment reminding content and a command to be confirmed to the user terminal if the payment risk level is a second risk level, so that the user terminal displays a confirmation control on a reminding layer displaying the payment reminding content.

Optionally, the processing module 708 includes:

the first processing submodule is configured to perform payment processing on the information to be paid if the countdown display is detected to be finished;

and the second processing module is configured to perform payment processing on the information to be paid according to a default payment instruction if the default payment instruction submitted by the user terminal when the countdown display is finished is detected.

Optionally, the payment processing apparatus further includes:

the time delay module is configured to send a preset time delay duration to the user terminal if the user terminal is detected to submit a time delay instruction input aiming at the reminding layer, so that the user terminal displays the reminding layer according to the preset time delay duration when the countdown display is finished; or, the user terminal suspends the countdown time according to the preset delay time.

Optionally, the payment processing apparatus further includes:

a third determination module configured to generate exception details and cancel the payment processing if the payment risk level is a third risk level; the third risk level is that the state of the payee and/or the state of the payer are abnormal; and sending a cancel prompt carrying the abnormal details to the user terminal.

Optionally, the generating module 704 includes:

the account determination submodule is configured to determine a payment account of a payer according to a payer identification contained in the information to be paid;

a coupon inquiry submodule configured to inquire whether a coupon exists in the payment account;

if yes, operating a condition judgment submodule, wherein the condition judgment submodule is configured to judge whether the payment type corresponding to the payment identifier meets the use condition of the coupon;

if yes, an amount calculation sub-module is operated, and the amount calculation sub-module is configured to calculate the payment amount of the payer based on the coupon amount and the collection amount of the coupon; generating the reminder based on the collection amount and the payment amount; wherein the information to be paid comprises at least one of: the payment identifier, the collection amount, the collector identifier, the payer identifier and the collection currency.

The embodiment of the payment reminding processing device provided by the specification is as follows:

in the above embodiment, a payment reminding processing method is provided, and a corresponding payment reminding processing apparatus is also provided, which is described below with reference to the accompanying drawings.

Referring to fig. 8, a schematic diagram of a payment reminder processing apparatus provided in this embodiment is shown.

The embodiment provides a payment reminding processing apparatus, including:

a receiving module 802, configured to receive a reminding duration and reminding content sent by the server after the payment risk identification is performed on the information to be paid;

the display module 804 is configured to display a reminding layer carrying the reminding content, and perform countdown display on the reminding layer by taking the reminding duration as a countdown duration;

a synchronization module 806, configured to synchronize a detection result with the server if the user operation instruction input for the reminder layer is not detected when the countdown display is finished.

Optionally, the reminding content is displayed by counting down through the reminding layer, and the reminding layer displays counting down time; the reminding layer is located above the application page, and the reminding layer is displayed above the application page of the application program under the condition that the application program is accessed.

Optionally, the payment reminder processing apparatus further includes:

the payment code display module is configured to display a payment code page carrying a payment code;

accordingly, the display module 804 includes:

and the layer display sub-module is configured to display the reminding layer on the upper layer of the payment code page.

Optionally, the payment reminder processing apparatus further includes:

a first submitting module, configured to send a first operation instruction to the server and terminate the countdown if the countdown display is not finished and the first operation instruction input for the reminding layer is detected;

the second submitting module is configured to send a second operation instruction to the server and terminate the countdown if the objection control configured by the reminding layer is detected to be triggered under the condition that the countdown display is not finished;

and the cancellation prompt receiving module is configured to receive and display the cancellation prompt sent by the server after the payment cancellation processing.

Optionally, the receiving module 802 includes:

the time length receiving module is configured to receive reminding content sent by the server under the condition that the payment risk level of the information to be paid is a first risk level and reminding time length corresponding to the first risk level;

correspondingly, the payment reminder processing apparatus further includes:

the to-be-confirmed instruction receiving module is configured to receive payment reminding content and to-be-confirmed instructions which are sent by the server under the condition that the payment risk level of the to-be-paid information is a second risk level;

and the layer to be confirmed generating module is configured to generate and display a reminding layer which contains the payment reminding content and is configured with a confirmation control.

Optionally, the payment reminder processing apparatus further includes:

the abnormal detail receiving module is configured to receive and display a cancellation prompt which is sent by the server and carries the abnormal detail under the condition that the payment risk level of the information to be paid is a third risk level; wherein the third risk level is a payee status and/or payer status anomaly.

Optionally, the payment reminder processing apparatus further includes:

the delay instruction submitting module is configured to submit a delay instruction to the server and receive a preset delay time sent by the server;

the pause module is configured to pause the countdown time displayed on the reminding layer according to the preset delay time;

and the time delay display module is configured to display the reminding layer according to the preset time delay duration under the condition that the countdown time displayed by the countdown is zero.

Optionally, the synchronization module 806 includes:

and the payment instruction submitting sub-module is configured to submit a default payment instruction to the server if the user operation instruction input aiming at the reminding layer is not detected under the condition that the countdown display is finished.

The embodiment of a payment processing device provided by the specification is as follows:

corresponding to the above-described payment processing method, based on the same technical concept, one or more embodiments of the present specification further provide a payment processing apparatus for executing the above-described payment processing method, and fig. 9 is a schematic structural diagram of the payment processing apparatus provided in one or more embodiments of the present specification.

As shown in fig. 9, the payment processing apparatus may have a relatively large difference due to different configurations or performances, and may include one or more processors 901 and a memory 902, where one or more stored applications or data may be stored in the memory 902. Memory 902 may be, among other things, transient storage or persistent storage. The application stored in memory 902 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in the payment processing apparatus. Still further, the processor 901 may be configured to communicate with the memory 902 to execute a series of computer-executable instructions in the memory 902 on the payment processing device. The payment processing apparatus may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input-output interfaces 905, one or more keyboards 906, and the like.

In one particular embodiment, a payment processing apparatus 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 processing apparatus, and configured for execution by the one or more processors the one or more programs include computer-executable instructions for:

inputting the information to be paid obtained after the code scanning component scans the codes into a risk identification algorithm to identify the payment risk, and outputting the payment risk level;

if the payment risk level is a preset risk level, determining a reminding time length corresponding to the preset risk level, and generating reminding content based on the information to be paid;

sending the reminding time length and the reminding content to a user terminal so that the user terminal performs countdown display on the reminding content according to the reminding time length;

and carrying out payment processing on the information to be paid when the countdown display is finished.

Optionally, if the payment risk level is a preset risk level, determining a reminding duration corresponding to the preset risk level includes:

accordingly, the computer-executable instructions, when executed, further comprise:

and if the payment risk level is a second risk level, sending payment reminding content and a command to be confirmed to the user terminal so that the user terminal displays a confirmation control on a reminding layer displaying the payment reminding content.

An embodiment of a payment reminder processing apparatus provided in this specification is as follows:

corresponding to the above-described payment reminder processing method, based on the same technical concept, one or more embodiments of the present specification further provide a payment reminder processing apparatus for executing the above-described payment reminder processing method, and fig. 10 is a schematic structural diagram of the payment reminder processing apparatus provided in one or more embodiments of the present specification.

As shown in fig. 10, the payment reminder processing apparatus may have a relatively large difference due to different configurations or performances, and may include one or more processors 1001 and a memory 1002, and one or more stored applications or data may be stored in the memory 1002. Memory 1002 may be, among other things, transient storage or persistent storage. The application stored in memory 1002 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in the payment alert processing apparatus. Still further, the processor 1001 may be configured to communicate with the memory 1002, executing a series of computer executable instructions in the memory 1002 on the payment alert processing device. The payment reminder processing apparatus may 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, etc.

In a particular embodiment, the payment advice processing arrangement comprises 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 comprise one or more modules, and each module may comprise a series of computer-executable instructions for the payment advice processing arrangement, and the one or more programs being configured for execution by the one or more processors comprise computer-executable instructions for:

receiving a reminding time length and reminding content which are sent by a server after payment risk identification is carried out on information to be paid;

displaying a reminding layer carrying the reminding content, and performing countdown display on the reminding layer by taking the reminding time length as a countdown time length;

and if the user operation instruction input aiming at the reminding layer is not detected under the condition that the countdown display is finished, synchronizing a detection result to the server.

An embodiment of a storage medium provided in this specification is as follows:

corresponding to the above-described payment processing method, based on the same technical concept, one or more embodiments of the present specification further provide a storage medium.

The storage medium provided in this embodiment is used to store computer-executable instructions, and when executed, the computer-executable instructions implement the following processes:

accordingly, the computer-executable instructions, when executed, further implement the following:

Another storage medium embodiment provided in this specification is as follows:

on the basis of the same technical concept, one or more embodiments of the present specification further provide a storage medium corresponding to the payment reminder processing method described above.

It should be noted that the embodiment of the storage medium in this specification and the embodiment of the payment processing method in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the foregoing corresponding method, and repeated details are not described here.

Characteristic embodiments of the present specification have been described above. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. Additionally, the processes depicted in the accompanying figures do not necessarily require the order in which features are shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 30's of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a characteristic Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardbylangue (Hardware Description Language), vhjhdul, and vhigh-Language, which are currently used in most general. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, 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, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be conceived to be both a software module implementing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.

One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description 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, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims

1. A payment processing method is applied to a server and comprises the following steps:

2. The payment processing method of claim 1, entering the payment information into a risk identification algorithm for payment risk identification, comprising:

and identifying whether a payee identifier and/or a payer identifier contained in the information to be paid exists in an abnormal identifier list by using the risk identification algorithm, and/or identifying whether a payee amount contained in the information to be paid is larger than a preset risk amount by using the risk identification algorithm.

3. The payment processing method of claim 1, the generating reminder content based on the information to be paid, comprising:

4. The payment processing method of claim 1, wherein the user terminal performs the countdown displaying by displaying a reminding layer generated based on the reminding content, and the reminding layer displays a countdown time.

5. The payment processing method of claim 4, further comprising:

if the user terminal is detected to submit a first operation instruction input aiming at the reminding layer, or if a second operation instruction submitted by the user terminal is detected, the payment processing is cancelled;

and sending a cancellation prompt that the payment processing is cancelled to the user terminal.

6. The payment processing method according to claim 1, wherein if the payment risk level is a preset risk level, determining a reminding duration corresponding to the preset risk level comprises:

7. The payment processing method of claim 1, wherein if the payment risk level is a preset risk level, determining a reminding duration corresponding to the preset risk level comprises:

correspondingly, the payment processing method further comprises the following steps:

8. The payment processing method of claim 1, the payment processing of the information to be paid at the end of the countdown display comprising:

if the countdown display is detected to be finished, payment processing is carried out on the information to be paid;

alternatively, the first and second electrodes may be,

and if a default payment instruction submitted by the user terminal when the countdown display is finished is detected, performing payment processing on the information to be paid according to the default payment instruction.

9. The payment processing method of claim 4, further comprising:

if the fact that the user terminal submits a delay instruction input aiming at the reminding layer is detected, sending a preset delay time to the user terminal, so that the user terminal displays the reminding layer according to the preset delay time when the countdown display is finished; or, the user terminal suspends the countdown time according to the preset delay time.

10. The payment processing method of claim 1, further comprising:

if the payment risk level is a third risk level, generating abnormal details and canceling the payment processing; the third risk level is that the state of the payee and/or the state of the payer are abnormal;

and sending a cancel prompt carrying the abnormal details to the user terminal.

11. The payment processing method of claim 1, the generating reminder content based on the information to be paid, comprising:

determining a payment account of a payer according to the payer identification contained in the information to be paid;

inquiring whether a coupon exists in the payment account;

if yes, judging whether the payment type corresponding to the payment identifier meets the use condition of the coupon;

if yes, calculating the payment amount of the payer based on the preferential amount and the collection amount of the coupon;

generating the reminder based on the collection amount and the payment amount;

wherein the information to be paid comprises at least one of: the payment identifier, the collection amount, the collector identifier, the payer identifier and the collection currency.

12. A payment reminding processing method is applied to a user terminal and comprises the following steps:

13. The payment reminder processing method of claim 12, the reminder content being displayed countdown through the reminder layer, and the reminder layer being displayed with a countdown time; the reminding layer is located above the application page, and the reminding layer is displayed above the application page of the application program under the condition that the application program is accessed.

14. The payment reminding processing method according to claim 12, wherein before the step of receiving the reminding duration and the reminding content sent by the server after identifying the payment risk of the information to be paid is executed, the method further comprises:

displaying a payment code page carrying a payment code;

correspondingly, the displaying of the reminding layer carrying the reminding content includes:

and displaying the reminding picture layer on the upper layer of the payment code page.

15. The payment reminder processing method of claim 12, further comprising:

if a first operation instruction input aiming at the reminding layer is detected under the condition that the countdown display is not finished, sending the first operation instruction to the server and terminating the countdown;

alternatively, the first and second electrodes may be,

16. The payment reminding processing method according to claim 12, wherein the receiving of the reminding duration and the reminding content sent by the server after the payment risk identification of the information to be paid comprises:

receiving reminding content sent by the server under the condition that the payment risk level of the information to be paid is a first risk level and reminding duration corresponding to the first risk level;

correspondingly, the payment reminder processing method further comprises the following steps:

receiving payment reminding content and a to-be-confirmed instruction which are sent by the server under the condition that the payment risk level of the to-be-paid information is a second risk level;

and generating and displaying a reminding layer which contains the payment reminding content and is provided with a confirmation control.

17. The payment reminder processing method of claim 12, further comprising:

receiving and displaying a cancellation prompt which is sent by the server and carries abnormal details under the condition that the payment risk level of the information to be paid is a third risk level;

wherein the third risk level is a payee status and/or payer status anomaly.

18. The payment reminder processing method of claim 13, further comprising:

submitting a delay instruction to the server and receiving a preset delay time sent by the server;

pausing the countdown time displayed on the reminding layer according to the preset delay time;

alternatively, the first and second electrodes may be,

and displaying the reminding picture layer according to the preset delay time under the condition that the countdown time displayed by the countdown is zero.

19. The payment reminder processing method according to claim 12, wherein if the countdown display is over, and a user operation instruction input for the reminder layer is not detected, synchronizing a detection result to the server includes:

and if the user operation instruction input aiming at the reminding layer is not detected under the condition that the countdown display is finished, submitting a default payment instruction to the server.

20. A payment processing apparatus, operating at a server, comprising:

the identification module is configured to input the information to be paid obtained after the code scanning component scans the codes into a risk identification algorithm to carry out payment risk identification and output a payment risk level;

the generating module is configured to determine a reminding time length corresponding to a preset risk level if the payment risk level is the preset risk level, and generate reminding content based on the information to be paid;

the sending module is configured to send the reminding time length and the reminding content to a user terminal so that the user terminal can display the reminding content in a countdown mode according to the reminding time length;

the processing module is configured to perform payment processing on the information to be paid when the countdown display is finished.

21. A payment reminding processing device, which runs on a user terminal, comprises:

the receiving module is configured to receive the reminding duration and the reminding content which are sent by the server after the payment risk identification is carried out on the information to be paid;

the display module is configured to display a reminding layer carrying the reminding content, and perform countdown display on the reminding layer by taking the reminding duration as a countdown duration;

and the synchronization module is configured to synchronize a detection result to the server if the user operation instruction input for the reminding layer is not detected under the condition that the countdown display is finished.

22. A payment processing apparatus comprising:

a processor; and the number of the first and second groups,

a memory configured to store computer-executable instructions that, when executed, cause the processor to:

23. A payment advice processing arrangement comprising:

a processor; and the number of the first and second groups,

24. A storage medium storing computer-executable instructions that when executed implement the following:

sending the reminding time length and the reminding content to a user terminal so that the user terminal can display the reminding content in a countdown mode according to the reminding time length;

25. A storage medium storing computer-executable instructions that when executed implement the following: