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

Abstract

The embodiment of the invention discloses an account aggregation payment method and system, electronic equipment, a readable medium and a product. A specific embodiment of the method comprises the following steps: in response to a detected user face login operation, obtaining a face information calling voucher; in response to determining that the equipment state of the article circulation applet corresponding to the self-service equipment end represents the activation state, acquiring face information; acquiring user identification information from a self-service server side corresponding to the self-service equipment side according to the user token; in response to determining that the user relationship result represents that a user corresponding to the user identifier opens a face member account corresponding to the target platform and the article circulation application, taking a user account corresponding to the user identifier as an aggregated user account corresponding to the face member account to log in the self-service equipment end; and in response to the detected payment operation, displaying a payment mode selection window. The implementation mode is related to cloud payment, and a face member account and member accounts opened in other modes can be opened, so that payment related data of the same user can be fused.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular to account aggregation payment methods, systems, electronic devices, readable media, and products. Background Art

[0002] Under the membership system of an item circulation application, the organizer can organize the member accounts under it in a unified manner. At present, when users make payments, the usual method is to use the previously activated face membership login application to make payments.

[0003] However, the inventors have discovered that when the above method is used, the following technical problems often occur: a membership account logged in using facial recognition cannot be connected with a membership account opened using other methods, and there are many cases where one user has multiple membership accounts, resulting in the inability to merge the payment-related data of the same user.

[0004] The above information disclosed in this Background section is only for enhancement of understanding of the background of the inventive concept and therefore it may contain information that does not form the prior art that is already known in this country to a person of ordinary skill in the art. Summary of the invention

[0005] The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[0006] Some embodiments of the present disclosure propose an account aggregation payment method, an account aggregation payment system, an electronic device, a computer-readable medium, and a computer program product to solve one or more of the technical problems mentioned in the above background technology section.

[0007] In a first aspect, some embodiments of the present disclosure provide an account aggregation payment method, the method comprising: in response to detecting a user face login operation, obtaining a face information call credential from a platform service end corresponding to a target platform, wherein the user face login operation corresponds to an item circulation applet, the item circulation applet corresponds to an item circulation application, and the self-service device end is integrated with a software development kit corresponding to the face recognition service of the target platform; in response to determining that the device status representation activation state of the self-service device end corresponding to the item circulation applet, obtaining face information according to the face information call credential, wherein the face information includes a user command card; according to the above-mentioned user token, obtaining user identification information from the self-service end corresponding to the above-mentioned self-service device end, wherein the above-mentioned user identification information includes the user identification and user relationship result corresponding to the above-mentioned self-service end; in response to determining that the above-mentioned user relationship result represents that the user corresponding to the user identification has opened a face membership account corresponding to the above-mentioned target platform and the above-mentioned item circulation application, the user account corresponding to the above-mentioned user identification is logged in to the above-mentioned self-service device end as an aggregated user account corresponding to the above-mentioned face membership account; in response to detecting a payment operation, displaying a payment method selection window corresponding to the aggregated user account, so that the user can select a payment method and then make a payment.

[0008] Optionally, in response to detecting a payment operation, displaying a payment method selection window corresponding to the aggregated user account for the user to select a payment method and before making 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 opened a facial membership account corresponding to the target platform and the item circulation application, obtaining user code number information; querying the member account corresponding to the user code number information to obtain a first member query result; in response to determining that the first member query result indicates that there is no member account, calling a member registration interface to obtain a first member registration result; determining the user account of the self-service terminal corresponding to the first member registration result as the aggregated user account; storing the determined aggregated user account and the member relationship information corresponding to the user code number information to the self-service terminal; and logging in to the aggregated user account at the self-service device.

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

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

[0011] Optionally, in response to detecting a payment operation, displaying a payment method selection window corresponding to the aggregated user account for the user to select a payment method and before making payment, the method further includes: in response to detecting a user scan code login operation, obtaining a member login code from the self-service end; in response to detecting a scan code result corresponding to the member login code, querying the member account corresponding to the scan code result according to the scan code result to obtain a second member query result; in response to determining that the second member query result indicates that there is no member account, calling a member registration interface to obtain a second member registration result; determining the user account of the self-service end corresponding to the second member registration result as the aggregated user account; storing the determined aggregated user account and the member relationship information corresponding to the scan code result to the self-service end; and logging in to the aggregated user account at the self-service device end.

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

[0013] Optionally, before obtaining the facial information call credentials from the platform server corresponding to the target platform, the method also includes: initializing the above-mentioned item circulation applet; preloading the initialized item circulation applet; initializing the software development kit corresponding to the above-mentioned face recognition service.

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

[0015] Optionally, the method also includes: in response to detecting a selection operation of a payment control acting on 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; in response to determining that the user terminal has passed the payment device verification, initiating a payment deduction request to the joint payment service end.

[0016] In the second aspect, some embodiments of the present disclosure provide an account aggregation payment system, the system comprising: a self-service device end, configured to execute the above-mentioned method of any implementation method of the first aspect; a self-service service end, configured to respond to the request of the above-mentioned self-service device end; and a platform service end, configured to provide mini-program services and face recognition services.

[0017] In a third aspect, some embodiments of the present disclosure provide an electronic device comprising: one or more processors; a storage device on which one or more programs are stored, and 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 manner of the above-mentioned first aspect.

[0018] In a fourth aspect, some embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method described in any implementation manner of the above-mentioned first aspect is implemented.

[0019] In a fifth aspect, some embodiments of the present disclosure provide a computer program product, including a computer program, which implements the method described in any implementation manner of the above-mentioned first aspect when executed by a processor.

[0020] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the account aggregation payment method of some embodiments of the present disclosure, the face member account and the member account opened by other methods can be connected, and then the payment-related data of the same user can be integrated. Specifically, the reason why the payment-related data of the same user cannot be integrated is that the member account logged in using the face cannot be connected with the member account 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. Based on this, the account aggregation payment method of some embodiments of the present disclosure, first, in response to detecting the user face login operation, obtain the face information call credential from the platform service end corresponding to the target platform, wherein the user face login operation corresponds to the item circulation applet, the item circulation applet corresponds to the item circulation application, and the self-service device end is integrated with the software development kit corresponding to the face-swiping service of the target platform. Thus, the credential for obtaining face information can be obtained in advance. Then, in response to determining that the device state representation activation state of the self-service device end corresponding to the item circulation applet is activated, the face information is obtained according to the face information call credential, wherein the face information includes a user token. Thus, the face information of the user on the target platform can be obtained when the current device is activated. Secondly, according to the user token, the user identification information is obtained from the self-service end corresponding to the self-service device end, wherein the user identification information includes the user identification and user relationship result corresponding to the self-service end. Thus, the user identification of the user on the self-service end and the user relationship result representing whether the user has opened a face membership account can be obtained according to the obtained user token. Next, in response to determining that the user relationship result represents that the user corresponding to the user identification has opened a face membership account corresponding to the target platform and the above-mentioned item circulation application, the user account corresponding to the user identification is logged in on the self-service device end as an aggregated user account corresponding to the face membership account. Thus, after determining that the user relationship result represents that the user has opened a face membership account, the user account of the self-service end can be logged in as an aggregated user account after the face is recognized. Finally, in response to detecting a payment operation, a payment method selection window corresponding to the aggregated user account is displayed for the user to select a payment method and then make a payment. Thus, after logging in to the aggregated user account, payment can be made using the payment method of the aggregated user account. Also, when a user logs in through face recognition, what he actually logs in is the user account of the associated self-service end, that is, the face member account can be aggregated under the user account dimension of the self-service end to log in, so that payment can be made under the aggregated user account dimension of the self-service end. In turn, the face member account and the self-service end user account are connected, reducing the situation of multiple member accounts for one user, so that the user's payment-related data can be integrated under the user account dimension of the self-service end. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] Figure 1 is an architectural diagram of an exemplary system in which some embodiments of the present disclosure may be applied;

[0023] Figure 2 is a flow chart of some embodiments of the account aggregation payment method according to the present disclosure;

[0024] Figure 3 are flow charts of other embodiments of the account aggregation payment method according to the present disclosure;

[0025] Figure 4 It is a schematic diagram of the structure of some embodiments of the account aggregation payment system according to the present disclosure;

[0026] Figure 5 It is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION

[0027] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0028] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

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

[0030] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

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

[0032] With regard to the collection, storage, and use of user personal information (such as facial information, user identification, and user account) involved in this disclosure, relevant organizations or individuals must fulfill obligations including conducting personal information security impact assessments, fulfilling the obligation to inform the personal information subject, and obtaining the prior authorization and consent of the personal information subject before performing the corresponding operations.

[0033] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

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

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

[0036] Users can use user-end devices 101, 102, 103 to interact with self-service end device 104 through public network 106 to receive or send messages, etc. Various communication client applications can be installed on user-end devices 101, 102, 103, such as web browser applications, item circulation applications, quick payment applications, search applications, instant messaging tools, email clients, social platform software, etc. User-end devices 101, 102, 103 may include but are not limited to mobile phones, tablet computers, watches, and bracelets. An item circulation application can be installed on the self-service end device 104 for users to pay after self-checking items. Mini-program applications can also be run on the self-service end device 104.

[0037] The self-service terminal device 104 can be hardware or software. When the self-service terminal device 104 is hardware, it can be various electronic devices with a display screen and supporting barcode recognition, including but not limited to self-service 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 multiple software or software modules for providing distributed services, or it can be implemented as a single software or software module. No specific limitation is made here.

[0038] The self-service server 108 may be a server that provides various services, such as a backend server that provides support for the information displayed on the self-service device 104. The backend server may analyze and process the received request and other data, and feed back the processing results to the self-service device 104. The internal server 107 may be a server that provides various services in a local area network mode. The platform server 109 may be a server that provides face recognition services corresponding to the target platform.

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

[0040] It should be understood that Figure 1 The number of user-end devices, self-service end devices, local area networks, public networks and servers in the embodiment is only for illustration. Any number of user-end devices, self-service end devices, local area networks, public networks and servers may be provided according to implementation requirements.

[0041] Continue to refer Figure 2 , shows a process 200 of some embodiments of the account aggregation payment method according to the present disclosure. The account aggregation payment method, applied to the self-service device end, includes the following steps:

[0042] Step 201, in response to detecting a user face login operation, obtaining a face information calling credential from a platform server corresponding to a target platform.

[0043] In some embodiments, the execution entity of the account aggregation payment method (e.g. Figure 1The self-service terminal device 104 shown can obtain the face information call credential from the platform service terminal corresponding to the target platform in response to detecting the user face login operation. Among them, the above-mentioned user face login operation can be an operation for using face to log in to the item circulation applet. For example, the user face login operation can be a selection operation acting on the face login control displayed on the self-service terminal device. The above-mentioned self-service device terminal includes a self-service terminal device. The above-mentioned self-service device terminal is integrated with a software development kit corresponding to the face recognition service of the target platform, so that the user can use the face recognition service of the target platform on the self-service device terminal. The target platform can be an instant messaging software platform, and various applets can be integrated in the application corresponding to the target platform. The item circulation applet can be an item circulation applet application for the physical merchant placed on the self-service device terminal. The item circulation application can be an item management application. Users can log in to member accounts, view items, place orders and pay through the item circulation applet and the item circulation device terminal application. The applet running in the self-service terminal can be a hardware applet. The hardware applet can be a series of hardware applet frameworks specially developed based on to B hardware devices, which can realize some of the applet functions of mobile phones and facilitate the use of devices by physical merchants. In practice, the above-mentioned execution entity can first call the ciphertext acquisition interface included in the above-mentioned software development kit to obtain the ciphertext. For example, the interface name of the ciphertext acquisition interface can be "getWxpayfaceRawdata". Then, the above-mentioned ciphertext can be sent to the above-mentioned platform server, and the face information call certificate corresponding to the above-mentioned ciphertext sent by the above-mentioned platform server can be received. The face information call certificate may include a unique authorization code. Optionally, the face information call certificate may also include the environmental configuration information of the self-service device end, the application identifier applied for in the target platform, the identifier of the bound applet, and the merchant number corresponding to the official account.

[0044] Optionally, before obtaining the facial information call credentials from the platform service end corresponding to the target platform, the above-mentioned execution subject may also initialize the above-mentioned item circulation applet. In practice, the above-mentioned execution subject may call the initialization interface of the applet framework to initialize the above-mentioned item circulation applet. The initialized item circulation applet may then be preloaded. In practice, the above-mentioned execution subject may call the applet preloading interface to load the general resources of the item circulation applet in advance. General resources may include but are not limited to at least one of the following: text, image, video. Secondly, the software development kit corresponding to the above-mentioned face scanning service may be initialized. In practice, the initialization interface of the software development kit may be used to perform initialization processing to release the camera from occupancy and clear the previously cached user face image in order to perform this face scanning operation.

[0045] Step 202, in response to determining that the device status representation of the item circulation applet corresponding to the self-service device is activated, calling the credential according to the facial information to obtain the facial information.

[0046] In some embodiments, the above-mentioned execution subject may obtain facial information in response to determining that the device status of the above-mentioned self-service device terminal corresponding to the above-mentioned item circulation applet represents the activation state, and according to the above-mentioned facial information call credential. Among them, the above-mentioned device status may represent whether the self-service device terminal is in an activated state. In practice, the above-mentioned execution subject may first initialize each face-swiping call parameter with the application identifier, merchant number, and unique authorization code included in the above-mentioned facial information call credential. Then, the facial information acquisition interface may be called. The facial information acquisition interface may be an interface for obtaining user-related information corresponding to the target platform of the face-swiping user. The interface name of the facial information acquisition interface may be "authorizeByWxFacePay". Facial information may include a user token, and may also include a platform user identifier and / or a platform user nickname corresponding to the above-mentioned target platform. The user token may serve as the unique identity of the current user.

[0047] Optionally, before step 203, first, the execution entity may determine whether an activation token exists locally. In practice, it may be determined through the mini-program framework whether an activation token exists locally. The activation token may be saved after the device activation interface is called and issued. Then, in response to determining that an activation token exists locally, the activation status of the self-service device terminal may be checked through the mini-program framework. Next, in response to determining that the device status represents an unactivated state, the device activation interface of the mini-program framework may be called to activate the self-service device terminal. The interface name of the device activation interface may be "activateDeviceBylo".

[0048] Step 203: Obtain user identification information from the self-service end of the corresponding self-service device end according to the user token.

[0049] In some embodiments, the execution subject may obtain user identification information from the self-service terminal corresponding to the self-service device terminal according to the user token. The user identification information includes the user identification corresponding to the self-service terminal and the user relationship result. After the user of the self-service terminal opens the face membership account corresponding to the target platform and the goods circulation application, the user can use the face recognition service of the target platform to log in to the face membership account of the goods circulation application, and the user token, platform user identification, and platform user nickname can be written into the account information corresponding to the user account of the self-service terminal for subsequent query. The user identification corresponding to the self-service terminal may be an identification that uniquely represents the user on the self-service terminal. The user relationship result may indicate whether the user has opened the face membership account corresponding to the target platform.

[0050] Step 204, in response to determining that the user relationship result indicates that the user corresponding to the user identifier has opened a facial membership account corresponding to the target platform and the item circulation application, the user account corresponding to the user identifier is logged in on the self-service device as an aggregated user account of the corresponding facial membership account.

[0051] In some embodiments, the execution subject may, in response to determining that the user relationship result indicates that the user corresponding to the user identifier has opened a face membership account corresponding to the target platform and the item circulation application, log in the user account corresponding to the user identifier as an aggregated user account corresponding to the face membership account on the self-service device. In practice, the execution subject may call the account login interface of the self-service end to log in the aggregated user account on the self-service device.

[0052] Optionally, before step 205, the execution subject may further perform the following steps:

[0053] The first step is to obtain user code number information in response to determining that the above user relationship result indicates that the user corresponding to the user identifier has not opened a facial membership account corresponding to the above target platform and the above item circulation application. The above user code number information may be the user's mobile phone number or membership card number. In practice, in response to detecting the user's membership card number input operation or membership card swiping operation, the above execution subject may obtain the membership card number as the user code number information. The membership card number may be the one entered by the user or the number of the read membership card. The above execution subject may also use the mobile phone number entered by the user as the user code number information in response to detecting the user's mobile phone number input operation.

[0054] The second step is to query the member account corresponding to the user code number information to obtain the first member query result. In practice, the above-mentioned execution subject can query the member account corresponding to the user code number information in the local area network mode in response to determining that the network mode of the above-mentioned self-service terminal includes the local area network mode, and obtain the first member query result. Specifically, the above-mentioned execution subject can call the member query interface under the local area network to query the member account corresponding to the user code number information. The member query interface can be an interface under the ISV service. Then, the above-mentioned first member query result can be synchronized to the above-mentioned self-service terminal through the public network, so that the self-service terminal synchronizes the member query result in the local area network mode. Optionally, the above-mentioned execution subject can call the member query interface under the public network in response to determining that the network mode of the above-mentioned self-service terminal only includes the public network mode, and obtain the first member query result. The member query interface under the public network can be an interface of the self-service terminal.

[0055] The third step is to call the member registration interface to obtain the first member registration result in response to determining that the above-mentioned first member query result indicates that there is no member account. In practice, the above-mentioned execution subject can call the member registration interface of the corresponding member registration service end in the local area network mode in response to determining that the network mode of the above-mentioned self-service end includes the local area network mode to obtain the first member registration result. Specifically, the member registration service end can be a server corresponding to the ISV service. The member registration interface can meet the ISV standard. Then, the above-mentioned first member registration result can be synchronized to the above-mentioned self-service end through the public network. Optionally, the above-mentioned execution subject can call the member registration interface under the public network in response to determining that the network mode of the above-mentioned self-service end only includes the public network mode to obtain the first member registration result. The member registration interface under the public network can be the interface of the self-service end. Member account query and registration under the public network mode can be encapsulated in a registration query interface.

[0056] In the fourth step, the user account of the self-service terminal corresponding to the first member registration result is determined as an aggregated user account.

[0057] The fifth step is to store the member relationship information corresponding to the determined aggregated user account and the user code number information in the self-service terminal. The member relationship information may be information representing the association between the aggregated user account and the user code number information. The member relationship information may include the aggregated user account and the user code number information.

[0058] The sixth step is to log in the aggregated user account on the self-service device. In practice, the execution subject can call the account login interface in the local area network mode to obtain the first login result. The account login interface called in the local area network mode can be the interface of the ISV server. The first login result can be in ciphertext form. Then, the first login result can be synchronized to the self-service end through the public network. The execution subject can also call the account login interface in the public network mode to obtain the first login result. The account login interface called in the public network mode can be the interface of the self-service end. The account login interface of the self-service end can further call the account login interface of the ISV server. Therefore, when the user of the self-service end opens a member account of the item circulation application through a mobile phone number or a membership card, the user can use the mobile phone number or the membership card number to log in to the member account of the item circulation application, and the mobile phone number and the membership card number can be written into the account information corresponding to the user account of the self-service end for subsequent query.

[0059] Optionally, the execution subject may determine the user account of the self-service terminal corresponding to the first member query result as an aggregated user account in response to determining that the first member query result represents a member account. Then, the determined aggregated user account and the member relationship information corresponding to the user code number information may be stored in the self-service terminal. Finally, the aggregated user account may be logged in at the self-service device. Thus, when the member account can be queried, the aggregated user account may be directly logged in at the self-service device.

[0060] Optionally, before step 205, the execution entity may perform the following steps:

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

[0062] In the second step, in response to detecting the scanning result corresponding to the above-mentioned member login code, according to the above-mentioned scanning result, query the member account corresponding to the above-mentioned scanning result to obtain the second member query result. Among them, the user can scan the member login code displayed on the self-service device through the scanning control in the mini program of the user terminal device. The user can also scan the member login code displayed on the self-service device through the scanning control in the official account of the user terminal device. The scanning result may include the scanning user identifier of the corresponding mini program or official account. For example, when the mini program or official account is integrated in the above-mentioned target platform, the scanning user identifier may be the platform user identifier of the user on the target platform. In practice, the above-mentioned execution subject may query the member account corresponding to the above-mentioned scanning user identifier in the local area network mode in response to determining that the network mode of the above-mentioned self-service end includes a local area network mode, and obtain the second member query result. Specifically, the above-mentioned execution subject may call the member query interface under the local area network to query the member account corresponding to the above-mentioned scanning user identifier. The member query interface may be an interface under the ISV service. Then, the above-mentioned second member query result may be synchronized to the above-mentioned self-service end through the public network, so that the self-service end synchronizes the member query result in the local area network mode. Optionally, in response to determining that the network mode of the self-service terminal only includes the public network mode, the execution subject may call a member query interface under the public network to query the member account corresponding to the scanned code user identifier to obtain a second member query result. The member query interface under the public network may be an interface of the self-service terminal.

[0063] The third step is to call the member registration interface to obtain the second member registration result in response to determining that the second member query result indicates that there is no member account. In practice, the execution subject may call the member registration interface of the corresponding member registration service end in the LAN mode in response to determining that the network mode of the self-service end includes the LAN mode to obtain the second member registration result. Specifically, the member registration service end may be a server corresponding to the ISV service. The member registration interface may meet the ISV standard. Then, the second member registration result may be synchronized to the self-service end through the public network. Optionally, the execution subject may call the member registration interface under the public network in response to determining that the network mode of the self-service end only includes the public network mode to obtain the second member registration result. The member registration interface under the public network may be an interface of the self-service end.

[0064] In the fourth step, the user account of the self-service terminal corresponding to the second member registration result is determined as the aggregated user account.

[0065] The fifth step is to store the determined aggregated user account and the member relationship information corresponding to the above-mentioned code scanning result to the above-mentioned self-service terminal. The member relationship information can be information representing the association between the aggregated user account and the above-mentioned code scanning result. The member relationship information can include the aggregated user account and the above-mentioned code scanning user identifier.

[0066] The sixth step is to log in the aggregated user account on the self-service device. In practice, the execution subject can call the account login interface in the LAN mode to obtain the second login result. The account login interface called in the LAN mode can be the interface of the ISV server. The first login result can be in ciphertext form. Then, the second login result can be synchronized to the self-service end through the public network. The execution subject can also call the account login interface in the public network mode to obtain the second login result. The account login interface called in the public network mode can be the interface of the self-service end. The account login interface of the self-service end can further call the account login interface of the ISV server. Therefore, when the user of the self-service end opens a member account of the item circulation application by scanning the code, the user can log in to the member account of the item circulation application by scanning the code, and the scanned user identifier can be written into the account information corresponding to the user account of the self-service end for subsequent query.

[0067] Optionally, the execution subject may determine the user account of the self-service terminal corresponding to the second member query result as an aggregated user account in response to determining that the second member query result represents a member account. Then, the determined aggregated user account and the member relationship information corresponding to the user code number information may be stored in the self-service terminal. Finally, the aggregated user account may be logged in at the self-service device. Thus, when the member account can be queried by scanning the code to log in, the aggregated user account may be directly logged in at the self-service device.

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

[0069] Step 205, in response to detecting a payment operation, displaying a payment method selection window corresponding to the aggregated user account, so that the user can select a payment method and make payment.

[0070] In some embodiments, the execution entity may display a payment method selection window corresponding to the aggregated user account in response to detecting a payment operation, so that the user can select a payment method and then make a payment. The payment operation may be a user's selection operation of an order payment control for an order. An order may be an order consisting of items whose barcodes are scanned by the user. In practice, the execution entity may display the payment method selection window corresponding to the aggregated user account in the form of a pop-up window.

[0071] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the account aggregation payment method of some embodiments of the present disclosure, the face member account and the member account opened by other methods can be connected, and then the payment-related data of the same user can be integrated. Specifically, the reason why the payment-related data of the same user cannot be integrated is that the member account logged in using the face cannot be connected with the member account 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. Based on this, the account aggregation payment method of some embodiments of the present disclosure, first, in response to detecting the user face login operation, obtain the face information call credential from the platform service end corresponding to the target platform, wherein the user face login operation corresponds to the item circulation applet, the item circulation applet corresponds to the item circulation application, and the self-service device end is integrated with the software development kit corresponding to the face-swiping service of the target platform. Thus, the credential for obtaining face information can be obtained in advance. Then, in response to determining that the device state representation activation state of the self-service device end corresponding to the item circulation applet is activated, the face information is obtained according to the face information call credential, wherein the face information includes a user token. Thus, the face information of the user on the target platform can be obtained when the current device is activated. Secondly, according to the user token, the user identification information is obtained from the self-service end corresponding to the self-service device end, wherein the user identification information includes the user identification and user relationship result corresponding to the self-service end. Thus, the user identification of the user on the self-service end and the user relationship result representing whether the user has opened a face membership account can be obtained according to the obtained user token. Next, in response to determining that the user relationship result represents that the user corresponding to the user identification has opened a face membership account corresponding to the target platform and the above-mentioned item circulation application, the user account corresponding to the user identification is logged in on the self-service device end as an aggregated user account corresponding to the face membership account. Thus, after determining that the user relationship result represents that the user has opened a face membership account, the user account of the self-service end can be logged in as an aggregated user account after the face is recognized. Finally, in response to detecting a payment operation, a payment method selection window corresponding to the aggregated user account is displayed for the user to select a payment method and then make a payment. Thus, after logging in to the aggregated user account, payment can be made using the payment method of the aggregated user account. Also, when a user logs in through face recognition, what he actually logs in is the user account of the associated self-service end, that is, the face member account can be aggregated under the user account dimension of the self-service end to log in, so that payment can be made under the aggregated user account dimension of the self-service end. In turn, the face member account and the self-service end user account are connected, reducing the situation of multiple member accounts for one user, so that the user's payment-related data can be integrated under the user account dimension of the self-service end.

[0072] Further references Figure 3 , which shows a process 300 of another embodiment of the account aggregation payment method. The process 300 of the account aggregation payment method includes the following steps:

[0073] Step 301, in response to detecting a user face login operation, obtaining a face information calling credential from a platform server corresponding to a target platform.

[0074] Step 302, in response to determining that the device status representation of the item circulation applet corresponding to the self-service device is activated, calling the credential according to the facial information to obtain the facial information.

[0075] Step 303: Obtain user identification information from the self-service end of the corresponding self-service device end according to the user token.

[0076] Step 304, in response to determining that the user relationship result indicates that the user corresponding to the user identifier has opened a facial membership account corresponding to the target platform and the item circulation application, the user account corresponding to the user identifier is logged in on the self-service device as an aggregated user account of the corresponding facial membership account.

[0077] In some embodiments, the specific implementation of steps 301-304 and the technical effects brought about can be referred to Figure 2 The corresponding steps 201-204 in the embodiments are not described in detail here.

[0078] Step 305 , in response to detecting a payment operation, obtaining information of various payment methods associated with the aggregated user account from the self-service end.

[0079] In some embodiments, the execution entity of the account aggregation payment method (e.g. Figure 1 The self-service terminal device 104 shown in the figure can obtain various payment method information associated with the aggregated user account from the above-mentioned self-service terminal in response to detecting a payment operation. Among them, the above-mentioned various payment method information can represent various 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 account opening bank information and the bank card number. When the payment method is QR code payment, the payment method information may include a code scanning application identifier and a QR code image. When the payment method is face payment, the payment method information may include a face swiping application identifier. Face payment may include face payment corresponding to the target platform, and may also include face payment corresponding to the self-service terminal. When the payment method is Baitiao payment, the payment method information may include a Baitiao account number. When the payment method is fingerprint payment, the payment method information may include a finger identifier to be detected. The above-mentioned various payment method information are all previously configured or bound by the user corresponding to the aggregated user account in the application corresponding to the self-service terminal.

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

[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 user terminal supports the payment method corresponding to the joint payment server. In practice, the user terminal can determine whether the current user terminal device supports HCE (Host-based Card Emulation) or TSM (Trusted Service Manager). Then, in response to determining that HCE or TSM is supported, it can be determined that the user terminal supports the payment method corresponding to the joint payment server.

[0083] In the second step, in response to determining that the user terminal supports the payment method corresponding to the joint payment service terminal, the device information of the user terminal is sent to the joint payment service terminal for device verification to obtain a device verification result. The device information may include a device model. The device model may include a device brand and a device name.

[0084] In the third step, in response to determining that the device verification result indicates that the verification is successful, the account opening request is sent to the self-service terminal for user verification to obtain a first user verification result. The account opening request may be a request to open a virtual card with a user account of the self-service terminal. The self-service terminal may perform a user real-name verification on the user account logged in by the user terminal to obtain a first user verification result.

[0085] In the fourth step, in response to detecting that the first user verification result indicates successful verification, a card application request is sent to the joint payment service end for user verification to obtain a second user verification result. The card application request may indicate a request to the joint payment service end to open a virtual card. The joint payment service end may perform a user real-name verification on the user account logged in by the user end to obtain a first user verification result. Specifically, the joint payment service end may call a real-name verification interface from the self-service end to obtain a second user verification result.

[0086] Step 5: In response to determining 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, obtain a virtual card identifier, and cause the joint payment server to write the 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 can uniquely identify the virtual card.

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

[0088] In some embodiments, the execution entity may display the payment method selection controls corresponding to the payment method information in the payment method selection window. Optionally, the payment method selection window may also display the payment method selection controls corresponding to the joint payment method. The joint payment method may be a payment method that supports various types of UnionPay cards for payment settlement. Optionally, the payment method selection window may also display the payment method selection controls corresponding to the membership card balance payment. Optionally, the self-service terminal may be configured with but not limited to the following payment settlement devices: barcode scanner, password keyboard, fingerprint keyboard, face camera, POS machine, card reader for membership card. The payment method selection control may be used for users to select a payment method.

[0089] Step 307: In response to detecting a selection operation on a payment method selection control among the payment method selection controls, display a payment window.

[0090] In some embodiments, the execution entity may display a payment window in response to detecting a selection operation on a payment method selection control in each of the payment method selection controls. The payment window corresponds to the payment method information corresponding to the selected payment method selection control. The payment window may be a window for users to perform payment verification. For example, when the payment method is bank card payment, an input box for the user to enter a payment password may be displayed in the payment window. When the payment method is face payment, an image box for the user to scan his face may be displayed in the payment window. When the payment method is QR code payment, a payment QR code image for the user to scan may be displayed in the payment window.

[0091] Optionally, the execution subject may obtain the device information of the user end as the device information to be verified in response to detecting the selection operation of the payment control corresponding to the target virtual card identifier displayed in the payment window. Then, obtain at least one device information corresponding to the target virtual card identifier as a set of pre-stored device information. After the user successfully opens a card on a user-end device, the virtual card can be written into a bracelet or watch to bind the virtual card identifier to each device, so that the bracelet and watch can 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 be determined that the user end has passed the payment device verification. Finally, in response to determining that the user end has passed the payment device verification, a payment deduction request may be initiated to the joint payment service end. The payment deduction request may include the order value and the aggregated user account. Therefore, a payment request can only be initiated under the condition that the device used for payment is the device bound to the aggregated user account when the virtual card is first activated. Therefore, when the device is lost, the device information of the lost device under the aggregated user account can be directly unbound. Even if the lost device is used for payment, a payment request cannot be successfully initiated, thereby improving payment security.

[0092] from Figure 3 It can be seen that Figure 2 Compared with the description of some corresponding embodiments, Figure 3 The process 300 of the account aggregation payment method in some corresponding embodiments embodies the steps of expanding the payment process. Therefore, the schemes described in these embodiments can aggregate multiple payment methods for users to choose to pay, and realize the integration of multiple payment accounts corresponding to the aggregated user account.

[0093] Further references Figure 4 , which shows a schematic diagram of some embodiments of an account aggregation payment system 400. The account aggregation payment system 400 includes a self-service device end 401, a self-service end 402 and a platform service end 403.

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

[0095] The self-service terminal 402 may be a server that provides services for the self-service device terminal 401, and may be configured to respond to requests from the self-service device terminal. The self-service terminal 402 may store account information of each user account. If the user corresponding to the user account has registered a member account of the item circulation application, the account information may be associated with at least one of the following: a member account of the item circulation application, a member mobile phone number, and a member card number.

[0096] The platform server 403 may be a backend server of the target platform, and may be configured to provide mini-program services and face recognition services.

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

[0098] Through the account aggregation payment system of some embodiments of the present disclosure, facial recognition membership accounts and membership accounts opened by other methods can be connected, and then the payment-related data of the same user can be integrated.

[0099] Reference below Figure 5 , which shows an electronic device 500 (eg, Figure 1 A schematic diagram of the structure of the self-service terminal device 104). Figure 5 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0100] like Figure 5 As shown, the electronic device 500 may include a processing device 501 (e.g., a central processing unit, a graphics processing unit, 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. In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0101] Typically, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 5 The electronic device 500 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 5 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0102] In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of some embodiments of the present disclosure are executed.

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

[0104] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0105] The above-mentioned computer-readable medium may be included in the above-mentioned electronic device; or it may exist independently without being installed in the electronic device. The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the electronic device, the electronic device: in response to detecting a user face login operation, obtains a face information call credential from the platform service end corresponding to the target platform, wherein the above-mentioned user face login operation corresponds to an item circulation applet, the above-mentioned item circulation applet corresponds to an item circulation application, and the above-mentioned self-service device end is integrated with a software development kit corresponding to the face scanning service of the above-mentioned target platform; in response to determining that the device status representation activation state of the above-mentioned self-service device end corresponding to the above-mentioned item circulation applet, obtains face information according to the above-mentioned face information call credential, wherein the above-mentioned face information The facial information includes a user token; based on the user token, user identification information is obtained from the self-service end corresponding to the self-service device end, wherein the user identification information includes the user identification and user relationship result corresponding to the self-service end; in response to determining that the user relationship result represents that the user corresponding to the user identification has opened a facial membership account corresponding to the target platform and the item circulation application, the user account corresponding to the user identification is logged in to the self-service device end as an aggregated user account corresponding to the facial membership account; in response to detecting a payment operation, a payment method selection window corresponding to the aggregated user account is displayed for the user to select a payment method and then make payment.

[0106] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate 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 a remote computer, the remote computer may 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 may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0107] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0108] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

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

[0110] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above invention concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure.

Claims

1. An account aggregation payment method, applied to a self-service device, comprising: In response to detecting a user face login operation, obtaining a face information calling credential from a platform service end corresponding to the target platform, wherein the user face login operation corresponds to an item circulation applet, the item circulation applet corresponds to an item circulation application, and the self-service device end is integrated with 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 item circulation applet corresponding to the self-service device is activated, calling the credential according to the facial information to obtain the facial information, wherein the facial information includes a user token; According to the user token, obtaining user identification information from a self-service end corresponding to the self-service device end, wherein the user identification information includes a user identification and a user relationship result corresponding to the self-service end; In response to determining that the user relationship result indicates that the user corresponding to the user identifier has opened a face membership account corresponding to the target platform and the item circulation application, the user account corresponding to the user identifier is logged in on the self-service device as an aggregated user account corresponding to the face membership account; In response to detecting a payment operation, a payment method selection window corresponding to the aggregated user account is displayed for the user to select a payment method and then make payment.

2. The method according to claim 1, wherein: Before displaying a payment method selection window corresponding to the aggregated user account in response to detecting a payment operation so that the user can 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 opened a face membership account corresponding to the target platform and the item circulation application, obtaining user code number information; Querying the member account corresponding to the user code number information to obtain a first member query result; In response to determining that the first member query result indicates that there is no member account, calling a member registration interface to obtain a first member registration result; Determining the user account of the self-service terminal corresponding to the first member registration result as an aggregated user account; storing the determined aggregated user account and the member relationship information corresponding to the user code number information 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 querying of the member account corresponding to the user code number information to obtain the first member query result includes: In response to determining that the network mode of the self-service terminal includes a local area network mode, querying a member account corresponding to the user code number information in the local area network mode to obtain a first member query result; The first member query result is synchronized to the self-service terminal through the public network.

4. The method according to claim 2, wherein: The calling of the member registration interface to obtain the first member registration result includes: In response to determining that the network mode of the self-service end includes a local area network mode, calling a member registration interface of a corresponding member registration service end in the local area network mode to obtain a first member registration result; The first member registration result is 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 corresponding to the aggregated user account in response to detecting a payment operation so that the user can select a payment method and make payment, the method further includes: In response to detecting a user scanning code login operation, obtaining a member login code from the self-service terminal; In response to detecting a scan result corresponding to the member login code, querying the member account corresponding to the scan result according to the scan result to obtain a second member query result; In response to determining that the second member query result indicates that there is no member account, calling a member registration interface to obtain a second member registration result; Determining the user account of the self-service terminal corresponding to the second member registration result as an aggregated user account; Storing the determined aggregated user account and the membership relationship information corresponding to the code scanning result 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 to 5, wherein: In response to detecting a payment operation, displaying a payment method selection window corresponding to the aggregated user account so that the user can select a payment method and make payment, including: In response to detecting a payment operation, obtaining from the self-service terminal information of various payment methods associated with the aggregated user account; Displaying each payment method selection control corresponding to each payment method information in the payment method selection window; In response to detecting a selection operation on a payment method selection control among the payment method selection controls, a payment window is displayed, wherein the payment window corresponds to payment method information corresponding to the selected payment method selection control.

7. The method according to claim 1, wherein: Before obtaining the face information calling credential from the platform server corresponding to the target platform, the method further includes: Initializing the item circulation applet; Preload the initialized item circulation applet; Initialize the software development kit corresponding to the face recognition service.

8. The method according to claim 6, wherein: The payment method information includes virtual card payment information corresponding to the self-service end and the joint payment service end, the virtual card payment information includes a virtual card identifier, the virtual card identifier is associated with a user account of the self-service end; and the virtual card corresponding to the virtual card identifier is activated by the user end through the following steps: Determine whether the user terminal supports the payment method corresponding to the joint payment service terminal; In response to determining that the user terminal supports the payment method corresponding to the joint payment service terminal, sending the device information of the user terminal to the joint payment service 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 to obtain 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 service end for user verification to obtain a second user verification result; In response to determining that the second user verification result indicates successful verification, a virtual card activation request is sent to the joint payment service end to activate the virtual card, obtain a virtual card identifier, and allow the joint payment service end to write the virtual card identifier into the device information.

9. The method according to claim 8, wherein: The method further comprises: In response to detecting a selection operation of a payment control corresponding to a target virtual card identifier displayed in the payment window, obtaining device information of the user terminal as device information to be verified; Acquire 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 to-be-verified device information exists in the pre-stored device information set, determining that the user terminal passes the payment device verification; In response to determining that the user terminal passes the payment device verification, a payment deduction request is initiated to the joint payment service terminal.

10. An account aggregation payment system, comprising: A self-service device terminal, configured to execute the method according to any one of claims 1 to 9; A self-service terminal, configured to respond to a request from the self-service device terminal; The platform server is configured to provide mini program services and face recognition services.

11. An electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 9.

12. A computer readable medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

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

Images