Payment processing method, apparatus, device, storage medium, and computer program product

Abstract

A payment processing method, device, equipment, storage medium and computer program product are applied to various scenes such as cloud technology, artificial intelligence, block chain, Internet of Vehicles, intelligent transportation, smart home and the like, and the method comprises: receiving a combined payment request sent by a target terminal device, the combined payment request comprising identity information of a target object; determining a target account identifier by using the identity information, and obtaining M orders associated with the target account identifier from a combined order library, each order in the M orders being written into the combined order library after being associated with the target account identifier by a payment server based on image data and order data of the target object sent by an order processing device; performing combined payment on at least one order in the M orders, and returning a combined payment result to the target terminal device, M being a positive integer. By using the method of the present application, the security and convenience of digital payment can be improved.

Description

Technical Field

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

[0002] Advances in internet technology have spurred the birth of e-commerce. Traditional financial payment channels have been unable to meet the demands of e-commerce development. Therefore, digital payment methods, achieved through hardware such as computers and smart devices, and digital technologies like communication, artificial intelligence, and information security, are increasingly favored by users. Consumers no longer need to use cash when transacting with merchants, simplifying the transaction process. However, in supermarket payment scenarios, consumers need to enter their purchase information at the checkout counter, often wasting time queuing and resulting in poor convenience. Furthermore, consumers often have concerns about payment security. Therefore, improving the security and convenience of digital payments is essential. Summary of the Invention

[0003] This application provides a payment processing method, apparatus, device, storage medium, and computer program product that can improve the security and convenience of digital payments.

[0004] On one hand, embodiments of this application provide a payment processing method, the method comprising: Receive a merged payment request sent by the target terminal device, wherein the merged payment request includes the identity information of the target object; The target account identifier is determined using the identity information, and M orders associated with the target account identifier are obtained from the merged order database. Each of the M orders is the image data and order data of the target object sent by the payment server based on the order processing device. Each order is associated with the target account identifier and written into the merged order database. At least one of the M orders is merged for payment, and the merged payment result is returned to the target terminal device, where M is a positive integer.

[0005] On one hand, embodiments of this application provide a payment processing method, the method comprising: The image data of the target object is acquired and sent to the payment server, so that the payment server performs identity recognition processing on the image data of the target object to obtain the target account identifier. Displays an order merging notification message; If the target object confirms the order merging prompt information, an order merging request is sent to the payment server. The order merging request includes the order data to be merged. The order merging request is used to instruct the payment server to associate the target account identifier with each order corresponding to the order data and write it into the merged order database. The orders in the merged order database are used by the payment server to perform merged payment. Receive the order merging result sent by the payment server.

[0006] On one hand, embodiments of this application provide a payment processing method, the method comprising: A merged payment request is sent to the payment server. The merged payment request includes the identity information of the target object, so that the payment server can use the identity information to determine the target account identifier and obtain M orders associated with the target account identifier from the merged order database, where M is a positive integer. Receive the M orders sent by the payment server; If a payment confirmation operation is received, a payment confirmation request is sent to the payment server. The payment confirmation request includes at least one of the M orders and is used to instruct the payment server to make a combined payment for at least one of the M orders.

[0007] On one hand, embodiments of this application provide a payment processing apparatus, the apparatus comprising: The receiving unit is used to receive a merged payment request sent by the target terminal device, wherein the merged payment request includes the identity information of the target object; The processing unit is configured to determine the target account identifier using the identity information, and obtain M orders associated with the target account identifier from the merged order database. Each of the M orders is generated by the payment server based on the image data and order data of the target object sent by the order processing device. The unit associates each order with the target account identifier and writes it into the merged order database. The processing unit is also configured to perform a combined payment for at least one of the M orders and return the combined payment result to the target terminal device, where M is a positive integer.

[0008] On one hand, embodiments of this application provide a payment processing apparatus, the apparatus comprising: An acquisition unit is used to acquire image data of a target object and send the image data of the target object to a payment server, so that the payment server performs identity recognition processing on the image data of the target object to obtain the target account identifier. The processing unit is used to display order merging prompts. The processing unit is further configured to, if it receives a confirmation operation from the target object for the order merging prompt information, send an order merging request to the payment server. The order merging request includes order data to be merged. The order merging request is used to instruct the payment server to associate the target account identifier with each order corresponding to the order data and write it into the merged order database. The orders in the merged order database are used by the payment server for merged payment. The receiving unit is used to receive the order merging results sent by the payment server.

[0009] On one hand, embodiments of this application provide a payment processing apparatus, the apparatus comprising: The sending unit is used to send a merged payment request to the payment server. The merged payment request includes the identity information of the target object, so that the payment server can use the identity information to determine the target account identifier and obtain M orders associated with the target account identifier from the merged order database, where M is a positive integer. A receiving unit is configured to receive the M orders sent by the payment server; The sending unit is configured to send a payment confirmation request to the payment server if a payment confirmation operation is received. The payment confirmation request includes at least one of the M orders and is used to instruct the payment server to make a combined payment for at least one of the M orders.

[0010] On one hand, embodiments of this application provide a computer device, which includes a processor, a communication interface, and a memory. The processor, the communication interface, and the memory are interconnected. The memory stores a computer program, and the processor is used to call the computer program to execute the payment processing method of any of the above possible implementations.

[0011] On one hand, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements a payment processing method of any possible implementation.

[0012] Accordingly, this application also provides a computer program product, which includes a computer program or computer instructions, and the computer program or computer instructions are executed by a processor to implement the steps of the payment processing method provided in this application.

[0013] Accordingly, this application also provides a computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the payment processing method provided in this application.

[0014] In this embodiment, the payment server can receive a merged payment request sent by the target terminal device. This merged payment request includes the target object's identity information. The server can use this identity information to determine the target account identifier and retrieve M (positive integer) orders associated with the target account identifier from the merged order database. At least one of these M orders is then merged for payment, and the merged payment result is returned to the target terminal device. Each of the M orders is generated by the payment server based on the target object's image data and order data sent by the order processing device, and each order is associated with the target account identifier and written into the merged order database. Using this method, the target object can merge orders into the merged order database through the order processing device and then perform batch payments on the target terminal device, improving the convenience and security of digital payments. Attached Figure Description

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

[0016] Figure 1 A schematic diagram of the system architecture of a payment processing system provided in this application embodiment. Figure 1 ; Figure 2 A schematic diagram of the system architecture of a payment processing system provided in this application embodiment. Figure 2 ; Figure 3 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 1 ; Figure 4 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 2 ; Figure 5 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 3 ; Figure 6 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 4 ; Figure 7 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 5 ; Figure 8 A schematic diagram of the system architecture of a payment processing system provided in this application embodiment. Figure 3 ; Figure 9 A schematic diagram of the system architecture of a payment processing system provided in this application embodiment. Figure 4 ; Figure 10 This is a schematic diagram of the structure of a payment processing device provided in an embodiment of this application; Figure 11 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

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

[0018] This application proposes a payment processing method that can improve the security and convenience of digital payments, applicable to various scenarios such as cloud technology, artificial intelligence, blockchain, connected vehicles, smart transportation, and smart homes. The proposed payment processing method can be implemented based on cloud technology and / or artificial intelligence technology. Cloud technology is a general term encompassing network technology, information technology, integration technology, management platform technology, and application technology applied in cloud computing business models. It can form a resource pool, available on demand, and is flexible and convenient. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to a backend system for logical processing. Data at different levels will be processed separately, and various industry data will require robust system support, which can only be achieved through cloud computing. Artificial intelligence is the theory, methods, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results. In other words, artificial intelligence (AI) is a comprehensive technology within computer science that attempts to understand the essence of intelligence and produce new intelligent machines that can react in a way similar to human intelligence. AI studies the design principles and implementation methods of various intelligent machines, enabling them to possess perception, reasoning, and decision-making capabilities.

[0019] The payment processing method provided in this application embodiment may specifically involve one or more of cloud technologies, such as cloud storage, cloud databases, and big data. For example, it may retrieve the data (e.g., target account identifier) ​​required to execute the payment processing method from a cloud database. Furthermore, the payment processing method provided in this application embodiment may specifically involve one or more of artificial intelligence foundational technologies, such as distributed storage and large-scale payment processing technologies. For example, it may store orders from a merged order database on multiple independent devices.

[0020] Please see Figure 1 , Figure 1 A schematic diagram of the system architecture of a payment processing system provided in this application embodiment. Figure 1 ; Figure 1 The system architecture shown can be used to implement the payment processing method proposed in the embodiments of this application. For example... Figure 1 As shown, the system architecture includes: a payment server 10, a target terminal device 11, and an order processing device 12. The number of target terminal devices 11 and order processing devices 12 can be one or more.

[0021] The payment server 10 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. The target terminal device 11 can be an order processing device 12, including facial recognition payment devices, iris recognition payment devices, etc.; it can also be a user terminal device, which can be a smartphone, tablet, laptop, desktop computer, intelligent voice interaction device, smart home appliance, in-vehicle terminal, etc., but is not limited to these. Understandably, the order processing device 12 and the target terminal device 11 can be the same device. Figure 1 The target terminal device 11, the order processing device 12, and the payment server 10 shown are connected via a network.

[0022] Figure 1 The system architecture shown can implement the payment processing method provided in this application embodiment. Its implementation process roughly includes: ① Payment server 10 receives image data of the target object sent by order processing device 12; ② Payment server 10 performs identity recognition processing on the image data of the target object to obtain a target account identifier; ③ Payment server 10 receives an order merging request sent by order processing device 12, the order merging request including order data to be merged; ④ Payment server 10 associates the target account identifier with each order corresponding to the order data and writes it into the merged order database, and returns the order merging result to order processing device 12; ⑤ Payment server 10 receives a merged payment request sent by target terminal device 11, the merged payment request including the target object's identity information; ⑥ Payment server 10 uses the identity information to determine the target account identifier and obtains M orders associated with the target account identifier from the merged order database; ⑦ Payment server 10 performs merged payment on at least one of the M orders and returns the merged payment result to target terminal device 11, where M is a positive integer. Using the method of this application can improve the security and convenience of digital payments.

[0023] Please see Figure 2 , Figure 2 A schematic diagram of the system architecture of a payment processing system provided in this application embodiment. Figure 2The system architecture includes a payment server 10, target terminal devices 11, order processing devices 12, and a management server 13. These components are connected via a network. The management server 13 can correspond to a merchant platform, and the payment server 10 can correspond to a third-party platform. The merged order database is managed by the management server 13. Specifically, the payment server 10 receives image data of the target object sent by the order processing device 12 and uses this data for identity verification to obtain a target account identifier. The payment server 10 then sends the obtained target account identifier to the management server 13. The management server 13 receives the target account identifier from the payment server 10 and the order data to be merged from the order processing device. It then associates the target account identifier with each corresponding order and writes it into the merged order database. In addition, after receiving the merged payment request sent by the target terminal device 11, the payment server 10 can use the identity information of the target object included in the merged payment request to determine the target account identifier, and send the target account identifier to the management server 13. The management server 13 can use the target account identifier to retrieve M orders associated with the target account identifier from the merged order database, and send the M orders to the payment server 10, which will then perform merged payment on the M orders; or, the M orders can be sent to the target terminal device 11, and the target object can select at least one order from the M orders displayed on the target terminal device 11, and then send the at least one order to the payment server 10, which will then perform merged payment on the at least one order and return the merged payment result to the target terminal device 11.

[0024] Currently, some users feel that facial recognition payment devices, iris recognition payment devices, and other similar devices are insecure. Using the method described in this application, payment operations can be performed without using these devices. Instead, orders are first merged into a consolidated order database, and then batch payments are made on the user's terminal device. This improves both the security and convenience of digital payments, and also enhances users' sense of security, addressing the issue of users with low security using facial or iris payments. This can increase the adoption rate of facial or iris payments and improve the user experience.

[0025] In addition, in supermarket payment scenarios, consumers need to enter the goods and make payment all at once at the checkout, which causes users to waste time queuing for a long time. Using the method of this application, users can merge orders into a merged order database in advance through one or more order processing devices, and make batch payments directly on the target terminal device at checkout, which can improve the convenience and security of digital payment and improve payment efficiency.

[0026] It is understood that the system architecture diagrams described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0027] The specific implementation of the payment processing method will be explained in detail below.

[0028] Please see Figure 3 , Figure 3 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 1 The payment processing method described in the embodiments of this application can be provided by... Figure 1 The payment processing method, executed by the payment server 10, includes, but is not limited to, the following steps: S301. Receive a merged payment request sent by the target terminal device. The merged payment request includes the identity information of the target object.

[0029] The target is the user who performs a consolidated payment task using the target terminal device. Identification information is used to uniquely identify this target. The consolidated payment request instructs the payment server to consolidate payments for orders in the consolidated order database. The consolidated order database includes one or more orders, and these orders are associated with account identifiers.

[0030] In one embodiment, the target terminal device can provide a merge payment control. When the target object triggers the merge payment control, the target terminal device generates a merge payment request containing the target object's identity information and sends the merge payment request to the payment server.

[0031] S302. Use the identity information to determine the target account identifier, and retrieve M orders associated with the target account identifier from the merged order database. Each of the M orders is the image data of the target object and the order data sent by the payment server based on the order processing device. Write each order into the merged order database after associating it with the target account identifier.

[0032] The target object has a corresponding target account identifier, which can be the account identifier corresponding to the account registered by the target object on the application (which may be a mini-program) providing the consolidated payment service. In one embodiment, the payment server can use the identity information to determine the uniquely identified target object and obtain the target account identifier by looking up the account identifier corresponding to the target object. Since one or more orders in the consolidated order database are associated with the account identifier, M orders associated with the target account identifier can be obtained from these one or more orders.

[0033] In one embodiment, the order processing device, after obtaining permission from the target object, can acquire image data and order data of the target object. The image data may include facial data, iris data, etc., of the target object acquired by the order processing device. The order processing device can send the image data and order data of the target object to a payment server. The payment server uses the image data of the target object for identity verification to determine the target object, obtains the account identifier corresponding to the target object, and thus obtains the target account identifier. For example, the payment server can store image data of multiple objects and the corresponding account identifiers of multiple objects. It can compare the image data of the target object with the image data of multiple objects, find the most similar object as the target object, and use the account identifier corresponding to the most similar object as the target account identifier. Furthermore, the payment server can associate the target account identifier with each order corresponding to the order data and write it into a merged order database.

[0034] It should be noted that each order corresponding to this order data is contained in M ​​orders associated with the target account identifier. The M orders may be sent by the target object using the same order processing device, or they may be sent by the target object using different order processing devices.

[0035] S303. Perform a combined payment for at least one of the M orders and return the combined payment result to the target terminal device, where M is a positive integer.

[0036] In one embodiment, when the payment server receives a merged payment request, it can use the target account identifier to obtain the graphic code information bound to the target account identifier. This graphic code information can be used to execute the payment task. Additionally, the payment server can send the obtained M orders to the target terminal device. The target user can select from the displayed M orders on the target terminal device. When a selection occurs for at least one of the M orders, the target terminal device can send that at least one order to the payment server. The payment server uses the graphic code information bound to the target account identifier to perform a merged payment for that at least one order and returns the merged payment result to the target terminal device. This merged payment result can include merged payment success or merged payment failure. For example, if the target user possesses sufficient digital assets for merged payment, the merged payment result is merged payment success.

[0037] In a feasible embodiment, after receiving M orders, the payment server can use the graphic code information bound to the target account identifier to merge and pay the M orders, and return the merged payment result to the target terminal device.

[0038] In supermarket payment scenarios, customers can use order processing devices located in different locations to merge the product information that needs to be paid into a merged order database. At checkout, customers can select an order processing device (which is the target terminal device) to send a merged payment request to the payment server, thereby realizing the merged payment of orders or multiple product information. This can reduce the pressure on cashiers and checkout, effectively improve the convenience and efficiency of digital payments, and also solve the queuing problem.

[0039] In addition, users who feel that facial recognition payment devices, iris recognition payment devices, etc. are insecure can choose to merge payments at checkout. This will first merge the orders into a merged order database without performing the payment operation. The unpaid orders can then be transferred to the user's terminal device (which is now the target terminal device). The target user can then make batch payments on the user's terminal device. This can solve the problem of users with low security using facial recognition or iris recognition payments, increase the adoption rate of facial recognition or iris recognition payments, and improve the security of digital payments.

[0040] In this embodiment, the payment server can receive a merged payment request sent by the target terminal device. This merged payment request includes the target object's identity information. The server can use this identity information to determine the target account identifier and retrieve M (positive integer) orders associated with the target account identifier from the merged order database. At least one of these M orders is then merged for payment, and the merged payment result is returned to the target terminal device. Each of the M orders is generated by the payment server based on the target object's image data and order data sent by the order processing device, and each order is associated with the target account identifier and written into the merged order database. Using this method, the target object can merge orders into the merged order database through the order processing device and then perform batch payments on the target terminal device, improving the convenience and security of digital payments.

[0041] Please see Figure 4 , Figure 4 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 2 The payment processing method described in the embodiments of this application can be provided by... Figure 1 The order processing device 12 executes the payment processing method, which includes, but is not limited to, the following steps: S401. Obtain the image data of the target object and send the image data of the target object to the payment server so that the payment server can perform identity recognition processing on the image data of the target object to obtain the target account identifier.

[0042] In one embodiment, the order processing device, after obtaining permission from the target object, can acquire image data and order data of the target object. The image data may include facial data, iris data, etc., of the target object acquired by the order processing device. The order processing device can send the image data and order data of the target object to a payment server. The payment server uses the image data of the target object for identity verification to determine the target object, obtains the account identifier corresponding to the target object, and thus obtains the target account identifier. For example, the payment server can store image data of multiple objects and the corresponding account identifiers of multiple objects. It can compare the image data of the target object with the image data of multiple objects, find the most similar object as the target object, and use the account identifier corresponding to the most similar object as the target account identifier.

[0043] S402, Display order merging prompt information.

[0044] The order merging prompt message is used to inform the target object that orders can be merged into the merged order library, and subsequent batch payment of orders can be processed.

[0045] S403. If a confirmation operation is received from the target object regarding the order merging prompt, an order merging request is sent to the payment server. The order merging request includes the order data to be merged. The order merging request is used to instruct the payment server to associate the target account identifier with each order corresponding to the order data and write it into the merged order database. The orders in the merged order database are used by the payment server for merged payment.

[0046] In one embodiment, when the order processing device receives confirmation from the target object regarding the order merging prompt, it can send an order merging request to the payment server. This request may include order data to be merged. The order data to be merged may be generated before the order processing device acquires the target object's image data, or it may be generated after the order processing device sends the target object's image data to the payment server, using product information added via the order processing device's scanning device (e.g., a barcode scanner). The order data to be merged may include one or more product information items, which may be obtained using the order processing device's scanning device. Further, in response to the order merging request, the payment server may associate the obtained target account identifier with the corresponding order data and write it into the merged order database.

[0047] S404: Receive the order merging result sent by the payment server.

[0048] In one embodiment, after the payment server associates the target account identifier and the order data corresponding to the order and writes them into the merged order database, it returns the order merging result to the order processing device as "order merging successful". If the payment server cannot associate the target account identifier and the order data corresponding to the order and write them into the merged order database, it returns the order merging result as "order merging failed".

[0049] In this embodiment, the order processing device can send the image data of the target object and the order data to be merged to the payment server. The payment server uses the image data of the target object to obtain the target account identifier, and then associates the target account identifier with the order data and writes it into the merged order database. This allows the payment server to use the orders in the merged order database for merged payment, which can improve the security and convenience of digital payment.

[0050] Please see Figure 5 , Figure 5 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 3 The payment processing method described in the embodiments of this application can be provided by... Figure 1 The target terminal device 11 executes the payment processing method, which includes, but is not limited to, the following steps: S501. Send a merged payment request to the payment server. The merged payment request includes the identity information of the target object, so that the payment server can use the identity information to determine the target account identifier and obtain M orders associated with the target account identifier from the merged order database, where M is a positive integer.

[0051] In one embodiment, the target terminal device can send a merged payment request to the payment server. This merged payment request includes the identity information of the target object. The payment server can use this identity information to uniquely identify the target object and obtain the account identifier corresponding to the target object as the target account identifier. The merged order database includes one or more orders. Since these one or more orders are associated with the account identifier, the payment server can obtain M orders associated with the target account identifier from these one or more orders and send the M orders to the target terminal device.

[0052] S502: Receive M orders sent by the payment server.

[0053] S503. If a payment confirmation operation is received, a payment confirmation request is sent to the payment server. The payment confirmation request includes at least one of the M orders and is used to instruct the payment server to make a combined payment for at least one of the M orders.

[0054] In one embodiment, the target terminal device can display the received M orders, and the target object can select from the displayed M orders on the target terminal device. When the selection operation for at least one of the M orders occurs, at least one order is determined from the M orders based on the selection operation, and a payment confirmation request is sent to the payment server. The payment confirmation request includes the at least one order. The payment server can obtain the graphic code information bound to the target account identifier and use the graphic code information bound to the target account identifier to perform a combined payment for the at least one order.

[0055] In this embodiment, the target terminal device can send a merged payment request to the payment server. The payment server can respond to the merged payment request by using the identity information of the target object contained in the merged payment request to obtain the target account identifier, thereby performing merged payment on at least one of the M orders associated with the target account identifier, which can improve the convenience and security of digital payment.

[0056] Please see Figure 6 , Figure 6 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 4 The payment processing method described in the embodiments of this application can be provided by... Figure 1The payment processing method is jointly executed by the payment server 10, the target terminal device 11, and the order processing device 12. This payment processing method includes, but is not limited to, the following steps: S601, The order processing device sends the image data of the target object to the payment server.

[0057] In one embodiment, the order processing device may include a shooting device, which may be a 3D camera, such as a depth camera or an infrared camera. The shooting device can acquire video data of the target object after obtaining permission from the target object. The image data of the video data may include facial data, iris data, etc. The order processing device can optimize multiple image data from the video data of the target object to obtain the target object's image data. Specifically, a preset image quality evaluation index can be obtained. This index includes one or more of the following: size of the target part (e.g., face, iris), angle of the target part, contrast, brightness, and sharpness. The image quality evaluation index can be used to evaluate and select the optimal image data from the multiple image data included in the video data of the target object. For example, if the target part is a face, the angle score is higher when the face is facing forward, or the higher the image sharpness, the higher the score. The image data with the highest score can be selected as the target object's image data. Furthermore, the order processing device can send the target object's image data to a payment server.

[0058] S602. The payment server receives the image data of the target object sent by the order processing device, performs identity recognition processing on the image data of the target object, and obtains the target account identifier.

[0059] In one embodiment, the payment server can extract image features from the image data of the target object, and extract image features from the image data of multiple objects, calculate the similarity between the image features of the image data of the target object and the image features of the image data of multiple objects, take the object with the highest similarity as the target object, and take the account identifier corresponding to the object with the highest similarity as the target account identifier.

[0060] S603. If the order processing device receives a confirmation operation from the target object for the displayed order merging prompt information, it sends an order merging request to the payment server. The order merging request includes the order data to be merged.

[0061] In one embodiment, after obtaining the target account identifier, the payment server can send the target account identifier to the order processing device. The order processing device can display a confirmation prompt message for the target account identifier (or the account information corresponding to the target account identifier) ​​for the target object to perform secondary identity verification. When the payment server receives the target object's confirmation operation for the confirmation prompt message, it can display an order merging prompt message. When the order processing device receives the target object's confirmation operation for the displayed order merging prompt message, it sends an order merging request to the payment server. The order merging request includes the order data to be merged, which may include product information added using the scanning device of the order processing device.

[0062] In another embodiment, when the order processing device receives a confirmation prompt from the target object regarding the target account identifier, it can display a product entry control. After the target object selects the product entry control, it can add product information using the scanning device of the order processing device. When the target object finishes adding the product information, it can select the order merging control. When the order processing device receives the target object's selection of the order merging control, it uses the added product information as the order data to be merged and sends an order merging request to the payment server. The order merging request may include the order data to be merged.

[0063] In a feasible embodiment, the target object adds product information using the barcode scanner of the order processing device. When the target object finishes adding the product information, in addition to displaying the order merging control, a regular payment control can also be displayed. When the target object selects the regular payment control, it can generate order data using the added product information. The order processing device can send an order payment request to the payment server. The order payment request includes the order data. The payment server can use the graphic code information bound to the target account identifier to make a regular payment for the order corresponding to the order data.

[0064] S604. In response to the order merging request sent by the order processing device, the payment server associates the target account identifier with each order corresponding to the order data and writes it into the merged order database, and returns the order merging result to the order processing device.

[0065] In one implementation, the target object can use the barcode scanner of the order processing device to add product information and generate order data containing the added product information. Then, the order processing device can obtain the image data of the target object and send the order data and the image data of the target object to the payment server. The payment server uses the image data of the target object to perform identity recognition processing to obtain the target account identifier. Then, the target account identifier is associated with the order corresponding to the order data and written into the merged order database.

[0066] S605. The target terminal device sends a merged payment request to the payment server. The merged payment request includes the identity information of the target object.

[0067] In one embodiment, the target terminal device may be a user terminal device. The target object may make a selection operation on the displayed merge payment control in the application that provides merge payment services. When the target terminal device determines that the target object has made a selection operation on the merge payment control, it may obtain the account identifier bound to the target terminal device after obtaining the target object's permission or authorization. The account identifier may be the account identifier corresponding to the account registered by the target object in the application that provides merge payment services. The merge payment request is generated using the account identifier bound to the target terminal device. At this time, the identity information of the target object is the account identifier bound to the target terminal device.

[0068] In one feasible implementation, the target terminal device can be an order processing device, which can display a merge payment control. When the target object selects the merge payment control and the target terminal device obtains the target object's permission, it can acquire the target object's video data. For example, when the target terminal device is a face recognition payment device or an iris recognition payment device, the image data in the target object's video data can include the target object's face or iris. Furthermore, multiple image data in the target object's video data can be optimized to obtain the target object's image data. A merge payment request is generated using the target object's image data. At this time, the target object's identity information is the target object's image data.

[0069] S606. In response to the merged payment request, the payment server uses the identity information to determine the target account identifier and retrieves M orders associated with the target account identifier from the merged order database.

[0070] In one embodiment, if the target terminal device is an order processing device and the identity information of the target object is the image data of the target object, the payment server can perform identity recognition processing on the image data of the target object to obtain the target account identifier. If the target terminal device is a user terminal device and the identity information of the target object is the account identifier bound to the user terminal device, the payment server can use the account identifier bound to the user terminal device as the target account identifier. Furthermore, M orders that are associated with the target account identifier can be obtained from one or more orders included in the merged order database.

[0071] S607. The target terminal device receives M orders sent by the payment server.

[0072] In one embodiment, the target terminal device can receive and display M orders sent by the payment server. The target object can make a selection operation on the M orders. The target terminal device obtains the selection operation of the target object on the M orders and determines at least one selected order from the M orders based on the selection operation.

[0073] S608. If the target terminal device receives a payment confirmation operation, it sends a payment confirmation request to the payment server. The payment confirmation request includes at least one of the M orders.

[0074] In one embodiment, after the target terminal device determines at least one order based on the target object's selection operation for M orders, it can send a payment confirmation request to the payment server.

[0075] S609. In response to the payment confirmation request, the payment server performs a combined payment on at least one of the M orders and returns the combined payment result to the target terminal device.

[0076] In one embodiment, the payment server may, in response to a payment confirmation request, obtain the graphic code information bound to the target account identifier, perform merged payment on at least one order based on the graphic code information bound to the target account identifier, and return the merged payment result to the target terminal device. When the merged payment result indicates that at least one order has been successfully paid, at least one order may be deleted from the merged order database.

[0077] In this embodiment, the order processing device can send the image data of the target object and the order data to be merged to the payment server. The payment server uses the image data of the target object to obtain the target account identifier, and then associates the target account identifier with the order data and writes it into the merged order database. In addition, the target terminal device can send a merged payment request to the payment server. The payment server can respond to the merged payment request, use the identity information of the target object contained in the merged payment request to obtain the target account identifier, and then perform merged payment on at least one of the M orders associated with the target account identifier, which can improve the convenience and security of digital payment.

[0078] Please see Figure 7 , Figure 7 A flowchart illustrating a payment processing method provided in this application embodiment. Figure 5 The payment processing method described in the embodiments of this application can be provided by... Figure 2 The payment processing method is jointly executed by the payment server 10, the target terminal device 11, the order processing device 12, and the management server 13. This payment processing method includes, but is not limited to, the following steps: S701, The order processing device sends the image data of the target object to the payment server.

[0079] S702. The payment server receives the image data of the target object sent by the order processing device, performs identity recognition processing on the image data of the target object, and obtains the target account identifier.

[0080] For detailed descriptions of S701 and S702, please refer to S601 and S602; they will not be repeated in this embodiment.

[0081] S703, The payment server sends the target account identifier to the management server.

[0082] S704. If the order processing device receives a confirmation operation from the target object regarding the displayed order merging prompt information, it sends an order merging request to the management server. The order merging request includes the order data to be merged.

[0083] In one feasible embodiment, the order processing device can receive a target account identifier sent by the payment server and display a confirmation prompt message for the target account identifier. When the target object confirms the confirmation prompt message, the device displays an order merging prompt message. When the target object confirms the order merging prompt message, the order processing device can obtain the product information added through the order processing device, generate order data containing the added product information, and send an order merging request containing the order data to the management server. The management server uses the order data as the order data to be merged.

[0084] In one embodiment, the management server can retrieve the cumulative orders associated with the target account identifier from the merged order database using the target account identifier. The cumulative orders may include product information added by the target object when shopping at the supermarket. The cumulative orders can be sent to the order processing device, which displays the product information included in the cumulative orders. The target object can view the product information added in the cumulative orders and delete the added product information, or add new product information to the cumulative orders using a barcode scanner. The order processing device can display an order merging control. When the target object completes its operation, it can select the order merging control. The order processing device then generates an order merging request using the updated cumulative orders and sends it to the management server. In response to the order merging request, the management server uses the updated cumulative orders included in the order merging request as the order data to be merged.

[0085] S705: In response to the order merging request sent by the order processing device, the management server associates the target account identifier with each order corresponding to the order data and writes it into the merged order database, and returns the order merging result to the order processing device.

[0086] S706. The target terminal device sends a merged payment request to the payment server. The merged payment request includes the identity information of the target object.

[0087] In one embodiment, the target terminal device may be a user terminal device. The target object may make a selection operation on the displayed merge payment control in the application that provides merge payment services. When the target terminal device determines that the target object has made a selection operation on the merge payment control, it may obtain the account identifier bound to the target terminal device after obtaining the target object's permission or authorization. The account identifier may be the account identifier of the account registered by the target object in the application that provides merge payment services. The merge payment request is generated using the account identifier bound to the target terminal device. At this time, the identity information of the target object is the account identifier bound to the target terminal device.

[0088] In one feasible implementation, the target terminal device can be an order processing device, which can display a merge payment control. When the target object selects the merge payment control and the target terminal device obtains the target object's permission, it can acquire the target object's video data. For example, when the target terminal device is a face recognition payment device or an iris recognition payment device, the image data in the target object's video data can include the target object's face data or iris data. Furthermore, multiple image data in the target object's video data can be optimized to obtain the target object's image data. A merge payment request is generated using the target object's image data. At this time, the target object's identity information is the target object's image data.

[0089] S707. In response to the merged payment request, the payment server uses the identity information to determine the target account identifier and sends the target account identifier to the management server.

[0090] In one embodiment, if the target terminal device is an order processing device and the identity information of the target object is the image data of the target object, the payment server can perform identity recognition processing on the image data of the target object to obtain the target account identifier. If the target terminal device is a user terminal device and the identity information of the target object is the account identifier bound to the user terminal device, the payment server can use the account identifier bound to the user terminal device as the target account identifier. Furthermore, the target account identifier can be sent to the management server.

[0091] S708, the management server uses the target account identifier to retrieve M orders associated with the target account identifier from the merged order database, and sends the M orders to the target terminal device.

[0092] In one embodiment, the management server can obtain M orders that are associated with the target account identifier from one or more orders included in the merged order database, and further send the M orders to the payment server, which then sends the M orders to the target terminal device.

[0093] S709. The target terminal device receives M orders sent by the management server.

[0094] In one embodiment, the target terminal device can receive and display M orders sent by the management server, and the target object can perform a selection operation on the M orders. The target terminal device obtains the selection operation of the target object on the M orders and determines at least one selected order from the M orders based on the selection operation.

[0095] S710. If the target terminal device receives a payment confirmation operation, it sends a payment confirmation request to the payment server. The payment confirmation request includes at least one of the M orders.

[0096] S711. In response to the payment confirmation request, the payment server performs a combined payment for at least one of the M orders and returns the combined payment result to the target terminal device.

[0097] In one embodiment, the payment server may, in response to a payment confirmation request, obtain the graphic code information bound to the target account identifier, perform merged payment on at least one order based on the graphic code information bound to the target account identifier, and return the merged payment result to the target terminal device. When the merged payment result indicates that at least one order has been successfully paid, at least one order may be deleted from the merged order database.

[0098] In a feasible embodiment, after the target terminal device sends a merged payment request to the payment server, the payment server can obtain the target account identifier and the graphic code information bound to the target account identifier, and send the obtained target account identifier to the management server. The management server uses the target account identifier to obtain M orders associated with the target account identifier from the merged order database, and then sends the M orders to the payment server. The payment server uses the graphic code information bound to the target account identifier to perform merged payment on the M orders.

[0099] In this embodiment, the order processing device can send the image data of the target object and the order data to be merged to the payment server. The payment server uses the image data of the target object to obtain the target account identifier, and then sends the target account identifier to the management server. The management server associates the target account identifier with the orders corresponding to the order data and writes them into the merged order database. In addition, the target terminal device can send a merged payment request to the payment server. The payment server can respond to the merged payment request, use the identity information of the target object contained in the merged payment request to obtain the target account identifier, and send the target account identifier to the management server. The management server obtains the M orders associated with the target account identifier, and then the payment server performs merged payment on at least one of the M orders, which can improve the convenience and security of digital payment.

[0100] Please see Figure 8 , Figure 8 A system illustration of a payment processing system provided in this application embodiment. Figure 3 The payment processing system includes a third-party platform 801, a merchant platform 802, and an order processing device 803. Figure 8 (Using order processing device A and order processing device B as examples for illustration).

[0101] The third-party platform can correspond to a payment server, and can provide identity verification, account services, and payment services. The identity verification service, upon receiving image data of the target object from the order processing device, performs identity verification on the target object's image data to obtain image data of objects with high similarity to the target object. The account service can find the account identifier corresponding to the object with high similarity determined by the identity verification service (i.e., the target object) as the target account identifier. The payment service can obtain the graphic code information bound to the target account identifier and use this graphic code information to execute the payment task.

[0102] The merchant platform can correspond to a management server, providing order merging services and managing a merged order database. This order merging service, upon receiving a target account identifier and the order data to be merged, associates the target account identifier with the corresponding order data and writes it into the merged order database. It also retrieves the cumulative orders associated with the target account identifier from the merged order database using the target account identifier.

[0103] Order processing equipment can provide a data acquisition module, such as Figure 8The data acquisition module includes an acquisition module and a body biopsy module. The acquisition module uses a camera to acquire video data of the target image, and the body biopsy module can select the target object's image data from multiple image data included in the video data. Additionally, the order processing device can also provide order merging controls (e.g., Figure 8 "Order Accumulation" and merged payment controls (e.g.) Figure 8 In the "Merged Payment" mechanism, when the target object selects an order merge control, it can send an order merge request to a third-party platform. This request includes the target object's image data. The third-party platform responds to the request by using the target object's image data for identity verification, obtaining the target account identifier, and sending it to the product platform. The product platform then retrieves the accumulated orders from the merged order database. These accumulated orders include one or more product information items, which can be sent to the order processing device. Further, the order processing device uses a provided accumulated order update module to allow the target object to delete product information from the one or more product information items or add new product information (achieved through a product recognition module and a barcode scanner) to generate new order data. The order processing device then sends the new order data to the product platform, which associates the target account identifier with the corresponding order and writes it into the merged order database. When the target user selects the merge payment control, the order processing device becomes the target terminal device. The target terminal device can send a merge payment request to a third-party platform. This request includes the target user's image data. The third-party platform uses the target user's image data for identity verification, obtains the target account identifier, and then sends it to the product platform. The product platform uses the target account identifier to retrieve the cumulative orders associated with the target account identifier from the merge order database and sends these cumulative orders to the third-party platform. The third-party platform then obtains the graphic code information bound to the target account identifier and uses this graphic code information to perform merge payment for one or more items included in the cumulative orders. In one implementation, the order processing device can provide a payment result module. This module can display a prompt message containing the cumulative orders and the graphic code information bound to the target account identifier on the target terminal device. When the target user confirms this prompt message, the third-party platform then uses the graphic code information bound to the target account identifier to perform merge payment for one or more items included in the cumulative orders.

[0104] The method described in this application embodiment allows orders to be pre-merged into a merged order database using one or more order processing devices, and batch payments can be made directly in the order processing devices during checkout, which can improve the convenience and security of digital payments and increase payment efficiency.

[0105] Please see Figure 9 , Figure 9 A system illustration of a payment processing system provided in this application embodiment. Figure 4 The payment processing system includes a third-party platform (901), an order processing device (902), and a user terminal device (903).

[0106] Third-party platforms can provide identity verification services, account services, payment services (including payment order services), order merging services, and merged order update services, as well as manage a merged order database. The identity verification service, upon receiving image data of a target object from an order processing device, performs identity verification on the target object's image data to obtain image data of objects with high similarity to the target object. The account service can find the account identifier corresponding to the object with high similarity determined by the identity verification service (i.e., the target object) as the target account identifier. The payment service can obtain the graphic code information bound to the target account identifier and execute the payment task using this graphic code information. The order merging service, upon receiving the target account identifier and the order data to be merged, associates the target account identifier with the corresponding order and writes it into the merged order database, and retrieves the cumulative orders associated with the target account identifier from the merged order database using the target account identifier. The merged order update service can delete orders that have been paid for from the merged order database.

[0107] Order processing equipment can provide a data acquisition module, such as Figure 9 The data acquisition module includes an acquisition module and a body biopsy module. The acquisition module uses a camera to acquire video data of the target image, and the body biopsy module can select the target object's image data from multiple image data included in the video data. Additionally, the order processing device can also provide order merging controls (e.g., Figure 9 "Consolidated payment" and regular payment controls (e.g.) Figure 9In the "Confirm Payment" section, when the target object selects the order merging control, it can send an order merging request to the third-party platform. This order merging request includes the target object's image data. The third-party platform responds to the order merging request by using the target object's image data for identity verification, obtaining the target account identifier. It can then associate the target account identifier with the order data to be merged and write it into the merged order database. When the target object selects the regular payment control, it can send an order payment request to the third-party platform. This order payment request includes the target object's image data. The third-party platform responds to the order payment request by using the target object's image data for identity verification, obtaining the target account identifier, acquiring the graphic code information bound to the target account identifier, and using the graphic code information bound to the target account identifier to perform regular payment for the order data. In one implementation, the order processing device can provide a result page module, through which the order merging result (i.e., ...) can be displayed. Figure 9 The result status will be displayed in the table.

[0108] The user terminal device can provide a basic payment module, based on which it can send a merged payment request to a third-party platform. The merged payment request includes the account identifier bound to the user terminal device. In response to the merged payment request, the third-party platform uses the account identifier bound to the user terminal device as the target account identifier, retrieves M orders associated with the target account identifier from the merged order database, and sends the M orders to the user terminal device. The user terminal device displays the M orders, and the target user selects at least one order from the M orders. The third-party platform then uses the graphic code information bound to the target account identifier to perform merged payment on the at least one order.

[0109] Using the method of this application, payment operations can be performed without using facial recognition payment devices, iris recognition payment devices, or other similar devices. Instead, orders are first merged into a merged order database, and then batch payments are made on the user's terminal device. This can improve the security and convenience of digital payments, as well as enhance the user's sense of security.

[0110] It is understood that in the specific embodiments of this application, image data and other related data of the target object are involved. When the above embodiments of this application are applied to specific products or technologies, permission or consent from the target object is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0111] The methods of the embodiments of this application have been described in detail above. Accordingly, to facilitate better implementation of the methods of the embodiments of this application, the apparatus of the embodiments of this application is provided below. Please refer to... Figure 10 , Figure 10 This is a schematic diagram of the structure of a payment processing device provided in an embodiment of this application.

[0112] In one embodiment, the payment processing device 100 corresponds to a payment server, and the payment processing device 100 may include: The receiving unit 1001 is used to receive a merged payment request sent by the target terminal device, wherein the merged payment request includes the identity information of the target object; Processing unit 1002 is used to determine the target account identifier using the identity information, and to obtain M orders associated with the target account identifier from the merged order database. Each of the M orders is image data and order data of the target object sent by the payment server based on the order processing device. Each order is associated with the target account identifier and written into the merged order database. The processing unit 1002 is further configured to perform a combined payment on at least one of the M orders and return the combined payment result to the target terminal device, where M is a positive integer.

[0113] In one embodiment, the receiving unit 1001 is specifically used to: receive image data of the target object sent by the order processing device; the processing unit 1002 is specifically used to: perform identity recognition processing on the image data of the target object to obtain the target account identifier; the processing unit 1002 is specifically used to: receive an order merging request sent by the order processing device, the order merging request including order data to be merged; the processing unit 1002 is specifically used to: associate the target account identifier with each order corresponding to the order data and write it into the merged order database, and return the order merging result to the order processing device.

[0114] In one embodiment, the receiving unit 1001 is specifically used to: receive image data of the target object sent by the order processing device; the processing unit 1002 is specifically used to: perform identity recognition processing on the image data of the target object to obtain the target account identifier; and send the target account identifier to the management server so that after receiving the order data to be merged sent by the order processing device, the management server associates the target account identifier with each order corresponding to the order data and writes it into the merged order database.

[0115] In one embodiment, the processing unit 1002 is specifically used to: if the target terminal device is the order processing device and the identity information of the target object is the image data of the target object, then perform identity recognition processing on the image data of the target object to obtain a target account identifier; if the target terminal device is a user terminal device and the identity information of the target object is the account identifier bound to the user terminal device, then use the account identifier bound to the user terminal device as the target account identifier.

[0116] In one embodiment, the payment processing device further includes an acquisition unit 1003, which is configured to: acquire graphic code information bound to the target account identifier; the processing unit 1002 is specifically configured to: send the M orders to the target terminal device so that the target terminal device displays the M orders, and determine at least one order based on the target object's selection operation for the M orders; the receiving unit 1001 is specifically configured to: receive a payment confirmation request sent by the target terminal device, the payment confirmation request including the at least one order; and the processing unit 1002 is specifically configured to: perform a combined payment for the at least one order based on the graphic code information bound to the target account identifier.

[0117] In one embodiment, the receiving unit 1001 is specifically configured to: if the merged payment result indicates that the at least one order has been successfully paid, then delete the at least one order from the merged order database.

[0118] In one embodiment, the payment processing device 100 corresponds to an order processing device, and the payment processing device 100 may include: The acquisition unit 1003 is used to acquire image data of a target object and send the image data of the target object to the payment server, so that the payment server performs identity recognition processing on the image data of the target object to obtain the target account identifier. Processing unit 1002 is used to display order merging prompt information; The processing unit 1002 is further configured to send an order merging request to the payment server if it receives a confirmation operation from the target object for the order merging prompt information. The order merging request includes order data to be merged. The order merging request is used to instruct the payment server to associate the target account identifier with each order corresponding to the order data and write it into the merged order database. The orders in the merged order database are used by the payment server for merged payment. The receiving unit 1001 is used to receive the order merging result sent by the payment server.

[0119] In one embodiment, the receiving unit 1001 is specifically used to: receive the target account identifier sent by the payment server; the processing unit 1002 is specifically used to: display confirmation prompt information of the target account identifier; if a confirmation operation is received from the target object in response to the confirmation prompt information, then the step of displaying the order merging prompt information is executed.

[0120] In one embodiment, the acquisition unit 1003 is specifically used to: acquire video data of the target object; the processing unit 1002 is specifically used to: determine the image data of the target object from multiple image data included in the video data based on preset image quality evaluation indicators, wherein the image quality evaluation indicators include one or more of the following: size of the target part, angle of the target part, contrast, brightness, and sharpness.

[0121] In one embodiment, the payment processing device 100 corresponds to an order processing device, and the payment processing device 100 may include: The sending unit is used to send a merged payment request to the payment server. The merged payment request includes the identity information of the target object, so that the payment server can use the identity information to determine the target account identifier and obtain M orders associated with the target account identifier from the merged order database, where M is a positive integer. A receiving unit is configured to receive the M orders sent by the payment server; The sending unit is configured to send a payment confirmation request to the payment server if a payment confirmation operation is received. The payment confirmation request includes at least one of the M orders and is used to instruct the payment server to make a combined payment for at least one of the M orders.

[0122] In one embodiment, the processing unit 1002 is specifically used to: display the M orders; the acquisition unit 1003 is specifically used to: acquire the selection operation of the target object for the M orders; and the processing unit 1002 is specifically used to: determine at least one order from the M orders based on the selection operation.

[0123] It is understood that the functions of each functional unit of the payment processing device described in the embodiments of this application can be specifically implemented according to the methods in the above method embodiments, and the specific implementation process can be referred to the relevant descriptions in the above method embodiments, which will not be repeated here.

[0124] In this embodiment, the payment server can receive a merged payment request sent by the target terminal device. This merged payment request includes the target object's identity information. The server can use this identity information to determine the target account identifier and retrieve M (positive integer) orders associated with the target account identifier from the merged order database. At least one of these M orders is then merged for payment, and the merged payment result is returned to the target terminal device. Each of the M orders is generated by the payment server based on the target object's image data and order data sent by the order processing device, and each order is associated with the target account identifier and written into the merged order database. Using this method, the target object can merge orders into the merged order database through the order processing device and then perform batch payments on the target terminal device, improving the convenience and security of digital payments.

[0125] like Figure 11 As shown, Figure 11 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. The internal structure of the computer device 110 is as follows: Figure 11 As shown, it includes: one or more processors 1101, memory 1102, and communication interface 1103. The processors 1101, memory 1102, and communication interface 1103 can be connected via bus 1104 or other means. This embodiment of the application takes the connection via bus 1104 as an example.

[0126] The processor 1101 (or CPU, Central Processing Unit) is the computing and control core of the computer device 110. It can parse various instructions within the computer device 110 and process various data. For example, the CPU can parse power-on / off commands sent by a target object to the computer device 110 and control the computer device 110 to perform power-on / off operations. Furthermore, the CPU can transmit various interactive data between internal structures of the computer device 110, and so on. The communication interface 1103 may optionally include standard wired interfaces or wireless interfaces (such as Wi-Fi, mobile communication interfaces, etc.), and is controlled by the processor 1101 for sending and receiving data. The memory 1102 is the storage device in the computer device 110, used to store computer programs and data. It is understood that the memory 1102 here can include both the computer device 110's built-in memory and extended memory supported by the computer device 110. The memory 1102 provides storage space for storing the operating system of the computer device 110, which may include, but is not limited to, Windows, Linux, Android, iOS, etc. This application does not limit this.

[0127] In one embodiment, the computer device corresponds to a payment server, and the processor 1101 performs the following operations by running a computer program stored in the memory 1102: In this embodiment, the payment server can receive a merged payment request sent by the target terminal device. This merged payment request includes the target object's identity information. The server can use this identity information to determine the target account identifier and retrieve M (positive integer) orders associated with the target account identifier from the merged order database. At least one of these M orders is then merged for payment, and the merged payment result is returned to the target terminal device. Each of the M orders is generated by the payment server based on the target object's image data and order data sent by the order processing device, and each order is associated with the target account identifier and written into the merged order database. Using this method, the target object can merge orders into the merged order database through the order processing device and then perform batch payments on the target terminal device, improving the convenience and security of digital payments.

[0128] In one embodiment, the processor 1101 is specifically configured to: receive image data of the target object sent by the order processing device; perform identity recognition processing on the image data of the target object to obtain the target account identifier; receive an order merging request sent by the order processing device, the order merging request including order data to be merged; associate the target account identifier with each order corresponding to the order data and write it into the merged order database, and return the order merging result to the order processing device.

[0129] In one embodiment, the processor 1101 is specifically configured to: receive image data of the target object sent by the order processing device; perform identity recognition processing on the image data of the target object to obtain the target account identifier; and send the target account identifier to the management server so that after receiving the order data to be merged sent by the order processing device, the management server associates the target account identifier with each order corresponding to the order data and writes it into the merged order database.

[0130] In one embodiment, the processor 1101 is specifically configured to: if the target terminal device is the order processing device and the identity information of the target object is the image data of the target object, then perform identity recognition processing on the image data of the target object to obtain a target account identifier; if the target terminal device is a user terminal device and the identity information of the target object is the account identifier bound to the user terminal device, then use the account identifier bound to the user terminal device as the target account identifier.

[0131] In one embodiment, the processor 1101 is specifically configured to: obtain the graphic code information bound to the target account identifier; send the M orders to the target terminal device so that the target terminal device displays the M orders, and determine at least one order based on the target object's selection operation for the M orders; receive a payment confirmation request sent by the target terminal device, the payment confirmation request including the at least one order; and perform a combined payment for the at least one order based on the graphic code information bound to the target account identifier.

[0132] In one embodiment, the processor 1101 is specifically configured to: if the merged payment result indicates that the at least one order has been successfully paid, then delete the at least one order from the merged order database.

[0133] In one embodiment, the computer device corresponds to an order processing device, and the processor 1101 performs the following operations by running a computer program stored in the memory 1102: The image data of the target object is acquired and sent to the payment server, so that the payment server performs identity recognition processing on the image data of the target object to obtain the target account identifier. Displays an order merging notification message; If the target object confirms the order merging prompt information, an order merging request is sent to the payment server. The order merging request includes the order data to be merged. The order merging request is used to instruct the payment server to associate the target account identifier with each order corresponding to the order data and write it into the merged order database. The orders in the merged order database are used by the payment server to perform merged payment. Receive the order merging result sent by the payment server.

[0134] In one embodiment, the processor 1101 is specifically configured to: receive the target account identifier sent by the payment server; display confirmation prompt information for the target account identifier; and if a confirmation operation is received from the target object in response to the confirmation prompt information, execute the step of displaying the order merging prompt information.

[0135] In one embodiment, the processor 1101 is specifically configured to: acquire video data of a target object; and determine image data of the target object from a plurality of image data included in the video data based on a preset image quality evaluation index, wherein the image quality evaluation index includes one or more of the following: size of the target part, angle of the target part, contrast, brightness, and sharpness.

[0136] In one embodiment, the computer device corresponds to a target terminal device, and the processor 1101 performs the following operations by running a computer program stored in the memory 1102: A merged payment request is sent to the payment server. The merged payment request includes the identity information of the target object, so that the payment server can use the identity information to determine the target account identifier and obtain M orders associated with the target account identifier from the merged order database, where M is a positive integer. Receive the M orders sent by the payment server; If a payment confirmation operation is received, a payment confirmation request is sent to the payment server, which instructs the payment server to merge and pay for at least one of the M orders.

[0137] In one embodiment, the processor 1101 is specifically configured to: display the M orders; obtain the selection operation of the target object for the M orders; and determine at least one order from the M orders based on the selection operation.

[0138] In specific implementations, the processor 1101, memory 1102, and communication interface 1103 described in the embodiments of this application can execute the implementation method described in the payment processing method provided in the embodiments of this application, or the implementation method described in the payment processing device provided in the embodiments of this application, which will not be repeated here.

[0139] In this embodiment, the payment server can receive a merged payment request sent by the target terminal device. This merged payment request includes the target object's identity information. The server can use this identity information to determine the target account identifier and retrieve M (positive integer) orders associated with the target account identifier from the merged order database. At least one of these M orders is then merged for payment, and the merged payment result is returned to the target terminal device. Each of the M orders is generated by the payment server based on the target object's image data and order data sent by the order processing device, and each order is associated with the target account identifier and written into the merged order database. Using this method, the target object can merge orders into the merged order database through the order processing device and then perform batch payments on the target terminal device, improving the convenience and security of digital payments.

[0140] This application also provides a computer-readable storage medium storing a computer program that, when run on a computer device, causes the computer device to execute the payment processing method of any of the possible implementations described above. Specific implementation details are provided above and will not be repeated here.

[0141] This application also provides a computer program product, which includes a computer program or computer instructions. When executed by a processor, the computer program or computer instructions implement the steps of the payment processing method provided in this application. The specific implementation method can be found in the foregoing description and will not be repeated here.

[0142] This application also provides a computer program comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the payment processing method provided in this application. The specific implementation can be found in the foregoing description and will not be repeated here.

[0143] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0144] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0145] The above-disclosed embodiments are only some of the embodiments of this application, and should not be construed as limiting the scope of this application. Therefore, any equivalent changes made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A payment processing method, characterized in that, Applied to a payment server, the method includes: The system receives a consolidated payment request sent by a target terminal device, the consolidated payment request including the identity information of the target object; the target terminal device is a user terminal device or a first order processing device. The target account identifier is determined using the identity information, and M orders associated with the target account identifier are retrieved from the merged order database; The payment is made in combination for at least one of the M orders, and the combined payment result is returned to the target terminal device, where M is a positive integer. The method further includes: The system receives image data of the target object sent by the second order processing device and performs identity recognition processing on the image data of the target object to obtain a target account identifier; the second order processing device is a different order processing device from the first order processing device. Receive an order merging request sent by the second order processing device, the order merging request including order data to be merged; The target account identifier and the order corresponding to the order data are associated and written into the merged order database, and the order merging result is returned to the second order processing device.

2. The method according to claim 1, characterized in that, The step of associating the target account identifier with the order corresponding to the order data and writing it into the merged order database includes: The target account identifier is sent to the management server so that after receiving the order data to be merged from the order processing device, the management server associates the target account identifier with the order corresponding to the order data and writes it into the merged order database.

3. The method according to claim 1 or 2, characterized in that, The step of determining the target account identifier using the identity information includes: If the target terminal device is the first order processing device, and the identity information of the target object is the image data of the target object, then the image data of the target object is subjected to identity recognition processing to obtain the target account identifier; If the target terminal device is a user terminal device, and the identity information of the target object is the account identifier bound to the user terminal device, then the account identifier bound to the user terminal device shall be used as the target account identifier.

4. The method according to claim 1 or 2, characterized in that, The method of merging and paying for at least one of the M orders includes: Obtain the graphic code information bound to the target account identifier; The M orders are sent to the target terminal device so that the target terminal device displays the M orders, and at least one order is determined based on the target object's selection operation for the M orders; Receive a payment confirmation request sent by the target terminal device, the payment confirmation request including the at least one order; The at least one order is merged and paid based on the graphic code information bound to the target account identifier.

5. The method according to claim 1, characterized in that, The method further includes: If the merged payment result indicates that at least one order has been successfully paid, then at least one order will be deleted from the merged order database.

6. A payment processing method, characterized in that, Applied to a second order processing device, the method includes: The image data of the target object is acquired and sent to the payment server, so that the payment server can perform identity recognition processing on the image data of the target object to obtain the target account identifier. Displays an order merging notification message; If the target object confirms the order merging prompt, an order merging request is sent to the payment server. The order merging request includes the order data to be merged. The order merging request instructs the payment server to associate the target account identifier with the corresponding order data and write it into the merged order database. The merged order database is used by the payment server, upon receiving a merged payment request from the target terminal device, to determine the target account identifier using the target object's identity information in the merged payment request, retrieve M orders associated with the target account identifier from the merged order database, perform merged payment on at least one of the M orders, and return the merged payment result to the target terminal device. M is a positive integer. The target terminal device is either a user terminal device or a first order processing device, and the second order processing device is a different order processing device from the first order processing device. Receive the order merging result sent by the payment server.

7. The method according to claim 6, characterized in that, The method further includes: Receive the target account identifier sent by the payment server; Display a confirmation message indicating the target account identifier; If a confirmation operation is received from the target object in response to the confirmation prompt, then the step of displaying the order merging prompt is executed.

8. The method according to claim 6, characterized in that, The acquisition of image data of the target object includes: Obtain video data of the target object; Based on preset image quality evaluation indicators, the image data of the target object is determined from multiple image data included in the video data. The image quality evaluation indicators include one or more of the following: size of the target part, angle of the target part, contrast, brightness, and sharpness.

9. A payment processing method, characterized in that, The method is applied to a target terminal device, which is either a user terminal device or a first order processing device, and further includes: A merged payment request is sent to the payment server. The merged payment request includes the identity information of the target object, so that the payment server can use the identity information to determine the target account identifier and retrieve M orders associated with the target account identifier from the merged order database, where M is a positive integer. Each of the M orders is generated when the payment server receives image data of the target object from a second order processing device, performs identity recognition processing on the image data to obtain the target account identifier, receives an order merge request from the second order processing device, retrieves order data from the order merge request, and associates the target account identifier with the order corresponding to the order data, then writes it into the merged order database. The second order processing device is a different order processing device from the first order processing device. Receive the M orders sent by the payment server; If a payment confirmation operation is received, a payment confirmation request is sent to the payment server, which instructs the payment server to merge and pay for at least one of the M orders.

10. The method according to claim 9, characterized in that, The method further includes: Display the M orders; Obtain the selection operation of the target object for the M orders; Based on the selection operation, at least one order is determined from the M orders.

11. A payment processing device, characterized in that, It includes units for implementing the payment processing method as described in any one of claims 1-5, or units for implementing the payment processing method as described in any one of claims 6-8, or units for implementing the payment processing method as described in any one of claims 9-10.

12. A computer device, characterized in that, The computer device includes a memory, a communication interface, and a processor, wherein the memory, the communication interface, and the processor are interconnected; the memory stores a computer program, and the processor calls the computer program stored in the memory to implement the payment processing method as described in any one of claims 1-5, or to implement the payment processing method as described in any one of claims 6-8, or to implement the payment processing method as described in any one of claims 9-10.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the payment processing method as described in any one of claims 1-5, or includes methods for implementing the payment processing method as described in any one of claims 6-8, or includes methods for implementing the payment processing method as described in any one of claims 9-10.

14. A computer program product, characterized in that, The computer program product includes a computer program or computer instructions that, when executed by a processor, implement the payment processing method as described in any one of claims 1-5, or implement the payment processing method as described in any one of claims 6-8, or implement the payment processing method as described in any one of claims 9-10.

Images