CN113807831B - Payment method and device - Google Patents

Abstract

The application discloses a payment method and device, and belongs to the technical field of electronics. The specific scheme comprises the following steps: under the condition of displaying a first graphic code, receiving scanning input of a scanning device, and obtaining a scanning request of the scanning device, wherein the scanning request comprises M payment modes supported by the scanning device; in the case that at least one payment method of the M payment methods is included in the payment method list, determining a target payment method from the at least one payment method, and executing a payment operation based on the target payment method; the first graphic code comprises payment information of a payment mode in the payment mode list, and M is a positive integer.

Description

Payment method and device

Technical Field

The present application belongs to the field of electronic technology, and specifically relates to a payment method and device.

Background Art

With the development of communication technology, there are more and more payment applications on the market. However, merchants usually do not support all payment applications. Therefore, in the prior art, if a user wants to make a payment, he needs to first determine the payment application supported by the merchant, and then select the corresponding application from the payment applications installed in the electronic device to make the payment. However, the payment method of the prior art is less convenient to operate, and the user may need to spend a lot of time in the process of searching for the application.

Summary of the invention

The purpose of the embodiments of the present application is to provide a payment method and device that can solve the problem of poor operational convenience of payment methods in the prior art.

In a first aspect, an embodiment of the present application provides a payment method, the method comprising: when displaying a first graphic code, receiving a scan input from a scanning device, obtaining a scan request from the scanning device, the scan request including M payment methods supported by the scanning device; when a payment method list includes at least one payment method among the M payment methods, determining a target payment method from the at least one payment method, and performing a payment operation based on the target payment method; wherein the first graphic code includes payment information of the payment method in the payment method list, and M is a positive integer.

In a second aspect, an embodiment of the present application provides a payment device, including: a display module, a receiving module, and a processing module. The receiving module is used to receive a scan input of a scanning device when the display module displays a first graphic code, and obtain a scan request of the scanning device, wherein the scan request includes M payment methods supported by the scanning device. The processing module is used to determine a target payment method from the at least one payment method when a payment method list includes at least one payment method of the M payment methods, and perform a payment operation based on the target payment method; wherein the first graphic code includes payment information of the payment method in the payment method list, and M is a positive integer.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

In the embodiment of the present application, a scanning request of the scanning device can be obtained by displaying the first graphic code, and the payment method supported by the scanning device can be determined according to the scanning request, so that when the payment method list includes at least one payment method supported by the scanning device, the target payment method is determined from the at least one payment method, and the payment operation is performed based on the target payment method. Through this solution, since the target payment method supported by the scanning device can be automatically determined from the payment method list, the user does not need to manually search for the payment method, which simplifies the user operation and avoids the problem that the user needs to spend a lot of time in the process of searching for the payment method.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a payment method provided in an embodiment of the present application;

FIG. 2 is one of the interface operation diagrams of the payment method provided in the embodiment of the present application;

FIG3 is a second schematic diagram of the interface operation of the payment method provided in the embodiment of the present application;

FIG4 is a third schematic diagram of the interface operation of the payment method provided in the embodiment of the present application;

FIG5 is a schematic diagram of the structure of a payment device provided in an embodiment of the present application;

FIG6 is one of the hardware schematic diagrams of the electronic device provided in the embodiment of the present application;

FIG. 7 is a second hardware schematic diagram of the electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and/or" in the specification and claims represents at least one of the connected objects, and the character "/" generally indicates that the objects associated with each other are in an "or" relationship.

The payment method provided in the embodiment of the present application is described in detail below through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

As shown in FIG. 1 , an embodiment of the present application provides a payment method, which can be applied to an electronic device. The method may include steps 101-102:

Step 101: When displaying a first graphic code, receiving a scanning input from a scanning device to obtain a scanning request from the scanning device.

The scanning request may include M payment methods supported by the scanning device, where M is a positive integer.

When a user wants to pay by using a graphic code, an input can be made to the electronic device, and the electronic device can generate a first image code in response to the input according to a payment method in a payment method list of the electronic device, and display the first graphic code in the payment interface. Afterwards, when the first graphic code is displayed, a scanning device can scan and input the first graphic code, and the electronic device can receive the scanning input of the scanning device, obtain a scanning request of the scanning device according to the scanning input, and determine the M payment methods supported by the scanning device according to the scanning request.

Optionally, the above-mentioned payment interface may also include a payment method list. The electronic device may display a first graphic code in a first area of the payment interface and display a payment method list in a second area. The first area and the second area are different areas in the payment interface.

Exemplarily, as shown in (a) in FIG. 2 , when a user wants to pay via a graphic code, the user may click on the payment control 21 in the shortcut interface, and as shown in (b) in FIG. 2 , the electronic device may display a first graphic code 23 in a first area 22 of the payment interface and a payment method list 25 in a second area 24 of the payment interface in response to the click input.

Optionally, the above-mentioned payment method list may include one or more payment methods, and the user can trigger the electronic device to edit the payment method list. For example, the electronic device can add a new payment method to the payment method list, delete a payment method in the payment method list, adjust the arrangement order of each payment method in the payment method list, display hidden payment methods, etc.

Exemplarily, continuing to refer to (b) in Figure 2, the payment method list may include payment method 1, payment method 2 and payment method 3. The user can add a new payment method to the payment method list by adding control 26, delete payment method 1 from the payment method list by long pressing payment method 1, trigger the electronic device to display the payment methods hidden in the payment method list by inputting into the display control 27, and adjust the arrangement order of any payment method in the payment method list by dragging it.

Optionally, before receiving the scanning input of the scanning device, the electronic device may receive a first input of a first payment method from the user while displaying all payment methods installed on the electronic device, and generate a payment method list in response to the first input. The payment method list may include at least the first payment method, which is any one of all payment methods in the electronic device.

Optionally, the first input may be a touch input of the user for the first payment method, and the touch input may be a click input or a long press input, etc.

For example, the first payment method is payment method 1. As shown in FIG3 , the user can trigger the electronic device to display all installed payment methods, i.e., payment method 1 to payment method 8, by inputting "payment method" in the search bar 31. After that, the user can click on the icon of payment method 1 to input, thereby triggering the electronic device to generate a payment method list including payment method 1.

Step 102: When the payment method list of the electronic device includes at least one payment method among M payment methods, determine a target payment method from the at least one payment method, and perform a payment operation based on the target payment method.

Optionally, after determining the M payment methods supported by the scanning device, the electronic device may determine whether at least one of the M payment methods is included by traversing the payment method list. For example, if the M payment methods include payment method 1 and payment method 2, and the payment method list includes payment method 1, payment method 2, and payment method 3, the electronic device may determine that the payment method list includes payment method 1 and payment method 2 of the M payment methods.

Optionally, after determining at least one payment method, the electronic device may determine a target payment method from the at least one payment method according to preset rules, wherein the preset rules may include at least one of the following: the frequency of use of the at least one payment method in the payment method list, the time when the at least one payment method is added to the payment method list, and the arrangement order of the at least one payment method in the payment method list.

Optionally, the electronic device may determine the most frequently used payment method among at least one payment method as the target payment method; or, determine the payment method among at least one payment method that was added to the payment method list the earliest as the target payment method; or, determine the payment method among at least one payment method that is ranked highest in the payment method list as the target payment method.

For example, if the preset rule is the frequency of use of at least one payment method in the payment method list, if the electronic device determines that the payment method list includes payment method 1 and payment method 2 among M payment methods, and the frequency of use of payment method 1 is higher than that of payment method 2, the electronic device may determine payment method 1 as the target payment method.

Optionally, after being determined as the target payment method, the electronic device can send a payment instruction to the target payment backend of the target payment method, so that the target payment backend performs the payment operation according to the payment instruction and the order information sent by the scanning device; thereafter, the electronic device can receive a payment success prompt message sent by the target payment backend.

Specifically, since the first graphic code includes the payment information of the payment method in the payment method list, after scanning the first graphic code, the code scanning device can send order information to the payment backend of each payment method in the payment method list respectively. After the electronic device determines the target payment method, the electronic device can send a payment instruction to the target payment backend. The target payment backend can perform the payment operation after receiving the payment instruction and order information. That is to say, after receiving the order information, the payment backend needs to wait for the instruction of the payment instruction before performing the payment operation. Afterwards, after the payment is successful, the payment backend can send a prompt message of successful payment to the electronic device and the code scanning device respectively.

In an embodiment of the present application, since the target payment method supported by the scanning device can be automatically determined from the payment method list of the electronic device, the user does not need to manually search for the payment method, which simplifies the user operation and avoids the problem of the user spending a lot of time searching for the payment method.

Optionally, after obtaining the scanning request from the scanning device, the above method may further include steps 103-105:

Step 103: When the payment method list of the electronic device does not include at least one payment method, the electronic device displays a payment method adding interface.

Among them, the above-mentioned payment method adding interface may include N payment methods, including K payment methods that are highlighted, the K payment methods are payment methods supported by the scanning device, N and K are positive integers, and N is greater than or equal to K.

Exemplarily, taking N as 8 and K as 1 as an example, the payment method supported by the scanning device is payment method 8, and the payment method list includes payment method 1, payment method 2, and payment method 3. After traversing the payment method list, the electronic device can determine that payment method 8 is not included in the payment method list, so it can display the payment method adding interface shown in Figure 4, in which the icons of payment method 1, payment method 2, and payment method 3 include a first identifier 41, and the first identifier 41 is used to indicate the payment method that has been added to the payment method list, and the icon of payment method 8 includes a second identifier 42, and the second identifier 42 is used to indicate the payment method supported by the scanning device.

Step 104: The electronic device receives a second input from the user for a second payment method among the K payment methods.

Continuing to refer to FIG. 4 , since K is 1, payment method 8 is the second payment method. If the user wants to add payment method 8 to the payment method list, the user can make a second input for payment method 8, and accordingly, the electronic device can receive the second input.

Optionally, the second input may be a touch input of the second payment method by the user, and the touch input may be a click input or a long press input, etc.

Step 105: In response to the second input, the electronic device adds the second payment method to the payment method list and displays the second graphic code.

The second graphic code may include payment information of the second payment method.

The electronic device may add a second payment method to the payment method list in response to a first input. For example, if the payment method list includes payment method 1, payment method 2, and payment method 3 before receiving the first input, then after receiving a second input for payment method 8, the electronic device may add payment method 8 to the payment method list, i.e., the payment method list includes payment method 1, payment method 2, payment method 3, and payment method 8.

After updating the payment method list, the electronic device may generate and display a second graphic code according to the updated payment method list so that the scanning device can re-scan, and the electronic device may re-execute the above steps 101 and 102.

In an embodiment of the present application, since at least one payment method is not included in the payment method list of the electronic device, a second payment method supported by the scanning device can be added to the payment method list through the user's second input, and a second graphic code including payment information of the second payment method is displayed. Therefore, the payment scenario needs when the merchant's payment method is different from the payment method in the payment method list can be met.

It should be noted that the payment method provided in the embodiment of the present application can be executed by a payment device or a control module in the payment device for executing the payment method. In the embodiment of the present application, the payment device provided in the embodiment of the present application is described by taking the payment method executed by the payment device as an example.

As shown in FIG5 , the embodiment of the present application further provides a payment device 500, comprising: a display module 501, a receiving module 502 and a processing module 503. The receiving module 502 can be used to receive a scan input of a scanning device when the display module 501 displays a first graphic code, and obtain a scan request of the scanning device, wherein the scan request includes M payment methods supported by the scanning device. The processing module 503 can be used to determine a target payment method from the at least one payment method when a payment method list includes at least one payment method of the M payment methods, and perform a payment operation based on the target payment method; wherein the first graphic code includes payment information of the payment method in the payment method list, and M is a positive integer.

Optionally, the above-mentioned processing module 503 can be specifically used to: determine the target payment method from the at least one payment method according to preset rules; wherein the preset rules include at least one of the following: the frequency of use of the at least one payment method in the payment method list, the time when the at least one payment method is added to the payment method list, and the arrangement order of the at least one payment method in the payment method list.

Optionally, the device 500 may further include a sending module 504. The sending module 504 may be used to send a payment instruction to a target payment backend of the target payment method, so that the target payment backend performs a payment operation according to the payment instruction and the order information sent by the scanning device. The receiving module 502 may also be used to receive a prompt message of successful payment sent by the target payment backend.

Optionally, the receiving module 502 may also be used to receive a first input of a first payment method from a user before receiving a scanning input from a scanning device, when the display module 501 displays all installed payment methods. The processing module 503 may also be used to generate the payment method list in response to the first input; wherein the payment method list includes at least the first payment method, and the first payment method is any one of all the payment methods.

Optionally, the display module 501 can also be used to display a payment method adding interface when the at least one payment method is not included in the payment method list, the payment method adding interface including N payment methods, the N payment methods including K payment methods that are highlighted, and the K payment methods are payment methods supported by the scanning device. The receiving module 502 can also be used to receive a second input from a user for a second payment method among the K payment methods. The processing module 503 can also be used to add the second payment method to the payment method list in response to the second input, and display a second graphic code; wherein the second graphic code includes payment information of the second payment method, N and K are positive integers, and N is greater than or equal to K.

In an embodiment of the present application, since the target payment method supported by the scanning device can be automatically determined from the payment method list, the user does not need to manually search for the payment method, which simplifies the user operation and avoids the problem of the user spending a lot of time searching for the payment method.

The payment device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

The payment device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

The payment device provided in the embodiment of the present application can implement each process implemented by the method embodiments of Figures 1 to 4, and will not be described again here to avoid repetition.

Optionally, as shown in Figure 6, an embodiment of the present application also provides an electronic device 600, including a processor 601, a memory 602, and a program or instruction stored in the memory 602 and executable on the processor 601. When the program or instruction is executed by the processor 601, each process of the above-mentioned payment method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

FIG. 7 is a schematic diagram of the hardware structure of an electronic device implementing an embodiment of the present application.

The electronic device 1000 includes but is not limited to components such as a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.

Those skilled in the art can understand that the electronic device 1000 can also include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 1010 through a power management system, so that the power management system can manage charging, discharging, and power consumption. The electronic device structure shown in FIG7 does not constitute a limitation on the electronic device, and the electronic device can include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.

The user input unit 1007 may be used to receive a scan input from a scanning device when the display unit 1006 displays the first graphic code, and obtain a scan request from the scanning device, wherein the scan request includes M payment methods supported by the scanning device. The processor 1010 may be used to determine a target payment method from the at least one payment method when the payment method list includes at least one payment method from the M payment methods, and perform a payment operation based on the target payment method; wherein the first graphic code includes payment information of the payment method in the payment method list, and M is a positive integer.

In the embodiment of the present application, since the target payment method supported by the scanning device can be automatically determined from the payment method list, the user does not need to manually search for the payment method, which simplifies the user operation and avoids the problem of the user spending a lot of time searching for the payment method.

Optionally, the above-mentioned processor 1010 can be specifically used to: determine the target payment method from the at least one payment method according to preset rules; wherein the preset rules include at least one of the following: the frequency of use of the at least one payment method in the payment method list, the time when the at least one payment method is added to the payment method list, and the arrangement order of the at least one payment method in the payment method list.

In an embodiment of the present application, since the target payment method can be determined from at least one payment method according to preset rules, when at least one payment method includes multiple payment methods, the target payment method can be quickly determined and the payment operation can be performed based on the target payment method.

Optionally, the radio frequency unit 1001 can be used to send a payment instruction to the target payment backend of the target payment method, so that the target payment backend performs a payment operation according to the payment instruction and the order information sent by the scanning device. The user input unit 1007 can also be used to receive a prompt message of successful payment sent by the target payment backend.

In the embodiment of the present application, since a payment instruction can be sent to the target payment backend, the target payment backend can perform a payment operation according to the payment instruction. In this way, when the payment method list includes multiple payment methods, the payment backend of each payment method can determine whether a payment operation needs to be performed.

Optionally, the user input unit 1007 may also be used to receive a first input of a first payment method from a user before receiving the scanning input of the scanning device, when the display unit 1006 displays all installed payment methods. The processor 1010 may also be used to generate the payment method list in response to the first input; wherein the payment method list includes at least the first payment method, and the first payment method is any one of all the payment methods.

In the embodiment of the present application, since the generation of a payment method list can be triggered by the first input of the first payment method, a payment basis can be provided for the scanning device to support different payment methods.

Optionally, the display unit 1006 may also be used to display a payment method adding interface when the at least one payment method is not included in the payment method list, the payment method adding interface including N payment methods, the N payment methods including K payment methods highlighted, and the K payment methods being payment methods supported by the scanning device. The user input unit 1007 may also be used to receive a second input from a user for a second payment method among the K payment methods. The processor 1010 may also be used to add the second payment method to the payment method list and display a second graphic code in response to the second input; wherein the second graphic code includes payment information of the second payment method, N and K are positive integers, and N is greater than or equal to K.

In the embodiment of the present application, since the target payment method supported by the scanning device can be automatically determined from the payment method list, the user does not need to manually search for the payment method, which simplifies the user operation and avoids the problem of the user spending a lot of time searching for the payment method.

It should be understood that in the embodiment of the present application, the input unit 1004 may include a graphics processor (Graphics Processing Unit, GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, a function key (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here. The memory 1009 can be used to store software programs and various data, including but not limited to applications and operating systems. The processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the modem processor may not be integrated into the processor 1010.

An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned payment method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned payment method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

It should be noted that, in this article, the term "comprises", "includes" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims (8)

1. A method of payment, comprising:

Under the condition of displaying a first graphic code, receiving scanning input of a scanning device, and obtaining a scanning request of the scanning device, wherein the scanning request comprises M payment modes supported by the scanning device;

in the case that at least one payment method of the M payment methods is included in the payment method list, determining a target payment method from the at least one payment method, and executing a payment operation based on the target payment method;

wherein, the first graphic code comprises payment information of a payment mode in the payment mode list, M is a positive integer;

Displaying a payment mode adding interface under the condition that the payment mode list does not comprise at least one payment mode, wherein the payment mode adding interface comprises N payment modes, the N payment modes comprise K highlighted payment modes, and the K payment modes are supported by the scanning equipment;

Receiving a second input of a user to a second payment mode of the K payment modes;

Adding the second payment means to the payment means list in response to the second input and displaying a second graphical code;

the second graphic code includes payment information of the second payment mode, N, K is a positive integer, and N is greater than or equal to K.

2. The payment method of claim 1, wherein the determining a target payment method from the at least one payment method comprises:

Determining the target payment mode from the at least one payment mode according to a preset rule;

Wherein the preset rule comprises at least one of the following: the use frequency of the at least one payment mode in the payment mode list, the time of adding the at least one payment mode to the payment mode list and the arrangement sequence of the at least one payment mode in the payment mode list.

3. The payment method of claim 1, wherein the performing a payment operation based on the target payment means comprises:

Sending a payment instruction to a target payment background of the target payment mode, so that the target payment background executes payment operation according to the payment instruction and order information sent by the scanning equipment;

And receiving prompt information of successful payment sent by the target payment background.

4. A payment method as claimed in any one of claims 1 to 3, wherein prior to receiving a scan input from a scanning device, the method further comprises:

receiving a first input of a first payment means by a user while displaying all payment means installed;

generating the payment means list in response to the first input;

the payment mode list at least comprises the first payment mode, and the first payment mode is any one of all payment modes.

5. A payment device, comprising: the device comprises a display module, a receiving module and a processing module;

The receiving module is used for receiving the scanning input of the scanning equipment under the condition that the display module displays the first graphic code, and obtaining a scanning request of the scanning equipment, wherein the scanning request comprises M payment modes supported by the scanning equipment;

the processing module is used for determining a target payment mode from at least one payment mode and executing payment operation based on the target payment mode when the payment mode list comprises at least one payment mode of the M payment modes;

wherein, the first graphic code comprises payment information of a payment mode in the payment mode list, M is a positive integer;

The display module is further configured to display a payment manner adding interface when the at least one payment manner is not included in the payment manner list, where the payment manner adding interface includes N payment manners, and the N payment manners include K highlighted payment manners, and the K payment manners are payment manners supported by the scanning device;

The receiving module is further configured to receive a second input of a user to a second payment manner among the K payment manners;

The processing module is further configured to add the second payment method to the payment method list and display a second graphic code in response to the second input;

the second graphic code includes payment information of the second payment mode, N, K is a positive integer, and N is greater than or equal to K.

6. The payment device of claim 5, wherein the processing module is specifically configured to: determining the target payment mode from the at least one payment mode according to a preset rule; wherein the preset rule comprises at least one of the following: the use frequency of the at least one payment mode in the payment mode list, the time of adding the at least one payment mode to the payment mode list and the arrangement sequence of the at least one payment mode in the payment mode list.

7. The payment device of claim 5, further comprising a transmission module;

The sending module is used for sending a payment instruction to a target payment background of the target payment mode so that the target payment background executes payment operation according to the payment instruction and order information sent by the scanning equipment;

The receiving module is further used for receiving prompt information of successful payment sent by the target payment background.

8. A payment device as recited in any one of claims 5 to 7, wherein,

The receiving module is further configured to receive a first input of a first payment mode from a user under the condition that the display module displays all installed payment modes before receiving the scan input of the scanning device;

the processing module is further configured to generate the payment manner list in response to the first input;

the payment mode list at least comprises the first payment mode, and the first payment mode is any one of all payment modes.