Aggregate payment method and device, electronic equipment and storage medium

Abstract

The invention provides an aggregation payment method and device, electronic equipment and a storage medium, and the method comprises the steps: when a mobile terminal is close to NFC cashier equipment, the NFC cashier equipment sends a Clips trigger message to the mobile terminal, so that the mobile terminal loads an aggregation cashier interface, the aggregation cashier interface comprises a plurality of candidate payment applications, and the candidate payment applications are sent to the NFC cashier equipment; and the user performs selection operation on the aggregation cashier interface to determine a target payment application, and the mobile terminal calls the target payment application according to the call identifier corresponding to the target payment application so as to perform payment by using the target payment application. Through the payment process, the user does not need to search the payment application in the mobile terminal, but can directly select the target payment application in the aggregation cashier interface for payment, so that the payment process of the user is simplified, and the payment efficiency and convenience are greatly improved. And a plurality of selectable candidate payment applications are provided in the aggregated cashier interface, so that the payment flexibility of the user is greatly improved, and the payment experience of the user is further improved.

Description

Technical Field

[0001] The present invention relates to the field of electronic payment technology, and in particular to an aggregate payment method, device, electronic device and storage medium. Background Art

[0002] With the rapid development of electronic payment technology, electronic payment has been widely used in various industries. Currently, users need to manually find payment apps such as WeChat and Alipay, scan the QR code, and enter the payment amount to complete the payment.

[0003] This is a cumbersome process for users who don't have their payment app on their phone's homepage, especially when time is tight or the scenario is complex, which can easily lead to payment delays. For the elderly or users unfamiliar with smartphone operations, they may not be able to quickly find WeChat or Alipay, and may even need to seek help from others, further increasing the difficulty and time cost of the operation. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide an aggregated payment method, device, electronic device, and storage medium to improve the convenience and efficiency of electronic payment.

[0005] According to one aspect of the present invention, there is provided an aggregate payment method applied to a mobile terminal, the method comprising:

[0006] When the mobile terminal is close to an NFC cash register device, obtaining Clips trigger information sent by the NFC cash register device;

[0007] In response to the Clips trigger information, displaying an aggregated cashier interface on the mobile terminal, wherein the aggregated cashier interface displays a plurality of candidate payment applications and payment information, wherein the payment information includes a payment amount;

[0008] Determining a target payment application based on the operation received by the aggregated cashier interface, and calling the target payment application according to a call identifier corresponding to the target payment application;

[0009] The target payment application is used to execute a payment action according to the payment information.

[0010] In a possible embodiment, the method further includes: receiving aggregated cashier interface setting information, wherein the aggregated cashier interface setting information includes identifiers of multiple candidate payment applications to be displayed;

[0011] Based on the aggregated cashier interface setting information, configuring a call identifier corresponding to each of the candidate payment applications;

[0012] Storing each of the candidate payment application identifiers and a call identifier corresponding to each of the candidate payment applications;

[0013] The displaying of the aggregated cashier interface in the mobile terminal includes:

[0014] The aggregated cashier interface is loaded based on the stored candidate payment application identifiers and the call identifiers corresponding to the candidate payment applications.

[0015] In a possible embodiment, the aggregated cashier interface further includes an alternative application entry, and the receiving of aggregated cashier interface setting information includes:

[0016] According to the record of the number of times the user's payment application is used, a preset number of payment applications with the highest number of uses are determined as candidate payment applications;

[0017] Determining, based on a preset payment application list and a record of the number of times the payment application is used, that the payment application and the alternative payment application are not installed in the mobile terminal;

[0018] Generating the aggregated cashier interface setting information based on the candidate payment application, the not-installed payment application, and the alternative payment application;

[0019] The method further comprises:

[0020] Configuring a call identifier corresponding to each of the alternative payment applications and a download link for each of the not-installed payment applications;

[0021] The candidate payment applications and the non-installed payment applications are displayed on a display page corresponding to the candidate application entrance.

[0022] In a possible embodiment, the calling identifier includes a Scheme URL and / or a Universal Link;

[0023] The calling the target payment application according to the calling identifier corresponding to the target payment application includes:

[0024] Call the target payment application according to the Scheme URL bound to the target payment application, and send the payment information to the target payment application; or,

[0025] The target payment application is called according to the Universal Link bound to the target payment application, and the payment information is sent to the target payment application.

[0026] According to another aspect of the present invention, there is provided an aggregate payment device, which is applied to a mobile terminal and includes:

[0027] An acquisition module, configured to acquire Clips trigger information sent by the NFC cash register device when the mobile terminal is close to the NFC cash register device;

[0028] a response module, configured to display an aggregated cashier interface on the mobile terminal in response to the Clips trigger information, wherein the aggregated cashier interface displays a plurality of candidate payment applications and payment information, wherein the payment information includes a payment amount;

[0029] A calling module, configured to determine a target payment application based on the operation received by the aggregated cashier interface, and call the target payment application according to a calling identifier corresponding to the target payment application;

[0030] The payment module is used to use the target payment application to perform a payment action according to the payment information.

[0031] In a possible embodiment, the apparatus further includes: a setting module configured to receive aggregated cashier interface setting information, wherein the aggregated cashier interface setting information includes identifiers of multiple candidate payment applications to be displayed;

[0032] Based on the aggregated cashier interface setting information, configuring a call identifier corresponding to each of the candidate payment applications;

[0033] Storing each of the candidate payment application identifiers and a call identifier corresponding to each of the candidate payment applications;

[0034] The displaying of the aggregated cashier interface in the mobile terminal includes:

[0035] The aggregated cashier interface is loaded based on the stored candidate payment application identifiers and the call identifiers corresponding to the candidate payment applications.

[0036] In a possible embodiment, the aggregated cashier interface further includes an alternative application entry, and the receiving of aggregated cashier interface setting information includes:

[0037] According to the record of the number of times the user's payment application is used, a preset number of payment applications with the highest number of uses are determined as candidate payment applications;

[0038] Determining, based on a preset payment application list and a record of the number of times the payment application is used, that the payment application and the alternative payment application are not installed in the mobile terminal;

[0039] Generating the aggregated cashier interface setting information based on the candidate payment application, the not-installed payment application, and the alternative payment application;

[0040] The setting module is used to configure the call identifier corresponding to each of the alternative payment applications and the download link of each of the not-installed payment applications;

[0041] The response module is configured to display each of the alternative payment applications and each of the non-installed payment applications on a display page corresponding to the alternative application entry.

[0042] In a possible embodiment, the calling identifier includes a Scheme URL and / or a Universal Link;

[0043] The calling the target payment application according to the calling identifier corresponding to the target payment application includes:

[0044] Call the target payment application according to the Scheme URL bound to the target payment application, and send the payment information to the target payment application; or,

[0045] The target payment application is called according to the Universal Link bound to the target payment application, and the payment information is sent to the target payment application.

[0046] According to another aspect of the present invention, there is provided an electronic device, comprising:

[0047] processor; and

[0048] Memory for storing programs,

[0049] The program includes instructions, which, when executed by the processor, enable the processor to execute any of the above-mentioned aggregate payment methods.

[0050] According to another aspect of the present invention, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable a computer to execute any of the above-mentioned aggregate payment methods.

[0051] One or more technical solutions provided in an embodiment of the present invention are as follows: when a mobile terminal approaches an NFC cash register device, the NFC cash register device sends a Clips trigger message to the mobile terminal. After receiving the Clips trigger message, the mobile terminal loads an aggregated cash register interface, which contains multiple candidate payment applications. The user can determine the target payment application by selecting it in the aggregated cash register interface. The mobile terminal calls the target payment application according to the call identifier corresponding to the target payment application, and uses the target payment application to make payment according to the payment information. Through this payment process, the user does not need to search for the payment application in the mobile terminal, but can directly select the target payment application from the candidate payment applications displayed in the aggregated cash register interface to make payment, thereby simplifying the user's payment process and greatly improving payment efficiency and convenience. In addition, by providing multiple selectable candidate payment applications in the aggregated cash register interface, the user's payment flexibility is greatly improved, further improving the user's payment experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Further details, features and advantages of the present invention are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:

[0053] Figure 1 A schematic diagram of a flow chart of the aggregate payment method provided by an embodiment of the present invention;

[0054] Figure 2 A schematic diagram of another process of the aggregate payment method provided in an embodiment of the present invention;

[0055] Figure 3 A schematic diagram of the structure of an aggregate payment device provided in an embodiment of the present invention;

[0056] Figure 4 A block diagram of an exemplary electronic device capable of implementing the embodiments of the present invention is shown. DETAILED DESCRIPTION

[0057] Embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present invention. It should be understood that the drawings and embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of protection of the present invention.

[0058] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0059] The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc. mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0060] It should be noted that the modifications of "one" and "multiple" mentioned in the present invention are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0061] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0062] To improve the convenience and efficiency of electronic payments, the present invention provides a method, apparatus, electronic device, and storage medium for aggregated payment. The aggregated payment method provided by the present invention can be applied to any electronic device with electronic payment functionality. As a possible implementation, the electronic device can be a mobile terminal, such as a mobile phone, electronic watch, or head-mounted device. The following describes the solution of the present invention with reference to the accompanying drawings:

[0063] like Figure 1 As shown, Figure 1 A schematic flow chart of the aggregate payment method provided in an embodiment of the present invention may include the following steps:

[0064] S101. When the mobile terminal is close to an NFC cash register device, obtain Clips trigger information sent by the NFC cash register device;

[0065] S102. In response to the Clips trigger information, displaying an aggregated cashier interface on the mobile terminal, wherein the aggregated cashier interface displays a plurality of candidate payment applications and payment information, wherein the payment information includes a payment amount;

[0066] S103: Determine a target payment application based on the operation received by the aggregated cashier interface, and call the target payment application according to a call identifier corresponding to the target payment application;

[0067] S104: Utilize the target payment application to execute a payment action according to the payment information.

[0068] According to an embodiment of the present invention, when a mobile terminal is close to an NFC cash register device, the NFC cash register device sends a Clips trigger message to the mobile terminal. After receiving the Clips trigger message, the mobile terminal loads an aggregated cash register interface. The aggregated cash register interface includes multiple candidate payment applications. The user can determine the target payment application by selecting it in the aggregated cash register interface. The mobile terminal calls the target payment application according to the call identifier corresponding to the target payment application, and uses the target payment application to make payment according to the payment information. Through this payment process, the user does not need to search for the payment application in the mobile terminal, but can directly select the target payment application from the candidate payment applications displayed in the aggregated cash register interface to make payment, which simplifies the user payment process and greatly improves payment efficiency and convenience. In addition, by providing multiple selectable candidate payment applications in the aggregated cash register interface, the user's payment flexibility is greatly improved, further improving the user's payment experience.

[0069] The following is an exemplary description of S101-S104:

[0070] At present, many mobile terminals are equipped with NFC (Near Field Communication) function. NFC integrates contactless card reader, contactless card and point-to-point functions into a single chip, combines the functions of the reader and tag parts of RFID (Radio Frequency Identification), and adds point-to-point communication capabilities. Generally, the NFC communication transmission distance does not exceed 4 cm, and may reach 10 cm in some applications. The mobile terminal can realize various functions such as mobile payment, identity recognition, and data transmission through the NFC function. In S101, the user can bring the mobile terminal with NFC function close to the NFC cash register device to carry out the payment process. The close approach here can be that the user touches the mobile terminal to the NFC sensing area of the NFC cash register device, or reduces the distance between the mobile terminal and the NFC sensing area of the NFC cash register device to within the NFC communication distance.

[0071] An NFC cash register device is a cash register device with NFC function. As a possible implementation method, in order to enable users to find the NFC sensing area in the NFC cash register device conveniently and quickly, an NFC payment aggregation card structure can be set in the NFC cash register device. The NFC payment aggregation card coincides with the NFC sensing area in the NFC cash register device, and prompt information can be marked on the NFC payment aggregation card to guide users to place the mobile terminal close to the NFC payment aggregation card for payment.

[0072] An NFC cash register device may pre-store an execution script that may include execution logic for sending a Clips (C Language Integrated Production System) identifier and payment information via NFC communication. The Clips identifier may be the name of the Clips program, and the payment information may include the payment amount, merchant information, and the like. CLIPS is a C-language expert system development tool used to build rule-driven applications. For example, the execution script may include a Clips identifier, payment information parameters, and merchant information parameters. After the NFC cash register device obtains the payment amount that the user needs to pay, it may use the payment amount to assign a value to the payment information parameter in the execution script, and use the merchant name to assign a value to the merchant information parameter, thereby sending the Clips identifier, payment amount, and merchant information to the mobile terminal via NFC.

[0073] The above-mentioned Clips identifier is actually a trigger information. Specifically, the mobile terminal can start the Clips dynamic loading process after receiving the Clips identifier. The Clips dynamic loading process is implemented by loading the aggregated cashier interface through the Clips program in the mobile terminal. The aggregated cashier interface can display multiple candidate payment applications. The candidate payment applications can include various payment applications installed in the mobile terminal. Each candidate payment application corresponds to a preset button area. The user clicks the button area to select the candidate payment application corresponding to the button area. The user can select the target payment application by clicking, sliding, and other operations in each candidate payment application displayed in the aggregated cashier page. After the mobile terminal receives the user's operation in the aggregated cashier interface, it can determine the target payment application and then call the target payment application through the call identifier corresponding to the target payment application. Specifically, while calling the target payment application through the call identifier corresponding to the target payment application, the payment information can be sent to the target payment application, thereby jumping to the target payment application and completing the payment according to the payment information.

[0074] For example, the aggregated cashier page may display payment application 1, payment application 2, and payment application 3. If the user selects payment application 1, they can call payment application 1 using the call identifier corresponding to payment application 1 and pass the payment amount to payment application 1. At this point, the mobile terminal automatically jumps to payment application 1 and displays the payment page of payment application 1 according to the payment amount. The user can confirm the payment on this payment page using a fingerprint, password, or other method.

[0075] After the user completes the payment, the target payment application can return to the payment status, that is, the display interface in the mobile terminal displays the result of payment success or payment failure. As a possible implementation method, the target payment application can return the payment result to the aggregated cashier interface, so that the payment result is displayed in the aggregated cashier interface, and the Clips interface is closed after the payment result is displayed for a preset time. The preset time can be set according to the actual application scenario, such as 1s. In the actual payment scenario, it may happen that the user wants to switch to other payment applications for payment after selecting the target payment application. In order to deal with this situation, in a possible embodiment, when the payment result is a payment failure, the aggregated cashier interface can be returned to allow the user to re-select the target payment application based on the candidate payment applications displayed on the aggregated cashier interface. The above-mentioned payment failure may include the user giving up the payment, the payment failure due to insufficient balance, etc.

[0076] The Clips program supports dynamically editable pages, and accordingly, the call identifiers corresponding to the candidate payment applications can be pre-set in the Clips program. The above call identifiers can include Scheme URLs (protocol URLs or application links) and Universal Links, where Scheme URLs are a special link format for communication between applications. This type of link allows applications to be opened or specific operations to be performed through a specified protocol (Scheme). Scheme URLs usually start with a specific protocol, such as http: / / , https: / / , mailto:, tel:, etc., or they can be custom application protocols, such as yourapp: / / . Universal Link can be compared to a deep link, which can easily launch the client application directly by opening an Https link. When a user clicks on a link, if the corresponding App is installed on the device, the system will try to use the App to open the link.

[0077] In a possible embodiment, the above method may further include the following steps:

[0078] S11. Receive aggregated cashier interface setting information, where the aggregated cashier interface setting information includes identifiers of multiple candidate payment applications that need to be displayed.

[0079] The aggregated cashier interface setting information can be automatically generated by the mobile terminal during the Clips program configuration phase. There may be multiple payment applications installed in the mobile terminal, and the aggregated cashier interface setting information can include all payment applications installed in the mobile terminal. In actual applications, even if multiple payment applications are installed in the mobile terminal, only some of the payment applications are used due to the customer's payment habits. Based on this, in order to better adapt to the user's payment habits, the various payment applications in the mobile terminal can be divided into candidate payment applications and alternative payment applications, among which the candidate payment applications are applications that need to be displayed in the aggregated cashier interface, and the alternative payment applications can be displayed in the next-level interface. The next-level interface can be realized by adding a page link to the cashier aggregation page. For example, the "alternative application" entry can be displayed in the cashier aggregation interface, and the next-level interface can be entered by clicking the "alternative application" entry link.

[0080] In one possible implementation, a preset number of payment applications with the highest usage times can be determined as candidate payment applications based on the user's payment application usage records; and alternative payment applications in the mobile terminal can be determined based on the preset payment application list and the payment application usage records.

[0081] The user payment application usage record can record the correspondence between the identifiers of each payment application installed in the mobile terminal and the number of times it is used. Based on the user payment application usage record, the payment applications can be sorted. Specifically, the payment applications can be sorted in descending order of usage, and a preset number of payment applications with the highest number of usages are selected as candidate payment applications. The editable page of Clips allows developers to dynamically configure the number of buttons and jump targets in the interface as needed. The preset number can be configured according to the actual application scenario, such as the size of the aggregated cashier interface and the user's usual font size. The above preset number can also be determined based on the user payment application usage record. For example, if there are multiple payment applications with the highest and same number of usages, these payment applications can all be used as candidate payment applications. For example, if the user uses 4 payment applications 100 times each, these four payment applications can all be used as candidate payment applications. The alternative payment application is the payment application other than the candidate payment application among the payment applications installed in the mobile terminal.

[0082] In one possible embodiment, a list of compliant payment applications may be preset, including payment applications that comply with national laws and regulations. Based on this list of compliant payment applications and the user's payment application usage history, it is possible to determine whether a payment application is not installed. This compliant payment application is a payment application that is present in the compliant payment application list but not in the user's payment application usage history. This compliant payment application may be displayed on the next level of the aggregated cashier interface along with the alternative payment applications.

[0083] S12. Based on the aggregated cashier interface setting information, configure a call identifier corresponding to each candidate payment application.

[0084] The call identifier may include a Scheme URL and a Universal Link. In this step, the call identifier may be configured for each candidate payment application and alternative payment application according to the jump method supported by each payment application. Exemplarily, each button area in the aggregated cashier interface may be bound to a specific Scheme URL. Accordingly, the button area of each candidate payment application in the aggregated cashier interface may be preset, and the button area may be bound to the corresponding candidate payment application. For example, app1: / / pay is used to jump to candidate payment application 1, and app2: / / is used to jump to candidate payment application 2. When the user clicks on the corresponding button area, the mobile terminal calls the bound Scheme, directly opens the corresponding payment app, and carries the necessary payment parameters. The button area of the candidate payment application in the aggregated cashier interface may be determined according to the preset display style and the order of the candidate payment applications. Exemplarily, if three candidate payment applications are displayed vertically in the aggregated cashier interface, the button area may be selected from top to bottom in the order of the number of times the candidate payment application is used from high to low.

[0085] For payment apps that support Universal Link, the button area can be bound to a specific Universal Link, such as https: / / pay.example.com / pay?orderId=123. When the user clicks the button area, the mobile device automatically invokes the corresponding payment app through Universal Link and accurately navigates to the payment page to complete the payment.

[0086] In one possible embodiment, a download link for each payment application that has not been installed can also be configured. Specifically, a button area corresponding to the payment application that has not been installed can be bound to the download link of the payment application that has not been installed in the Clips program. When the user clicks the button area, the payment application that has not been installed can be automatically downloaded.

[0087] S13: Store each candidate payment application identifier and a call identifier corresponding to each candidate payment application.

[0088] As described above, the configuration phase binds the key area corresponding to the payment application to the call identifier of the payment application. Therefore, when storing, the candidate payment application identifier, key area identifier, and call identifier can be stored in correspondence. The key area identifier can be the coordinates of the key area.

[0089] When the aggregated cashier interface is displayed on the mobile terminal, the aggregated cashier interface can be loaded based on the stored identifiers of each candidate payment application and the call identifiers corresponding to each candidate payment application. Specifically, the aggregated cashier interface can be loaded and displayed according to a preset display style and the key area corresponding to the candidate payment application identifier. When the mobile terminal receives an operation such as a click or slide on a key area by the user, it can jump to the target payment application corresponding to the key area through the call identifier corresponding to the key area, and pass the payment information to the target payment application, so that the target payment application automatically enters the payment page and fills in the payment information, helping the user to quickly complete the payment operation.

[0090] Through this technical solution, Clips can leverage the built-in security mechanisms of mobile devices to ensure that Scheme and Universal Link calls are legitimate and trusted, ensuring user payment security. This approach also offers high compatibility and supports most mainstream payment apps on the market.

[0091] In a possible embodiment, the above-mentioned mobile terminal may include an NFC trigger module, a Clips dynamic loading module, a payment method selection module, and a jump payment module, wherein the NFC trigger module is used to automatically trigger a Clips loading request when the user brings the mobile terminal close to a cash register device that supports NFC. The Clips dynamic loading module can automatically load the Clips program of the aggregated cash register through NFC or a QR code. Specifically, the Clips program can be loaded by receiving trigger information sent by the NFC cash register device or trigger information obtained by scanning a QR code by the mobile terminal. The payment method selection module is used to display various payment application options on the Clips interface, and the user can directly select a payment method. The jump payment module is used to directly jump to the corresponding payment app to complete the payment after the user selects a payment method.

[0092] like Figure 2 As shown, Figure 2Another flow diagram of the aggregated cashier method provided by the present invention may include the following process: an NFC cashier device includes an NFC payment aggregation card, which includes an NFC sensing area. At the same time, the NFC payment aggregation card may display a prompt message stating "Please place your phone here." After a user touches their phone to the NFC payment aggregation card, the phone receives a Clips trigger message sent by the NFC cashier device via NFC communication. In response to the Clips trigger message, the phone calls the Clips program, which can load the aggregated cashier interface according to pre-stored aggregated cashier interface settings. The aggregated cashier interface displays multiple selectable candidate payment applications and payment information. For example, the aggregated cashier interface may display payment information of 5.00 yuan, as well as candidate payment application 1, candidate payment application 2, and candidate payment application 3. The user can click on the corresponding candidate payment application, and the phone will call the target payment application using the call identifier corresponding to the target payment application selected by the user, and pass the payment information to the target payment application to complete the payment in the target payment application.

[0093] In the embodiments of the present invention, NFC and Clips dynamic loading technology are used to directly invoke the aggregated cash register Clips interface through NFC touch. Users can quickly select a variety of payment methods to complete payment without manually searching for the payment app. By applying the embodiments of the present invention, by simplifying the payment process, users can quickly complete payment operations directly through NFC touch, significantly improving payment convenience. Furthermore, Clips dynamic loading does not require the pre-installation of the aggregated payment app, occupies less resources, and is applicable to more scenarios. Aggregated Clips supports multiple payment methods, has strong compatibility, and adapts to different user needs, significantly improving payment efficiency and user experience.

[0094] Based on the same inventive concept, according to another aspect of the present invention, there is also provided an aggregate payment device, which is applied to a mobile terminal, such as Figure 3 As shown, the apparatus 300 may include:

[0095] The acquisition module 301 is configured to acquire Clips trigger information sent by the NFC cash register device when the mobile terminal is close to the NFC cash register device;

[0096] A response module 302 is configured to display an aggregated cashier interface on the mobile terminal in response to the Clips trigger information, wherein the aggregated cashier interface displays multiple candidate payment applications and payment information, wherein the payment information includes a payment amount;

[0097] A calling module 303 is configured to determine a target payment application based on the operation received by the aggregated cashier interface, and call the target payment application according to a call identifier corresponding to the target payment application;

[0098] The payment module 304 is configured to utilize the target payment application to execute a payment action according to the payment information.

[0099] In a possible embodiment, the apparatus further includes: a setting module configured to receive aggregated cashier interface setting information, wherein the aggregated cashier interface setting information includes identifiers of multiple candidate payment applications to be displayed;

[0100] Based on the aggregated cashier interface setting information, configuring a call identifier corresponding to each of the candidate payment applications;

[0101] Storing each of the candidate payment application identifiers and a call identifier corresponding to each of the candidate payment applications;

[0102] The displaying of the aggregated cashier interface in the mobile terminal includes:

[0103] The aggregated cashier interface is loaded based on the stored candidate payment application identifiers and the call identifiers corresponding to the candidate payment applications.

[0104] In a possible embodiment, the aggregated cashier interface further includes an alternative application entry, and the receiving of aggregated cashier interface setting information includes:

[0105] According to the record of the number of times the user's payment application is used, a preset number of payment applications with the highest number of uses are determined as candidate payment applications;

[0106] Determining, based on a preset payment application list and a record of the number of times the payment application is used, that the payment application and the alternative payment application are not installed in the mobile terminal;

[0107] Generating the aggregated cashier interface setting information based on the candidate payment application, the not-installed payment application, and the alternative payment application;

[0108] The setting module is used to configure the call identifier corresponding to each of the alternative payment applications and the download link of each of the not-installed payment applications;

[0109] The response module is configured to display each of the alternative payment applications and each of the non-installed payment applications on a display page corresponding to the alternative application entry.

[0110] In a possible embodiment, the calling identifier includes a Scheme URL and / or a Universal Link;

[0111] The calling the target payment application according to the calling identifier corresponding to the target payment application includes:

[0112] Call the target payment application according to the Scheme URL bound to the target payment application, and send the payment information to the target payment application; or,

[0113] The target payment application is called according to the Universal Link bound to the target payment application, and the payment information is sent to the target payment application.

[0114] Among them, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in the present invention are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0115] An exemplary embodiment of the present invention further provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by the at least one processor, wherein the computer program, when executed by the at least one processor, causes the electronic device to perform a method according to an embodiment of the present invention.

[0116] Exemplary embodiments of the present invention further provide a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to perform a method according to an embodiment of the present invention.

[0117] An exemplary embodiment of the present invention further provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor of a computer, the computer is configured to cause the computer to perform a method according to an embodiment of the present invention.

[0118] refer to Figure 4 , a block diagram of an electronic device 400 that can serve as a server or client of the present invention will now be described, which is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0119] like Figure 4As shown, electronic device 400 includes a computing unit 401, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 402 or a computer program loaded from a storage unit 408 into a random access memory (RAM) 403. Various programs and data required for the operation of electronic device 400 can also be stored in RAM 403. Computing unit 401, ROM 402, and RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to bus 404.

[0120] Multiple components within electronic device 400 are connected to I / O interface 405, including an input unit 406, an output unit 407, a storage unit 408, and a communication unit 409. Input unit 406 can be any type of device capable of inputting information into electronic device 400. Input unit 406 can receive input numeric or character information and generate key input signals related to user settings and / or function control of the electronic device. Output unit 407 can be any type of device capable of presenting information and may include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. Storage unit 408 may include, but is not limited to, a magnetic disk or an optical disk. Communication unit 409 allows electronic device 400 to exchange information / data with other devices via computer networks such as the Internet and / or various telecommunication networks and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver and / or a chipset, such as a Bluetooth™ device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0121] The computing unit 401 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 401 performs the various methods and processes described above. For example, in some embodiments, any of the above-mentioned aggregate payment methods can be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 408. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 400 via the ROM 402 and / or the communication unit 409. In some embodiments, the computing unit 401 can be configured to execute any of the above-mentioned aggregate payment methods by any other appropriate means (e.g., by means of firmware).

[0122] The program code for implementing the method of the present invention can be written in any combination of one or more programming languages. Such program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0123] In the context of the present invention, machine-readable medium can be a tangible medium that can contain or store a program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0124] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., a magnetic disk, an optical disk, a memory, a programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0125] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0126] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0127] Computer systems may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The client and server relationship arises through computer programs running on the respective computers and having a client-server relationship to each other.

Claims

1. An aggregate payment method, characterized in that: Applied to a mobile terminal, the method includes: When the mobile terminal is close to an NFC cash register device, obtaining Clips trigger information sent by the NFC cash register device; In response to the Clips trigger information, displaying an aggregated cashier interface on the mobile terminal, wherein the aggregated cashier interface displays a plurality of candidate payment applications and payment information, wherein the payment information includes a payment amount; Determining a target payment application based on the operation received by the aggregated cashier interface, and calling the target payment application according to a call identifier corresponding to the target payment application; The target payment application is used to execute a payment action according to the payment information.

2. The method according to claim 1, characterized in that The method further comprises: Receiving aggregated cashier interface setting information, wherein the aggregated cashier interface setting information includes identifiers of multiple candidate payment applications to be displayed; Based on the aggregated cashier interface setting information, configuring a call identifier corresponding to each of the candidate payment applications; Storing each of the candidate payment application identifiers and a call identifier corresponding to each of the candidate payment applications; The displaying of the aggregated cashier interface in the mobile terminal includes: The aggregated cashier interface is loaded based on the stored candidate payment application identifiers and the call identifiers corresponding to the candidate payment applications.

3. The method according to claim 2, characterized in that The aggregated cashier interface also includes an alternative application entry, and the receiving of aggregated cashier interface setting information includes: According to the record of the number of times the user's payment application is used, a preset number of payment applications with the highest number of uses are determined as candidate payment applications; Determining, based on a preset payment application list and a record of the number of times the payment application is used, that the payment application and the alternative payment application are not installed in the mobile terminal; Generating the aggregated cashier interface setting information based on the candidate payment application, the not-installed payment application, and the alternative payment application; The method further comprises: Configuring a call identifier corresponding to each of the alternative payment applications and a download link for each of the not-installed payment applications; The candidate payment applications and the non-installed payment applications are displayed on a display page corresponding to the candidate application entrance.

4. The method according to claim 2, characterized in that The call identifier includes a Scheme URL and / or a Universal Link; The calling the target payment application according to the calling identifier corresponding to the target payment application includes: Call the target payment application according to the Scheme URL bound to the target payment application, and send the payment information to the target payment application; or, The target payment application is called according to the Universal Link bound to the target payment application, and the payment information is sent to the target payment application.

5. An aggregate payment device, characterized in that: Applied to a mobile terminal, the device includes: An acquisition module, configured to acquire Clips trigger information sent by the NFC cash register device when the mobile terminal is close to the NFC cash register device; a response module, configured to display an aggregated cashier interface on the mobile terminal in response to the Clips trigger information, wherein the aggregated cashier interface displays a plurality of candidate payment applications and payment information, wherein the payment information includes a payment amount; A calling module, configured to determine a target payment application based on the operation received by the aggregated cashier interface, and call the target payment application according to a calling identifier corresponding to the target payment application; The payment module is used to use the target payment application to perform a payment action according to the payment information.

6. The device according to claim 5, characterized in that The device further comprises: A setting module, configured to receive aggregated cashier interface setting information, wherein the aggregated cashier interface setting information includes identifiers of multiple candidate payment applications to be displayed; Based on the aggregated cashier interface setting information, configuring a call identifier corresponding to each of the candidate payment applications; Storing each of the candidate payment application identifiers and a call identifier corresponding to each of the candidate payment applications; The displaying of the aggregated cashier interface in the mobile terminal includes: The aggregated cashier interface is loaded based on the stored candidate payment application identifiers and the call identifiers corresponding to the candidate payment applications.

7. The device according to claim 6, characterized in that The aggregated cashier interface also includes an alternative application entry, and the receiving of aggregated cashier interface setting information includes: According to the record of the number of times the user's payment application is used, a preset number of payment applications with the highest number of uses are determined as candidate payment applications; Determining, based on a preset payment application list and a record of the number of times the payment application is used, that the payment application and the alternative payment application are not installed in the mobile terminal; Generating the aggregated cashier interface setting information based on the candidate payment application, the not-installed payment application, and the alternative payment application; The setting module is used to configure the call identifier corresponding to each of the alternative payment applications and the download link of each of the not-installed payment applications; The response module is configured to display each of the alternative payment applications and each of the non-installed payment applications on a display page corresponding to the alternative application entry.

8. The device according to claim 6, characterized in that The call identifier includes a Scheme URL and / or a Universal Link; The calling the target payment application according to the calling identifier corresponding to the target payment application includes: Call the target payment application according to the Scheme URL bound to the target payment application, and send the payment information to the target payment application; or, The target payment application is called according to the Universal Link bound to the target payment application, and the payment information is sent to the target payment application.

9. An electronic device comprising: processor; as well as Memory for storing programs, The program includes instructions, which, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 4.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to enable a computer to execute the method according to any one of claims 1 to 4.

Images