Method and apparatus for implementing payment function on intelligent business terminal

Abstract

The present invention provides a method and device for implementing a payment function on an intelligent commercial terminal. The method includes: the intelligent commercial terminal obtains system permissions using a system signature, pre-sets payment configuration information for non-system applications of the intelligent commercial terminal through a payment application, and uploads the payment configuration information to a cloud server; the intelligent commercial terminal sends non-system application information to the cloud server to obtain corresponding payment configuration information from the cloud server; the payment application monitors the currently running application; if it is monitored that the payment configuration information of the currently running application matches the obtained corresponding payment configuration information, the payment application is triggered to perform a payment operation for the currently running application. The present invention can complete payments conveniently and quickly, improving the user's payment experience.

Description

Technical Field

[0001] Embodiments of the present invention relate to the technical field of intelligent terminals, and in particular, to a method and device for implementing a payment function on an intelligent commercial terminal. Background Art

[0002] In the era of mobile Internet, in addition to means such as online banking and electronic credit cards, there is also a way to relatively reduce the risk of online payment, that is, the payment mode and its payment process using third-party applications that are developing rapidly. In the actual operation process, the third-party application can be the bank itself that issues credit cards. Specifically, when making an online payment, the disclosure of the credit card number and password only transfers between the cardholder and the bank, reducing the risk caused by transfer through merchants. The third-party application can also be an institution with good reputation and technical support capabilities other than the bank. The payment is carried out by the third party between the cardholder or customer and the bank. Specifically, the cardholder first transfers account information to the third party in the form of some electronic data that replaces the bank account number, avoiding the cardholder directly disclosing bank information to the merchant. In addition, there is no need to log in to different online banking interfaces. Instead, each time you log in, you can see the interface of the third-party institution. The third-party application signs relevant agreements with each major bank, enabling the third-party application and the bank to perform some form of data exchange and relevant information confirmation. In this way, the third-party application can implement a payment process between the cardholder or consumer and each bank, and the final payee or merchant.

[0003] However, most of the current payment plugins on the market are developed on Windows. When implementing the payment function on a terminal based on the Android system, the function of automatically capturing the amount information requires system permissions or the user to manually set permissions for the third-party application. Usually, the third-party application does not have the corresponding system permissions, and manual authorization by the user is relatively cumbersome.

[0004] It should be noted that the above introduction of the technical background is only for the convenience of clearly and completely explaining the technical solution of the present invention and facilitating the understanding of those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art just because these solutions are described in the background art part of the present invention. Summary of the Invention

[0005] Aiming at the above problems, the purpose of the embodiments of the present invention is to provide a method and device for implementing a payment function on an intelligent commercial terminal, which can complete the payment conveniently and quickly, and improve the payment experience of users.

[0006] To achieve the above object, an embodiment of the present invention provides a method for implementing a payment function on an intelligent commercial terminal. At least one payment application is installed on the intelligent commercial terminal. The method includes: the intelligent commercial terminal uses a system signature to obtain system permissions, sets payment configuration information for non-system applications of the intelligent commercial terminal in advance through the payment application, and uploads the payment configuration information to a cloud server; the intelligent commercial terminal sends non-system application information to the cloud server to obtain the payment configuration information corresponding to the non-system application from the cloud server; the intelligent commercial terminal monitors the currently running application through the payment application; if it is monitored that the payment configuration information of the currently running application matches the obtained corresponding payment configuration information, the intelligent commercial terminal triggers the payment application to perform a payment operation for the currently running application.

[0007] An embodiment of the present invention provides a device for implementing a payment function, including: a setting module for using a system signature to obtain system permissions, setting payment configuration information for non-system applications of the intelligent commercial terminal in advance through the payment application, and uploading the payment configuration information to a cloud server; an obtaining module for sending non-system application information to the cloud server to obtain the payment configuration information corresponding to the non-system application from the cloud server; a monitoring module for monitoring the currently running application through the payment application; a payment module for triggering the payment application to perform a payment operation for the currently running application if it is monitored that the payment configuration information of the currently running application matches the obtained corresponding payment configuration information.

[0008] As can be seen from the above, the method and device for implementing a payment function on the intelligent commercial terminal provided by the embodiments of the present invention obtain system permissions through a system signature for enabling the system permissions set for the payment application on the intelligent commercial terminal in advance. Thus, payment configuration information can be set for non-system applications of the intelligent commercial terminal and stored in the cloud server. Through the monitoring of the currently running application by the payment application, when it is monitored that the payment configuration information of the currently running application matches the obtained corresponding payment configuration information, a payment operation is triggered, thereby enabling convenient and fast payment and improving the user's payment experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts. In the drawings:

[0010] Figure 1Schematic flowchart of a method for implementing a payment function on an intelligent commercial terminal provided by an embodiment of the present invention.

[0011] Figure 2 Interaction schematic diagram between the client and the server provided by an embodiment of the present invention.

[0012] Figure 3 Interaction schematic diagram between the payment application of the client and the cloud storing data of the server provided by an embodiment of the present invention.

[0013] Figure 4 Schematic structural diagram of a device for implementing a payment function on an intelligent commercial terminal provided by an embodiment of the present invention. Detailed implementation manners

[0014] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. In addition, the singular forms "a", "the" and "said" used in the embodiments of the present invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0015] Reference to "embodiment" in this document means that a particular feature, structure or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. The phrase appears in various places in the specification and does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein may be combined with other embodiments.

[0016] To enable those skilled in the art of this technology to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings.

[0017] An embodiment of the present invention provides a method for implementing a payment function on an intelligent commercial terminal. The method is applied to the intelligent commercial terminal, and preferably, an Android system is installed on the intelligent commercial terminal and at least one payment application is installed, such as Figure 1 As shown, the method specifically includes the following steps:

[0018] Step S11, the smart business terminal uses the system signature to obtain system permissions, pre-sets payment configuration information for non-system applications of the smart business terminal through the payment application, and uploads the payment configuration information to the cloud server;

[0019] Step S12, when the smart business terminal is turned on or the payment application is started, the non-system application information is sent to the cloud server, so as to obtain the payment configuration information corresponding to the non-system application from the cloud server;

[0020] Step S13, the smart business terminal monitors the currently running application through the payment application;

[0021] Step S14: If the payment configuration information of the currently running application is monitored to match the corresponding payment configuration information obtained, the smart business terminal triggers the payment application to perform a payment operation for the currently running application.

[0022] Figure 2 Schematic diagram of interaction between a client and a cloud server, wherein the client is an intelligent business terminal equipped with an Android system, and at least one payment application is installed on the intelligent business terminal, such as Figure 2 As shown, including:

[0023] Step S21, the client sends a request to the server to obtain payment configuration information of the non-system application on the smart business terminal, wherein the request includes the package name and version of the non-system application;

[0024] Step S22: The server retrieves the payment configuration information of the corresponding application according to the received package name and version, and returns it to the client.

[0025] In step S23, the client monitors the Accessibility Event event to learn about the information changes of the currently running application, and matches the payment configuration information of the currently running application with the obtained payment configuration information of the corresponding application. If the match is successful, the payment application is triggered to display a transaction prompt for the currently running application to request the user to pay.

[0026] Step S24, after the client confirms the payment, the server performs the payment transaction and returns the payment result to the client, wherein the user clicks confirm in the transaction prompt displayed on the client to initiate the payment transaction.

[0027] Step S25: the client displays the payment result.

[0028] Figure 3 It is a detailed diagram of the interaction between the client and the cloud server, such as Figure 3 As shown, including:

[0029] Step S31: The payment application obtains system permissions using the system signature of the intelligent business terminal, pre-sets payment configuration information for non-system applications of the intelligent business terminal, and uploads the payment configuration information to the cloud server.

[0030] In this step, the payment application sets payment configuration information for non-system applications of the intelligent business terminal in SaaS (Software-as-a-Service) according to the configuration process. The payment configuration information includes one or more of the following: the package name of the application, version, checkout page class name, ID and location of the payment amount control on the checkout page, etc. After the setting is completed, the payment configuration information is uploaded to the cloud server.

[0031] Step S32: The intelligent business terminal uploads the package name and version of the non-system application to the cloud server.

[0032] In this step, after the intelligent business terminal boots up or the payment application starts, it sends the information of the non-system applications it has installed to the cloud server, where the application information includes the package name and version of the application.

[0033] Step S33: The cloud server retrieves the payment configuration information of the corresponding application according to the package name and version of the application, and returns it to the intelligent business terminal.

[0034] In this step, the cloud server retrieves the payment configuration information of the corresponding application locally according to the received package name and version of the application and returns it to the intelligent business terminal. The payment application configuration information includes the package name, version, checkout page class name, ID and location of the payment amount control on the checkout page, etc.

[0035] In addition, the payment configuration information returned by the cloud server also includes a configuration type, which can further include: A, indicating that the application has configured the payment application; B, indicating that the application has docked with the interface of the payment application; C, indicating that the application has neither configured the payment application nor docked with the interface of the payment application, but belongs to a cashier application.

[0036] Step S34: The intelligent business terminal determines whether the returned payment configuration information is empty. If it is not empty, proceed to step S35; if it is empty, end the process.

[0037] Step S35: The intelligent business terminal monitors the currently running non-system applications through the payment application.

[0038] In this step, the payment application monitors the currently running non-system applications by invoking the UIAutomation function in the system's UIAutomationShellWrapper.

[0039] Step S36: Determine whether the payment configuration information of the currently running application being monitored matches the obtained payment configuration information of the corresponding application. If it matches, proceed to Step S37 or S310; if it does not match, proceed to Step S311 or S312.

[0040] In this step, when the application information changes, an AccessibilityEvent event is emitted. If the payment application monitors the AccessibilityEvent event, it calls the UIAutomation API in the system UIAutomationShellWrapper class to capture the AccessibilityNodeInfo node information of the currently running application, and determines whether the payment configuration information (package name, version, checkout page class name, checkout page payment amount control ID, location, and configuration type) in the AccessibilityNodeInfo node information of the currently running application matches the obtained payment configuration information of the corresponding application.

[0041] Step S37: If it matches and the configuration type is that Application A has configured a payment application, display the payment page. After obtaining the payment confirmation from the client, initiate a payment transaction to the cloud server.

[0042] Step S38: The cloud server completes the payment transaction and returns the payment result to the payment application.

[0043] Step S39: Display the payment result.

[0044] Step S310: If it matches and the configuration type is that Application B has docked the interface of a payment application, prompt the user to directly use the docked payment application interface.

[0045] Step S311: If it does not match and the configuration type is that Application A has configured a payment application, it may be that the version has been upgraded. Prompt to reset the configuration information, and after completion, upload it to the cloud server for storage.

[0046] Step S312: If it does not match and the configuration type is that Application C has neither configured a payment application nor docked the interface of a payment application, but it is a cashier application, set the payment configuration information for the application and upload the payment configuration information to the cloud server for storage.

[0047] The embodiment of the present invention also provides a device for implementing a payment function. The device is preferably an intelligent commercial terminal of the Android system, such as Figure 4 as shown, including:

[0048] A setting module 41, configured to obtain system permissions using a system signature, set payment configuration information for non-system applications of an intelligent business terminal in advance through a payment application, and upload the payment configuration information to a cloud server;

[0049] An obtaining module 42, configured to send non-system application information to the cloud server so as to obtain the payment configuration information corresponding to the non-system application from the cloud server;

[0050] A monitoring module 43, configured to monitor the currently running application through the payment application;

[0051] A payment module 44, configured to, if it is monitored that the payment configuration information of the currently running application matches the obtained corresponding payment configuration information, trigger the payment application to perform a payment operation for the currently running application.

[0052] Wherein, the setting module is specifically configured to: set payment configuration information for non-system applications of the intelligent business terminal in SaaS according to a configuration process through the payment application, and the payment configuration information includes: the package name of the application, the version, the class name of the checkout page, the ID and location of the payment amount control on the checkout page; after the setting is completed, upload the payment configuration information to the cloud server.

[0053] Wherein the obtaining module is specifically configured to: send the package name and version of the application to the cloud server so that the cloud server retrieves the payment configuration information of the corresponding application locally according to the received package name and version of the application and returns it to the intelligent business terminal, and the payment application configuration information includes: the package name of the application, the version, the class name of the checkout page, the ID of the payment amount control on the checkout page, the location, and the configuration type; the configuration type further includes one or more of the following: the application has configured the payment application; the application has docked with the interface of the payment application; the application has neither configured the payment application nor docked with the interface of the payment application, but belongs to a cashier application.

[0054] Wherein the monitoring module is specifically configured to: the payment application monitors the currently running application by invoking the UIAutomation function in the UIAutomationShellWrapper class of the system; if an AccessibilityEvent event is monitored, call the UIAutomationAPI in the system UIAutomationShellWrapper class to capture the AccessibilityNodeInfo node information of the currently running application, and determine whether the payment configuration information in the AccessibilityNodeInfo node information of the currently running application matches the obtained corresponding payment configuration information.

[0055] The payment module is specifically used for: if it is monitored that the payment configuration information of the currently running application matches the corresponding payment configuration information obtained, and the configuration type in the obtained payment application configuration information is that the application has been configured with a payment application, then the payment page is displayed, and after the payment confirmation is obtained, a payment transaction is initiated to the cloud server; if it is monitored that the payment configuration information of the currently running application matches the corresponding payment configuration information obtained, and the configuration type in the obtained payment application configuration information is an interface of the application that has been connected to the payment application, then the user is prompted to use the connected payment application interface directly; if it is monitored that the payment configuration information of the currently running application does not match the corresponding payment configuration information obtained, and the configuration type in the obtained payment application configuration information is that the application has not been configured with a payment application and has no interface for the resulting payment application, but belongs to a cash register application, then the setting module is triggered to set the payment configuration information for the currently running application, and the payment configuration information is uploaded to the cloud server for storage.

[0056] An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of the method described in the above embodiments are implemented.

[0057] An embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in the above embodiments when executing the program.

[0058] The method and device for realizing the payment function on the smart business terminal provided by the embodiment of the present invention, by pre-setting a system signature for the payment application on the smart business terminal to enable the system permission, the system permission can be obtained through the system signature, so that the payment configuration information can be set for the non-system application of the smart business terminal and stored in the cloud server. The payment application monitors the currently running application, and when the payment configuration information of the currently running application matches the corresponding payment configuration information obtained, the payment operation is triggered, so that the payment can be completed conveniently and quickly, improving the user's payment experience.

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

[0060] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present invention. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate means for realizing the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 or multiple blocks.

[0061] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including instruction means, and the instruction means realizes the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 or multiple blocks.

[0062] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for realizing the functions specified in one flow Figure 1 one flow or multiple flows and / or blocks Figure 1 or multiple blocks.

[0063] The specific embodiments described above further elaborate on the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are only specific embodiments of the present invention and are not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for implementing a payment function on an intelligent commercial terminal, where the intelligent commercial terminal is installed with an Android system and has at least one payment application, characterized in that, Including: The intelligent business terminal uses the system signature to obtain system permissions, sets payment configuration information for non-system applications of the intelligent business terminal in advance through a payment application, and uploads the payment configuration information to the cloud server; The intelligent business terminal sends non-system application information to the cloud server to obtain the payment configuration information corresponding to the non-system application from the cloud server; The intelligent business terminal monitors the currently running application through the payment application; If it is monitored that the payment configuration information of the currently running application matches the obtained corresponding payment configuration information, the intelligent business terminal triggers the payment application to perform a payment operation for the currently running application; The step of setting payment configuration information for non-system applications of the intelligent business terminal in advance through the payment application and uploading the payment configuration information to the cloud server specifically includes: Setting payment configuration information for non-system applications of the intelligent business terminal in the SaaS according to the configuration process through the payment application. The payment configuration information includes: the package name, version, checkout page class name, checkout page payment amount control ID and location of the application; after the setting is completed, the payment configuration information is uploaded to the cloud server.

2. The method for implementing a payment function on an intelligent commercial terminal according to claim 1, characterized in that, The step of the intelligent business terminal sending non-system application information to the cloud server to obtain the payment configuration information corresponding to the non-system application from the cloud server specifically includes: The intelligent business terminal sends the package name and version of the application to the cloud server, so that the cloud server retrieves the payment configuration information of the corresponding application locally according to the received package name and version of the application and returns it to the intelligent business terminal, where the payment configuration information includes: the package name, version, checkout page class name, checkout page payment amount control ID, location and configuration type of the application; The configuration type includes one or more of the following: the application has been configured with the payment application; the application has been docked with the interface of the payment application; the application has not been configured with the payment application and has not been docked with the interface of the payment application, but belongs to a cashier application.

3. The method for implementing a payment function on an intelligent commercial terminal according to claim 2, wherein, The step of the intelligent business terminal monitoring the currently running application through the payment application specifically includes: The payment application monitors the currently running application by invoking the UIAutomation function in the UIAutomationShellWrapper class of the system; If the AccessibilityEvent event is monitored, the UIAutomation API in the system UIAutomationShellWrapper class is called to capture the AccessibilityNodeInfo node information of the currently running application, and it is judged whether the payment configuration information in the AccessibilityNodeInfo node information of the currently running application matches the obtained corresponding payment configuration information.

4. The method for realizing the payment function on the intelligent business terminal according to claim 3, wherein, The step that if it is monitored that the payment configuration information of the currently running application matches the obtained corresponding payment configuration information, the intelligent business terminal triggers the payment application to perform a payment operation for the currently running application specifically includes: If it is monitored that the payment configuration information of the currently running application matches the corresponding payment configuration information obtained, and the configuration type in the obtained payment configuration information is that the payment application has been configured for the application, then display the payment page. After obtaining the payment confirmation, initiate a payment transaction to the cloud server.

5. The method for implementing a payment function on an intelligent business terminal according to claim 3, characterized in that, If it is monitored that the payment configuration information of the currently running application matches the corresponding payment configuration information obtained, then the intelligent business terminal triggers the payment application to perform a payment operation for the currently running application, specifically including: If it is monitored that the payment configuration information of the currently running application matches the corresponding payment configuration information obtained, and the configuration type in the obtained payment configuration information is that the application has docked with the interface of the payment application, then prompt the user to directly use the already docked payment application interface.

6. The method for implementing a payment function on an intelligent business terminal according to claim 3, wherein The method further includes: If it is monitored that the payment configuration information of the currently running application does not match the corresponding payment configuration information obtained, and the configuration type in the obtained payment configuration information is that the application has neither configured the payment application nor docked with the interface of the payment application, but it belongs to the cashier application, then set the payment configuration information for the currently running application and upload the payment configuration information to the cloud server for storage.

7. A device for implementing a payment function, characterized in that Including: A setting module, configured to obtain system permissions using the system signature, set payment configuration information for non-system applications of the intelligent business terminal in advance through the payment application, and upload the payment configuration information to the cloud server; An obtaining module, configured to send non-system application information to the cloud server so as to obtain the corresponding payment configuration information of the non-system application from the cloud server; A monitoring module, configured to monitor the currently running application through the payment application; A payment module, configured to trigger the payment application to perform a payment operation for the currently running application if it is monitored that the payment configuration information of the currently running application matches the corresponding payment configuration information obtained; The step of setting the payment configuration information for non-system applications of the intelligent business terminal in advance through the payment application and uploading the payment configuration information to the cloud server specifically includes: Setting the payment configuration information for non-system applications of the intelligent business terminal in the SaaS according to the configuration process through the payment application. The payment configuration information includes: the package name, version, checkout page class name, ID and location of the payment amount control on the checkout page. The intelligent business terminal is installed with the Android system.

8. The apparatus for implementing the payment function according to claim 7, wherein The monitoring module is specifically configured to: The payment application monitors the currently running application by invoking the UIAutomation function in the UIAutomationShellWrapper class of the system; if the AccessibilityEvent event is monitored, then call the UIAutomation API in the system UIAutomationShellWrapper class to capture the AccessibilityNodeInfo node information of the currently running application, and determine whether the payment configuration information in the AccessibilityNodeInfo node information of the currently running application matches the corresponding payment configuration information obtained.

9. The device for realizing the payment function according to claim 7, characterized in that, The payment module is specifically configured to: If it is monitored that the payment configuration information of the currently running application matches the corresponding payment configuration information obtained, and the configuration type in the obtained payment configuration information is that the payment application has been configured for the application, then display the payment page. After obtaining the payment confirmation from the client, initiate a payment transaction to the cloud server; If it is monitored that the payment configuration information of the currently running application matches the corresponding payment configuration information obtained, and the configuration type in the obtained payment configuration information is that the application has docked with the interface of the payment application, then prompt the user to directly use the already docked payment application interface.

Images