Payment method and device, electronic equipment and computer readable storage medium

Abstract

The embodiment of the invention provides a payment method and device, electronic equipment and a computer readable storage medium, and relates to the technical field of payment, WeChat payment and block chains. The method is executed by the electronic equipment, the electronic equipment comprises a first display screen and a second display screen, and the method comprises the following steps: displaying a first client interface of a first applet through the first display screen, displaying a second client interface of a second applet through the second display screen, and displaying first order information of a target order on the first client interface, displaying second order information of the target order on a second client interface; and in response to a payment triggering operation for the target order received through the target client interface, performing payment processing on the target order. According to the scheme, the two applets are operated in the electronic equipment at the same time, the order information of the target order is displayed through the display screens corresponding to the two applets respectively, payment processing of the target order is achieved, and the payment experience can be improved.

Description

[0001] This application is a divisional application of the invention patent application with application number "202110620041.0" and the invention title "Payment Method, Apparatus, Electronic Device and Computer-Readable Storage Medium". Technical Field

[0002] This application relates to the fields of payment, WeChat payment, and blockchain technology. Specifically, this application relates to a payment method, device, electronic device, and computer-readable storage medium. Background Technology

[0003] With the development of internet technology, mobile payment has become one of the main payment methods. Its payment method is simple and brings convenience to users' lives.

[0004] There are many existing offline payment methods, most of which are based on a single screen. This means that the cashier initiates the payment based on the order displayed on a single screen, and the customer passively makes the payment, resulting in a poor payment experience. Summary of the Invention

[0005] The purpose of this application is to provide a payment method, apparatus, electronic device, and computer-readable storage medium that can improve the payment experience.

[0006] On one hand, embodiments of this application provide a payment method executed by an electronic device, the electronic device including a first display screen and a second display screen, the method including: The first client interface of the first mini-program is displayed on the first display screen, and the second client interface of the second mini-program is displayed on the second display screen, wherein the first mini-program and the second mini-program are related mini-programs; The first order information of the target order is displayed on the first client interface, and the second order information of the target order is displayed on the second client interface. The first and second order information are generated based on the product information of the goods to be paid for, which is collected by the product information collection device. In response to a payment trigger operation received through the target client interface for the target order, process the payment for the target order; The target client interface mentioned above is at least one of the first client interface or the second client interface.

[0007] On the other hand, embodiments of this application provide a payment device, which includes a first display screen, a second display screen, and a processor, wherein the first display screen and the second display screen are respectively connected to the processor; The first display screen is used to display the first client interface of the first mini-program, and the second display screen is used to display the second client interface of the second mini-program, wherein the first mini-program and the second mini-program are related mini-programs; The processor is configured to generate first order information and second order information for a target order upon receiving product information of a product to be paid for, collected through a product information collection device; display the first order information through a first client interface and the second order information through a second client interface; and process the payment of the target order information upon receiving a payment trigger operation for the target order received through the target client interface. The target client interface mentioned above is at least one of the first client interface or the second client interface.

[0008] Furthermore, embodiments of this application provide a payment device included in an electronic device, the electronic device including a first display screen and a second display screen, the device comprising: The interface display module is used to display the first client interface of the first mini-program on the first display screen and the second client interface of the second mini-program on the second display screen, wherein the first mini-program and the second mini-program are related mini-programs; The order display module is used to display the first order information of the target order on the first client interface and the second order information of the target order on the second client interface. The first and second order information are generated based on the product information of the goods to be paid for, which is collected by the product information collection device. The order processing module is used to process payments for target orders in response to payment trigger operations received through the target client interface. The target client interface mentioned above is at least one of the first client interface or the second client interface.

[0009] Optionally, when the order processing module processes a payment for a target order in response to a payment trigger operation received through the target client interface, it specifically performs the following: Display at least one payment method option on the first client interface; In response to a selection operation of a target payment method among at least one payment method options received through a first client interface, the target order is processed for payment using the target payment method. The payment trigger operation includes the selection operation, and the target client interface includes the first client interface.

[0010] Optionally, the above-mentioned payment method options include facial recognition payment and non-facial recognition payment. If the target payment method is non-facial recognition payment, the order processing module, when processing payment for the target order using the target payment method, specifically uses: Displays the payment interface corresponding to the target payment method for the target order; In response to a payment confirmation action for a target order, the payment for the target order is processed using the target payment method; the payment triggering action also includes a payment confirmation action.

[0011] Optionally, if the target payment method is facial recognition payment, the order processing module will process the payment for the target order using the target payment method, specifically for: The system uses image acquisition devices to collect facial information of users who are paying for target orders. Send the amount to be paid for the target order and the facial information to the payment server corresponding to the facial payment method, so that the payment server can process the payment for the target order based on the facial information.

[0012] Optionally, the second client interface displays a payment control. When the order processing module displays at least one payment method option on the first client interface, it is specifically used for: In response to a selection trigger action for the payment control, at least one payment method option is displayed on the first client interface; The target client interface also includes a second client interface, and the payment triggering operation also includes selecting a triggering operation.

[0013] Optionally, the device may also include: The startup module is used to respond to a first startup operation on the electronic device, load a first mini-program and a second mini-program respectively, and display the first initialization interface of the first mini-program on a first display screen and the second initialization interface of the second mini-program on a second display screen.

[0014] Optionally, when the startup module loads the second applet in response to a first startup operation on the electronic device, it is specifically used for... In response to a first startup operation on an electronic device, a second display screen is activated, and the second display screen displays at least one application identifier, including the application identifier corresponding to the second mini-program. In response to a trigger operation targeting the application identifier corresponding to the second mini-program, load the second mini-program.

[0015] Optionally, the first client interface displays a setting indicator. When the first client interface cannot display information, the device further includes: The fault handling module is used to reload the first mini-program in response to a trigger operation based on a set identifier.

[0016] On the other hand, embodiments of this application also provide an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the payment method provided in any optional embodiment of this application when running the computer program.

[0017] On the other hand, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when run by a processor, executes the payment method provided in any optional embodiment of this application.

[0018] Furthermore, embodiments of this application also provide a computer program product or computer program that, when run on a computer device, causes the computer device to execute any of the optional implementation methods provided in this application. The computer program product or computer program includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the payment method provided in any optional implementation of this application.

[0019] The beneficial effects of the technical solution provided in this application are as follows: The solution provided in this application embodiment can display the first client interface of a first mini-program on the first display screen of an electronic device, and the second client interface of a second mini-program on the second display screen. The first client interface displays the first order information of the target order, and the second client interface displays the second order information of the target order. Since the order information is displayed through two client interfaces, during payment, a payment trigger operation for the target order can be received through either the first or second client interface, and the payment for the target order can be processed in response to this operation. In this application solution, on the one hand, displaying order information through two client interfaces allows both the payer and the payee to have a detailed understanding of the target order before payment processing, thereby improving the user's payment experience. On the other hand, since the two client interfaces correspond to two mini-programs, and two mini-programs run simultaneously on the electronic device, payment can be realized based on the functions corresponding to these two mini-programs, thus improving the user experience of the electronic device. Additional aspects and advantages of this application will be set forth in part in the description which follows, and will become apparent from the description or may be learned by practice of this application. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0021] Figure 1A flowchart illustrating a payment method provided in an embodiment of this application; Figure 2 A schematic diagram of a mini-program container provided in an embodiment of this application; Figure 3 A schematic diagram of a mini-program process provided in an embodiment of this application; Figure 4 A schematic diagram illustrating the mini-program processes corresponding to two mini-programs, provided as an embodiment of this application; Figure 5 A schematic diagram of a first client interface provided in an embodiment of this application; Figure 6 A schematic diagram of a second client interface provided in an embodiment of this application; Figure 7 A schematic diagram of yet another second client interface provided in an embodiment of this application; Figure 8 A schematic diagram of an animation information display interface provided in an embodiment of this application. Figure 9 A schematic diagram of a message transmission process provided in an embodiment of this application; Figure 10 This application provides a schematic diagram of a dual-screen interaction process. Figure 11 This is a schematic diagram of the structure of a face payment system provided in an embodiment of this application; Figure 12 This is a schematic diagram of the structure of a payment device provided in an embodiment of this application; Figure 13 This is a schematic diagram of the structure of another payment device provided in an embodiment of this application; Figure 14 This is a schematic diagram of the structure of a payment device provided in an embodiment of this application; Figure 15 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting the invention.

[0023] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0024] The payment method provided in this application embodiment can be applied to various practical application scenarios, such as facial recognition payment, payment password payment, WeChat payment, etc.

[0025] The methods provided in the various optional embodiments of this application, which involve the extraction of facial features and the determination of identity information based on facial information, can be implemented using artificial intelligence technology.

[0026] Artificial intelligence (AI) is the theory, methods, technology, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to achieve optimal results. In other words, AI is a comprehensive technology within computer science that attempts to understand the essence of intelligence and produce a new kind of intelligent machine that can react in a way similar to human intelligence. AI studies the design principles and implementation methods of various intelligent machines, enabling them to possess the functions of perception, reasoning, and decision-making.

[0027] The processing of facial information involved in the embodiments of this application can be implemented using cloud technology. For example, the data storage involved in the processing can be implemented using cloud storage, and the data calculation involved in the processing can be implemented using cloud computing.

[0028] The solution provided in this application can be executed by any electronic device, including a user terminal device (payment device) or a server (payment server). The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The terminal device can include at least one of the following: smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, smart TV, or smart in-vehicle device.

[0029] In one possible implementation, the payment device and the payment server can form a blockchain, and the payment server and the payment device can be nodes on the blockchain. The payment method in this application embodiment can be executed by at least one node on the blockchain. That is, the payment server or server cluster in this application embodiment can be one or at least two nodes on the blockchain, and the payment device in this application embodiment can be one node on the blockchain.

[0030] To better understand and describe the solutions provided in the embodiments of this application, some technical terms involved in the embodiments of this application will be explained below.

[0031] Dual-screen facial recognition device: A dual-screen facial recognition payment terminal, typically with the front screen for customers and the back screen for cashiers.

[0032] IoT Mini Programs: IoT (Internet of Things) refers to mini programs that can run on hardware devices that are independent of the WeChat terminal environment. In this application, it refers to mini programs that run on hardware devices equipped with the Android system.

[0033] Mini Program Runtime: This refers to the running instance of a mini program, used to refer to each individual instance of a running mini program.

[0034] Mini Program Container: The runtime container for each mini program. The mini program container can provide parameters for displaying the client interface of the mini program. In this application's solution, based on the parameters in the mini program container corresponding to the mini program, it is possible to know what the client interface of the mini program to be displayed will look like.

[0035] Process isolation: A technique to prevent process A from writing to process B.

[0036] AppId of a Mini Program: AppId is used to identify the identity of a Mini Program and is a unique ID of the Mini Program.

[0037] JsEvent: This is a role in the mini-program framework similar to the mini-program interface. It can be understood as a passive callback function used to receive event notifications from the mini-program container and to distribute the notifications to the target mini-program's runtime.

[0038] IPC message pipe: IPC (Inter-Process Communication) is a message channel implemented using Android's own IPC mechanism, used for cross-process message transmission.

[0039] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0040] This application provides a possible implementation method, such as... Figure 1 The diagram illustrates a flowchart of a payment method. This method can be executed by any electronic device. For example, the method in this embodiment can be executed on a terminal device or a server, or interactively executed by a terminal device (referred to as a payment device in this embodiment) and a server (referred to as a payment server in this embodiment). For ease of description, the method provided in this embodiment will be described below using an electronic device (payment device) as the execution subject.

[0041] Figure 1 This application illustrates a flowchart of a payment method according to an embodiment of the present application. The method is executed by an electronic device, which includes a first display screen and a second display screen, such as... Figure 1 As shown, the method may include the following steps: Step S110: Display the first client interface of the first mini-program on the first display screen, and display the second client interface of the second mini-program on the second display screen, wherein the first mini-program and the second mini-program are related mini-programs.

[0042] Before displaying the first client interface and the second client interface, the method further includes: In response to a first startup operation on the electronic device, a first mini-program and a second mini-program are loaded respectively, and a first initialization interface of the first mini-program is displayed on a first display screen, and a second initialization interface of the second mini-program is displayed on a second display screen.

[0043] The first startup operation refers to activating an electronic device with two displays, enabling dual-screen payment. This first startup operation can be a touch operation on the device's startup button, such as a long press or a click. After the electronic device starts, both displays and the corresponding mini-program are launched, displaying the client interface on the displays.

[0044] When loading the first mini-program, relevant information, including the initial setup interface, can be loaded and displayed from the server corresponding to that mini-program. Similarly, when loading the second mini-program, relevant information, including the second setup interface, can be loaded and displayed from the server corresponding to that mini-program. The two mini-programs can correspond to the same server, or each can correspond to a separate server.

[0045] Optionally, the first mini-program and the second mini-program can correspond to the same mini-program container, or they can each correspond to a separate mini-program container. If the first mini-program and the second mini-program each correspond to a separate mini-program container, for ease of description, the container corresponding to the first mini-program can be called the first container, and the container corresponding to the second mini-program can be called the second container. These two containers are isolated. When the first mini-program is loaded, it can be run through the first container to display the first client interface on the first display screen. Similarly, when the second mini-program is loaded, it can be run through the second container to display the second client interface on the second display screen. The first client interface may include a first initialization interface, and the second client interface may include a second initialization interface.

[0046] When the electronic device is started, a first container is launched. Launching the first container involves launch parameters, which may include the app ID of the mini-program, such as the App ID of the first mini-program. The first container can then determine which mini-program to run based on the App ID. The launch parameters may also include display information about the first client interface of the first mini-program. This display information describes the specific format of the first client interface, and based on this information, the first container can display the first client interface on a first display screen.

[0047] Optionally, the first and second mini-programs in this application can be IoT mini-programs.

[0048] like Figure 2 The diagram shown illustrates the mini-program container. Figure 2 The IoT mini-program in the context can be either the first mini-program or the second mini-program. Each mini-program corresponds to a mini-program container, through which the corresponding mini-program can be run.

[0049] Optionally, the first or second mini-program mentioned above can be a mini-program running under the settings application, that is, the mini-program can be called through the interface of the settings application. In this case, you need to log in to the settings application before calling the mini-program.

[0050] Optionally, when the first or second mini-program is running, the corresponding mini-program process can be invoked, so that the mini-program runs in the corresponding mini-program process.

[0051] As an example, such as Figure 3 The diagram shown illustrates the structure of a mini-program during runtime. Figure 3In this context, "Login State 1" refers to the login state of the application corresponding to the user of the mini-program (the user can be a customer or a cashier). After the user logs into the application, i.e., in Login State 1, the mini-program instance (mini-program Runtime) corresponding to the mini-program can be run through the mini-program container.

[0052] As yet another example, such as Figure 4 The diagrams shown illustrate the structure of the two mini-programs during runtime. Figure 4 In this context, the front screen (first display screen) process refers to the process corresponding to the first mini-program, the back screen (second display screen) process refers to the process corresponding to the second mini-program, login state 1 refers to the login state of the user (customer) corresponding to the first mini-program's settings application, and login state 2 refers to the login state of the user (cashier) corresponding to the second mini-program's settings application. After a customer logs into the settings application, i.e., in login state 1, the mini-program instance (mini-program Runtime) corresponding to the first mini-program can be run through the mini-program container of the first mini-program. Similarly, after a cashier logs into the settings application, i.e., in login state 2, the mini-program instance (mini-program Runtime) corresponding to the second mini-program can be run through the mini-program container of the second mini-program.

[0053] Optionally, in response to a first startup operation on the electronic device, the second applet is loaded, including: In response to a first startup operation on an electronic device, a second display screen is activated, and the second display screen displays at least one application identifier, including the application identifier corresponding to the second mini-program. In response to a trigger operation targeting the application identifier corresponding to the second mini-program, load the second mini-program.

[0054] The second display screen can show at least one application identifier. Each identifier can correspond to either a mini-program or an application. Since the second display screen is intended for merchant staff, in addition to displaying the application identifier for the mini-program with payment functionality, it can also display application identifiers for other functional applications or mini-programs, such as mini-programs with inventory management or personnel management functions. When the second mini-program needs to be loaded, the merchant staff must select its application identifier from the at least one displayed on the second display screen; this is a trigger operation based on the application identifier of the second mini-program. The second mini-program can then be loaded based on this trigger operation. The merchant staff initiate this trigger operation.

[0055] The system comprises two mini-programs: a first display screen (facing customers), a second display screen (facing cashiers), and a client interface (user interface for displaying information to both cashiers and customers). A first mini-program displays information to customers and handles actions triggered by customers on the first client interface. It primarily receives actions triggered by customers on the first client interface and displays information sent from the second display screen to the first display screen—in other words, information that the merchant's staff wants customers to see. A second mini-program displays information to merchant staff and handles actions triggered by merchant staff on the second client interface. It primarily receives actions triggered by merchant staff on the second client interface and displays information sent from the first display screen to the second display screen—in other words, information that customers want merchant staff to see.

[0056] The first and second mini-programs are linked and can work together to complete the payment function. This linking can be achieved by establishing a relationship between the mini-program IDs of the first and second mini-programs.

[0057] As an example, such as Figure 6 The diagram shown is of the second client interface, which is the client interface corresponding to the back screen. The back screen is the second display screen facing the cashier. This interface displays two application identifiers, one is application identifier A, and the other is application identifier B. Application identifier B is the application identifier corresponding to the second mini program. In response to the trigger operation of application identifier B, the second mini program can be loaded.

[0058] Step S120: Display the first order information of the target order on the first client interface and the second order information of the target order on the second client interface. The first and second order information are generated based on the product information of the goods to be paid for, which is collected by the product information collection device.

[0059] The first order information and the second order information can be different types of information corresponding to the same order (target order), or they can be the same information. If the first order information and the second order information are different types of information, since the first order information is customer-facing, this information can mainly include product information of the purchased goods, such as product name, unit price, quantity, and amount to be paid. Since the second order information is merchant cashier-facing, this second order information can mainly include product information of the goods purchased by the customer and product information of related goods, such as inventory information and the total purchase volume of a certain product within a certain period of time.

[0060] The product information collection device can be an external device to the electronic device or part of the electronic device itself. If it is an external device, after collecting the product information of the product to be paid for through the product information collection device, the product information is sent to the electronic device.

[0061] Optionally, the aforementioned first order information and second order information can be determined in the following ways: The system receives product information of goods to be paid for from the product information collection device, and generates first order information and second order information based on the product information of the goods to be paid for.

[0062] The product information for the goods pending payment may include, but is not limited to, the product name, unit price, quantity, and the outstanding payment amount. This product information is collected by the merchant's staff, such as cashiers.

[0063] The first and second order information can be displayed at the same or different times. For example, the first order information can be displayed on the first client interface simultaneously, while the second order information is displayed on the second client interface. Alternatively, the second order information can be displayed on the second client interface first, which also displays a payment control. When a trigger operation is received for the payment control, the first order information is displayed on the first client interface in response to the trigger operation.

[0064] Step 130: In response to a payment trigger operation received through the target client interface for the target order, process the payment for the target order. The target client interface is at least one of a first client interface or a second client interface.

[0065] In this context, a payment trigger operation refers to the action of initiating payment for a target order. This operation is initiated by a user (who can be a customer or a merchant employee) on the target client interface of the payment device. This interface is the interface through which the user interacts with the payment device. This interface can be the interface containing the first order information (the first client interface), in which case the payment trigger operation is performed on that interface. Alternatively, the target client interface can be the interface containing the second order information (the second client interface), in which case the payment trigger operation is performed on that interface. Furthermore, the target client interface can be both the first and second client interfaces, in which case the payment trigger operation includes operations performed on both the first and second client interfaces.

[0066] Users can trigger this operation based on the payment identifier displayed on the target client interface. This payment identifier can be represented by at least one of characters, text, or graphics; the specific form of the payment identifier is not limited in this application. The payment trigger operation can be a click operation, a long press, etc., and the specific form of the trigger operation is not limited in this application.

[0067] In an optional embodiment of this application, the above-mentioned payment processing for the target order in response to a payment trigger operation received through the target client interface includes: Display at least one payment method option on the first client interface; In response to a selection operation of a target payment method among at least one payment method options received through a first client interface, the target order is processed for payment using the target payment method. The payment trigger operation includes the selection operation, and the target client interface includes the first client interface.

[0068] The payment trigger operation can be triggered on the first client interface, that is, the target client interface is the first client interface, which is faced by the customer. On this client interface, at least one payment method can be provided to the customer. Each payment method option corresponds to one payment method. The payment method can include at least one of the following: payment code, WeChat payment code, face payment method, and WeChat face payment method. Based on the above payment methods, the customer can choose the payment method they want to pay.

[0069] Optionally, the above-mentioned payment processing of the target order through the target payment method includes: sending the amount to be paid for the target order to the payment server corresponding to the target payment method, so that the payment server processes the payment for the target order.

[0070] Optionally, the first client interface may display payment controls, showing at least one payment method option, including: In response to a triggered action on the payment control, at least one payment method option is displayed on the first client interface.

[0071] The triggering of the payment control indicates a desire to make payment for the target order, and the payment method option can be displayed when the payment control is triggered. The payment control can be displayed on the first client interface in the form of a payment icon, which can be text, image, symbol, etc., and this application does not limit the specific form of the payment icon.

[0072] As an example, such as Figure 5The diagram shown is of the first client interface, which is the client interface corresponding to the front screen, which is the first display screen facing the customer. The first client interface displays the first order information, which includes product a1 and product a2. The first client interface also displays a payment control "Pay". In response to the trigger operation of the payment control, at least one payment method option can be displayed on the first client interface.

[0073] In an optional embodiment of this application, the second client interface displays payment controls, and the first client interface displays at least one payment method option, including: In response to a selection trigger action for the payment control, at least one payment method option is displayed on the first client interface; The target client interface also includes a second client interface, and the payment triggering operation also includes selecting a triggering operation.

[0074] The second client interface is for merchant staff. Payment triggering operations can also include operations triggered by merchant staff based on the selection of payment control, as well as operations by customers on the first client interface, that is, the payment is completed jointly by merchant staff and customers.

[0075] The triggering of the payment control indicates a desire to collect payment for the target order, and the payment method option can be displayed when the payment control is triggered. The payment control can be displayed on the second client interface in the form of a payment icon, which can be text, image, symbol, etc., and this application does not limit the specific form of the payment icon.

[0076] As an example, such as Figure 7 Another schematic diagram of the second client interface shown is shown. This second client interface is the client interface corresponding to the back screen, which is the second display screen facing the cashier. The second client interface displays second order information, which includes product a1 and product a2. The second client interface also displays a payment control "Payment". In response to the trigger operation of the payment control, at least one payment method option can be displayed on the first client interface.

[0077] The solution provided in this application embodiment can display a first client interface of a first mini-program on a first display screen of an electronic device, and a second client interface of a second mini-program on a second display screen. The first client interface displays the first order information of the target order, and the second client interface displays the second order information of the target order. Since order information is displayed through two client interfaces, during payment, a payment trigger operation for the target order can be received through either the first or second client interface, and payment processing can be performed in response to this operation. In this solution, on the one hand, displaying order information through two client interfaces allows both the payer and the payee to have a detailed understanding of the target order before payment processing, thereby improving the user's payment experience. On the other hand, since the two client interfaces correspond to two mini-programs, and both mini-programs run simultaneously on the electronic device, payment can be achieved based on the functions corresponding to these two mini-programs, improving the user experience of the electronic device.

[0078] On the other hand, since two related mini-programs can run simultaneously on an electronic device, enabling dual-screen communication, the maintenance and development of mini-programs is more convenient for technicians than that of applications, thus reducing development costs.

[0079] The above-mentioned payment method options may include facial recognition payment and non-facial recognition payment. Facial recognition payment may include, but is not limited to, WeChat facial recognition payment and Alipay facial recognition payment. Non-facial recognition payment may include, but is not limited to, payment code payment and payment password payment.

[0080] In an optional embodiment of this application, at least one payment method option includes facial recognition payment and non-facial recognition payment. If the target payment method is non-facial recognition payment, the payment process for the target order using the target payment method includes: Displays the payment interface corresponding to the target payment method for the target order; In response to a payment confirmation action for a target order, the payment for the target order is processed using the target payment method; the payment triggering action also includes a payment confirmation action.

[0081] The payment processing methods for facial recognition payment and non-facial recognition payment differ. Facial recognition payment requires obtaining facial information and processes the payment based on that information. Non-facial recognition payment does not require obtaining facial information; instead, it obtains the customer's payment information through the payment interface to complete the payment. For example, if the target payment method is a payment code, the payment interface will be the interface corresponding to the payment code. If the target payment method is WeChat Pay, the payment interface will be the interface corresponding to the WeChat payment code.

[0082] If the target payment method is not facial recognition, upon the customer's selection of a non-facial recognition payment method, the corresponding payment interface for that method will be displayed. On this interface, in response to the payment confirmation for the target order, payment can be processed using the target payment method. Specifically, the amount due for the target order can be sent to the payment server corresponding to the target payment method, enabling the payment server to process the payment.

[0083] In this case, a payment control may be displayed on the payment interface, and the payment confirmation operation can be a trigger operation on the payment control.

[0084] In an optional embodiment of this application, if the target payment method is facial recognition payment, the above-mentioned payment processing for the target order via the target payment method includes: The system uses image acquisition devices to collect facial information of users who are paying for target orders. Send the amount to be paid for the target order and the facial information to the payment server corresponding to the facial payment method, so that the payment server can process the payment for the target order based on the facial information.

[0085] Since the target payment method is facial recognition payment, in response to the selection of the target payment method, the image acquisition device can be invoked to collect the facial information of the user paying the target order. Then, a payment request and facial information are sent to the payment server corresponding to the facial recognition payment method. The request includes the amount to be paid for the target order. Based on the facial information, the server can determine the user's identity information, obtain the user's payment account based on the identity information, and finally deduct the amount to be paid from the payment account to complete the payment.

[0086] When using the facial recognition payment method based on this application, payment can be completed without the need for the customer's terminal device, further improving the user's payment experience.

[0087] Before using an image acquisition device to collect a user's facial information, it is necessary to obtain the user's permission before acquiring their identity information. This identity information refers to information that identifies the user, such as their ID card number or mobile phone number.

[0088] The image acquisition device can be part of the electronic device or an external device of the electronic device.

[0089] Optionally, the payment server mentioned above can determine the user's identity information based on facial information, which may include: Extracting facial features from facial information; The user's identity information is determined based on facial features and the facial features of each facial image stored in the database, as well as the identity information corresponding to each facial feature.

[0090] The database pre-stores facial features of multiple facial images and the identity information corresponding to each facial feature.

[0091] Among them, facial features in facial information can be extracted based on existing image feature extraction methods. For example, facial features can be extracted based on neural networks. The neural network can be a pre-trained network. The input of the neural network is facial information, and the output is facial features of the facial information.

[0092] Optionally, the user's identity information can be determined based on the feature distance between the facial features of the face information and the facial features in the database.

[0093] The smaller the feature distance between two facial features, the more similar the two facial features are. In this case, the identity information corresponding to the facial feature with the smallest feature distance to the facial features in the database can be determined as the user's identity information.

[0094] Optionally, the feature distance can be characterized by Euclidean distance.

[0095] In an optional embodiment of this application, the method further includes: In response to obtaining the payment result of the target order, the payment result is displayed in at least one of the second client interface or the first client interface.

[0096] After payment is processed, the payment result can be displayed on the client interface, indicating whether the payment was successful or failed.

[0097] Users can understand the payment status, i.e., whether the payment was successful, based on the payment result. This payment result can be represented by text, symbols, graphics, etc., and this application does not limit the specific form of the payment result. For example, the payment result can be the text "Payment Successful" or "Payment Failed," or it can be the symbols "√" or "×," where "√" indicates payment success and "×" indicates payment failure.

[0098] In an optional embodiment of this application, the method further includes: In response to a payment-triggered action, retrieve and display animation information; In response to receiving the payment result, the animation information display ends, and the payment result is displayed.

[0099] During the payment server's processing of a target order, the payment process may take some time, or network issues may prevent the payment device from quickly receiving the payment result, leading the user to mistakenly believe there is a problem with the payment (e.g., the payment device is frozen) and thus unable to complete the payment. To address this, an animation can be displayed on the payment device's client interface during the payment processing. Upon receiving the payment result from the payment server, the animation ends, and the payment result is displayed. This prevents the user from mistakenly believing there is a problem with the payment process, further improving the user experience.

[0100] The animation information can be pre-configured and stored in the payment device. Optionally, the animation information can be a spinning animation, and this application does not limit the specific form of the animation information.

[0101] The interface displaying the animation information can be at least one of the first client interface or the second client interface.

[0102] Optionally, in addition to displaying the animation information, a prompt message can also be displayed to inform the user of the current payment status (payment in progress). The prompt message can be text-based.

[0103] As an example, such as Figure 8 The diagram shown illustrates the display interface for animation information. In this example, the animation information is displayed on the second client interface, where the animation information is... Figure 8 The circles shown (corresponding to a spinning animation effect) also include prompts ( Figure 8 The message "Processing, please wait" is displayed.

[0104] Optionally, the image acquisition device can be invoked to collect the facial information of the user making the payment for the target order, including: Use image acquisition equipment to collect at least two facial images of the user who is paying for the target order; Identify face images that meet the set conditions from at least two face images, and use the face images that meet the set conditions as face information; The conditions set include at least one of the following: The proportion of the face size in the face image is greater than or equal to a first set value; The face capture angle meets the set angle; The image quality meets the set quality requirements.

[0105] The process involves using an image acquisition device to capture at least two facial images, which can be used as facial information. However, considering that some of the acquired facial images may affect the accuracy of facial recognition in practical applications, the at least two facial images are filtered to ensure that the user's identity information can be accurately identified based on the filtered facial images.

[0106] The facial shooting angle refers to the angle at which the face is captured, which includes the shooting height, shooting direction, and shooting distance. Different shooting angles result in different facial images.

[0107] Image quality can be reflected by different metrics, such as at least one of image contrast, sharpness, or brightness.

[0108] The face image can be one of at least two images. Face recognition is performed based on this face image, and the recognition result is used as the user's identity information.

[0109] Optionally, if the set conditions include at least two of the above indicators, then for each face image in at least two face images, based on the weights of the two indicators corresponding to the face image and the indicator corresponding to the face image, the image score of the face image is determined, and the face image with the highest image score among the at least two face images is determined as the face information.

[0110] Optionally, if the payment device acquires a user's facial video, then at least two facial images can be at least two consecutive facial images from the user's facial video.

[0111] Optionally, in the above-mentioned first and second displays, sending information from one display to the other includes: If the target information meets the set conditions, send the target information.

[0112] If the target information does not meet the set conditions, it also includes: Generate a prompt message and send it to the display screen of the target message.

[0113] The target information includes the target order, and the set conditions include at least one of the following: the target information conforms to the set information rules, and the mini-program corresponding to the display screen receiving the target information is associated with the mini-program corresponding to the display screen sending the target information.

[0114] The information setting rules are rules established for the information itself, such as the information length not exceeding a set length. The information length is affected by the communication mechanism used to transmit the information; therefore, based on the communication mechanism, the length of the transmitted information is set to ensure effective transmission. The connection between the mini-program corresponding to the receiving screen and the mini-program corresponding to the sending screen means that if one mini-program is the sending screen's mini-program, the other is the receiving screen's mini-program. For example, if the sending screen's mini-program is the first mini-program, then the receiving screen's mini-program is the second mini-program. If the receiving screen's mini-program is not the second mini-program, the target information is not sent, and a prompt message is generated and displayed on the first client interface of the first screen.

[0115] Optionally, the two mini-programs can each correspond to a processor, that is, the first mini-program corresponds to a processor (which can be called the front screen processor) and the second mini-program corresponds to a processor (which can be called the back screen processor). The two processors can communicate with each other. Sending information from one display screen to another display screen can also be understood as follows: if the sender of the target information is the first display screen and the receiver is the second display screen, then the first display screen will transmit the received target information to the front screen processor, the front screen processor will send the target information to the back screen processor, and the back screen processor will then send the target information to the second display screen for display.

[0116] As an example, the following combines Figure 9 Further explanation of the process of sending target information: such as Figure 9 The diagram shown illustrates the target information transmission process. Figure 9 In this process, the first display screen sends the target information to the front screen processor (the processor corresponding to the front screen mini-program). Before sending the target information, the front screen processor assembles the target information into a message structure. This message structure includes the mini-program ID (AppId) of the front screen mini-program and the message content (the specific content of the target information). The message content can be a plain string or a JSON structure. The message manager, which is the processor of the payment device, includes a front screen processor and a back screen processor. It is used to process information sent from the front and back screens and to control the display of corresponding information on the front and back screens. When sending target information, the target information is first sent to the front screen processor of the message manager. In this example, the front screen processor can be based on a set processing identifier, such as... Figure 9The alt identifier shown is used by the front-screen processor to generate a sending result notification and inform the front-screen mini-program whether the target information was successfully sent. In other words, regardless of whether the sending is successful or not, if the front-screen processor detects the alt identifier after sending the target information to the front-screen processor, it will execute the step of generating a sending result notification and informing the front-screen mini-program.

[0117] The front screen processor detects whether the target information meets the set conditions, and the conditions that are not met include... Figure 9 The back screen shown has no mini-programs (e.g., no second mini-program is currently running on the back screen), and the message content is too long (the message length exceeds the set length). If the target information meets the set conditions ( Figure 9 If the detection shown in the image passes, the front screen processor transmits the target information to the corresponding back screen processor of the back screen mini-program via the IPC (Inter-Process Communication) message pipeline. The back screen processor encapsulates the target information into a JsEvent (JavaScript event object) and finally generates a back screen mini-program Runtime (instance) through the back screen processor, so as to process the target information through this instance. Figure 9 (The processing message shown), for example, displays the target information on the second client interface of the second display screen.

[0118] Optionally, if the second mini-program malfunctions, the method further includes: In response to a trigger operation targeting the application identifier of the second mini-program displayed on the second client interface, reload the second mini-program.

[0119] This solution utilizes two mini-programs for payment. If the second mini-program malfunctions—for example, failing to display order information or receive user triggers—it can be manually restarted. This involves reloading the second mini-program in response to a trigger action targeting its application identifier. Compared to redownloading the entire application if it malfunctions, this solution reloads the mini-program faster, resulting in a better user experience. For instance, if a payment failure occurs, the shorter reload time reduces customer wait time and improves the payment experience.

[0120] Optionally, if the first client interface displays a set identifier, and the information cannot be displayed normally on the first client interface, the method further includes: In response to a trigger action on the setting identifier displayed on the first client interface, the first mini-program is reloaded.

[0121] If the first client interface fails to display information correctly, it indicates a potential malfunction in the first mini-program. In this case, the first mini-program can be reloaded based on a triggered action of a set flag. This set flag can be a shutdown flag for the first client interface when a malfunction occurs. Triggering an action on this shutdown flag will close the first client interface and simultaneously reload the first mini-program.

[0122] The closing indicator can be text, symbols, etc., and this application does not limit the specific form of the closing indicator. For example, it could be " ".

[0123] Optionally, after reloading the mini-program, the content displayed on the corresponding client interface after reloading is the same content displayed when the mini-program malfunctioned. That is, the data corresponding to the malfunction is cached in the electronic device. In this way, when reloading the mini-program, the cached data can be directly called for display, which can avoid users performing repeated operations and processors performing repeated processing, thereby improving processing efficiency.

[0124] In the above scheme, payment processing for the target order can also be done based on the payment server, and determining the user's identity information based on facial information can also be done based on the payment server.

[0125] Based on and Figure 1 Using the same principle as the method shown, this application also provides a payment device, such as... Figure 12 As shown, the payment device includes a first display screen, a second display screen, and a processor, with the first and second display screens respectively connected to the processor; The first display screen is used to display the first client interface of the first mini program, and the second display screen is used to display the second client interface of the second mini program, wherein the first mini program and the second mini program are related mini programs; The processor is configured to generate first order information and second order information for a target order upon receiving product information of a product to be paid for, collected through a product information collection device; display the first order information through a first client interface and the second order information through a second client interface; and process the payment of the target order information upon receiving a payment trigger operation for the target order received through the target client interface. The target client interface is at least one of the first client interface or the second client interface.

[0126] Based on the payment device provided in this application, a first client interface of a first mini-program can be displayed on a first screen of the electronic device, and a second client interface of a second mini-program can be displayed on a second screen. The first client interface displays the first order information of the target order, and the second client interface displays the second order information of the target order. Since order information is displayed through two client interfaces, during payment, a payment trigger operation for the target order can be received through either the first or second client interface, and the payment for the target order can be processed in response to this operation. In this solution, on the one hand, displaying order information through two client interfaces allows both the payer and the payee to have a detailed understanding of the target order before payment processing, thereby improving the user's payment experience. On the other hand, since the two client interfaces correspond to two mini-programs, and two mini-programs run simultaneously on the electronic device, payment can be achieved based on the functions corresponding to these two mini-programs, thus improving the user experience of the electronic device.

[0127] In an optional embodiment of this application, the first display screen is further used to display setting information.

[0128] The settings information can be configured by the merchant's staff, such as advertising information or product information. This settings information can be displayed simultaneously with the first order information in different areas of the first client interface, or it can be displayed when the first order information is not shown on the first client interface. If the settings information is product information, the merchant's staff can use this information to improve product conversion rates.

[0129] In an optional embodiment of this application, the payment device further includes a commodity information collection device, which is used to collect commodity information of the commodity to be paid.

[0130] The product information collection device can send the collected product information to the processor of the payment device, so that the processor can generate the first order information and the second order information of the target order based on the product information of the product to be paid.

[0131] In an optional embodiment of this application, the payment device further includes an image acquisition device, and the processor is further configured to call the image acquisition device to acquire the facial information of the user of the target payment order when receiving a selection operation for the target payment method displayed on the first client interface.

[0132] The image acquisition device can be part of the payment device, such as the camera of the payment device.

[0133] Optionally, the payment device may also include an external card reader (e.g., a POS (point of sale) machine) that enables bank card payments.

[0134] Optionally, if the information received by the processor has a time sequence, it can be processed according to the order of receipt. If the information received has no order, the priority of each piece of information can be determined and the information can be processed based on the priority.

[0135] Optionally, the first display screen and the second display screen can each correspond to a processor. For example, the first display screen corresponds to a first processor (also known as a front screen processor), and the second display screen corresponds to a second processor (also known as a rear screen processor). The two processors can communicate with each other.

[0136] The first processor is used to display the first order information through the first client interface when it receives the first order information sent by the second processor. The second processor is used to generate first order information and second order information for the target order upon receiving product information of the goods to be paid for, collected through the product information collection device; display the second order information through the second client interface, and send the first order information to the first processor; The target processor is used to process the payment information of the target order when it receives a payment trigger operation for the target order received through the target client interface; The target client interface is at least one of a first client interface or a second client interface, and the target processor is at least one of a first processor or a second processor.

[0137] As an example, see Figure 13 The diagram shows the structure of another payment device, which includes a first display screen, a second display screen, a first processor, a second processor, and a communication server; the first display screen is connected to the first processor, the second display screen is connected to the second processor, and the first processor and the second processor are respectively connected to the communication server; The first display screen is used to display the first client interface of the first mini program, and the second display screen is used to display the second client interface of the second mini program, wherein the first mini program and the second mini program are related mini programs; The second processor is used to generate first order information and second order information for the target order upon receiving product information of the goods to be paid for, collected through the product information collection device; display the second order information through the second client interface; and send the first order information to the first processor through the communication server. The first processor is used to display the first order information through the first client interface when it receives the first order information sent by the second processor. The target processor is used to process the payment for the target order when it receives a payment trigger operation for the target order received through the target client interface; Wherein, the target client interface is at least one of a first client interface or a second client interface, and the target processor is at least one of a first processor or a second processor.

[0138] The communication server provides communication services for the first processor and the second processor, meaning that the first processor and the second processor can communicate through the communication server, and the first processor and the second processor can also communicate with the payment server through the communication server. The first processor is the processor corresponding to the first display screen, which is the display screen facing the customer; therefore, the first processor is the front-screen processor described above. The second display screen is the display screen facing the cashier; therefore, the second processor is the back-screen processor described above.

[0139] It is understood that the application provided herein Figure 1 The optional embodiments shown and Figure 1 Other alternative embodiments based on the scheme shown, and Figure 12 and Figure 13 The optional embodiments shown and Figure 12 The alternative embodiments based on the illustrated scheme are descriptions of the same technical solution from two different perspectives. One is a description from the perspective of the payment device (i.e., from the user's perspective), where the execution subject of the method is the payment device used by the user to make the payment. The other is a description from the perspective of the payment device. In the preceding description, some repetitive content may not have been repeated. However, the descriptions from the two different perspectives can be referenced and supplemented by each other, which is clear to those skilled in the art.

[0140] To better illustrate and understand the principles of the method provided in this application, the solution of this application is described below with reference to an optional specific embodiment. It should be noted that the specific implementation of each step in this specific embodiment should not be construed as a limitation on the solution of this application. Other implementation methods that can be conceived by those skilled in the art based on the principles of the solution provided in this application should also be considered within the protection scope of this application.

[0141] In this example, facial recognition payment is used as an example to illustrate the solution of this application. Figure 10 This diagram illustrates the interaction flow of a dual-screen payment device. Figure 10 In this process, customers interact with the second display screen through the first client interface of the first mini-program (the mini-program on the front screen of the device) displayed on the first screen, while cashiers interact with the first display screen through the second client interface of the second mini-program (the mini-program on the back screen of the device) displayed on the second screen. The two mini-programs can communicate with each other to complete the payment process.

[0142] Figure 11 This application illustrates a structural diagram of a face payment system based on a dual-screen payment device to which this application applies, such as... Figure 11 As shown, the system may include electronic devices (payment devices) and a payment server ( Figure 11 (not shown in the image), wherein the payment device and the payment server can communicate with each other, and the specific form of the communication network is not limited in the embodiments of this application.

[0143] The payment device includes a first display screen, a second display screen, and a processor (message manager). The first and second display screens are respectively connected to the processor. The first display screen displays the first client interface of a first mini-program (IoT mini-program 1, which can be called the front-screen mini-program), and the second display screen displays the second client interface of a second mini-program (IoT mini-program 2, which can also be called the back-screen mini-program). The first and second mini-programs are related mini-programs. The first mini-program runs through the front-screen mini-program container, and the second mini-program runs through the back-screen mini-program container. The mini-program container is the container carrier for the mini-program to run, and the front-screen mini-program container and the back-screen mini-program container are isolated in process.

[0144] The first display screen faces the customer, and the second display screen faces the cashier. The two screens communicate via a communication module, which is essentially a message manager. This message manager consists of three parts: a message channel for transmitting cross-process messages, i.e., information between the two screens; a front screen processor for receiving and processing information received from the first client interface and information sent from the back screen processor; and a back screen processor for receiving and processing information received from the second client interface and information sent from the front screen processor. Figure 11 Taking the interactive flow shown as an example, whether it is a payment behavior initiated by the front screen (front screen initiated behavior, such as payment) or a collection behavior initiated by the back screen (back screen initiated behavior, such as collection), the entire payment process can be completed through bidirectional communication transmission via this message manager.

[0145] The following section provides a further explanation of this solution in the context of facial recognition payment: This example illustrates a payment process initiated via the front screen. Before making a payment using an electronic device, the device must first be started, loading a first mini-program and a second mini-program. The specific startup process is as follows: In response to the first startup operation (power-on startup) on the electronic device, the first mini-program is loaded. Loading the first mini-program includes automatically loading its runtime environment, initializing its first container, and starting its runtime. After loading, the first initialization interface of the first mini-program can be displayed on the first screen. Simultaneously with the startup of the first mini-program, in response to the cashier's ability to click the application icon of the second mini-program displayed on the second screen, the runtime environment of the second mini-program is loaded, its second container is initialized, and its runtime is started. After loading, the second initialization interface of the second mini-program can be displayed on the second screen. The first client interface may include the first initialization interface, and the second client interface may include the second initialization interface.

[0146] Through the above startup process, the electronic device can function normally and complete the payment function. After the cashier collects the product information of the product to be paid through the product information collection device, the product information of the product to be paid is transmitted to the message manager. The message manager generates the first order information and the second order information of the target order based on the product information of the product to be paid. The first order information is displayed on the first client interface, and the second order information is displayed on the second client interface. The first client interface also displays a payment control. In response to the trigger operation of the payment control, at least one payment method option is displayed. The at least one payment option includes the WeChat face payment option. In response to the payment trigger operation (triggering behavior, payment) received through the first client interface for the WeChat face payment option (target payment method), the image collection device is called to collect the facial information of the user (customer) paying the target order. The facial information and the amount to be paid for the target order are sent to the payment server corresponding to the target payment method so that the payment server can determine the user's identity information based on the facial information, obtain the user's WeChat payment account information based on the identity information, and deduct the amount to be paid from the WeChat payment account to complete the face payment (payment completed). In response to obtaining the payment result of the target order, the payment result is displayed in at least one of the second client interface or the first client interface.

[0147] Upon receiving a payment trigger operation for the WeChat face payment option, the first display screen can send the message indicating that the customer has selected WeChat face payment as the target information to the second display screen to notify the cashier of the customer's chosen payment method. Specifically, the first display screen sends this target information to the front screen processor. Before sending the target information, the front screen processor assembles the target information into a message structure. This message structure includes the mini-program ID (AppId) of the first mini-program and the message content (the specific content of the target information; in this example, the target payment method selected by the customer is WeChat face payment). The front screen processor checks whether the target information meets the set conditions. If it does, the front screen processor transmits the target information to the back screen processor through the IPC message pipeline. The back screen processor encapsulates the target information into a JsEvent and finally generates a back screen mini-program Runtime (instance) through the back screen processor to process the target information through this instance. Figure 9 (The processing message shown), for example, displays the target information on the second client interface of the second display screen.

[0148] Based on the solution of this application, the order information of the target order is displayed on a dual-screen payment device, and the payment trigger operation for the target order is received through the first client interface or the second client interface, making the entire payment process more convenient and providing users with a better payment experience.

[0149] Based on this application Figure 1 Based on the same principle as the provided method, this application also provides a payment device, which is included in an electronic device. The electronic device includes a first display screen and a second display screen, such as... Figure 14 As shown, the payment device 30 includes an interface display module 310, an order display module 320, and an order processing module 330; wherein: The interface display module 310 is used to display the first client interface of the first mini-program through the first display screen and the second client interface of the second mini-program through the second display screen, wherein the first mini-program and the second mini-program are related mini-programs; The order display module 320 is used to display the first order information of the target order on the first client interface and the second order information of the target order on the second client interface. The first order information and the second order information are generated based on the product information of the goods to be paid for, which is collected by the product information collection device. The order processing module 330 is used to process the payment for the target order in response to a payment trigger operation received through the target client interface. The target client interface is at least one of the first client interface or the second client interface.

[0150] The solution provided in this application embodiment can display a first client interface of a first mini-program on a first display screen of an electronic device, and a second client interface of a second mini-program on a second display screen. The first client interface displays the first order information of the target order, and the second client interface displays the second order information of the target order. Since order information is displayed through two client interfaces, during payment, a payment trigger operation for the target order can be received through either the first or second client interface, and payment processing can be performed in response to this operation. In this solution, on the one hand, displaying order information through two client interfaces allows both the payer and the payee to have a detailed understanding of the target order before payment processing, thereby improving the user's payment experience. On the other hand, since the two client interfaces correspond to two mini-programs, and both mini-programs run simultaneously on the electronic device, payment can be achieved based on the functions corresponding to these two mini-programs, improving the user experience of the electronic device.

[0151] Optionally, when the order processing module processes a payment for a target order in response to a payment trigger operation received through the target client interface, it specifically performs the following: Display at least one payment method option on the first client interface; In response to a selection operation of a target payment method among at least one payment method options received through a first client interface, the target order is processed for payment using the target payment method. The payment trigger operation includes the selection operation, and the target client interface includes the first client interface.

[0152] Optionally, the above-mentioned payment method options include facial recognition payment and non-facial recognition payment. If the target payment method is non-facial recognition payment, the order processing module, when processing payment for the target order using the target payment method, specifically uses: Displays the payment interface corresponding to the target payment method for the target order; In response to a payment confirmation action for a target order, the payment for the target order is processed using the target payment method; the payment triggering action also includes a payment confirmation action.

[0153] Optionally, if the target payment method is facial recognition payment, the order processing module will process the payment for the target order using the target payment method, specifically for: The system uses image acquisition devices to collect facial information of users who are paying for target orders. Send the amount to be paid for the target order and the facial information to the payment server corresponding to the facial payment method, so that the payment server can process the payment for the target order based on the facial information.

[0154] Optionally, the second client interface displays a payment control. When the order processing module displays at least one payment method option on the first client interface, it is specifically used for: In response to a selection trigger action for the payment control, at least one payment method option is displayed on the first client interface; The target client interface also includes a second client interface, and the payment triggering operation also includes selecting a triggering operation.

[0155] Optionally, the device may also include: The startup module is used to respond to a first startup operation on the electronic device, load a first mini-program and a second mini-program respectively, and display the first initialization interface of the first mini-program on a first display screen and the second initialization interface of the second mini-program on a second display screen.

[0156] Optionally, when the startup module loads the second applet in response to a first startup operation on the electronic device, it is specifically used for... In response to a first startup operation on an electronic device, a second display screen is activated, and the second display screen displays at least one application identifier, including the application identifier corresponding to the second mini-program. In response to a trigger operation targeting the application identifier corresponding to the second mini-program, load the second mini-program.

[0157] Optionally, the first client interface displays a setting indicator. When the first client interface cannot display information, the device further includes: The fault handling module is used to reload the first mini-program in response to a trigger operation based on a set identifier.

[0158] The payment device in this application embodiment can execute the payment method provided in this application embodiment. The implementation principle is similar. The actions performed by each module and unit in the payment device in each embodiment of this application correspond to the steps in the payment method in each embodiment of this application. For detailed functional descriptions of each module of the payment device, please refer to the descriptions in the corresponding payment methods shown above. They will not be repeated here.

[0159] The payment device may be a computer program (including program code) running on a computer device, for example, the display device of the user interface is an application software; the device may be used to perform the corresponding steps in the method provided in the embodiments of this application.

[0160] In some embodiments, the payment device provided by the present invention can be implemented in a combination of hardware and software. As an example, the payment device provided by the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the payment method provided by the present invention. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0161] In other embodiments, the payment device provided in the embodiments of the present invention can be implemented in software. The payment device stored in the memory can be software in the form of programs and plug-ins, and includes a series of modules, including the interface display module 310, the order display module 320 and the order processing module 330 in the payment device 30; wherein, each module in the payment device 30 is used to implement the payment method provided in the embodiments of the present invention.

[0162] This application provides a payment device that, compared to existing technologies, displays a first client interface of a first mini-program on a first display screen of an electronic device, and a second client interface of a second mini-program on a second display screen. The first client interface displays first order information for the target order, and the second client interface displays second order information for the target order. Because order information is displayed through two client interfaces, during payment, a payment trigger operation for the target order can be received through either the first or second client interface, and payment processing can be performed in response to this operation. In this solution, on the one hand, displaying order information through two client interfaces allows both the payer and payee to have a detailed understanding of the target order before payment processing, thereby improving the user's payment experience. On the other hand, since the two client interfaces correspond to two mini-programs, and both mini-programs run simultaneously on the electronic device, payment can be achieved based on the functions corresponding to these two mini-programs, improving the user experience of the electronic device.

[0163] The payment device of this application has been described above from the perspective of a virtual module or virtual unit. The electronic device of this application will now be described from the perspective of a physical device.

[0164] Based on the same principle as the method provided in the embodiments of this application, an electronic device is provided in the embodiments of this application. The electronic device includes a memory and a processor. The memory stores a computer program, which, when executed by the processor, can implement the method provided in any optional manner of this application.

[0165] As an optional solution, Figure 15 The diagram shows a structural schematic of an electronic device to which an embodiment of this application applies, such as... Figure 15 As shown, Figure 15 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0166] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0167] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 15 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0168] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0169] The memory 4003 stores application code (computer program) that executes the solution of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the application code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.

[0170] Among them, electronic devices include, but are not limited to, user terminal devices and servers, wherein the servers can be physical servers, cloud servers, single servers or server clusters, etc.

[0171] This application also provides a computer-readable storage medium storing a computer program, which, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments.

[0172] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in various optional implementations of the above-described method embodiments.

[0173] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by 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 accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0174] The above description is only a partial embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A payment method, characterized in that, The method is performed by an electronic device, the electronic device including a first display screen and a second display screen, the method comprising: The first display screen shows the first client interface of the first mini-program, and the second display screen shows the second client interface of the second mini-program, wherein the first mini-program and the second mini-program are associated mini-programs; In response to a payment trigger operation for a target order received through a target client interface, payment processing is performed on the target order; wherein the target client interface is at least one of the first client interface or the second client interface.

2. The method according to claim 1, characterized in that, The first mini-program and the second mini-program correspond to the same mini-program container and run through the same mini-program container; or the first mini-program and the second mini-program each correspond to a mini-program container, the first mini-program runs through the first container, and the second mini-program runs through the second container.

3. The method according to claim 1, characterized in that, The step of processing payment for the target order in response to a payment trigger operation received through the target client interface includes: At least one payment method option is displayed on the first client interface; In response to a selection operation of a target payment method among the at least one payment method options received through the first client interface, the target order is processed for payment through the target payment method, the payment triggering operation includes the selection operation, and the target client interface includes the first client interface.

4. The method according to claim 3, characterized in that, The at least one payment method option includes facial recognition payment and non-facial recognition payment. If the target payment method is the non-facial recognition payment method, the step of processing the payment for the target order through the target payment method includes: Display the payment interface corresponding to the target payment method for the target order; In response to the payment confirmation operation for the target order, the target order is processed for payment using the target payment method; the payment triggering operation also includes the payment confirmation operation.

5. The method according to claim 3, characterized in that, If the target payment method is the facial recognition payment method, the step of processing the payment for the target order using the target payment method includes: The system uses an image acquisition device to collect the facial information of the user who paid for the target order. The payment server corresponding to the facial recognition payment method sends the amount to be paid for the target order and the facial information to the payment server, so that the payment server can process the payment for the target order based on the facial information.

6. The method according to claim 3, characterized in that, The second client interface displays payment collection controls; Displaying at least one payment method option on the first client interface includes: In response to a selection trigger operation of the payment control on the second client interface, at least one payment method option is displayed on the first client interface; The target client interface also includes the second client interface, and the payment triggering operation also includes the selection triggering operation.

7. The method according to claim 5, characterized in that, The step of calling the image acquisition device to collect the facial information of the user paying for the target order includes: The system uses an image acquisition device to capture at least two facial images of the user who paid for the target order. For each face image in at least two face images, determine the index value of each preset evaluation index corresponding to the face image; based on the weight of each preset evaluation index and the index value of the face image corresponding to each of the evaluation indexes, determine the image score of the face image. The face image with the highest image score among the at least two face images is identified as the face information; Each of the evaluation indicators includes at least two of the following: The proportion of face size in a face image; Facial shooting angle; Image quality.

8. The method according to claim 1, characterized in that, The payment processing for the target order includes: Based on the payment information of the target order and the mini-program identifier of the mini-program corresponding to the target client interface, the message structure is assembled through the processor corresponding to the target client interface to obtain the target message; The target message is sent to the processor of the associated mini-program through the processor corresponding to the target client interface, so that the target message can be displayed through the client interface of the associated mini-program.

9. The method according to claim 1, characterized in that, The method further includes: The order information of the target order is displayed on at least one of the first client interface or the second client interface.

10. The method according to claim 9, characterized in that, The order information for the target order includes first order information for customers and second order information for merchant cashiers; Displaying the order information of the target order in at least one of the first client interface or the second client interface includes: The first order information of the target order is displayed on the first client interface; The second order information of the target order is displayed on the second client interface.

11. The method according to claim 10, characterized in that, The second client interface displays a payment collection control; Displaying the order information of the target order in at least one of the first client interface or the second client interface includes: The second order information of the target order is displayed on the second client interface; In response to a trigger operation on the payment control in the second client interface, the first order information of the target order is displayed on the first client interface.

12. The method according to claim 1, characterized in that, The order information of the target order is generated from the product information of the goods to be paid for, collected by the product information collection device; the product information collection device is an external device of the electronic device, or the electronic device includes the product information collection device.

13. A payment device, characterized in that, It includes a first display screen, a second display screen, a first processor, and a second processor, wherein the first display screen and the second display screen are respectively connected to the processor; The first display screen is used to display the first client interface of the first mini-program, and the second display screen is used to display the second client interface of the second mini-program, wherein the first mini-program and the second mini-program are associated mini-programs; The processor is configured to perform payment processing on the target order when it receives a payment trigger operation for the target order received through the target client interface; wherein the target client interface is at least one of the first client interface or the second client interface.

14. The payment device according to claim 13, characterized in that, The payment device also includes an image acquisition device, and the processor is further configured to, upon receiving a selection operation for the target payment method displayed on the first client interface, invoke the image acquisition device to acquire the facial information of the user paying the target order.

15. The payment device according to claim 13, characterized in that, The processor includes a first processor and a second processor, and the payment device also includes a communication server; The first processor is connected to the first display screen, the second processor is connected to the second display screen, and the first processor and the second processor communicate through the communication server; The first processor is configured to display the first order information through the first client interface when it receives the first order information sent by the second processor; The second processor is used to generate first order information and second order information for the target order upon receiving product information of the goods to be paid for, collected through the product information collection device. The second order information is displayed through the second client interface, and the first order information is sent to the first processor through the communication server. A target processor is configured to process the payment for the target order upon receiving a payment trigger operation for the target order received through the target client interface. Wherein, the target client interface is at least one of the first client interface or the second client interface, and the target processor is at least one of the first processor or the second processor.

16. The payment device according to claim 13, characterized in that, The processor includes a first processor and a second processor, wherein the first processor is connected to the first display screen and the second processor is connected to the second display screen; A target processor is configured to assemble a message structure to obtain a target message based on the payment information of the target order and the mini-program identifier of the mini-program corresponding to the target client interface; and send the target message to the processor corresponding to the associated mini-program of the mini-program so as to display the target message through the client interface corresponding to the associated mini-program. The target processor is at least one of the first processor or the second processor.

17. A payment device, characterized in that, The device is included in an electronic device, the electronic device including a first display screen and a second display screen, the device comprising: The interface display module is used to display the first client interface of the first mini-program through the first display screen and the second client interface of the second mini-program through the second display screen. The first mini-program and the second mini-program are associated mini-programs. The first mini-program and the second mini-program each correspond to a mini-program container. The first mini-program runs through the first container and the second mini-program runs through the second container. The order processing module is used to process the payment for the target order in response to a payment trigger operation received through the target client interface; wherein the target client interface is at least one of the first client interface or the second client interface.

18. An electronic device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and the processor performs the method of any one of claims 1 to 12 when running the computer program.

19. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1-12.

Images