Payment method, electronic device, and communication system

By using an intelligent agent to act as an intermediary for users to make payments on the payment side, the problem of intelligent agents being unable to automatically complete payments in the payment process is solved, achieving fully automated payment and improving the user experience.

CN120634545BActive Publication Date: 2025-11-21SHENZHEN XUNLIAN ZHIFU NETWORK CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202511132648.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2025-08-13
Publication Date
2025-11-21
Estimated Expiration
2045-08-13

AI Technical Summary

Technical Problem

In existing technologies, the intelligent agents on electronic devices cannot automatically complete payments, resulting in cumbersome user operations and frequent interface transitions, which negatively impacts the user experience.

Method used

The intelligent agent obtains authorization from multiple shopping applications on the payment side and acts as an agent for users to make payments, realizing fully automated payment processes, including order creation and payment processing.

Benefits of technology

By automating the payment process through intelligent agents, user operation steps and interface jumps are reduced, improving the user experience and simplifying the payment process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120634545B_ABST
    Figure CN120634545B_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide a payment method, an electronic device and a communication system. An agent can obtain authorization of a plurality of shopping applications at a payment side, and then collect money on behalf of the shopping applications at the payment side. The agent can also obtain payment authorization of a user at the payment side, and then make payment on behalf of the user at the payment side. The payment side can include a plurality of payment applications and their servers. In this way, after receiving a user instruction for purchasing goods, the agent can automatically create an order, complete payment of the order, and feed back the payment result to the user, realizing full-process automation and improving user experience.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of electronic technology, and in particular to payment methods, electronic devices and communication systems. Background Technology

[0002] Currently, with the development of artificial intelligence technology, some applications or functions on electronic devices, such as voice assistants, can automatically help users complete various tasks based on user commands, such as ordering food or hailing a ride by voice. However, these applications or functions still have limitations in the payment process and cannot automatically help users complete payments. Summary of the Invention

[0003] This application provides a payment method, electronic device, and communication system. The intelligent agent can obtain authorization from multiple shopping applications on the payment side and then act as an agent for these applications to collect payments. The intelligent agent can also obtain payment authorization from the user on the payment side and then act as an agent for the user to make payments. The payment side can include multiple payment applications and their servers. In this way, after receiving a user instruction to purchase goods, the intelligent agent can autonomously create an order, complete the payment, and provide feedback to the user, achieving full-process automation and thus improving the user experience.

[0004] Firstly, embodiments of this application provide a payment method applied to an electronic device. The electronic device may include a first application. The first application may have an intelligent agent deployed on it, or may invoke an intelligent agent. The electronic device may also include one or more payment applications and one or more shopping applications. The payment application may refer to an application or platform that provides payment services. The shopping application may be an application or platform that provides online shopping services to users. One or more payment applications may include the first payment application. One or more shopping applications may include the first shopping application.

[0005] The payment method may include: First, an electronic device can receive a first user instruction to purchase a first product through a first application. Then, the electronic device can respond to the first user instruction by sending an order request to a first shopping application to purchase the first product through the first application. The electronic device can then respond to the order request through the first shopping application, generate a first order for the first product, and send the order information to the first application. Finally, after receiving the order information through the first application, the electronic device can complete the payment for the first order.

[0006] The first user instruction can be in various forms, such as voice instructions, text instructions, image instructions, and action instructions. The first user instruction may include information about the first product, including but not limited to one or more of the following: the name, specifications, and quantity of the first product. The order request may include information about the first product. This information may include, but is not limited to, the name, specifications, and quantity of the first product.

[0007] The payment method provided in this application allows users to input user instructions for purchasing goods through an intelligent agent, and then view order information and complete payment through the intelligent agent. This reduces user operation steps and interface jump processes, thereby reducing user disturbance and improving the user experience.

[0008] In conjunction with the first aspect, in some embodiments, the method for an electronic device to complete payment for the first order after receiving the information of the first order through the first application may specifically include: after receiving the information of the first order through the first application, the electronic device sends a payment request for the first order to a first payment application through the first application. Then, the electronic device can complete the payment for the first order by responding to the payment request through the first payment application.

[0009] In conjunction with the first aspect, in some embodiments, the first user instruction is used to purchase the first product immediately.

[0010] In conjunction with the first aspect, in some embodiments, after an electronic device receives information about a first order through a first application, the method for completing payment for the first order may specifically include: after receiving the information about the first order through the first application, the electronic device sends a payment request to the server of a first payment application, requesting the server of the first payment application to pay for the first order. Then, the electronic device may receive a first message from the server of the first payment application indicating that payment for the first order has been completed.

[0011] In conjunction with the first aspect, in some embodiments, the first user instruction can be used to purchase a first product at a set time.

[0012] In conjunction with the first aspect, in some embodiments, a payment request may include a payment token. The payment token may be a credential authorizing the first payment application and its server to act as an agent for the user in making payments, supporting the first application in interacting with the user through payment transactions between the first payment application and its server. The payment token can take various forms; for example, it may be a unique identifier generated by the server of the first payment application. Upon receiving the payment token sent by the first application, the first payment application or its server can determine the user's identity based on the payment token and thus complete the payment.

[0013] In conjunction with the first aspect, in some embodiments, the electronic device can obtain a payment token through a first application.

[0014] In conjunction with the first aspect, in some embodiments, the method for an electronic device to obtain a payment token through a first application may specifically include: the electronic device displaying a first user interface through the first payment application, the first user interface being used to prompt the user to enter authentication information. The electronic device may receive first authentication information through the first user interface. Then, the electronic device receives a verification result from the first payment application indicating that the first authentication information has been verified successfully. After successful verification, the electronic device may send a second authorization request for requesting a payment token to the server of the first payment application through the first application, and then receive the payment token from the server of the first payment application through the first application.

[0015] In conjunction with the first aspect, in some embodiments, before the electronic device displays the first user interface through the first payment application, it may further include: the electronic device sending a first authorization request to the server of the first payment application through the first application, and the electronic device receiving a first authorization identifier from the server of the first payment application through the first application.

[0016] In conjunction with the first aspect, in some embodiments, the payment token may include a first payment token. The first payment token is obtained by the electronic device through a first application before receiving a first user instruction. The first payment token may correspond to a first authorized amount. Before sending a payment request, if the first application detects that the amount of the first order is less than the first authorized amount, the payment request includes the first payment token.

[0017] In conjunction with the first aspect, in some embodiments, the payment token may include a second payment token, which is obtained after receiving a first user instruction through the first application. Before sending a payment request, if the first application detects that the amount of the first order is greater than the first authorized amount, or if the first user instruction includes a preset amount, then the payment request includes the second payment token. The second authorized amount corresponding to the second payment token is either the amount of the first order or the preset amount.

[0018] In conjunction with the first aspect, in some embodiments, the first payment token expires after the first authorization period ends.

[0019] In conjunction with the first aspect, in some embodiments, the second payment token expires after the number of uses reaches a preset number or after the second authorization period expires.

[0020] In conjunction with the first aspect, in some embodiments, the method further includes: the electronic device receiving instructions from a third user through a first application. In response to the third user instructions, the electronic device displays one or more of the following through the first application: the authorization time, authorization validity period, authorization amount, and corresponding payment application of the payment token. This allows the user to comprehensively and intuitively understand and manage the authorization status of the payment token.

[0021] In conjunction with the first aspect, in some embodiments, before the electronic device receives the first user instruction through the first application, the method further includes: the electronic device sending first registration information to the server of the first payment application through the first application. The electronic device then sends second registration information to the server of the first payment application through the first shopping application. The first shopping application integrates shopping information from one or more merchants, and the second registration information may include the registration information of one or more merchants.

[0022] In conjunction with the first aspect, in some embodiments, after the electronic device receives the information of the first order through the first application, the method further includes: the electronic device displaying the information of the first order through the first application. This allows users to understand the order status and details in real time, improving the user experience.

[0023] In conjunction with the first aspect, in some embodiments, after the electronic device receives the information of the first order through the first application and completes the payment for the first order, the method further includes: the electronic device outputting a first notification message through the first application, the first notification message being used to notify the user that the payment for the first order has been completed. This allows the user to monitor the payment status of the order in real time, improving the user experience.

[0024] In conjunction with the first aspect, in some embodiments, after the electronic device receives the information of the first order through the first application and before completing the payment of the first order, the method further includes: the electronic device outputting a second prompt message through the first payment application, the second prompt message being used to prompt the user to perform risk verification.

[0025] In conjunction with the first aspect, in some embodiments, after sending the payment request, the method further includes: the electronic device receiving a fourth user instruction, which is used to confirm payment for the first order. This allows the user to decide whether to actually perform the payment operation. The user can issue a payment confirmation instruction only after confirming that the order information is correct and the financial situation is appropriate, thereby enhancing payment security and improving the user experience.

[0026] In conjunction with the first aspect, in some embodiments, the first application may be a voice assistant application.

[0027] Secondly, embodiments of this application provide an electronic device, which may include a memory and a processor. The memory may store a computer program, and when the processor executes the computer program, it may perform the method described in the first aspect and any possible implementation thereof.

[0028] Thirdly, embodiments of this application provide a communication system that may include an electronic device and a server; wherein the electronic device may be the electronic device in the first aspect and any possible implementation thereof, and the server may be the server in the first aspect and any possible implementation thereof.

[0029] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, can perform the method described in the first aspect and any possible implementation thereof.

[0030] Fifthly, embodiments of this application provide a computer program product that, when executed by a processor, can perform the methods described in the first aspect and any possible implementation thereof.

[0031] In a sixth aspect, embodiments of this application provide a chip system applied to an electronic device. The chip system includes one or more processors that invoke a computer program to enable the electronic device to perform the methods described in the first aspect and any possible implementation thereof. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0033] Figure 1 An example is shown of an interactive process in which an intelligent agent assists a user in placing an order;

[0034] Figure 2 An example of a method for password-free payment is shown;

[0035] Figure 3 An example is shown of a method for an intelligent agent to assist a user in completing a payment;

[0036] Figure 4 An exemplary system architecture for implementing the payment method provided in the embodiments of this application is shown;

[0037] Figure 5 The interactive flow of the payment method provided in the embodiments of this application is illustrated by way of example;

[0038] Figure 6The implementation flow of the payment method provided in the embodiments of this application is illustrated by way of example;

[0039] Figure 7 The process of a payment token corresponding to a first payment application is illustrated exemplarily;

[0040] Figure 8 An exemplary illustration shows a first user interface provided in an embodiment of this application;

[0041] Figure 9 An example is shown of a user interface for displaying authorization records;

[0042] Figure 10 The process of Embodiment 1 is illustrated by way of example;

[0043] Figure 11 Two user interfaces are shown as examples, prompting the user to confirm payment for the first order.

[0044] Figure 12 The process of Embodiment 2 is illustrated by way of example;

[0045] Figure 13 This is an interactive schematic diagram of the payment method provided in Embodiment 2;

[0046] Figure 14 An electronic device 100 provided in an embodiment of this application is illustrated by way of example;

[0047] Figure 15 An exemplary embodiment of the server 200 provided in this application is shown;

[0048] Figure 16 An exemplary embodiment of the communication system 300 provided in this application is shown. Detailed Implementation

[0049] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be a limitation of this application.

[0050] In this embodiment, the electronic device may include a first application. The first application may integrate an Artificial Intelligence Agent (AI Agent) or may invoke an AI Agent.

[0051] An intelligent agent is an intelligent entity capable of autonomously perceiving its environment, making independent decisions, and executing tasks, possessing autonomy, adaptability, and interactive capabilities. AI Agents deeply couple the cognitive capabilities of Large Language Models (LLMs) with their tool-calling capabilities, achieving automated task processing through a closed loop of "perception-planning-action." They can not only answer questions but also proactively complete a series of tasks.

[0052] An intelligent agent can include a memory module, a tool module, and an action module.

[0053] The memory module is responsible for storing and / or organizing acquired information to assist in driving the agent's decision-making. The tool module is used to invoke tools and is the final executor of the decision; the tools invoked by the tool module may be external to the agent or internal to it. The action module translates the agent's plans into concrete actions. In some cases, the action module's output includes invoking tools; in this case, the action module can utilize the tool module to invoke the tools.

[0054] An intelligent agent can be software, hardware, or a system. Intelligent agents can be deployed on electronic devices, which can integrate hardware and computing resources, enabling the intelligent agent to perceive the environment, process data, make decisions, and take corresponding actions in real time.

[0055] In this embodiment of the application, the electronic device may include one or more shopping applications.

[0056] A shopping app can be a software program that runs on electronic devices such as smartphones and tablets. Each shopping app can have its own server. The shopping app on the electronic device and the shopping app's server work together to provide users with an online shopping experience, allowing users to browse, select, and purchase goods or services on their electronic devices.

[0057] In this embodiment, the electronic device may further include one or more payment applications. A payment application can refer to an application or platform that provides payment services. Each payment application may have a corresponding server. The payment application and its server can jointly support users in making electronic payments and can be responsible for core functions such as processing payment transactions, fund clearing, and risk management. Payment applications may include mobile payment applications, online payment gateways, bank payment applications, third-party payment platforms, etc.

[0058] The primary application on the electronic device, the shopping application, the payment application, and the servers of the shopping application and the payment application can work together to complete the payment function.

[0059] The following section introduces a method for an intelligent agent to assist users in placing orders.

[0060] An intelligent agent on an electronic device can receive user input instructions for purchasing goods. The agent can then use the natural language capabilities of a large language model to parse these instructions, identifying key information such as the store name and product name. Based on this information, the agent can then orchestrate tasks to be performed, such as opening the corresponding shopping app on the electronic device, searching for products within the app, and creating an order to purchase the goods.

[0061] Figure 1 An example is shown of an interactive process in which an intelligent agent assists a user in placing an order.

[0062] Figure 1 The interactive process shown can include the following three stages: receiving instructions, placing an order, and making a payment.

[0063] in, Figure 1 (a) in the text can correspond to the instruction receiving stage. For example... Figure 1 As shown in (a), the intelligent agent can receive the user's voice command "Please help me buy product a" through voice interaction.

[0064] Figure 1 (b)-(e) in the diagram correspond to the order-taking process. In this process, the agent can locate and open a shopping app A on an electronic device, which can be used to purchase product a. The agent can then simulate user actions within the shopping app A to quickly generate an order for product a, as shown in... Figure 1 Search for and select product a in the interface shown in (c). Figure 1 In the interface shown in (d), select the specifications of product a. Figure 1 In the interface shown in (e), the user fills in the shipping address and clicks the "Submit Order" button, etc. The agent can simulate user actions to create an order a1 for purchasing product a in shopping application A, and then proceed to the payment stage. For example, the agent simulates a user clicking the "Submit Order" button and then proceeding to the payment stage.

[0065] Figure 1 (f) in this context can correspond to the payment process. In the payment process, the intelligent agent no longer participates in the interaction; instead, the user manually triggers the payment for the order. For example, the user can... Figure 1 Clicking "Confirm Payment" on the payment interface of payment application B shown in (f) triggers payment order a1. In some embodiments, to reduce disruption to the user, payment can be made through a password-free payment method.

[0066] Figure 2 An example of a method for password-free payment is shown.

[0067] like Figure 2 As shown, this password-free payment method can include a signing stage and a payment stage. The signing stage can specifically include the following steps:

[0068] 1. Shopping application A requests its server to create a signed order.

[0069] 2. The server of shopping application A calls the pre-signing interface of the server of payment application B.

[0070] 3. The server of payment application B returns a pre-signature number (preSignNo) to the server of shopping application A.

[0071] 4. The server of shopping application A sets the contract parameters (contractStr) and returns them to shopping application A.

[0072] 5. Shopping application A calls the formal contract signing interface via contractStr to launch the contract signing and cashier platform.

[0073] 6. Payment application B displays contract-related information through the contract checkout.

[0074] 7. The user completes the signing process at the payment application B's signing checkout.

[0075] 8. Payment application B's server processes the contract.

[0076] 9. After successfully processing the contract, the server of payment application B returns the contract result to payment application B.

[0077] 10. Payment application B displays the signing results page.

[0078] 11. After the user closes the signing results page, payment application B will return the signing results to shopping application A.

[0079] 12. When the server of shopping application A calls the pre-signing interface of the server of payment application B, it can pass a callback interface address. After the signing operation is completed, the server of payment application B can asynchronously notify the server of shopping application A of the signing result through this callback interface.

[0080] Once the contract is signed, the payment phase can begin. During payment, the server of shopping application A can directly call the password-free payment interface of payment application B's server to complete the deduction service. Payment application B's server can then return the password-free payment request result to shopping application A's server. After successfully processing the password-free payment deduction, payment application B's server can call the callback interface address passed by shopping application A's server when requesting the password-free payment interface to asynchronously notify shopping application A's server of the payment result.

[0081] exist Figure 1 and Figure 2 In the method shown, because the payment application does not provide an open interface to the agent, the agent can only help the user open the shopping application and generate an order within the shopping application, but cannot help the user complete the payment for the order within the payment application. Therefore, after the user inputs a user instruction to the agent to purchase a certain product, manual operation is still required in the payment process to complete the final order payment.

[0082] Furthermore, in Figure 1 In this method of using an intelligent agent to assist users in placing orders, after the user inputs a command through the agent, the interface on the electronic device will undergo multiple screen transitions, including but not limited to transitions from the interface corresponding to the intelligent agent to the shopping app interface, transitions between multiple interfaces within the shopping app, and transitions from the shopping app interface to the payment interface. These screen transitions waste power on the electronic device, lead to redundant and time-consuming ordering processes, and result in a poor user experience.

[0083] With the development of intelligent agent technology, some engineers have proposed new methods for intelligent agents to assist users in making payments. The following describes one such method.

[0084] Figure 3 An example is shown of a method by which an intelligent agent assists a user in completing a payment.

[0085] exist Figure 3 In the method shown, the intelligent agent can integrate shopping functionality. That is, the intelligent agent can act as a shopping application, selling goods or services to users, generating orders, and collecting payments. For example, intelligent agent A could be a poetry creation assistant, capable of creating poems based on user instructions and then generating a payment order for that poem creation. Furthermore, the intelligent agent can interact with the payment application's server through a series of open interfaces to complete the order payment. Figure 3 As shown, the agent can send a payment request to the payment application's server based on the generated order. Upon receiving the payment request, the payment application's server can return a payment link to the agent. The agent can then use the payment link to navigate to the payment interface to complete the payment. Finally, the payment application's server returns the payment result to the agent.

[0086] However, in Figure 3 In the payment methods shown, different agents can provide different shopping functions or services. An agent can only process payments for orders related to the shopping function it provides. For example, agent A could be a poetry writer / singer, providing poetry writing services to users and collecting payment. Agent B could be a flight booking assistant, helping users book flights and collecting payment, and so on. Therefore, Figure 3The agent in this approach cannot assist users with ordering and payment across multiple shopping apps, which is a significant limitation.

[0087] This application provides payment methods, electronic devices, and communication systems.

[0088] The system architecture for implementing the payment method provided in the embodiments of this application will be introduced below.

[0089] Figure 4 An exemplary system architecture for implementing the payment method provided in the embodiments of this application is shown.

[0090] like Figure 4 As shown, the system architecture can include the user side, merchant side, payment side, and intelligent agent.

[0091] The user side can include the user. As the payment entity, the user can authorize a smart agent to perform related payment operations on their behalf. For example, the smart agent can access the user's payment information, send payment requests to the payment application on the payment side, and so on. The specific details regarding user authorization of smart agents to perform payment operations will be discussed in detail later and will not be elaborated upon here.

[0092] The merchant side can include one or more shopping applications, such as Figure 4 The examples shown are shopping apps A, B, C, etc. The merchant-side shopping app, acting as the payment recipient, can establish an authorization relationship with the intelligent agent on the payment side. The merchant-side shopping app can send information about orders to be paid to the intelligent agent, which then sends a payment request for that order to the payment side and completes the payment collection on behalf of the shopping app.

[0093] The payment side can include multiple payment applications and their servers, such as Figure 4 The payment application 1 and its server 1, payment application 2 and its server 2, payment application 3 and its server 3, etc. are shown.

[0094] intelligent agents in Figure 4In the illustrated system architecture, the agent acts as an intermediary, connecting multiple shopping applications on the merchant side and multiple payment applications and their servers on the payment side. In this embodiment, both shopping applications and the agent can register on the server of the payment application on the payment side. The agent can then act as an agent for the registered shopping applications to collect payments on that payment application and its server. For example, the agent can register on the server of payment application 1 on the payment side, and shopping applications A, B, and C on the merchant side can also register on the server of payment application 1. This allows the agent to collect payments on behalf of the registered shopping applications A, B, and C on the server of payment application 1. Essentially, after registering on the server of the payment application, the agent can act as the largest acquiring merchant using that payment application. The agent can act as the recipient of all orders and then deliver the received order amounts to the corresponding shopping application or the corresponding acquiring merchant entity within the shopping application.

[0095] Thus, through the payment method provided in this application embodiment, the intelligent agent can obtain authorization from multiple shopping applications on the payment side, and then act as an agent for these shopping applications to collect payments. The intelligent agent can also obtain user authorization on the payment side, and then act as an agent for the user to make payments. The payment side may include multiple payment applications and their servers. In this way, after receiving a user instruction to purchase goods, the intelligent agent can autonomously create an order, complete the payment, and provide feedback to the user on the payment result, achieving full-process automation and thus improving the user experience.

[0096] Figure 5 The interactive flow of the payment method provided in the embodiments of this application is illustrated by way of example.

[0097] like Figure 5 As shown in (a), the electronic device can receive the user instruction "Please buy me an iced Americano" through an agent and display the user instruction through the agent. Then, as... Figure 5 As shown in (b), in response to a received user instruction, the electronic device can continue to display the message "An order has been generated for you" in the agent's dialogue interface, indicating to the user that an order has been generated for the purchase of the specified item (i.e., an iced Americano). The electronic device can also display order information in the dialogue interface through the agent, including but not limited to: images, names, specifications, quantities, and order amounts of the purchased item. Finally, the electronic device can... Figure 5 The dialogue interface of the agent shown in (c) displays prompts such as "Order payment completed" or "I have purchased an iced Americano for you", indicating to the user that the order payment has been completed.

[0098] Therefore, the payment method provided in this application embodiment allows users to input user instructions for purchasing goods through an intelligent agent, and then view order information and complete payment through the intelligent agent. This reduces user operation steps and interface jump processes, thereby reducing disturbance to users and improving user experience.

[0099] Figure 5 This is merely an illustrative description of the interaction flow of the payment method provided in the embodiments of this application, and is not intended to limit the scope. For example, in some embodiments, the electronic device may also display the ordering process through a shopping application, display a payment page through a payment application, and return to the dialogue interface of the smart agent after the payment is completed, etc.

[0100] The implementation process of the payment method provided in the embodiments of this application is described below.

[0101] Figure 6 The implementation flow of the payment method provided in the embodiments of this application is illustrated by way of example. The details are as follows:

[0102] S101. The electronic device receives a first user instruction through a first application, the first user instruction being used to purchase a first product.

[0103] The first application is an intelligent agent application, meaning that the first application can deploy intelligent agents or can invoke intelligent agents.

[0104] In some embodiments, the first application may be a voice assistant application. The first application can provide voice interaction functions for the user. For example, the first application can preset a wake-up command. When the electronic device detects the wake-up command input by the user, it can wake up the first application and then interact with the user via voice to receive the first user command.

[0105] The first user instruction is a request or operation issued by the user to the first application to trigger the purchase of the first product. The first user instruction can take various forms, such as voice instructions, text instructions, image instructions, and action instructions. The first user instruction may include information about the first product, including but not limited to one or more of the following: the name of the first product, its specifications, quantity, etc. The first application can determine the first product based on this information. For example, the first user instruction could be "Buy me a large iced Americano," thus determining that the first product's name is iced Americano, its specifications are large, and its quantity is one cup.

[0106] The first commodity can be a physical product, a virtual product, a service, or a function, etc.

[0107] In some embodiments, the first user instruction may be a single user instruction. For example, an electronic device may receive a user instruction such as "Please buy me a large iced Americano" through a first application. In this case, the electronic device can parse the user's intended first item to purchase from the aforementioned single user instruction as "a large iced Americano" through the first application.

[0108] In some embodiments, the first user instruction can also be multiple user instructions, which can be used to refine the user's shopping intent and collectively reflect the user's intention to purchase the first item. For example, an electronic device may first receive the following user instruction through a first application: "Please buy me a cup of coffee." At this time, the electronic device cannot determine the specific information of the first item the user intends to purchase based on the received user instruction, or it cannot determine the first item the user intends to purchase. To further clarify the user's purchasing intent, the electronic device can guide the user to input more user instructions through the first application. For example, the electronic device can continue to output the following prompts to the user through the first application: "What flavor of coffee do you want to buy?", "What cup size do you want?", etc. Then, the electronic device can further receive one or more user instructions, such as "Iced Americano" or "Large". Based on the above multiple user instructions, the electronic device can determine through the first application that the first item the user intends to purchase is "a large iced Americano". In other words, the electronic device can guide the user to input multiple user instructions through the first application to obtain more purchase information, including but not limited to: the first item, the specifications of the first item, the purchase time, the delivery address, etc.

[0109] In other embodiments, the first user instruction may include information about the first product, such as "Please buy me coffee." In this case, the first application can determine the first product according to specific rules, or the first application can pass product-related information (such as "coffee") from the first user instruction to a shopping application, which then determines the first product based on the received product-related information and specific rules. For example, the first application can determine the frequently purchased "iced Americano" as the first product based on "coffee" in the first user instruction combined with historical user instructions.

[0110] S102. The electronic device sends an order request to the first shopping application in response to a first user instruction through the first application. The order request is used to request the purchase of the first product.

[0111] First Shopping App is a shopping app for purchasing first-hand goods.

[0112] The electronic device can determine the first shopping application based on the instructions of the first user through the first application.

[0113] In some embodiments, the first user instruction may include information indicating a first shopping application, such as the name of the first shopping application. The electronic device can parse the name of the first shopping application from the first user instruction and determine the first shopping application based on its name. For example, the first user instruction could be "Please buy an iced Americano in shopping application A," and the electronic device can determine that the first shopping application is shopping application A.

[0114] In other embodiments, the first user instruction may not include information for instructing a first shopping application. The electronic device can use the first application to query one or more shopping applications available for purchasing the first product. If only one shopping application is found, it can be designated as the first shopping application. If multiple shopping applications are found, the electronic device can prompt the user to select a first shopping application from the query results, or the electronic device can directly select a shopping application from the query results according to certain rules, such as selecting the shopping application most frequently used by the user.

[0115] S103. The electronic device responds to the order request through the first shopping application, generates a first order, and sends the information of the first order to the first application. The first order is used to purchase the first product.

[0116] An order request may include information about the first product. This information may include, but is not limited to, the product's name, specifications, quantity, etc. The shopping app can create a first order based on this information. The first order is used to purchase the first product. For example, a first order could be used to purchase a large iced Americano.

[0117] In some embodiments, after receiving an order request, the first shopping application can first parse the information of the first product from the request, and then perform product checks based on the information, including but not limited to one or more of the following: checking whether the first shopping application sells the first product, whether the inventory of the first product is sufficient, etc. If there are any problems in the above checks, the first shopping application can return a prompt message to the first application, informing the first application that the first shopping application does not sell the first product or that the first product is sold out, etc. The first application can further prompt the user that the order creation failed. If the above checks pass, the first shopping application can create the first order, generate the information of the first order, and send the information of the first order to the first application.

[0118] The information for the first order may include, but is not limited to, one or more of the following: the order amount of the first order, the identifier of the first order (such as the order number), the product details of the first order (such as product images), the status of the first order (such as creating, paying, etc.), etc.

[0119] S104. After receiving the information of the first order through the first application, the electronic device completes the payment for the first order.

[0120] In this embodiment, after receiving information about the first order, the first application can send a payment request to the first payment application or its server to request payment for the first order. The first payment application or its server can respond to the payment request, pay the first order, and return the payment result to the first application. The payment request may include, but is not limited to, one or more of the following: the identifier of the first order, the identifier of the first shopping application, the amount of the first order, the identifier of the acquiring merchant in the first shopping application, etc.

[0121] The first payment application can be any one of one or more payment applications already installed on the electronic device. For example, the first payment application could be... Figure 4 Any one of the payment applications 1, 2, or 3.

[0122] In some embodiments, the first payment application may be determined by a first application. The first user instruction may include information for instructing the first payment application. For example, the first user instruction may be "Please buy me a large iced Americano, pay using payment application 1," and then the first application can determine the first payment application as payment application 1 based on the first user instruction. The first user instruction may also not include information for instructing the first payment application. In this case, after receiving the information of the first order sent by the first shopping application, the first application may prompt the user to select the first payment application from among multiple payment applications, or the user may choose the first payment application independently according to preset rules.

[0123] In other embodiments, the first payment application may also be determined by the first shopping application. For example, the first shopping application may establish an association with one or more payment applications, and when the first shopping application generates an order, it may designate a payment application with which it has already established an association as the first payment application. Another example is that the first shopping application may use the payment application used in its last purchase as the first payment application, and so on. In this case, when the first shopping application sends the first order information to the first application, it may also send the identifier of the first payment application, such as the name, serial number, or other unique identifier of the first payment application.

[0124] In some embodiments, the payment request sent by the first application to the first payment application or the server of the first payment application may further include a payment token corresponding to the first payment application. The payment token may be obtained by the first application from the server of the first payment application. In this embodiment, the payment token may be a credential authorizing the first application to act as an agent for the user in the first payment application and its server, used to support the first application in interacting with the user through payment on behalf of the user. The payment token can take various forms; for example, it may be a unique identifier generated by the server of the first payment application. After receiving the payment token sent by the first application, the first payment application or its server can determine the user's identity based on the payment token and then complete the payment.

[0125] The following describes how the first application obtains the payment token corresponding to the first payment application.

[0126] Figure 7 This example illustrates the process of a payment token corresponding to a first payment application. The details are as follows:

[0127] S201. The first application registers with the server of the first payment application.

[0128] Electronic devices can send initial registration information to the server of a first payment application via a first application. This initial registration information may include the first application's agency qualification information, such as enterprise certification, service scope, and security certificates. After receiving the initial registration information, the server of the first payment application can complete the registration of the first application based on this information. The first application can then obtain legal agency qualifications on the server of the first payment application, including acting as an agent for users to make payments, acting as an agent for shopping applications to collect payments, etc.

[0129] S202. The first shopping application registers with the server of the first payment application.

[0130] Specifically, the first shopping application can send a second registration message to the server of the first payment application. The first shopping application can integrate shopping information from one or more merchants, and the second registration information may also include the registration information of these one or more merchants. The second registration message may include, but is not limited to, one or more of the following: merchant number, business license, payment account, etc.

[0131] S203. The first application and the first shopping application establish a proxy relationship on the server of the first payment application.

[0132] After registering with the First Payment app's server, the First Shopping app can establish an agency relationship with the First Payment app. The First Payment app can then legally act as an agent for the First Shopping app in handling payment-related operations.

[0133] S204. The first application sends a first authorization request to the server of the first payment application.

[0134] S205. The first application receives the first authorization identifier from the server of the first payment application.

[0135] The first application can call the pre-authorization interface provided by the server of the first payment application to send a pre-authorization request, i.e., a first authorization request, to the server of the first payment application. The first authorization request can include parameters such as user identifier, first application identifier, and electronic device identifier. Pre-authorization can be used to initially verify the user's legitimacy and avoid resource waste or security risks caused by directly requesting payment tokens.

[0136] If the pre-authorization is successful, the electronic device can receive a pre-authorization success message, such as "pre-authorization successful," and a pre-authorization identifier from the server of the first payment application via the first application, and then continue to execute S206. The pre-authorization identifier can be a unique identifier, such as presig_123456. The pre-authorization identifier is the same as the first authorization identifier.

[0137] If pre-authorization fails, the electronic device can receive a pre-authorization failure message from the server of the first payment application, such as "application does not have permission," "user not registered," "user identifier is empty," etc., and then terminate the process of obtaining the payment token. In this embodiment, the reasons for pre-authorization failure may include, but are not limited to, the following: the first application has not registered on the server of the first payment application, the user has not opened an account in the first payment application, the first application has not obtained payment agent permissions, etc.

[0138] In some embodiments, S204 and S205 may not be executed when the electronic device obtains the payment token of the corresponding first payment application through the first application.

[0139] S206. First application notification: The first payment application displays a first user interface, which prompts the user to enter authentication information.

[0140] S207. Receive the first authentication information in the first user interface.

[0141] After pre-authorization is approved, the first application can open the first user interface of the first payment application through the interface or jump link provided by the first payment application.

[0142] Figure 8 An exemplary first user interface provided by an embodiment of this application is shown.

[0143] like Figure 8As shown, the first user interface may include an authorization information display area 10, an authentication information input area 11, and a confirmation control 12. The authorization information display area 10 can be used to display currently authorized information to the user, such as the authorized object, authorization validity period, authorization description, etc. The authentication information input area 11 may include a text input box for obtaining the user's authentication information. When the electronic device detects that the user clicks the confirmation control 12 on the first user interface, it can trigger the execution of step S208.

[0144] Figure 8 This is merely one example of a first user interface. In other embodiments, the first user interface can have a variety of different displays. For example, the authentication information input area 11 of the first user interface may also include voice input controls, facial recognition controls, fingerprint collection controls, and other controls for receiving user authentication information.

[0145] In this application embodiment, the identity verification information may include, but is not limited to, one or more of the following: payment account and payment password, user fingerprint information, user facial information, SMS verification code, etc.

[0146] In some embodiments, the electronic device may prompt the user for confirmation of authorization before displaying the first user interface, for example, by displaying a prompt message on the interface. After the electronic device detects that the user has confirmed authorization, it then displays the first user interface and receives the first authentication information entered by the user.

[0147] S208. The first payment application sends the first authentication information to the server of the first payment application.

[0148] S209. The first payment application receives the verification result from the server of the first payment application.

[0149] S210. The first application receives the verification result from the first payment application, and the verification result indicates that the first identity verification information has passed the verification.

[0150] The server of the first payment application can verify the user's identity based on the first identity verification information, such as comparing the payment password in the first identity verification information with the payment password stored when the user registered to see if they match, comparing the SMS verification code in the first identity verification information with the random code generated by the server to see if they match, and checking whether biometric features (such as fingerprint information, facial information, etc.) match.

[0151] If a match is found, the verification is confirmed as successful, and a message such as "Verification Successful" is sent to the first payment application, indicating that the first identity verification information has been verified. If a mismatch is found, the verification is confirmed as failed, and a message such as "Verification Failed" is sent to the first payment application, indicating that the first identity verification information has failed. The electronic device can then prompt the user of authorization failure or prompt the user to re-enter the first identity verification information through the first application or the first payment application.

[0152] S211. The first application sends a second authorization request to the server of the first payment application, the second authorization request being used to request a payment token.

[0153] S212. The first application receives a payment token from the server of the first payment application.

[0154] After user identity verification is successful, the electronic device can formally request a payment token from the server of the first payment application through the first application. In response to the second authorization request, the server of the first payment application can generate a payment token and send the generated payment token to the first application on the electronic device.

[0155] The second authorization request may include the first authorization identifier obtained in S205. The server of the first payment application can associate the first authorization identifier with the previous pre-authorization record to confirm that the authorization has passed the user's legitimacy verification. If the electronic device has not performed the pre-authorization in S204-S205, the second authorization request may include parameters such as the user identifier used to verify the user's legitimacy, the identifier of the first application, and the identifier of the electronic device.

[0156] Payment tokens can have a corresponding authorization period and / or authorization amount. The authorization period is the legal time window for using the payment token; after this time, the payment token will automatically expire. The authorization amount can be the maximum transaction amount allowed by the payment token; transactions exceeding this amount will be rejected.

[0157] In some embodiments, the authorization validity period and authorization amount corresponding to the payment token can be determined by the first application, for example, by the first application based on user instructions. The first application can receive user instructions indicating the authorization validity period and authorization amount, such as "Please enable password-free payment for payment application A, with an authorization validity period of 1 month and an authorization amount of 200 yuan." In this case, the second authorization request may also include the authorization validity period, authorization amount, etc. In other embodiments, the authorization validity period and authorization amount corresponding to the payment token can also be determined by the server of the first payment application. For example, the server of the first payment application can dynamically generate the authorization validity period and authorization amount based on information such as payment business rules and risk control strategies.

[0158] S213. The first application receives a payment token status change notification from the server of the first payment application.

[0159] The server of the first payment application can proactively notify the application of changes in the status of the payment token via a callback interface, such as when the payment token is about to expire or has been revoked by the user. This ensures that the first application can be aware of the payment token's status in real time, preventing payment failures due to expired payment tokens.

[0160] In this embodiment of the application, payment tokens can be divided into two categories. One category can be referred to as a first payment token, and the other category can be referred to as a second payment token.

[0161] The first payment token can be a long-term authorized token, and it may not have a limit on the number of uses. That is, the first payment token can be used an unlimited number of times within its authorized validity period. The first payment token may correspond to a first authorized validity period and a first authorized amount. The first payment token expires after the first authorized validity period. In this embodiment, the first payment token may be obtained by the electronic device through a first application before receiving a first user instruction to purchase a first product.

[0162] The second payment token may correspond to a preset number of uses. That is, the second payment token cannot be used an unlimited number of times. For example, if the valid number of uses for the second payment token is one, then the second payment token can only be used once. The second payment token may correspond to a second authorization validity period and a second authorization amount. The second payment token may expire after the preset number of uses is reached or after the second authorization validity period ends. In this embodiment, the second payment token may be obtained after the electronic device receives a first user instruction for purchasing a first product through the first application, or after the first application receives information about a first order sent by a first shopping application.

[0163] In this embodiment, the electronic device can also receive a user instruction for viewing authorization records through the first application, which can be referred to as a third user instruction. The third user instruction can be a voice instruction, such as "view authorization records." It can also be an action instruction or gesture instruction, such as clicking a control for viewing authorization records on the interface of the first application. In response to the third user instruction, the electronic device can display the authorization records through the first application. The authorization records may include, but are not limited to, one or more of the following: the authorization time of the payment token, the authorization validity period, the authorization amount, the corresponding payment application, etc.

[0164] Figure 9 An example user interface for displaying authorization records is shown.

[0165] like Figure 9As shown in (a) and (b) above, the user interface for displaying the authorization record may include controls 21 and 22. When the electronic device detects that the user has selected control 21, it may display as shown in (a) and (b) below. Figure 9 The interface shown in (a) displays the authorization record of the first payment token to the user. When the electronic device detects that the user has selected control 22, it can display as shown in [image / description]. Figure 9 The interface shown in (b) displays the authorization record of the second payment token to the user.

[0166] Figure 9 Both (a) and (b) can include multiple authorization records, and each authorization record's corresponding display area can include a "View" control. Users can click the "View" control to view more detailed authorization information for the corresponding authorization record. For example, when the electronic device detects that the user clicks the "View" control 23 corresponding to authorization record 1, it can display... Figure 9 The interface shown in (c) displays detailed information about Authorization Record 1 to the user. Authorization Record 1 corresponds to the first payment token, which can be exemplified as Payment Token 1. Figure 9 As shown in (c), the electronic device can display that the status of payment token 1 is within the validity period, the corresponding payment application is payment application 1, the authorization validity period is from March 1, 2025 to June 1, 2025, and the authorized amount is 200 yuan, etc. If the status of the payment token is within the validity period, then... Figure 9 (c) may also include control 25. When the electronic device detects that the user clicks control 25, it can actively revoke payment token 1. For example, when the electronic device detects that the user clicks the "view" control 24 corresponding to authorization record 4, it can display... Figure 9 The interface shown in (c) displays detailed information about authorization record 4 to the user. Authorization record 4 corresponds to the second payment token, which can be exemplified as payment token 2. Figure 9 As shown in (d), the electronic device can display that the status of payment token 2 is expired, the corresponding payment application is payment application 2, the authorization validity period is from 12:00 to 24:00 on March 10, 2025, the authorization amount is 1000 yuan, the authorization usage is 1 time, and it has been used 1 time.

[0167] The previous section introduced the method for the first application to obtain the payment token of the first payment application. The following section details the method of using the payment token to make payments through two examples.

[0168] Example 1

[0169] In Embodiment 1, the first user instruction can be used to instantly purchase the first item. After receiving the information of the first order through the first application, the electronic device can send a payment request to the first payment application through the first application. The payment request can be used to request payment for the first order. Then, the electronic device can complete the payment for the first order by responding to the payment request through the first payment application.

[0170] Figure 10 The process of Embodiment 1 is illustrated below. The details are as follows:

[0171] S301. The electronic device receives a second user instruction through a first application, the second user instruction being used to obtain a first payment token.

[0172] The second user command can be in various forms, such as voice commands, text commands, etc.

[0173] The second user instruction may include information indicating the first payment application, such as the name of the first payment application. For example, the second user instruction could be "Enable password-free payment for payment application 1," where the first payment application is, in example, payment application 1. In response to the second user instruction, the electronic device can obtain a first payment token from the server of payment application 1 through the first application.

[0174] The second user instruction can include the authorization validity period and the authorization amount. For example, the second user instruction could be "Activate password-free payment for payment application 1, with an authorization validity period of 1 month and an authorization amount of 200 yuan." Then, the first application can obtain a first payment token from the server of payment application 1, with an authorization validity period of 1 month and an authorization amount of 200 yuan. Specifically, during the process of obtaining the first payment token, the second authorization request sent by the first application to the server of payment application 1 can include information for the authorization validity period and the authorization amount.

[0175] S302. The electronic device obtains a first payment token from the server of the first payment application through the first application.

[0176] For details on S302, please refer to S204-S212 above; they will not be elaborated here.

[0177] S303. The electronic device receives a first user instruction through a first application, the first user instruction being used to purchase a first product immediately.

[0178] In this context, "immediate purchase of the first item" refers to purchasing the first item immediately. For example, the first user instruction could be "Please buy me an iced Americano." In response to the first user instruction, the electronic device immediately sends an order request to the first shopping application, i.e., executes S304.

[0179] S304. The electronic device sends an order request to the first shopping application in response to a first user instruction via the first application.

[0180] The order request is used to request the purchase of the first item.

[0181] S305. The electronic device generates a first order in response to an order request through a first shopping application, and sends the information of the first order to the first application. The first order is used to purchase a first product.

[0182] For details of S303-S305, please refer to S101-S103, which will not be elaborated here.

[0183] S306. The electronic device displays information about the first order through a first application.

[0184] The method for displaying information about a first order through a first application by an electronic device can be found in [reference needed]. Figure 5 (b) in the text will not be elaborated here.

[0185] S307. The electronic device sends a payment request to the first payment application through the first application.

[0186] In Example 1, the payment request includes a payment token corresponding to the first payment application.

[0187] Specifically, before sending a payment request, the first application can first check whether the first payment token is within its authorized validity period. If not, it can prompt the user to obtain a new first payment token or cancel the payment. If yes, it can then check whether the amount of the first order is less than the first authorized amount corresponding to the first payment token.

[0188] If the first application detects that the amount of the first order is less than the first authorized amount of the first payment token, the payment request sent by the first application to the first payment application may include the first payment token. If the first application detects that the amount of the first order is greater than the first authorized amount, the electronic device may obtain a second payment token from the server of the first payment application through the first application. The second authorized amount corresponding to the second payment token may be the amount of the first order. In this case, the payment request sent by the first application to the first payment application includes the second payment token.

[0189] In some implementations, the first user instruction may also include a preset amount for purchasing the first item. In this case, the electronic device can obtain a second payment token from the server of the first payment application through the first application before sending the payment request. The authorized amount corresponding to the second payment token can be the preset amount included in the first user instruction. The payment request sent by the first application to the first payment application may include the second payment token. For example, the first user instruction could be "Please book a double room for me at a price under 500 yuan". Then, the electronic device can obtain a payment token 2 with an authorized amount of 500 yuan from the first payment application through the first application. The preset number of uses for payment token 2 is one. After receiving the information of the first order, the first application sends a payment request containing payment token 2 to the first payment application.

[0190] The payment request may also include the identifier of the first order, the identifier of the first shopping application, the amount of the first order, the identifier of the acquiring merchant in the first shopping application, and so on.

[0191] S308. The electronic device detected that the user confirmed payment for the first order.

[0192] In Embodiment 1, the electronic device may also prompt the user to confirm payment for the first order via the first application or the first payment application. The electronic device can then receive a fourth user instruction to confirm payment for the first order via the first application or the first payment application.

[0193] The fourth user instruction can be a voice instruction. For example, an electronic device can receive a voice instruction such as "confirm payment" or "cancel order" via the first user.

[0194] The fourth user instruction can also be a gesture instruction. Specifically, the electronic device can display a user interface prompting the user to confirm payment for the first order through the first application or the first payment application, see [link to relevant documentation]. Figure 11 Then, the user's confirmation of payment for the first order was detected on the user interface prompting the user to confirm payment for the first order.

[0195] Figure 11 Two user interfaces are shown as examples, prompting the user to confirm payment for the first order.

[0196] like Figure 11As shown in (a), the electronic device can display dialog box 30 in the dialog interface of the first application. Dialog box 30 can display the prompt text "Do you want to confirm payment?", as well as a "Cancel Order" control 31 and a "Confirm Payment" control 32. The "Cancel Order" control 31 is used to cancel the payment for the first order, and the "Confirm Payment" control 32 can be used to pay for the first order. For example, the electronic device can detect when the user clicks the "Confirm Payment" control 32, and then the electronic device can send a prompt message to the first payment application through the first application, allowing the first payment application to continue completing the payment for the first order.

[0197] like Figure 11 As shown in (b), the electronic device can also launch a payment window 33 of the first payment application via the first application. The payment window 33 may include a "Cancel Order" control 34 and a "Confirm Payment" control 35. The "Cancel Order" control 34 is used to cancel the payment for the first order, and the "Confirm Payment" control 35 can be used to pay for the first order. For example, the electronic device can detect when the user clicks the "Confirm Payment" control 35, and the first payment application continues to complete the payment for the first payment order.

[0198] In the interaction flow of the payment method provided in Example 1, Figure 11 The user interface shown can be exemplarily described in... Figure 5 It will be displayed after (b) in the middle.

[0199] It should be noted that S308 is an optional step in the payment method provided in Embodiment 1, and in some implementations, S308 may not be executed.

[0200] S309. The electronic device sends an identity verification request to the server of the first payment application through the first payment application.

[0201] S310. The electronic device receives the identity verification result from the server of the first payment application through the first payment application.

[0202] The identity verification request may include a payment token. Upon receiving the identity verification request, the server of the first payment application can verify the legitimacy and validity of the payment token. Legitimacy refers to whether the payment token was generated by the server of the first payment application. Validity refers to whether the payment token is within its authorized validity period, whether the amount of the first order is less than the authorized amount corresponding to the payment token, and so on.

[0203] If the verification passes, the server of the first payment application can return an indication message such as "Verification passed" to the first payment application, and then continue to execute the subsequent payment process. If the verification fails, the server of the first payment application can return a warning message to the first payment application based on the specific reason for the verification failure, such as "Payment token has expired" or "Order amount exceeds authorized amount", etc.

[0204] In some implementations, electronic devices can also perform risk control (i.e., risk management) on the payment of the first order through the first payment application, further enhancing payment security. Risk control involves using technical means, rule engines, and data analysis to monitor and intervene in transaction behavior in real time to identify, assess, and intercept potential risks, thereby maintaining the legitimacy of the transaction.

[0205] S311-S313 are the steps for implementing risk control.

[0206] S311. The electronic device detects that the user has completed risk control confirmation through the first payment application.

[0207] The first payment application can detect risks in the payment of the first order based on risk control rules. Examples include login from a different location and high-frequency trading alerts. Then, the electronic device can prompt the user for risk control confirmation through the first payment application or the first application itself. Specifically, the electronic device can output a second prompt message through the first payment application to remind the user to confirm the risk control. Methods for user risk control confirmation may include, but are not limited to: entering a verification code, answering security questions, and biometric verification. Through these methods, the first payment application can obtain the risk control confirmation information entered by the user.

[0208] S312. The electronic device sends a risk control verification request to the server of the first payment application through the first payment application.

[0209] S313. The electronic device receives the risk control verification result from the server of the first payment application through the first payment application.

[0210] The risk control verification request can include risk control confirmation information entered by the user. The server of the first payment application can perform risk control verification based on this confirmation information to determine whether to allow the payment of the first order to proceed. If the risk control verification passes, it can return an indication message such as "Verification passed" to the first payment application, instructing the application to complete the payment for the first order. If the risk control verification fails, it can return an indication message such as "Verification failed" to the application, instructing it to terminate the payment for the first order.

[0211] In some implementations, S311-S313 can be omitted, meaning that risk detection and risk control confirmation can be omitted.

[0212] S314. The electronic device completes the payment for the first order through the first payment application.

[0213] S315. The electronic device receives a payment result from the first payment application through the first application.

[0214] S316. The electronic device displays the payment result through a first application.

[0215] The electronic device can output a first notification message to the user, indicating that the payment for the first order has been completed, based on the payment result through a first application. This first notification message can be a voice prompt or a user-defined interface prompt. For example... Figure 5 As shown in (c), the electronic device can display prompts such as "Order payment completed" or "I have purchased an iced Americano for you" in the chat interface of the first application.

[0216] After the payment for the first order is completed, the server of the first payment application can also send the payment result to the first shopping application. The first shopping application can then process the first order based on the payment result, such as preparing for shipment, recording the transaction, etc.

[0217] In Embodiment 1, the user can open the smart agent (i.e., the first application) on an electronic device and input a command to purchase goods immediately. With a payment token already obtained, the smart agent can directly complete the order and payment through task scheduling, or require only a simple confirmation from the user to complete the payment, thereby effectively reducing user disruption and improving convenience.

[0218] Example 2

[0219] In Embodiment 2, the first user instruction can be used to purchase the first item at a set time. In response to the first user instruction, the electronic device can create a scheduled task through the first application, and then generate a first order through the first shopping application at the predetermined time. After receiving the first order information through the first application, the electronic device can send a payment request to the server of the first payment application. This payment request can be used to request the server of the first payment application to pay for the first order. Then, the electronic device can receive a first message from the server of the first payment application. This first message can be used to indicate that the payment for the first order has been completed.

[0220] Figure 12 The process of Embodiment 2 is illustrated below.

[0221] S401. The electronic device receives a second user instruction through a first application, the second user instruction being used to obtain a first payment token.

[0222] S402. The electronic device obtains a first payment token from the server of the first payment application through the first application.

[0223] For details on S401-S402, please refer to S301-302; they will not be elaborated here.

[0224] S403. The electronic device receives a first user instruction through a first application, the first user instruction being used to purchase a first product at a set time.

[0225] S404. Electronic devices create timed order placement tasks through a first application.

[0226] Specifically, "timed purchase of the first item" refers to purchasing the first item at a specific point in time or within a specific time period. In other words, the first user instruction can be used to purchase the first item at a specific point in the future, or it can be used to purchase the first item within a certain time period in the future.

[0227] Figure 13 This is an interactive schematic diagram of the payment method provided in Embodiment 2.

[0228] like Figure 13 As shown in (a), the first user instruction received by the first application could be "Please buy me an iced Americano at 8 AM tomorrow." The first application can create a first scheduled task based on the first user instruction. This first scheduled task instructs the first application to send an order request for a large iced Americano to the first shopping application at 8 AM tomorrow. The electronic device can also display the created first scheduled task in the dialog interface of the first application. Figure 13 As shown in (a), the dialog interface of the first application can display that the execution time of the first scheduled task is "June 1, 2025, 8:00", and the content of the first scheduled task is "Buy a cup of iced Americano".

[0229] like Figure 13 As shown in (b), the first user instruction received by the first application could be, "Please book a hotel for me before 8 PM tomorrow with a price below 1000 yuan." The first application can create a second scheduled task based on this instruction. This second scheduled task instructs the first application to monitor hotel prices before 8 PM tomorrow and send an order request to the first shopping application when the hotel price is below 1000 yuan. Specifically, the first application can send the information of the created second scheduled task to the first shopping application. The first shopping application can continuously monitor product prices, i.e., hotel prices, within a specified time period. When a hotel price is detected to be below 1000 yuan, the first shopping application can send an instruction to the first application, instructing it to send an order request. For example... Figure 13As shown in (b), the electronic device can display information about the second scheduled task in the dialog interface of the first application, including an execution time of "before 20:00 on June 1, 2025" and a task content of "booking a hotel with a price based on 1,000 yuan". After the first application sends the information about the second scheduled task to the first shopping application, the electronic device can also display the text "The scheduled task has been notified to the shopping application" in the dialog interface of the first application.

[0230] It is important to note that, Figure 13 In the scenario shown in (b), the first application can obtain a second payment token from the first payment application after receiving the instruction from the first user. The authorization amount is RMB 1,000 and the authorization validity period is until 20:00 on June 1, 2025.

[0231] S405. The electronic device sends an order request to a first shopping application through a first application. The order request is used to request the purchase of a first product.

[0232] S406. The electronic device responds to an order request through a first shopping application, generates information for a first order, and sends the information for the first order to the first application. The first order is used to purchase a first product.

[0233] For details on S405-S406, please refer to S304-S305; they will not be elaborated upon here.

[0234] S407. The electronic device sends a payment request to the server of the first payment application through the first application.

[0235] In the timed purchase scenario of Embodiment 2, the first application can send a payment request to the server of the first payment application. The payment request may include a first payment token or a second payment token, as detailed in S307.

[0236] In Embodiment 2, the electronic device can also perform risk control (i.e., risk management) on the payment of the first order through the server of the first payment application. Specifically, this includes S408-S413.

[0237] S408. The server of the first payment application identified a transaction risk.

[0238] The server of the first payment application can detect that there is a risk in the payment of the first order according to the risk control rules, and trigger the user transaction risk control process.

[0239] S409. The server of the first payment application suspends payment for the first order.

[0240] S410. Electronic devices notify users to confirm risk control procedures.

[0241] In Embodiment 2, the server of the first payment application can send risk warning information to the first application, and then the first application will notify the user to confirm the risk control through voice or interface display. Electronic devices can also notify users to confirm the risk control through system notifications (such as push notifications) or SMS verification codes.

[0242] S411. The electronic device detects that the user has completed risk control confirmation through the first payment application.

[0243] S412. The electronic device sends a risk control verification request to the server of the first payment application through the first payment application.

[0244] S413. The electronic device receives the risk control verification result from the server of the first payment application through the first payment application.

[0245] For details on S411-S413, please refer to S311-S312; they will not be elaborated here.

[0246] In some implementations, S408-S413 can be omitted, meaning that risk detection and risk control confirmation can be omitted.

[0247] S414. The electronic device completes the payment for the first order through the server of the first payment application.

[0248] S415. The electronic device receives a payment result from the server of the first payment application through the first application.

[0249] In other embodiments, when the first user instruction is used to immediately purchase the first item, the electronic device can also execute S301-S306 in Embodiment 1, and then execute S407-S415 in Embodiment 2 to complete the order payment. That is, when the first user instruction is used to immediately purchase the first item, the first application can immediately send an order request to the first shopping application and receive the first order information. Then, the first application can send a payment request to the server of the first payment application to complete the payment for the first order.

[0250] In other embodiments, when the first user instruction is used to purchase the first item at a set time, the electronic device can also execute S401-S406 in Embodiment 2, and then execute S307-S316 in Embodiment 1 to complete the order payment. That is, when the first user instruction is used to purchase the first item at a set time, the first application can construct a scheduled task to periodically send an order request to the first shopping application and receive the first order information. Then, the first application can send a payment request to the first payment application to complete the payment for the first order.

[0251] This application also provides an electronic device 100.

[0252] Figure 14 An electronic device 100 provided in an embodiment of this application is illustrated by way of example.

[0253] Electronic device 100 can be implemented as the electronic device mentioned above.

[0254] The device type of electronic device 100 can be any of the following: smartphone, tablet, handheld computer, desktop computer, laptop computer, ultra-mobile personal computer (UMPC), personal digital assistant (PDA), wearable devices such as smart bracelet, smartwatch, and smart glasses, extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), in-vehicle devices, or smart city devices.

[0255] Electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a magnetic sensor 180D, a proximity sensor 180G, a fingerprint sensor 180H, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0256] The processor 110 can be one or more, and they can be integrated into an integrated circuit of a system-on-a-chip (SOC). An SOC is a system-on-a-chip. The processor 110 may include a central processing unit (CPU), a graphics processing unit (GPU), and a neural network processing unit (NPU). The CPU may include an application processor (AP) and a baseband processor (BP). The AP is responsible for running the operating system, user interface, and applications on the terminal device; the BP is responsible for transmitting and receiving wireless signals and managing radio frequency services. The GPU is responsible for graphics rendering, performing tasks such as shading, material filling, rendering, and output based on rendering instructions and data from the CPU. The NPU, by referencing biological neural network structures, such as the transmission patterns between neurons in the human brain, can quickly process input information and continuously learn. The NPU can be used to run artificial intelligence algorithms, such as instruction recommendation algorithms, image processing algorithms, and image understanding algorithms. The CPU and GPU can be used to render and synthesize the image to be displayed on the screen 194.

[0257] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, photos, videos, and other data can be stored on the external memory card.

[0258] The internal memory 121 can be used to store one or more computer programs. The processor 110 can execute the payment methods provided in some embodiments of this application, as well as various functional applications and data processing, by running the computer programs stored in the internal memory 121. In this embodiment, the internal memory 121 can store program code for a first application, program code for a first shopping application, and program code for a first payment application. The processor 110 can execute the program code for the first application to receive user instructions, parse user instructions, send order requests to the first shopping application, send payment requests to the first payment application or its server, and so on. The processor 110 can execute the program code for the first shopping application to receive order requests, generate a first order, send information about the first order to the first application, and so on. The processor 110 can execute the program code for the first payment application to receive order requests and complete the payment for the first order, and so on.

[0259] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0260] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0261] The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use on the electronic device 100. The mobile communication module 150 can receive electromagnetic waves via the antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 can be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 can be housed in the same device.

[0262] The wireless communication module 160 can provide wireless communication solutions for applications in the electronic device 100, including wireless local area networks, Bluetooth, global navigation satellite systems, frequency modulation, short-range wireless communication technologies, and infrared technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0263] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with networks and other devices through wireless communication technology.

[0264] Electronic devices can implement audio functions such as music playback and recording through audio modules 170, speakers 170A, receivers 170B, microphones 170C, headphone jacks 170D, and application processors.

[0265] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0266] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. Electronic devices can listen to music or make hands-free calls through the speaker 170A.

[0267] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When an electronic device answers a phone call or voice message, the receiver 170B can be brought close to the ear to hear the voice.

[0268] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic devices can have at least one microphone 170C. In some embodiments, electronic devices can have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic devices can have three, four, or more microphones 170C, enabling sound signal collection, noise reduction, sound source identification, and directional recording, among other functions.

[0269] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface, or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, etc.

[0270] Electronic device 100 can realize display functions through GPU, display screen 194, and application processor. GPU is a microprocessor for image processing, connected to display screen 194 and application processor. GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute instructions to generate or modify display information.

[0271] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0272] A touch sensor can be installed in the display screen 194. The touch sensor is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Then, the electronic device can provide visual output related to the touch operation through the display screen 194. The electronic device can implement display functions through the GPU, display screen 194, touch sensor, and application processor. In this embodiment, the electronic device can use the display functions provided by the GPU, display screen 194, touch sensor, and application processor to display a dialog interface of a first application to the user, and allow user interaction with the electronic device through the aforementioned display screen 194.

[0273] The components in the electronic device 100 can be implemented as hardware modules, software modules, or a combination of software and hardware modules. Figure 14 The illustrated device structure does not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements.

[0274] This application embodiment also provides a server 200. The server 200 can be implemented as a server for the first payment application in the method embodiment described above.

[0275] Figure 15 An exemplary embodiment of the server 200 provided in this application is shown.

[0276] like Figure 15 As shown, server 200 may include: processor 210, memory 220, input / output device 230, communication module 240, etc., and these components can be coupled via a bus.

[0277] Server 200 may have powerful computing resources, and its processor 210 may include one or more powerful processors, such as central processing unit (CPU), neural network processing unit (NPU), graphics processing unit (GPU), etc.

[0278] The processor 210 may include one or more interfaces, such as an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0279] The processor 210 may have a cache memory, which can be used to store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can directly retrieve it from the cache memory, which can reduce the waiting time of the processor 210 and improve the program running efficiency.

[0280] The processor 210 can also connect to external memory. This memory can be high-speed random access memory or non-volatile memory, such as a hard disk, flash memory, universal flash memory (UFS), etc. The memory can also be an external memory card, such as a Micro SD card.

[0281] The processor 210 is the computing core of the server 200, possessing powerful computing capabilities. Coupled with the memory 220, it can read and execute computer-readable instructions stored in the memory 220, running the operating system and various programs. Specifically, the CPU 210 can call programs stored in the memory 220, such as the implementation program of the payment method provided in this embodiment, and execute the instructions contained in that program.

[0282] The memory 220 may include high-speed random access memory, non-volatile memory, such as disk, flash memory, or other non-volatile solid-state storage devices. The memory 220 can be used to store various software programs and multiple sets of instructions. The memory 220 may store an operating system, such as Linux. The memory 220 may also store one or more programs, such as programs involved in patch creation, such as compilers and linkers. The memory 220 may also store the implementation program of the payment method provided in this application embodiment. In this application embodiment, the processor 210 can receive authorization requests and order requests sent by the electronic device 100 by running the program in the memory 220, and can also perform user authentication and generate payment tokens, complete the payment of the first order, etc.

[0283] Input / output device 230 may include devices such as a display screen, keyboard, and mouse, and can be used to receive user input and output program execution results to the user.

[0284] The communication module 240 may include a wired communication module and a wireless communication module. The wired communication module supports wired communication protocols such as Universal Serial Bus (USB), serial port, and Ethernet, communicating with other devices via physical communication cables. The wireless communication module may include 2G / 3G / 4G / 5G wireless communication modules, Wi-Fi communication modules, etc. The wireless communication module receives electromagnetic waves via an antenna, modulates and filters the electromagnetic wave signals, and sends the processed signal to the processor 210. The wireless communication module can also receive signals to be transmitted from the processor 210, modulate and amplify them, and then convert them into electromagnetic waves for radiation via the antenna.

[0285] Figure 15 The illustrated structure does not constitute a limitation on server 200. Server 200 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

[0286] This application also provides a communication system 300.

[0287] Figure 16 An exemplary embodiment of the communication system 300 provided in this application is shown.

[0288] like Figure 16 As shown, the communication system 300 may include an electronic device 100 and a server 200.

[0289] The electronic device may include a primary application, a payment application, and a shopping application.

[0290] The first application may include an intelligent agent, or may invoke an intelligent agent. The first application can receive user instructions. In response to user instructions, the first application can send an order request to the shopping application, send an authorization request to server 200, and obtain a payment token, etc. After receiving the order request from the first application, the shopping application can generate order information and send it to the first application. The first application can then send a payment request carrying a payment token to the payment application or server 200 based on the order information. In some embodiments, the first application can also display order information, payment results, risk warnings, authorization records for obtaining the payment token, etc., to the user.

[0291] Server 200 can be a server for a payment application. In this embodiment, server 200 can receive registration information from a first application and a shopping application, and establish an agency relationship between the first application and the shopping application, meaning that the first application can act as an agent for the shopping application to complete order payment on behalf of the shopping application. Server 200 can also receive authorization requests sent by the first application, generate a payment token, and return the payment token to the first application on the electronic device 100. Server 200 can receive payment requests from the first application, complete order payment according to the payment token included in the payment request, and return the payment result to the first application and the shopping application. In some embodiments, server 200 can also perform risk control and risk verification to ensure the security of payment transactions.

[0292] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the payment method provided in this application.

[0293] This application also provides a computer program product that, when run, can implement the payment method provided in this application.

[0294] This application also provides a chip system, which includes a processor coupled to a memory. The processor executes a computer program stored in the memory to implement the payment method provided in this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0295] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0296] The terms "first" and "second" used in the embodiments of this application are for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0297] The above detailed embodiments further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. A payment method, characterized in that, Applied to an electronic device, the electronic device having a first application, a first shopping application, and a first payment application installed, the method includes: The first application registers on the server of the first payment application and obtains agency qualifications, which include acting as an agent for users to make payments and acting as an agent for shopping applications to collect payments. The first application is a voice assistant application. The first shopping application registers on the server of the first payment application; The first application and the first shopping application establish an agency relationship on the server of the first payment application, and the agency relationship includes the first application acting as an agent for the first shopping application to collect payments; The first application sends an authorization request to the server of the first payment application, and then receives a payment token from the server of the first payment application; After receiving information about a first order from the first shopping application, the first application sends a payment request to the first payment application or the server of the first payment application to request payment for the first order. The payment request includes a payment token corresponding to the first payment application, which is obtained by the first application from the server of the first payment application. Complete the payment for the first order.

2. The method as described in claim 1, characterized in that, Before the first application receives information about the first order from the first shopping application, the method further includes: The electronic device receives a first user instruction through the first application, and the first user instruction is used to purchase a first product. The electronic device, through the first application, responds to the first user's instruction and sends an order request to the first shopping application. The order request is used to request the purchase of the first product, and the order request includes the identifier of the first product. The electronic device generates information for a first order in response to the order request through the first shopping application. The first order is used to purchase the first product, and the information for the first order includes the amount of the first order.

3. The method as described in claim 2, characterized in that, After receiving information about the first order from the first shopping application, the first application sends a payment request to the first payment application or the server of the first payment application, specifically including: When the first user instruction is used to purchase the first product immediately, after receiving the first order information from the first shopping application, the first application sends a payment request to the first payment application. When the first user instruction is used to purchase the first product at a set time, the first application receives the first order information from the first shopping application and sends a payment request to the server of the first payment application.

4. The method according to any one of claims 1-3, characterized in that, The first application sends an authorization request to the server of the first payment application, and then receives a payment token from the server of the first payment application, specifically including: The electronic device displays a first user interface through the first payment application, and the first user interface is used to prompt the user to enter authentication information. The electronic device receives first authentication information in the first user interface; The electronic device receives a verification result from the first payment application through the first application, and the verification result indicates that the first identity verification information has been verified. The electronic device sends a second authorization request to the server of the first payment application through the first application, the second authorization request being used to request a payment token; The electronic device receives the payment token from the server of the first payment application through the first application.

5. The method as described in claim 4, characterized in that, Before the electronic device displays the first user interface through the first payment application, it further includes: The electronic device sends a first authorization request to the server of the first payment application through the first application; The electronic device receives a first authorization identifier from the server of the first payment application through the first application.

6. The method as described in claim 5, characterized in that, The payment token includes a first payment token, which is obtained by the electronic device through the first application before receiving the first user instruction, and the first payment token corresponds to the first authorized amount; Before sending the payment request, the following is also included: If the first application detects that the amount of the first order is less than the first authorized amount, then the payment request includes the first payment token.

7. The method as described in claim 6, characterized in that, The payment token includes a second payment token, which is obtained after receiving the first user instruction through the first application; Before sending the payment request, the following is also included: If the first application detects that the amount of the first order is greater than the first authorized amount, or if the first user instruction includes a preset amount, then the payment request includes the second payment token, and the second authorized amount corresponding to the second payment token is the amount of the first order or the preset amount.

8. The method as described in claim 7, characterized in that, The first payment token expires after the first authorization period ends.

9. The method as described in claim 7 or 8, characterized in that, The second payment token expires after it has been used a preset number of times or after the second authorization period has ended.

10. The method as described in claim 9, characterized in that, The method further includes: The electronic device receives instructions from a third user through the first application; In response to the third user instruction, the electronic device displays one or more of the following through the first application: the authorization time, authorization validity period, authorization amount, and corresponding payment application of the payment token.

11. The method as described in claim 10, characterized in that, After the first application receives information about the first order from the first shopping application, the process also includes: The electronic device displays information about the first order through the first application.

12. The method as described in claim 10 or 11, characterized in that, After the payment for the first order is completed, the following is also included: The electronic device outputs a first prompt message through the first application, which is used to notify the user that the payment for the first order has been completed.

13. The method as described in claim 12, characterized in that, Before completing the payment for the first order, the following is also included: The electronic device outputs a second prompt message through the first payment application, which is used to prompt the user to perform a risk verification.

14. The method as described in claim 13, characterized in that, Following the sending of the payment request, the following is also included: The electronic device receives a fourth user instruction, which is used to confirm payment for the first order.

15. An electronic device, characterized in that, The electronic device is equipped with a first application, a first shopping application, and a first payment application. The electronic device also includes a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the steps of the method according to any one of claims 1-14.

16. A communication system, comprising: An electronic device and a server, wherein the electronic device is the electronic device according to any one of claims 1-14; and the server is the server according to any one of claims 1-14.

17. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the steps of the method described in any one of claims 1-14.

18. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1-14.

19. A chip system, characterized in that, The chip system includes one or more processors, which are configured to invoke computer instructions to perform the method as described in any one of claims 1-14.

Citation Information

Patent Citations

  • Voice payment method and device, electronic equipment and storage medium

    CN111784325A

  • Electronic system and method for enabling payment of a good or service by means of voice commands

    US20230259928A1