Account aggregation payment method, system, electronic device, readable medium and product

Abstract

Embodiments of the present disclosure disclose account aggregation payment methods, systems, electronic devices, readable media and products. A specific embodiment of the method comprises: in response to detecting a user face login operation, obtaining face information call credentials; in response to determining that the device state representation of the corresponding item circulation applet of the self-service device end is in an activated state, obtaining face information; according to the user token, obtaining user identification information from the self-service server corresponding to the self-service device end; in response to determining that the user relationship result represents that the user identification corresponds to a user who has opened a face member account of the corresponding target platform and item circulation application, logging the user account corresponding to the user identification as the aggregation user account of the corresponding face member account on the self-service device end; in response to detecting a payment operation, displaying a payment method selection window. This embodiment is related to cloud payment, and can integrate the face member account and the member account opened in other ways to integrate the payment related data of the same user.

Description

Technical Field

[0001] Embodiments of this disclosure relate to the field of computer technology, and more specifically to account aggregation payment methods, systems, electronic devices, readable media, and products. Background Technology

[0002] Within a membership system of a goods circulation application, the organizer can centrally manage its member accounts. Currently, when users make payments, the common method is to log in using a pre-activated facial recognition membership.

[0003] However, the inventors discovered that when using the above method, the following technical problems often occur: member accounts that log in using facial recognition cannot be linked with member accounts opened by other methods, and there are many cases where a user has multiple member accounts, resulting in the inability to integrate the payment-related data of the same user.

[0004] The information disclosed in this background section is only intended to enhance the understanding of the background of the inventive concept, and therefore may contain information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] The summary portion of this disclosure is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description portion. This summary portion is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0006] Some embodiments of this disclosure provide account aggregation payment methods, account aggregation payment systems, electronic devices, computer-readable media, and computer program products to solve one or more of the technical problems mentioned in the background section above.

[0007] In a first aspect, some embodiments of this disclosure provide an account aggregation payment method, which includes: in response to detecting a user's face login operation, obtaining a face information retrieval credential from a platform server corresponding to a target platform, wherein the user's face login operation corresponds to a goods circulation mini-program, the goods circulation mini-program corresponds to a goods circulation application, and the self-service device integrates a software development kit corresponding to the face recognition service of the target platform; in response to determining that the device status representation of the goods circulation mini-program corresponding to the self-service device is active, obtaining face information based on the face information retrieval credential, wherein the face information includes a user token. Based on the aforementioned user token, user identification information is obtained from the self-service terminal corresponding to the aforementioned self-service device. This user identification information includes the user identification corresponding to the aforementioned self-service terminal and the user relationship result. In response to determining that the user relationship result indicates the user corresponding to the user identification has activated a facial recognition membership account corresponding to the aforementioned target platform and the aforementioned goods circulation application, the user account corresponding to the aforementioned user identification is logged into the aforementioned self-service device as an aggregated user account corresponding to the aforementioned facial recognition membership account. In response to detecting a payment operation, a payment method selection window for the corresponding aggregated user account is displayed, allowing the user to select a payment method and make the payment.

[0008] Optionally, before displaying the payment method selection window for the corresponding aggregated user account in response to the detection of a payment operation, allowing the user to select a payment method and make payment, the method further includes: in response to determining that the user relationship result indicates that the user corresponding to the user identifier has not activated the corresponding face recognition membership account for the target platform and the goods circulation application, obtaining user code information; querying the membership account corresponding to the user code information to obtain a first membership query result; in response to determining that the first membership query result indicates that there is no membership account, calling the membership registration interface to obtain a first membership registration result; determining the user account corresponding to the first membership registration result on the self-service terminal as the aggregated user account; storing the determined aggregated user account and the membership relationship information corresponding to the user code information on the self-service terminal; and logging into the aggregated user account on the self-service terminal.

[0009] Optionally, the above query for the member account corresponding to the above user code information to obtain the first member query result includes: in response to determining that the network mode of the above self-service terminal includes a local area network mode, querying the member account corresponding to the above user code information in the local area network mode to obtain the first member query result; and synchronizing the above first member query result to the above self-service terminal via the public network.

[0010] Optionally, calling the member registration interface to obtain the first member registration result includes: in response to determining that the network mode of the self-service terminal includes a local area network (LAN) mode, calling the member registration interface of the corresponding member registration server in the LAN mode to obtain the first member registration result; and synchronizing the first member registration result to the self-service terminal via the public network.

[0011] Optionally, before displaying the payment method selection window for the corresponding aggregated user account in response to the detection of a payment operation, allowing the user to select a payment method and make payment, the method further includes: in response to the detection of a user's QR code login operation, obtaining a member login code from the self-service terminal; in response to the detection of a QR code scanning result corresponding to the member login code, querying the member account corresponding to the QR code scanning result to obtain a second member query result; in response to determining that the second member query result indicates no member account, calling the member registration interface to obtain a second member registration result; identifying the user account on the self-service terminal corresponding to the second member registration result as the aggregated user account; storing the identified aggregated user account and the member relationship information corresponding to the QR code scanning result on the self-service terminal; and logging into the aggregated user account on the self-service terminal.

[0012] Optionally, the above-mentioned response to detecting a payment operation, displaying a payment method selection window for the corresponding aggregated user account, for the user to select a payment method and make payment, includes: in response to detecting a payment operation, obtaining information on each payment method associated with the aggregated user account from the self-service terminal; displaying each payment method selection control corresponding to the above-mentioned payment method information in the payment method selection window; and in response to detecting a selection operation performed on the payment method selection control in the above-mentioned payment method selection controls, displaying a payment window, wherein the payment window corresponds to the payment method information corresponding to the selected payment method selection control.

[0013] Optionally, before obtaining the facial information credential from the platform server corresponding to the target platform, the method further includes: initializing the aforementioned goods circulation mini-program; preloading the initialized goods circulation mini-program; and initializing the software development kit corresponding to the aforementioned facial recognition service.

[0014] Optionally, the aforementioned payment method information includes virtual card payment information corresponding to the self-service terminal and the joint payment terminal. The virtual card payment information includes a virtual card identifier, which is associated with the user account of the self-service terminal. The virtual card corresponding to the virtual card identifier is activated by the user terminal through the following steps: determining whether the user terminal supports the payment method corresponding to the joint payment terminal; in response to determining that the user terminal supports the payment method corresponding to the joint payment terminal, sending the user terminal's device information to the joint payment terminal for device verification, and obtaining a device verification result; in response to determining that the device verification result indicates successful verification, sending an account opening request to the self-service terminal for user verification, and obtaining a first user verification result; in response to detecting that the first user verification result indicates successful verification, sending a card application request to the joint payment terminal for user verification, and obtaining a second user verification result; in response to determining that the second user verification result indicates successful verification, sending a virtual card activation request to the joint payment terminal for virtual card activation, and obtaining a virtual card identifier, so that the joint payment terminal writes the virtual card identifier into the device information.

[0015] Optionally, the method further includes: in response to detecting a selection operation of a payment control applied to the corresponding target virtual card identifier displayed in the payment window, obtaining device information of the user terminal as device information to be verified; obtaining at least one device information corresponding to the target virtual card identifier as a pre-stored device information set; in response to determining that the device information to be verified exists in the pre-stored device information set, determining that the user terminal has passed the payment device verification; and in response to determining that the user terminal has passed the payment device verification, initiating a payment deduction request to the joint payment service.

[0016] Secondly, some embodiments of this disclosure provide an account aggregation payment system, the system comprising: a self-service device terminal configured to execute the method described in any implementation of the first aspect; a self-service terminal configured to respond to requests from the self-service device terminal; and a platform server terminal configured to provide mini-program services and facial recognition services.

[0017] Thirdly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation of the first aspect above.

[0018] Fourthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0019] Fifthly, some embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0020] The above embodiments of this disclosure have the following beneficial effects: The account aggregation payment method of some embodiments of this disclosure can connect facial recognition membership accounts with membership accounts opened through other means, thereby integrating the payment-related data of the same user. Specifically, the reason why the payment-related data of the same user cannot be integrated is that membership accounts using facial recognition login cannot be connected with membership accounts opened through other means, and there are many cases where a user has multiple membership accounts, resulting in the inability to integrate the payment-related data of the same user. Based on this, the account aggregation payment method of some embodiments of this disclosure firstly, in response to detecting a user's facial recognition login operation, obtains a facial information retrieval credential from the platform server corresponding to the target platform. The user's facial recognition login operation corresponds to a goods circulation mini-program, the goods circulation mini-program corresponds to a goods circulation application, and the self-service device integrates the software development kit corresponding to the facial recognition service of the target platform. Thus, a credential for obtaining facial information can be obtained in advance. Then, in response to determining that the device status representation of the goods circulation mini-program corresponding to the self-service device is active, facial information is obtained according to the facial information retrieval credential, wherein the facial information includes a user token. Therefore, the user's facial information on the aforementioned target platform can be obtained while the device is currently activated. Secondly, based on the user token, user identification information is obtained from the self-service terminal corresponding to the self-service device. This user identification information includes the user identifier corresponding to the self-service terminal and the user relationship result. Thus, the user's user identifier on the self-service terminal and the user relationship result indicating whether the user has activated a facial recognition membership account can be obtained based on the obtained user token. Next, in response to determining that the user relationship result indicates the user identifier has activated a facial recognition membership account for the aforementioned target platform and the aforementioned goods circulation application, the user account corresponding to the user identifier is logged into the self-service terminal as the aggregated user account for the aforementioned facial recognition membership account. Thus, after determining that the user relationship result indicates the user has activated a facial recognition membership account, the user account on the self-service terminal can be used as the aggregated user account for login after facial recognition. Finally, in response to detecting a payment operation, a payment method selection window for the corresponding aggregated user account is displayed, allowing the user to select a payment method and make a payment. Thus, after logging into the aggregated user account, payment can be made using the aggregated user account's payment method. Because when users log in via facial recognition, they are actually logging into the associated self-service terminal user account. This means that facial recognition membership accounts can be aggregated under the self-service terminal user account level, allowing payments to be made within this aggregated self-service terminal user account level. This effectively connects facial recognition membership accounts and self-service terminal user accounts, reducing the likelihood of a user having multiple membership accounts and enabling the merging of user payment-related data under the self-service terminal user account level. Attached Figure Description

[0021] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0022] Figure 1 This is an architecture diagram of an exemplary system to which some embodiments of this disclosure can be applied;

[0023] Figure 2 This is a flowchart of some embodiments of the account aggregation payment method according to this disclosure;

[0024] Figure 3 This is a flowchart of some other embodiments of the account aggregation payment method according to this disclosure;

[0025] Figure 4 This is a structural diagram of some embodiments of the account aggregation payment system according to this disclosure;

[0026] Figure 5 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation

[0027] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0028] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0029] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0030] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0031] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0032] Before performing any of the operations involving the collection, storage, or use of user personal information (such as facial information, user identifiers, and user accounts) disclosed in this disclosure, the relevant organizations or individuals shall fulfill their obligations, including conducting personal information security impact assessments, informing personal information subjects, and obtaining prior authorization and consent from personal information subjects.

[0033] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0034] Figure 1 An exemplary system architecture 100 is shown that can be applied to an account aggregation payment method or account aggregation payment system according to some embodiments of the present disclosure.

[0035] like Figure 1 As shown, the system architecture 100 may include user terminal devices 101, 102, and 103, self-service terminal device 104, local area network 105, public network 106, internal server 107, self-service terminal server 108, and platform server 109. The public network 106 serves as the medium for providing communication links between user terminal devices 101, 102, and 103 and self-service terminal device 104, between self-service terminal device 104 and self-service terminal server 108, and between self-service terminal device 104 and platform server 109. The local area network 105 serves as the medium for providing a communication link between self-service terminal device 104 and internal server 107. The local area network 105 and the public network 106 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0036] Users can use user-end devices 101, 102, and 103 to interact with self-service terminal device 104 via public network 106 to receive or send messages, etc. Various communication client applications can be installed on user-end devices 101, 102, and 103, such as web browser applications, goods circulation applications, quick payment applications, search applications, instant messaging tools, email clients, social media platform software, etc. User-end devices 101, 102, and 103 can include, but are not limited to, mobile phones, tablets, watches, and wristbands. Self-service terminal device 104 can have a goods circulation application installed for users to self-check and pay for goods. Self-service terminal device 104 can also run mini-program applications.

[0037] The self-service terminal device 104 can be either hardware or software. When the self-service terminal device 104 is hardware, it can be various electronic devices with a display screen and support barcode recognition, including but not limited to self-checkout machines. When the self-service terminal device 104 is software, it can be installed in the electronic devices listed above. It can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or it can be implemented as a single software program or software module. No specific limitations are made here.

[0038] The self-service server 108 can be a server providing various services, such as a backend server supporting the information displayed on the self-service device 104. The backend server can analyze and process received requests and other data, and then return the processing results to the self-service device 104. The internal server 107 can be a server providing various services in a local area network (LAN) mode. The platform server 109 can be a server providing facial recognition services corresponding to the target platform.

[0039] It should be noted that the internal server 107, self-service server 108, and platform server 109 can be either hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the server is software, it can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.

[0040] It should be understood that Figure 1 The number of client devices, self-service devices, local area networks, public networks, and servers shown in the diagram is merely illustrative. Depending on implementation needs, any number of client devices, self-service devices, local area networks, public networks, and servers can be included.

[0041] Continue to refer to Figure 2 The diagram illustrates a flow 200 of some embodiments of the account aggregation payment method according to this disclosure. This account aggregation payment method, applied to a self-service device, includes the following steps:

[0042] Step 201: In response to detecting a user's face login operation, obtain the face information access credential from the platform server corresponding to the target platform.

[0043] In some embodiments, the entity executing the account aggregation payment method (e.g.) Figure 1The self-service terminal device 104 shown can obtain a facial information credential from the platform server corresponding to the target platform in response to detecting a user's facial login operation. The aforementioned user facial login operation can be an operation used to log in to a goods circulation mini-program using facial recognition. For example, the user facial login operation can be a selection operation on the facial login control displayed on the self-service terminal device. The aforementioned self-service terminal includes a self-service terminal device. The aforementioned self-service terminal integrates a software development kit corresponding to the facial recognition service of the target platform, thereby enabling users to use the facial recognition service of the target platform on the self-service terminal. The target platform can be an instant messaging software platform, and various mini-programs can be integrated into the application corresponding to the target platform. The goods circulation mini-program can be a goods circulation mini-program application for physical merchants placed on the self-service terminal. The goods circulation application can be a goods management application. Users can log in to their member accounts, view goods, place orders, and make payments through the goods circulation mini-program and the goods circulation terminal application. The mini-program running in the self-service terminal can be a hardware mini-program. Hardware mini-programs can be a series of hardware mini-program frameworks specifically developed for B2B hardware devices. They can implement some of the functions of mobile mini-programs, facilitating device use by physical merchants. In practice, the aforementioned execution entity can first call the encrypted text acquisition interface included in the aforementioned software development kit to obtain the encrypted text. For example, the interface name of the encrypted text acquisition interface can be "getWxpayfaceRawdata". Then, the encrypted text can be sent to the aforementioned platform server, and the platform server can send a face information retrieval credential corresponding to the encrypted text. The face information retrieval credential may include a unique authorization code. Optionally, the face information retrieval credential may also include the environment configuration information of the self-service device, the application identifier applied for in the target platform, the identifier of the bound mini-program, and the merchant number corresponding to the official account.

[0044] Optionally, before obtaining the facial information credential from the platform server corresponding to the target platform, the aforementioned executing entity can also initialize the aforementioned goods circulation mini-program. In practice, the aforementioned executing entity can call the initialization interface of the mini-program framework to initialize the aforementioned goods circulation mini-program. Then, the initialized goods circulation mini-program can be preloaded. In practice, the aforementioned executing entity can call the mini-program preloading interface to preload the general resources of the goods circulation mini-program. General resources can include, but are not limited to, at least one of the following: text, images, and videos. Secondly, the software development kit (SDK) corresponding to the aforementioned facial recognition service can be initialized. In practice, initialization can be performed through the initialization interface of the SSD to release the camera from its occupancy and clear the previously cached user facial images in order to perform this facial recognition operation.

[0045] Step 202: In response to determining the activation status of the device status representation of the corresponding item circulation mini-program on the self-service device, retrieve the facial information by calling the credential based on the facial information.

[0046] In some embodiments, the executing entity may, in response to determining the activation status of the device state of the self-service device corresponding to the item circulation mini-program, obtain facial information based on the facial information retrieval credential. The device state can indicate whether the self-service device is active. In practice, the executing entity may first initialize each facial recognition retrieval parameter using the application identifier, merchant number, and unique authorization code included in the facial information retrieval credential. Then, it may call the facial information acquisition interface. The facial information acquisition interface can be an interface used to obtain user-related information of the target platform corresponding to the facial recognition user. The interface name of the facial information acquisition interface can be "authorizeByWxFacePay". The facial information may include a user token, and may also include a platform user identifier and / or platform user nickname corresponding to the target platform. The user token can serve as the unique identifier of the current user.

[0047] Optionally, before step 203, the aforementioned executing entity can first determine whether an activation token exists locally. In practice, this can be determined through the mini-program framework. The activation token can be saved after being issued by calling the device activation interface. Then, in response to determining that an activation token exists locally, the activation status of the self-service device can be checked through the mini-program framework. Next, in response to determining that the device status indicates an inactive state, the device activation interface of the mini-program framework can be called to activate the self-service device. The interface name of the device activation interface can be "activateDeviceBylo".

[0048] Step 203: Obtain user identification information from the self-service terminal of the corresponding self-service device based on the user token.

[0049] In some embodiments, the executing entity can obtain user identification information from the self-service terminal corresponding to the self-service device based on the user token. The user identification information includes the user identifier corresponding to the self-service terminal and the user relationship result. Once a user on the self-service terminal activates a facial recognition membership account for the target platform and the goods circulation application, the user can log in to the goods circulation application's facial recognition membership account using the target platform's facial recognition service. Their user token, platform user identifier, and platform user nickname can be written into the account information corresponding to the user account on the self-service terminal for subsequent queries. The user identifier corresponding to the self-service terminal can be a unique identifier for the user on the self-service terminal. The user relationship result indicates whether the user has activated a facial recognition membership account for the target platform.

[0050] Step 204: In response to determining that the user relationship result represents the user identifier corresponding to the user has opened a face membership account for the corresponding target platform and the item circulation application, log in to the self-service device terminal as the aggregated user account of the corresponding face membership account for the user identifier.

[0051] In some embodiments, the executing entity may, in response to determining that the user relationship result indicates that the user corresponding to the user identifier has activated a facial recognition membership account corresponding to the target platform and the goods circulation application, log in the user account corresponding to the user identifier as an aggregated user account corresponding to the facial recognition membership account on the self-service device. In practice, the executing entity may call the account login interface of the self-service terminal to log in the aggregated user account on the self-service device.

[0052] Optionally, prior to step 205, the aforementioned executing entity may also perform the following steps:

[0053] The first step, in response to the determination that the user relationship result indicates the user identifier has not activated the corresponding facial recognition membership account for the target platform and the goods circulation application, is to obtain the user identification number. This user identification number can be the user's mobile phone number or membership card number. In practice, in response to detecting a user's membership card number input or swiping operation, the executing entity can obtain the membership card number as the user identification number. The membership card number can be entered by the user or read from the membership card. The executing entity can also, in response to detecting a user's mobile phone number input, use the entered mobile phone number as the user identification number.

[0054] The second step is to query the member account corresponding to the aforementioned user code information to obtain the first member query result. In practice, the executing entity can respond to the determination that the network mode of the self-service terminal includes LAN mode, and query the member account corresponding to the aforementioned user code information in LAN mode to obtain the first member query result. Specifically, the executing entity can call the member query interface under LAN to query the member account corresponding to the aforementioned user code information. The member query interface can be an interface under the ISV service. Then, the first member query result can be synchronized to the aforementioned self-service terminal via the public network, so that the self-service terminal synchronizes the member query result in LAN mode. Optionally, the executing entity can respond to the determination that the network mode of the aforementioned self-service terminal only includes public network mode, and call the member query interface under public network to query the member account corresponding to the aforementioned user code information to obtain the first member query result. The member query interface under public network can be an interface of the self-service terminal.

[0055] The third step involves, in response to the determination that the first member query result indicates no member account, calling the member registration interface to obtain the first member registration result. In practice, the executing entity can, in response to the determination that the network mode of the self-service terminal includes LAN mode, call the member registration interface of the corresponding member registration server in LAN mode to obtain the first member registration result. Specifically, the member registration server can be the server corresponding to the ISV service. The member registration interface can meet the ISV standard. Then, the first member registration result can be synchronized to the self-service terminal via the public network. Optionally, the executing entity can, in response to the determination that the network mode of the self-service terminal only includes public network mode, call the member registration interface under the public network to obtain the first member registration result. The member registration interface under the public network can be the interface of the self-service terminal. Member account query and registration in public network mode can be encapsulated in a registration query interface.

[0056] The fourth step is to identify the user account corresponding to the first member registration result as the aggregated user account.

[0057] The fifth step is to store the membership relationship information corresponding to the identified aggregated user accounts and the aforementioned user code information in the self-service terminal. Membership relationship information can represent the association between the aggregated user accounts and the aforementioned user code information. Membership relationship information may include the aggregated user accounts and the aforementioned user code information.

[0058] Step 6: Log in to the aggregated user account on the aforementioned self-service device. In practice, the executing entity can call the account login interface in LAN mode to obtain the first login result. The account login interface called in LAN mode can be the interface of the ISV server. The first login result can be in encrypted form. Then, the first login result can be synchronized to the self-service terminal via the public network. The executing entity can also call the account login interface in public network mode to obtain the first login result. The account login interface called in public network mode can be the interface of the self-service terminal. The account login interface of the self-service terminal can further call the account login interface of the ISV server. Thus, when a user on the self-service terminal activates a member account for the goods circulation application using a mobile phone number or membership card, the user can log in to the member account of the goods circulation application using their mobile phone number or membership card number. Their mobile phone number and membership card number can be written into the account information corresponding to the user account on the self-service terminal for subsequent querying.

[0059] Optionally, in response to determining that the first member query result indicates the existence of a member account, the aforementioned executing entity may designate the user account corresponding to the first member query result on the self-service terminal as an aggregated user account. Then, the determined aggregated user account and the member relationship information corresponding to the aforementioned user code information can be stored on the self-service terminal. Finally, the aggregated user account can be logged into on the self-service terminal. Thus, when a member account is searchable, the aggregated user account can be directly logged into on the self-service terminal.

[0060] Optionally, prior to step 205, the aforementioned executing entity may perform the following steps:

[0061] The first step, in response to detecting a user's QR code login operation, is to obtain a member login code from the aforementioned self-service terminal. This user QR code login operation can be a selection operation applied to a QR code login control. The QR code login control can include a mini-program QR code control and / or a public account QR code control. In practice, when the user QR code login operation is a selection operation applied to a mini-program QR code control, the executing entity can obtain a mini-program member login code from the aforementioned self-service terminal as the member login code. When the user QR code login operation is a selection operation applied to a public account QR code control, the executing entity can obtain a public account member login code from the aforementioned self-service terminal as the member login code.

[0062] The second step involves responding to the detection of a scan result corresponding to the aforementioned member login code. Based on this scan result, the corresponding member account is queried to obtain the second member query result. Users can scan the member login code displayed on the self-service device using a scan control within a mini-program on their user device. Alternatively, users can scan the member login code displayed on the self-service device using a scan control within a public account on their user device. The scan result may include the scan user identifier of the corresponding mini-program or public account. For example, when the mini-program or public account is integrated into the target platform, the scan user identifier can be the user's platform user identifier on the target platform. In practice, the executing entity can respond to the determination that the network mode of the self-service terminal includes a local area network (LAN) mode, and query the member account corresponding to the scan user identifier in LAN mode to obtain the second member query result. Specifically, the executing entity can call the member query interface under the LAN to query the member account corresponding to the scan user identifier. The member query interface can be an interface under the ISV service. Then, the second member query result can be synchronized to the self-service terminal via the public network, allowing the self-service terminal to synchronize the member query result under LAN mode. Optionally, in response to determining that the network mode of the self-service terminal only includes the public network mode, the aforementioned executing entity may call the member query interface under the public network to query the member account corresponding to the aforementioned scanned user identifier, and obtain the second member query result. The member query interface under the public network can be the interface of the self-service terminal.

[0063] The third step involves, in response to the determination that the second member query result indicates no member account, calling the member registration interface to obtain the second member registration result. In practice, the executing entity can, in response to the determination that the network mode of the self-service terminal includes LAN mode, call the member registration interface of the corresponding member registration server in LAN mode to obtain the second member registration result. Specifically, the member registration server can be the server corresponding to the ISV service. The member registration interface can meet the ISV standard. Then, the second member registration result can be synchronized to the self-service terminal via the public network. Optionally, the executing entity can, in response to the determination that the network mode of the self-service terminal only includes public network mode, call the member registration interface under the public network to obtain the second member registration result. The member registration interface under the public network can be the interface of the self-service terminal.

[0064] The fourth step is to identify the user account corresponding to the above-mentioned self-service terminal as the aggregated user account, based on the above-mentioned second member registration result.

[0065] The fifth step involves storing the identified aggregated user accounts and the corresponding membership relationship information for the scanned results in the self-service terminal. Membership relationship information can represent the association between the aggregated user accounts and the scanned results. This information may include the aggregated user accounts and the scanned user identifiers.

[0066] Step 6: Log in to the aggregated user account on the aforementioned self-service device. In practice, the executing entity can call the account login interface in LAN mode to obtain the second login result. The account login interface called in LAN mode can be the interface of the ISV server. The first login result can be in encrypted form. Then, the second login result can be synchronized to the self-service terminal via the public network. The executing entity can also call the account login interface in public network mode to obtain the second login result. The account login interface called in public network mode can be the interface of the self-service terminal. The account login interface of the self-service terminal can further call the account login interface of the ISV server. Therefore, when a user on the self-service terminal activates a member account for the goods circulation application by scanning a QR code, the user can log in to the member account of the goods circulation application by scanning a QR code. The user's QR code identifier can be written into the account information corresponding to the user account on the self-service terminal for subsequent querying.

[0067] Optionally, in response to determining that the second member query result indicates the existence of a member account, the aforementioned executing entity may designate the user account corresponding to the second member query result on the self-service terminal as an aggregated user account. Then, the determined aggregated user account and the member relationship information corresponding to the aforementioned user code information can be stored on the self-service terminal. Finally, the aggregated user account can be logged into on the self-service terminal. Therefore, when a member account can be found by scanning a QR code, the aggregated user account can be directly logged into on the self-service terminal.

[0068] It should be noted that the member account can be the account registered by the user for the item circulation application.

[0069] Step 205: In response to the detection of a payment operation, a payment method selection window for the corresponding aggregated user account is displayed so that the user can select a payment method and make the payment.

[0070] In some embodiments, the aforementioned executing entity may, in response to detecting a payment operation, display a payment method selection window for the corresponding aggregated user account, allowing the user to select a payment method and proceed with the payment. The payment operation may be a user's selection of an order payment control for an order. An order may consist of individual items scanned by the user. In practice, the aforementioned executing entity may display the payment method selection window for the corresponding aggregated user account in the form of a pop-up window.

[0071] The above embodiments of this disclosure have the following beneficial effects: The account aggregation payment method of some embodiments of this disclosure can connect facial recognition membership accounts with membership accounts opened through other means, thereby integrating the payment-related data of the same user. Specifically, the reason why the payment-related data of the same user cannot be integrated is that membership accounts using facial recognition login cannot be connected with membership accounts opened through other means, and there are many cases where a user has multiple membership accounts, resulting in the inability to integrate the payment-related data of the same user. Based on this, the account aggregation payment method of some embodiments of this disclosure firstly, in response to detecting a user's facial recognition login operation, obtains a facial information retrieval credential from the platform server corresponding to the target platform. The user's facial recognition login operation corresponds to a goods circulation mini-program, the goods circulation mini-program corresponds to a goods circulation application, and the self-service device integrates the software development kit corresponding to the facial recognition service of the target platform. Thus, a credential for obtaining facial information can be obtained in advance. Then, in response to determining that the device status representation of the goods circulation mini-program corresponding to the self-service device is active, facial information is obtained according to the facial information retrieval credential, wherein the facial information includes a user token. Therefore, the user's facial information on the aforementioned target platform can be obtained while the device is currently activated. Secondly, based on the user token, user identification information is obtained from the self-service terminal corresponding to the self-service device. This user identification information includes the user identifier corresponding to the self-service terminal and the user relationship result. Thus, the user's user identifier on the self-service terminal and the user relationship result indicating whether the user has activated a facial recognition membership account can be obtained based on the obtained user token. Next, in response to determining that the user relationship result indicates the user identifier has activated a facial recognition membership account for the aforementioned target platform and the aforementioned goods circulation application, the user account corresponding to the user identifier is logged into the self-service terminal as the aggregated user account for the aforementioned facial recognition membership account. Thus, after determining that the user relationship result indicates the user has activated a facial recognition membership account, the user account on the self-service terminal can be used as the aggregated user account for login after facial recognition. Finally, in response to detecting a payment operation, a payment method selection window for the corresponding aggregated user account is displayed, allowing the user to select a payment method and make a payment. Thus, after logging into the aggregated user account, payment can be made using the aggregated user account's payment method. Because when users log in via facial recognition, they are actually logging into the associated self-service terminal user account. This means that facial recognition membership accounts can be aggregated under the self-service terminal user account level, allowing payments to be made within this aggregated self-service terminal user account level. This effectively connects facial recognition membership accounts and self-service terminal user accounts, reducing the likelihood of a user having multiple membership accounts and enabling the merging of user payment-related data under the self-service terminal user account level.

[0072] Further reference Figure 3 This illustrates a flow 300 of another embodiment of the account aggregation payment method. Flow 300 of the account aggregation payment method includes the following steps:

[0073] Step 301: In response to detecting a user's face login operation, obtain the face information access credential from the platform server corresponding to the target platform.

[0074] Step 302: In response to determining the activation status of the device status representation of the corresponding item circulation mini-program on the self-service device, retrieve the facial information by calling the credential based on the facial information.

[0075] Step 303: Obtain user identification information from the self-service terminal of the corresponding self-service device based on the user token.

[0076] Step 304: In response to determining that the user relationship result represents the user identifier corresponding to the user has opened a face membership account for the corresponding target platform and the item circulation application, log in to the self-service device terminal as the aggregated user account of the corresponding face membership account for the user identifier.

[0077] In some embodiments, the specific implementation of steps 301-304 and the resulting technical effects can be found in [reference needed]. Figure 2 Steps 201-204 in the corresponding embodiments will not be repeated here.

[0078] Step 305: In response to the detection of a payment operation, obtain information on each payment method associated with the aggregated user account from the self-service terminal.

[0079] In some embodiments, the entity executing the account aggregation payment method (e.g.) Figure 1 The self-service terminal device 104 shown can, in response to detecting a payment operation, obtain information on various payment methods associated with the aggregated user account from the self-service terminal. This information on each payment method can represent the payment methods previously added by the user. The payment method information may include a payment account identifier. For example, when the payment method is bank card payment, the payment method information may include the bank name and bank card number. When the payment method is QR code payment, the payment method information may include the scanning application identifier and the QR code image. When the payment method is facial recognition payment, the payment method information may include the facial recognition application identifier. Facial recognition payment may include facial recognition payment corresponding to the target platform, or it may include facial recognition payment corresponding to the self-service terminal. When the payment method is a credit card payment, the payment method information may include the credit card account. When the payment method is fingerprint payment, the payment method information may include the fingerprint identifier to be detected. All of the above payment method information is configured or bound by the user corresponding to the aggregated user account in the application corresponding to the self-service terminal.

[0080] Optionally, the payment method information mentioned above includes virtual card payment information corresponding to the self-service terminal and the joint payment terminal. The virtual card payment information includes a virtual card identifier. The joint payment terminal can be a UnionPay terminal. The virtual card identifier is associated with the user account of the self-service terminal.

[0081] The virtual card corresponding to the above virtual card identifier is activated by the user through the following steps:

[0082] The first step is to determine whether the aforementioned user terminal supports the payment methods corresponding to the aforementioned joint payment server. In practice, the user terminal can determine whether its current device supports HCE (Host-based Card Emulation) or TSM (Trusted Service Manager). Then, in response to the determination that HCE or TSM is supported, it can be determined that the aforementioned user terminal supports the payment methods corresponding to the aforementioned joint payment server.

[0083] The second step involves, in response to the confirmation that the aforementioned user terminal supports the payment methods corresponding to the aforementioned joint payment server, sending the device information of the aforementioned user terminal to the aforementioned joint payment server for device verification, and obtaining the device verification result. Device information may include the device model. The device model may include the device brand and device name.

[0084] Third, in response to the confirmation that the above device verification result indicates successful verification, the account opening request is sent to the self-service terminal for user verification, obtaining the first user verification result. The account opening request can be a request to open a virtual card using the user account on the self-service terminal. The self-service terminal can perform real-name verification on the user account logged in on the user terminal, obtaining the first user verification result.

[0085] Fourth, in response to the detection of the first user verification result indicating successful verification, the card application request is sent to the aforementioned joint payment server for user verification, obtaining the second user verification result. The card application request can represent a request to the joint payment server to open a virtual card. The joint payment server can perform real-name verification on the user account logged in by the user terminal, obtaining the first user verification result. Specifically, the joint payment server can call the real-name verification interface from the self-service terminal to obtain the second user verification result.

[0086] Fifth, in response to the confirmation that the second user verification result indicates successful verification, a virtual card activation request is sent to the aforementioned joint payment server to activate the virtual card and obtain a virtual card identifier. The joint payment server then writes this virtual card identifier into the device information. In practice, the virtual card activation interface of the joint payment server can be called to activate the virtual card and obtain the virtual card identifier. The virtual card identifier uniquely identifies the virtual card.

[0087] Step 306: Display the payment method selection controls corresponding to each payment method in the payment method selection window.

[0088] In some embodiments, the aforementioned executing entity may display payment method selection controls corresponding to the various payment method information in the payment method selection window. Optionally, the payment method selection window may also display payment method selection controls corresponding to joint payment methods. Joint payment methods can be payment methods that support payment settlement for various types of UnionPay cards. Optionally, the payment method selection window may also display payment method selection controls corresponding to membership card balance payments. Optionally, the self-service terminal may be configured with, but is not limited to, the following payment settlement devices: barcode scanner, keypad, fingerprint keypad, facial recognition device, POS machine, and card reader for membership cards. The payment method selection controls can be used to allow users to select payment methods.

[0089] Step 307: In response to detecting a selection operation performed on the payment method selection control in each payment method selection control, a payment window is displayed.

[0090] In some embodiments, the executing entity may display a payment window in response to detecting a selection operation performed on the payment method selection control. The payment window corresponds to the payment method information associated with the selected payment method selection control. The payment window can be a window for user payment verification. For example, when the payment method is bank card payment, the payment window may display an input box for the user to enter their payment password. When the payment method is facial recognition payment, the payment window may display an image box for the user to scan their face. When the payment method is QR code payment, the payment window may display a payment QR code image for the user to scan.

[0091] Optionally, the aforementioned execution entity may, in response to detecting a selection operation of the payment control applied to the corresponding target virtual card identifier displayed in the payment window, obtain the user's device information as the device information to be verified. Then, it may obtain at least one device information corresponding to the target virtual card identifier as a pre-stored device information set. After a user successfully activates a card on a user's device, the virtual card can be written to a wristband or watch to bind the virtual card identifier to various devices, enabling the wristband or watch to also be used for payment. At least one device information may be the device information of each device bound to the target virtual card identifier. Then, in response to determining that the device information to be verified exists in the pre-stored device information set, it may determine that the user has passed the payment device verification. Finally, in response to determining that the user has passed the payment device verification, it may initiate a payment deduction request to the aforementioned joint payment service. The payment deduction request may include the order value and the aggregated user account. Therefore, a payment request can only be initiated if the device used for payment is the device that the aggregated user account bound to when the virtual card was first activated. This allows the device information of the lost device under the aggregated user account to be directly unbound if the device is lost. Even if the lost device is used for payment, the payment request cannot be successfully initiated, thereby improving payment security.

[0092] from Figure 3 It can be seen from this that, with Figure 2 Compared to the description of some corresponding embodiments, Figure 3 The flow 300 of the account aggregation payment method in some corresponding embodiments embodies the steps of extending the payment process. Thus, the solutions described in these embodiments can aggregate multiple payment methods for users to choose from, achieving the fusion of multiple payment accounts corresponding to an aggregated user account.

[0093] Further reference Figure 4 The diagram illustrates some embodiments of the account aggregation payment system 400. The account aggregation payment system 400 includes a self-service device terminal 401, a self-service server terminal 402, and a platform server terminal 403.

[0094] The self-service device 401 can be a self-checkout payment device placed in a physical store. The self-service device 401 can be configured to perform... Figure 2 , 3 The method described in the corresponding embodiment.

[0095] The self-service terminal 402 can be a server providing services to the self-service device terminal 401, and can be configured to respond to requests from the self-service device terminal. The self-service terminal 402 can store account information for each user account. If the user account corresponds to a user who has registered a member account for the goods circulation application, their account information can be associated with at least one of the following: the member account of the goods circulation application, the member's mobile phone number, or the member card number.

[0096] A 403 error on the platform server can be the target platform's backend server, which can be configured to provide mini-program services and facial recognition services.

[0097] Optionally, the account aggregation payment system 400 may also include a user terminal and an internal server. The user terminal may include various terminal devices used by the user. The internal server may be a server within the local area network of a physical merchant that provides backend services for the circulation of goods.

[0098] The account aggregation payment system through some embodiments of this disclosure can connect facial recognition membership accounts and membership accounts opened through other means, thereby merging payment-related data of the same user.

[0099] The following is for reference. Figure 5 It illustrates an electronic device 500 suitable for implementing some embodiments of the present disclosure (e.g., Figure 1 A schematic diagram of the structure of the self-service terminal device 104. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.

[0100] like Figure 5 As shown, the electronic device 500 may include a processing unit 501 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processing unit 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0101] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 5 Each box shown can represent a device or multiple devices as needed.

[0102] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 509, or installed from storage device 508, or installed from ROM 502. When the computer program is executed by processing device 501, it performs the functions defined in the methods of some embodiments of this disclosure.

[0103] It should be noted that, in some embodiments of this disclosure, the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0104] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0105] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: in response to detecting a user's face login operation, obtain a face information retrieval credential from the platform server corresponding to the target platform, wherein the user's face login operation corresponds to a goods circulation mini-program, the goods circulation mini-program corresponds to a goods circulation application, and the self-service device integrates a software development kit corresponding to the face-scanning service of the target platform; in response to determining the activation state of the device status representation of the goods circulation mini-program corresponding to the self-service device, obtain face information based on the aforementioned face information retrieval credential, wherein the aforementioned face information... The facial information includes a user token; based on the user token, user identification information is obtained from the self-service terminal corresponding to the self-service device, wherein the user identification information includes the user identification corresponding to the self-service terminal and the user relationship result; in response to determining that the user relationship result indicates that the user corresponding to the user identification has opened a facial recognition membership account corresponding to the target platform and the goods circulation application, the user account corresponding to the user identification is logged into the self-service device as an aggregated user account corresponding to the facial recognition membership account; in response to detecting a payment operation, a payment method selection window for the corresponding aggregated user account is displayed for the user to select a payment method and make a payment.

[0106] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0107] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0108] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0109] Some embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements any of the account aggregation payment methods described above.

[0110] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. An account aggregation payment method, applied to self-service devices, comprising: In response to the detection of a user's face login operation, a face information retrieval credential is obtained from the platform server corresponding to the target platform. The user's face login operation corresponds to a goods circulation mini-program, the goods circulation mini-program corresponds to a goods circulation application, and the self-service device integrates a software development kit corresponding to the face recognition service of the target platform. In response to determining the activation status of the device status representation of the item circulation mini-program corresponding to the self-service device, the device retrieves facial information based on the facial information credential, wherein the facial information includes a user token; Based on the user token, user identification information is obtained from the self-service terminal corresponding to the self-service device, wherein the user identification information includes the user identifier corresponding to the self-service terminal and the user relationship result; In response to determining that the user relationship result indicates that the user corresponding to the user identifier has activated a facial recognition membership account corresponding to the target platform and the item circulation application, the user account corresponding to the user identifier is logged into the self-service device as the aggregated user account corresponding to the facial recognition membership account; In response to the detection of a payment operation, a payment method selection window for the corresponding aggregated user account is displayed, allowing the user to select a payment method before making the payment.

2. The method according to claim 1, wherein, Before displaying a payment method selection window for the corresponding aggregated user account in response to a detected payment operation, allowing the user to select a payment method and proceed with the payment, the method further includes: In response to determining that the user relationship result indicates that the user ID corresponding to the user identifier has not activated the corresponding face membership account for the target platform and the item circulation application, the user code information is obtained; Query the member account corresponding to the user code information to obtain the first member query result; In response to determining that the first member query result indicates no member account, the member registration interface is called to obtain the first member registration result; The user account corresponding to the first member registration result in the self-service terminal is identified as the aggregated user account. The membership relationship information corresponding to the identified aggregated user accounts and the user code information is stored in the self-service terminal; Log in to the aggregated user account on the self-service device.

3. The method according to claim 2, wherein, The query for the member account corresponding to the user ID information yields the first member query result, including: In response to determining that the network mode of the self-service terminal includes a local area network (LAN) mode, the member account corresponding to the user code information is queried in the LAN mode to obtain the first member query result. The query results of the first member will be synchronized to the self-service terminal via the public network.

4. The method according to claim 2, wherein, The process of calling the member registration interface to obtain the first member registration result includes: In response to determining that the network mode of the self-service terminal includes a local area network (LAN) mode, the member registration interface of the corresponding member registration server is called in the LAN mode to obtain the first member registration result. The first member registration result will be synchronized to the self-service terminal via the public network.

5. The method according to claim 1, wherein, Before displaying a payment method selection window for the corresponding aggregated user account in response to a detected payment operation, allowing the user to select a payment method and proceed with the payment, the method further includes: In response to detecting a user's QR code login operation, the member login code is obtained from the self-service terminal; In response to detecting a scan result corresponding to the member login code, the member account corresponding to the scan result is queried based on the scan result to obtain a second member query result; In response to the determination that the second member query result indicates no member account, the member registration interface is called to obtain the second member registration result; The user account corresponding to the second member registration result in the self-service terminal is identified as the aggregated user account; The identified aggregated user accounts and the membership relationship information corresponding to the scan results are stored in the self-service terminal; Log in to the aggregated user account on the self-service device.

6. The method according to any one of claims 1-5, wherein, The step of responding to the detection of a payment operation by displaying a payment method selection window for the corresponding aggregated user account, allowing the user to select a payment method and proceed with the payment, includes: In response to the detection of a payment operation, information on each payment method associated with the aggregated user account is obtained from the self-service terminal; The payment method selection window displays various payment method selection controls corresponding to the information of each payment method; In response to detecting a selection operation performed on the payment method selection control of each payment method selection control, a payment window is displayed, wherein the payment window corresponds to the payment method information of the selected payment method selection control.

7. The method according to claim 1, wherein, Before obtaining the face information retrieval credential from the platform server corresponding to the target platform, the method further includes: The item circulation mini-program is initialized. Preload the initialized item circulation mini-program; The software development kit (SDK) corresponding to the facial recognition service is initialized.

8. The method according to claim 6, wherein, The payment method information includes virtual card payment information corresponding to the self-service terminal and the joint payment terminal. The virtual card payment information includes a virtual card identifier, which is associated with the user account of the self-service terminal; and the virtual card corresponding to the virtual card identifier is activated by the user through the following steps: Determine whether the user terminal supports the payment method corresponding to the joint payment server; In response to determining that the user terminal supports the payment method corresponding to the joint payment server, the device information of the user terminal is sent to the joint payment server for device verification, and the device verification result is obtained. In response to the determination that the device verification result indicates successful verification, the account opening request is sent to the self-service terminal for user verification, and a first user verification result is obtained. In response to the detection that the first user verification result indicates successful verification, the card application request is sent to the joint payment server for user verification, and a second user verification result is obtained. In response to the determination that the second user verification result indicates successful verification, a virtual card activation request is sent to the joint payment server to activate the virtual card and obtain a virtual card identifier, so that the joint payment server writes the virtual card identifier into the device information.

9. The method according to claim 8, wherein, The method further includes: In response to detecting a selection operation of the payment control that is applied to the corresponding target virtual card identifier displayed in the payment window, the device information of the user terminal is obtained as the device information to be verified. Obtain at least one device information corresponding to the target virtual card identifier as a pre-stored device information set; In response to determining that the device information to be verified exists in the pre-stored device information set, it is determined that the user terminal verifies the payment device. In response to determining that the user terminal has passed the payment device verification, a payment deduction request is initiated to the joint payment service.

10. An account aggregation payment system, comprising: The self-service device is configured to perform the method described in any one of claims 1-9; The self-service terminal is configured to respond to requests from the self-service device. The platform server is configured to provide mini-program services and facial recognition services.

11. An electronic device, comprising: One or more processors; Storage device, on which one or more programs are stored, When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-9.

12. A computer-readable medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-9.

13. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-9.

Images