Payment methods, devices, payment receivers, media, and computer program products

Abstract

This application relates to the field of information security technology, and provides a payment method, device, payment receiver, storage medium, and computer program product, which can be specifically applied in the financial field. This application can effectively avoid payment chaos, and in situations such as multiple people vying for payment, it can effectively prevent payment chaos and ensure that only users who scan the QR code can make payments. Furthermore, it can also restrict payments to specific users, such as in scenarios where only the party concerned or invited groups are allowed to pay, ensuring that the payment QR code is used for its designated purpose, thereby improving payment security. The method includes: responding to a user's payment request, generating a payment QR code for the object to be paid, displaying the payment QR code for the payment initiator to scan, instructing the payment initiator to provide verification information for payment verification, obtaining the received verification information, and if the received verification information matches the verification information agreed upon by the target user, then allowing the payment initiator to make the payment.

Description

Technical Field

[0001] This application relates to the field of information security technology, and in particular to a payment method, device, payment receiver, storage medium, and computer program product. Background Technology

[0002] With the development of information technology, more and more electronic payment methods have emerged, among which electronic payment via terminals is a common payment method.

[0003] In traditional technology, the phenomenon of completing payments by scanning QR codes at terminals has become increasingly common in daily life (such as vending machines). However, when situations arise, such as multiple people vying to pay, this technology can easily cause payment chaos. Summary of the Invention

[0004] Therefore, it is necessary to provide a payment method, device, payment receiver, computer-readable storage medium, and computer program product to address the aforementioned technical problems.

[0005] Firstly, this application provides a payment method. The method includes:

[0006] In response to a user's payment request, generate a payment QR code for the object to be paid;

[0007] Display the payment QR code so that the payment initiator can scan it and then instruct the payment initiator to provide verification information for payment verification;

[0008] Retrieve the received verification information;

[0009] If the received verification information matches the verification information agreed upon with the target user, the payment initiator is allowed to proceed with the payment.

[0010] In one embodiment, in response to a user's payment request, a payment QR code for the object to be paid is generated, including:

[0011] In response to a user's payment request, a verification information input interface is displayed;

[0012] Obtain the verification information entered by the user on the verification information input interface;

[0013] The input verification information is used as verification information agreed upon with the target user to generate a payment QR code for the object to be paid.

[0014] In one embodiment, in response to a user's payment request, a payment QR code for the object to be paid is generated, including:

[0015] In response to a user's payment request, a contact information input interface is displayed;

[0016] Obtain the contact information entered by the user on the contact information input interface;

[0017] Generate a verification message as a verification message for consensus with the target user;

[0018] Send the generated verification information to the terminal corresponding to the contact information;

[0019] Generate the payment QR code for the object to be paid.

[0020] In one embodiment, in response to a user's payment request, a payment QR code for the object to be paid is generated, including:

[0021] In response to a user's payment request, a verification message is generated as a verification message agreed upon with the target user;

[0022] Display the generated verification information;

[0023] Generate the payment QR code for the object to be paid.

[0024] In one embodiment, the generated verification information is displayed, including:

[0025] The generated verification information is displayed using preset visual constraints; these preset visual constraints include display size constraints and / or display position constraints.

[0026] In one embodiment, generating a payment QR code for the payee includes:

[0027] Based on the verification information agreed upon with the target user and the payment information of the person to be paid, a payment QR code is generated for the person to be paid.

[0028] In one embodiment, the method further includes:

[0029] If the received verification information is inconsistent with the verification information agreed upon with the target user, the payment initiator will refuse to make the payment.

[0030] Secondly, this application also provides a payment device. The device includes:

[0031] The payment QR code generation module is used to generate a payment QR code for the object to be paid in response to a user's payment request.

[0032] A payment QR code display module is used to display the payment QR code so that the payment initiator can scan it and instruct the payment initiator to provide verification information for payment verification.

[0033] The verification information acquisition module is used to acquire the received verification information;

[0034] The payment permission module is used to allow the payment initiator to make a payment if the received verification information is consistent with the verification information agreed upon by the target user.

[0035] Thirdly, this application also provides a payment receiving terminal. The payment receiving terminal includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0036] In response to a user's payment request, a payment QR code for the object to be paid is generated; the payment QR code is displayed so that the payment initiator can scan it and then instruct the payment initiator to provide verification information for payment verification; the received verification information is obtained; if the received verification information is consistent with the verification information agreed upon with the target user, the payment initiator is allowed to proceed with the payment.

[0037] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0038] In response to a user's payment request, a payment QR code for the object to be paid is generated; the payment QR code is displayed so that the payment initiator can scan it and then instruct the payment initiator to provide verification information for payment verification; the received verification information is obtained; if the received verification information is consistent with the verification information agreed upon with the target user, the payment initiator is allowed to proceed with the payment.

[0039] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0040] In response to a user's payment request, a payment QR code for the object to be paid is generated; the payment QR code is displayed so that the payment initiator can scan it and then instruct the payment initiator to provide verification information for payment verification; the received verification information is obtained; if the received verification information is consistent with the verification information agreed upon with the target user, the payment initiator is allowed to proceed with the payment.

[0041] The aforementioned payment method, device, payment receiver, storage medium, and computer program product, in response to a user's payment request, generate a payment QR code for the object to be paid, display the payment QR code, and allow the payment initiator to scan it and instruct the payment initiator to provide verification information for payment verification. If the received verification information is consistent with the verification information agreed upon by the target user, the payment initiator is allowed to make the payment. This solution responds to a user's payment request by generating a payment QR code corresponding to the object to be paid. The QR code is then displayed, allowing the user to scan it via the payment initiator. A verification information input interface then pops up, instructing the user to provide verification information for payment verification. The system receives this verification information and checks if it matches the verification information agreed upon by the target user. If they match, the payment initiator is allowed to proceed with the payment, effectively preventing payment chaos. Furthermore, it effectively avoids payment chaos in situations such as multiple users vying for payment and ensures that only users who scan the QR code can make a payment. Additionally, it can restrict payments to specific users, such as allowing only the individual or invited group to pay, thus achieving dedicated QR codes and improving payment security. Attached Figure Description

[0042] Figure 1 This is a diagram illustrating the application environment of a payment method in one embodiment;

[0043] Figure 2 This is a flowchart illustrating a payment method in one embodiment;

[0044] Figure 3 This is a flowchart illustrating the payment method in another embodiment;

[0045] Figure 4 This is a flowchart illustrating the payment method in yet another embodiment;

[0046] Figure 5 This is a schematic diagram illustrating the construction of a QR code generation module in one embodiment;

[0047] Figure 6 This is a schematic diagram illustrating the construction of a QR code recognition module in one embodiment;

[0048] Figure 7 This is a structural block diagram of a payment device in one embodiment;

[0049] Figure 8 This is an internal structure diagram of the payment receiver in one embodiment. Detailed Implementation

[0050] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0051] The payment method provided in this application can be applied to, for example... Figure 1 The application environment shown is as follows. This application scenario can include a payment receiver and a payment initiator, which can communicate with each other. Specifically, in response to a user's payment request, the payment receiver generates a payment QR code for the object to be paid and displays the QR code. After the payment initiator scans the QR code, the payment receiver instructs the payment initiator to provide verification information for payment verification. The payment initiator sends the verification information to the payment receiver, which receives the received verification information. If the received verification information matches the verification information agreed upon with the target user, the payment initiator is allowed to proceed with the payment. The payment receiver can be, but is not limited to, various vending machines, service machines, personal computers, laptops, smartphones, tablets, and servers. The payment initiator can be, but is not limited to, various smartphones.

[0052] In one embodiment, such as Figure 2 As shown, a payment method is provided, which is applied to... Figure 1 Taking the payment receiving terminal in the example, the following steps are included:

[0053] Step S201: In response to the user's payment request, generate a payment QR code for the object to be paid.

[0054] In this step, the user's payment request may include payment information for the object to be paid, which may be a product or a business order (such as a fine order).

[0055] Specifically, it receives user payment requests and, in response to those requests, generates a payment QR code for the object to be paid.

[0056] For example, such as Figure 3 As shown, in response to the user's payment request, the backend system of the payment receiver generates a payment QR code for the information to be verified.

[0057] Step S202: Display the payment QR code so that the payment initiator can scan it and instruct the payment initiator to provide verification information for payment verification.

[0058] In this step, the verification information is used by the payment receiver to determine whether the verification information is consistent with the verification information agreed upon by the target user. If they are consistent, the payment initiator is allowed to proceed with the payment.

[0059] Specifically, such as Figure 3As shown, the payment QR code generated by the payment receiver can be displayed on the screen of the payment receiver (e.g., the QR code is displayed on the front-end system of the payment receiver). After the payment initiator scans the payment QR code (e.g., after the customer scans the payment QR code through the APP of the payment initiator), a verification information input interface can pop up in the payment initiator to instruct the payment initiator to enter the verification information for payment verification in the interface and then send the feedback to the payment receiver.

[0060] Step S203: Obtain the received verification information.

[0061] Specifically, obtain the verification information sent by the payment initiator.

[0062] Step S204: If the received verification information is consistent with the verification information agreed upon by the target user, then the payment initiator is allowed to make the payment.

[0063] In this step, the verification information agreed upon with the target user can be verification information agreed upon by the payment receiver and the target user. For example, it can be verification information that the payment receiver and the target user already know or have been preset, or it can be verification information that only the target user knows in the user group, which is used to limit the target user to the payment.

[0064] Specifically, it determines whether the received verification information is consistent with the verification information agreed upon by the target user. If they are consistent, the payment initiator is allowed to make the payment; otherwise, the payment initiator is refused to make the payment.

[0065] For example, such as Figure 3 As shown, the backend system of the payment receiver can parse whether the payment QR code is pending verification information. If not, the payment initiator can be allowed to make the payment directly. If so, the user (customer) is prompted to enter verification information and verify the verification information. The system determines whether the received verification information is consistent with the verification information agreed upon by the target user. If they are consistent, the payment initiator is allowed to make the payment. If they are inconsistent, the payment initiator is refused to make the payment.

[0066] In the aforementioned payment method, in response to a user's payment request, a payment QR code for the object to be paid is generated and displayed. The payment initiator scans this QR code and is instructed to provide verification information for payment verification. The received verification information is then retrieved. If the received verification information matches the verification information agreed upon by the target user, the payment initiator is allowed to proceed with the payment. This scheme, in response to a user's payment request, generates and displays a payment QR code corresponding to the object to be paid. After the user scans this QR code, a verification information input interface pops up, instructing the user to provide verification information on this interface. The system receives this verification information and determines whether it matches the verification information agreed upon by the target user. If they match, the payment initiator is allowed to proceed with the payment, effectively avoiding payment chaos. Furthermore, it effectively prevents payment chaos in situations such as multiple users vying for payment and ensures that only users who scan the QR code can make payments. Additionally, it can restrict payments to specific users, such as allowing only the individual or invited group to pay, thus achieving dedicated QR codes and improving payment security.

[0067] In one embodiment, the step S201 above, which generates a payment QR code for the object to be paid in response to a user's payment request, specifically includes: displaying a verification information input interface in response to a user's payment request; obtaining the verification information entered by the user on the verification information input interface; and using the entered verification information as verification information agreed upon with the target user to generate a payment QR code for the object to be paid.

[0068] In this embodiment, the verification information input interface can be an interface displayed on the screen of the payment receiver to instruct the user to input verification information. The verification information input by the user can serve as verification information agreed upon with the target user.

[0069] Specifically, in response to a user's payment request, a verification information input interface can be displayed on the screen of the payment receiver. The verification message entered by the user on the verification information input interface can be obtained, and the entered verification information can be used as the verification information agreed upon with the target user to generate a payment QR code for the object to be paid.

[0070] For example, such as Figure 3 As shown, the front-end system may include a display screen for the payment receiver. There are three options for generating verification information, one of which is that the user (customer) enters the verification information on the interface, such as... Figure 4 As shown, the payment receiver may include Figure 4The system includes a merchant (which can be the front-end system of the payment receiver), a QR code generation module, and a QR code recognition module. The QR code generation module can receive custom verification information input by the user (customer) and then include this verification information in the encrypted information of the generated QR code. It can then display (return) a QR code containing the verification information (verification information agreed upon with the target user) to the user. For example, Figure 5 As shown, the QR code generation module can be used to collect verification information and add it to the QR code information. The QR code generation module may include a merchant-defined verification information collection module 01 (responsible for generating the merchant-defined verification information, displaying it to the customer on the front-end page, or sending it to the customer's mobile phone) and a customer-defined verification information collection module 02 (responsible for receiving the customer-defined verification information); for example... Figure 4 and Figure 6 As shown, the QR code recognition module can be used for verification information parsing and processing. The QR code recognition module may include a verification information parsing module 01 (responsible for determining whether there is verification information in the QR code and parsing out the verification information in the QR code), a customer verification information receiving module 02 (responsible for prompting the customer to enter verification information when the QR code contains verification information after the customer scans the QR code through the APP), and a verification information checking module 03 (responsible for checking the consistency between the verification information in the QR code and the verification information entered by the customer after the customer enters the verification information; if the verification information is consistent, the payment process will proceed).

[0071] The technical solution of this embodiment, in response to a user's payment request, displays an interface to instruct the user (such as a target user) to input verification information, and uses the obtained input verification information as the verification information agreed upon with the target user. This allows the verification information to be defined by the target user, so that only users who know the verification information can make payments, enabling users to pay in sequence and further avoiding payment chaos.

[0072] In one embodiment, step S201 above, which generates a payment QR code for the object to be paid in response to a user's payment request, specifically includes: displaying a contact information input interface in response to a user's payment request; obtaining the contact information entered by the user on the contact information input interface; generating verification information as verification information agreed upon with the target user; sending the generated verification information to the terminal corresponding to the contact information; and generating a payment QR code for the object to be paid.

[0073] In this embodiment, the contact information input interface can be an interface used to instruct users (such as target users) to input contact information; the contact information can be a mobile phone number or an email address; the terminal can be a mobile phone (such as a smartphone), and the terminal can be the same device as the payment initiator.

[0074] Specifically, such as Figure 3As shown, in response to a user's payment request, a contact information input interface is displayed, the contact information entered by the user on the contact information input interface (e.g., a customer enters a mobile phone number) is obtained, and a verification message (e.g., a random number verification code) can be randomly generated as the verification message agreed upon with the target user. The generated verification message is sent to the terminal corresponding to the contact information (e.g., the terminal corresponding to the contact information is the customer's mobile phone corresponding to the mobile phone number), and a payment QR code for the object to be paid is generated.

[0075] The technical solution of this embodiment, by sending the generated verification information as the verification information agreed upon with the target user to the terminal corresponding to the contact information, ensures that the verification information agreed upon with the target user is only known to the target user in the user group. This prevents non-target users in the user group from obtaining the verification information agreed upon with the target user through improper means such as spying, thus enabling orderly payment and further avoiding payment chaos.

[0076] In one embodiment, the step S201 above, which generates a payment QR code for the object to be paid in response to a user's payment request, specifically includes: generating verification information as verification information agreed upon with the target user in response to a user's payment request; displaying the generated verification information; and generating a payment QR code for the object to be paid.

[0077] Specifically, in response to a user's payment request, a verification message is generated as a verification message agreed upon with the target user. This generated verification message can be displayed on the screen of the payment receiver, and a payment QR code for the object to be paid is generated.

[0078] For example, such as Figure 3 As shown, the screen on the payment receiver displays a randomly generated verification code, such as... Figure 4 As shown, this is equivalent to the merchant informing the customer of the verification information defined by the merchant, and at the same time, the merchant sending (inputting) the verification information defined by the merchant to the QR code generation module.

[0079] The technical solution of this embodiment generates and displays verification information as consensus with the target user, thereby enabling orderly payment and avoiding payment chaos by showing the target user the verification information that is consensus with the target user.

[0080] In one embodiment, the above method may further display the generated verification information by the following steps, specifically including: displaying the generated verification information in a preset visual constraint manner.

[0081] In this embodiment, the preset visual restriction methods include display size restriction and / or display position restriction.

[0082] Specifically, in response to a user's payment request, after generating verification information as a consensus with the target user, the generated verification information is displayed in a way that is subject to preset visual constraints (for example, the generated verification information can be displayed in an inconspicuous position on the display screen of the payment receiver and / or in a small font or other inconspicuous manner).

[0083] The technical solution of this embodiment, by displaying the generated verification information in a preset visual restriction manner, prevents non-target users from obtaining the verification information agreed upon by the target user through improper means such as peeping, thereby achieving secure and orderly payment and further avoiding payment chaos.

[0084] In one embodiment, the step S201 of generating the payment QR code of the object to be paid specifically includes: generating the payment QR code of the object to be paid based on the verification information agreed upon with the target user and the payment information of the object to be paid.

[0085] Specifically, a payment QR code for the payee is generated based on the verification information agreed upon with the target user and the payment information of the payee.

[0086] For example, the verification information agreed upon with the target user is encrypted into the QR code string corresponding to the payment information of the object to be paid, thereby generating the payment QR code for the object to be paid.

[0087] The technical solution of this embodiment encrypts the verification information agreed upon with the target user into the payment QR code of the object to be paid, thereby realizing that the payment QR code is dedicated to a specific purpose. Only users who know the verification information agreed upon with the target user can make payments, thus improving payment security.

[0088] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0089] Based on the same inventive concept, this application also provides a payment device for implementing the payment method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more payment device embodiments provided below can be found in the limitations of the payment method described above, and will not be repeated here.

[0090] In one embodiment, such as Figure 7 As shown, a payment device 700 is provided, which may include:

[0091] The payment QR code generation module 701 is used to generate a payment QR code for the object to be paid in response to a user's payment request.

[0092] The payment QR code display module 702 is used to display the payment QR code so that the payment initiator can scan it and instruct the payment initiator to provide verification information for payment verification.

[0093] The verification information acquisition module 703 is used to acquire the received verification information;

[0094] The payment permission module 704 is used to allow the payment initiator to make a payment if the received verification information is consistent with the verification information agreed upon by the target user.

[0095] In one embodiment, the payment QR code generation module 701 is further configured to respond to a user's payment request by displaying a verification information input interface; obtaining the verification information entered by the user on the verification information input interface; and using the entered verification information as verification information agreed upon with the target user to generate a payment QR code for the object to be paid.

[0096] In one embodiment, the payment QR code generation module 701 is further configured to respond to a user's payment request by displaying a contact information input interface; obtaining the contact information entered by the user on the contact information input interface; generating verification information as verification information agreed upon with the target user; sending the generated verification information to the terminal corresponding to the contact information; and generating a payment QR code for the object to be paid.

[0097] In one embodiment, the payment QR code generation module 701 is further configured to, in response to a user's payment request, generate verification information as verification information agreed upon with the target user; display the generated verification information; and generate a payment QR code for the object to be paid.

[0098] In one embodiment, the payment QR code generation module 701 is further configured to display the generated verification information in a preset visual constraint manner; wherein the preset visual constraint manner includes display size constraint and / or display position constraint.

[0099] In one embodiment, the payment QR code generation module 701 is further configured to generate a payment QR code for the payee based on the verification information agreed upon with the target user and the payment information of the payee.

[0100] The various modules in the aforementioned payment device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0101] It should be noted that the payment method and apparatus provided in this application can be used in payment-related application areas in the financial field, or in payment processing in any field other than the financial field. The application areas of the payment method and apparatus provided in this application are not limited.

[0102] In one embodiment, a payment receiver is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 8 As shown, the payment receiver includes a processor, memory, communication interface, display screen, and input device connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides the environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals. Wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. The computer device also includes input / output interfaces, which are connection circuits for exchanging information between the processor and external devices. These interfaces are connected to the processor via a bus and are referred to as I / O interfaces. When the computer program is executed by the processor, it implements a payment method. The display screen of the payment receiver can be an LCD screen or an e-ink screen. The input device can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the payment receiver's casing, or an external keyboard, touchpad, or mouse.

[0103] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the solution of this application and does not constitute a limitation on the payment receiver to which the solution of this application is applied. A specific payment receiver may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0104] In one embodiment, a payment receiver is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0105] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0106] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0107] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0108] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0109] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0110] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A payment method, characterized in that, Applied to a payment receiving end, the method includes: In response to a user's payment request, generating a payment QR code for the object to be paid includes: generating verification information as verification information agreed upon with the target user in response to the user's payment request; displaying the generated verification information; and generating a payment QR code for the object to be paid based on the verification information agreed upon with the target user and the payment information of the object to be paid. Displaying the generated verification information includes: displaying the generated verification information in a preset visual constraint manner; wherein, the preset visual constraint manner includes display size constraint and / or display position constraint; The payment QR code is displayed so that the payment initiator can scan it and instruct the payment initiator to provide verification information for payment verification. Retrieve the received verification information; If the received verification information is consistent with the verification information agreed upon with the target user, then the payment initiator is allowed to make the payment, wherein the verification information agreed upon with the target user is used to limit the target user of the payment.

2. The method according to claim 1, characterized in that, The step of generating a payment QR code for the object to be paid in response to a user's payment request includes: In response to a user's payment request, a verification information input interface is displayed; Obtain the verification information entered by the user on the verification information input interface; The input verification information is used as verification information agreed upon with the target user to generate a payment QR code for the object to be paid.

3. The method according to claim 1, characterized in that, The step of generating a payment QR code for the object to be paid in response to a user's payment request includes: In response to a user's payment request, a contact information input interface is displayed; Obtain the contact information entered by the user on the contact information input interface; Generate a verification message as a verification message for consensus with the target user; The generated verification information is sent to the terminal corresponding to the contact information. Generate the payment QR code for the object to be paid.

4. A payment device, characterized in that, The device, used in a payment receiving terminal, includes: A payment QR code generation module is used to generate a payment QR code for a payment object in response to a user's payment request, including: generating verification information as verification information agreed upon with the target user in response to the user's payment request; displaying the generated verification information; and generating a payment QR code for the payment object based on the verification information agreed upon with the target user and the payment information of the payment object. The generated verification information is displayed by: displaying the generated verification information in a preset visual constraint manner; wherein, the preset visual constraint manner includes display size constraint and / or display position constraint; a payment QR code display module is used to display the payment QR code so that after scanning by the payment initiator, it can instruct the payment initiator to provide verification information for payment verification; The verification information acquisition module is used to acquire the received verification information; The payment permission module is configured to allow the payment initiator to make a payment if the received verification information is consistent with the verification information agreed upon with the target user, wherein the verification information agreed upon with the target user is used to limit the target user of the payment.

5. A payment receiver, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 4.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 3.

7. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 3.

Images