WO-2026092206-A1 - SMART WATCH AGGREGATION CODE SERVICE PROCESSING

WO2026092206A1WO 2026092206 A1WO2026092206 A1WO 2026092206A1WO-2026092206-A1

Abstract

Disclosed in embodiments of the present description is a smart watch aggregation code service processing solution, comprising: an application server receiving a service trigger instruction that is sent by a smart watch end when scanning an aggregation code displayed by a target merchant; on the basis of the service trigger instruction, sending a merchant information query request to an aggregation code service provider by calling a first SPI, such that the smart watch end obtains information of the target merchant; receiving a service execution request sent by the smart watch end on the basis of the information of the target merchant; on the basis of the service execution request, sending a corresponding merchant service order creation request to the aggregation code service provider by calling a second SPI, such that the aggregation code service provider places a corresponding order on an open platform corresponding to the application server, wherein the first SPI and the second SPI are defined by an application service provider to which the application server belongs, and are implemented by the aggregation code service provider; and receiving a merchant service order generated and returned by the open platform in response to the placement of the order, and on the basis of the merchant service order, advancing service processing to completion.

Inventors

RUAN, Xuecong
SHEN, JUNQIANG
FAN, Zean
YANG, Yuelong

Assignees

支付宝(杭州)数字服务技术有限公司

Dates

Publication Date: 20260507
Application Date: 20251020
Priority Date: 20241104

Claims (20)

A method for processing aggregated code services on a smartwatch, applied to an application server, the method comprising: Receive business trigger commands sent by the smartwatch by scanning the aggregation code displayed by the target merchant; According to the business triggering instruction, a merchant information query request is sent to the aggregation code service provider by calling the first SPI interface, so that the smart watch can obtain the target merchant information queried by the aggregation code service provider; Receive the business execution request sent by the smartwatch based on the target merchant's information; According to the business execution request, the corresponding merchant business order creation request is sent to the aggregation code service provider by calling the second SPI interface, so that the aggregation code service provider places the corresponding order to the open platform of the application server. The first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider. The system receives the merchant business order generated and returned by the open platform in response to the order, and proceeds with the business processing according to the merchant business order.
The method as described in claim 1, wherein sending a merchant information query request to the aggregation code service provider so that the smartwatch obtains the target merchant information queried by the aggregation code service provider, specifically includes: A merchant information query request carrying the code value of the aggregation code and the identifier of the smartwatch is sent to the aggregation code service provider, so that the aggregation code service provider can query the information of the target merchant based on the code value of the aggregation code, and return the information of the target merchant to the smartwatch based on the identifier of the smartwatch.
The method as described in claim 1, prior to sending a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business trigger instruction, the method further includes: Based on the business trigger instruction, determine whether the smartwatch supports H5 containers, and confirm that the result of the determination is no.
The method as described in claim 1, wherein receiving the business execution request sent by the smartwatch based on the target merchant's information specifically includes: Receive the business execution request sent by the smartwatch in response to the confirmation operation performed on the confirmation interface; The confirmation interface is not a page within the H5 container.
As described in claim 4, the confirmation interface is an interface generated locally by the smartwatch based on the information of the target merchant, rather than a page obtained from the aggregation code service provider or the application server.
As described in claim 4 or 5, the first SPI interface defines a dial theme feature parameter, which is used by the aggregation code service provider to assign a value based on the queried merchant information. The information of the target merchant is represented by the assigned dial theme feature parameter and returned to the smartwatch through the first SPI interface. The process of receiving the business execution request sent by the smartwatch based on the target merchant's information specifically includes: The system receives a business execution request sent by the smartwatch in response to a confirmation operation performed on a temporary watch face theme interface, which serves as the confirmation interface. The temporary watch face theme interface is generated based on the assigned watch face theme feature parameters and is automatically switched from the default watch face theme interface.
The method as described in claim 6, after the merchant business order processing is completed, further includes: Send a command to the smartwatch to restore the watch face theme, so that the smartwatch switches back from the temporary watch face theme to the default watch face theme.
The method described in claim 1, wherein the open platform is a platform provided by the application service provider for placing orders by the aggregation code service provider or merchant, and the open platform and the application server are different entities.
The method as described in claim 1, wherein the application server includes a payment server, the application service provider includes a payment service provider, the business execution request includes a payment request, and the merchant business order includes a merchant cash register order.
A method for processing aggregated code services on a smartwatch, applied to a smartwatch, the method comprising: By scanning the aggregation code displayed by the target merchant, a business triggering instruction is sent to the application server, so that the application server, according to the business triggering instruction, sends a merchant information query request to the aggregation code service provider by calling the first SPI interface; The system obtains the target merchant information queried by the aggregation code service provider and sends a business execution request to the application server based on the target merchant information. The application server then, based on the business execution request, sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface, receives the merchant business order, and completes the business processing according to the merchant business order. The merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing an order with the corresponding open platform of the application server. The first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider.
A smartwatch-based QR code processing device, used in a payment server, the device comprising: The trigger receiving module receives business trigger commands sent by the smartwatch by scanning the aggregation code displayed by the target merchant; The first calling module, according to the business triggering instruction, sends a merchant information query request to the aggregation code service provider by calling the first SPI interface, so that the smart watch can obtain the target merchant information queried by the aggregation code service provider; The execution receiving module receives a business execution request sent by the smartwatch based on the information of the target merchant. The second calling module, based on the business execution request, sends a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface, so that the aggregation code service provider places an order with the open platform corresponding to the application server. The first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider. The business promotion module receives the merchant business order generated and returned by the open platform in response to the order, and promotes the business processing process to completion according to the merchant business order.
The apparatus of claim 11, wherein the first calling module sends a merchant information query request carrying the code value of the aggregation code and the identifier of the smartwatch to the aggregation code service provider, so that the aggregation code service provider can query the information of the target merchant based on the code value of the aggregation code, and return the information of the target merchant to the smartwatch based on the identifier of the smartwatch.
The apparatus of claim 11, wherein before the first calling module sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business triggering instruction, the first calling module determines whether the smartwatch supports the H5 container according to the business triggering instruction, and determines that the result of the determination is no.
The apparatus of claim 11, wherein the execution receiving module receives a business execution request sent by the smartwatch in response to a confirmation operation performed on the confirmation interface; The confirmation interface is not a page within an H5 container.
The device as described in claim 14, wherein the confirmation interface is an interface generated locally by the smartwatch based on the information of the target merchant, rather than a page obtained from the aggregation code service provider or the application server.
The apparatus as described in claim 14 or 15, wherein the first SPI interface defines a dial theme feature parameter, the dial theme feature parameter being used by the aggregation code service provider to assign a value based on the queried merchant information, and the information of the target merchant is represented by the assigned dial theme feature parameter, and returned to the smartwatch through the first SPI interface; The execution receiving module receives a business execution request sent by the smartwatch in response to a confirmation operation performed on a temporary watch face theme interface, which serves as the confirmation interface. The temporary watch face theme interface is generated based on the assigned watch face theme feature parameters and is automatically switched from the default watch face theme interface.
The device as described in claim 16, wherein after the merchant business order processing is completed, the business promotion module sends a watch face theme interface restoration command to the smartwatch, so that the smartwatch switches back from the temporary watch face theme interface to the default watch face theme interface.
The apparatus as described in claim 11, wherein the open platform is a platform provided by the application service provider for placing orders by the aggregation code service provider or merchant, and the open platform and the application server are different entities.
The apparatus of claim 11, wherein the application server includes a payment server, the application service provider includes a payment service provider, the business execution request includes a payment request, and the merchant business order includes a merchant cash register order.
A smartwatch aggregation code service processing device, applied to a smartwatch, the device comprising: The scanning trigger module sends a business trigger instruction to the application server by scanning the aggregation code displayed by the target merchant, so that the application server sends a merchant information query request to the aggregation code service provider by calling the first SPI interface according to the business trigger instruction. The execution request module obtains the target merchant information queried by the aggregation code service provider, and sends a business execution request to the application server based on the target merchant information. This allows the application server to send a corresponding merchant business order creation request to the aggregation code service provider by calling the second SPI interface, and to receive the merchant business order. The application server then proceeds with the business processing based on the merchant business order. The merchant business order is generated and returned to the aggregation code service provider by the aggregation code service provider responding to the business order creation request and placing an order with the corresponding open platform of the application server. The first SPI interface and the second SPI interface are defined by the application service provider to which the application server belongs, but are implemented by the aggregation code service provider.

Description

Smartwatch aggregation code business processing Technical Field This manual relates to the field of payment technology, and in particular to methods, devices, and equipment for processing smartwatch aggregated code transactions. Background Technology With the development of internet technology and the widespread use of smartphones, more and more businesses can be conducted through smartphone applications, bringing great convenience to people's lives. QR codes are now widely used in payment and other business sectors. Users may use different payment service providers' QR code payment services in their daily lives, resulting in different QR codes for payment. Users need to use the correct mapping between these providers' QR codes on their devices (usually the app client) to scan that provider's QR code to make a payment. Scanning a different provider's QR code with the same app may result in payment failure. Therefore, to provide convenience and error tolerance for users, aggregated QR codes have emerged. These aggregate QR code services from two or more different payment service providers. Merchants can generate their own aggregated QR codes for users to use for payment. Users can scan these aggregated QR codes using any of the payment service providers' apps to make a payment. In one current QR code payment solution, when a payment service provider's application scans the merchant's QR code on a smartphone, the merchant's QR code H5 page will open in the application's H5 container. Users can then place orders and make payments on the QR code H5 page. However, the above-mentioned aggregated code payment solution has problems on smartwatches. Due to the limitations of the smartwatch operating system, it is often impossible to implement in an H5 container environment, making it difficult to use this solution to realize aggregated code payment on smartwatches. Similar problems may exist for other aggregated code services on smartwatches. Therefore, a more suitable solution for processing aggregated code business is needed for smartwatches. Summary of the Invention This specification provides one or more embodiments of a method, apparatus, and device for processing aggregated code services on smartwatches, in order to solve the following technical problem: the need for an aggregated code service processing solution more suitable for smartwatches. To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows. This specification provides one or more embodiments of a smartwatch aggregation code business processing method applied to a payment server. The method includes: receiving a business trigger instruction sent by the smartwatch terminal through scanning an aggregation code displayed by a target merchant; according to the business trigger instruction, sending a merchant information query request to an aggregation code service provider by calling a first SPI interface (Service Provider Interface), so that the smartwatch terminal obtains the target merchant information queried by the aggregation code service provider; receiving a business execution request sent by the smartwatch terminal based on the target merchant information; according to the business execution request, sending a corresponding merchant business order creation request to the aggregation code service provider by calling a second SPI interface, so that the aggregation code service provider places a corresponding order with the open platform corresponding to the application server, wherein the first SPI interface and the second SPI interface are interfaces defined by the application service provider to which the application server belongs, but implemented by the aggregation code service provider; receiving a merchant business order generated and returned by the open platform in response to the order, and advancing the business processing process according to the merchant business order. This specification provides another method for processing aggregated code services on a smartwatch, applied to a smartwatch. The method includes: scanning an aggregated code displayed by a target merchant and sending a service trigger instruction to an application server, so that the application server, according to the service trigger instruction, sends a merchant information query request to an aggregated code service provider by calling a first SPI interface; obtaining the target merchant information queried by the aggregated code service provider, and sending a service execution request to the application server based on the target merchant information, so that the application server, according to the service execution request, sends a corresponding merchant business order creation request to the aggregated code service provider by calling a second SPI interface; receiving the merchant business order; and advancing the business processing process according to the merchant business order. The merchant b