Method, apparatus and device for multi-person payment, and medium

Abstract

Disclosed in the embodiments of the present specification are a method, apparatus and device for multi-person payment, and a medium. The solution may comprise: after a first terminal establishes a short-distance communication connection with a second terminal, sending, to the second terminal and by means of the short-distance communication connection, transaction identification information of a transaction that needs to be paid by a plurality of users, wherein each of the plurality of users needs to pay a portion of the amount in the transaction; and subsequently, acquiring payment result information fed back by a server, wherein the server is a target server to which the second terminal sends a payment processing request on the basis of the transaction identification information; and the server executes a payment process on the basis of the payment processing request to generate the payment result information.

Description

A method, apparatus, equipment and medium for multi-person payment

[0001] This application claims priority to Chinese Patent Application No. 202510105010.X, filed on January 23, 2025, entitled "A Method, Apparatus, Device and Medium for Multiple Payments", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of short-range communication technology, and in particular to a method, apparatus, device, and medium for multi-person payment. Background Technology

[0003] With the development of the times, electronic payment has become increasingly popular, and multi-person payments among friends have also become a trend. This includes splitting the bill equally (AA) or other non-AA multi-person payments. For example, in multi-person payment scenarios, friends share the bill, with each person contributing their share. Currently, multi-person payment orders are mainly realized through sharing on various online social products. For instance, orders are shared with friends via chat by displaying images or links related to the order. Before making payment, the parties involved need to access the corresponding social product and find the order QR code or link shared by the initiator. Furthermore, multi-person payments require existing friendships or membership in the same group, which lacks convenience.

[0004] Therefore, a more convenient multi-person payment solution is needed. Summary of the Invention

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

[0006] To address the aforementioned technical problems, embodiments of this specification provide a first method for multi-user payment, comprising: establishing a short-range communication connection between a first terminal and a second terminal; sending transaction identifier information of a transaction requiring payment by multiple users to the second terminal via the short-range communication connection; each of the multiple users needing to pay a portion of the transaction amount; obtaining payment result information fed back by a server; the server being the target server for the second terminal to send a payment processing request based on the transaction identifier information; and the server executing a payment process based on the payment processing request to generate the payment result information.

[0007] This specification also provides a second method for multi-user payment, comprising: establishing a short-range communication connection between a second terminal and a first terminal; obtaining transaction identifier information of a transaction in the first terminal that requires payment by multiple users through the short-range communication connection; sending a payment processing request to a server based on the transaction identifier information; the server executing 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.

[0008] This specification also provides a third method for multi-user payment, comprising: obtaining a payment processing request sent by a second terminal; the payment processing request being generated by the second terminal based on transaction identifier information obtained from a first terminal via short-range communication; the transaction identifier information corresponding to a transaction requiring payment by multiple users; each of the multiple users needing to pay a portion of the transaction amount; executing a payment process for the second terminal corresponding to the transaction identifier information based on the payment processing request; and sending payment result information for the second terminal to the second terminal.

[0009] This specification also provides a device for multi-user payment, comprising: a connection module for establishing a short-range communication connection with a second terminal; a sending module for sending transaction identifier information of a transaction requiring payment 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 transaction amount; and an acquisition module for acquiring payment result information fed back by a server; the server being the target server for the second terminal to send a payment processing request based on the transaction identifier information; and the server executing a payment process based on the payment processing request to generate the payment result information.

[0010] This specification also provides a second type of multi-user payment device, comprising: a connection module for establishing a short-range communication connection with a first terminal; a first acquisition module for acquiring transaction identifier information of transactions requiring payment by multiple users in the first terminal through the short-range communication connection; a sending module for sending a payment processing request to a server based on the transaction identifier information; the server executing a payment process for the second terminal based on the payment processing request; and a second acquisition module for acquiring payment result information for the second terminal generated by the server based on the payment processing request.

[0011] This specification also provides a third type of multi-user payment device, comprising: an acquisition module for acquiring 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 a first terminal via 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; an execution module for executing a payment process for the second terminal corresponding to the transaction identification information based on the payment processing request; and a sending module for sending payment result information for the second terminal to the second terminal.

[0012] This specification also provides a device for multi-user payment, 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, the instructions being executed by the at least one processor to enable the at least one processor to implement the first multi-user payment method described above, or the second multi-user payment method described above, or the third multi-user payment method described above.

[0013] This specification also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the first method of multi-person payment, the second method of multi-person payment, or the third method of multi-person payment described above.

[0014] At least one embodiment provided in this specification can achieve the following beneficial effects:

[0015] In the embodiments of this specification, in a multi-user payment scenario, after the first terminal establishes a short-range communication connection with the second terminal, the first terminal can send transaction identifier information for a transaction requiring payment by multiple users to the second terminal via the short-range communication connection. Upon receiving the transaction identifier information, the second terminal can send a payment processing request to the server based on this information. Upon receiving the payment processing request, the server can execute the payment process based on the request, generate payment result information, and then feed that result information back to the first terminal. Therefore, when the first terminal needs to send a transaction order to the second terminal, it no longer needs to send it via a QR code or link; instead, it establishes a short-range communication connection with the second terminal and transmits the transaction identifier information to the second terminal via this connection, allowing the second terminal to complete the payment at the server based on the transaction identifier information. Because the short-range communication connection is easy to establish—user terminals only need to be close together to connect—it effectively improves payment convenience and enhances the user experience in multi-user payment scenarios.

[0016] On the other hand, even if the user of the first terminal and the user of the second terminal are not friends in the terminal application, multi-person payment can still be realized, which can also improve the convenience of payment. Attached Figure Description

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

[0018] Figure 1 is a schematic diagram of an application scenario of a multi-person payment method provided in the embodiments of this specification;

[0019] Figure 2 is a flowchart illustrating a method for multi-person payment provided in an embodiment of this specification;

[0020] Figure 3 is a schematic diagram of a payment page for multiple users to make payments, provided in an embodiment of this specification;

[0021] Figure 4 is a schematic diagram of a payment result page provided in an embodiment of this specification;

[0022] Figure 5 is a flowchart illustrating the second method for multi-person payment provided in the embodiments of this specification;

[0023] Figure 6 is a flowchart illustrating the third method for multi-person payment provided in the embodiments of this specification;

[0024] Figure 7 is a swimlane diagram of a multi-person payment method provided in an embodiment of this specification;

[0025] Figure 8 is a structural schematic diagram of a multi-person payment device corresponding to Figure 2 provided in the embodiments of this specification;

[0026] Figure 9 is a structural schematic diagram of the second type of multi-person payment device corresponding to Figure 5 provided in the embodiments of this specification;

[0027] Figure 10 is a structural schematic diagram of the third type of multi-person payment device corresponding to Figure 6 provided in the embodiments of this specification;

[0028] Figure 11 is a schematic diagram of the structure of a multi-person payment device provided in an embodiment of this specification. Detailed Implementation

[0029] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0030] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” used in one or more embodiments of this application and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” used in one or more embodiments of this application refers to and includes any or all possible combinations of one or more associated listed items.

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

[0032] 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, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0033] In current technology, for scenarios requiring multiple people to make payments, major mobile payment platforms have launched multi-person payment products, allowing friends to share bills and each person to contribute a portion of the cost. However, current multi-person payment orders are mainly shared through various online social products. Before making payment, the party executing the transaction needs to enter the corresponding social product and find the order QR code or link shared by the transaction initiator, or the party executing the transaction needs to scan the order QR code presented by the transaction initiator using a mobile device, which lacks convenience.

[0034] To address the shortcomings of the existing technology, the following embodiments are provided in this solution.

[0035] Figure 1 is a schematic diagram of an application scenario of a multi-person payment method provided in the embodiments of this specification.

[0036] As shown in Figure 1, after the first terminal 101 and the second terminal 102 establish a short-range communication connection, the first terminal 101 can send transaction identifier information of a transaction that requires payment by multiple users to the second terminal 102 through the short-range communication connection. After receiving the transaction identifier information, the second terminal 102 can send a payment processing request to the server 103 based on the transaction identifier information. After receiving the payment processing request, the server 103 can execute the payment process corresponding to the transaction identifier information for the second terminal 102 based on the payment processing request, generate payment result information, and feed back the payment result information to both the first terminal 101 and the second terminal 102.

[0037] The server 103 includes, but is not limited to, any device, equipment, platform, or server cluster with computing and processing capabilities. Data transmission between the first terminal 101 and the server 103 can be conducted via a local area network (LAN), a wide area network (WAN), the Internet, or other types of data network connections, or through other means, without specific limitations. Similarly, data transmission between the second terminal 102 and the server 103 can be conducted via a LAN, a WAN, the Internet, or other types of data network connections, or through other means, without specific limitations.

[0038] The first terminal 101 and the second terminal 102 transmit information based on a short-range communication connection. The short-range 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.

[0039] Figure 2 is a flowchart illustrating a multi-person payment method provided in an embodiment of this specification. From a hardware perspective, the executing entity of this process can be a terminal device, specifically a first terminal. From a program perspective, the executing entity of this process can be an application program installed on the terminal device. As shown in Figure 2, the process may include the following steps:

[0040] Step 202: The first terminal establishes a short-range communication connection with the second terminal.

[0041] In the embodiments described in this specification, the first terminal and the second terminal can be any terminal device with short-range communication capabilities, such as a smartphone, tablet, laptop, PDA, or smartwatch. In practical applications, the first terminal can be the terminal device of the transaction initiator, and the second terminal can be the terminal device of the corresponding transaction executor. For example, in a scenario where one or more users of second devices need to make payments to users of first devices, the first device is the receiving device, and the second device is the paying device in a multi-person payment scenario. In a scenario where one user of a first device needs to make payments to one or more users of second devices, the first device is the paying device, and the second device is the receiving device in a multi-person payment scenario. Alternatively, in other embodiments, the first terminal can also be the terminal device of the transaction executor, and the second terminal can also be the terminal device of the transaction initiator.

[0042] In the embodiments of this specification, short-distance communication (SMC) is a communication technology that uses transmission media such as radio waves and infrared light to achieve data transmission over a relatively short distance (usually tens of meters or less). SMC technology is typically peer-to-peer, meaning that the communicating parties are on a relatively equal footing, and communication can be achieved without a complex network architecture. Due to the short communication distance and relatively low technical complexity, SMC technology is usually inexpensive and suitable for large-scale deployment and application. SMC technology is currently widely used in home networks, vehicle communication, industrial automation, mobile payment, and access control, among other fields.

[0043] Short-range communication connection methods may include, but are not limited to: Near Field Communication (NFC) connection, Radio Frequency Identification (RFID) connection, Bluetooth connection, infrared connection, and Wi-Fi connection. Taking the establishment of an NFC connection between terminal devices as an example, after two terminal devices have NFC enabled, they can establish an NFC connection between them by bringing them close together and simply "tapping" them together, which is very convenient and efficient.

[0044] Step 204: Send transaction identifier information of a transaction that requires payment 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.

[0045] In the embodiments described in this specification, a transaction requiring payment by multiple users refers to a transaction that requires payment from two or more users for the same transaction. In practical applications, the first terminal can establish a short-range communication connection with one or more second terminals and send transaction identification information to each second terminal through the short-range communication connection, so that the paying users of each second terminal can make payments based on the transaction identification information obtained from the first terminal.

[0046] In the embodiments of this specification, for transactions requiring payment by multiple users, each of the multiple users needs to pay a portion of the transaction amount. The second device, having obtained 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 representing a transaction order, identification information indicating that multiple users need to process a transaction order, etc., without specific limitations.

[0047] In practical applications, the first user can be one of multiple users who need to pay a portion of the transaction. For example, users A, B, and C have a meal together and agree to split the bill (AA). User A first pays the entire bill using their mobile device. Then, User A initiates the AA payment on their mobile device. A transaction identifier is generated on User A's mobile device, and a short-range communication connection is established between User A's mobile device and the mobile devices of User B and User C. The transaction identifier corresponding to this meal order is then sent to User B's and User C's mobile devices. After receiving the transaction identifier, User B and User C can use it to complete their partial payment at the server. In this context, user A's mobile terminal can establish a one-to-one short-range communication connection with user B's mobile terminal and user C's mobile terminal. For example, user A's mobile terminal can communicate with user B's mobile terminal first, and then with user C's mobile terminal; or, user A's mobile terminal can communicate with user C's mobile terminal first, and then with user B's mobile terminal.

[0048] In practical applications, the first terminal can also be a merchant's payment device. The first terminal doesn't necessarily have to be the transaction executor; for example, the first device doesn't necessarily have to be the payer. For instance, users A, B, and C have a meal together and agree to split the cost equally (AA system). Merchant D sets the payment amount and number of people on its payment device and generates a transaction identifier for this meal order. Then, users A, B, and C, holding their mobile phones, approach merchant D's payment device and establish short-range communication connections. After establishing these connections, merchant D's payment device can send the transaction identifier to each user's phone. Users A, B, and C can then use this transaction identifier to make their respective payments on the server.

[0049] Step 206: Obtain payment result information from the server; the server is the target server from which the second terminal sends a payment processing request based on the transaction identifier information; the server executes the payment process based on the payment processing request to generate the payment result information.

[0050] In the embodiments of this specification, payment result information may include, but is not limited to, at least one of the following: the account avatar information of the transaction executor, the account ID information of the transaction executor, the time point information of the transaction executor's payment completion, the amount paid by the transaction executor, the amount to be paid by the transaction executor, and the payment status information of the transaction executor. The payment status information may include at least one of the following: payment incomplete, payment in progress, payment completed, or payment failed.

[0051] In practical applications, after the first terminal obtains the payment information of a target transaction requiring payment from multiple users, submitted by the first user via the payment page, it can send this payment information to the server, requesting the server to generate 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 requiring payment from multiple users. After the second terminal obtains the transaction identification information of the transaction requiring payment from multiple users via a short-range 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 from the second terminal, the server can determine the corresponding target transaction requiring payment from multiple users based on the transaction identification information in the payment processing request and execute the corresponding deduction for the target transaction.

[0052] In practical applications, after the server executes the corresponding payment process based on the payment processing request sent by the second terminal, it can generate payment result information and also feed this payment result information back to the second terminal. The server can also feed the payment result information back to the first terminal, or it can feed the payment result information back to both the second and first terminals; there are no specific limitations on this.

[0053] In the method shown in Figure 2, in a multi-user payment scenario, after the first terminal establishes a short-range communication connection with the second terminal, the first terminal can send transaction identifier information for a transaction requiring payment from multiple users to the second terminal via this connection. Upon receiving the transaction identifier information, the second terminal can send a payment processing request to the server based on this information. Upon receiving the payment processing request, the server can execute the payment process, generate payment result information, and then send this result information back to the first terminal. Therefore, when the first terminal needs to send a transaction order to the second terminal, it no longer needs to send it via a QR code or link. Instead, it establishes a short-range communication connection with the second terminal and transmits the transaction identifier information to it, allowing the second terminal to complete the payment at the server based on the transaction identifier information. Because establishing a short-range communication connection is convenient—user terminals only need to be close to each other to establish a connection—it effectively improves payment convenience and enhances the user experience in multi-user payment scenarios. Furthermore, even if the users of the first and second terminals are not friends in the application, multi-user payments can still be achieved, further improving payment convenience.

[0054] Based on the method shown in Figure 2, this specification also provides some specific implementation schemes of the method, which are described below.

[0055] Optionally, in the method shown in Figure 2, step 202, before the first terminal establishes a short-range communication connection with the second terminal, may further include: 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 including amount information and the number of people participating in the transaction; and determining the transaction identification information based on the payment information.

[0056] In the embodiments of this specification, the first user can be a user of the first terminal, or correspondingly, the user who initiated the transaction. In practical applications, the user of the first terminal can trigger the display of a payment page for multiple users to pay in various ways. For example, after the user of the first terminal makes full payment for an order, they can find a control for displaying the payment page on the order details page, and the control for displaying the payment page can display prompts such as "AA payment", "AA payment with friends", and "multiple payment". Another example is if the user of the first terminal wants to use a payment application on the first terminal for multi-user payment. The operation page of the payment application can include a control for displaying the payment page. For example, the user can find the payment page for multi-user payment by following a preset path. Clicking the controls such as "Receive / Pay" - "Payment" - "Multiple Payment" in the payment application can also display the payment page. Yet another example is when the user of the first terminal is a receiving merchant. When creating a merchant order, the receiving merchant can trigger the "AA payment" payment page for multiple users to pay, so that the merchant can further set the amount to be paid by each consumer and the number of consumers to pay on the payment page.

[0057] In practical applications, the payment page used for payments by multiple users can be generated locally on the first terminal or generated by the first terminal requesting the server; there is no specific limitation on this.

[0058] In practical applications, a first-terminal user can open the target payment application and initiate a multi-user payment within it. After the first-terminal user initiates the multi-user payment, the target payment application can display a payment page for multiple users to pay. In the embodiments of this specification, the first-terminal user can enter payment information such as the amount and the number of participants in the transaction on the displayed payment page for multiple users to pay. After entering this payment information, the user can submit the payment. The amount information can be the total amount, the amount per person, or a portion of the amount; no specific limitation is made.

[0059] In practical applications, the displayed payment page can also include amount information. For example, if a first user pays the full amount for an order and then splits the cost with other users, the paid order will include the paid amount. The first user can find the control for displaying the payment page on the details page of that paid order and trigger the display of the payment page for multiple users. The displayed payment page can then show the amount of the paid order by default, without requiring the first user to input the amount, although the first user can also modify the amount. Similarly, if the first terminal is linked to a POS system, and the POS system has already determined the payment amount and other information, the payment page on the first terminal can display the amount and other information without requiring the user to manually input it.

[0060] The payment information submitted by the first user on the payment page can be entered by the first user or displayed by default on the payment page. No user input is required; only user confirmation is needed. There are no specific restrictions on the source of the payment information.

[0061] In practical applications, the payment information provided by the first user on the payment page, in addition to the amount information and the number of participants in the transaction mentioned above, may also include, but is not limited to: the reason for receiving or paying payment, the payer or payee information designated by the first user, and the payment amount information corresponding to the payer or payee designated by the first user. Setting a reason for receiving or paying payment allows the payer or payee to better understand the reason for the transaction, which is conducive to the smooth progress of payment. After the first user designates a payer or payee, they can receive or pay payment to the designated payer or payee, which helps to improve the flexibility and accuracy of payment. Furthermore, the first user can also specify the amount to be paid by each payer or payee, thereby enabling more flexible receipt or payment.

[0062] Figure 3 is a schematic diagram of a payment page for multiple users to make payments, provided in an embodiment of this specification. As shown in Figure 3, the payment page allows users to enter the total amount, the total number of people, and the reason for payment. After entering the total amount and the total number of people, the average amount received per person is also displayed. For example, if the total amount is 1 yuan and the total number of people is 2, the average amount received per person is 0.5 yuan. Users can also enter the reason for payment on this payment page, or choose from preset reasons such as "gathering," "dinner," or "utility bill."

[0063] Optionally, determining the transaction identifier 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 identifier information based on the payment information; and obtaining the transaction identifier information sent by the server.

[0064] In the embodiments described in this specification, after the first user provides payment information such as amount information and number of participants in the transaction on the payment page and submits it, the first terminal can send a first payment trigger request carrying this 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.

[0065] In practical applications, transaction identifier information can be in string format, containing one or more characters. Each character can be any form, such as a number, letter, Chinese character, or symbol. The number of characters and their combinations can be determined based on actual needs or configuration schemes. Alternatively, transaction identifier information can be in random number or other forms, without specific limitations. Each transaction identifier can correspond to a payment order, where one transaction identifier corresponds to a payment order that needs to be paid by multiple users. If multiple second terminals need to participate in the transaction, the first terminal can generate only one transaction identifier. Multiple second terminals can obtain the same transaction identifier and then request the server to process their respective payments based on the obtained transaction identifier.

[0066] As one implementation method, the transaction identification information can represent the information displayed by the QR code in existing multi-person payment scenarios, such as the QR code number corresponding to the QR code.

[0067] In practical applications, after the server generates corresponding transaction identifier information based on a payment information set, it can associate and store the payment information with the corresponding transaction identifier information. This allows the server to later determine transactions and payment information requiring payment from multiple users based on the transaction identifier information. After generating the transaction identifier information, the server can then send the generated transaction identifier information back to the first terminal.

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

[0069] In practical applications, transaction identification information can also be generated locally by the first terminal using preset rules based on payment information. After generating transaction identification information, the first terminal can send the transaction identification information and payment information to the server. After receiving the information, the server can associate and store the transaction identification information and payment information.

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

[0071] In the method shown in Figure 2, step 202 involves the first terminal establishing a short-range communication connection with the second terminal. Specifically, this may include the first terminal acquiring an electromagnetic signal sent by the second terminal to trigger near-field communication.

[0072] Correspondingly, in the method shown in Figure 2, step 204, sending transaction identification information of a transaction requiring payment by multiple users to the second terminal via the short-range communication connection, may specifically include: sending the transaction identification information to the second terminal via near-field communication based on the electromagnetic signal.

[0073] In the embodiments of this specification, Near Field Communication (NFC) is an emerging technology that allows devices (such as mobile phones) using NFC technology to exchange data when they are close to each other. It evolved from the integration of contactless radio frequency identification (RFID) and interconnection technologies. By integrating the functions of inductive card reader, inductive card and point-to-point communication on a single chip, it enables mobile payment, electronic ticketing, access control, mobile identity recognition, anti-counterfeiting and other functions using mobile terminals.

[0074] In practical applications, near-field communication (NFC) can be divided into passive mode and active mode. In passive mode, the NFC initiating device (also known as the master device) requires a power supply. The master device uses the power supply to provide a radio frequency field and sends data to the NFC target device (also known as the slave device) based on the electromagnetic signals of the radio frequency field.

[0075] In the embodiments of this specification, if the short-range 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 to trigger near-field communication, and send the transaction identification information fed back by the server to the second terminal through near-field communication.

[0076] Optionally, the short-range communication connection may include a Bluetooth connection; in the method of Figure 2, step 202, the first terminal and the second terminal establish a short-range communication connection, which may specifically include: the first terminal and the second terminal pairing via Bluetooth; and establishing a Bluetooth connection with the second terminal.

[0077] Correspondingly, the step of sending transaction identification information for transactions requiring payment by multiple users to the second terminal via the short-range communication connection may specifically include: the first terminal sending the transaction identification information to the second terminal via a Bluetooth connection established with the first terminal.

[0078] In the embodiments described in this specification, Bluetooth is a wireless technology that supports short-range communication (generally within 10 meters) between devices. Bluetooth enables wireless information exchange between numerous devices, including mobile phones, PDAs, wireless headsets, laptops, and related peripherals. Utilizing Bluetooth technology effectively simplifies communication between mobile communication terminal devices and also successfully simplifies communication between devices and the Internet, making data transmission faster and more efficient.

[0079] In practical applications, the first terminal can pair with the second terminal via Bluetooth. After successful pairing, a Bluetooth connection is established between the first and second terminals. Once the Bluetooth connection is established, transaction identification information can be sent to the second terminal through the established Bluetooth connection.

[0080] Optionally, in the method shown in Figure 2, step 202, before the first terminal and the second terminal establish a short-range communication connection, may further 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 conforms to the short-range communication; and saving the processed transaction identification information to the short-range communication module of the first terminal.

[0081] In the embodiments of this specification, a communication protocol refers to the rules and agreements that must be followed by both terminal devices to complete communication or services. The protocol defines the format used for data units, the information and meaning that information units should contain, the connection method, and the timing of information transmission and reception, thereby ensuring that data can be successfully transmitted to the designated terminal device. A short-range communication protocol can refer to the technical specifications used to achieve wireless communication between devices over short distances. Short-range communication protocols are typically suitable for data transmission over distances of tens of meters or less, and feature low power consumption, low cost, and peer-to-peer communication.

[0082] In practical applications, establishing short-range communication between the first terminal and the second terminal requires adherence to short-range communication protocol rules. Transaction identification information, as data that needs to be transmitted using short-range communication, needs to be processed using preset protocol rules that conform to short-range communication protocol rules. After processing, the transaction identification information can be saved in the short-range 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-range communication.

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

[0084] In practical applications, short-range communication modules can include, but are not limited to: Bluetooth modules, NFC near-field communication modules, RFID modules, infrared connection modules, and Wi-Fi modules. Each module can correspond to a specific short-range communication connection method. For example, if both terminal 1 and terminal 2 have NFC near-field communication modules, and both terminals have enabled NFC near-field communication, they can establish an NFC connection when brought close together.

[0085] Optionally, if the short-range communication is NFC near-field communication, the method may further include: enabling the card emulation mode of near-field communication on the first terminal.

[0086] Correspondingly, saving the processed transaction identifier information to the short-range communication module of the first terminal may specifically include: saving the processed transaction identifier information to the simulated card obtained in the first terminal based on the card emulation mode.

[0087] In the embodiments of this specification, near-field communication can be divided into three working modes: point-to-point communication mode, card reader mode, and card emulation mode. In point-to-point mode, two NFC devices can exchange data. For example, multiple NFC-enabled digital cameras or mobile phones can wirelessly interconnect using NFC technology to exchange data. The key to point-to-point communication is connecting two devices that both have NFC functionality, thereby enabling data transmission between points.

[0088] In practical applications, near-field communication (NFC) between the first and second terminals can be achieved through point-to-point mode, or through reader mode and card emulation mode; there are no specific limitations. In card emulation mode, an NFC-enabled device is simulated as a tag or contactless card. For example, an NFC-enabled mobile phone can be read as an access card or bank card. In reader mode, an NFC device can be used as a contactless reader / writer. For example, an NFC-enabled mobile phone can read and write tags that support the NFC data format standard. An NFC device in reader mode can read data from an NFC device in card emulation mode.

[0089] In practical applications, the first terminal can be set to card emulation mode for near-field communication (NFC), while the second terminal can be set to card reader mode for NFC. When the first and second terminals are brought close together, an NFC connection can be established, allowing the second terminal to read data from the first terminal. Specifically, the first terminal saves the processed transaction identifier information to a simulated card obtained in card emulation mode, and the second terminal in card reader mode can then read the transaction identifier information from the simulated card.

[0090] Optionally, the payment result information may include at least one of the following: information on users who have paid, information on users who have not paid, information on the number of people who have paid, information on the amount paid, information on the number of people who have not paid, and information on the amount not paid.

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

[0092] As one implementation, the payment result information may further include the first transaction amount information executed by the second terminal; correspondingly, the method may further 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.

[0093] In practical applications, there can be multiple devices interacting with the first terminal. For example, after the first terminal is close to the second terminal, it can also be close to the third terminal. The user of the third terminal can be a user who needs to make payments for multiple people. Optionally, the method in the embodiments of this specification may further 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 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.

[0094] If the first end user specifies a corresponding transaction party user when initiating a transaction, such as specifying a transaction execution party user, the payment results page can also display information about users who have not paid, such as information about users who have not made payments. Information about users who have not paid can include their profile picture, nickname, and account ID, etc.

[0095] In the embodiments of this specification, transaction amount information may refer to the amount paid by each paying user, and completed transaction amount information may refer to the total amount paid by all paying users. For example: a certain payment requires 3 users (user 1, user 2, and user 3) to each pay 1 yuan. If user 1 and user 2 have completed their payments, but user 3 has not, 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.

[0096] In practical applications, after the first terminal receives the payment result information from the server, it can generate a payment result page locally based on this information. Alternatively, the server can generate the payment result page and send it to the first terminal; there are no specific limitations on this. The payment result page can display at least part of the payment result information.

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

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

[0099] In the embodiments of this specification, the first control used to trigger payment via short-range communication can be an "NFC payment" control, a "Bluetooth payment" control, etc. After the first user triggers the "NFC payment" control, NFC mode can be activated to prepare for data transfer based on NFC; after the first user triggers the "Bluetooth payment" control, Bluetooth can be activated to prepare for data transfer based on Bluetooth.

[0100] In practical applications, the first user's first operation on the first control can include, but is not limited to, clicking, swiping, selecting, and long-pressing. The payment page can contain various types of first controls for users to choose from. For example, Figure 3 is used as an example again. As shown in Figure 3, the payment page contains both an "NFC payment" control and a "Bluetooth payment" control. In practical applications, only one type of control may be used; this is not a limitation.

[0101] Optionally, in the method shown in Figure 2, step 202, before the first terminal and the second terminal establish a short-range communication connection, may further include: displaying a prompt message indicating that payment will be made via short-range communication.

[0102] In the embodiments of this specification, the prompts indicating payment via short-range communication may include messages such as: "Please bring your phone close to the screen," "NFC payment, please tap your phone," "Pay with a simple tap," and "Please turn on Bluetooth." Displaying these prompts guides and instructs payers to make payments via short-range communication, which helps improve payment efficiency and user experience.

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

[0104] In practical applications, payment result information can be displayed on the same page as the notification information used to prompt payment via short-range communication. For example, after the first terminal initiates payment, a page is displayed, which can initially show the notification information. After the second terminal obtains the transaction identifier information or completes the payment, the page can display both the notification information and the result information. Alternatively, payment result information and notification information can be displayed on different pages. For example, payment result information can be displayed via pop-up windows or overlays, without specific limitations. For instance, after the first terminal initiates payment, it can display a notification page containing the notification information. After the second terminal completes the payment, the first terminal can display a result page containing the payment result information. If other terminal users need to establish communication with the first terminal, after the result page on the first terminal has been displayed for a preset time, such as 3 seconds, the first terminal can automatically display a page containing the notification information.

[0105] For example, Figure 4 will be used as an example for illustration. As shown in Figure 4, the page displayed in Figure 4 shows payment result information such as "1 person has paid", "User 2 has paid 0.25 yuan", "User 3 and User 4 have not yet completed payment", "User 3 and User 4 are both waiting to pay 0.25 yuan", and "Total amount received: 0.25 yuan received". At the same time, the prompt message "Please ask the payer to bring the device closer" is also displayed.

[0106] It is understood that Figure 4 is only an illustration. In actual applications, the content shown in Figure 4 may not be fully displayed, or may not be displayed all at once, or may only be a portion of the content, depending on the specific content displayed on the actual page settings. For example, after a user initiates a multi-person payment, the first terminal may display a prompt message indicating that other devices are approaching. If the user performs a click, swipe, or other operation in the area displaying the prompt message, the completed transaction information, such as the amount received as mentioned above, may be displayed in that area.

[0107] Optionally, the method may further include: displaying a second control that sends the transaction to other users using non-short-range communication; if an operation of the second control by a user is detected, then sending a message for other users to pay for the transaction to the other users using non-short-range communication.

[0108] In the embodiments of this specification, non-short-range communication methods can include scanning QR codes, sending links, etc. If the first terminal does not have the conditions to send data using short-range communication methods, it can also use non-short-range communication methods to send transactions to other users so that other users can make payments. This makes the solution more complete, avoids situations where communication is impossible due to a single communication method, and helps to improve the flexibility and success rate of communication.

[0109] In practical applications, user actions on the second control can include, but are not limited to, clicking, swiping, selecting, and long-pressing. After a user triggers the second control, a payment QR code or payment link can be generated, allowing other users to make payments by scanning the QR code or clicking the payment link.

[0110] In practical applications, sending a message for other users to make payments for the transaction via non-short-range communication can be done through SMS, instant messaging, or app messages to prompt other users to make the payment. Optionally, if the first user's operation on the second control is detected, sending a message for other users to make payments for the transaction via non-short-range communication can specifically include:

[0111] If user interaction with the second control is detected, payment sharing information corresponding to the transaction identifier information is determined; the payment sharing information includes at least one of a code image or link information corresponding to the transaction identifier information.

[0112] Based on the information of the third user determined by the first user, the payment sharing information is sent to the third user's user terminal via non-short-range communication.

[0113] In the embodiments of this specification, the payment sharing information can 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-range communication method; no specific limitation is made in this regard. The payment sharing information may carry transaction identification information so that after the third user's user terminal 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.

[0114] In practical applications, payment sharing information is sent to a third user's terminal. This can be achieved by the first terminal sending a payment sharing information generation request to the server. This request may include transaction identifier information and the third user's terminal address or account information. Upon receiving the request, the server generates the payment sharing information. After generating the information, the server can directly send it to the third user based on their terminal address or account information. Alternatively, the server can send the payment sharing information back to the first terminal user, who then sends it to the third user's terminal. Alternatively, the payment sharing information can be generated locally on the first terminal, and then sent by the first terminal user to the third user's terminal.

[0115] Optionally, the second control may be located on a page for displaying the payment result information; or, the second control may be located on a page for displaying a prompt message indicating that payment is made via short-range communication.

[0116] In the embodiments of this specification, the second control is a control capable of sending transactions to other users based on non-short-range communication. Therefore, the second control can be located on a page used to display the payment result information; or, the second control can be located on a page used to display a prompt message indicating that payment was made via short-range communication. This allows users to switch from short-range communication to non-short-range communication at any time by triggering the second control, improving the convenience of communication mode switching and meeting different user needs.

[0117] In the embodiments of this specification, the first terminal user may also designate a second terminal user to participate in the transaction. Optionally, the payment page may also include an area for filling in or selecting the user information of the second terminal; the payment information may also include the user information of the second terminal.

[0118] In the embodiments of this specification, the user information of the second terminal may include, but is not limited to: the user account ID of the second terminal, the user account nickname of the second terminal, and the user account avatar of the second terminal.

[0119] In practical applications, the payment page can also include an area for filling in or selecting user information for a 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; alternatively, if the user of the first terminal and the user of the second terminal have a friend relationship or a history of payment, 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. For example, still using Figure 3 as an example, the payment page shown in Figure 3 also includes a "Select Payer" control. After the first user triggers the "Select Payer" control, a drop-down menu is generated, which can display at least one second user who has a friend relationship or a history of payment with the first user, allowing the first user to select from them for greater convenience.

[0120] In practical applications, if the user of the first terminal specifies the user of the second terminal, the transaction identifier information determined based on the payment information can also correspond to the user information of the specified second terminal. Therefore, when the server performs payment processing based on the transaction identifier information, it can refuse to allow other users besides the specified second terminal user to perform payment processing.

[0121] Optionally, the number of participants in the transaction can be the number including users of the first terminal or the number excluding users of the first terminal.

[0122] In practical applications, when a user on the first terminal enters the number of people participating in the transaction on the payment page, they may or may not include themselves. For example, if user A, user B, and user C spend a total of 300 yuan, and they agree to split the cost equally (AA), with user A paying the merchant the full amount first, when user A initiates payment, they can enter the total amount as 300 yuan and the total number of people as 3 (including user A) on the payment page. In this case, the average payment per person is 100 yuan. Alternatively, user A can enter the total amount as 200 yuan and the total number of people as 2 (excluding user A) on the payment page. In this case, the average payment per person is also 100 yuan.

[0123] In practical applications, the first terminal user can be either the merchant or one of the payers. When the first terminal user is the merchant, the merchant usually does not need to include themselves when determining the number of participants in the transaction. For example: User A and User B spend 100 yuan together and agree to split the cost equally (AA). Merchant C uses an NFC payment device to collect the payment, setting the total amount to 100 yuan and the total number of participants to 2. After setting this up, User A and User B each bring their phones close to the NFC payment device to complete the payment, each paying 50 yuan.

[0124] In practical applications, optionally, the payment page can also include a selection control for choosing whether to include the user of the first terminal as the payer, so that users can more conveniently set the number of participants in the transaction.

[0125] As one implementation, the transaction initiator may not be the payee; the initiator can designate a payee. Optionally, the payment page may also include an area for selecting or filling in the payee; the transaction identification information is identification information indicating that at least one user, including the user of the first terminal, has made a payment to the payee.

[0126] In practical applications, the user of the first terminal can also be the payer. 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 determined transaction identifier information is the identifier information that at least one user, including the user of the first terminal, has made a payment to the payee. Subsequently, the user of the first terminal can complete the payment at the server based on the transaction identifier 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 identifier information to User B's terminal and User C's terminal via short-range communication. User A's terminal, User B's terminal, and User C's terminal can then complete the payment to User D at the server based on the transaction identifier information.

[0127] In practical applications, when the first terminal user initiates the transaction, they can designate the payee. The second terminal user can be either the payee or the payer. When the second terminal user is the payee designated by the first terminal user, a short-range communication connection is not required between the first and second terminals. The first terminal can directly complete the payment at the server based on the transaction identifier information. Alternatively, a short-range communication connection can be established between the first and second terminals, after which the second terminal can display prompts such as "No payment required" or "Waiting for payment from the other party." When the second terminal user is not the payee designated by the first terminal user but is one of the payers, the first terminal can send the transaction identifier information to the second terminal via short-range communication so that the second terminal user can complete the payment at the server based on the transaction identifier information.

[0128] The multi-person payment provided in the embodiments of this specification can be a payment where multiple parties pay one party, or a payment where one party pays multiple parties. Optionally, the user of the first terminal is the recipient, and the transaction identification information is identification information used by multiple other users to make payments to the user of the first terminal; or, the user of the first terminal is the payer, and the transaction identification information is identification information used by the user of the first terminal to make payments to multiple other users.

[0129] In practical applications, the user of the first terminal can be either the payer or the payee. When the user of the first terminal is the payer, a payment can be created for a single payee or for multiple payees. When a payment is created for a single payee, the transaction identifier information is the same as that used by the user of the first terminal to make a payment to that single payee; when a payment is created for multiple payees, the transaction identifier information is the same as that used by the user of the first terminal to make payments to multiple other users.

[0130] Figure 5 is a flowchart illustrating the second method for multi-person payment provided in the embodiments of this specification. From a hardware perspective, the executing entity of this process can be a terminal device, specifically a second terminal. From a program perspective, the executing entity of this process can be an application running on the terminal device. As shown in Figure 5, the process may include the following steps:

[0131] Step 502: The second terminal establishes a short-range communication connection with the first terminal.

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

[0133] Step 506: Based on the transaction identifier information, send a payment processing request to the server; the server executes the payment process for the second terminal based on the payment processing request.

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

[0135] In the embodiments of this specification, the first terminal, the second terminal, the short-range communication connection, the transaction requiring payment by multiple users, the transaction identification information, and the payment processing request can have the same meaning as the terms mentioned in the embodiments of the method in Figure 2. Since the process of establishing a short-range communication connection between the second terminal and the first terminal and the transmission process of the transaction identification information have been described in detail above, they will not be repeated here.

[0136] In this embodiment, the second terminal can obtain transaction identifier information of a transaction requiring payment by multiple users from the first terminal via short-range communication. Then, it can send a payment processing request to the server. This request may include the transaction identifier information. Upon receiving the payment processing request from the second terminal, the server can determine the target transaction requiring payment by multiple users based on the transaction identifier information and execute the deduction for that transaction. After executing the payment process for the second terminal based on the payment processing request, the server can generate payment result information for the second terminal and send this information back to the second terminal.

[0137] In practical applications, the second terminal can make payments simply by touching or bringing it close to the first terminal, which is very convenient and efficient. After receiving the payment result information from the server, the second terminal can display a payment result display page containing the payment result information; alternatively, it can announce the payment result via voice; or it can use other methods to display the payment result to the user, without specific limitations.

[0138] In practical applications, users on the second terminal can make payments by simply tapping the device together with the first terminal. After tapping, the second terminal displays a payment page showing the required payment amount and a "Confirm Payment" control. The user can then complete the payment by triggering the "Confirm Payment" control. Alternatively, the second terminal can directly make a payment after tapping with the first terminal, without requiring user confirmation or input of the payment amount, thus improving payment efficiency and convenience.

[0139] In the method shown in Figure 5, after the second terminal establishes a short-range communication connection with the first terminal, the second terminal can obtain transaction identifier information for transactions requiring payment from multiple users from the first terminal via this connection. Upon receiving the transaction identifier information, the second terminal can send a payment processing request to the server based on this information. Upon receiving the payment processing request, the server can execute the payment process, generate payment result information, and then send this result information back to the first terminal. Therefore, when the first terminal needs to send a transaction order to the second terminal, it no longer needs to send it via a QR code or link. Instead, it establishes a short-range communication connection with the second terminal and transmits the transaction identifier information to the second terminal, allowing the second terminal to complete the payment at the server based on the transaction identifier information. Because establishing a short-range communication connection is convenient—user terminals only need to be close together to connect—it effectively improves payment convenience and enhances the user experience in multi-user payment scenarios.

[0140] On the other hand, the second terminal does not require opening a payment application, clicking a link, or scanning a QR code. After unlocking, it can be used to make a payment simply by tapping it on the device, making the payment process highly convenient.

[0141] Based on the method shown in Figure 5, this specification also provides some specific implementation schemes of the method, which are described below.

[0142] In one implementation, step 502 above, where the second terminal establishes a short-range communication connection with the first terminal, may specifically include: the second terminal sending an electromagnetic signal to trigger near-field communication; and establishing an NFC near-field communication connection with the first terminal responding to the electromagnetic signal.

[0143] In this process, the second terminal, acting as the initiator of near-field communication, sends electromagnetic signals to detect whether a first near-field communication device is nearby. Once detected, it sends instruction information to the first device, which then sends transaction identification information to the second device based on the instruction information.

[0144] Optionally, before the second terminal sends the electromagnetic signal for triggering near-field communication, it may further include: activating the reader mode of the near-field communication of the second terminal.

[0145] In the embodiments of this specification, if the short-range communication connection between the first terminal and the second terminal is an NFC near-field communication connection, the second terminal, as a card reader device, can send an electromagnetic signal to trigger near-field communication, and the first terminal can establish an NFC near-field communication connection with the second terminal based on the electromagnetic signal sent by the second terminal to trigger near-field communication.

[0146] In practical applications, once the second terminal user unlocks it, the second terminal can activate card reader mode. Specifically, the terminal system can set the mobile terminal to card reader mode after confirming that the terminal is unlocked.

[0147] In practical applications, the first and second terminals can communicate via near-field communication (NFC) in point-to-point mode, or via a card reader mode and a card emulation mode. The first terminal can be set to card emulation mode for NFC, while the second terminal can be set to card reader mode. Once both are enabled, an NFC connection can be established when the first and second terminals are brought close together, allowing the second terminal to read data from the first terminal.

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

[0149] In practical applications, the short-range communication connection between the first terminal and the second terminal can also be a Bluetooth connection. The first terminal can pair with the second terminal via Bluetooth, and after successful pairing, 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, it can obtain transaction identification information through the Bluetooth connection established with the first terminal.

[0150] Optionally, in the method shown in Figure 5, step 504, obtaining transaction identifier information of transactions requiring payment by multiple users in the first terminal through the short-range communication connection, may specifically include: obtaining tag information of short-range communication in the first terminal through the short-range communication connection; the tag information includes the transaction identifier information.

[0151] In the embodiments of this specification, the tag information can represent information sent from a first terminal to a second terminal via short-range communication. This information may include transaction identification information, as well as device information of the first terminal, tag validity period, and other information. The tag information can carry various types of information; specifically, the tag information can be in the form of a link, a data packet, or other forms, without specific limitations.

[0152] To facilitate payment by a second terminal, the tag information may optionally include application identification information of the payment application. Correspondingly, the method may further include: launching the payment application based on the application identification information.

[0153] Correspondingly, sending a payment processing request to the server based on the transaction identifier information may specifically include: using the launched payment application to send a payment processing request to the server.

[0154] In the embodiments of this specification, the application identification information of a payment application may include, but is not limited to: the application name, abbreviation, letter abbreviation, package name, and package signature of the payment application. There is a correspondence between the application identification information and the payment application, allowing different systems to launch the same payment application based on its application identification information.

[0155] In practical applications, after the second terminal receives the tag information sent by the first terminal, the terminal system program can parse the tag information to determine the application identifier information of the payment application within the tag information, and launch the corresponding payment application based on this application identifier information. The terminal system program can also send the transaction identifier information parsed from the tag information to the launched payment application, which then generates a payment processing request based on the transaction identifier information and sends the request to the server. The server can be the server corresponding to the payment application, or it can be any server capable of processing business requests initiated by the payment application. The payment application can be launched in the foreground or in the background; there is no specific limitation on this.

[0156] Optionally, the method in Figure 5 may further include: displaying a transaction page based on the transaction identifier information; the transaction page including the amount to be paid by the second terminal or including an area for filling in the transaction amount; and obtaining the confirmation operation performed by the second user based on the transaction page.

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

[0158] In the embodiments of this specification, after the second terminal obtains the transaction identifier information, it can send a second payment trigger request to the server based on the transaction identifier information. After receiving the second payment trigger request, the server can generate and return a transaction page to the second terminal. This transaction page may include the amount information to be paid by the second terminal. After the second terminal user sees the displayed amount information, if it is correct, it can perform a confirmation operation based on the transaction page, such as by clicking the "Confirm Payment" control on the transaction page. After the second terminal user confirms, the second terminal can send a payment processing request containing the transaction identifier information to the server. The payment processing request may also include the amount information to be paid by the second terminal. In practical 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 has defaulted to confirmation. For example, if the second user does not perform any operation within a 30-second countdown after the transaction page is displayed, it can be considered that the user has confirmed.

[0159] In practical applications, the transaction page may also include an area for entering the transaction amount. If the transaction page does not display the amount the second terminal needs to pay, or if the second terminal user does not agree with the amount displayed on the transaction page, the second terminal user can manually enter the transaction amount. After entering the amount, the second terminal user can confirm it. Upon confirmation, the second terminal can send a payment processing request containing transaction identifier information to the server. This payment processing request may also include the amount information entered by the second terminal user.

[0160] In practical applications, the transaction page may not be displayed on the second terminal, eliminating the need for confirmation from the second terminal user and minimizing disruption. This ensures that the second terminal user can continue using other applications on the second terminal. For example, while playing games, reading ebooks, or watching videos on their phone, users can simply place their phone against the screen to make a payment without exiting the app. After the second terminal completes the payment, the system can also obtain payment result information, which serves as a notification to indicate whether the payment has been completed. Specifically, the payment result information can be provided via SMS, app messages, notification sounds, or displayed on a single page.

[0161] Figure 6 is a flowchart illustrating the third method for multi-person payment provided in the embodiments of this specification. From a hardware perspective, the entity executing this process can be a server. From a program perspective, the entity executing this process can be an application running on the server. As shown in Figure 6, the process may include the following steps:

[0162] Step 602: 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-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.

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

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

[0165] In the embodiments of this specification, the first terminal, the second terminal, the short-range communication connection, the transaction requiring payment by multiple users, the transaction identification information, the payment result information, and the payment processing request can have the same meaning as the terms mentioned in the embodiments of the method in Figure 2. Since the process of establishing a short-range communication connection between the second terminal and the first terminal and the transmission process of the transaction identification information have been described in detail above, they will not be repeated here.

[0166] In practical applications, the server can pre-store the association between transaction identifier information and target transactions requiring payment from multiple users. Therefore, upon receiving a payment processing request from the second terminal, the server can determine the corresponding target transaction requiring payment from multiple users based on the transaction identifier information in the request and execute the deduction accordingly. After executing the payment process for the second terminal based on the payment processing request, the server can generate payment result information for the second terminal and feed it back to the second terminal.

[0167] In the method shown in Figure 6, after the first terminal establishes a short-range communication connection with the second terminal, the first terminal can send transaction identifier information for transactions requiring payment from multiple users to the second terminal via this connection. Upon receiving the transaction identifier information, the second terminal can send a payment processing request to the server based on this information. Upon receiving the payment processing request, the server can execute the payment process, generate payment result information, and then send this result information back to the first terminal. Therefore, when the first terminal needs to send a transaction order to the second terminal, it no longer needs to send it via a QR code or link. Instead, it establishes a short-range communication connection with the second terminal and transmits the transaction identifier information to it, allowing the second terminal to complete the payment at the server based on the transaction identifier information. Because establishing a short-range communication connection is convenient—user terminals only need to be close together to connect—it effectively improves payment convenience and enhances the user experience in multi-user payment scenarios.

[0168] Based on the method shown in Figure 6, this specification also provides some specific implementation schemes of the method, which are described below.

[0169] Optionally, the method in Figure 6 may further include: sending payment result information representing the transaction result of the second terminal to the first terminal.

[0170] In practical applications, after the server generates payment result information representing the transaction result of the second terminal, it can feed back the payment result information to the second terminal, or send the payment result information to the first terminal, so that the user of the first terminal can also know the transaction result of the second terminal, which helps to improve the user experience.

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

[0172] In the embodiments 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, it can calculate the completed transaction amount information of the transaction based on the completed transaction amount information of each second terminal. The completed transaction amount information can be the total completed amount information after summing the completed transaction amounts for each second terminal. 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 their payments, while user 3 has not yet completed their payments, then the completed transaction amount for user 1 is 1 yuan, the completed transaction amount for user 2 is 1 yuan, and the completed transaction amount for transaction A is 2 yuan.

[0173] In practical applications, after the server calculates the transaction amount information of the completed transaction, it can send the transaction amount information of the completed transaction to the first terminal so that the user of the first terminal can know the current payment status. Alternatively, the server can send the transaction amount information of each second terminal to the first terminal, and the first terminal can calculate the transaction amount information of the completed transaction locally. There is no specific limitation on this.

[0174] Optionally, the method in this specification may further 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 payment information submitted by the first user; the payment information includes amount information and the number of participants in the transaction; generating the transaction identifier information based on the first payment trigger request; and sending the transaction identifier information to the first terminal.

[0175] In the embodiments described in this specification, after the first user enters payment information such as the amount and the number of participants in the transaction on the payment page and submits it, the first terminal can send a first payment trigger request carrying this 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.

[0176] In practical applications, after the server generates corresponding transaction identifier information based on a payment information set, it can associate and store the payment information with the corresponding transaction identifier information. This allows the server to later determine transactions and payment information requiring payment from multiple users based on the transaction identifier information. After generating the transaction identifier information, the server can then send the generated transaction identifier information back to the first terminal.

[0177] Optionally, before obtaining the payment processing request sent by the second terminal in step 602 above, the method may further include: obtaining a second payment trigger request sent by the second terminal based on the transaction identifier 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 includes an area for filling in the transaction amount.

[0178] In this embodiment, after the second terminal obtains the transaction identifier information, it can send a second payment trigger request to the server based on the transaction identifier information. The second payment trigger request may carry the transaction identifier information. After receiving the second payment trigger request, the server can determine the corresponding target payment order based on the transaction identifier information in the second payment trigger request. Then, based on the amount information and number of users or the payment information required by the user-specified payer in the target payment order, the server can determine the amount the second terminal needs to pay and generate a transaction page. After generating the transaction page, the server can send the transaction page back to the second terminal. The transaction page may include the amount information the second terminal needs to pay. After seeing the displayed amount information, if the second terminal user confirms that it is correct, they can perform a confirmation operation based on the transaction page.

[0179] In practical applications, the transaction page may also include an area for entering the transaction amount. If the transaction page does not display the amount the second terminal needs to pay, or if the second terminal user does not agree with the amount displayed on the transaction page, the second terminal user can manually enter the transaction amount. After entering the amount, the second terminal user can confirm it. Upon confirmation, the second terminal can send a payment processing request containing transaction identifier information to the server. This payment processing request may also include the amount information entered by the second terminal user.

[0180] Optionally, step 604 above: executing the payment process for the second terminal corresponding to the transaction identifier 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 information that the second terminal needs to pay represents a portion 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.

[0181] In the embodiments described in this specification, after the server determines the amount to be paid by the second terminal in the transaction, it can execute the corresponding deduction, deducting the amount to be paid by the second terminal from the user's account. Specifically, the corresponding amount can be deducted from the user's logged-in account in the payment application, or the user of the second terminal can make payment by scanning a QR code, etc., without specific limitations.

[0182] Optionally, after obtaining the payment processing request sent by the second terminal, the process may further 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 that has been completed for the transaction is less than the total amount required for the transaction; the number of people who have completed the transaction for the transaction is less than the total number of people required for the transaction; the transaction identification information is in a valid state; and the second terminal has not executed a payment for the transaction.

[0183] In the embodiments described in this specification, after receiving a payment processing request from the second terminal, the server can determine whether the payment processing request meets the transaction processing conditions. For payment processing requests that do not meet the transaction processing conditions, processing can be prohibited. This avoids wasting processing resources, helps save processing resources, and improves processing efficiency.

[0184] In practical applications, if the amount of completed transactions is not less than the total amount required for the transaction, then no further processing of the payment request is needed; if the number of completed transactions is not less than the total number of participants required for the transaction, then no further processing of the payment request is needed; if the transaction identifier information has expired and is invalid, then no further processing of the payment request is needed; if the second terminal has already executed payment for the transaction, then no further processing of the payment request sent by the second terminal is needed.

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

[0186] In the embodiments of this specification, if the payment processing request does not meet the transaction conditions, the server may send a transaction prompt message to the second terminal. This transaction prompt message may include at least one of two options: a message indicating that the transaction has ended or a message indicating that payment is not required. After receiving the transaction prompt message from the server, the second terminal may display the message so that the user can understand the reason for the payment failure.

[0187] Figure 7 is a swimlane diagram of a multi-person payment method provided in an embodiment of this specification. As shown in Figure 7, the execution entities involved in the multi-person payment method may include a first terminal, a second terminal, and a server. Near-field communication (NFC) is used as an example for illustration. The method flow in Figure 7 may include a transaction identifier information generation and storage stage, a NFC communication stage, and a payment stage. Specifically, it may include the following steps: In the transaction identifier information generation and storage stage, an optional implementation may be as shown in steps 702 to 718 of Figure 7.

[0188] Step 702: The first terminal displays a payment page for multiple users to make payments.

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

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

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

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

[0193] Step 712: The server sends the transaction identifier information back to the first terminal.

[0194] Step 714: The first terminal obtains the transaction identifier information.

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

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

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

[0198] During the near-field communication phase, an optional implementation may be as shown in steps 720 to 730 of Figure 7.

[0199] Step 720: The first terminal displays a prompt message indicating that payment will be made via short-range communication.

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

[0201] Step 724: The second terminal sends an electromagnetic signal to trigger near-field communication.

[0202] Step 726: The first terminal acquires the electromagnetic signal sent by the second terminal to trigger near-field communication.

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

[0204] Step 730: The second terminal obtains the transaction identifier information.

[0205] During the payment phase, an optional implementation may be as shown in steps 732 to 752 of Figure 7.

[0206] Step 732: The second terminal generates a second payment trigger request based on the transaction identifier information, and the second payment trigger request carries the transaction identifier information.

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

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

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

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

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

[0212] Step 744: The server sends the payment result information, representing the transaction result of the second terminal, to the first terminal.

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

[0214] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods.

[0215] Figure 8 is a structural schematic diagram of a multi-person payment device corresponding to Figure 2, provided in an embodiment of this specification. As shown in Figure 8, the device may include:

[0216] The connection module 802 is used to establish a short-range communication connection with the second terminal.

[0217] The sending module 804 is used to send transaction identifier information of a transaction that needs to be paid by multiple users to the second terminal through the short-range communication connection; each of the multiple users needs to pay a portion of the amount in the transaction.

[0218] The acquisition module 806 is used to acquire 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 identifier information; the server executes the payment process based on the payment processing request to generate the payment result information.

[0219] Based on the device in Figure 8, this specification also provides some specific implementation schemes of the device, which will be described below.

[0220] Optionally, the device may further include: a payment page display module for displaying a payment page for multiple users to pay; a payment information acquisition module for acquiring payment information submitted by a first user based on the payment page, wherein the payment information includes amount information and the number of participants in the transaction; and an identification information determination module for determining the transaction identification information based on the payment information.

[0221] Optionally, the identification information determination module may specifically include: a request sending submodule, used to send a first payment trigger request containing the payment information to the server; the server generates the transaction identification information based on the payment information. An identification information acquisition submodule is used to acquire the transaction identification information sent by the server.

[0222] Optionally, the short-range 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 the electromagnetic signal sent by the second terminal to trigger near-field communication.

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

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

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

[0226] Optionally, the device may further include: a protocol rule processing module, configured to process the transaction identifier information according to preset protocol rules to obtain processed transaction identifier information; the preset protocol rules are protocol rules conforming to the short-range communication. An identifier information storage module, configured to store the processed transaction identifier information in the short-range communication module of the first terminal.

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

[0228] Optionally, if the short-range communication is NFC near-field communication, the device may further include: a card emulation mode activation module, used to enable the card emulation mode of near-field communication for the first terminal.

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

[0230] Optionally, the payment result information may include at least one of the following: information on users who have paid, information on users who have not paid, information on the number of people who have paid, information on the amount paid, information on the number of people who have not paid, and information on the amount not paid.

[0231] Optionally, the payment result information may include the first transaction amount information executed by the second terminal; the device may further include: a payment result page display module for 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.

[0232] Optionally, the device may further include: a second transaction amount information acquisition module, used 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.

[0233] The transaction amount information display module is used to display the second transaction amount information or the second completed transaction amount information on the payment result page; the second completed transaction amount information is 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.

[0234] Optionally, the payment page includes a first control for triggering payment using short-range communication. Correspondingly, the payment information acquisition module may specifically include: a first acquisition submodule, used to acquire a first operation performed by the first user on the first control; and a second acquisition submodule, used to acquire the payment information based on the first operation.

[0235] Optionally, the device may further include: a prompt information display module, used to display prompt information indicating that payment is made via short-range communication.

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

[0237] Optionally, the device may further include: a second control display module for displaying a second control for sending the transaction to other users using a non-short-range communication method.

[0238] The non-short-range communication sending module is used to send a message for other users to make payments for the transaction to the other users via non-short-range communication if it detects an operation by the user on the second control.

[0239] Optionally, the non-short-range communication sending module may specifically include: a payment sharing information determination submodule, used to determine payment sharing information corresponding to the transaction identifier information if user operation on the second control is detected; the payment sharing information includes at least one of a code image or link information corresponding to the transaction identifier information. The payment sharing information sending submodule is used to send the payment sharing information to the third user's user terminal via non-short-range communication based on the information of the third user determined by the first user.

[0240] Optionally, the second control is located on a page for displaying the payment result information; or, the second control is located on a page for displaying a prompt message indicating that payment is made via short-range communication.

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

[0242] Optionally, the number of participants in the transaction can be the number including users of the first terminal or the number excluding users of the first terminal.

[0243] Optionally, the payment page may also include a selection control for choosing whether to use the user of the first terminal as the payer.

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

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

[0246] Figure 9 is a structural schematic diagram of the second type of multi-person payment device corresponding to Figure 5, provided in an embodiment of this specification. As shown in Figure 9, the device may include:

[0247] The connection module 902 is used to establish a short-range communication connection with the first terminal.

[0248] The first acquisition module 904 is used to acquire transaction identifier information of transactions that need to be paid by multiple users in the first terminal through the short-range communication connection.

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

[0250] 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.

[0251] Based on the device in Figure 9, this specification also provides some specific implementation schemes of the device, which will be described below.

[0252] Optionally, the connection module 902 may specifically include: an electromagnetic signal transmitting submodule, used to transmit an electromagnetic signal for triggering near-field communication; and a near-field communication connection establishment submodule, used to establish an NFC near-field communication connection with the first terminal responding to the electromagnetic signal.

[0253] Optionally, the device may further include: a reader mode activation module for activating the reader mode of the near-field communication of the second terminal.

[0254] Optionally, the connection module 902 may specifically include: a Bluetooth pairing submodule for Bluetooth pairing with the first terminal; and a Bluetooth connection submodule for establishing a Bluetooth connection with the first terminal.

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

[0256] Optionally, the tag information may also include application identification information of the payment application; the device may further include: a payment application launch module, used to launch the payment application based on the application identification information.

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

[0258] Optionally, the device may further include: a transaction page display module, used to display a transaction page based on the transaction identifier information; the transaction page includes information on the amount to be paid by the second terminal or includes an area for entering the transaction amount. A confirmation operation acquisition module is used to acquire confirmation operations performed by the second user based on the transaction page.

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

[0260] Figure 10 is a structural schematic diagram of the third type of multi-person payment device corresponding to Figure 6, provided in the embodiments of this specification. As shown in Figure 10, the device may include:

[0261] The acquisition module 1002 is 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 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.

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

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

[0264] Based on the device in Figure 10, this specification also provides some specific implementation schemes of the device, which will be described below.

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

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

[0267] Optionally, the device may further include: a payment trigger request acquisition module, configured 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 the number of participants in the transaction. A transaction identifier information generation module, configured to generate the transaction identifier information based on the first payment trigger request. A transaction identifier information sending module, configured to send the transaction identifier information to the first terminal.

[0268] 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 identifier information; and a transaction page feedback module, configured to provide 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 includes an area for entering the transaction amount.

[0269] Optionally, the execution module 1004 may specifically include: an amount information determination submodule, used to determine the amount information to be paid by the second terminal in the transaction; the amount information to be paid by the second terminal represents a portion of the total amount corresponding to the transaction; and an amount deduction submodule, used to deduct the amount to be paid by the second terminal from the user account of the second terminal.

[0270] Optionally, the device may further include: a judgment module, used to determine whether the payment processing request meets the transaction processing conditions. The transaction processing conditions include at least one of the following: the total amount of completed transactions for the transaction is less than the total amount required for the transaction; the number of people for whom the transaction has been completed is less than the total number of people required for the transaction; the transaction identification information is valid; and the second terminal has not executed a payment for the transaction.

[0271] Optionally, the device may further include: a transaction prompt information feedback module, used to send 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 a prompt indicating that the transaction has ended and a prompt indicating that no payment is required.

[0272] Based on the same idea, this specification also provides devices corresponding to the above methods in its embodiments.

[0273] Figure 11 is a schematic diagram of a computing device provided in an embodiment of this specification. As shown in Figure 11, the device 1100 may include: at least one processor 1110; and a memory 1130 communicatively connected to the at least one processor.

[0274] Corresponding to the multi-person payment method shown in Figure 2, the memory 1130 stores instructions 1120 that can be executed by the at least one processor 1110. These instructions, when executed by the at least one processor 1110, enable the at least one processor 1110 to:

[0275] A short-range communication connection is established with the second terminal; transaction identifier information of a transaction requiring payment by multiple users is sent to the second terminal through the short-range communication connection; each of the multiple users needs to pay a portion of the amount in the transaction; payment result information is obtained from the server; the server is the target server for the second terminal to send a payment processing request based on the transaction identifier information; the server executes the payment process based on the payment processing request to generate the payment result information.

[0276] Corresponding to the multi-user payment method shown in Figure 5, the memory 1130 stores instructions 1120 that can be executed by the at least one processor 1110. These instructions, when executed by the at least one processor 1110, enable the at least one processor 1110 to: establish a short-range communication connection with a first terminal; obtain transaction identifier information of transactions requiring payment by multiple users in the first terminal through the short-range communication connection; send a payment processing request to a server based on the transaction identifier information; and execute a payment process for the second terminal based on the payment processing request.

[0277] Obtain the payment result information for the second terminal generated by the server based on the payment processing request.

[0278] In the multi-user payment method shown in Figure 6, the memory 1130 stores instructions 1120 that can be executed by the at least one processor 1110. These instructions, when executed by the at least one processor 1110, enable the at least one processor 1110 to: acquire a payment processing request sent by a second terminal; the payment processing request is generated by the second terminal based on transaction identifier information obtained from a first terminal via short-range communication; the transaction identifier information corresponds to a transaction requiring payment by multiple users; each of the multiple users needs to pay a portion of the transaction amount; execute the payment process corresponding to the transaction identifier information for the second terminal based on the payment processing request; and send payment result information for the second terminal to the second terminal.

[0279] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device shown in FIG11 is basically similar to the method embodiment, so the description is relatively simple; relevant parts can be referred to the description of the method embodiment.

[0280] An embodiment of this specification also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the above-described method for multi-person payment.

[0281] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium belongs to the same concept as the technical solution of the multi-person payment method described above. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the icon generation method or the training method of the icon generation model described above.

[0282] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0283] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, 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, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0284] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

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

[0286] For ease of description, the above devices are described in terms of function, divided into various units. Of course, in implementing this specification, the functions of each unit can be implemented in one or more software and / or hardware components.

[0287] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied 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.

[0288] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0289] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0290] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

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

[0292] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0293] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0294] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

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

[0296] The above description is merely an embodiment of this specification and is not intended to limit this specification. Various modifications and variations can be made to this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for multi-person payment, comprising: The first terminal establishes a short-range communication connection with the second terminal; The transaction identifier information of a transaction requiring payment by multiple users is sent 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; Obtain payment result information from the server; the server is the target server to which the second terminal sends a payment processing request based on the transaction identifier information. The server executes the payment process based on the payment processing request to generate the payment result information.

2. The method as described in claim 1, further comprising, before the first terminal establishes a short-range communication connection with the second terminal: Displays a payment page for multiple users to make payments; Obtain the payment information submitted by the first user based on the payment page; The payment information includes the amount and the number of people participating in the transaction; Based on the payment information, the transaction identifier information is determined.

3. The method as described in claim 2, wherein determining the transaction identifier information based on the payment information specifically includes: Send a first payment trigger request containing the payment information to the server; The server generates the transaction identification information based on the payment information; Obtain the transaction identifier information sent by the server.

4. The method as described in claim 1, wherein the short-range communication connection includes an NFC near-field communication connection; the establishment of a short-range communication connection between the first terminal and the second terminal specifically includes: The first terminal acquires the electromagnetic signal sent by the second terminal to trigger near-field communication; The step of sending transaction identifier information for transactions requiring payment by multiple users to the second terminal via the short-range 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 as described in claim 1, wherein the short-range communication connection includes a Bluetooth connection; the establishment of a short-range communication connection between the first terminal and the second terminal specifically includes: The first terminal and the second terminal pair via Bluetooth; Establish a Bluetooth connection with the second terminal; The step of sending transaction identifier information for transactions requiring payment by multiple users to the second terminal via the short-range 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 as described in claim 1, further comprising, before the first terminal establishes a short-range communication connection with the second terminal: The transaction identifier information is processed according to preset protocol rules to obtain processed transaction identifier information; The preset protocol rules are those that conform to the short-range communication protocol rules; The processed transaction identification information is saved to the short-range communication module of the first terminal.

7. The method as described in claim 6, wherein the short-range communication module includes at least one of a Bluetooth module and an NFC near-field communication module.

8. The method of claim 6, wherein the short-range communication is NFC near-field communication; the method further comprises: Enable the card emulation mode for near-field communication on the first terminal; Saving the processed transaction identifier information to the short-range communication module of the first terminal specifically includes: The processed transaction identification information is saved to the simulated card obtained in the first terminal based on the card emulation mode.

9. The method as described in claim 1, wherein the payment result information includes at least one of the following: information of users who have paid, information of users who have not paid, information of the number of people who have paid, information of the amount paid, information of the number of people who have not paid, and information of the amount not paid.

10. The method of claim 1, wherein the payment result information includes the first transaction amount information executed by the second terminal; the method further includes: The 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: Obtain the transaction amount information of the second transaction executed by the third terminal; The third terminal is the terminal of the user who needs to make payment for the transaction; The payment result page displays the second transaction amount information or the second completed transaction amount information; the second completed transaction amount information is 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-range communication method; The step of obtaining the payment information submitted by the first user based on the payment page specifically includes: Obtain the first operation performed by the first user on the first control; Based on the first operation, the payment information is obtained.

13. The method of claim 1, further comprising, before the first terminal establishes a short-range communication connection with the second terminal: The system displays a message prompting users to make payments via short-range communication.

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

15. The method of claim 1, further comprising: A second control displays the method of sending the transaction to other users using non-short-range communication. If user interaction with the second control is detected, a message for other users to make payments for the transaction is sent to the other users via non-short-range communication.

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

17. The method of claim 15, wherein the second control is located on a page for displaying the payment result information; or, the second control is located on a page for displaying a prompt message indicating that payment is made via short-range communication.

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

19. The method of claim 2, wherein the number of participants 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 includes a selection control for selecting whether to use the user of the first terminal as the payer.

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

22. The method of claim 1, wherein the user of the first terminal is the payee, and the transaction identification information is identification information used by multiple other users to make payments to the user of the first terminal; or, the user of the first terminal is the payer, and the transaction identification information is identification information used by the user of the first terminal to make payments to multiple other users.

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

24. The method as described in claim 23, wherein establishing a short-range communication connection between the second terminal and the first terminal specifically includes: The second terminal sends an electromagnetic signal to trigger near-field communication; An NFC near-field communication connection is established with the first terminal that responds to the electromagnetic signal.

25. The method of claim 24, further comprising, before the second terminal sends the electromagnetic signal for triggering near-field communication: Initiate the card reader mode for near-field communication of the second terminal.

26. The method as described in claim 23, wherein establishing a short-range communication connection between the second terminal and the first terminal specifically includes: The second terminal pairs with the first terminal via Bluetooth; Establish a Bluetooth connection with the first terminal.

27. The method of claim 23, wherein obtaining transaction identifier information of transactions requiring payment by multiple users in the first terminal via the short-range communication connection specifically includes: The tag information of the short-range communication in the first terminal is obtained 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: The payment application is launched based on the application identification information; Sending a payment processing request to the server based on the transaction identifier information specifically includes: Using the launched payment application, a payment processing request is sent to the server.

29. The method of claim 23, further comprising: Based on the transaction identifier information, a transaction page is displayed; the transaction page includes information on the amount to be paid by the second terminal or includes an area for entering the transaction amount. Obtain the confirmation operation performed by the second user based on the transaction page; Sending 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: Obtain the 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 via 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, the payment process corresponding to the transaction identifier information for the second terminal is executed; Send payment result information for the second terminal to the second terminal.

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

32. The method of claim 31, wherein if the second terminal has completed payment, the method further comprises: Based on the transaction amount information already completed by the second terminal, determine the transaction amount information already completed for the transaction; The transaction amount information indicating that the transaction has been completed is sent to the first terminal.

33. The method of claim 30, further comprising: Obtain the 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 the amount and the number of participants in the transaction; The transaction identifier information is generated based on the first payment trigger request; The transaction identifier information is sent to the first terminal.

34. The method of claim 30, further comprising, before obtaining the payment processing request sent by the second terminal: Obtain the second payment trigger request sent by the second terminal based on the transaction identifier information; The second payment trigger request sends a transaction page to the second terminal; the transaction page includes information about the amount the second terminal needs to pay, or the transaction page includes an area for entering the transaction amount.

35. The method of claim 30, wherein executing the payment process for the second terminal corresponding to the transaction identifier information based on the payment processing request specifically includes: Determine the amount that the second terminal needs to pay in the transaction; The amount to be paid by the second terminal represents a portion of the total amount corresponding to the transaction; The amount payable by the second terminal will be deducted from the user account of the second terminal.

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

37. The method of claim 36, further comprising: If the payment processing request does not meet the transaction conditions, a transaction prompt message is sent to the second terminal. The transaction notification information includes at least one of the following: a notification indicating that the transaction has ended or a notification indicating that no payment is required.

38. A device for multi-person payment, comprising: A connection module is used to establish a short-range communication connection with a second terminal; The sending module is used to send transaction identifier 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; The acquisition module is used to acquire 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 identifier information. The server executes the payment process based on the payment processing request to generate the payment result information.

39. A device for multi-person payment, comprising: A connection module is used to establish a short-range communication connection with the first terminal; The first acquisition module is used to acquire transaction identifier information of transactions that need to be paid by multiple users in the first terminal through the short-range communication connection; The sending module is used to send a payment processing request to the server based on the transaction identifier information; The server executes the 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 device for multi-person payment, comprising: The acquisition module is used to acquire payment processing requests 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 via 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; An execution module is used to execute the payment process for the second terminal corresponding to the transaction identifier information based on the payment processing request; The sending module is used to send payment result information for the second terminal to the second terminal.

41. A device for multi-user payment, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which enable the at least one processor to implement the multi-person payment method according to any one of claims 1 to 22, or the multi-person payment method according to any one of claims 23 to 29, or the multi-person payment method according to any one of claims 30 to 37.

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

Images