Multi-person payment method, device, equipment and medium

Abstract

The embodiment of the invention discloses a multi-person payment method and device, equipment and a medium. According to the scheme, the method comprises the following steps: after a short-distance communication connection is established between a first terminal and a second terminal, transaction identification information of transactions needing to be paid by a plurality of users is sent to the second terminal through the short-distance communication connection; wherein each user in the plurality of users needs to pay a part of money in the transaction. Then, payment result information fed back by a server can be obtained, and the server is a target server for the second terminal to send a payment processing request based on the transaction identification information; and the server executes a payment process based on the payment processing request to generate the payment result information.

Description

Technical Field

[0001] The present application relates to the field of short-distance communication technology, and in particular to a method, device, equipment and medium for multi-person payment. Background Art

[0002] With the development of the times, electronic payment is becoming more and more popular, and multi-person payment between friends has also become a trend, such as AA payment between friends, or multi-person payment in non-AA form. For example, in a multi-person payment scenario, friends share bills, and each person shares part of the cost. At present, multi-person payment orders are mainly realized through sharing of various online social products. For example, pictures or links related to the order are shared with friends through chat sharing. Before payment, the transaction executor needs to enter the corresponding social product and find the order QR code or order link shared by the transaction initiator before payment can be made. In addition, users who have a friend relationship or are in the same group can make multi-person payments, which is not convenient enough.

[0003] In view of this, a more convenient multi-person payment solution needs to be provided. Summary of the invention

[0004] In view of this, embodiments of the present application provide a method, apparatus, device and medium for multi-person payment to provide a more convenient multi-person payment solution.

[0005] To solve the above technical problems, an embodiment of this specification provides a first multi-person payment method, including: a first terminal establishes a short-distance communication connection with a second terminal; transaction identification information of a transaction that needs to be paid by multiple users is sent to the second terminal through the short-distance communication connection; each of the multiple users needs to pay a part of the amount in the transaction; payment result information feedback from a server is obtained; the server is the target server for sending a payment processing request to the second terminal based on the transaction identification information; the server executes a payment process based on the payment processing request to generate the payment result information.

[0006] The embodiments of this specification also provide a second method for multi-person payment, including: a second terminal establishes a short-distance communication connection with a first terminal; obtaining transaction identification information of a transaction that needs to be paid by multiple users in the first terminal through the short-distance communication connection; based on the transaction identification information, sending a payment processing request to a server; the server executes a payment process for the second terminal based on the payment processing request; and obtaining payment result information for the second terminal generated by the server based on the payment processing request.

[0007] An embodiment of this specification also provides a third method for multi-person payment, including: obtaining a payment processing request sent by a second terminal; the payment processing request is generated by the second terminal based on transaction identification information obtained from the first terminal through short-range communication; the transaction identification information corresponds to a transaction that needs to be paid by multiple users; each of the multiple users needs to pay a portion of the amount in the transaction; based on the payment processing request, execute the payment process for the second terminal corresponding to the transaction identification information; and send payment result information for the second terminal to the second terminal.

[0008] The embodiments of this specification also provide a device for multi-person payment, including: a connection module, used to establish a short-distance communication connection with a second terminal; a sending module, used to send transaction identification information of a transaction that needs to be paid by multiple users to the second terminal through the short-distance communication connection; each of the multiple users needs to pay a part of the amount in the transaction; an acquisition module, used to obtain payment result information fed back by a server; the server is the target server for the second terminal to send a payment processing request based on the transaction identification information; the server executes a payment process based on the payment processing request to generate the payment result information.

[0009] The embodiments of this specification also provide a second multi-person payment device, including: a connection module, used to establish a short-distance communication connection with a first terminal; a first acquisition module, used to obtain transaction identification information of a transaction that needs to be paid by multiple users in the first terminal through the short-distance communication connection; a sending module, used to send a payment processing request to a server based on the transaction identification information; the server executes a payment process for the second terminal based on the payment processing request; and a second acquisition module, used to obtain payment result information for the second terminal generated by the server based on the payment processing request.

[0010] The embodiments of this specification also provide a third multi-person payment device, including: an acquisition module, used to acquire a payment processing request sent by a second terminal; the payment processing request is generated by the second terminal based on transaction identification information obtained from the first terminal through short-distance communication; the transaction identification information corresponds to a transaction that needs to be paid by multiple users; each of the multiple users needs to pay a portion of the amount in the transaction; an execution module, used to execute the payment process for the second terminal corresponding to the transaction identification information based on the payment processing request; and a sending module, used to send payment result information for the second terminal to the second terminal.

[0011] An embodiment of the present specification also provides a multi-person payment device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to implement the first multi-person payment method mentioned above, or implement the second multi-person payment method mentioned above, or implement the third multi-person payment method mentioned above.

[0012] The embodiments of this specification also provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, can implement the first method of multi-person payment mentioned above, or implement the second method of multi-person payment mentioned above, or implement the third method of multi-person payment mentioned above.

[0013] At least one embodiment provided in this specification can achieve the following beneficial effects: In the embodiments of this specification, in the scenario of multi-person payment, after the first terminal establishes a short-distance communication connection with the second terminal, the first terminal can send the transaction identification information of the transaction that needs to be paid by multiple users to the second terminal through the short-distance communication connection; after the second terminal receives the transaction identification information, it can send a payment processing request to the server based on the transaction identification information; after the server receives the payment processing request, it can execute the payment process based on the payment processing request, generate payment result information, and feed back the payment result information to the first terminal. Thus, when the first terminal needs to send the transaction order to the second terminal, it is no longer necessary to send it in the form of a QR code or link, but to establish a short-distance communication connection with the second terminal, and transmit the transaction identification information to the second terminal based on the short-distance communication connection, so that the second terminal completes the payment at the server based on the transaction identification information. Since the short-distance communication connection is convenient to establish, the user terminals can complete the connection by being close to each other, which can effectively improve the payment convenience in the multi-person payment scenario and improve the user experience.

[0014] On the other hand, even if the user of the first terminal and the user of the second terminal do not have a friend relationship in the terminal application, multi-person payment can be implemented, and the convenience of payment can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0016] Figure 1A schematic diagram of an application scenario of a multi-person payment method provided in an embodiment of this specification; Figure 2 A flowchart of a multi-person payment method provided in an embodiment of this specification; Figure 3 A schematic diagram of a payment page for multiple users to pay provided in an embodiment of this specification; Figure 4 A schematic diagram of a payment result page provided in an embodiment of this specification; Figure 5 A flowchart of a second multi-person payment method provided in an embodiment of this specification; Figure 6 A flowchart of a third multi-person payment method provided in an embodiment of this specification; Figure 7 A swim lane diagram of a multi-person payment method provided in an embodiment of this specification; Figure 8 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a multi-person payment device; Fig. 9 The embodiments of this specification provide corresponding to Figure 5 A schematic diagram of the structure of a second multi-person payment device; Fig.10 The embodiments of this specification provide corresponding to Figure 6 A schematic diagram of the structure of a third multi-person payment device; Fig.11 A schematic diagram of the structure of a multi-person payment device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0017] Many specific details are described in the following description to facilitate a full understanding of the present application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present application, so the present application is not limited by the specific implementation disclosed below.

[0018] The terms used in one or more embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present application. The singular forms of "a", "said" and "the" used in one or more embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of the present application refers to and includes any or all possible combinations of one or more associated listed items.

[0019] It should be understood that, although the terms first, second, etc. may be used to describe various information in one or more embodiments of the present application, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0020] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards in the relevant regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0021] In the prior art, in response to the demand for payment by multiple people, all major mobile payment platforms have launched multi-person payment products, which are used to share bills among friends, with each person sharing part of the expenses. However, currently, multi-person payment orders are mainly shared through various online social products. Before payment, the transaction executor needs to enter the corresponding social product and find the order QR code or order link shared by the transaction initiator before payment can be made. Alternatively, the transaction executor needs to use a terminal to scan the order QR code presented by the transaction initiator before payment can be made, which is not convenient enough.

[0022] In order to solve the defects in the prior art, this solution provides the following embodiments.

[0023] Figure 1 A schematic diagram of an application scenario of a multi-person payment method provided in an embodiment of this specification.

[0024] like Figure 1 As shown, after the first terminal 101 establishes a short-distance communication connection with the second terminal 102, the first terminal 101 can send transaction identification information of a transaction that needs to be paid by multiple users to the second terminal 102 through the short-distance communication connection; after the second terminal 102 receives the transaction identification information, it can send a payment processing request to the server 103 based on the transaction identification information; after receiving the payment processing request, the server 103 can execute the payment process for the second terminal 102 corresponding to the transaction identification information based on the payment processing request, generate payment result information, and feed back the payment result information to the first terminal 101 and the second terminal 102.

[0025] The server 103 includes but is not limited to any device, equipment, platform, server cluster, etc. with computing and processing capabilities. The first terminal 101 and the server 103 can transmit data through a local area network connection, a wide area network connection, an Internet connection, or other types of data network connections, or transmit data through other methods, without specific limitations. Similarly, the second terminal 102 and the server 103 can transmit data through a local area network connection, a wide area network connection, an Internet connection, or other types of data network connections, or transmit data through other methods, without specific limitations.

[0026] The first terminal 101 and the second terminal 102 transmit information based on a short-distance communication connection, wherein the short-distance communication connection method may include but is not limited to: Near Field Communication (NFC) connection, Radio Frequency Identification (RFID) connection, Bluetooth connection, infrared connection, Wi-Fi connection, etc.

[0027] Figure 2 This is a flowchart of a multi-person payment method provided in an embodiment of this specification. From a hardware perspective, the execution subject of the process can be a terminal device, specifically a first terminal. From a program perspective, the execution subject of the process can be an application installed on the terminal device. Figure 2 As shown, the process may include the following steps: Step 202: The first terminal establishes a short-range communication connection with the second terminal.

[0028] In the embodiments of this specification, the first terminal and the second terminal can be any terminal device with short-range communication function, such as a smart phone, a tablet computer, a laptop computer, a PDA, a smart watch, etc. In practical applications, the first terminal can be a terminal device of the transaction initiator, and the second terminal can be a terminal device of the corresponding transaction executor. For example, in a scenario where one or more users of the second device need to pay the user of the first device, the first device is the device of the payee, and the second device is the device of the payee participating in the multi-person payment. In a scenario where a user of a first device needs to pay one or more users of the second device, the first device is the device of the payee, and the second device is the device of the payee participating in the multi-person payment. Alternatively, in other embodiments, the first terminal can also be a terminal device of the transaction executor, and the second terminal can also be a terminal device of the transaction initiator.

[0029] In the embodiments of this specification, short distance communication (Short Distance Communication) is a communication technology that uses transmission media such as radio waves and infrared rays to achieve data transmission within a relatively short distance (usually tens of meters or less). Short distance communication technology is usually reciprocal, that is, the communicating parties are in a relatively equal position, and communication can be achieved without a complex network architecture. Due to the short communication distance and relatively low technical complexity, the cost of short distance communication technology is usually low and suitable for large-scale deployment and application. Short distance communication technology is currently widely used in home networks, vehicle communications, industrial automation, mobile payments and access control.

[0030] Among them, short-distance communication connection methods may include but are not limited to: Near Field Communication (NFC) connection, Radio Frequency Identification (RFID) connection, Bluetooth connection, infrared connection, Wi-Fi connection, etc. Taking the establishment of NFC connection between terminal devices as an example, after the two terminal devices turn on the NFC function, they are close to each other, and the NFC connection between the two terminal devices can be achieved by "sticking" and other methods, which is very convenient and efficient.

[0031] Step 204: Sending transaction identification information of a transaction that needs to be paid by multiple users to the second terminal via the short-range communication connection; each of the multiple users needs to pay a portion of the amount in the transaction.

[0032] In the embodiments of this specification, a transaction that needs to be paid by multiple users refers to a transaction that needs to be paid by two or more users for the same transaction. In actual applications, the first terminal can establish a short-distance communication connection with one or more second terminals, and send transaction identification information to each second terminal through the short-distance communication connection, so that the paying user of each second terminal can make payment based on the transaction identification information obtained from the first terminal.

[0033] In the embodiments of this specification, for a transaction that needs to be paid by multiple users, each of the multiple users needs to pay part of the amount of the transaction. The second device that obtains the transaction identification information provided by the first device can request the server to process the payment. The transaction identification information can be a string of characters, or other information that can identify a transaction, such as identification information used to indicate a transaction order, identification information indicating that multiple users are required to process a transaction order, etc., and there is no specific limitation on this.

[0034] In actual applications, the user of the first terminal may be one of the multiple users who need to pay part of the amount in the transaction. For example, user A, user B, and user C have a meal together. When paying for the meal, the three agree to pay by AA. After user A first pays the entire meal fee using his mobile terminal, user A can initiate AA payment on his mobile terminal. Transaction identification information for paying the transaction will be generated in user A's mobile terminal. Then, his mobile terminal will establish a short-distance communication connection with the mobile terminals of user B and user C, and the transaction identification information corresponding to the meal order will be sent to the mobile terminals of user B and user C. After receiving the transaction identification information corresponding to the meal order, the mobile terminals of user B and user C can complete the payment of the part of the amount they need to pay at the server based on the transaction identification information. Among them, a one-to-one short-range communication connection can be established between the mobile terminal of user A and the mobile terminal of user B and the mobile terminal of user C. For example, the mobile terminal of user A can first communicate with the mobile terminal of user B and then communicate with the mobile terminal of user C; or, the mobile terminal of user A can first communicate with the mobile terminal of user C and then communicate with the mobile terminal of user B.

[0035] In actual applications, the first terminal may also be the merchant's payment device, and the first terminal may not be the transaction executor, for example, the first device may not be the payer. For example: User A, User B, and User C have a meal together. When paying for the meal, the three agree to pay AA. Merchant D sets the payment amount and the number of people at its own payment device, and generates the transaction identification information corresponding to the meal order. After that, User A, User B, and User C hold their mobile phones and approach the merchant D's payment device, and can establish short-distance communication connections respectively. After establishing short-distance communication connections respectively, the merchant D's payment device can send the transaction identification information corresponding to the meal order to User A's mobile phone, User B's mobile phone, and User C's mobile phone respectively. User A, User B, and User C can subsequently complete the payment of part of the amount they need to pay at the server based on the transaction identification information.

[0036] Step 206: Obtain payment result information fed back by the server; the server is the target server to which the second terminal sends a payment processing request based on the transaction identification information; the server executes a payment process based on the payment processing request to generate the payment result information.

[0037] In the embodiments of this specification, the payment result information may include, but is not limited to, at least one of: account avatar information of the transaction executor, account ID information of the transaction executor, time point information of the transaction executor's payment completion, amount information paid by the transaction executor, amount information to be paid by the transaction executor, payment status information of the transaction executor, etc. Among them, the payment status information may include at least one of: unfinished payment, payment in progress, completed payment, payment failure information, etc.

[0038] In actual applications, after the first terminal obtains the payment information of the target transaction that needs to be paid by multiple users and is submitted by the first user based on the payment page, the first terminal can send the payment information to the server and request the server to generate the corresponding transaction identification information. The server can also save the transaction identification information or store the correspondence between the transaction identification information and the target transaction that needs to be paid by multiple users. After the second terminal obtains the transaction identification information of the transaction that needs to be paid by multiple users based on the short-distance communication connection, it can generate a payment processing request carrying the transaction identification information and send the payment processing request to the server. After receiving the payment processing request sent by the second terminal, the server can determine the corresponding target transaction that needs to be paid by multiple users based on the transaction identification information in the payment processing request and perform the deduction work corresponding to the target transaction.

[0039] In actual applications, the server can generate payment result information after executing the corresponding payment process based on the payment processing request sent by the second terminal, and can also feed back the payment result information to the second terminal. The server can also feed back the payment result information to the first terminal, or can also feed back the payment result information to the second terminal and the first terminal, which is not specifically limited.

[0040] Figure 2In the method, in a multi-person payment scenario, after the first terminal establishes a short-distance communication connection with the second terminal, the first terminal can send the transaction identification information of the transaction that needs to be paid by multiple users to the second terminal through the short-distance communication connection; after the second terminal receives the transaction identification information, it can send a payment processing request to the server based on the transaction identification information; after the server receives the payment processing request, it can execute the payment process based on the payment processing request, generate payment result information, and feed back the payment result information to the first terminal. Thus, when the first terminal needs to send the transaction order to the second terminal, it is no longer necessary to send it in the form of a QR code or link, but to establish a short-distance communication connection with the second terminal, and transmit the transaction identification information to the second terminal based on the short-distance communication connection, so that the second terminal completes the payment at the server based on the transaction identification information. Since the short-distance communication connection is convenient to establish, the user terminals can complete the connection by approaching each other, thereby effectively improving the payment convenience in the multi-person payment scenario and improving the user experience. On the other hand, even if the user of the first terminal and the user of the second terminal do not have a friend relationship in the terminal application, multi-person payment can be realized, and the convenience of payment can also be improved.

[0041] based on Figure 2 The method in this specification also provides some specific implementation plans of the method, which are described below.

[0042] Optional, Figure 2 The method in step 202, before the first terminal establishes a short-distance communication connection with the second terminal, may also include: displaying a payment page for payment by multiple users; obtaining payment information submitted by the first user based on the payment page; the payment information includes amount information and information on the number of people involved in the transaction; and determining the transaction identification information based on the payment information.

[0043] In the embodiments of this specification, the first user may be the user of the first terminal, and may also be the transaction initiator user. In actual applications, the user of the first terminal may trigger the display of a payment page for multiple users to pay in a variety of ways. For example, after the user of the first terminal pays the full amount for an order, the control for displaying the payment page may be found in the details page of the order, and prompts such as "AA collection", "AA with friends", and "multi-person payment" may be displayed on the control for displaying the payment page. For another example, the user of the first terminal wants to use a payment application in the first terminal to make a multi-person payment. The operation page of the payment application may include a control for displaying the payment page. For example, the user can find the payment page for multi-person payment according to the preset path. For example, in the payment application, click on the controls such as "collection and payment"-"payment"-"multi-person payment" in sequence, and the payment page may also be displayed. For another example, when the user of the first terminal is a payment merchant, the payment merchant can trigger the payment page for multiple users of "AA collection" when creating a business order collection, so that the merchant can further set the amount that the consumer needs to pay and the number of consumers who need to pay in the payment page.

[0044] In actual applications, the payment page used for payment by multiple users may be generated locally by the first terminal, or may be generated by the first terminal requesting the server, which is not specifically limited.

[0045] In actual applications, the first terminal user can open the target payment application and initiate a multi-person payment in the target payment application. After the first terminal user initiates a multi-person payment in the target payment application, the target payment application can display a payment page for multiple users to pay. In the embodiment of this specification, the first user can enter payment information such as the amount information and the number of people involved in the transaction in the displayed payment page for multiple users to pay, and submit the payment after entering the payment information. The amount information can be the total amount, the per capita amount, or a partial amount, which is not specifically limited.

[0046] In actual applications, the displayed payment page may also include amount information. For example, if the first user pays the full amount for an order and then makes an AA with other users, the paid order includes the paid amount. After the first user finds the control for displaying the payment page in the details page of the paid order and triggers the display of the payment page for multiple users to pay, the displayed payment page may display the amount of the paid order by default, and the first user does not need to enter the amount. The first user may also modify the amount. For another example, the first terminal is associated with a cash register system, and the payment amount and other information have been determined in the cash register system. The payment page of the first terminal may display the amount and other information without the need for the user to enter it manually.

[0047] The payment information submitted by the first user based on the payment page may be input by the first user or displayed by default on the payment page. No user input is required, only user confirmation is required. The source of the payment information is not specifically limited here.

[0048] In actual applications, the payment information provided by the first user based on the payment page may include, but is not limited to, the reason for collection or payment, the payee or payee information specified by the first user, and the payment amount information corresponding to the payee or payee specified by the first user, in addition to the amount information and the number of people involved in the transaction described above. Setting the reason for collection or payment can make the payer or payee more aware of the reason for the transaction, which is conducive to the smooth payment. After the first user specifies the payer or payee, the specified payer or payee can be collected or paid, which is conducive to improving the flexibility and accuracy of payment. In addition, the first user can also specify the amount information that each payer or payee needs to pay, so that the collection or payment can be more flexible.

[0049] Figure 3 A schematic diagram of a payment page for multiple users to pay is provided in an embodiment of this specification. Figure 3 As shown, the total amount, total number of people, and reason for payment can be filled in the payment page. After entering the total amount and total number of people, the per capita payment amount can also be displayed. For example, if the total amount is 1 yuan and the total number of people is 2, the per capita payment amount is 0.5 yuan. Users can also enter the reason for payment in the payment page, or select one from the preset reasons for payment, such as "party", "dinner", and "utility bills".

[0050] Optionally, determining the transaction identification information based on the payment information may specifically include: sending a first payment trigger request containing the payment information to the server; the server generating the transaction identification information based on the payment information; and obtaining the transaction identification information sent by the server.

[0051] In the embodiment of this specification, the first user provides payment information such as amount information and number of people involved in the transaction on the payment page and submits it. The first terminal can send a first payment trigger request carrying the payment information to the server. After receiving the first payment trigger request sent by the first terminal, the server can generate transaction identification information based on the payment information carried in the first payment trigger request.

[0052] In actual applications, the transaction identification information may be in the form of a string, and the transaction identification information may contain one or more characters, and each character may be in any form such as numbers, letters, Chinese characters, symbols, etc. The number of characters contained in the transaction identification information and the combination of each character may be determined according to actual needs or configuration schemes. Alternatively, the transaction identification information may also be in the form of a random number or other forms, which are not specifically limited. Each transaction identification information may correspond to a payment order, wherein a payment order corresponding to one transaction identification information needs to be paid by multiple users. If there are multiple second terminals that need to participate in the transaction, the transaction identification information generated by the first terminal may be one, and multiple second terminals may obtain the same transaction identification information, and then request the server to process their respective payments based on the obtained transaction identification information.

[0053] As an implementation mode, the transaction identification information may represent the information represented by the QR code displayed in an existing multi-person payment scenario, for example, it may be the QR code number corresponding to the QR code.

[0054] In actual applications, after the server generates corresponding transaction identification information based on a payment information, the server can associate and store the payment information with the corresponding transaction identification information, so that the corresponding transactions and payment information that need to be paid by multiple users can be determined based on the transaction identification information later. After the server generates the transaction identification information, the generated transaction identification information can be fed back to the first terminal.

[0055] In actual applications, the first payment trigger request may also carry the identifier of the first terminal or the user identifier of the user logged in to the first terminal. The server may associate and store the generated transaction identification information with the identifier of the first terminal or the user identifier of the user logged in to the first terminal carried in the first payment trigger request, so that the server can subsequently determine the transaction initiator based on the transaction identification information.

[0056] In actual applications, the transaction identification information may also be generated locally by the first terminal using preset rules based on the payment information. After the first terminal generates the transaction identification information, it may send the transaction identification information and the payment information to the server, and the server may associate and store the transaction identification information and the payment information after receiving them.

[0057] Optionally, the short-range communication connection may include an NFC near field communication connection.

[0058] Figure 2 In the method, step 202, the first terminal establishes a short-range communication connection with the second terminal, which may specifically include: the first terminal obtains an electromagnetic signal sent by the second terminal for triggering near field communication.

[0059] Correspondingly, Figure 2In the method, step 204, sending transaction identification information of a transaction that needs to be paid by multiple users to the second terminal through the short-range communication connection can specifically include: sending the transaction identification information to the second terminal through near field communication based on the electromagnetic signal.

[0060] In the embodiments of this specification, near field communication is an emerging technology. Devices using NFC technology (such as mobile phones) can exchange data when they are close to each other. It is evolved from the integration of contactless radio frequency identification (RFID) and interconnection technology. By integrating the functions of inductive card reader, inductive card and point-to-point communication on a single chip, mobile terminals are used to realize mobile payment, electronic ticketing, access control, mobile identity recognition, anti-counterfeiting and other functions.

[0061] In practical applications, the working modes of near field communication can be divided into passive mode and active mode. In the passive mode, the NFC initiator device (also called the master device) needs a power supply device. The master device uses the energy of the power supply device to provide a radio frequency field and sends data to the NFC target device (also called the slave device) based on the electromagnetic signal of the radio frequency field.

[0062] In an embodiment of the present specification, if the short-distance communication connection between the first terminal and the second terminal is an NFC near-field communication connection, the first terminal can establish near-field communication with the second terminal based on the electromagnetic signal sent by the second terminal for triggering near-field communication, and send the transaction identification information fed back by the server to the second terminal through near-field communication.

[0063] Optionally, the short-range communication connection may include a Bluetooth connection; Figure 2 In the method, step 202, the first terminal establishes a short-range communication connection with the second terminal, which may specifically include: the first terminal and the second terminal perform Bluetooth pairing; and establish a Bluetooth connection with the second terminal.

[0064] Correspondingly, sending the transaction identification information of the transaction that needs to be paid by multiple users to the second terminal through the short-range communication connection may specifically include: the first terminal sending the transaction identification information to the second terminal through a Bluetooth connection established with the first terminal.

[0065] In the embodiments of this specification, Bluetooth is a radio technology that supports short-range communication between devices (generally within 10m). Bluetooth can exchange wireless information between many devices including mobile phones, PDAs, wireless headsets, laptops, and related peripherals. Using Bluetooth technology can effectively simplify the communication between mobile communication terminal devices, and can also successfully simplify the communication between devices and the Internet, making data transmission faster and more efficient.

[0066] In actual application, the first terminal can be paired with the second terminal by Bluetooth, and after the pairing is successful, a Bluetooth connection is established between the first terminal and the second terminal. After the Bluetooth connection is established between the first terminal and the second terminal, the transaction identification information can be sent to the second terminal through the Bluetooth connection established with the second terminal.

[0067] Optional, Figure 2 The method in step 202, before the first terminal establishes a short-distance communication connection with the second terminal, may also include: processing the transaction identification information according to a preset protocol rule to obtain processed transaction identification information; the preset protocol rule is a protocol rule that complies with the short-distance communication; and saving the processed transaction identification information to the short-distance communication module of the first terminal.

[0068] In the embodiments of this specification, the communication protocol refers to the rules and agreements that the terminal devices of both parties must follow to complete the communication or service. The protocol defines the format used by the data unit, the information and meaning that the information unit should contain, the connection method, and the timing of information sending and receiving, so as to ensure that the data can be smoothly transmitted to the specified terminal device. The short-range communication protocol may refer to the technical specifications used to achieve wireless communication between devices within a short distance. Short-range communication protocols are generally suitable for data transmission within a distance of tens of meters or less, and have the characteristics of low power consumption, low cost, and peer-to-peer communication.

[0069] In actual applications, short-distance communication is established between the first terminal and the second terminal, and the protocol rules of short-distance communication need to be complied with. The transaction identification information, as data that needs to be transmitted using short-distance communication, needs to be processed using preset protocol rules that comply with the protocol rules of short-distance communication. After processing, the transaction identification information can be saved in the short-distance communication module of the first terminal, so that the first terminal can subsequently send the transaction identification information to the second terminal based on short-distance communication.

[0070] Optionally, the short-range communication module may include at least one of a Bluetooth module and an NFC near-field communication module.

[0071] In actual applications, short-distance communication modules may include but are not limited to: Bluetooth module, NFC near-field communication module, radio frequency identification module, infrared connection module, Wi-Fi module, etc. Each module may correspond to a short-distance communication connection method. For example: Terminal 1 and Terminal 2 both have NFC near-field communication modules. After Terminal 1 and Terminal 2 both turn on the NFC near-field communication function, they can achieve NFC connection when they are close to each other.

[0072] Optionally, if the short-distance communication is NFC near field communication; the method may further include: enabling the first terminal to enter a card emulation mode of near field communication.

[0073] Correspondingly, the storing the processed transaction identification information in the short-distance communication module of the first terminal may specifically include: storing the processed transaction identification information in a simulated card obtained in the first terminal based on the card simulation mode.

[0074] In the embodiments of this specification, near field communication can be divided into three working modes, namely: point-to-point communication mode, card reader mode and card emulation mode. Among them, two NFC devices can exchange data in the point-to-point mode. For example, multiple digital cameras and mobile phones with NFC functions can use NFC technology to wirelessly interconnect and exchange data. For the point-to-point form, the key is to connect two devices with NFC functions so that data transmission between points can be realized.

[0075] In actual applications, the first terminal and the second terminal can perform near field communication through point-to-point mode, or through card reader mode and card simulation mode, and there is no specific limitation on this. Among them, the card simulation mode simulates a device with NFC function into a tag or contactless card. For example, a mobile phone that supports NFC can be read as an access card, bank card, etc. The NFC device in the card reader mode can be used as a contactless reader / writer. For example, a mobile phone with NFC function turned on can read and write tags that support the NFC data format standard. The NFC device in the card reader mode can read data from the NFC device in the card simulation mode.

[0076] In actual applications, the first terminal can be turned on in the card emulation mode of near field communication, and the second terminal can be turned on in the card reader mode of near field communication accordingly. When the first terminal and the second terminal are close to each other, an NFC connection can be established, and after the connection, the second terminal can read the data in the first terminal. Specifically, after the first terminal saves the processed transaction identification information to the simulated card obtained based on the card emulation mode, the second terminal in the card reader mode can read the transaction identification information from the simulated card.

[0077] Optionally, the payment result information may include at least one of information of paid users, information of non-paid users, information of the number of people who have paid, information of the paid amount, information of the number of non-paid people, and information of the unpaid amount.

[0078] In the embodiments of this specification, the information of the paid user may include, but is not limited to: the account avatar information of the paid user, the nickname information of the paid user, the terminal device name information of the paid user, and the account ID information of the paid user. The information of the unpaid user may include, but is not limited to: the account avatar information of the user who has not completed the payment, the nickname information of the user who has not completed the payment, the terminal device name information of the user who has not completed the payment, and the account ID information of the user who has not completed the payment.

[0079] As an implementation mode, the payment result information may also include the first transaction amount information executed by the second terminal; correspondingly, the method may also include: displaying a payment result page; the payment result page includes the first transaction amount information or the first completed transaction amount information obtained based on the first transaction amount information.

[0080] In actual applications, there may be multiple devices interacting with the first terminal. For example, after the first terminal is close to the second terminal, the first terminal may also be close to the third terminal, and the user of the third terminal may be a user who needs to make a multi-person payment. Optionally, the method in the embodiment of this specification may also include: obtaining the second transaction amount information executed by the third terminal; the third terminal is the terminal of the user who needs to pay for the transaction; displaying the second transaction amount information or the second completed transaction amount information on the payment result page; the second completed transaction amount information is information obtained by adding the transaction amount represented by the second transaction amount information to the completed transaction amount represented by the first completed transaction amount information.

[0081] If the first terminal user specifies the corresponding transaction party user when initiating the transaction, such as the transaction execution party user, the payment result page may also display the information of the unpaid user, such as the information of the unpaid user. The information of the unpaid user may refer to the avatar information, user nickname information, account ID information, etc. of the user who has not paid or received the payment.

[0082] In the embodiments of this specification, transaction amount information may refer to the amount information paid by each paying user, and completed transaction amount information may refer to the total amount information paid by all paying users. For example: a payment requires three users (user 1, user 2, and user 3) to pay 1 yuan each. If user 1 and user 2 complete the payment, and user 3 does not complete the payment, then the first transaction amount executed by user 1 using the terminal is 1 yuan, the second transaction amount executed by user 2 using the terminal is 1 yuan, and the completed transaction amount is 2 yuan.

[0083] In actual applications, after the first terminal obtains the payment result information fed back by the server, it can generate a payment result page locally based on the payment result information, or the server can generate the payment result page and then send it to the first terminal, which is not specifically limited. The payment result page can display at least part of the payment result information.

[0084] Figure 4 This is a schematic diagram of a payment result page provided in an embodiment of this specification. Figure 4 As shown in the figure, user 1 is the initiator of the transaction. When user 1 initiates the payment, the total amount set is 0.75 yuan, and user 2, user 3, and user 4 are required to pay 0.25 yuan each. User 2 has completed the payment, and the payment result page shows "1 person has paid", and the avatar and nickname of user 2 can be displayed, and it also shows that user 2 has "paid 0.25 yuan". User 3 and user 4 have not completed the payment yet, and the payment result page shows "2 people have not paid", and the avatars and nicknames of user 3 and user 4 can be displayed, and it also shows that user 3 and user 4 both "pend to pay 0.25 yuan". The payment result page also shows the total amount of money received: "0.25 yuan has been received".

[0085] Optionally, the payment page may include a first control for triggering payment using a short-distance communication method; correspondingly, obtaining the payment information submitted by the first user based on the payment page may specifically include: obtaining a first operation of the first user on the first control; and obtaining the payment information based on the first operation.

[0086] In the embodiments of this specification, the first control for triggering payment by short-distance communication may be an "NFC payment collection" control, a "Bluetooth payment collection" control, etc. After the first user triggers the "NFC payment collection" control, the NFC mode may be activated to prepare for data transmission based on NFC; after the first user triggers the "Bluetooth payment collection" control, Bluetooth may be activated to prepare for data transmission based on Bluetooth.

[0087] In actual applications, the first operation of the first user on the first control may include but is not limited to: clicking, sliding, selecting, long pressing, etc. The payment page may include multiple types of first controls for users to choose from. Figure 3 Take this as an example to illustrate: Figure 3 The payment page shown includes both the "NFC payment collection" control and the "Bluetooth payment collection" control. In actual applications, only one of the controls may be used, which is not limited here.

[0088] Optional, Figure 2In the method, step 202, before the first terminal establishes a short-distance communication connection with the second terminal, it may also include: displaying prompt information prompting payment by way of short-distance communication.

[0089] In the embodiments of this specification, the prompt information for payment through short-distance communication may be prompt information such as: "Please bring your phone closer", "NFC payment, please come and stick it", "Touch and pay", "Please turn on Bluetooth", etc. Displaying these prompt information can guide and instruct the payer to pay through short-distance communication, which is conducive to improving payment efficiency and user experience.

[0090] Optionally, the method may further include: displaying payment result information in a prompt page that displays the prompt information.

[0091] In actual applications, the payment result information can be displayed on the same page as the prompt information for prompting payment by means of short-distance communication. For example, after the first terminal initiates payment, a page is displayed, in which the prompt information can be displayed first. After the second terminal obtains the transaction identification information or completes the payment, the page can display the prompt information and the result information at the same time. Alternatively, the payment result information and the prompt information can also be displayed on different pages, for example, the payment result information can also be displayed in the form of a pop-up window or a floating layer, which is not specifically limited. For example, after the first terminal initiates payment, the first terminal can display a prompt page containing prompt information. After the second terminal completes payment, the first terminal can display a result page containing payment result information. If other terminal users are required to establish communication with the first terminal, after the result page in the first terminal is displayed for a preset period of time, for example, after 3 seconds, the first terminal can also automatically display a page containing prompt information.

[0092] For example, Figure 4 Take this as an example to illustrate: Figure 4 As shown, in Figure 4 The displayed page shows payment result information such as "1 person has paid", user 2 "has paid 0.25 yuan", user 3 and user 4 have not completed payment yet, user 3 and user 4 are both "pending payment of 0.25 yuan", and total amount received: "Received 0.25 yuan". It also displays a prompt message "Please ask the payer to bring the device closer".

[0093] Understandably, Figure 4 This is just an illustration. The actual application can be based on the specific display content of the actual setting page. Figure 4The displayed content may not be displayed in full, or may not be displayed in full at the same time, or may only display part of the content. For example, after the user of the first terminal initiates a multi-person payment, the first terminal may display a prompt message indicating that other devices are approaching. If the user clicks, swipes, or performs other operations in the area where the prompt message is displayed, the area may display the completed transaction information, such as the amount of money received mentioned above.

[0094] Optionally, the method may further include: displaying a second control for sending the transaction to other users in a non-short-distance communication manner; if the user's operation on the second control is obtained, sending a message for other users to pay for the transaction to the other users in a non-short-distance communication manner.

[0095] In the embodiments of this specification, the non-short-distance communication method may be scanning a QR code, sending a link, etc. If the first terminal does not have the conditions to send data by short-distance communication, it may also use a non-short-distance communication method to send transactions to other users so that other users can make payments, thereby making the solution more perfect, avoiding the situation where communication cannot be achieved under special circumstances due to a single communication method, and is conducive to improving the flexibility and success rate of communication.

[0096] In actual applications, the user's operations on the second control may include but are not limited to: clicking, sliding, selecting, long pressing, etc. After the user triggers the second control, a payment QR code or payment link may be generated, and other users may pay by scanning the QR code or clicking the payment link.

[0097] In actual applications, the message for other users to pay for the transaction is sent to the other users by means of non-short-distance communication, which can be sent by SMS, instant messaging, APP application messages, etc., to prompt other users to pay. Optionally, if the operation of the first user on the second control is obtained, the message for other users to pay for the transaction is sent to the other users by means of non-short-distance communication, which can specifically include: If the user's operation on the second control is obtained, the payment sharing information corresponding to the transaction identification information is determined; the payment sharing information includes at least one of the code image or link information corresponding to the transaction identification information; According to the information of the third user determined by the first user, the payment sharing information is sent to the user terminal of the third user in a non-short-range communication manner.

[0098] In the embodiments of this specification, the payment sharing information may be code image information, such as a QR code, or link information, or other information that can carry transaction identification information and can be transmitted based on a non-short-distance communication method, and there is no specific limitation on this. The payment sharing information may carry transaction identification information, so that after the user terminal of the third user receives the payment sharing information, it can complete the payment at the server based on the transaction identification information carried in the payment sharing information.

[0099] In actual applications, the payment sharing information is sent to the user terminal of the third user. The first terminal may send a payment sharing information generation request to the server, wherein the payment sharing information generation request may include transaction identification information and the terminal address information of the third user or the account information of the third user. After receiving the payment sharing information generation request, the server may generate the payment sharing information. After the server generates the payment sharing information, it may directly send the payment sharing information to the third user based on the terminal address information of the third user or the account information of the third user. Alternatively, the server may feed back the payment sharing information to the first terminal user, and then the first terminal user may send the payment sharing information to the user terminal of the third user. Alternatively, the payment sharing information may also be generated locally in the first terminal, and after generation, the first terminal user may send the payment sharing information to the user terminal of the third user.

[0100] Optionally, the second control may be located in a page for displaying the payment result information; or, the second control may be located in a page for displaying prompt information for payment via short-distance communication.

[0101] In the embodiment of this specification, the second control is a control that can send transactions to other users based on a non-short-distance communication method. Therefore, the second control can be located in a page for displaying the payment result information; or, the second control can be located in a page for displaying prompt information for prompting payment via short-distance communication. In this way, the user can switch the short-distance communication method to the non-short-distance communication method at any time by triggering the second control, which is conducive to improving the convenience of switching the communication method and meeting the different needs of users.

[0102] In the embodiment of this specification, the first terminal user can also specify the second terminal user who participates in the transaction. Optionally, the payment page can also include an area for filling in or selecting the user information of the second terminal; the payment information also includes the user information of the second terminal.

[0103] In the embodiment of the present specification, the user information of the second terminal may include, but is not limited to: a user account ID of the second terminal, a user account nickname of the second terminal, a user account avatar of the second terminal, and the like.

[0104] In actual applications, the payment page may also include an area for filling in or selecting the user information of the second terminal. The user of the first terminal initiating the payment can specify the transaction executor by filling in the user information of the second terminal on the payment page; or, if there is a friend relationship or a historical payment relationship between the user of the first terminal and the user of the second terminal, the user of the first terminal can also specify the transaction executor by selecting the user information of the second terminal on the payment page. Figure 3 For example, Figure 3 The payment page shown in also includes a "Select Payer" control. After the first user triggers the "Select Payer" control, a drop-down menu can be generated. The drop-down menu can display at least one second user who has a friend relationship or a historical payment relationship with the first user, so that the first user can choose from it, which is more convenient.

[0105] In actual applications, if the user of the first terminal specifies the user of the second terminal, the transaction identification information determined based on the payment information can also correspond to the user information of the designated second terminal. Therefore, when the server performs payment processing based on the transaction identification information, it can refuse other users other than the designated user of the second terminal to perform payment processing.

[0106] Optionally, the number represented by the information on the number of people participating in the transaction is a number including users of the first terminal or a number excluding users of the first terminal.

[0107] In actual applications, when the user of the first terminal enters the number of people participating in the transaction on the payment page, he or she may or may not be included. For example, user A, user B, and user C spend a total of 300 yuan, and the three agree to pay AA, and user A pays the merchant in full first. After user A pays 300 yuan to the merchant, when user A initiates payment, he or she may fill in the total amount: 300 yuan, total number of people: 3 people (including user A) on the payment page. In this case, the per capita payment is 100 yuan; or, when user A initiates payment, he or she may also fill in the total amount: 200 yuan, total number of people: 2 people (excluding user A) on the payment page. In this case, the per capita payment is also 100 yuan.

[0108] In actual applications, the user of the first terminal can be a merchant or one of the payees. When the user of the first terminal is a merchant, the merchant usually does not need to include itself when determining the number of people participating in the transaction. For example: User A and User B spend a total of 100 yuan, and the two agree to pay AA. Merchant C uses an NFC payment device to collect payment. When collecting payment, the total amount is set to 100 yuan and the total number of people is 2. After the setting is completed, User A and User B each put their mobile phones close to the NFC payment device to complete the payment, and each pays 50 yuan.

[0109] In actual applications, optionally, the payment page may further include a selection control for selecting whether to use the user of the first terminal as the payer, so that the user can more conveniently set the number of people participating in the transaction.

[0110] As an implementation method, the transaction initiator may not be the payee, and the initiator may specify the payee. Optionally, the payment page may also include an area for selecting or filling in the payee; the transaction identification information is identification information of at least one user including the user of the first terminal making a payment to the payee.

[0111] In actual applications, the user of the first terminal can also be the payee. In this case, the user of the first terminal can select or fill in the relevant information of the payee on the payment page. Correspondingly, based on the payment information, the transaction identification information determined is the identification information of the payment made to the payee by at least one user including the user of the first terminal. Subsequently, the user of the first terminal can complete the payment at the server based on the transaction identification information. For example: User A, User B, and User C need to pay User D, User A is the transaction initiator, and User D is designated as the payee. User A's terminal can send the transaction identification information to User B's terminal and User C's terminal through short-range communication. User A's terminal, User B's terminal, and User C's terminal can subsequently complete the payment to User D at the server based on the transaction identification information.

[0112] In actual applications, when the first terminal user is the initiator of the transaction, the payee can be specified, and the second terminal user can be the payee or the payer. When the second terminal user is the payee specified by the first terminal user, a short-distance communication connection may not be established between the first terminal and the second terminal, and the first terminal can directly complete the payment at the server based on the transaction identification information. Alternatively, a short-distance communication connection may be established between the first terminal and the second terminal, and after the connection is established, the second terminal may display prompt information such as: "No payment required" or "Waiting for the other party to pay". When the second terminal user is not the payee specified by the first terminal user, but one of the payers, the first terminal may send the transaction identification information to the second terminal through short-distance communication, so that the second terminal user can complete the payment at the server based on the transaction identification information.

[0113] The multi-party payment provided in the embodiments of this specification may be a payment from multiple parties to one party, or a payment from one party to multiple parties. Optionally, the user of the first terminal is the payee, and the transaction identification information is identification information used by multiple other users to pay the user of the first terminal; or, the user of the first terminal is the payee, and the transaction identification information is identification information used by the user of the first terminal to pay multiple other users.

[0114] In actual applications, the user of the first terminal can be a payer or a payee. When the user of the first terminal is a payer, a payment to a single payee or a payment to multiple payees can be created. When a payment to a single payee is created, the transaction identification information is the identification information used by the user of the first terminal to make a payment to the single payee; when a payment to multiple payees is created, the transaction identification information is the identification information used by the user of the first terminal to make a payment to multiple other users.

[0115] Figure 5 This is a flow chart of the second multi-person payment method provided in the embodiment of this specification. From the hardware perspective, the execution subject of the process can be a terminal device, specifically a second terminal. From the program perspective, the execution subject of the process can be an application installed on the terminal device. Figure 5 As shown, the process may include the following steps: Step 502: The second terminal establishes a short-range communication connection with the first terminal.

[0116] Step 504: Acquire transaction identification information of transactions that need to be paid by multiple users in the first terminal through the short-range communication connection.

[0117] Step 506: Based on the transaction identification information, a payment processing request is sent to a server; the server executes a payment process for the second terminal based on the payment processing request.

[0118] Step 508: Obtain payment result information for the second terminal generated by the server based on the payment processing request.

[0119] In the embodiment of the present specification, the first terminal, the second terminal, the short-range communication connection, the transaction to be paid by multiple users, the transaction identification information, and the payment processing request can be Figure 2 The meanings of the terms mentioned in the embodiments of the method are consistent. Since the process of establishing a short-distance communication connection between the second terminal and the first terminal and the process of transmitting the transaction identification information have been described in detail above, they will not be repeated here.

[0120] In the embodiment of this specification, the second terminal can obtain the transaction identification information of the transaction that needs to be paid by multiple users from the first terminal through short-distance communication, and then send a payment processing request to the server. The payment processing request can carry the transaction identification information. After the server receives the payment processing request sent by the second terminal, it can determine the corresponding target transaction that needs to be paid by multiple users based on the transaction identification information in the payment processing request, and perform the deduction work corresponding to the target transaction. After the server executes the payment process for the second terminal based on the payment processing request, it can generate payment result information for the second terminal, and feed back the payment result information for the second terminal to the second terminal.

[0121] In actual applications, the second terminal can realize payment by sticking it close to or approaching the first terminal, which is very convenient and efficient. After receiving the payment result information fed back by the server, the second terminal can display the payment result display page containing the payment result information; or, it can also broadcast the payment result by voice; or, it can also use other methods to display the payment result to the user, which is not specifically limited.

[0122] In actual applications, the user of the second terminal can make payments by "sticking" the second terminal to the first terminal. After the second terminal is "sticked" to the first terminal, the second terminal displays a payment page, which can display the required payment amount and the "Confirm Payment" control. The user can make payments after triggering the "Confirm Payment" control. Alternatively, after the second terminal is "sticked" to the first terminal, payment can be made directly without the user's confirmation or input of the required payment amount, which is conducive to improving payment efficiency and convenience.

[0123] Figure 5 In the method, after the second terminal establishes a short-distance communication connection with the first terminal, the second terminal can obtain the transaction identification information of the transaction that needs to be paid by multiple users from the first terminal through the short-distance communication connection; after the second terminal receives the transaction identification information, it can send a payment processing request to the server based on the transaction identification information; after the server receives the payment processing request, it can execute the payment process based on the payment processing request, generate payment result information, and feed back the payment result information to the first terminal. Therefore, when the first terminal needs to send the transaction order to the second terminal, it is no longer necessary to send it in the form of a QR code or a link, but to establish a short-distance communication connection with the second terminal, and transmit the transaction identification information to the second terminal based on the short-distance communication connection, so that the second terminal can complete the payment at the server based on the transaction identification information. Since the short-distance communication connection is convenient to establish, the user terminals can complete the connection by being close to each other, which can effectively improve the payment convenience in multi-person payment scenarios and improve the user experience.

[0124] On the other hand, the second terminal does not need to open the payment application, nor does it need to click on the link or identify the QR code. After unlocking, you can pay by just tapping it, which makes payment more convenient.

[0125] based on Figure 5 The method in this specification also provides some specific implementation plans of the method, which are described below.

[0126] As an implementation manner, the above step 502, in which the second terminal establishes a short-range communication connection with the first terminal, may specifically include: the second terminal sends an electromagnetic signal for triggering near field communication; and establishes an NFC near field communication connection with the first terminal in response to the electromagnetic signal.

[0127] Among them, the second terminal, as the initiator of near-field communication, sends out an electromagnetic signal to detect whether there is a first near-field communication device nearby. Once detected, it sends instruction information to the first device, and the first device sends transaction identification information to the second device based on the instruction information.

[0128] Optionally, before the second terminal sends the electromagnetic signal for triggering near field communication, the method may further include: starting a card reader mode for near field communication of the second terminal.

[0129] In an embodiment of the present specification, if the short-distance communication connection between the first terminal and the second terminal is an NFC near-field communication connection, the second terminal as a device in reader mode can send an electromagnetic signal for triggering near-field communication, and the first terminal can establish an NFC near-field communication connection with the second terminal based on the electromagnetic signal for triggering near-field communication sent by the second terminal.

[0130] In actual application, after the second terminal user unlocks the second terminal, the second terminal can start the card reader mode. Specifically, the terminal system can set the mobile terminal to the card reader mode after determining that the terminal is in the unlocked state.

[0131] In actual applications, the first terminal and the second terminal can perform near field communication through point-to-point mode, or through card reader mode and card emulation mode. The first terminal can be turned on in card emulation mode for near field communication, and the second terminal can be turned on in card reader mode for near field communication. After each is turned on, the first terminal and the second terminal can establish an NFC connection when they are close to each other, and after the connection is connected, the second terminal can read the data in the first terminal.

[0132] As another implementation, the above step 502, in which the second terminal establishes a short-range communication connection with the first terminal, may specifically include: the second terminal performs Bluetooth pairing with the first terminal; and establishes a Bluetooth connection with the first terminal.

[0133] In practical applications, the short-range communication connection between the first terminal and the second terminal may also be a Bluetooth connection. The first terminal may be paired with the second terminal via Bluetooth, and after the pairing is successful, a Bluetooth connection is established between the first terminal and the second terminal. After the second terminal establishes a Bluetooth connection with the first terminal, the transaction identification information may be obtained through the Bluetooth connection established with the first terminal.

[0134] Optional, Figure 5 In the method, step 504, obtaining transaction identification information of a transaction that needs to be paid by multiple users in the first terminal through the short-distance communication connection can specifically include: obtaining tag information of short-distance communication in the first terminal through the short-distance communication connection; the tag information includes the transaction identification information.

[0135] In the embodiments of this specification, tag information may represent information sent from a first terminal to a second terminal via short-distance communication, which may include transaction identification information, device information of the first terminal, validity period of the tag, etc. The tag information may carry various information, and the specific tag information may be in the form of a link, a data packet, or other forms, which are not specifically limited.

[0136] In order to facilitate the second terminal to participate in payment. Optionally, the tag information may also include application identification information of the payment application. Correspondingly, the method may also include: starting the payment application based on the application identification information.

[0137] Correspondingly, sending the payment processing request to the server based on the transaction identification information may specifically include: sending the payment processing request to the server by using the started payment application.

[0138] In the embodiments of this specification, the application identification information of the payment application may include, but is not limited to: the application name of the payment application, the application abbreviation of the payment application, the abbreviation of the payment application, the package name of the payment application, the package signature of the payment application, etc. There is a corresponding relationship between the application identification information of the payment application and the payment application, so that different systems can start the same payment application according to the application identification information of the payment application.

[0139] In actual applications, after the second terminal obtains the tag information sent by the first terminal, the terminal system program can parse the tag information, determine the application identification information of the payment application in the tag information, and start the corresponding payment application based on the application identification information. The terminal system program can also send the transaction identification information parsed from the tag information to the started payment application, and the payment application generates a payment processing request based on the transaction identification information and sends the payment processing request to the server. The server can be a server corresponding to the payment application, or the server can be a server that can process business requests initiated by the payment application. The payment application can be started at the front end or in the background, and there is no specific limitation on this.

[0140] Optional, Figure 5 The method may also include: displaying a transaction page based on the transaction identification information; the transaction page includes information on the amount to be paid by the second terminal or the transaction page includes an area for filling in the transaction amount; obtaining a confirmation operation performed by the second user based on the transaction page.

[0141] Correspondingly, the sending of the payment processing request to the server may specifically include: based on the confirmation operation, sending the payment processing request to the server.

[0142] In the embodiment of the present specification, after the second terminal obtains the transaction identification information, it can send a second payment trigger request to the server based on the transaction identification information. After the server obtains the second payment trigger request, it can generate and feedback a transaction page to the second terminal. The transaction page may include the amount information that the second terminal needs to pay. After the second terminal user sees the displayed amount information to be paid, if it is confirmed that it is correct, it can perform a confirmation operation based on the transaction page, for example, by clicking the "Confirm Payment" control in the transaction page to confirm. After the second terminal user confirms, the second terminal can send a payment processing request containing the transaction identification information to the server. Among them, the payment processing request can also include the amount information that the second terminal needs to pay. In actual applications, if the second user does not perform any operation within a preset time period after the transaction page is displayed, it can also be considered that the second user confirms by default. For example: after the transaction page is displayed, if the second user does not perform any operation within a 30-second countdown, it can indicate user confirmation.

[0143] In actual applications, the transaction page may also include an area for filling in the transaction amount. When the transaction page does not display the amount information that the second terminal needs to pay, or the second terminal user does not recognize the amount information that the second terminal needs to pay displayed on the transaction page, the second terminal user may also fill in the transaction amount on the transaction page. After the second terminal user completes the filling, he can confirm. After confirmation, the second terminal can send a payment processing request containing transaction identification information to the server. Among them, the payment processing request may also include the amount information filled in by the second terminal user himself.

[0144] In actual applications, the transaction page may not be displayed in the second terminal, and the second terminal user does not need to confirm, so as to reduce the disturbance to the second terminal user. In this way, it will not affect the second terminal user's use of other applications in the second terminal. For example: when the user is playing games, reading e-books, watching videos, etc. on the mobile phone, there is no need to exit. After sticking the mobile phone, payment can be directly realized. After the second terminal makes a payment, the payment result information executed by the second terminal can also be obtained, wherein the payment result executed by the second terminal is used to prompt whether the second terminal has completed the payment. Specifically, the payment result information executed by the second terminal can be prompted by SMS, application message, prompt tone, etc., or it can be displayed on a page.

[0145] Figure 6 This is a flow chart of the third multi-person payment method provided in the embodiment of this specification. From the hardware perspective, the execution subject of this process can be a server. From the program perspective, the execution subject of this process can be an application installed on the server. Figure 6 As shown, the process may include the following steps: Step 602: Obtain a payment processing request sent by a second terminal; the payment processing request is generated by the second terminal based on transaction identification information obtained from the first terminal through short-range communication; the transaction identification information corresponds to a transaction that needs to be paid by multiple users; each of the multiple users needs to pay part of the amount in the transaction.

[0146] Step 604: Execute the payment process corresponding to the transaction identification information for the second terminal based on the payment processing request.

[0147] Step 606: Send payment result information for the second terminal to the second terminal.

[0148] In the embodiment of the present specification, the first terminal, the second terminal, the short-range communication connection, the transaction to be paid by multiple users, the transaction identification information, the payment result information, and the payment processing request can be Figure 2The meanings of the terms mentioned in the embodiments of the method are consistent. Since the process of establishing a short-distance communication connection between the second terminal and the first terminal and the process of transmitting the transaction identification information have been described in detail above, they will not be repeated here.

[0149] In actual applications, the server may pre-store an association between transaction identification information and target transactions that need to be paid by multiple users. Thus, after receiving the payment processing request sent by the second terminal, the server may determine the corresponding target transaction that needs to be paid by multiple users based on the transaction identification information in the payment processing request, and perform the deduction work corresponding to the target transaction. After the server executes the payment process for the second terminal based on the payment processing request, it may generate payment result information for the second terminal, and feed back the payment result information for the second terminal to the second terminal.

[0150] Figure 6 In the method, after the first terminal establishes a short-distance communication connection with the second terminal, the first terminal can send the transaction identification information of the transaction that needs to be paid by multiple users to the second terminal through the short-distance communication connection; after the second terminal receives the transaction identification information, it can send a payment processing request to the server based on the transaction identification information; after the server receives the payment processing request, it can execute the payment process based on the payment processing request, generate payment result information, and feed back the payment result information to the first terminal. Therefore, when the first terminal needs to send the transaction order to the second terminal, it is no longer necessary to send it in the form of a QR code or a link, but to establish a short-distance communication connection with the second terminal, and transmit the transaction identification information to the second terminal based on the short-distance communication connection, so that the second terminal completes the payment at the server based on the transaction identification information. Since the short-distance communication connection is convenient to establish, the user terminals can complete the connection by being close to each other, which can effectively improve the payment convenience in multi-person payment scenarios and enhance the user experience.

[0151] based on Figure 6 The method in this specification also provides some specific implementation plans of the method, which are described below.

[0152] Optional, Figure 6 The method may further include: sending payment result information indicating the transaction result of the second terminal to the first terminal.

[0153] In actual applications, after the server generates payment result information representing the transaction result of the second terminal, the payment result information can be fed back to the second terminal, and the payment result information can also be sent to the first terminal so that the user of the first terminal can also understand the transaction result of the second terminal, which is conducive to improving the user experience.

[0154] Optionally, if the second terminal has completed the payment, the method may further include: determining the completed transaction amount information for the transaction based on the transaction amount information completed by the second terminal; and sending the completed transaction amount information to the first terminal.

[0155] In the embodiment of this specification, if there are multiple second terminals, after the server completes the payment execution work for at least some of the second terminals, the transaction amount information of the completed transaction can be calculated based on the transaction amount information of each second terminal, wherein the completed transaction amount information can be the total completed amount information after the transaction amounts completed for each second terminal are summarized. For example: for transaction A, user 1 needs to pay 1 yuan, user 2 needs to pay 1 yuan, and user 3 needs to pay 1 yuan. If user 1 and user 2 have completed the payment, and user 3 has not completed the payment yet, then the transaction amount completed by user 1 is 1 yuan, the transaction amount completed by user 2 is 1 yuan, and the transaction amount completed for transaction A is 2 yuan.

[0156] In actual applications, after the server calculates the transaction amount information of the completed transaction, the server can send the transaction amount information of the completed transaction to the first terminal so that the user of the first terminal can understand the current payment situation. Alternatively, the server can send the transaction amount information of each second terminal to the first terminal, and the first terminal will locally calculate the transaction amount information of the completed transaction. There is no specific limitation on this.

[0157] Optionally, the method in this specification may also include: obtaining a first payment trigger request sent by the first terminal; the first payment trigger request is generated by the first terminal based on the payment information submitted by the first user; the payment information includes amount information and information on the number of people involved in the transaction; based on the first payment trigger request, generating the transaction identification information; and sending the transaction identification information to the first terminal.

[0158] In the embodiment of this specification, after the first user enters payment information such as amount information and number of persons participating in the transaction in the payment page and submits it, the first terminal may send a first payment trigger request carrying the payment information to the server. After receiving the first payment trigger request sent by the first terminal, the server may generate transaction identification information based on the payment information carried in the first payment trigger request.

[0159] In actual applications, after the server generates corresponding transaction identification information based on a payment information, the server can associate and store the payment information with the corresponding transaction identification information, so that the corresponding transactions and payment information that need to be paid by multiple users can be determined based on the transaction identification information later. After the server generates the transaction identification information, the generated transaction identification information can be fed back to the first terminal.

[0160] Optionally, the above step 602, before obtaining the payment processing request sent by the second terminal, may also include: obtaining a second payment trigger request sent by the second terminal based on the transaction identification information; feeding back a transaction page to the second terminal based on the second payment trigger request; the transaction page includes information on the amount to be paid by the second terminal or the transaction page includes an area for filling in the transaction amount.

[0161] In an embodiment of the present specification, after the second terminal obtains the transaction identification information, it can send a second payment trigger request to the server based on the transaction identification information, and the second payment trigger request can carry the transaction identification information. After the server obtains the second payment trigger request, it can determine the corresponding target payment order based on the transaction identification information in the second payment trigger request, so that it can determine the amount information to be paid by the second terminal based on the amount information in the target payment order and the number of people information or the payment information required by the payee user specified by the user, and generate a transaction page. After the server generates the transaction page, it can feed the transaction page back to the second terminal. The transaction page may include the amount information to be paid by the second terminal. After the second terminal user sees the displayed amount information to be paid, if it is confirmed that it is correct, the confirmation operation can be performed based on the transaction page.

[0162] In actual applications, the transaction page may also include an area for filling in the transaction amount. When the transaction page does not display the amount information that the second terminal needs to pay, or the second terminal user does not recognize the amount information that the second terminal needs to pay displayed on the transaction page, the second terminal user may also fill in the transaction amount on the transaction page. After the second terminal user completes the filling, he can confirm. After confirmation, the second terminal can send a payment processing request containing transaction identification information to the server. Among them, the payment processing request may also include the amount information filled in by the second terminal user himself.

[0163] Optionally, the above step 604: executing the payment process for the second terminal corresponding to the transaction identification information based on the payment processing request, may specifically include: determining the amount information that the second terminal needs to pay in the transaction; the amount indicated by the amount information that the second terminal needs to pay is a partial amount of the total amount corresponding to the transaction; deducting the amount that the second terminal needs to pay from the user account of the second terminal.

[0164] In the embodiments of this specification, after the server determines the amount information that the second terminal needs to pay in the transaction, it can perform the corresponding deduction work and deduct the amount that the second terminal needs to pay from the user account of the second terminal. Specifically, the corresponding amount can be deducted from the account that the user of the second terminal has logged in through the payment application, or the user of the second terminal can pay by scanning a code, etc., without specific limitation.

[0165] Optionally, after obtaining the payment processing request sent by the second terminal, the above-mentioned process may also include: determining whether the payment processing request meets the transaction processing conditions; the transaction processing conditions include at least one of the following: the transaction amount completed for the transaction is less than the total amount required for the transaction; the number of transactions completed for the transaction is less than the total number of transactions required for the transaction; the transaction identification information is in a valid state; the second terminal has not completed payment for the transaction.

[0166] In the embodiment of the present specification, after receiving the payment processing request sent by the second terminal, the server can determine whether the payment processing request meets the transaction processing conditions, and for payment processing requests that do not meet the transaction processing conditions, processing can be prohibited. This can avoid the waste of processing resources, help save processing resources, and improve processing efficiency.

[0167] In actual applications, if the transaction amount for the completed transaction is no less than the total amount required for the transaction, there is no need to process the payment processing request; if the number of people for the completed transaction is no less than the total number of people required for the transaction, there is no need to process the payment processing request; if the transaction identification information has expired and is invalid, there is no need to process the payment processing request; if the second terminal has already executed payment for the transaction, there is no need to process the payment processing request sent by the second terminal.

[0168] Optionally, the method in the embodiment of this specification may further include: if the payment processing request does not meet the transaction conditions, then feeding back transaction prompt information to the second terminal; the transaction prompt information includes at least one of prompt information indicating that the transaction has ended and prompt information indicating that no payment is required.

[0169] In the embodiment of the present specification, if the payment processing request does not meet the transaction conditions, the server may feedback transaction prompt information to the second terminal, wherein the transaction prompt information may include at least one of prompt information indicating that the transaction has ended and prompt information indicating that no payment is required. After receiving the transaction prompt information fed back by the server, the second terminal may display the transaction prompt information so that the user can know the reason for the payment failure.

[0170] Figure 7A swim lane diagram of a multi-person payment method provided in an embodiment of this specification. Figure 7 As shown, the execution entities involved in the process of the multi-person payment method may include a first terminal, a second terminal, and a server. Here, near field communication is used as an example for explanation. Figure 7 The method flow may include a transaction identification information generation and storage stage, a near field communication stage, and a payment stage, and may specifically include the following steps: In the transaction identification information generation and storage stage, an optional implementation method may be as follows Figure 7 As shown in steps 702 to 718 in .

[0171] Step 702: The first terminal displays a payment page for multiple users to pay.

[0172] Step 704: The first terminal obtains payment information submitted by the first user based on the payment page.

[0173] Step 706: The first terminal sends a first payment trigger request including payment information to the server.

[0174] Step 708: The server obtains the first payment triggering request sent by the first terminal.

[0175] Step 710: The server generates transaction identification information based on the first payment trigger request.

[0176] Step 712: The server feeds back the transaction identification information to the first terminal.

[0177] Step 714: The first terminal obtains transaction identification information.

[0178] Step 716: The first terminal processes the transaction identification information according to the preset protocol rules to obtain processed transaction identification information.

[0179] Step 718: The first terminal starts the card simulation mode of the near field communication and saves the processed transaction identification information to the simulated card.

[0180] In actual applications, the step of the first terminal starting the card simulation mode of near field communication in step 718 can also be before, after or during any step in the above steps 702 to 718, as long as the transaction identification information can be saved in the simulated card before the second terminal approaches the first terminal.

[0181] In the near field communication stage, an optional implementation method may be as follows Figure 7 As shown in steps 720 to 730 in .

[0182] Step 720: The first terminal displays a prompt message prompting payment via short-distance communication.

[0183] Step 722: The second terminal starts the card reader mode of near field communication.

[0184] Step 724: The second terminal sends an electromagnetic signal for triggering near field communication.

[0185] Step 726: The first terminal obtains the electromagnetic signal sent by the second terminal for triggering near field communication.

[0186] Step 728: The first terminal sends the transaction identification information to the second terminal via near field communication based on the electromagnetic signal.

[0187] Step 730: The second terminal obtains transaction identification information.

[0188] In the payment phase, an optional implementation may be as follows Figure 7 As shown in steps 732 to 752 in .

[0189] Step 732: The second terminal generates a second payment triggering request based on the transaction identification information, and the second payment triggering request carries the transaction identification information.

[0190] Step 734: The second terminal sends a second payment trigger request to the server.

[0191] Step 736: The server receives the second payment trigger request and processes the transaction for the second terminal.

[0192] Step 738: The server generates payment result information for the second terminal.

[0193] Step 740: The server sends payment result information for the second terminal to the second terminal.

[0194] Step 742: The second terminal obtains payment result information for the second terminal sent by the server.

[0195] Step 744: The server sends payment result information indicating the transaction result of the second terminal to the first terminal.

[0196] Step 746: The first terminal obtains payment result information sent by the server, indicating the transaction result of the second terminal.

[0197] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0198] Figure 8 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of a multi-person payment device. Figure 8 As shown, the device may include: The connection module 802 is used to establish a short-distance communication connection with the second terminal.

[0199] The sending module 804 is used to send the transaction identification information of the transaction that needs to be paid by multiple users to the second terminal through the short-distance communication connection; each of the multiple users needs to pay part of the amount in the transaction.

[0200] The acquisition module 806 is used to obtain the payment result information fed back by the server; the server is the target server to which the second terminal sends the payment processing request based on the transaction identification information; the server executes the payment process based on the payment processing request to generate the payment result information.

[0201] based on Figure 8 The present specification also provides some specific implementation schemes of the device, which are described below.

[0202] Optionally, the device may further include: a payment page display module, used to display a payment page for multiple users to pay; a payment information acquisition module, used to acquire payment information submitted by the first user based on the payment page; the payment information includes amount information and information about the number of people involved in the transaction; an identification information determination module, used to determine the transaction identification information based on the payment information.

[0203] Optionally, the identification information determination module may specifically include: a request sending submodule, configured to send a first payment trigger request including the payment information to the server; the server generates the transaction identification information based on the payment information; and an identification information acquisition submodule, configured to acquire the transaction identification information sent by the server.

[0204] Optionally, the short-distance communication connection may include an NFC near-field communication connection; the connection module 802 may specifically include: an electromagnetic signal acquisition submodule, used to acquire an electromagnetic signal sent by the second terminal for triggering near-field communication.

[0205] Correspondingly, the sending module 804 may specifically include: a sending submodule, configured to send the transaction identification information to the second terminal through near field communication based on the electromagnetic signal.

[0206] Optionally, the short-range communication connection may include a Bluetooth connection; the connection module 802 may specifically include: a Bluetooth pairing submodule, used for performing Bluetooth pairing with the second terminal; and a Bluetooth connection submodule, used for establishing a Bluetooth connection with the second terminal.

[0207] Correspondingly, the sending module 804 may specifically include: a sending submodule, configured to send the transaction identification information to the second terminal via a Bluetooth connection established with the first terminal.

[0208] Optionally, the device may further include: a protocol rule processing module, configured to process the transaction identification information according to a preset protocol rule to obtain processed transaction identification information; the preset protocol rule is a protocol rule that complies with the short-distance communication. An identification information storage module, configured to store the processed transaction identification information in the short-distance communication module of the first terminal.

[0209] Optionally, the short-range communication module may include at least one of a Bluetooth module and an NFC near-field communication module.

[0210] Optionally, if the short-distance communication is NFC near field communication, the device may further include: a card simulation mode activation module, configured to activate the card simulation mode of near field communication for the first terminal.

[0211] Correspondingly, the identification information storage module may specifically include: an identification information storage submodule, which is used to save the processed transaction identification information into a simulated card obtained in the first terminal based on the card simulation mode.

[0212] Optionally, the payment result information may include at least one of information of paid users, information of non-paid users, information of the number of people who have paid, information of paid amounts, information of the number of non-paid people, and information of unpaid amounts.

[0213] Optionally, the payment result information may include the first transaction amount information executed by the second terminal; the device may also include: a payment result page display module, used to display a payment result page; the payment result page includes the first transaction amount information or the first completed transaction amount information obtained based on the first transaction amount information.

[0214] Optionally, the device may further include: a second transaction amount information acquisition module, configured to acquire second transaction amount information executed by a third terminal; the third terminal is a terminal of a user who needs to pay for the transaction.

[0215] A transaction amount information display module is used to display the second transaction amount information or the second completed transaction amount information in the payment result page; the second completed transaction amount information is the information obtained by adding the transaction amount represented by the second transaction amount information to the completed transaction amount represented by the first completed transaction amount information.

[0216] Optionally, the payment page includes a first control for triggering payment using a short-distance communication method. Correspondingly, the payment information acquisition module may specifically include: a first acquisition submodule for acquiring a first operation of the first user on the first control. A second acquisition submodule for acquiring the payment information based on the first operation.

[0217] Optionally, the device may further include: a prompt information display module, used to display prompt information for prompting payment via short-distance communication.

[0218] Optionally, the device may further include: a payment result information display module, configured to display the payment result information in a prompt page that displays the prompt information.

[0219] Optionally, the device may further include: a second control display module, used to display a second control for sending the transaction to other users in a non-short-range communication manner.

[0220] The non-short-range communication sending module is used to send a message for other users to pay for the transaction to the other users by means of non-short-range communication if the user's operation on the second control is obtained.

[0221] Optionally, the non-short-distance communication sending module may specifically include: a payment sharing information determination submodule, which is used to determine the payment sharing information corresponding to the transaction identification information if the user's operation on the second control is obtained; the payment sharing information includes at least one of a code image or link information corresponding to the transaction identification information. A payment sharing information sending submodule is used to send the payment sharing information to the user terminal of the third user through a non-short-distance communication method based on the information of the third user determined by the first user.

[0222] Optionally, the second control is located in a page for displaying the payment result information; or, the second control is located in a page for displaying prompt information for payment via short-distance communication.

[0223] Optionally, the payment page may further include an area for filling in or selecting user information of the second terminal; the payment information may further include user information of the second terminal.

[0224] Optionally, the number represented by the information on the number of people participating in the transaction is a number including users of the first terminal or a number excluding users of the first terminal.

[0225] Optionally, the payment page may further include a selection control for selecting whether to use the user of the first terminal as the payer.

[0226] Optionally, the payment page may include an area for selecting or filling in a payee; the transaction identification information is identification information of a payment made to the payee by at least one user including a user of the first terminal.

[0227] Optionally, the user of the first terminal is the payee, and the transaction identification information is identification information used by multiple other users to pay the user of the first terminal; or, the user of the first terminal is the payee, and the transaction identification information is identification information used by the user of the first terminal to pay multiple other users.

[0228] Fig. 9 The embodiments of this specification provide corresponding to Figure 5 The second multi-person payment device is shown in FIG. Fig. 9 As shown, the device may include: The connection module 902 is used to establish a short-distance communication connection with the first terminal.

[0229] The first acquisition module 904 is configured to acquire, through the short-distance communication connection, transaction identification information of transactions in the first terminal that need to be paid by multiple users.

[0230] The sending module 906 is used to send a payment processing request to the server based on the transaction identification information; the server executes the payment process for the second terminal based on the payment processing request.

[0231] The second acquisition module 908 is used to acquire payment result information for the second terminal generated by the server based on the payment processing request.

[0232] based on Fig. 9 The present specification also provides some specific implementation schemes of the device, which are described below.

[0233] Optionally, the connection module 902 may specifically include: an electromagnetic signal sending submodule, configured to send an electromagnetic signal for triggering near field communication; and a near field communication connection establishing submodule, configured to establish an NFC near field communication connection with the first terminal that responds to the electromagnetic signal.

[0234] Optionally, the device may further include: a card reader mode activation module, configured to activate a card reader mode of near field communication of the second terminal.

[0235] Optionally, the connection module 902 may specifically include: a Bluetooth pairing submodule, configured to perform Bluetooth pairing with the first terminal; and a Bluetooth connection submodule, configured to establish a Bluetooth connection with the first terminal.

[0236] Optionally, the first acquisition module 904 may specifically include: an acquisition submodule, configured to acquire tag information of short-range communication in the first terminal through the short-range communication connection; the tag information includes the transaction identification information.

[0237] Optionally, the tag information may further include application identification information of the payment application; the device may further include: a payment application starting module, configured to start the payment application based on the application identification information.

[0238] Correspondingly, the sending module 906 may specifically include: a sending submodule, configured to send a payment processing request to a server using the started payment application.

[0239] Optionally, the device may further include: a transaction page display module, configured to display a transaction page based on the transaction identification information; the transaction page includes information on the amount to be paid by the second terminal or includes an area for filling in the transaction amount; and a confirmation operation acquisition module, configured to acquire a confirmation operation performed by the second user based on the transaction page.

[0240] Correspondingly, the sending module 906 may specifically include: a sending submodule, configured to send a payment processing request to a server based on the confirmation operation.

[0241] Fig.10 The embodiments of this specification provide corresponding to Figure 6 The schematic diagram of the structure of the third multi-person payment device. Fig.10 As shown, the device may include: The acquisition module 1002 is used to obtain a payment processing request sent by the second terminal; the payment processing request is generated by the second terminal based on the transaction identification information obtained from the first terminal through short-distance communication; the transaction identification information corresponds to a transaction that needs to be paid by multiple users; each of the multiple users needs to pay part of the amount in the transaction.

[0242] The execution module 1004 is used to execute the payment process corresponding to the transaction identification information for the second terminal based on the payment processing request.

[0243] The sending module 1006 is used to send the payment result information for the second terminal to the second terminal.

[0244] based on Fig.10 The present specification also provides some specific implementation schemes of the device, which are described below.

[0245] Optionally, the device may further include: a payment result information sending module, configured to send payment result information indicating a transaction result of the second terminal to the first terminal.

[0246] Optionally, if the second terminal has completed the payment, the device may further include: a transaction amount information determination module, configured to determine the completed transaction amount information for the transaction based on the transaction amount information completed by the second terminal; and a transaction amount information sending module, configured to send the completed transaction amount information to the first terminal.

[0247] Optionally, the device may further include: a payment trigger request acquisition module, used to acquire a first payment trigger request sent by the first terminal; the first payment trigger request is generated by the first terminal based on payment information submitted by the first user; the payment information includes amount information and number of people participating in the transaction. A transaction identification information generation module, used to generate the transaction identification information based on the first payment trigger request. A transaction identification information sending module, used to send the transaction identification information to the first terminal.

[0248] Optionally, the device may further include: a second payment trigger request acquisition module, configured to acquire a second payment trigger request sent by the second terminal based on the transaction identification information. A transaction page feedback module, configured to feedback a transaction page to the second terminal based on the second payment trigger request; the transaction page includes information on the amount to be paid by the second terminal or the transaction page includes an area for filling in the transaction amount.

[0249] Optionally, the execution module 1004 may specifically include: an amount information determination submodule, used to determine the amount information that the second terminal needs to pay in the transaction; the amount indicated by the amount information that the second terminal needs to pay is a partial amount of the total amount corresponding to the transaction. An amount deduction submodule, used to deduct the amount that the second terminal needs to pay from the user account of the second terminal.

[0250] Optionally, the device may further include: a judgment module, configured to judge whether the payment processing request meets a transaction processing condition. The transaction processing condition includes at least one of the following: the transaction amount completed for the transaction is less than the total amount required for the transaction; the number of transactions completed for the transaction is less than the total number of transactions required for the transaction; the transaction identification information is in a valid state; the second terminal has not completed payment for the transaction.

[0251] Optionally, the device may further include: a transaction prompt information feedback module, which is used to feedback transaction prompt information to the second terminal if the payment processing request does not meet the transaction conditions; the transaction prompt information includes at least one of prompt information indicating that the transaction has ended and prompt information indicating that no payment is required.

[0252] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0253] Fig.11 This is a schematic diagram of a computing device provided in an embodiment of this specification. Fig.11 As shown, the device 1100 may include: at least one processor 1110; and a memory 1130 communicatively connected to the at least one processor; Among them, corresponding to Figure 2 The multi-person payment method shown in the embodiment of the present invention, the memory 1130 stores instructions 1120 that can be executed by the at least one processor 1110, and the instructions are executed by the at least one processor 1110 to enable the at least one processor 1110 to: Establish a short-distance communication connection with a second terminal; send transaction identification information of a transaction that needs to be paid by multiple users to the second terminal through the short-distance communication connection; each of the multiple users needs to pay a part of the amount in the transaction; obtain payment result information fed back by a server; the server is the target server for the second terminal to send a payment processing request based on the transaction identification information; the server executes a payment process based on the payment processing request to generate the payment result information.

[0254] Among them, corresponding to Figure 5 In the multi-person payment method shown, the memory 1130 stores instructions 1120 that can be executed by the at least one processor 1110, and the instructions are executed by the at least one processor 1110 to enable the at least one processor 1110 to: establish a short-distance communication connection with a first terminal; obtain transaction identification information of a transaction that needs to be paid by multiple users in the first terminal through the short-distance communication connection; send a payment processing request to a server based on the transaction identification information; the server executes a payment process for the second terminal based on the payment processing request; Acquire payment result information for the second terminal generated by the server based on the payment processing request.

[0255] Among them, corresponding to Figure 6In the multi-person payment method shown, the memory 1130 stores instructions 1120 that can be executed by the at least one processor 1110, and the instructions are executed by the at least one processor 1110 so that the at least one processor 1110 can: obtain a payment processing request sent by the second terminal; the payment processing request is generated by the second terminal based on transaction identification information obtained from the first terminal through short-distance communication; the transaction identification information corresponds to a transaction that needs to be paid by multiple users; each of the multiple users needs to pay part of the amount in the transaction; based on the payment processing request, the payment process for the second terminal corresponding to the transaction identification information is executed; and the payment result information for the second terminal is sent to the second terminal.

[0256] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. Fig.11 As for the device shown, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0257] An embodiment of the present specification also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the above-mentioned multi-person payment method.

[0258] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the multi-person payment method mentioned above belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be found in the description of the technical scheme of the icon generation method or the training method of the icon generation model mentioned above.

[0259] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous. In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0260] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0261] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0262] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0263] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0264] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0265] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0266] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0267] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0268] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0269] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0270] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0271] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0272] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. A multi-person payment method, comprising: The first terminal establishes a short-range communication connection with the second terminal; Sending transaction identification information of a transaction that needs to be paid by multiple users to the second terminal via the short-range communication connection; each of the multiple users needs to pay part of the amount in the transaction; Acquire payment result information fed back by a server; the server is a target server to which the second terminal sends a payment processing request based on the transaction identification information; The server executes a payment process based on the payment processing request to generate the payment result information.

2. The method according to claim 1, before the first terminal establishes a short-range communication connection with the second terminal, further comprising: Displaying a payment page for multiple users to pay; Obtaining payment information submitted by the first user based on the payment page; The payment information includes the amount information and the number of persons involved in the transaction; Based on the payment information, the transaction identification information is determined.

3. The method according to claim 2, wherein determining the transaction identification information based on the payment information specifically comprises: Sending a first payment trigger request including the payment information to the server; The server generates the transaction identification information based on the payment information; Acquire the transaction identification information sent by the server.

4. The method according to claim 1, wherein the short-range communication connection comprises an NFC near-field communication connection; and the first terminal and the second terminal establish a short-range communication connection, specifically comprising: The first terminal obtains an electromagnetic signal sent by the second terminal for triggering near field communication; The sending the transaction identification information of the transaction to be paid by multiple users to the second terminal through the short-distance communication connection specifically includes: Based on the electromagnetic signal, the transaction identification information is sent to the second terminal via near field communication.

5. The method according to claim 1, wherein the short-range communication connection comprises a Bluetooth connection; and the first terminal establishing a short-range communication connection with the second terminal specifically comprises: The first terminal performs Bluetooth pairing with the second terminal; Establishing a Bluetooth connection with the second terminal; The sending the transaction identification information of the transaction to be paid by multiple users to the second terminal through the short-distance communication connection specifically includes: The first terminal sends the transaction identification information to the second terminal through a Bluetooth connection established with the first terminal.

6. The method according to claim 1, before the first terminal establishes a short-range communication connection with the second terminal, further comprising: Processing the transaction identification information according to a preset protocol rule to obtain processed transaction identification information; The preset protocol rule is a protocol rule that complies with the short-distance communication; The processed transaction identification information is stored in the short-range communication module of the first terminal. 7 . The method according to claim 6 , wherein the short-range communication module comprises at least one of a Bluetooth module and an NFC near-field communication module.

8. The method according to claim 6, wherein if the short-distance communication is NFC near-field communication; the method further comprises: Enable the first terminal to enter a card emulation mode for near field communication; The step of storing the processed transaction identification information in the short-distance communication module of the first terminal specifically includes: The processed transaction identification information is saved in a simulated card obtained in the first terminal based on the card simulation mode.

9. The method as claimed in claim 1, wherein the payment result information includes at least one of information of paid users, information of non-paid users, information of the number of paid people, information of paid amounts, information of non-paid people, and information of non-paid amounts.

10. The method according to claim 1, wherein the payment result information includes information about the first transaction amount executed by the second terminal; the method further comprises: A payment result page is displayed; the payment result page includes the first transaction amount information or the first completed transaction amount information obtained based on the first transaction amount information.

11. The method of claim 10, further comprising: Acquire the second transaction amount information executed by the third terminal; The third terminal is a terminal of a user who needs to pay for the transaction; The second transaction amount information or the second completed transaction amount information is displayed in the payment result page; the second completed transaction amount information is the information obtained by adding the transaction amount represented by the second transaction amount information to the completed transaction amount represented by the first completed transaction amount information.

12. The method of claim 2, wherein the payment page includes a first control for triggering payment using a short-distance communication method; The obtaining the payment information submitted by the first user based on the payment page specifically includes: Acquire a first operation of the first user on the first control; Based on the first operation, the payment information is obtained.

13. The method according to claim 1, before the first terminal establishes a short-range communication connection with the second terminal, further comprising: A prompt message is displayed to prompt payment via short-distance communication.

14. The method of claim 13, further comprising: The payment result information is displayed in a prompt page that displays the prompt information.

15. The method of claim 1, further comprising: Displaying a second control for sending the transaction to other users in a non-short-range communication manner; If the user's operation on the second control is obtained, a message for other users to pay for the transaction is sent to the other users in a non-short-range communication manner.

16. The method of claim 15, wherein if the operation of the first user on the second control is obtained, sending a message for other users to pay for the transaction to the other users in a non-short-range communication manner, specifically comprises: If the user's operation on the second control is obtained, determining the payment sharing information corresponding to the transaction identification information; The payment sharing information includes at least one of a code image or link information corresponding to the transaction identification information; According to the information of the third user determined by the first user, the payment sharing information is sent to the user terminal of the third user in a non-short-range communication manner.

17. The method of claim 15, wherein the second control is located in a page for displaying the payment result information; or, the second control is located in a page for displaying prompt information for payment via short-distance communication.

18. The method according to claim 2, wherein the payment page further includes an area for filling in or selecting user information of the second terminal; and the payment information further includes user information of the second terminal.

19. The method according to claim 2, wherein the number represented by the information on the number of people participating in the transaction is a number including users of the first terminal or a number excluding users of the first terminal.

20. The method of claim 19, wherein the payment page further comprises a selection control for selecting whether to use the user of the first terminal as the payee.

21. The method as claimed in claim 2, wherein the payment page includes an area for selecting or filling in a payee; and the transaction identification information is identification information of a payment made to the payee by at least one user including a user of the first terminal.

22. In the method as claimed in claim 1, the user of the first terminal is the payee, and the transaction identification information is identification information used by multiple other users to pay the user of the first terminal; or, the user of the first terminal is the payee, and the transaction identification information is identification information used by the user of the first terminal to pay multiple other users.

23. A method for multi-person payment, comprising: The second terminal establishes a short-range communication connection with the first terminal; Acquiring transaction identification information of transactions that need to be paid by multiple users in the first terminal through the short-range communication connection; Based on the transaction identification information, sending a payment processing request to a server; The server executes a payment process for the second terminal based on the payment processing request; Acquire payment result information for the second terminal generated by the server based on the payment processing request.

24. The method according to claim 23, wherein the second terminal establishes a short-range communication connection with the first terminal, specifically comprising: The second terminal sends an electromagnetic signal for triggering near field communication; An NFC near field communication connection is established with the first terminal that responds to the electromagnetic signal.

25. The method according to claim 24, before the second terminal sends the electromagnetic signal for triggering near field communication, further comprising: A card reader mode of near field communication of the second terminal is started.

26. The method according to claim 23, wherein the second terminal establishes a short-range communication connection with the first terminal, specifically comprising: The second terminal performs Bluetooth pairing with the first terminal; Establishing a Bluetooth connection with the first terminal.

27. The method of claim 23, wherein obtaining transaction identification information of transactions that need to be paid by multiple users in the first terminal through the short-range communication connection specifically comprises: Acquire tag information of short-range communication in the first terminal through the short-range communication connection; The tag information includes the transaction identification information.

28. The method of claim 27, wherein the tag information further includes application identification information of the payment application; the method further includes: Based on the application identification information, starting the payment application; The sending of the payment processing request to the server based on the transaction identification information specifically includes: Using the activated payment application, a payment processing request is sent to the server.

29. The method of claim 23, further comprising: Based on the transaction identification information, displaying a transaction page; the transaction page includes information on the amount to be paid by the second terminal or the transaction page includes an area for filling in the transaction amount; Acquiring a confirmation operation performed by the second user based on the transaction page; The sending of the payment processing request to the server specifically includes: Based on the confirmation operation, a payment processing request is sent to the server.

30. A method for multi-person payment, comprising: Obtaining a payment processing request sent by the second terminal; The payment processing request is generated by the second terminal based on transaction identification information obtained from the first terminal by short-distance communication; the transaction identification information corresponds to a transaction that needs to be paid by multiple users; each of the multiple users needs to pay part of the amount in the transaction; executing a payment process for the second terminal corresponding to the transaction identification information based on the payment processing request; The payment result information for the second terminal is sent to the second terminal.

31. The method of claim 30, further comprising: The payment result information indicating the transaction result of the second terminal is sent to the first terminal.

32. The method of claim 31, if the second terminal has completed payment, the method further comprises: Determining the completed transaction amount information for the transaction based on the transaction amount information completed by the second terminal; Sending the transaction amount information of the completed transaction to the first terminal.

33. The method of claim 30, further comprising: Obtaining a first payment trigger request sent by the first terminal; The first payment triggering request is generated by the first terminal based on payment information submitted by the first user; The payment information includes amount information and number of persons involved in the transaction; generating the transaction identification information based on the first payment trigger request; The transaction identification information is sent to the first terminal.

34. The method according to claim 30, before obtaining the payment processing request sent by the second terminal, further comprising: Acquire a second payment triggering request sent by the second terminal based on the transaction identification information; Based on the second payment trigger request, a transaction page is fed back to the second terminal; the transaction page includes information on the amount to be paid by the second terminal or the transaction page includes an area for filling in the transaction amount.

35. The method according to claim 30, wherein executing the payment process corresponding to the transaction identification information for the second terminal based on the payment processing request specifically comprises: Determining information about the amount that the second terminal needs to pay in the transaction; The amount indicated by the amount information to be paid by the second terminal is a partial amount of the total amount corresponding to the transaction; The amount to be paid by the second terminal is deducted from the user account of the second terminal.

36. The method according to claim 30, after obtaining the payment processing request sent by the second terminal, further comprising: Determining whether the payment processing request meets the transaction processing conditions; The transaction processing conditions include at least one of the following: The transaction amount completed for the transaction is less than the total amount required for the transaction; The number of people who have completed the transaction is less than the total number of people required for the transaction; The transaction identification information is in a valid state; The second terminal has not completed payment for the transaction.

37. The method of claim 36, further comprising: If the payment processing request does not meet the transaction conditions, feeding back transaction prompt information to the second terminal; The transaction prompt information includes at least one of prompt information indicating that the transaction has been completed and prompt information indicating that no payment is required.

38. A multi-person payment device, comprising: A connection module, used to establish a short-distance communication connection with a second terminal; a sending module, configured to send transaction identification information of a transaction to be paid by multiple users to the second terminal via the short-distance communication connection; each of the multiple users needs to pay a portion of the amount in the transaction; an acquisition module, configured to acquire payment result information fed back by a server; the server being a target server to which the second terminal sends a payment processing request based on the transaction identification information; The server executes a payment process based on the payment processing request to generate the payment result information.

39. A multi-person payment device, comprising: A connection module, used to establish a short-distance communication connection with the first terminal; A first acquisition module, configured to acquire, through the short-distance communication connection, transaction identification information of transactions that need to be paid by multiple users in the first terminal; A sending module, used for sending a payment processing request to a server based on the transaction identification information; The server executes a payment process for the second terminal based on the payment processing request; The second acquisition module is used to acquire payment result information for the second terminal generated by the server based on the payment processing request.

40. A multi-person payment device, comprising: An acquisition module, used to acquire a payment processing request sent by the second terminal; The payment processing request is generated by the second terminal based on transaction identification information obtained from the first terminal by short-distance communication; the transaction identification information corresponds to a transaction that needs to be paid by multiple users; each of the multiple users needs to pay part of the amount in the transaction; An execution module, configured to execute the payment process for the second terminal corresponding to the transaction identification information based on the payment processing request; The sending module is used to send the payment result information for the second terminal to the second terminal.

41. A multi-person payment device, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can implement the multi-person payment method described in any one of claims 1 to 22, or implement the multi-person payment method described in any one of claims 23 to 29, or implement the multi-person payment method described in any one of claims 30 to 37.

42. A computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the multi-person payment method described in any one of claims 1 to 22, or the multi-person payment method described in any one of claims 23 to 29, or the multi-person payment method described in any one of claims 30 to 37.

Images