A graphic code verification method and device

Abstract

One or more embodiments of the present specification provide a method and device for verifying a graphic code, the method comprising: performing a scanning process on a target graphic code to generate a scanning result for the target graphic code; judging whether the target graphic code meets a preset condition based on the generated scanning result; if so, determining that the current scanning operation is an operation requesting verification of whether the target graphic code belongs to the applicant user; and generating first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user. By generating targeted feedback information based on the graphic code verification result, the user is informed that the feedback information is generated for the verification requirement of the graphic code requested by the user, and is not a simple error message. In this way, the feedback result of the authenticity verification of the graphic code that has been completed for the user's graphic code verification requirement can be delivered to the user, thereby improving the interaction accuracy between the terminal and the user, and thereby improving the user experience.

Description

[0001] This application is a divisional application of the Chinese patent application submitted to the China Patent Office on December 11, 2018, with application number 201811508333.X and invention name “A Graphic Code Verification Method and Device”. Technical Field

[0002] One or more aspects of this specification relate to the field of information verification, and in particular, to a method and device for verifying a graphic code. Background Art

[0003] At present, graphic codes are used more and more widely in people's daily lives. For example, scanning codes to add friends, scanning codes to query product information, scanning codes to pay, etc. Among them, for the function of collecting payments by scanning codes, merchants need to apply to graphic code distribution agencies for payment QR codes for their respective accounts. Usually, after users receive the payment QR code they applied for, they need to use the scanning application of the account that has been logged in to scan the payment QR code to verify whether the payment QR code is the one they applied for, so as to ensure that when subsequent buyers scan the payment QR code to make payments, the buyer's payment amount can be accurately transferred to the merchant account that needs to be paid.

[0004] However, currently, when it is recognized that the payment account corresponding to the graphic code is consistent with the application account used for scanning the code, the mobile terminal still enters the interface for transferring money to the user and directly gives an error prompt on the transfer interface. For example, it prompts that the accounts of both parties are the same, please check and try again, payment to oneself is not supported, etc., which makes it impossible for users to feel that the prompt information is feedback for the graphic code verification requirements they requested, resulting in a poor user experience. Summary of the invention

[0005] The purpose of one or more embodiments of the present specification is to provide a method and device for verifying a graphic code, by generating targeted feedback information based on the graphic code verification result, so that users can know that the feedback information is generated in response to their request for verification of the graphic code they applied for, and is not a simple error prompt. In this way, the feedback result of the authenticity verification of the graphic code that has been completed in response to the user's graphic code verification requirement can be delivered to the user, thereby improving the accuracy of the interaction between the terminal and the user, and thereby improving the user experience.

[0006] To solve the above technical problems, one or more embodiments of this specification are implemented as follows:

[0007] One or more embodiments of this specification provide a method for verifying a graphic code, including:

[0008] Scanning a target graphic code to generate a scanning result for the target graphic code, wherein the target graphic code is a payment code distributed to the applicant user;

[0009] According to the generated scanning result, judging whether the target graphic code meets the preset conditions;

[0010] If the judgment result is that the preset condition is met, then determining that the current code scanning operation is an operation requesting to verify whether the target graphic code belongs to the applicant user; and,

[0011] The first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated.

[0012] One or more embodiments of this specification provide a graphic code verification device, including:

[0013] A scanning result determination module, used to perform scanning processing on a target graphic code and generate a scanning result for the target graphic code, wherein the target graphic code is a payment code distributed to an applicant user;

[0014] A graphic code judging module, used to judge whether the target graphic code meets a preset condition according to the generated scanning result;

[0015] A verification result determination module, for determining, if the result of the determination is that a preset condition is met, that the current code scanning operation is an operation requesting verification of whether the target graphic code belongs to the applicant user; and

[0016] The interactive information generating module is used to generate the first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user.

[0017] One or more embodiments of the present specification provide a graphic code verification device, including: a processor; and

[0018] a memory arranged to store computer executable instructions which, when executed, cause the processor to:

[0019] Scanning a target graphic code to generate a scanning result for the target graphic code, wherein the target graphic code is a payment code distributed to the applicant user;

[0020] According to the generated scanning result, judging whether the target graphic code meets the preset conditions;

[0021] If the judgment result is that the preset condition is met, then determining that the current code scanning operation is an operation requesting to verify whether the target graphic code belongs to the applicant user; and,

[0022] The first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated.

[0023] One or more embodiments of this specification provide a storage medium for storing computer-executable instructions, wherein the executable instructions implement the following process when executed:

[0024] Scanning a target graphic code to generate a scanning result for the target graphic code, wherein the target graphic code is a payment code distributed to the applicant user;

[0025] According to the generated scanning result, judging whether the target graphic code meets the preset conditions;

[0026] If the judgment result is that the preset condition is met, then determining that the current code scanning operation is an operation requesting to verify whether the target graphic code belongs to the applicant user; and,

[0027] The first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated.

[0028] The graphic code verification method and device in one or more embodiments of the present specification scans the target graphic code and generates a scanning result for the target graphic code; based on the generated scanning result, determines whether the target graphic code meets the preset conditions; if so, determines that this scanning operation is an operation requesting verification of whether the target graphic code belongs to the applicant user; generates first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user. In the process of automatically identifying whether the target graphic code is the graphic code applied for by the user based on the scanning operation of the user, targeted feedback information is generated based on the graphic code verification result, so that the user knows that the feedback information is generated for the verification requirement of the respective applied graphic code requested by the user, and is not a simple error prompt. In this way, the feedback result of the authenticity verification of the graphic code that has been completed for the user's graphic code verification requirement can be delivered to the user, thereby improving the accuracy of the interaction between the terminal and the user, and thus improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in one or more of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0030] Figure 1 A schematic diagram of an application scenario of a graphic code verification method provided by one or more embodiments of this specification;

[0031] Figure 2 A schematic diagram of a first flow chart of a graphic code verification method provided in one or more embodiments of this specification;

[0032] Figure 3 A second flow chart of a method for verifying a graphic code provided in one or more embodiments of this specification;

[0033] Figure 4 A third flow chart of a method for verifying a graphic code provided in one or more embodiments of this specification;

[0034] Figure 5 A fourth flow chart of a method for verifying a graphic code provided in one or more embodiments of this specification;

[0035] Figure 6 A schematic diagram of the implementation principle of abnormal feedback of graphic code verification in the graphic code verification method provided in one or more embodiments of this specification;

[0036] Figure 7 A schematic diagram of the module composition of a graphic code verification device provided in one or more embodiments of this specification;

[0037] Figure 8 A schematic diagram of the structure of a graphic code verification device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0038] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only one or more partial embodiments of this specification, rather than all embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of one or more embodiments of this specification.

[0039] One or more embodiments of the present specification provide a method and device for verifying a graphic code, which generates targeted feedback information based on the graphic code verification result, so that users can know that the feedback information is generated in response to their request for verification of the graphic code they applied for, and is not a simple error prompt. In this way, the feedback result of completing the authenticity verification of the graphic code in response to the user's graphic code verification requirement can be delivered to the user, thereby improving the accuracy of the interaction between the terminal and the user, and thereby improving the user experience.

[0040] Among them, when the user receives the target graphic code mailed by the graphic code distributor, the user needs to verify the authenticity of the target graphic code, that is, to verify whether the target graphic code is the payment code applied by the user, and when the verification result is that the target graphic code is the payment code applied by the user, the user is displayed with targeted interactive information, so that the user can perceive that the interactive information is generated in response to the verification demand of the graphic code applied by the user; Figure 1 A schematic diagram of an application scenario of a graphic code verification method provided in one or more embodiments of this specification, such as Figure 1 As shown in FIG. 1 , the process of verifying the target graphic code specifically includes:

[0041] First, after monitoring the user's scanning trigger operation, the mobile terminal scans the target graphic code and determines the scanning result for the target graphic code, wherein the mobile terminal may be a smart phone, a tablet computer, etc., and the target graphic code may be a payment QR code distributed to the applicant user;

[0042] Then, according to the obtained scanning result, it is determined whether the target graphic code meets the preset conditions. Specifically, the scanning result may include: the transfer account information corresponding to the target graphic code obtained by scanning the code, and then it can be determined whether the transfer account corresponding to the target graphic code is consistent with all the application accounts of the user applying for the target graphic code, so as to determine whether the target graphic code meets the preset conditions;

[0043] If the result of the judgment is not satisfied, it means that the current code scanning operation may be a transfer operation, so you can jump to the payment interface that provides transfer to the receiving account corresponding to the target graphic code;

[0044] If the judgment result is satisfied, it is determined that this scanning operation is an operation requesting verification of whether the target graphic code belongs to the applicant user, and interactive information is generated to indicate that the graphic code verification is successful and the target graphic code belongs to the applicant user. For example, a prompt message "The target graphic code is the payment code you applied for, please feel free to use it" is generated and displayed on the display interface. In this way, the feedback result of completing the graphic code authenticity verification for the user's graphic code verification requirements can be delivered to the user, thereby improving the interaction accuracy between the terminal and the user, and thereby improving the user experience.

[0045] Figure 2 A first flow chart of a method for verifying a graphic code provided in one or more embodiments of this specification, Figure 2 The method in can be Figure 1 The mobile terminal in the execution, such as Figure 2 As shown, the method comprises at least the following steps:

[0046] S201, scanning the target graphic code to generate a scanning result for the target graphic code, wherein the target graphic code is a payment code distributed to the applicant user, that is, a payment QR code applied by the applicant user to the graphic code distributor, so that subsequent buyers can transfer payment to the applicant user by scanning the payment QR code;

[0047] S202, judging whether the target graphic code meets a preset condition according to the generated scanning result, wherein the scanning result includes: first account information obtained by scanning the target graphic code;

[0048] The first account information obtained is compared with the second account information of the login account currently used for scanning the code, and whether the target graphic code meets the preset conditions is determined according to the comparison result;

[0049] Specifically, the second account information of the login account currently used for scanning the code is obtained, the first account information is compared with the second account information for consistency, and whether the target graphic code meets the preset conditions is determined according to the consistency comparison result. If the comparison result is consistent, it is determined that the target graphic code meets the preset conditions; if the comparison result is inconsistent, it is determined that the target graphic code does not meet the preset conditions;

[0050] If the judgment result is that the preset condition is met, then S203 is executed to determine whether the current code scanning operation is an operation requesting verification of whether the target graphic code belongs to the applicant user; and

[0051] S204, generating first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user;

[0052] Specifically, if the judgment result is that the preset condition is met, it means that the first account information is consistent with the second account information, that is, the transfer account corresponding to the target graphic code is the same as the application account used by the user to apply for the graphic code, that is, the user who applied for the target graphic code is the user himself, and the target graphic code can be used normally for payment. Therefore, it can be determined that the actual demand for this code scanning operation is to verify whether the graphic code is the user's own, rather than the initiated transfer payment operation. At this time, there is no need to open the transfer function, but to prompt the user that the QR code is correct. For example, in a specific embodiment, the above-mentioned first interactive information can be: the target graphic code is the payment code you applied for, please feel free to use it.

[0053] In one or more embodiments of the present specification, targeted feedback information is generated based on the graphic code verification result to let users know that the feedback information is generated in response to their request for verification of the graphic code they applied for, and is not a simple error prompt. In this way, the feedback result of the graphic code authenticity verification that has been completed in response to the user's graphic code verification requirement can be delivered to the user, thereby improving the accuracy of the interaction between the terminal and the user, and thereby improving the user experience.

[0054] Among them, Figure 3 As shown, the above S201 performs a scanning process on the target graphic code to generate a scanning result for the target graphic code, specifically including:

[0055] S2011, using a code scanning application to scan the target graphic code to obtain first account information corresponding to the target graphic code;

[0056] For example, when a user receives a payment QR code applied for by a user mailed by a graphic code distributor, the user needs to activate the payment QR code and verify whether the payment QR code is the payment code applied for by the user himself. Specifically, the user opens the "Scan" function in the Alipay application logged in with the application user account on the mobile terminal and aims at the target graphic code. At this time, after the mobile terminal detects the user's scanning trigger operation, it uses the scanning application to scan the target graphic code and obtains the first account information used to make the target graphic code;

[0057] S2012: Determine the acquired first account information as a scan result generated for the target graphic code, that is, the scan result includes the first account information used to generate the target graphic code.

[0058] Correspondingly, the above S202 determines whether the target graphic code meets the preset conditions according to the generated scanning result, specifically including:

[0059] S2021, obtaining second account information used to log in to the code scanning application, wherein the second account information may be account information of an applicant who requests to scan the target graphic code, so that by comparing the first account information with the second account information, it is determined whether the account information carried in the target graphic code is the account information used by the applicant to apply for the target graphic code;

[0060] S2022, determining whether the first account information in the scan result is consistent with the acquired second account information;

[0061] If the judgment result is consistent, it is determined that the target graphic code meets the preset conditions, that is, the account information carried in the target graphic code is the same as the account information used by the applicant to apply for the target graphic code, which means that the target graphic code is the payment QR code applied for by the applicant;

[0062] If the judgment result is inconsistent, it is determined that the target graphic code does not meet the preset conditions, that is, the account information carried in the target graphic code is different from the account information used to scan the code to log in, then it means that the target graphic code is the payment QR code that the user needs to transfer money to the merchant, or the process of graphic code verification for the applicant user indicates that for some reason the target graphic code is inconsistent with the payment QR code applied for by the applicant user. At this time, the user cannot use the target graphic code as a payment QR code and needs to provide feedback on the graphic code abnormality to the graphic code distributor.

[0063] Among them, for the case where the account information carried in the target graphic code is different from the account information used for scanning and logging in, one situation is that the user normally scans the merchant's payment QR code and needs to transfer money to the merchant. At this time, the corresponding transfer interface can be directly entered, such as Figure 4 As shown, after the above S202 determines whether the target graphic code meets the preset conditions according to the generated scanning result, it also includes:

[0064] If the result of the judgment is that the preset condition is not met, S205 is executed to jump to a payment interface for providing a transfer to the payment account corresponding to the target graphic code.

[0065] Specifically, when the account information carried in the target graphic code is different from the account information used to scan the code to log in, it is very likely that this scanning operation is the process of the user scanning the code to transfer payment to the seller, that is, the target QR code is the payment QR code of the merchant that the user needs to pay. At this time, the corresponding transfer interface can be automatically entered so that the user can complete the operation of transferring payment to the merchant.

[0066] Among them, for the case where the account information carried in the target graphic code is different from the account information used for scanning and logging in, another case is that when the user verifies whether the target graphic code is the QR code for receiving payment that he or she has applied for, the verification fails, that is, the target graphic code scanned by the user is not the QR code for payment that he or she has applied for. At this time, in order to facilitate the user to quickly complete the verification abnormality feedback, not only does it enter the corresponding transfer interface, but it also provides the user with a one-click abnormality feedback trigger control, such as Figure 5 As shown, after the above S205 jumps to the payment interface for providing a transfer to the payment account corresponding to the target graphic code, it also includes:

[0067] S206, displaying an information feedback control for reporting a graphic code verification failure on the payment interface that has been redirected;

[0068] S207, determining whether the user performs a touch operation on the information feedback control on the payment interface, wherein the touch operation may be a click operation;

[0069] If the judgment result is yes, execute S208 and send feedback information of graphic code verification failure to the graphic code distribution server. Specifically, when it is detected that the user performs a touch operation on the information feedback control, it can be determined that this scanning operation is an operation to request verification of whether the target graphic code belongs to the applicant user and the graphic code verification result fails, indicating that the user needs to feedback to the graphic code distributor feedback information used to characterize that the graphic code is not the payment code applied for by the user.

[0070] In one or more embodiments of the present specification, taking into account the situation where the account information carried in the target graphic code is different from the account information used for scanning the code to log in, there may be two different situations. One situation is that the user normally scans the merchant's payment QR code and needs to transfer money to the merchant. The other situation is that the user finds that the verification fails when verifying whether the target graphic code is the payment QR code applied for by himself. Among them, in the case where the target graphic code is wrong, in order to facilitate the user to quickly complete the verification exception feedback, not only the corresponding transfer interface is entered, but also a one-click exception feedback trigger control is provided to the user. In this way, the user does not need to contact customer service separately, nor does the user need to enter the designated interface for exception feedback, and the graphic code verification failure result can be fed back to the corresponding responsible terminal with one click.

[0071] like Figure 6 As shown, a schematic diagram of the implementation principle of abnormal feedback of graphic code verification in the graphic code verification method is given, specifically:

[0072] If the result of the judgment is that the target graphic code does not meet the preset conditions, jump to a payment interface for providing a transfer to the payment account corresponding to the target graphic code; and,

[0073] On the payment interface that is redirected, an information feedback control for feedback of graphic code verification failure is displayed, so that the user can click the information feedback control to feedback the graphic code verification failure result to the corresponding responsible terminal with one click.

[0074] In order for the user to quickly identify the trigger control for providing abnormal feedback, corresponding prompt information may be displayed on the trigger control. Specifically, the above S206 displays an information feedback control for providing feedback on the failure of the graphic code verification on the payment interface entered by the jump, which specifically includes:

[0075] Step 1: generating second interactive information for prompting the user to feedback that the graphic code verification fails, wherein the second interactive information may be "verification abnormality feedback";

[0076] Step 2: On the payment interface that is redirected, an information feedback control whose summary information is the second interactive information mentioned above is displayed, so that the user can quickly identify the information feedback control used to provide abnormal feedback, and by clicking the information feedback control, the result of the graphic code verification failure can be fed back to the corresponding responsible terminal with one click.

[0077] The graphic code verification method in one or more embodiments of the present specification performs a scanning process on the target graphic code to generate a scanning result for the target graphic code; based on the generated scanning result, it is determined whether the target graphic code meets the preset conditions; if so, it is determined that this scanning operation is an operation for requesting verification of whether the target graphic code belongs to the applicant user; and first interactive information is generated to indicate that the graphic code verification is successful and the target graphic code belongs to the applicant user. By generating targeted feedback information based on the graphic code verification result, the user is informed that the feedback information is generated for the verification requirements of the graphic code they requested, and is not a simple error message. In this way, the feedback result of the authenticity verification of the graphic code that has been completed for the user's graphic code verification requirements can be delivered to the user, thereby improving the interaction accuracy between the terminal and the user, and thus improving the user experience.

[0078] Corresponding to the above Figures 1 to 6 The graphic code verification method described above is based on the same technical concept, and one or more embodiments of this specification also provide a graphic code verification device. Figure 7 A schematic diagram of the module composition of a graphic code verification device provided in one or more embodiments of this specification, the device is used to perform Figures 1 to 6 The graphic code verification method described, such as Figure 7 As shown, the device comprises:

[0079] The code scanning result determination module 701 is used to perform code scanning processing on the target graphic code and generate a code scanning result for the target graphic code, wherein the target graphic code is a payment code distributed to the applicant user;

[0080] The graphic code determination module 702 is used to determine whether the target graphic code meets a preset condition according to the generated scanning result;

[0081] The verification result determination module 703 is used to determine that the current code scanning operation is an operation requesting to verify whether the target graphic code belongs to the applicant user if the judgment result satisfies the preset condition; and

[0082] The interaction information generating module 704 is used to generate first interaction information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant.

[0083] In one or more embodiments of the present specification, targeted feedback information is generated based on the graphic code verification result to let users know that the feedback information is generated in response to their request for verification of the graphic code they applied for, and is not a simple error prompt. In this way, the feedback result of the graphic code authenticity verification that has been completed in response to the user's graphic code verification requirement can be delivered to the user, thereby improving the accuracy of the interaction between the terminal and the user, and thereby improving the user experience.

[0084] Optionally, the code scanning result determination module 701 is specifically used to:

[0085] Scan the target graphic code using a code scanning application to obtain first account information corresponding to the target graphic code;

[0086] The first account information obtained is determined as a scanning result generated for the target graphic code.

[0087] Optionally, the graphic code determination module 702 is specifically used to:

[0088] Obtaining information of a second account used to log in to the code scanning application;

[0089] Determining whether the first account information is consistent with the second account information;

[0090] If the judgment result is consistent, it is determined that the target graphic code meets the preset condition.

[0091] Optionally, the device further includes an interactive interface control module, configured to:

[0092] If the judgment result is that the preset condition is not met, the interface jumps to a payment interface for transferring money to the payment account corresponding to the target graphic code.

[0093] Optionally, the device further comprises a feedback control display module, which is used to:

[0094] On the payment interface, a feedback control for reporting the failure of the graphic code verification is displayed; and

[0095] The device also includes a feedback information sending module, which is used to:

[0096] Determining whether the user performs a touch operation on the information feedback control;

[0097] If the judgment result is yes, a graphic code verification failure feedback message is sent to the graphic code distribution server.

[0098] Optionally, the feedback control display module is specifically used to:

[0099] generating second interactive information for prompting the user to feedback that the graphic code verification fails;

[0100] On the payment interface, summary information is displayed as an information feedback control of the second interaction information.

[0101] Optionally, the first interactive information includes: the target graphic code is the payment code you applied for, please feel free to use it.

[0102] The graphic code verification device in one or more embodiments of the present specification performs a scanning process on the target graphic code and generates a scanning result for the target graphic code; based on the generated scanning result, it is determined whether the target graphic code meets the preset conditions; if so, it is determined that this scanning operation is an operation for requesting verification of whether the target graphic code belongs to the applicant user; and first interactive information is generated indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user. By generating targeted feedback information based on the graphic code verification result, the user is informed that the feedback information is generated for the verification requirements of the respective graphic codes requested by the user, and is not a simple error message. In this way, the feedback result of the authenticity verification of the graphic code that has been completed for the user's graphic code verification requirements can be delivered to the user, thereby improving the interaction accuracy between the terminal and the user, and thus improving the user experience.

[0103] It should be noted that the embodiment of the graphic code verification device in this specification and the embodiment of the graphic code verification method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding graphic code verification method mentioned above, and the repeated parts will not be repeated.

[0104] Furthermore, corresponding to the above Figures 1 to 6 Based on the same technical concept, one or more embodiments of this specification also provide a graphic code verification device, which is used to execute the above-mentioned graphic code verification method, such as Figure 8 shown.

[0105] The graphic code verification device may have relatively large differences due to different configurations or performances, and may include one or more processors 801 and memory 802, and the memory 802 may store one or more storage applications or data. Among them, the memory 802 may be a temporary storage or a permanent storage. The application stored in the memory 802 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the graphic code verification device. Furthermore, the processor 801 may be configured to communicate with the memory 802, and execute a series of computer executable instructions in the memory 802 on the graphic code verification device. The graphic code verification device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input and output interfaces 805, one or more keyboards 806, etc.

[0106] In a specific embodiment, the graphic code verification device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions for the graphic code verification device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following:

[0107] Scanning a target graphic code to generate a scanning result for the target graphic code, wherein the target graphic code is a payment code distributed to the applicant user;

[0108] According to the generated scanning result, judging whether the target graphic code meets the preset conditions;

[0109] If the judgment result is that the preset condition is met, then determining that the current code scanning operation is an operation requesting to verify whether the target graphic code belongs to the applicant user; and,

[0110] The first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated.

[0111] In one or more embodiments of the present specification, targeted feedback information is generated based on the graphic code verification result to let users know that the feedback information is generated in response to their request for verification of the graphic code they applied for, and is not a simple error prompt. In this way, the feedback result of the graphic code authenticity verification that has been completed in response to the user's graphic code verification requirement can be delivered to the user, thereby improving the accuracy of the interaction between the terminal and the user, and thereby improving the user experience.

[0112] Optionally, when the computer executable instructions are executed, the scanning process is performed on the target graphic code to generate a scanning result for the target graphic code, including:

[0113] Scan the target graphic code using a code scanning application to obtain first account information corresponding to the target graphic code;

[0114] The first account information obtained is determined as a scanning result generated for the target graphic code.

[0115] Optionally, when the computer executable instruction is executed, judging whether the target graphic code meets a preset condition according to the generated scanning result includes:

[0116] Obtaining information of a second account used to log in to the code scanning application;

[0117] Determining whether the first account information is consistent with the second account information;

[0118] If the judgment result is consistent, it is determined that the target graphic code meets the preset condition.

[0119] Optionally, when the computer executable instructions are executed, they further include computer executable instructions for performing the following:

[0120] After judging whether the target graphic code meets a preset condition according to the generated scanning result, the method further includes:

[0121] If the judgment result is that the preset condition is not met, the interface jumps to a payment interface for transferring money to the payment account corresponding to the target graphic code.

[0122] Optionally, when the computer executable instructions are executed, they further include computer executable instructions for performing the following:

[0123] After jumping to the payment interface for providing a transfer to the payment account corresponding to the target graphic code, it also includes:

[0124] On the payment interface, an information feedback control for reporting the failure of the graphic code verification is displayed;

[0125] Determining whether the user performs a touch operation on the information feedback control;

[0126] If the judgment result is yes, a graphic code verification failure feedback message is sent to the graphic code distribution server.

[0127] Optionally, when the computer executable instructions are executed, the information feedback control for feeding back the failure of the graphic code verification is displayed on the payment interface, including:

[0128] generating second interactive information for prompting the user to feedback that the graphic code verification fails;

[0129] On the payment interface, summary information is displayed as an information feedback control of the second interaction information.

[0130] Optionally, when the computer executable instruction is executed, the first interactive information includes: the target graphic code is the payment code you applied for, please feel free to use it.

[0131] The graphic code verification device in one or more embodiments of the present specification performs a scanning process on the target graphic code and generates a scanning result for the target graphic code; based on the generated scanning result, it is determined whether the target graphic code meets the preset conditions; if so, it is determined that this scanning operation is an operation of requesting to verify whether the target graphic code belongs to the applicant user; and the first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated. By generating targeted feedback information based on the graphic code verification result, the user is informed that the feedback information is generated for the verification requirements of the respective graphic codes requested by the user, and is not a simple error message. In this way, the feedback result of the authenticity verification of the graphic code that has been completed for the user's graphic code verification requirements can be delivered to the user, thereby improving the interaction accuracy between the terminal and the user, and thus improving the user experience.

[0132] Furthermore, corresponding to the above Figures 1 to 6 The method shown is based on the same technical concept. One or more embodiments of this specification also provide a storage medium for storing computer executable instructions. In a specific embodiment, the storage medium can be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instructions stored in the storage medium are executed by the processor, the following process can be implemented:

[0133] Scanning a target graphic code to generate a scanning result for the target graphic code, wherein the target graphic code is a payment code distributed to the applicant user;

[0134] According to the generated scanning result, judging whether the target graphic code meets the preset conditions;

[0135] If the judgment result is that the preset condition is met, then determining that the current code scanning operation is an operation requesting to verify whether the target graphic code belongs to the applicant user; and,

[0136] The first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated.

[0137] In one or more embodiments of the present specification, targeted feedback information is generated based on the graphic code verification result to let users know that the feedback information is generated in response to their request for verification of the graphic code they applied for, and is not a simple error prompt. In this way, the feedback result of the graphic code authenticity verification that has been completed in response to the user's graphic code verification requirement can be delivered to the user, thereby improving the accuracy of the interaction between the terminal and the user, and thereby improving the user experience.

[0138] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the scanning process of the target graphic code to generate a scanning result for the target graphic code includes:

[0139] Scan the target graphic code using a code scanning application to obtain first account information corresponding to the target graphic code;

[0140] The first account information obtained is determined as a scanning result generated for the target graphic code.

[0141] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, judging whether the target graphic code meets a preset condition according to the generated scanning result includes:

[0142] Obtaining information of a second account used to log in to the code scanning application;

[0143] Determining whether the first account information is consistent with the second account information;

[0144] If the judgment result is consistent, it is determined that the target graphic code meets the preset condition.

[0145] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the following process is also implemented:

[0146] After judging whether the target graphic code meets a preset condition according to the generated scanning result, the method further includes:

[0147] If the judgment result is that the preset condition is not met, the interface jumps to a payment interface for transferring money to the payment account corresponding to the target graphic code.

[0148] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the following process is also implemented:

[0149] After jumping to the payment interface for providing a transfer to the payment account corresponding to the target graphic code, it also includes:

[0150] On the payment interface, an information feedback control for reporting the failure of the graphic code verification is displayed;

[0151] Determining whether the user performs a touch operation on the information feedback control;

[0152] If the judgment result is yes, a graphic code verification failure feedback message is sent to the graphic code distribution server.

[0153] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the information feedback control for feeding back the failure of the graphic code verification is displayed on the payment interface, including:

[0154] generating second interactive information for prompting the user to feedback that the graphic code verification fails;

[0155] On the payment interface, summary information is displayed as an information feedback control of the second interaction information.

[0156] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the first interaction information includes: the target graphic code is the payment code you applied for, please feel free to use it.

[0157] When the computer executable instructions stored in the storage medium in one or more embodiments of this specification are executed by the processor, the target graphic code is scanned and a scanning result for the target graphic code is generated; based on the generated scanning result, whether the target graphic code meets the preset conditions is determined; if so, the scanning operation is determined to be an operation requesting verification of whether the target graphic code belongs to the applicant user; and the first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated. By generating targeted feedback information based on the graphic code verification result, the user is informed that the feedback information is generated for the verification requirements of the graphic code they requested, and is not a simple error message. In this way, the feedback result of the authenticity verification of the graphic code that has been completed for the user's graphic code verification requirements can be delivered to the user, thereby improving the interaction accuracy between the terminal and the user, thereby improving the user experience.

[0158] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0159] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0160] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, 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.

[0161] For the convenience of description, the above devices are described in various units according to their functions. Of course, when implementing one or more of the present specification, the functions of each unit can be implemented in the same or more software and / or hardware.

[0162] It will be appreciated by those skilled in the art that one or more embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, one or more of this specification may be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more of this specification may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0163] One or more of the present specification is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to one or more embodiments of the present specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0164] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0165] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0167] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0168] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0169] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0170] It should be understood by those skilled in the art that one or more embodiments of this specification may be provided as methods, systems or computer program products. Therefore, one or more of this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, one or more of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

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

[0173] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification should be included in the scope of one or more claims of this specification.

Claims

1. A graphic code verification method, characterized in that: include: According to the scanning result of the target graphic code, it is judged whether the target graphic code meets the preset conditions; wherein the preset conditions include: the transfer account corresponding to the target graphic code is consistent with the application account used by the user to apply for the target graphic code; If the judgment result is that the preset condition is met, then determining that the current code scanning operation is an operation of the applicant user requesting to verify whether the target graphic code belongs to the target graphic code; and, The first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated.

2. The method according to claim 1, characterized in that Before judging whether the target graphic code meets a preset condition according to the scanning result of the target graphic code, the method further includes: The target graphic code is scanned to generate a scanning result for the target graphic code.

3. The method according to claim 1, characterized in that in, The target graphic code is a payment code distributed to the applicant user.

4. The method according to claim 2, characterized in that: The scanning process of the target graphic code to generate a scanning result for the target graphic code includes: Scan the target graphic code using a code scanning application to obtain first account information corresponding to the target graphic code; The first account information obtained is determined as a scanning result generated for the target graphic code.

5. The method according to claim 4, characterized in that The step of judging whether the target graphic code meets a preset condition according to the generated scanning result includes: Obtaining information of a second account used to log in to the code scanning application; Determining whether the first account information is consistent with the second account information; If the judgment result is consistent, it is determined that the target graphic code meets the preset condition.

6. The method according to claim 1, characterized in that After judging whether the target graphic code meets a preset condition according to the scanning result of the target graphic code, the method further includes: If the judgment result is that the preset condition is not met, the interface jumps to a payment interface for transferring money to the payment account corresponding to the target graphic code.

7. The method according to claim 6, characterized in that After jumping to the payment interface for providing a transfer to the payment account corresponding to the target graphic code, it also includes: On the payment interface, an information feedback control for reporting the failure of the graphic code verification is displayed; Determining whether the user performs a touch operation on the information feedback control; If the judgment result is yes, a graphic code verification failure feedback message is sent to the graphic code distribution server.

8. The method according to claim 7, characterized in that The information feedback control for feedback of graphic code verification failure is displayed on the payment interface, including: generating second interactive information for prompting the user to feedback that the graphic code verification fails; On the payment interface, summary information is displayed as an information feedback control of the second interaction information.

9. The method according to claim 3, characterized in that: The first interactive information includes: the target graphic code is the payment code you applied for, please feel free to use it.

10. A graphic code verification device, characterized in that: include: The graphic code judging module is used to judge whether the target graphic code meets the preset conditions according to the scanning result of the target graphic code; wherein the preset conditions include: the transfer account corresponding to the target graphic code is consistent with the application account used by the user to apply for the target graphic code; A verification result determination module, for determining, if the judgment result satisfies a preset condition, that the current code scanning operation is an operation of the applicant user requesting to verify whether the target graphic code belongs to the target graphic code; and The interactive information generating module is used to generate the first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user.

11. The device according to claim 10, characterized in that The device also includes: The scanning result determination module is used to perform scanning processing on the target graphic code and generate a scanning result for the target graphic code.

12. The device according to claim 10, characterized in that The target graphic code is a payment code distributed to the applicant user.

13. The device according to claim 11, characterized in that The code scanning result determination module is specifically used for: Scan the target graphic code using a code scanning application to obtain first account information corresponding to the target graphic code; The first account information obtained is determined as a scanning result generated for the target graphic code.

14. The device according to claim 13, characterized in that The graphic code determination module is specifically used for: Obtaining information of a second account used to log in to the code scanning application; Determining whether the first account information is consistent with the second account information; If the judgment result is consistent, it is determined that the target graphic code meets the preset condition.

15. The device according to claim 10, characterized in that The device also includes an interactive interface control module, which is used to: If the judgment result is that the preset condition is not met, the interface jumps to a payment interface for transferring money to the payment account corresponding to the target graphic code.

16. The device according to claim 15, characterized in that The device also includes a feedback control display module, which is used to: On the payment interface, a feedback control for reporting the failure of the graphic code verification is displayed; and The device also includes a feedback information sending module, which is used to: Determining whether the user performs a touch operation on the information feedback control; If the judgment result is yes, a graphic code verification failure feedback message is sent to the graphic code distribution server.

17. The device according to claim 16, characterized in that The feedback control display module is specifically used for: generating second interactive information for prompting the user to feedback that the graphic code verification fails; On the payment interface, summary information is displayed as an information feedback control of the second interaction information.

18. The device according to claim 12, characterized in that The first interactive information includes: the target graphic code is the payment code you applied for, please feel free to use it.

19. A graphic code verification device, characterized in that: include: processor; as well as a memory arranged to store computer executable instructions which, when executed, cause the processor to: According to the scanning result of the target graphic code, it is judged whether the target graphic code meets the preset conditions; wherein the preset conditions include: the transfer account corresponding to the target graphic code is consistent with the application account used by the user to apply for the target graphic code; If the judgment result is that the preset condition is met, then determining that the current code scanning operation is an operation of the applicant user requesting to verify whether the target graphic code belongs to the target graphic code; and, The first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated.

20. A storage medium for storing computer executable instructions, characterized in that: The executable instructions implement the following process when executed: According to the scanning result of the target graphic code, it is judged whether the target graphic code meets the preset conditions; wherein the preset conditions include: the transfer account corresponding to the target graphic code is consistent with the application account used by the user to apply for the target graphic code; If the judgment result is that the preset condition is met, then determining that the current code scanning operation is an operation of the applicant user requesting to verify whether the target graphic code belongs to the target graphic code; and, The first interactive information indicating that the graphic code verification is successful and the target graphic code belongs to the applicant user is generated.

Images