Service processing method and apparatus, device, computer-readable storage medium, and computer program product

Abstract

Embodiments of the present application provide a service processing method and apparatus, a device, a computer-readable storage medium, and a computer program product. The method comprises: in response to a configuration operation of a first subject for a palm-scanning payment service, receiving first palm information for the palm-scanning payment service; displaying at least one electronic payment account of the first subject; and in response to a selection operation for the at least one electronic payment account, configuring the selected first electronic payment account to be an electronic payment account associated with the first palm information, wherein when the palm-scanning payment service of the first palm information is used, the configured first electronic payment account associated with the first palm information is used to perform payment processing.

Description

Service processing methods, apparatus, equipment, computer-readable storage media, and computer program products

[0001] Cross-reference to related applications

[0002] This application is based on and claims priority to Chinese Patent Application No. 202411440576.X, filed on October 14, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of computer technology, and in particular to a service processing method, apparatus, device, computer-readable storage medium, and computer program product. Background Technology

[0004] With the rapid development of computer and artificial intelligence technologies, electronic payment has brought great convenience to people's lifestyles, and payment methods have become more diversified. Currently, biometric payment methods have made new progress, supporting not only facial recognition payment but also palm payment. Palm payment, as a payment method that places greater emphasis on security and privacy, is widely used in various payment scenarios. Users can make electronic payments through biometric recognition devices (such as palm payment devices) at offline stores, making it convenient for users without their own payment devices to complete payments, thus improving payment convenience. However, in palm payment services, users have to configure their payment accounts through specialized configuration equipment and specific platforms, which obviously has significant limitations. This not only wastes a lot of configuration resources for palm payment services but also leads to a lack of flexibility and convenience in palm payment scenarios.

[0005] In summary, there is currently no effective technical solution for how to expand the configuration method of the mobile payment service in a resource-efficient manner and improve the configuration efficiency of the mobile payment service. Summary of the Invention

[0006] This application provides a service processing method, apparatus, device, computer-readable storage medium, and computer program product, which can improve the configuration efficiency of the palm-swipe payment service in the palm-swipe payment scenario.

[0007] This application provides a service processing method executed by a first terminal device. The method includes: receiving first palm information for the palm payment service in response to a configuration operation of a first object for the palm payment service; displaying at least one electronic payment account of the first object; and configuring the selected first electronic payment account as an electronic payment account associated with the first palm information in response to a selection operation of the at least one electronic payment account; wherein, when using the palm payment service of the first palm information, the configured first electronic payment account associated with the first palm information is used for payment processing.

[0008] This application provides a service processing apparatus, comprising: a first transceiver unit configured to receive first palm information for a palm payment service in response to a configuration operation of a first object for a palm payment service; a first display unit configured to display at least one electronic payment account of the first object; and a configuration unit configured to configure the selected first electronic payment account as an electronic payment account associated with the first palm information in response to a selection operation of the at least one electronic payment account; wherein, when using the palm payment service of the first palm information, the payment is processed using the configured first electronic payment account associated with the first palm information.

[0009] This application provides a first terminal device, which includes: a memory for storing computer-executable instructions or computer programs; and a processor for executing the computer-executable instructions or computer programs stored in the memory to implement the above-described service processing method.

[0010] This application provides a service processing method executed by a second terminal device. The method includes: in response to a request operation for a palm payment service, receiving first palm information for the palm payment service; displaying a first electronic payment account configured and associated with the first palm information; and performing payment processing using the first electronic payment account.

[0011] This application provides a service processing apparatus, which includes: a second transceiver unit configured to receive first palm information for the palm payment service in response to a request operation for the palm payment service; a second display unit configured to display a first electronic payment account configured to be associated with the first palm information; and a payment unit configured to perform payment processing using the first electronic payment account.

[0012] This application provides a second terminal device, which includes: a memory for storing computer-executable instructions or computer programs; and a processor for executing the computer-executable instructions or computer programs stored in the memory to implement the above-described service processing method.

[0013] This application provides a computer-readable storage medium storing computer-executable instructions or computer programs. When these computer-executable instructions or computer programs are loaded and executed by a processor, the above-described service processing method is implemented.

[0014] This application provides a computer program product, which includes a computer program or computer executable instructions. When the computer program or computer executable instructions are executed by a processor, the above-described service processing method is implemented.

[0015] In this embodiment, by configuring a first electronic payment account as an electronic payment account associated with first palm information, the first electronic payment account can be used for the palm payment service. Thus, during the use of the palm payment service, upon receiving the first palm information, the configured first electronic payment account associated with the first palm information can be used for payment processing. Following the above process, based on the configuration operation of the first object, the first object can configure one or more electronic payment accounts associated with the first palm information, and these electronic payment accounts can be used for the palm payment service. The configuration of electronic payment accounts is no longer limited to professional configuration equipment and specific configuration platforms, nor is it limited to the type of entity possessing a physical payment account. This not only saves configuration resources when configuring the palm payment service but also enhances the diversity of payment accounts for the palm payment service and further improves the configuration efficiency for the palm payment service in the palm payment scenario. Furthermore, since the palm payment service can be implemented in various payment scenarios after configuration, and only the palm information of the object needs to be provided when using the palm payment service, the associated electronic payment account can be flexibly selected, thereby effectively improving the flexibility and convenience of payment in the palm payment scenario. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 is an architecture diagram of a service processing system provided in an embodiment of this application;

[0018] Figure 2 is a flowchart illustrating a service processing method provided in an embodiment of this application;

[0019] Figure 3a is a schematic diagram of a display service startup interface provided in an embodiment of this application;

[0020] Figure 3b is a schematic diagram showing an object identifier of a first object according to an embodiment of this application;

[0021] Figure 3c is a schematic diagram of an account login interface provided in an embodiment of this application;

[0022] Figure 3d is a schematic diagram of receiving first palm information according to an embodiment of this application;

[0023] Figure 3e is a schematic diagram of an invitation to input palm information provided in an embodiment of this application;

[0024] Figure 3f is a schematic diagram showing at least one electronic payment account of a first object according to an embodiment of this application;

[0025] Figure 3g is a schematic diagram of configuring an electronic payment account according to an embodiment of this application;

[0026] Figure 3h is a schematic diagram of an output account association invitation provided in an embodiment of this application;

[0027] Figure 4 is a flowchart illustrating another service processing method provided in an embodiment of this application;

[0028] Figure 5a is a schematic diagram of an account authorization prompt message provided in an embodiment of this application;

[0029] Figure 5b is a schematic diagram of an authentication interface provided in an embodiment of this application;

[0030] Figure 5c is a schematic diagram of another account authorization prompt information provided in an embodiment of this application;

[0031] Figure 5d is a schematic diagram of receiving authentication information in an authentication interface according to an embodiment of this application;

[0032] Figure 5e is a schematic diagram of setting a palm mark according to an embodiment of this application;

[0033] Figure 5f is a schematic diagram of displaying N palm information provided in an embodiment of this application;

[0034] Figure 6 is a flowchart illustrating another service processing method provided in an embodiment of this application;

[0035] Figure 7a is a schematic diagram of adding a second electronic payment account according to an embodiment of this application;

[0036] Figure 7b is a schematic diagram showing M electronic payment accounts according to an embodiment of this application;

[0037] Figure 7c is a schematic diagram of deleting an electronic payment account according to an embodiment of this application;

[0038] Figure 7d is a schematic diagram illustrating the setting of payment priority for an electronic payment account according to an embodiment of this application;

[0039] Figure 7e is a schematic diagram illustrating the setting of payment limits for an electronic payment account according to an embodiment of this application;

[0040] Figure 7f is a schematic diagram of setting payment permissions for an electronic payment account according to an embodiment of this application;

[0041] Figure 7g is a schematic diagram showing a bill under an electronic payment account according to an embodiment of this application;

[0042] Figure 7h is a schematic diagram of the configuration process of a palm payment service provided in an embodiment of this application;

[0043] Figure 8a is a schematic diagram of the configuration process of another palm payment service provided in an embodiment of this application;

[0044] Figure 8b is a schematic diagram of a process for inputting palm prints according to an embodiment of this application;

[0045] Figure 8c is a schematic diagram of a process for linking an electronic payment account according to an embodiment of this application;

[0046] Figure 8d is a flowchart illustrating an object identifier associated with a first object according to an embodiment of this application;

[0047] Figure 9 is a flowchart illustrating another service processing method provided in an embodiment of this application;

[0048] Figure 10a is a schematic diagram of receiving first palm information for palm payment service provided in an embodiment of this application;

[0049] Figure 10b is a schematic diagram showing a configured electronic payment account provided in an embodiment of this application;

[0050] Figure 10c is a schematic diagram of a display auxiliary verification interface provided in an embodiment of this application;

[0051] Figure 10d is a schematic diagram of an output payment result provided in an embodiment of this application;

[0052] Figure 10e is a schematic diagram of the usage process of a palm payment service provided in an embodiment of this application;

[0053] Figure 11a is a flowchart of an offline palm-swipe payment method provided in an embodiment of this application;

[0054] Figure 11b is a schematic diagram of a retrieval and identification process provided in an embodiment of this application;

[0055] Figure 11c is a schematic diagram of a return control code verification process provided in an embodiment of this application;

[0056] Figure 12a is a schematic diagram of a service processing device provided in an embodiment of this application;

[0057] Figure 12b is a schematic diagram of another service processing device provided in an embodiment of this application;

[0058] Figure 13 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0059] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0060] To better understand the technical solutions provided in the embodiments of this application, the key terms involved in the embodiments of this application will be introduced first:

[0061] (1) Palm information: refers to image data related to the user's palm collected through biometric identification technology, including but not limited to palm print images, palm vein images, etc. These images can be used for user identification and as the basis for payment verification.

[0062] (2) Palm Payment Service: Palm payment service is a payment service that uses palm information instead of traditional payment passwords. It collects the user's palm print or palm vein image (collectively referred to as palm information) and binds it to the user's electronic payment account. Users can complete payments by placing their palm on a recognition device without carrying a mobile phone or bank card. In this embodiment, the palm payment service may include a configuration process and a usage process. Illustratively, for a specific object (such as a user), the palm payment service needs to be configured before use. The configuration process mainly includes entering palm information and associating an electronic payment account. The usage process is based on the palm information entered during the configuration process and uses the corresponding electronic payment account for payment. The configuration and usage processes can be executed on different terminal devices, such as configuring on a mobile phone and using it on a palm payment device. The usage process of the palm payment service can be simply referred to as palm payment. Palm payment requires the use of palm recognition technology to identify the payment object. Palm recognition technology is a biometric identification technology that uses one or both palm prints and palm veins for identification. Palm print recognition identifies an individual by recognizing an image of the palm from the fingertips to the wrist. Vein recognition identifies an individual by recognizing and analyzing the patterns of veins. This technology uses harmless infrared light to illuminate a living body; the light penetrates the skin and reaches the blood vessels, where it is absorbed by the hemoglobin to form a vascular image. This image is then compared and matched with reference images in a database to achieve authentication and identification. In the configuration of palm payment services, specialized palm-scanning devices can be used to collect palm prints and palm veins as dual-factor features. During palm payment, the reading of both palm prints and palm veins accurately identifies the recipient, providing dual security protection.

[0063] (3) Payment Account: A payment account is an account that enables digital asset transfers (including receiving, paying, and transferring funds), payment settlements, and other services. Payment accounts can be opened by banks or other payment service providers (such as payment institutions and third-party payment platforms), exist in digital form, and correspond to the identity of the recipient. Classified by account type, payment accounts can include bank accounts (traditional savings accounts, etc.), electronic payment accounts, and special accounts (accounts used for specific purposes, such as pension accounts). Among these, an electronic payment account is an account used for receiving and paying digital assets via the internet. An electronic payment account is a virtual account without a specific physical form and is not directly associated with a bank account. Electronic payment accounts can be provided by third-party payment service providers or are part of online services provided by banks. Electronic payment accounts allow online transactions, such as shopping, transferring funds, and paying bills, without the need for traditional physical asset exchanges and provide convenient mobile payment services.

[0064] (4) First terminal device: is a smart device used by the user, such as a smartphone or tablet computer, used to input palm information, configure electronic payment account, and manage the relevant settings of palm payment service.

[0065] (5) Second terminal device: It is a dedicated palm recognition terminal deployed by offline merchants, which is used to read palm information when users pay and call the bound electronic payment account to complete the transaction deduction.

[0066] (6) Palm Scanning on Device: This refers to the process of fingerprint or palmprint recognition on a device. This technology is commonly used for security verification, such as unlocking mobile phones and payment authentication. By scanning the palmprint of an object (such as a user), the device can confirm the identity, thereby improving security. Specific operations may include placing the palm on a sensor, where the system captures and analyzes the palmprint features. Based on the comparison of the palmprint features with features in a feature database, the object's identity can be determined.

[0067] (7) Payment processing: refers to the process of deducting the corresponding amount from the bound electronic payment account based on the identified user identity information to complete the payment behavior.

[0068] Based on the above description of key terms, embodiments of this application propose a service processing method, apparatus, device, computer-readable storage medium, and computer program product. In this service processing method, a first terminal device can receive first palm information for the palm payment service in response to a configuration operation by a first object for the palm payment service. Next, at least one electronic payment account of the first object is displayed, with the first object being the owner of each electronic payment account. Then, in response to a selection operation for the at least one electronic payment account, the selected first electronic payment account is configured as an electronic payment account associated with the first palm information. Thus, the first electronic payment account can be used for the palm payment service, and during the use of the palm payment service, payment processing can be performed using the configured first electronic payment account associated with the first palm information upon receiving the first palm information. According to the above process, based on the configuration operation of the first object, the first object can configure one or more electronic payment accounts associated with the first palm information, and these electronic payment accounts can be used for the palm payment service. Therefore, the configuration of electronic payment accounts is no longer limited to the type of physical payment account, and the diversity of payment accounts used for palm payment services can be increased. In addition, palm payment services support access to various payment media (i.e., not only physical payment accounts, such as bank accounts, but also electronic payment accounts), expanding payment channels. Furthermore, if multiple electronic payment accounts are configured, when using palm payment services, only the palm information of the recipient needs to be provided to flexibly select the associated electronic payment account, effectively improving the flexibility and convenience of payments in palm payment scenarios.

[0069] It is understood that in the embodiments of this application, the term "at least one" refers to one or more, and "multiple" means two or more; for example, "at least one electronic payment account" refers to one, two or more electronic payment accounts. The terms "first," "second," etc., are used to distinguish identical or similar items with essentially the same function. It should be understood that there is no logical or temporal dependency between "first," "second," and "nth," nor is there any limitation on the quantity or execution order.

[0070] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0071] The architecture of the service processing system provided in the embodiments of this application will now be described with reference to the accompanying drawings.

[0072] Please refer to Figure 1, which is an architecture diagram of a service processing system provided in an embodiment of this application. As shown in Figure 1, the service processing system includes at least one terminal device (including a first terminal device 101a and a second terminal device 101b), a server 102, and a database 103; each terminal device can establish a communication connection with the server 102 via wired or wireless means, and the database 103 can establish a communication connection with the server 102 via wired or wireless means.

[0073] Terminal devices include, but are not limited to: smartphones, tablets, smart wearable devices, smart voice interaction devices, smart home appliances, personal computers, in-vehicle terminals, smart cameras, etc., and this application does not limit their use; the number of terminal devices is also not limited. Server 102 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms, but is not limited to these; the number of servers is also not limited. Based on deployment location, database 103 can be a local database of server 102 or a cloud database capable of establishing a connection with server 102. Based on attributes, database 103 can be a public database, i.e., a database open to all computer devices; or it can be a private database, i.e., a database open only to a specific server (such as server 102). The database 103 can be used to classify and store palm information collected by different terminal devices. For example, palm information collected by the first terminal device and palm information collected by the second terminal device can be classified and stored. Palm information, as a feature, can be used to compare and confirm the identity of the object.

[0074] The following explanation uses a terminal device comprising a first terminal device 101a and a second terminal device 101b as an example. The first terminal device 101a is used to execute the configuration process for the palm payment service, and the second terminal device 101b is used to execute the usage process for the palm payment service. The general flow of the service processing method executed by the first terminal device 101a is as follows: First, in response to the configuration operation of the first object for the palm payment service, the first terminal device 101a receives first palm information for the palm payment service. In a specific implementation, if the first object initiates the palm payment service, the first terminal device 101a can capture a palm image, thereby receiving the first palm information for the palm payment service, which is, for example, the palm information of the first object. Then, the first terminal device 101a displays at least one electronic payment account of the first object. For example, it can display one electronic payment account of the first object, or it can display multiple electronic payment accounts, each owned by the first object. If multiple electronic payment accounts are displayed, then the different electronic payment accounts can be provided by different payment platforms. For example, if the palm payment service is provided by a first application, the payment platform corresponding to each displayed electronic payment account is a payment platform that is allowed to access the first application. Finally, in response to the selection operation of at least one electronic payment account, the first terminal device 101a configures the selected first electronic payment account as the electronic payment account associated with the first palm information. In a specific implementation, if the first object selects an electronic payment account from at least one electronic payment account (e.g., two electronic payment accounts), then the selected electronic payment account is the first electronic payment account and can be configured as the electronic payment account associated with the first palm information.

[0075] In this embodiment of the application, after the first palm information is received by the first terminal device, if the object skips the configuration step of the first electronic payment account (for example, in the step of configuring the electronic payment account, the "determine later" option is selected) or the first electronic payment account associated with the first palm information has already been configured, the electronic payment account associated with the first palm information can still be configured. For example, in response to the addition operation of the electronic payment account, the first terminal device can trigger the execution of the step of displaying at least one electronic payment account of the first object, and configure the electronic payment account associated with the palm information for the palm payment service; the first palm information is associated with one or more electronic payment accounts.

[0076] In this embodiment of the application, if the first palm information has already been associated with the first electronic payment account, the first terminal device can still respond to the palm information addition operation, receive the second palm information for palm payment service, and based on the addition of the second palm information, the first terminal device can automatically associate the second palm information with the existing first electronic payment account; the first electronic payment account supports association with one or more palm information.

[0077] The general flow of the service processing method executed by the second terminal device 101b is as follows: First, in response to a request for the palm payment service, the second terminal device 101b receives first palm information for the palm payment service. Then, the second terminal device 101b displays a first electronic payment account configured and associated with the first palm information, the owner of which is the first object. Finally, the second terminal device 101b uses the first electronic payment account for payment processing. It can be seen that in the palm payment scenario, based on the receipt of the first palm information, the second terminal device can use the configured associated electronic payment account for payment. In this embodiment, if the first palm information is also associated with a second electronic payment account, the object can choose one of the electronic payment accounts for payment processing, thereby improving payment flexibility. For example, if the payment limit of a certain payment account is insufficient, another electronic payment account can be selected for payment.

[0078] The service processing system provided in this application embodiment allows a first terminal device to execute a configuration process for a palm payment service. In response to the configuration operation for the palm payment service, the first terminal device receives first palm information for the palm payment service, displays at least one electronic payment account of a first object, and then, in response to the selection of any one of the at least one electronic payment account, configures the selected first electronic payment account as an electronic payment account associated with the first palm information. Through the configuration of the palm payment service, one or more electronic payment accounts can be associated with the first palm information that can be used for the palm payment service. In the usage process of the palm payment service, a second terminal device can respond to a request operation for the palm payment service, receive the first palm information, and perform payment processing using the first electronic payment account associated with the first palm information. Based on the association between the first palm information and the electronic payment account, palm payment supports more payment methods, improving payment convenience and flexibility.

[0079] The service processing method provided in the embodiments of this application will be described next.

[0080] Please refer to Figure 2, which is a flowchart illustrating a service processing method provided in an embodiment of this application. This service processing method can be executed by a first terminal device (as shown in Figure 1, the first terminal device 101a), and can include the following steps S201 to S203.

[0081] S201, in response to the configuration operation of the first object for the palm payment service, receives first palm information for the palm payment service.

[0082] Here, the first object can refer to the user themselves, meaning the user accesses the service configuration interface of the palm payment service through their primary terminal device (such as a mobile phone) and actively initiates a configuration request. At this time, the palm payment system (which can be the aforementioned service processing system) will guide the first object to complete the palm recognition operation. The palm payment service is a cardless payment method based on biometric identification technology. The first object does not need to carry a mobile phone or bank card; they can complete the payment operation simply by using their palm.

[0083] The first palm information includes the palm information of the first object, which may include palm print and palm vein images. This data will serve as the basis for authenticating the first object. In this embodiment, the palm information of the first object may be collected by a first terminal device. To ensure the quality of collection, the first terminal device may have a built-in dedicated liveness detection sensor to prevent deceptive data entry using prosthetic hands or other non-living hand models.

[0084] The first terminal device can respond to the activation operation of the palm payment service by displaying a service configuration interface for the palm payment service. Then, in response to the login information received in the service configuration interface, it can display data collection guidance information to guide the first object to collect palm information. In response to the data collection operation performed by the first object, the first object's palm information is collected. The configuration operation of the first object for the palm payment service can include this data collection operation. That is, the first terminal device can also prompt the first object to place their palm in a specific posture to ensure the integrity and consistency of the image. In actual implementation, the first object can initiate the palm recording process through a mini-program of an instant messaging application. The first terminal device guides the first object to place their palm on the camera or dedicated sensor of the first terminal device, and the first terminal device completes liveness detection and collects multi-angle palm images. The multi-angle palm images collected through the mini-program will be encrypted and stored, and bound to the first object's identity information, providing a reliable identity verification basis for the subsequent palm payment service.

[0085] The startup operation can be a trigger operation on the startup control displayed on the service startup interface. The swipe payment service is provided by a first application, which can be a mini-program or a third-party application. The first application is a software service product that provides palm information input and swipe usage management, used to provide the swipe payment service. The service startup interface can be provided by the first application. The first terminal device can display the service startup interface in response to the scanning operation of the graphic code of the first application. For example, as shown in the schematic diagram of the service startup interface in Figure 3a, the first terminal device can scan the material code of an offline store or scan the graphic code of the swipe device to display the service startup interface 3100. The service startup interface displays a startup control 3101, and the text content of the startup control 3101 is: "Start a new swipe experience". The first terminal device can also directly respond to the startup operation of the first application (such as searching for and opening a mini-program (a mini-program is a type of application that does not require installation), or opening an application from the mobile phone desktop) to display the service startup interface.

[0086] After the launch control in the service launch interface is triggered, the service configuration interface can be displayed, and the object identifier of the first object can be displayed in the service configuration interface. If the first object has not registered an account in the first application, but the first application is associated with the second application, for example, the first application is a mini-program embedded in the second application, the first terminal device can display the object identifier associated with the second application (such as a mobile phone number). For example, as shown in the schematic diagram of displaying the object identifier of the first object in Figure 3b, when the launch control is clicked, the service configuration interface 3201 can be displayed. The service configuration interface 3201 is displayed above the service launch interface. The service configuration interface displays the object identifier 3202 of the first object. The displayed object identifier includes two mobile phone numbers. Selecting either mobile phone number allows the selected mobile phone number to be used to register an account online in the first application, thereby executing subsequent processes such as recording and associating electronic payment accounts. If the object selects not to allow or selects to use other identifiers, then the account login interface can be displayed, and the mobile phone number can be entered in the account login interface. If the first object has already registered an account in the first application, then after the launch control in the service launch interface is triggered, the service configuration interface displayed is the account login interface, which includes the login information to be entered. For example, as shown in Figure 3c, clicking the start button in the service startup interface can display the account login interface 3301, which includes the account to be entered, such as a phone number; if the first object has not yet entered palm information, the first terminal device can respond to the login information (such as a phone number) entered in the account login interface and display the information collection interface.

[0087] The data collection guidance information can be displayed on the data collection interface, which is completely independent of the service configuration interface; or it can be displayed in a message pop-up that floats on top of the service configuration interface. Data collection operations can include, but are not limited to: triggering operations on the data collection controls in the data collection interface (such as clicking), performing gesture operations in the data collection interface (such as double-clicking or long-pressing), and selecting controls in the message pop-up. Based on the execution of these data collection operations, the first terminal device can receive first palm information for the palm payment service.

[0088] In this embodiment, in response to the acquisition operation performed by the first object, the first terminal device can first display interactive prompt information. This interactive prompt information is used to prompt the first object to adjust the position and movement of its palm. The first terminal device can display palm images of the corresponding actions performed by the first object. The palm images corresponding to one or more actions acquired can be used as first palm information. It is understood that the acquisition of first palm information is a dynamic process. The interactive prompt information displayed in the first terminal device can change dynamically. For example, it can sequentially prompt the first object to perform action 1 (such as opening the palm), action 2 (making a fist), and action 3 (other fixed gestures), and sequentially acquire the images corresponding to the above actions. For example, as shown in the schematic diagram of receiving first palm information in FIG3d, based on the triggering of the acquisition control 3401 of "Start Entry" in the information acquisition interface, interactive prompt information 3402 can be output, the text content of which is: "Please make a fist". It can also display the palm image 3403 captured by the mobile phone camera, and the object can adjust the palm movement (such as making a fist) according to the interactive prompt information.

[0089] The first terminal device can call the shooting module to capture a first palm image (e.g., a left palm image) and identify this first palm image as the first palm information. The first terminal device can collect the first palm information itself, or the first palm information can be collected by a device connected to the first terminal device (e.g., a camera connected to a computer) and then sent to the first terminal device. The first palm information can be the palm information of a first object, or it can be the palm information of other objects that the first object allows to be added, such as the right palm image of a second object.

[0090] In one implementation, the first palm information may include the palm information of a second object. The first terminal device is the terminal device of the first object. The first terminal device can respond to the configuration operation of the first object for the palm payment service and output a palm information entry invitation. This palm information entry invitation can take one or more forms: a text link, a graphic code, etc. A graphic code is an information encoding product that encodes information through specific patterns, colors, or shapes, such as a QR code or barcode. For example, as shown in Figure 3e, clicking the "Invite others to enter palm information" control 3501 can display a text link 3502 for the palm information entry invitation. The first terminal device sends this palm information entry invitation to the second object. The first application provides the palm payment service, and the second object can be an object of the second application, which allows access to the first application. The palm information entry invitation can be sent to the second object via chat messages, email, etc. The second object's terminal device can receive the palm information entry invitation and, in response to the invitation (such as scanning a graphic code or clicking a text link), remotely enter the second object's palm information and return it directly to the first terminal device, or return a graphic code containing the palm information to the first terminal device; the first terminal device can receive the second object's palm information. In this method, even if the second object and the first object are in different locations, the palm information of the second object can be easily obtained based on the sending of the palm information entry invitation, solving the problem of being restricted from entering the palm information of another party because the object whose palm information is being entered and the object performing the configuration operation are in different areas.

[0091] In another implementation, the first palm information includes palm information obtained by identifying a palm information storage medium. The first terminal device can, in response to a configuration operation by a first object for the palm payment service, obtain the palm information storage medium, which stores palm information belonging to either the first or second object. The palm information storage medium includes, but is not limited to, graphic codes, text, numerical values, and audio. For example, before configuring the palm payment service, the first terminal device can receive a graphic code sent by the second object's terminal device and save it locally. This graphic code stores the palm information of the second object. The second object can actively input palm information into its terminal device and generate this graphic code, which is then sent to the first terminal device via appropriate methods (such as conversation messages, SMS, Bluetooth, short-range communication (e.g., "tap-to-pay" communication between terminal devices)). When configuring the palm payment service, the first terminal device, in response to the configuration operation, can directly obtain the graphic code from its local storage space. The first terminal device can identify the palm information storage medium and obtain the palm information stored therein. For example, in response to the scanning operation of the graphic code, the first terminal device recognizes the graphic code and receives the palm information stored in the graphic code. In this way, the input of palm information no longer requires real-time acquisition of palm images, but the palm information can be pre-stored in a corresponding form (such as a graphic code), and the first terminal device can conveniently and efficiently receive the palm information.

[0092] S202, displaying at least one electronic payment account of the first object.

[0093] In one implementation, the owner of each electronic payment account is the first object. The first terminal device displays at least one electronic payment account of the first object in an implementation manner, including any one or more of the following:

[0094] Method 1: Obtain the object identifier of the first object and display at least one electronic payment account corresponding to the object identifier of the first object. The object identifier of the first object includes, but is not limited to: the communication identification code of the first object (such as a mobile phone number), and the object identifier of the first object in the application providing the electronic payment account (such as a user ID). The first terminal device can obtain the object identifier of the first object based on an authorization operation targeting the object identifier. For example, when authorizing a mobile phone number to log in to a mini-program providing the mobile payment service, the authorized mobile phone number can be obtained as the object identifier. The first terminal device can also receive input operations from the first object targeting the object identifier and obtain the input object identifier as the object identifier of the first object. For example, the mobile phone number entered by the first object on the account login interface can be used as the object identifier of the first object.

[0095] Each electronic payment account of the first object corresponds to an object identifier of the first object. This correspondence refers to the binding between the electronic payment account and the object identifier. One object identifier can correspond to one or more electronic payment accounts. For example, a mobile phone number of an object can be bound to three electronic payment accounts, thus allowing at least one electronic payment account to be identified and displayed based on the object identifier. In this method, the first terminal device can accurately and quickly identify the electronic payment account based on the correspondence between the object identifier and the electronic payment account by automatically obtaining the object identifier of the first object.

[0096] Method 2: Receive at least one account information input by a first object and display the electronic payment account indicated by each account information. The account information may include one or more of the following: the account number of the electronic payment account, the account name of the electronic payment account, and the object to which the electronic payment account belongs. Each account information can indicate one electronic payment account, and different account information indicates different electronic payment accounts. The first terminal device can display the electronic payment account indicated by each account information. In this method, based on the account information input by the first object, the display of electronic payment accounts can be flexibly selected, rather than being fixed to displaying the electronic payment account corresponding to the object identifier, thus improving the flexibility of electronic payment account association.

[0097] It should be noted that in step S202, the first terminal device can obtain all available electronic payment accounts of the first object from the authorized third-party payment platform and display them on the interface of the first terminal device. Here, electronic payment accounts refer to accounts opened by the first object on third-party payment platforms such as payment applications and shopping applications, which support online and offline payment operations. Since the first object may have multiple payment accounts, the first terminal device needs to list all available accounts so that the first object can select according to its needs. When displaying these electronic payment accounts, the displayed information may include account name, balance, and whether the account is real-name authenticated. The first object can browse and select accounts by clicking or swiping. In actual implementation, the first terminal device can call the application programming interface (API) of the payment platform to obtain all associated electronic payment accounts under the first object's currently logged-in account and display the associated electronic payment accounts in a list format on the interface. Calling the payment platform's API and displaying the associated electronic payment accounts not only improves the convenience of the first object's operation but also enhances the system's compatibility and scalability.

[0098] In this embodiment, at least one electronic payment account of the first object can be displayed on the payment account configuration interface. Specifically, the first terminal device can display the payment account configuration interface, which shows at least one electronic payment account of the first object. These electronic payment accounts are not configured for use with the swipe payment service, i.e., they are not used for the swipe payment service under the first object's account.

[0099] The swipe payment service is provided by the first application. Each electronic payment account corresponds to a payment method (or payment channel), and each payment method is one that the first application allows to access. When displaying electronic payment accounts, the payment method corresponding to each electronic payment account can be displayed. Based on the selection of the corresponding payment method, the electronic payment account of the first object corresponding to the selected payment method can be displayed, such as the account information of the electronic payment account. For example, as shown in Figure 3f, which displays at least one electronic payment account of the first object, the payment account settings interface 3601 can display multiple currently supported payment methods, such as AA payment and BB electronic payment. Each payment method can correspond to one electronic payment account. For example, after AA payment, identified by payment method 3602, is selected, the account information 3603 of the corresponding electronic payment account can be displayed in the payment account settings interface. For example, the following text can be displayed: "The first application will associate with your payment account (**ge). After the association is completed, you can use the swipe service on offline swipe devices and enjoy a fast and convenient payment experience and service."

[0100] S203, in response to the selection operation of at least one electronic payment account, the selected first electronic payment account is configured as an electronic payment account associated with the first palm information.

[0101] In one implementation, the selection operation of at least one electronic payment account can be used to select one electronic payment account from at least one electronic payment account, and the selected electronic payment account can be referred to as the first electronic payment account. The selection operation includes, but is not limited to: clicking on any electronic payment account, selecting any electronic payment account, preset gesture operation, or operation on physical keys (such as the up and down keys on a physical keyboard).

[0102] During configuration, the first electronic payment account can be authenticated by the payment service provider to which it belongs. For example, if the first electronic payment account is provided by a second application, then the authentication can be performed by the background service of the second application. This authentication is to verify whether the object currently performing the configuration operation is indeed the owner of the first electronic payment account (i.e., the first object), and not another object, to ensure the security of the electronic payment account association. This authentication can be implemented based on the interactive information entered by the first object after selecting the electronic payment account, or it can be directly verified by the background without requiring the first object to perform other interactive operations. When the authentication is successful, an association can be established between the first electronic payment account and the first handheld information. After successful configuration, the first terminal device can also output a configuration success result, which indicates the association between the first electronic payment account and the first handheld information. For example, as shown in the schematic diagram of configuring the first electronic payment account in Figure 3g, after selecting to associate the first electronic payment account, a configuration success result can be output, which is displayed in a separate result interface 3701.

[0103] In this embodiment, based on the association between the first electronic payment account and the first palm information, when using the palm payment service based on the first palm information, the pre-configured first electronic payment account associated with the first palm information can be used for payment processing. For example, when the first object uses palm payment, if the collected information is the first palm information, then the payment can be processed through the first electronic payment account; that is, the corresponding amount of digital assets is transferred from the first electronic payment account and the asset amount of the first electronic payment account is updated. In other words, in this embodiment, the first object selects an account from the electronic payment accounts displayed on the first terminal device as the account to be bound to the previously collected first palm information. This binding relationship means that when the first object uses the palm payment service for offline consumption in the future, the bound first electronic payment account will be automatically called to complete the deduction operation. Payment processing refers to the process of deducting the corresponding amount from the bound first electronic payment account according to the identified first object identity information to complete the payment behavior. In the process of deducting the corresponding amount from the bound first electronic payment account according to the identified first object identity information to complete the payment behavior, communication with the payment platform is involved, including the sending of transaction requests, the receiving and feedback of transaction results, etc. Furthermore, the first terminal device can also support the first user in modifying or changing the bound accounts. For example, the first user can reselect other accounts to bind on the first terminal device, and the first user can also set payment limits, disable the mobile payment service permissions for certain accounts, etc.

[0104] In practice, after the first user selects an account, the first terminal device binds the unique identifier of the selected e-payment account to the user's palm information and uploads this binding relationship to the backend server of the palm payment service for storage. When the user subsequently uses the palm payment service offline, a second terminal device (such as a palm recognition terminal deployed by the merchant) reads the user's palm information, queries the backend system for the corresponding e-payment account, and completes the payment. The entire process eliminates the need for the user to carry a mobile phone, greatly improving the convenience and efficiency of the payment process.

[0105] The service processing method provided in this application embodiment achieves the goal of enabling the first object to complete payment without a card or mobile phone by collecting the palm information of the first object and binding the electronic payment account on the first terminal device. Specifically, the first object enters the palm information on the first terminal device and selects the operation of binding the first electronic payment account. Then, at any merchant where palm-scanning devices are installed, the first object only needs to place its palm on the recognition terminal to complete the palm-scanning payment service. The service processing method provided in this application embodiment not only simplifies the payment process and improves payment efficiency, but also enhances payment security, because each payment relies on the unique biometrics of the first object for verification, making it difficult to copy or forge.

[0106] In some embodiments, when configuring an electronic payment account for the palm payment service, the first terminal device can also respond to an account invitation operation by outputting an account association invitation and sending an account association invitation for the electronic payment account to a second object. The account invitation operation includes, but is not limited to, preset gesture operations and triggering operations on an invitation control. The invitation control can be located in the interface for displaying the electronic payment account of the first object, or in the association method selection interface. The association method selection interface includes a first association method and a second association method. The account invitation operation includes selecting the second association method. Selecting the first association method triggers the display of the electronic payment account of the first object. The account association invitation is used to invite the electronic payment account of the second object to be associated with the first palm information. The first application provides the palm payment service, and the second object can be an object of the second application, which allows access to the first application. If the second object agrees to the invitation, it can return an electronic payment account that is allowed to be associated, and the first terminal device can then associate the invited second object's electronic payment account with the first palm information. For example, as shown in FIG3h, when the control 3801 for associating another person's account is clicked, an account association invitation 3802 can be displayed and sent to the second object. The selection of the second object can be done before or after the account association invitation is sent. For example, after the account association invitation is sent, clicking "send" will display a list of objects, which includes multiple objects from the second application to choose from. Any of the selected objects can be used as the second object.

[0107] In addition, the first terminal device can also receive an account association invitation sent by the second object's terminal device. The account association invitation is used to invite the first object's electronic payment account to be associated with the second object's palm information. In response to the account association invitation, the first terminal device can send the first object's electronic payment account to the second object's terminal device. Thus, the first object's electronic payment account can be configured as an electronic payment account associated with the second object's palm information, that is, an electronic payment account used for the second object's palm payment service.

[0108] In the above embodiments, configuring the electronic payment account for the swipe payment service is no longer limited to selecting the displayed electronic payment account. Instead, it is possible to actively invite other objects to associate their electronic payment accounts or add one's own electronic payment account to the swipe payment service configured by other objects. In this way, when configuring the swipe payment service, the electronic payment accounts of other objects can be obtained, further enhancing the payment channels of swipe payment.

[0109] The service processing method provided in this application, based on the receipt of first palm information for the palm payment service and the selection of an electronic payment account, configures the selected first electronic payment account as an electronic payment account associated with the first palm information. Thus, the first electronic payment account can be used for the palm payment service, allowing payment processing via the configured first electronic payment account associated with the first palm information upon receiving the first palm information. Following the above process, based on the configuration operation of the first object, one or more electronic payment accounts associated with the first palm information can be configured, and these electronic payment accounts can be used for the palm payment service. Therefore, the configuration of payment accounts is no longer limited to the type of physical payment account, increasing the diversity of payment accounts used for the palm payment service. Furthermore, the palm payment service supports access to various payment media, expanding payment channels. When using the palm payment service, only the palm information of the object needs to be provided to flexibly select the associated electronic payment account, effectively improving the flexibility and convenience of payment in the palm payment scenario.

[0110] Please refer to Figure 4, which is a flowchart illustrating another service processing method provided in an embodiment of this application. This service processing method can be executed by a first terminal device (as shown in Figure 1, the first terminal device 101a), and the service processing method may include the following steps S401 to S405.

[0111] S401, in response to the configuration operation of the first object for the palm payment service, receives first palm information for the palm payment service.

[0112] S402, displaying at least one electronic payment account of the first object.

[0113] It should be noted that steps S401 and S402 are the same as steps S201 and S202 above. Please refer to the explanation of steps S201 and S202 for details. They will not be repeated here.

[0114] S403, in response to the selection of at least one electronic payment account, displays an authentication interface.

[0115] The identity verification interface is the interactive interface users enter after selecting a payment account. It further confirms the user's identity and payment permissions. The identity verification interface typically includes elements such as input fields, a verification code area, and biometric prompts. Its design ensures users have legitimate operating permissions. The purpose of the identity verification interface is to enhance system security and prevent unauthorized account binding. Introducing an identity verification process after the user completes account selection effectively prevents accidental or malicious account binding.

[0116] In this embodiment of the application, the implementation of S403 may include the following: in response to the selection operation of at least one electronic payment account, output account authorization prompt information, which is used to prompt the selected first electronic payment account to be authorized; in response to the authorization operation performed on the first electronic payment account, display an identity verification interface.

[0117] In one implementation, account authorization prompt information can be displayed in an authorization prompt interface. For example, in response to the selection of at least one electronic payment account, the first terminal device can display an authorization prompt interface, which includes the account authorization prompt information. The authorization prompt interface also includes an authorization confirmation control, and the authorization operation can be a trigger operation on the authorization confirmation control, such as clicking the authorization confirmation control. In another implementation, at least one electronic payment account is displayed in an account configuration interface, and the account authorization prompt information is displayed in an authorization prompt message. The authorization prompt message is displayed in the form of a message pop-up, a message notification bar, etc., and the authorization prompt message includes an authorization confirmation control. The authorization operation can be a trigger operation on the authorization confirmation control in the authorization prompt message. Based on the authorization operation performed on the first electronic account, the first terminal device can display an identity verification interface, which can include identity verification information to be entered, such as a payment password to be entered, or palm information to be collected.

[0118] For example, as shown in the schematic diagram of the account authorization prompt information in Figure 5a, as shown in the left image of Figure 5a, after selecting an electronic payment account, an authorization prompt interface 5100 can be displayed. This authorization prompt interface 5100 displays the following text: "Activate the deduction service" and "After activation, you can use the mobile payment service on offline payment devices and enjoy a fast and convenient payment experience and service." The authorization prompt interface also displays an activation button 5101 and a cancellation button 5102. Clicking the activation button 5101 further displays an identity verification interface 5103, which includes a payment password to be entered. The identity of the first object can be verified through the payment password. Based on the output of the account authorization prompt information, the first object can confirm whether to authorize the association of the first electronic payment account with the first mobile payment information, thereby confirming a second time whether to associate the first electronic payment account with the first mobile payment information. Based on this second confirmation of the first electronic payment account, the first electronic payment account can be authorized to be used for the mobile payment service, reducing the error rate of association between the electronic payment account and the first mobile payment information and ensuring the accuracy of the association intention.

[0119] In one implementation, the first terminal device may, in response to the selection of at least one electronic payment account, display at least one authentication method, each authentication method corresponding to one authentication information; when any of the at least one authentication method is selected, an authentication interface is displayed; the style and layout of the authentication interface match the selected authentication method.

[0120] In one specific implementation, after selecting a first electronic payment account, the displayed authentication method can be any authentication method supported by the first electronic payment account. This authentication method includes one or more of the following: password verification, facial recognition verification, palm recognition verification, fingerprint verification, voiceprint verification, iris recognition, etc. Different authentication methods verify different types of authentication information, and the authentication information received on the authentication interface matches the selected authentication method. For example, if the first electronic payment account is associated with a payment password and a face, then it can include password verification and facial recognition verification, corresponding to verifying the payment password and facial information respectively. If the first electronic payment account is also associated with a palm, then the authentication method can also include palm recognition verification, corresponding to verifying palm information. At least one authentication method can be in a pending selection state, and at least one authentication method can be displayed in the authentication method settings interface. This authentication method settings interface can be a new interface that completely covers the account configuration interface (used to display the electronic payment account), or it can be displayed as a floating or fixed window on the account configuration interface.

[0121] Different authentication methods correspond to different authentication interface layouts to receive authentication information for each method. Once an authentication method is selected, the corresponding authentication interface can be displayed. For example, if the first party chooses to authenticate via payment password, the authentication interface can display a blank box for entering the payment password (as shown in Figure 5a). If the first party chooses to authenticate via palm information, the authentication interface can display an area for capturing a palm image, similar to the palm image input interface in Figure 3d. The authentication interface may also include verification prompts to enter the appropriate type of authentication information.

[0122] For the above process of displaying the identity verification interface, see Figure 5b as an example. After the MM electronic payment account is selected, a message pop-up window 5201 can be displayed in the account configuration interface. This message pop-up window 5201 includes multiple identity verification methods, namely: password verification and palm verification. When password verification is selected, the corresponding identity verification interface 5202 can be displayed, and the payment password can be entered in this identity verification interface 5202. In this way, the first party can choose which method to use for identity verification, realizing flexible selection of identity verification methods and improving the convenience and flexibility of identity verification.

[0123] In another implementation, the first terminal device may also display at least one authentication method in response to an authorization operation performed on the first electronic payment account, each authentication method corresponding to one type of authentication information; when any of the at least one authentication method is selected, an authentication interface is displayed. That is, after the first electronic payment account is selected, an account authorization prompt may be displayed first, and then, based on the authorization operation performed on the first electronic payment account, the authentication method shown in Figure 5b above may be displayed, and then the authentication interface may be displayed.

[0124] S404: Receives the identity verification information corresponding to the selected first electronic payment account in the identity verification interface, and verifies the identity verification information.

[0125] In one implementation, the first object can input authentication information on the authentication interface, which corresponds to the first electronic payment account. The authentication information corresponding to the selected first electronic payment account includes at least one of the following: the payment password of the first electronic payment account, the account identifier of the first electronic payment account, the object identifier corresponding to the first electronic payment account, and the biometric information associated with the first electronic payment account. The account identifier of the first electronic payment account can be the account number or account ID of the first electronic payment account. The object identifier corresponding to the first electronic payment account includes, but is not limited to, the object ID of the first object, the identity number of the first object, and the mobile phone number of the first object. Biometric information refers to inherent physiological characteristics of the human body, including but not limited to fingerprints, irises, faces, palm prints, and voiceprints. It should be noted that if the palm payment service is provided by the first application and the first electronic payment account is provided by the second application, then the backend service of the second application will verify the identity based on the authentication information. Furthermore, if the authentication information is biometric information associated with the first electronic payment account (such as a palm image), then during the verification process, the biometric information received on the authentication interface will be compared with the source biometric information associated with the first electronic payment account managed by the second application.

[0126] For example, as shown in Figure 5c, which is a schematic diagram of receiving authentication information in the authentication interface, when the first electronic payment account is selected, the authentication interface 5301 can be displayed. The authentication interface 5301 prompts the user to enter the payment password of the first electronic account. After the first user enters the payment password in the authentication interface, the payment password can be displayed in plaintext or ciphertext.

[0127] In one implementation, the first terminal device can perform verification based on source information stored locally, or it can request the server to perform authentication. The first terminal device can send authentication information to the corresponding backend server (such as the backend server of the second application to which the first electronic payment account belongs), and the backend server will verify the authentication information and return an authentication result. The first terminal device can receive the authentication result, which indicates whether the verification was successful. During the verification process, the backend server can compare the authentication information with the pre-stored source information corresponding to the first electronic payment account. If they match, a first authentication result indicating successful verification can be generated; if they do not match, a second authentication result indicating verification failure can be generated. Therefore, the authentication result received by the first terminal device can include either the first or second authentication result. During the verification process, the first terminal device can display a verification loading bar to indicate the verification progress.

[0128] S405 If the verification is successful, the selected first electronic payment account will be configured as the electronic payment account associated with the first palm information.

[0129] In practical implementation, if verification is successful, it indicates that the selected first electronic payment account is indeed the first object. The first terminal device can then configure the first electronic payment account as an electronic payment account associated with the first palm information. For example, it can establish a binding relationship between the selected first electronic payment account and the current user's palm information (such as image data of the palm), and output a successful configuration result. During the binding process, the following operations can also be performed: updating database records, generating binding credentials, and sending confirmation notifications. By binding the electronic payment account to the palm information, users can complete payments by swiping their palm without carrying a mobile phone or bank card. The mechanism of binding the electronic payment account to the palm information not only improves the convenience of payment but also enhances transaction security, as only authenticated users can complete the binding. In summary, the first palm information can only be associated with the first electronic payment account with the permission or operation of the first object, thereby avoiding incorrect association of the first electronic payment account and improving the security of the association between the electronic payment account and the palm information.

[0130] In one feasible implementation, if verification fails, the authentication interface can be redisplayed to receive new authentication information and re-execute the verification steps. For example, if verification fails, the authentication interface shown in Figure 5a can be redisplayed, which will not be elaborated further here. In another feasible implementation, if verification fails, a new authentication interface can be displayed to collect new types of authentication information. For example, the initial verification displays the authentication interface shown in Figure 5a to receive the payment password. If verification fails, an interface similar to the palm print input in Figure 3d can be displayed as the authentication interface to receive palm print information.

[0131] In this embodiment, if identity verification is performed automatically without requiring interaction information from the recipient, the first terminal device can directly configure the first electronic payment account as an electronic payment account associated with the first palm information in response to the authorization operation performed on the first electronic payment account. For example, as shown in Figure 5d, after selecting the first electronic payment account, an authorization prompt interface 5401 can be displayed. This interface 5401 includes an authorization button 5402, the text of which reads: "Activate Now". When the authorization button is clicked, the backend of the palm payment service can automatically perform identity verification and, if successful, output a configuration result 5403 indicating successful addition of the electronic payment account.

[0132] In this embodiment of the application, the first terminal device can respond to the palm addition operation of the first object for the palm payment service, receive the second palm information added for the palm payment service, and configure the first electronic payment account as an electronic payment account associated with the second palm information.

[0133] In one implementation, the palm addition operation includes, but is not limited to, one or more of the following: preset gesture operation, triggering operation of the add button in the palm information management interface, and triggering operation of physical buttons. The palm information management interface is used to display the added palm information, such as displaying the first palm information, and can also be used to display at least one management control for the palm information, such as adding, deleting, or modifying controls. The relationship between the second palm information and the first palm information includes any of the following: First, the second palm information and the first palm information belong to different palm information of the same object. For example, the first palm information is the left palm image (palm image, i.e., palm print image) of the first object, and the second palm information is the right palm image of the first object. Second, the second palm information and the first palm information belong to different palm information of different objects. For example, the first palm information is the palm information of the first object (such as the left palm image), and the second palm information is the palm information of the second object (such as the right palm image).

[0134] In one implementation, the reception of the second palm information can be in the same way as the reception of the first palm information. For example, in response to the first object's palm addition operation for the palm payment service, the first terminal device can receive the second palm information in one or more of the following ways: Method 1: Display an information collection interface. This interface displays collection guidance information and a second palm image showing the corresponding action according to the collection guidance information. The first terminal device can capture the second palm image of the corresponding action and use it as the second palm information. Method 2: Output a palm information entry invitation and send it to the second object, so that the first terminal device can receive the palm information of the second object. If an electronic payment account (such as the first electronic payment account) has been configured for the palm payment service, the palm information of the second object, as the second palm information, can be automatically associated with the configured electronic payment account. Method 3: Obtain a palm information storage medium containing the palm information, and in response to the identification of the palm information storage medium, receive the palm information stored in the palm information storage medium.

[0135] If the first electronic account has already been configured as an electronic payment account associated with the first palm information before receiving the second palm information, then the first electronic account can be automatically configured as an electronic payment account associated with the second palm information without the need for authentication. If the first electronic account has not yet been configured as an electronic payment account associated with the first palm information after receiving the second palm information, then the first electronic payment account can be configured as an electronic payment account associated with the second palm information through authentication steps S403 to S406, and no authentication is required when configuring the first electronic payment account as an electronic payment account associated with the first palm information. In this embodiment, the first terminal device can respond to the configuration operation of the first object for the palm payment service, synchronously receiving the first palm information and the second palm information, where the first palm information and the second palm information are different palm information belonging to the same object or palm information of different objects, thereby configuring the first electronic payment account as an electronic payment account associated with the first palm information and configuring the first electronic payment account as an electronic payment account associated with the second palm information. That is, the first electronic payment account is configured as an electronic payment account for the palm payment service, and is associated with the first palm information and the second palm information respectively.

[0136] Therefore, the first electronic account is associated with two palm information entries, thereby improving the convenience of palm payment. In simpler terms, an electronic account can be associated with one or more palm information entries. The palm information received by the first object during the configuration operation and palm addition operation for the palm payment service can be managed under the account of the first object in the first application. Furthermore, a palm information entry can also be associated with one or more electronic accounts, and the owner of each electronic account is the first object.

[0137] In this embodiment, the palm payment service supports configuring N palm information entries; N is a positive integer. The N palm information entries include at least one palm information entry from a first object, and may also include at least one palm information entry from a second object. The first terminal device can manage the N palm information entries. Management of the N palm information entries can include one or more of the following: deletion, addition, replacement, modification, etc. Let any one of the N palm information entries be represented as palm information n, where n is a positive integer; wherein, palm information n includes one or both of palm print images and palm vein images. For example, each of the N palm information entries includes a palm print image. Taking any palm information entry (denoted as palm information n) as an example, the management of palm information n includes at least one of the following management methods.

[0138] Management Method 1: Set a palm identifier for palm information n. The palm identifier can be the name of the palm information, for example, naming the left palm information "Left Palm," or naming the left palm information of the first object "Hand No. 01," etc. The first terminal device can respond to the identifier setting operation for palm information n and set the palm identifier for palm information n. The identifier setting operation here includes, but is not limited to: preset operations for palm information (such as double-clicking the palm image) and selection operations for the palm identifier to be set. In one specific implementation, the first terminal device, in response to the palm identifier setting operation, can display at least one preset palm identifier. If any preset palm identifier is selected, the selected palm identifier can be set as the palm identifier of palm information n. For example, as shown in Figure 5e, when setting a palm identifier, clicking the identifier setting box 5501 below the left palm image displays a message window 5502. This message window 5502 includes two preset palm identifiers. When the first preset palm identifier 5503 is selected, the preset palm identifier 5503: 01 left palm is displayed in the identifier setting box 5501. Thus, by providing preset palm identifiers for selection, manual input of palm identifiers is avoided, improving operational convenience. In another specific implementation, the first terminal device responds to the palm identifier setting operation by displaying an identifier editing bar and receiving the palm identifier entered in the identifier editing bar, setting the palm identifier for palm information n. In this method, the object can customize the palm identifier to meet personalized needs.

[0139] Management Method Two: Displaying Palm Information n. The display methods for N palm information pieces can include one or more of the following: categorized display according to the object (e.g., first object, second object), categorized display according to the body part (e.g., left hand, right hand), and arranged display according to the receiving time. Based on the content included in palm information n, palmprint images can be displayed, and N palm images can be displayed in the palm information management interface. The palm information management interface is obtained by triggering the palm information management button in the application management interface. For example, as shown in Figure 5f, N palm information pieces are displayed. The first terminal device can display the application management interface 5600. By clicking the palm information management control (i.e., the "palm information" control 5601) in the management interface, the palm information management interface 5602 can be displayed, which displays the left palm image 5603 of object A. Since the palm information of the right hand was not recorded, the palm information management interface also displays an "Add" button for the right palm image of object A. When the "Add" button is clicked, the first terminal device can collect the right palm image of object A and display it on the palm information management interface.

[0140] Management Method 3: Delete palm information n. The first terminal device can respond to the deletion operation for palm information n and delete the palm information n. For example, as shown in Figure 5f, a delete control is displayed below the left palm image. Clicking the delete control can delete the left palm image. After deleting palm information n, the deleted palm information n is not displayed, and palm information n is no longer used for palm payment services. For example, if palm information n is associated with the first electronic payment account, the association between the first electronic payment account and palm information n can be automatically released after palm information n is deleted.

[0141] Management Method 4: Modify Palm Information n. Modifying palm information n can include replacing palm information n with new palm information (such as replacing it with a new palm print image), or modifying the palm identifier of palm information n. If it is replaced with new palm information, the first electronic account can be automatically associated with the new palm information.

[0142] Based on the above management methods, mobile information can be managed flexibly and autonomously, improving the convenience of mobile information management.

[0143] The service processing method provided in this application embodiment allows the first terminal device to receive authentication information through an authentication interface after selecting a first electronic payment account. This information is then used by the first electronic payment account for verification, enhancing the security of the association between the electronic payment account and the palm information, thereby ensuring the security of the electronic payment account. Furthermore, the first device can add other palm information for the palm payment service. By adding palm information, the palm payment service can support multiple palm information sets. For example, the palm payment service can record not only a left palm image but also a right palm image, allowing payment using either hand with the first electronic payment account, thus improving the convenience of palm payment.

[0144] Please refer to Figure 6, which is a flowchart illustrating another service processing method provided in an embodiment of this application. This service processing method can be executed by a first terminal device (as shown in Figure 1, the first terminal device 101a), and the service processing method may include the following steps S601 to S604.

[0145] S601, in response to the configuration operation of the first object for the palm payment service, receives first palm information for the palm payment service.

[0146] S602, displaying at least one electronic payment account of the first object.

[0147] S603, in response to the selection operation of at least one electronic payment account, the selected first electronic payment account is configured as an electronic payment account associated with the first palm information.

[0148] The specific implementation of steps S601 to S603 above can be found in the embodiments shown in Figure 2 or Figure 4, and will not be repeated here.

[0149] S604, in response to the first object's account addition operation for the palm payment service, receives the second electronic payment account added for the palm payment service, and configures the second electronic payment account as an electronic payment account associated with the first palm information.

[0150] In this embodiment, when a user uses the palm payment service, they may wish to bind multiple electronic payment accounts to meet different consumption scenarios or preferences. The account addition operation refers to a user's proactive request to bind a new account through a first terminal device. In specific implementations, the account addition operation includes, but is not limited to: preset gesture operations, triggering operations for adding controls in the account management interface, and preset operations for physical controls. For example, a user can choose to add a payment account from an instant messaging application or other supported third-party e-wallet accounts on their mobile phone. After receiving the account addition operation request, the first terminal device verifies the user's identity and ensures that the operation complies with security standards, and then incorporates the second electronic payment account into the palm payment system. This account addition process can improve the user's payment flexibility. The account management interface can be used to display the electronic payment accounts used for the palm payment service, and these electronic payment accounts are associated with each received palm information.

[0151] In one implementation, in response to an operation by a first object to add a payment service via palm scan, the first terminal device can display at least one authorized electronic payment account for the first object. These authorized electronic payment accounts are all owned by the first object and all support the palm scan payment service. Provided a first electronic payment account has already been configured for the first palm information, the displayed electronic payment accounts include those other than the configured first electronic payment account. When any electronic payment account is selected, the selected electronic payment account can be used as a second electronic payment account, thereby configuring the second electronic payment account as an electronic payment account associated with the first palm information. The owner of the second electronic payment account is the first object, and the first electronic payment account is different from the second electronic payment account. For example, the first electronic payment account is provided by a second application AA, and the second electronic payment account is provided by a second application BB. The second application AA and the second application BB are different third-party payment platforms.

[0152] For example, as shown in FIG7a, a schematic diagram of adding a second electronic payment account, the first terminal device can display an account management interface 7101. When the account addition control 7102 in the account management interface 7101 is clicked, one or more electronic payment accounts can be displayed, and based on the selection of any electronic payment account, it can be configured as an electronic payment account associated with the first palm information.

[0153] In another implementation, the second electronic payment account is the electronic payment account of the second object. In response to the first object's addition operation for the palm payment service, the first terminal device can display multiple association methods, including a first association method and a second association method. The first association method indicates the association of the first object's electronic payment account, and the second association method indicates the association of the second object's electronic payment account. If the first association method is selected, the step of displaying the first object's electronic payment account is triggered; if the second association method is selected, an account association invitation is output and sent to the second object. The second object can then return its own electronic payment account based on this invitation. The first terminal device can configure the second object's electronic payment account as an electronic payment account associated with the first palm information, meaning the owner of the second electronic payment account used for the palm payment service is the second object.

[0154] When configuring the second electronic payment account, the configuration steps are similar to those for the first electronic payment account. For example, first, an identity verification interface is displayed. The identity verification information corresponding to the second electronic payment account is received in the identity verification interface and verified. After successful verification, the second electronic payment account is configured as the electronic payment account associated with the first palm information. Since the first and second electronic payment accounts are configured as associated electronic payment accounts for the first palm information, when using the palm payment service of the first palm information, payment can be processed using either the configured first electronic payment account associated with the first palm information or the configured second electronic payment account associated with the first palm information, based on the payment recipient's choice of electronic payment account.

[0155] It should be noted that the configuration order of the first electronic payment account and the second electronic payment account is not limited in this application embodiment. For example, after receiving the first palm information, before configuring the first electronic payment account as the electronic payment account associated with the first palm information, the first terminal device can first execute S604, thereby displaying the electronic payment accounts of the first object that are not yet associated with the first palm information, and configuring the second electronic payment account associated with the first palm information for the palm payment service. Alternatively, the first terminal device can execute S604 after configuring the first electronic payment account as the electronic payment account associated with the first palm information, so that the electronic payment accounts associated with the first palm information include both the first electronic payment account and the second electronic payment account.

[0156] In this embodiment, the palm payment service supports configuring M electronic payment accounts associated with the first palm information for payment processing, where M is a positive integer. The first terminal device can also manage the M electronic payment accounts. The owners of the M electronic payment accounts are all the first object. In one specific implementation, the palm payment service is provided by a first application, and the M electronic payment accounts can be managed under accounts registered by the first object in the first application. Management of the configured M electronic payment accounts includes, but is not limited to, deleting electronic accounts and setting payment information for electronic accounts (such as payment priority, payment limit, and payment permissions).

[0157] The following explanation uses the management of a single electronic payment account as an example. Let any one of the M electronic payment accounts be denoted as electronic payment account m, where m is a positive integer and m is less than or equal to M. The management of electronic payment account m includes at least one of the following methods.

[0158] Management Method 1: Set an account identifier for electronic payment account m. The account identifier for electronic payment account m can be customized by the first object. This account identifier includes, but is not limited to, account name, account number, etc. For example, the account identifier can be the following customized account name: Payment Account No. 01, Xiaoming's Payment Account, etc. The account identifier set here can also be used for auxiliary verification in the usage process of the Shuazhang payment service. That is, when using the Shuazhang payment service, the verification of electronic payment accounts can also use the entered account identifier. For example, the entered account identifier must match the set account identifier to pass the verification and continue to provide payment services. In a feasible implementation, an account style can also be set for electronic payment account m. The account style is used to define the presentation style of the electronic payment account. For example, in the account management interface, each electronic payment account is displayed in the form of a virtual card, and patterns, pendants, etc. can be set for the virtual card. By setting the account style, the scenarios for customizing account settings can be enriched, and the fun of account management can be enhanced.

[0159] Management Method 2: Displaying Electronic Payment Accounts m. The display formats of electronic payment accounts include, but are not limited to: virtual cards, account names, virtual wallets, etc. M electronic payment accounts can be displayed in the account management interface, which is provided by the first application. The display arrangement of the M electronic payment accounts includes, but is not limited to: random arrangement, arrangement according to the account configuration timestamp size (e.g., from latest to earliest), arrangement according to the account's available credit limit size (e.g., from largest to smallest), arrangement according to the account name (e.g., by the first letter of the name, A, Z), and arrangement according to the account's payment priority (e.g., from highest to lowest). For example, as shown in Figure 7b, which illustrates the display of M electronic payment accounts, three electronic payment accounts are displayed in the account management interface in order of their configuration timestamps from most recent to oldest.

[0160] Management Method 3: Deleting Electronic Payment Account m. The first terminal device can respond to the deletion operation of electronic payment account m and delete it. This deletion operation includes, but is not limited to, triggering the delete control, preset gesture operations, etc. The delete control can be permanently displayed on the account management interface, or it can be hidden in the account management interface and activated after performing a preset operation on electronic payment account m (such as swiping left, long-pressing, continuous clicking, etc.). It can also be permanently displayed on the details interface of electronic payment account m. In one implementation, responding to the triggering of the delete control, M electronic payment accounts can be displayed in a selectable state. When electronic payment account m is selected, it can be deleted. For example, as shown in Figure 7c, which illustrates the deletion of an electronic payment account, as shown in part (1) of Figure 7c, when the control for removing the card 7301, which is fixedly displayed in the account management interface, is clicked, a checkbox can be displayed around each electronic payment account. When any one or more electronic payment accounts are selected, such as when the pay electronic payment account is selected, the checkbox 7302 can display the pattern corresponding to the selected state, and the selected electronic payment account can be deleted. When multiple electronic payment accounts are selected, batch deletion can also be achieved. As shown in part (2) of Figure 7c, when the removal card 7304 in the details interface 7303 of the electronic payment account is clicked, a confirmation prompt message 7305 can be output, and the electronic payment account m can be deleted after clicking confirmation.

[0161] It should be noted that after the electronic payment account m is deleted, the electronic payment account m will no longer be used for the palm payment service. The association between the electronic payment account m and all associated palm information can be terminated. For example, the association between the electronic payment account m and the first palm information can be terminated. If the electronic payment account m is also associated with other palm information (such as the second palm information), then the association between the electronic payment account m and the second palm information can also be terminated.

[0162] Management Method 4: Setting the Payment Priority of Electronic Payment Account m. In one implementation, the first terminal device can respond to a payment priority setting operation to set the payment priority of electronic payment account m. The payment priority can be used to indicate the order of priority use when making a payment via palm scan. A higher payment priority results in a higher priority order when making a payment via palm scan. The payment priority setting operation includes, but is not limited to: preset gesture operations, triggering the payment priority control in the details interface of electronic payment account m, and triggering the global priority setting control in the account management interface. The details interface of electronic payment account m can be triggered in response to the selection of electronic payment account m in the account management interface. The global priority setting control allows for one-click setting of the payment priorities of M electronic payment accounts, while the payment priority control in the details interface allows for individual setting of the payment priority of electronic payment account m, enabling setting the priority one by one.

[0163] For example, as shown in Figure 7d, the account management interface also includes a global priority setting control 7401. Clicking this control allows for one-click setting of the payment priority of all configured electronic payment accounts. For instance, if the payment priority of electronic payment account m is set to 1 (highest priority), and the payment priorities of the other electronic payment accounts are set to 2 respectively, then electronic payment account m, as the primary payment account, can be prioritized for payment when using the mobile payment service. Furthermore, the priorities of the other electronic payment accounts can be set to the same, and these accounts can be randomly displayed during payment for easy selection.

[0164] Management Method 5: Setting the payment limit for electronic payment account m. The first terminal device can respond to the operation of setting the payment limit for electronic payment account m and set the payment limit for electronic payment account m. The payment limit setting operation includes, but is not limited to, any one or more of the following: preset gesture operation, triggering operation of the payment limit control in the details interface of electronic payment account m, and triggering of preset physical button. The payment limit setting content includes at least one of the following: daily payment limit, weekly payment limit, monthly payment limit, and annual payment limit. For example, as shown in the schematic diagram of setting the payment limit of electronic payment account in Figure 7e, when the payment limit control 7501 in the details interface of electronic payment account m is clicked, the payment limit setting interface 7502 can be displayed. The payment limit setting interface 7502 includes the value of the payment limit to be set and the period (such as daily, weekly, monthly, quarterly, annual). If the first object enters a payment limit of 10 yuan and selects a daily period, after clicking the confirmation control, the first terminal device can set the daily payment limit of electronic payment account to 10 yuan.

[0165] Management Method Six: Setting Payment Permissions for Electronic Payment Account m. The first terminal device can respond to the payment permission setting operation for electronic payment account m and set the payment permissions for electronic payment account m. The payment permission setting operation includes, but is not limited to, one or more of the following: preset gesture operation, triggering the payment permission control in the details interface of electronic payment account m, or triggering a preset physical button. Payment permissions include at least one of the following: a permitted time period, and at least one permitted object.

[0166] For example, as shown in Figure 7f, which illustrates the setting of payment permissions for an electronic payment account, clicking the payment permission control 7601 in the details interface displays the payment permission setting interface 7602. This interface shows the usage time period and the user to be set. For instance, if the first user selects a start timestamp of 7:00 and an end timestamp of 23:00, the first terminal device can set the allowed usage time period for electronic payment account m to be from 7:00 to 23:00. Therefore, when using the mobile payment service, if the time period falls within this allowed period, payment using electronic payment account m is permitted. However, if the time period falls between 23:00 and 7:00 the next day, payment using electronic payment account m is prohibited. The allowed at least one object can be an object other than the first object, such as a second object, and this permission setting can be performed by the first object. Based on the payment permission setting operation, an object list can be displayed, which includes at least one object, all of which are images with palm information entered under the account of the first object. In response to the selection of one or more objects in the object list, the first terminal device can set the selected at least one object as an object that is allowed to use the palm payment service.

[0167] In this embodiment, the first terminal device can also display the bill under the electronic payment account m in response to the bill viewing operation of the electronic payment account m. The bill viewing operation includes, but is not limited to, preset gesture operations and triggering the bill details button in the details interface of the electronic payment account m. The bill under the electronic payment account m records at least one transaction involved in payment processing using the electronic payment account m in the swipe payment service. Each transaction includes, but is not limited to, transaction amount, transaction object, transaction time, and transaction location. For example, as shown in Figure 7g, when the bill details button 7701 in the details interface of the electronic payment account m is clicked, the bill 7702 under the electronic payment account m can be displayed. This bill includes three transactions made using the electronic payment account m during the use of the swipe payment service, each transaction including the transaction amount and transaction time. Through the bill of the electronic payment account, transactions through the electronic payment account m can be automatically recorded for the first object, and a bill query function can be provided for convenient viewing when the object has a corresponding query need. The billing information for electronic payment account m also supports viewing transactions by category, such as by transaction object or by transaction amount.

[0168] The service processing flow mentioned in Figures 2, 4, and 6 above can be the configuration flow of the swipe payment service. Regarding the technical logic support for the above products, in one implementation, the swipe payment service is provided by a first application. The first terminal device can register an account in the first application in response to the account registration operation of the first user. For example, referring to Figure 7h, the first user is a new user who has not yet registered an account in the first application. The first terminal device can download the first application 702 and register an account in response to the scanning operation of the graphic code on the swipe device 701. Then, the first application can sign up for an electronic payment account 703, and the electronic payment account 703 can return a successful signing result to the first application 702. This registration process can be seen in the schematic diagram of the configuration flow of the swipe payment service shown in Figure 7h.

[0169] More specifically, the registration process described above may include the following: In response to the configuration operation of the first object regarding the palm payment service, the first terminal device queries the configuration information of the first object for the palm payment service. Specifically, the first terminal device can query the configuration information of the first object for the palm payment service from a server, where the palm payment service is provided by a first application, and the server is an application server that provides data services to the first application. The configuration information indicates the configuration status of the first object for the palm payment service. This configuration information includes registration information; for example, the configuration information indicates that the first object has registered an account with the first application, but one or more of the following situations may exist: no palm information has been entered, no object identifier has been bound, and no electronic payment account has been associated. For example, in the configuration process of the palm payment service shown in Figure 8a, the object can configure the palm payment service in the object interface (e.g., user interface) in step S801; in step S802, request the control unit that configures the palm payment service to query registration information; in step S803, the control unit can obtain the object identity from the second application and register an account (i.e., rebuild), then obtain the object account and query the registration information. If the palm payment object's account is not bound to its own object identifier, then in step S804, the registered account and object identifier can be associated through the rebuild step. If the palm payment object has not entered palm information, features can also be collected through the rebuild step. If the palm payment object is not associated with an electronic payment account, it can also be associated with an electronic payment account through the rebuild step. Therefore, based on the instructions of the configuration information, one or more of the following situations can be performed:

[0170] Scenario 1: If the configuration information indicates that the first object has not entered the first palm information for the palm payment service, then the palm image of the first object is collected, and the palm image is used to extract features to obtain the first palm information.

[0171] Referring to the flowchart of palm image entry shown in Figure 8b, the first terminal device can call the palm image entry component in step S805 through the object interface. Then, in step S806, the object interface can request the control unit of the palm payment service to bind the palm. Then, in step S807, the control unit of the palm payment service registers the online palm image (i.e., the palm image collected by the first terminal device) for the palm payment object. By requesting registration through online acquisition, the device can activate its own shooting module or the shooting device connected to the first terminal device to capture the palm of the first object, obtaining the palm image of the first object. After feature extraction of the collected palm image in step S808, one or both of the palm print image and palm vein image can be obtained as the first palm information, so that the first terminal device can receive the first palm information for the palm payment service. The first palm information obtained after feature extraction can be added to the feature group in step S809 to provide retrieval content during palm payment.

[0172] Scenario 2: If the configuration information indicates that the first palm information is not associated with any electronic payment account, then query the activation permission of the first object's electronic payment account, and if the activation permission indicates that the electronic payment account has been activated, obtain at least one electronic payment account of the first object.

[0173] In specific implementation, the first terminal device can query the backend server corresponding to each electronic payment account of the first object to see if the electronic payment account is enabled; in simple terms, whether the electronic payment account is activated. If any electronic payment account is enabled, the first terminal device can obtain and display the electronic payment account, and the first application supports access to the electronic payment account. For example, the first application supports access to electronic payment accounts from three payment platforms, but the first object only enables electronic payment accounts from two of them. Therefore, it can obtain the two enabled electronic payment accounts to display them and associate the electronic payment accounts with the palm information based on the object's interactive operation. For example, as shown in the flowchart of associating electronic payment accounts in Figure 8c, in step S810, the electronic payment account component can be launched on the corresponding object interface, requesting the control terminal of the palm payment service to associate the electronic payment account with the first palm information. Thus, in step S811, the control unit can query the second application to see if the electronic payment account is enabled, that is, to see if the electronic payment account it provides is activated. If it is activated, the electronic payment account supports association (i.e., creation) with the first palm information.

[0174] Scenario 3: If the configuration information indicates that the account of the first object in the first application is not associated with the object identifier of the first object, then, if the object identifier of the first object is authorized, the account of the first object in the first application will be associated with the object identifier of the first object.

[0175] In one specific implementation, authorization request information can be displayed. This authorization request information is used to request authorization of the object identifier (e.g., authorized mobile phone number) of the first object. After the first object confirms the authorization, the object identifier of the first object can be queried from the second application. After the object identifier of the first object is found, the object identifier of the first object is bound to the swipe payment object (i.e., the object that has registered an account in the first application). For example, as shown in the flowchart of associating the object identifier of the first object in Figure 8d, the object identifier of the first object is the mobile phone number of the first object. In step S812, the object interface can request authorization of the object identifier (e.g., phone number). After the object confirms the authorization, the object identifier can be queried from the second application in step S813, and in step S814, the control unit of the swipe payment service can be requested to bind the object identifier. If the first object has not yet registered an account in the first application, an account can be registered (i.e., created) based on the object identifier to become the swipe payment object, and then the object identifier can be bound to the swipe payment object to obtain an account associated with the object identifier.

[0176] The service processing method provided in this application embodiment can configure a second electronic payment account associated with the first palm information after configuring a first electronic payment account associated with the first palm information for the palm payment service. Based on the configuration of the first and second electronic payment accounts, the first palm information can be associated with two electronic payment accounts, which is beneficial to the convenience of using electronic payment accounts when making palm payments. Furthermore, the first terminal device can also manage the M electronic payment accounts configured for the palm payment service, enabling flexible binding and deletion of electronic payment accounts and improving the autonomy of electronic payment account association. In addition, payment priority, payment limit, payment permissions, etc., of the electronic payment accounts can be set, which increases the diversity of electronic payment account settings and can meet personalized needs.

[0177] Please refer to Figure 9, which is a flowchart illustrating a service processing method provided in an exemplary embodiment of this application. This service processing method can be executed by a second terminal device (as shown in Figure 1, the second terminal device 101b), and the service processing method may include the following steps S901 to S903.

[0178] S901, in response to a request operation for the palm payment service, receives first palm information for the palm payment service.

[0179] In practical implementation, the request operation for the palm payment service can be initiated by the transaction object through a second terminal device. For example, when using the palm payment service in an offline convenience store, the request operation is initiated after scanning the barcode to settle the payment. The second terminal device can respond to the request operation by collecting first palm information for the palm payment service, such as collecting the palm information of the payment object, and then making payment based on the electronic payment account (such as electronic payment account m) bound to the payment object's palm information. For example, as shown in Figure 10a, which is a schematic diagram of receiving first palm information for the palm payment service, the second terminal device is a palm payment device in an offline store. The second terminal device has a palm sensing area 1001 and a display screen 1002. When the first object swipes its palm, it can place its palm above the palm sensing area in the air to receive the palm image of the first object and display at least one electronic payment account associated with the palm image on the display screen. That is to say, when the user completes identity verification on the palm payment device in the offline store, the second terminal device will trigger a request operation for the palm payment service. Requests for palm-swipe payment services are typically initiated by the user, such as placing their palm on the device's biometric sensor or confirming their payment intention through other means (e.g., clicking a button). The first palm information refers to the biometric data of the hand collected by the palm-swipe device and transmitted to the second terminal device for identity verification and payment authentication, such as palmprint images and liveness detection results. This first palm information is then encrypted and securely transmitted to the payment system for further processing.

[0180] First-hand information serves as the core basis for user authentication, effectively preventing unauthorized access and payment activities, thereby improving payment security. Furthermore, by using first-hand information for identity verification, users no longer need to carry a mobile phone or bank card, simplifying the payment process and enhancing the user experience.

[0181] S902, Displays the first electronic payment account that has been configured and associated with the first palm information.

[0182] In one implementation, a first electronic payment account and first palm information are associated during the configuration phase. When using the palm payment service, payment can be made using the first electronic payment account based on the first palm information. The second terminal device can display a payment method interface, which displays the configured electronic payment account associated with the first palm information, such as the first electronic payment account. For example, during the configuration phase of the palm payment service, an electronic payment account 'aa' associated with the first palm information has been configured for the palm payment service. Therefore, during the usage phase of the palm payment service, based on the received first palm information, the electronic payment account 'aa' can be displayed on the payment method interface, as shown in Figure 10b.

[0183] In this embodiment, after receiving the first palm information and successfully matching the user's identity, the second terminal device searches for and displays the user's bound electronic payment account. This electronic payment account is a digital wallet account that the user binds during registration to complete cardless payments, such as an instant messaging application payment account or another third-party payment platform account. The user needs to configure this electronic payment account in advance and associate it with the user's palm information. By displaying the first electronic payment account, the second terminal device ensures that the user clearly knows the payment account they are about to use, avoiding accidental operation or confusion of multiple accounts. Simultaneously, displaying the first electronic payment account also enhances the user's transparency and trust in the payment process.

[0184] In this embodiment, before displaying the various electronic payment accounts associated with the first palm information, the payment object can be verified first to assist in verifying whether the payment object is an entity that has activated the palm payment service. The process of assisting verification is explained below using the association of the first palm information with the first electronic payment account as an example. After executing the above step S901, the second terminal device can also display an assist verification interface and receive assist verification information in the payment verification interface; then, the second terminal device verifies the assist verification information; if the verification is successful, the step of displaying the configured first electronic payment account associated with the first palm information is triggered.

[0185] The request for the palm payment service is received by the second terminal device. The display trigger conditions for the auxiliary verification interface include one or more of the following: the first palm information is collected for the first time by the second terminal device, or the frequency of the first palm information being collected by the second terminal device does not reach a preset frequency. For example, when a payment recipient uses the palm payment service for the first time, and the second terminal device collects the first palm information for the first time, the auxiliary verification interface can be displayed to ensure security, and auxiliary verification information can be received through this interface. The auxiliary verification information includes one or more of the following: the object identifier of the first recipient, and the identity identifier of the first recipient. For example, as shown in Figure 10c, when a payment recipient uses the palm payment service for the first time, after the palm device receives the palm information, the auxiliary verification interface 1030 can be displayed. This auxiliary verification interface 1030 supports inputting verification information associated with the palm payment service, such as the last four digits of a mobile phone number. If the last four digits are successfully verified, the first electronic payment account shown in Figure 10b can be further displayed.

[0186] S903 uses the first electronic payment account for payment processing.

[0187] The first electronic payment account stores a corresponding amount of digital assets. When processing payments using the first electronic payment account, the corresponding amount of digital assets in the first electronic payment account can be transferred to the account of the counterparty according to the payment amount. The second terminal device can also output a payment result, which is used to indicate successful payment and includes information such as the payment amount and the counterparty. If the digital assets stored in the electronic payment account are of different types than the digital assets stored in the counterparty's account, the unit exchange rate between the two can also be displayed. For example, as shown in the schematic diagram of the output payment result in Figure 10d, when a certain electronic payment account is selected for payment processing, payment confirmation information can be displayed first. In response to the payment confirmation operation performed by the first counterparty, such as clicking the "Pay Now" control 1040, the payment result can be output in a separate interface 1041. This payment result is used to indicate successful payment and includes the payment amount and the counterparty (Convenience Store A); the interface 1401 also displays the exchange rate between different digital assets.

[0188] In this embodiment, when the user confirms payment, the second terminal device will use the displayed first electronic payment account to perform the deduction operation. Payment processing includes steps such as generating a transaction order, verifying the account balance, and calling the payment interface to complete the fund transfer. The payment process does not rely on physical cards or mobile phone scanning; it can be completed solely through the user's palm information. Using the first electronic payment account for payment processing not only improves payment efficiency but also reduces the user's dependence on mobile devices, especially suitable when the phone battery is low or unusable. Furthermore, since the payment process is based on the user's biometric identity rather than traditional passwords or card information, it significantly reduces the risk of information leakage and fraud. This embodiment, by responding to the palm payment request and receiving the first palm information, can achieve fast and secure identity verification; displaying the first electronic payment account associated with the first palm information ensures that the user clearly understands the source of payment, thus enabling the user to complete the payment process using the first electronic payment account. This achieves an efficient and convenient cardless payment experience without relying on a mobile phone or bank card, improving user satisfaction and payment security.

[0189] In this embodiment, the first palm information is also associated with a second electronic payment account. The second terminal device can also perform the following processing: displaying the configured second electronic payment account associated with the first palm information; if the second electronic payment account is selected, then using the second electronic payment account for payment processing; if the first electronic payment account is selected, then triggering the step of using the first electronic payment account for payment processing. That is, when the first palm information is associated with multiple electronic payment accounts (such as the first and second electronic payment accounts mentioned above), the first and second electronic payment accounts can be displayed, and the first and second electronic payment accounts can be displayed in an orderly manner. The methods of displaying the first electronic payment account include, but are not limited to: displaying them in descending order of the set payment amount, displaying them randomly, displaying them in descending order of the payment priority of the electronic payment accounts, and displaying them in ascending order of the timestamp associated with the first palm information. Since multiple electronic payment accounts are displayed, the payment recipient can select a certain electronic payment account for payment. Therefore, the second terminal device can respond to the selection of a certain electronic payment account and use the selected electronic payment account for payment processing. For example, the second terminal device can respond to the selection of a second electronic payment account and use the second electronic payment account for payment processing. The process of using the second electronic payment account for payment processing is similar to that of using the first electronic payment account for payment processing, and will not be described in detail here. When the first electronic payment account is selected, the second terminal device can respond to the selection of the first electronic payment account and trigger the execution step S903.

[0190] The service processing method provided in this application embodiment, by receiving first palm information for palm payment service, can display the configured electronic payment account and process the payment using the configured electronic payment account. This allows customers to complete payments at offline stores without needing a portable payment device (such as a mobile phone) or a physical bank card, improving payment efficiency. If multiple electronic payment accounts are configured, customers can also flexibly choose one for payment, further enhancing convenience and flexibility.

[0191] Based on the description of the above embodiments, online configuration services (including online palm recording) can be used via mobile terminals (such as mobile phones), and offline activation services can be achieved via palm scanning devices. For example, on the mobile phone, the user can scan the store's material code to enter the interactive interface of the first application, and then adjust their palm movements or positions according to the interactive prompts. The palm scanning system can perform liveness detection on the user's palm and complete the recording of the palm image (such as a palm RGB image). On the palm scanning device side, for users who have completed online recording, activation can be performed on the palm scanning device at an offline store within the corresponding time or geographical range. After the user clicks "Confirm," payment can begin. The palm scanning service side can replace the user's palm image with two-factor palm information (i.e., palmprint image and palm vein image).

[0192] In one implementation, the second terminal device is a palm-swiping device, and the palm-swiping payment service is provided by the first application. As shown in Figure 10e, which illustrates the usage flow of the palm-swiping payment service, the second terminal device is a palm-swiping device 1001. This device collects and provides first palm information (such as left hand information) to the backend server of the first application (i.e., the palm-swiping application backend 1002). The backend server can send an object identifier (such as object ID), a merchant identifier (such as merchant ID), and a dynamic token (i.e., a dynamic token generated dynamically for each palm-swiping payment) to an electronic payment account 1003. The dynamic token is associated with a static token (i.e., a long-term object token). Based on this association, it can be determined whether the requested electronic payment account is the one configured during the configuration phase. This static token is obtained after being associated with the electronic payment account during the configuration process of the palm-swiping payment service. Under the payment rules allowed by the electronic payment account, after successful palm-swiping identification, payment can be deducted from the electronic payment account, thus completing the cardless payment. For example, after verifying the information shown by the above object identifier and merchant identifier or dynamic token, the electronic payment account can return the payment code to the backend server, which in turn returns it to the second terminal device. Since the second terminal device is also connected to the merchant POS machine 1004 (i.e., the payment collection device used by the merchant for non-cash settlement), the payment code can be sent to the merchant POS machine. Thus, the merchant POS machine can use the payment code to apply to the electronic payment account to place an order, that is, to apply to transfer the corresponding amount of digital assets. Based on the recognition of the payment code, the electronic payment account can transfer the corresponding amount of digital assets to the merchant account through the merchant POS machine.

[0193] In this embodiment, the palm payment service is provided by a first application, and the request operation is received by a second terminal device. The second terminal device displays a first electronic payment account configured and associated with the first palm information. The specific technical process may include the following steps: First, a search is performed from a first feature database based on the first palm information. Then, if target palm information matching the first palm information is found in the first feature database, the identification result is determined based on the object associated with the target palm information. Finally, the first object is authenticated based on the identification result, and if the authentication is successful, at least one configured electronic payment account associated with the first palm information is queried.

[0194] In this embodiment, when searching from the first feature library based on the first palm information, the second terminal device is a terminal device that supports palmprint recognition and palm vein recognition, such as a palm-scanning device. The first feature library is used to store at least one set of palm information collected by the second terminal device; each set of palm information includes a palmprint image and a palm vein image; each set of palm information is associated with an object. Since the second terminal device can be deployed in offline stores, the first feature library can also be called an offline feature library. The first palm information may include one or both of palmprint images and palm vein images. Based on the first palm information, the second terminal device can first search in the first feature library to see if there is a set or more sets of palm information that match the first palm information. Here, matching can refer to the similarity between the first palm information and the palm information in the first feature library. For example, if the first palm information includes a palmprint image, then the set of palm information with the highest similarity to the palmprint image can be retrieved from the first feature library as the matching target palm information.

[0195] In one implementation, in a palm-swipe payment scenario, upon receiving the palm information of the first object, a liveness detection can be performed on the palm first. If the liveness detection passes, a palm image can be captured, and features can be extracted from the palm image to obtain the first palm information. Then, it can be retrieved from a first feature library. For example, as shown in the offline palm-swipe payment flowchart in Figure 11a, in step S1101, the first object requests palm-swipe payment, which can be identified by the object boundary. Here, the object boundary determines whether to extract an identification step, including liveness detection and merging the retrieval results. Then, the palm-swipe payment service is called to obtain the payment method (i.e., the deduction method is obtained in step S1102), and then at least one configured electronic payment account is displayed. During data collection, a liveness detection algorithm can be performed in step S1103 to collect a palm image as the palm passes through. Then, features can be extracted in step S1104 according to a feature algorithm. The first feature library can be feature groups, each feature group being a set of palm information, which can have a corresponding group name. During retrieval, retrieval can be performed according to features and group names. When multiple similar feature groups are retrieved, the retrieval results can be merged in step S1105. For example, if the retrieved palm information is associated with the most object A, then the identification result that the first palm information belongs to object A can be obtained.

[0196] After retrieving information from a first feature database based on the first palm information, if target palm information matching the first palm information is found in the first feature database, the recognition result is determined based on the object associated with the target palm information. In one specific implementation, the similarity between the target palm information and the first palm information is greater than a preset similarity (e.g., 96%). If the first palm information is the palm information of the first object, then the retrieval of the target palm information from the first feature database indicates that the second terminal device has also collected the palm information of the first object. Since each set of palm information is associated with an object, the object associated with the target palm information can be determined as the recognition result.

[0197] In this embodiment, if no matching set of palm information is found in the first feature library, a search is performed in the second feature library. The second feature library stores at least one set of palm information collected by the first terminal device; the first terminal device receives configuration operations for the palm payment service; each set of palm information includes a palmprint image, and each set of palm information is associated with an object. The first terminal device is a terminal device that supports palmprint recognition, such as a smartphone; since the first terminal device does not need to be fixed in an offline store but is a portable mobile terminal device, the object's palm information can be collected anytime, anywhere. Therefore, the second feature library can also be called an online feature library.

[0198] Based on the search results in the second feature database, the second terminal device can perform the content described in the following two cases.

[0199] Scenario 1: If target palm information matching the first palm information is retrieved from the second feature library, the recognition result is determined based on the object associated with the target palm information. In other words, even if the target palm information is not retrieved from the first feature library but is retrieved from the second feature library, the recognition result can still be determined based on the object associated with the target palm information. It should be noted that the palm information stored in the first and second feature libraries differs. The palm information stored in the second feature library includes palmprint images. If the first palm information includes palmprint images, the target palm information retrieved from the second feature library will include palmprint images matching the first palm information.

[0200] Scenario 2: If no target palm information matching the first palm information is found in the second feature library, a configuration request for the palm payment service is generated. In specific implementation, if the search result obtained from the second feature library is empty, it means that no target palm information matching the first palm information exists in the second feature library. Therefore, the second terminal device can generate a configuration request for the palm payment service, re-collect the first palm information for the palm payment service, and repeat the above steps.

[0201] After identifying the object associated with the target palm information, the first object can be authenticated based on the identification result. If the authentication is successful, at least one configured electronic payment account associated with the first palm information can be queried. In specific implementation, the first palm information is the palm information of the first object, the identification result includes the object associated with the target palm information, and the second terminal device can receive the returned control code (such as the last four digits of the mobile phone number to be entered) for authentication. For example, if the last four digits of the mobile phone number entered by the first object are the same as the last four digits of the mobile phone number bound to the object associated with the target palm information, it indicates that it is indeed the first object. Therefore, based on the object identifier (such as user ID) of the first object in the first application, the list of configured electronic payment accounts of the first object can be queried, thereby displaying at least one configured electronic payment account.

[0202] For example, as shown in the flowchart of the retrieval and identification process in Figure 11b, if the offline identification result is empty, the online database can be searched in step S1106, and the search results can be merged in step S1107 to obtain the identification result. If the online identification result is empty, it means that neither the first feature database nor the second feature database stores any palm information of the first object. Therefore, in one implementation, a request can be made to the palm-scanning object to activate the identification photo, that is, to collect the palm information of the palm-scanning object; in another implementation, a control code can be returned in step S1108, which is then given to the second terminal device for verification, such as requiring the palm-scanning object to fill in the last four digits of its mobile phone number. When highly similar palm information is retrieved from the second feature database, the identification result can be cached so that when the first palm information is used again, the cached identification result can be used directly without retrieving it from the feature database. If an identification result exists, to ensure security, a control code can be returned for verification, and after successful identification, the electronic payment account associated with the first object can be queried. For the process of returning the control code for verification, please refer to the detailed process shown in Figure 11c. The mobile payment service can request verification of the last four digits of a mobile phone number in step S1109. The second terminal device can receive and verify the last four digits of the mobile phone number entered by the mobile payment user. After successful verification, it obtains the payment method and updates the recognition result. Based on the recognition result, it can query the configured list of electronic payment accounts, which includes account IDs.

[0203] This application embodiment can be a cardless payment solution launched through cooperation between the palm-swiping technology provider, the payment institution providing the electronic payment account, and the merchant, featuring online palm recording and offline palm-swiping payment. Furthermore, this application embodiment can utilize the existing merchant network of the electronic payment account, eliminating the need to expand merchant acquiring networks one by one. The palm-swiping payment service is provided by a first application (APP or mini-program). Users can register and log in to an account on the first application via their mobile phone, completing palm recording and binding their electronic payment account within the mobile application. When users visit merchants with palm-swiping devices offline, they can use palm-swiping payment to deduct digital assets from their bound electronic payment account, completing the cardless payment without binding a bank card. After offline palm-swiping payment, users can also manage their palm and payment online via their mobile phone, such as re-recording their palm, managing payment limits, canceling and logging out of their account, etc.

[0204] The palm-scanning payment service mentioned in the service processing method provided in this application can be used in various payment scenarios, including but not limited to: offline shopping payment scenarios, online shopping payment scenarios, and other payment scenarios. For example, in an offline shopping payment scenario, after a customer purchases goods and the merchant settles the payment, an order awaiting payment is generated. The palm-scanning device in the offline store can collect the customer's palm information, and then, based on the comparison result between the collected palm information and the palm features stored in the feature database, display at least one electronic payment account configured for the palm-scanning payment service. Based on the selection of the electronic payment account, the order can be processed using the selected electronic payment account. This allows for flexible selection of electronic payment accounts, and when the limit of a certain electronic payment account is insufficient, other electronic payment accounts can be used for payment, improving payment convenience.

[0205] Please refer to Figure 12a, which is a schematic diagram of a service processing device provided in an embodiment of this application. This service processing device can be installed in the first terminal device provided in this embodiment. The service processing device shown in Figure 12a can be a computer program (including program code) running on the first terminal device. This service processing device can be used to execute some or all of the steps in the method embodiments shown in Figures 2, 4, and 6. Please refer to Figure 12a, the service processing device can include the following units: a first transceiver unit 1201, configured to receive first palm information for the palm payment service in response to a configuration operation of a first object for the palm payment service; a first display unit 1202, configured to display at least one electronic payment account of the first object; and a configuration unit 1203, configured to configure the selected first electronic payment account as an electronic payment account associated with the first palm information in response to a selection operation of at least one electronic payment account; wherein, when using the palm payment service of the first palm information, the configured first electronic payment account associated with the first palm information is used for payment processing.

[0206] In some embodiments, the owner of each electronic payment account is a first object, and the first display unit 1202 is further configured to: obtain the object identifier of the first object and display at least one electronic payment account corresponding to the object identifier of the first object; or, receive at least one account information input by the first object and display the electronic payment account indicated by each account information.

[0207] In some embodiments, the configuration unit 1203 is further configured to: display an authentication interface in response to the selection operation of at least one electronic payment account; receive authentication information corresponding to the selected first electronic payment account in the authentication interface and verify the authentication information; and configure the selected first electronic payment account as an electronic payment account associated with the first palm information in response to the successful verification of the authentication information; wherein the authentication information corresponding to the selected first electronic payment account includes at least one of the following: the payment password of the first electronic payment account, the account identifier of the first electronic payment account, the object identifier corresponding to the first electronic payment account, and the biometric information associated with the first electronic payment account.

[0208] In some embodiments, the first display unit 1202 is further configured to: output account authorization prompt information in response to the selection operation of at least one electronic payment account; the account authorization prompt information is used to prompt authorization of the selected first electronic payment account; and display an identity verification interface in response to the authorization operation performed on the first electronic payment account.

[0209] In some embodiments, the first transceiver unit 1201 is further configured to: receive second palm information added for the palm payment service in response to a palm addition operation of the first object for the palm payment service; the configuration unit 1203 is further configured to: configure the first electronic payment account as an electronic payment account associated with the second palm information; wherein the second palm information and the first palm information are palm information belonging to the same object; or, the second palm information and the first palm information are different palm information belonging to different objects.

[0210] In some embodiments, the first transceiver unit 1201 is further configured to: receive a second electronic payment account added for the palm payment service in response to an account addition operation of the first object for the palm payment service; the configuration unit 1203 is further configured to: configure the second electronic payment account as an electronic payment account associated with the first palm information; wherein the owner of the second electronic payment account is the first object, and the first electronic payment account is different from the second electronic payment account.

[0211] In some embodiments, the palm payment service supports configuring N palm information pieces, where any one of the N palm information pieces is represented as palm information n, and n and N are positive integers. The device further includes a management unit configured to manage the N palm information pieces. The management of palm information n includes at least one of the following: setting a palm identifier for palm information n, displaying palm information n, deleting palm information n, and modifying palm information n. Palm information n includes one or both of palm print images and palm vein images.

[0212] In some embodiments, the palm payment service supports configuring M electronic payment accounts associated with the first palm information for payment processing; let any one of the M electronic payment accounts be represented as electronic payment account m, where m and M are both positive integers, and m is less than or equal to M; the management unit is further configured to manage the M electronic payment accounts; wherein, the management of electronic payment account m includes at least one of the following: setting an account identifier for electronic payment account m, displaying electronic payment account m, deleting electronic payment account m, setting the payment priority of electronic payment account m, setting the payment limit of electronic payment account m, and setting the payment permissions of electronic payment account m.

[0213] In some embodiments, the palm payment service is configured with M electronic payment accounts associated with the first palm information for payment processing; let any one of the M electronic payment accounts be represented as electronic payment account m, the first display unit 1202 is further configured to: in response to a bill viewing operation on electronic payment account m, display the bill under electronic payment account m; the bill under electronic payment account m is used to record at least one transaction involved in the payment processing using electronic payment account m in the palm payment service.

[0214] In some embodiments, the payment limit settings include at least one of the following: daily payment limit, weekly payment limit, monthly payment limit, and annual payment limit; payment permissions include at least one of the following: allowed time period and allowed at least one object.

[0215] In some embodiments, the apparatus further includes a query unit configured to: query configuration information of the first object for the swipe payment service in response to a configuration operation of the first object for the swipe payment service; the configuration information is used to indicate the configuration status of the first object for the swipe payment service; and a first processing unit configured to: configure information for the first object based on the configuration status indicated by the configuration information.

[0216] In some embodiments, the swipe payment service is provided by a first application; the first processing unit is further configured to: in response to the configuration state indicated by the configuration information being a first configuration state, and upon confirming the object identifier of the authorized first object, associate the account of the first object in the first application with the object identifier of the first object; the first configuration state is: the account of the first object in the first application is not associated with the object identifier of the first object.

[0217] In some embodiments, the first processing unit is further configured to: in response to the configuration state indicated by the configuration information being a second configuration state, acquire a palm image of the first object; the second configuration state is: the first object has not recorded the first palm information for the palm payment service; and perform feature extraction on the palm image to obtain the first palm information.

[0218] In some embodiments, the first processing unit is further configured to: query the enable permission of the electronic payment account of the first object in response to the configuration state indicated by the configuration information being a third configuration state; the third configuration state being: the first palm information is not associated with any electronic payment account; and if the enable permission indicates that the electronic payment account has been enabled, obtain at least one electronic payment account of the first object.

[0219] Please refer to Figure 12b, which is a schematic diagram of another service processing device provided in an embodiment of this application. This service processing device can be installed in the second terminal device provided in this embodiment. The service processing device shown in Figure 12b can be a computer program (including program code) running on the second terminal device. This service processing device can be used to execute some or all of the steps in the method embodiment shown in Figure 9. Please refer to Figure 12b, the service processing device may include the following units: a second transceiver unit 1210, configured to receive first palm information for the palm payment service in response to a request operation for the palm payment service; a second display unit 1211, configured to display a first electronic payment account configured to be associated with the first palm information; and a payment unit 1212, configured to perform payment processing using the first electronic payment account.

[0220] In some embodiments, the first palm information is also associated with a second electronic payment account, and the second display unit 1211 is further configured to: display the configured second electronic payment account associated with the first palm information; in response to the second electronic payment account being selected, perform payment processing using the second electronic payment account; and in response to the first electronic payment account being selected, trigger the execution of the step of performing payment processing using the first electronic payment account.

[0221] In some embodiments, the palm payment service is provided by a first application, and the request operation is received by a second terminal device; the apparatus further includes: a second processing unit configured to: in response to retrieving target palm information matching the first palm information from a first feature library, determine an identification result based on the object associated with the target palm information; wherein, the first feature library is used to store at least one set of palm information collected by the second terminal device; each set of palm information includes a palm print image and a palm vein image; each set of palm information is associated with an object; authenticate the first object based on the identification result; and in response to the authentication result being successful, query at least one configured electronic payment account associated with the first palm information.

[0222] In some embodiments, the second processing unit is further configured to: in response to not finding palm information matching the first palm information in the first feature library, search in the second feature library; wherein the second feature library is used to store at least one palm information collected by the first terminal device; the first terminal device is used to receive configuration operations for the palm payment service; each palm information includes a palmprint image, and each palm information is associated with an object; in response to finding a target palm information matching the first palm information in the second feature library, determine the recognition result based on the object associated with the target palm information; in response to not finding a target palm information matching the first palm information in the second feature library, generate a configuration request for the palm payment service.

[0223] It is understood that the specific functions of each unit of the service processing apparatus described in the embodiments of this application can be specifically implemented according to the methods in the above method embodiments, and the specific implementation process can be referred to the relevant descriptions in the above method embodiments, which will not be repeated here. In addition, the beneficial effects of using the same method will not be repeated here either.

[0224] Please refer to Figure 13, which is a schematic diagram of a terminal device provided in an exemplary embodiment of this application. This terminal device can be implemented as either the first terminal device or the second terminal device described above. As shown in Figure 13, the terminal device may include an input device 1301, an output device 1302, a processor 1303, a memory 1304, a network interface 1305, and at least one communication bus 1306. The processor 1303 may be a Central Processing Unit (CPU). The processor may further include a hardware chip. The hardware chip may be an Application-Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), etc. The PLD may be a Field-Programmable Gate Array (FPGA), a Generic Array Logic (GAL), etc.

[0225] In this embodiment of the application, if the terminal device shown in FIG13 is the first terminal device, that is, the first terminal device 101a in the service processing system shown in FIG1, then the processor 1303 can be used to call the computer program in the memory 1304 to perform the following operations: in response to the configuration operation of the first object for the palm payment service, receiving the first palm information for the palm payment service; displaying at least one electronic payment account of the first object; in response to the selection operation of at least one electronic payment account, configuring the selected first electronic payment account as the electronic payment account associated with the first palm information; wherein, when using the palm payment service of the first palm information, the payment processing is performed using the configured first electronic payment account associated with the first palm information.

[0226] If the terminal device shown in Figure 13 is the second terminal device, namely the second terminal device 101b in the service processing system shown in Figure 1, then the processor 1303 can be used to call the computer program in the memory 1304 to perform the following operations: in response to a request operation for the palm payment service, receiving first palm information for the palm payment service; displaying the first electronic payment account configured and associated with the first palm information; and performing payment processing using the first electronic payment account.

[0227] It should be understood that the terminal device described in the embodiments of this application can execute the service processing method described in the corresponding embodiments above, or it can execute the service processing device described in the corresponding embodiments above, which will not be repeated here. In addition, the beneficial effects of using the same method will not be repeated here either.

[0228] Furthermore, it should be noted that this application embodiment also provides a computer-readable storage medium, which stores a computer program, and the computer program includes program instructions. When the processor executes the above program instructions, it can execute the methods in the embodiments corresponding to Figures 2, 4, 6, and 9 above. Therefore, it will not be described again here.

[0229] According to one aspect of this application, a computer program product is provided, comprising a computer program stored in a computer-readable storage medium. A processor of a terminal device reads the computer program from the computer-readable storage medium and executes the computer program, enabling the terminal device to perform the methods described in the embodiments corresponding to Figures 2, 4, 6, and 9 above; therefore, further details will not be provided here.

[0230] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0231] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Those skilled in the art will understand that all or part of the processes for implementing the above embodiments and equivalent variations made in accordance with the claims of this application are still within the scope of this application.

Claims

1. A service processing method, the method being executed by a first terminal device, the method comprising: In response to a configuration operation by a first object for the palm payment service, first palm information for the palm payment service is received. Display at least one electronic payment account of the first object; In response to the selection operation of the at least one electronic payment account, the selected first electronic payment account is configured as an electronic payment account associated with the first palm information; wherein, when using the palm payment service of the first palm information, the payment is processed using the configured first electronic payment account associated with the first palm information.

2. The method of claim 1, wherein, The owner of each of the electronic payment accounts is the first object; the at least one electronic payment account displaying the first object includes: Obtain the object identifier of the first object and display at least one electronic payment account corresponding to the object identifier of the first object; or, Receive at least one account information input by the first object, and display the electronic payment account indicated by each of the account information.

3. The method of claim 1 or 2, wherein, The step of configuring the selected first electronic payment account as an electronic payment account associated with the first palm information in response to the selection operation of the at least one electronic payment account includes: In response to the selection of the at least one electronic payment account, an authentication interface is displayed; The identity verification interface receives the identity verification information corresponding to the selected first electronic payment account and verifies the identity verification information. In response to successful verification of the identity verification information, the selected first electronic payment account is configured as an electronic payment account associated with the first palm information; The identity verification information corresponding to the selected first electronic payment account includes at least one of the following: the payment password of the first electronic payment account, the account identifier of the first electronic payment account, the object identifier corresponding to the first electronic payment account, and the biometric information associated with the first electronic payment account.

4. The method of any one of claims 1 to 3, wherein, The step of displaying an authentication interface in response to the selection of the at least one electronic payment account includes: In response to the selection operation of the at least one electronic payment account, an account authorization prompt message is output; the account authorization prompt message is used to prompt authorization for the selected first electronic payment account; In response to the authorization operation performed on the first electronic payment account, the identity verification interface is displayed.

5. The method of any one of claims 1 to 4, wherein, The method further includes: In response to the first object's palm-adding operation for the palm payment service, the second palm information added for the palm payment service is received. Configure the first electronic payment account as an electronic payment account associated with the second palm information; Wherein, the second palm information and the first palm information are different palm information belonging to the same object; or, the second palm information and the first palm information are palm information belonging to different objects.

6. The method of any one of claims 1 to 5, wherein, The method further includes: In response to the first object's account addition operation for the PalmPay payment service, a second electronic payment account added for the PalmPay payment service is received. Configure the second electronic payment account as an electronic payment account associated with the first palm information; The owner of the second electronic payment account is the first object, and the first electronic payment account is different from the second electronic payment account.

7. The method of any one of claims 1 to 6, wherein, The palm payment service supports configuring N palm information entries, where any one of the N palm information entries is represented as palm information entry n, and n and N are positive integers; the method also includes: managing the N palm information entries; The management of palm information n includes at least one of the following: setting a palm identifier for palm information n, displaying palm information n, deleting palm information n, and modifying palm information n; the palm information n includes one or both of palm print images and palm vein images.

8. The method of any one of claims 1 to 7, wherein, The palm payment service supports configuring M electronic payment accounts associated with the first palm information for payment processing; let any one of the M electronic payment accounts be represented as electronic payment account m, where m and M are both positive integers, and m is less than or equal to M; the method further includes: managing the M electronic payment accounts; The management of electronic payment account m includes at least one of the following: setting an account identifier for electronic payment account m, displaying electronic payment account m, deleting electronic payment account m, setting the payment priority of electronic payment account m, setting the payment limit of electronic payment account m, and setting the payment permissions of electronic payment account m.

9. The method of any one of claims 1 to 8, wherein, The palm payment service is configured with M electronic payment accounts associated with the first palm information for payment processing; let any one of the M electronic payment accounts be represented as electronic payment account m, and the method further includes: In response to a bill viewing operation on the electronic payment account m, the bill under the electronic payment account m is displayed; the bill under the electronic payment account m is used to record at least one transaction involved in the payment processing using the electronic payment account m in the swipe payment service.

10. The method of any one of claims 1 to 9, wherein, The payment limit settings include at least one of the following: daily payment limit, weekly payment limit, monthly payment limit, and annual payment limit; the payment permissions include at least one of the following: allowed time period and allowed at least one object.

11. The method of any one of claims 1 to 10, wherein, The method further includes: In response to a configuration operation of the first object for the swipe payment service, the configuration information of the first object for the swipe payment service is queried; the configuration information is used to indicate the configuration status of the first object for the swipe payment service. Based on the configuration information indicated by the configuration information, the first object is configured with information.

12. The method of any one of claims 1 to 11, wherein, The palm payment service is provided by a first application; the configuration of the first object based on the configuration information includes: In response to the configuration situation indicated by the configuration information being the first configuration situation, if the object identifier of the first object is confirmed to be authorized, the account of the first object in the first application is associated with the object identifier of the first object; the first configuration situation is: the account of the first object in the first application is not associated with the object identifier of the first object.

13. The method of any one of claims 1 to 12, wherein, The step of configuring information for the first object based on the configuration information indicated by the configuration information includes: In response to the configuration state indicated by the configuration information being the second configuration state, a palm image of the first object is collected; the second configuration state is: the first object has not recorded the first palm information for the palm payment service; Feature extraction is performed on the palm image to obtain the first palm information.

14. The method of any one of claims 1 to 13, wherein, The step of configuring information for the first object based on the configuration information indicated by the configuration information includes: In response to the configuration status indicated by the configuration information being the third configuration status, the activation permission of the electronic payment account of the first object is queried; the third configuration status is: the first palm information is not associated with any electronic payment account; If the enable permission indicates that the electronic payment account is enabled, obtain at least one electronic payment account of the first object.

15. A service processing method, the method being executed by a second terminal device, the method comprising: In response to a request operation for the palm payment service, first palm information for the palm payment service is received; Displays the first electronic payment account that has been configured and associated with the first palm information; The payment is processed using the first electronic payment account.

16. The method of claim 15, wherein, The first palm information is also associated with a second electronic payment account, and the method further includes: Displays the configured second electronic payment account associated with the first palm information; In response to the selection of the second electronic payment account, the payment is processed using the second electronic payment account; In response to the selection of the first electronic payment account, the step of processing payment using the first electronic payment account is triggered.

17. The method of claim 15 or 16, wherein, The palm payment service is provided by a first application, and the request operation is received by a second terminal device; the method further includes: In response to retrieving target palm information that matches the first palm information from the first feature library, a recognition result is determined based on the object associated with the target palm information; wherein, the first feature library is used to store at least one set of palm information collected by the second terminal device; each set of palm information includes a palm print image and a palm vein image; each set of palm information is associated with an object; The first object is authenticated based on the identification result; In response to a successful authentication result, at least one electronic payment account associated with the first palm information is queried.

18. The method of any one of claims 15 to 17, wherein, The method further includes: In response to the failure to find palm information matching the first palm information in the first feature library, a search is performed in the second feature library; wherein, the second feature library is used to store at least one palm information collected by the first terminal device; the first terminal device is used to receive configuration operations for the palm payment service; each palm information includes a palm print image, and each palm information is associated with an object; In response to retrieving target palm information that matches the first palm information from the second feature library, the recognition result is determined based on the object associated with the target palm information; In response to the failure to retrieve target palm information that matches the first palm information from the second feature library, a configuration request for the palm payment service is generated.

19. A service processing apparatus, comprising: The first transceiver unit is configured to receive first palm information for the palm payment service in response to a configuration operation of the first object for the palm payment service. The first display unit is configured to display at least one electronic payment account of the first object; The configuration unit is configured to, in response to the selection operation of the at least one electronic payment account, configure the selected first electronic payment account as an electronic payment account associated with the first palm information; wherein, when using the palm payment service of the first palm information, the configured first electronic payment account associated with the first palm information is used for payment processing.

20. A service processing apparatus, comprising: The second transceiver unit is configured to receive first palm information for the palm payment service in response to a request operation for the palm payment service. The second display unit is configured to display the first electronic payment account that has been configured and associated with the first palm information; The payment unit is configured to process payments using the first electronic payment account.

21. A first terminal device, comprising: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in the memory, implements the service processing method as described in any one of claims 1 to 14.

22. A second terminal device, comprising: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in the memory, implements the service processing method as described in any one of claims 15 to 18.

23. A computer-readable storage medium storing computer-executable instructions or a computer program that, when executed by a processor, implements the service processing method as described in any one of claims 1 to 18.

24. A computer program product comprising a computer program or computer-executable instructions, wherein when executed by a processor, the computer program or computer-executable instructions implement the service processing method as described in any one of claims 1 to 18.

Images