Payment system, payment method, storage medium, and program product

Abstract

The application provides a payment system, comprising: a first application module arranged in a first terminal, configured to send a device code request information to obtain a device code when payment is made, the device code request information comprising at least identification information for identifying the first terminal; a second application module arranged in a second terminal, configured to read the device code, generate payment information according to the read information, and send the payment information to be paid, the payment information comprising a payment order and a device code; a management application module arranged in a server, configured to receive the device code request information, generate the device code according to the request information and send the device code to the first application, receive the payment information sent by the second application module and determine a candidate payment method, and send the candidate payment method and the payment order to the first application; wherein the first application module makes payment according to the candidate payment method and the payment order. The application also provides a payment method, a program product and the like.

Description

Technical Field

[0001] This application relates to data processing, and more specifically, to payment technology based on device codes. Background Technology

[0002] In everyday QR code payments, depending on the merchant's payment method, the payer needs to find the corresponding payment application (APP) to complete the payment. The whole process is rather cumbersome and cannot prevent the risk of payment codes being maliciously stolen.

[0003] It is necessary to propose improved payment methods. Summary of the Invention

[0004] According to one aspect of this application, a payment system is provided to at least solve at least one of the above problems. The payment system includes: a first application configured to, upon being triggered, acquire a device identifier of the first terminal and generate device code request information including the device identifier, send the device code request information to a server to obtain a device code, and display the acquired device code; a second application configured to, upon reading the displayed device code on the second terminal, generate a transaction message and send the transaction message, the transaction message including a payment order and the device code; and a management application configured on a server configured to receive the device code request information, generate the device code based on the request information and send it to the first terminal, and parse the device code received by the server. The transaction message obtains the payment order and the device code, determines a candidate payment method, and sends the candidate payment method and the payment order to the first terminal; and the first application is configured to, after the first terminal receives the candidate payment method: when the candidate payment method includes only one payment method supported by the first terminal, launch the payment application corresponding to that payment method in the first terminal to perform payment based on the payment order; or, when the candidate payment method includes multiple payment methods supported by the first terminal, launch the payment application corresponding to the payment method selected from the multiple payment methods to perform payment based on the payment order.

[0005] In the example payment system, optionally, the management application is configured to determine the candidate payment method by one of the following methods: selecting the payment method supported by the second terminal as a candidate payment method; or selecting a payment method supported by both the payment method supported by the second terminal and the payment method supported by the first terminal as a candidate payment method.

[0006] In the example payment system, optionally, the first application is further configured to obtain application information after being triggered, and to send the application information to the server in the device code request information, or to send the application information and the device code request information to the server separately; wherein, the application information is used to indicate the payment application supported by the first terminal.

[0007] In the example payment system, optionally, the device code request information also includes the IP information of the first terminal, and the server establishes a communication channel with the first terminal through the IP information after receiving the transaction message from the second terminal.

[0008] In the example payment system, optionally, the second application is further configured to include the payment methods supported by the second terminal in the transaction message, or to send the payment methods supported by the second terminal separately from the transaction message to the server.

[0009] In the example payment system, optionally, the management application is configured to retrieve the payment methods supported by the second terminal from a pre-stored second type of terminal payment methods.

[0010] In the example payment system, optionally, the management application is further configured to retrieve the payment methods supported by the first terminal from a pre-stored first type of terminal payment methods.

[0011] In the example payment system, optionally, the second application generates the transaction message according to the scanned transaction process.

[0012] According to another aspect of this application, a payment method is also provided, which is executed by a server. The method includes: receiving device code request information sent by a first terminal, wherein the device code request information is generated after a first application on the first terminal is triggered, and the device code request information includes at least identification information for identifying the first terminal; generating a device code for the first terminal in response to the device code request information; sending the device code to the first terminal so that the first terminal can display it to a second terminal; receiving a transaction message sent from the second terminal, the transaction message being generated after the second terminal reads the device code, and including a payment order and the device code; parsing the transaction message to obtain the payment order and the device code; determining a candidate payment method; and sending the candidate payment method and the payment order to the first terminal based on the device code, so that after the first terminal receives the candidate payment method, a first application on the first terminal launches a payment application on the first terminal to perform payment based on the payment order.

[0013] According to another aspect of this application, a payment method is also provided, the method being executed by a first terminal, the method comprising: triggering a first application; in response to the triggering, the first application displaying a device code on the first terminal for a second terminal to read. The device code is obtained by the first application through the following process: the first application acquires identification information of the first terminal when triggered; and sends device code request information including the identification information to a server; receives a device code sent by the server, the device code being generated by the server for the first terminal based on the device code request information; and displays the device code to the second terminal.

[0014] According to another aspect of this application, a payment method is also provided, the method being executed by a second terminal, comprising: reading a device code displayed by a first terminal; generating a transaction message after reading the device code, the transaction message including a payment order and the device code; and sending the payment information and the device code.

[0015] According to another aspect of this application, a payment method is also provided, the method comprising: triggering a first application of the first terminal by a first terminal; in response to the triggering, the first application and a server obtain a device code and display the device code to a second terminal through the following interaction: the first application obtains the identification information of the first terminal upon being triggered; sends a device code request message to the server, the device code request message including the identification information; upon receiving the device code request message, the server generates a device code for the first terminal; sends the device code to the first terminal; and the second terminal reads the displayed device code and generates a transaction message, the transaction message including a payment order and the device code; and the second terminal transmits the transaction message... The transaction message is sent to the server; the server parses the transaction message to obtain the payment order and the device code; the server determines a candidate payment method and sends the candidate payment method and the payment order to the first terminal based on the device code; and the first application performs one of the following operations after the first terminal receives the candidate payment method: when the candidate payment method includes only one payment method supported by the first terminal, the payment application corresponding to that payment method in the first terminal is launched to make payment based on the payment order; when the candidate payment method includes multiple payment methods supported by the first terminal, the payment application corresponding to the payment method selected from the multiple payment methods is launched to make payment based on the payment order.

[0016] Optionally, the candidate payment method shown may be determined by the server in one of the following ways: using the payment methods supported by the second terminal as candidate payment methods; or selecting a payment method supported by both the payment methods supported by the second terminal and the payment methods supported by the first terminal as a candidate payment method.

[0017] Optionally, the payment method shown may further include: after being triggered, the first application also obtains application information, the application information being used to indicate the payment application supported by the first terminal; and the application information is included in the device code request information and sent to the server, or the application information and the device code request information are sent to the server separately.

[0018] Optionally, the device code request information in the payment method shown may also include the IP information of the first terminal, so that the server can establish a communication channel with the first terminal through the IP information after receiving the transaction message from the second terminal.

[0019] Optionally, the payment method shown may further include: the second terminal sending a payment method supported by the second terminal, or the server obtaining a payment method supported by the second terminal from a pre-stored second type of terminal payment method.

[0020] Optionally, the payment methods supported by the first terminal are obtained by the server from a pre-stored list of first-type terminal payment methods.

[0021] Additionally, a program product is provided, which includes program instructions that, when executed, can implement any of the payment methods described above.

[0022] A storage medium is also provided, which includes program instructions that, when executed, can implement any of the payment methods described above.

[0023] In the examples above, the first terminal is, for example, the payer's terminal, and the second terminal is, for example, the payee's terminal.

[0024] In the examples above, the device code is either requested by the first application of the first terminal from the server during each payment operation and generated by the server, or requested by the first application of the first terminal from the server and generated by the server, so that the first terminal can use it within a preset time period.

[0025] Using the examples according to this application, the payer only needs to trigger the first application to make the payment each time. In this process, the payer user does not need to search through numerous applications on the first terminal for a merchant-supported payment application when making a payment; they only need to trigger the first application, avoiding accidental operations during the payment application search and saving significant time. During the payment process, after the management application sends the payment order and candidate payment methods to the first terminal, the first application will immediately and proactively launch the payment application to be used on the first terminal, without requiring the user to select and launch the payment application. Furthermore, the device code shown is not a direct payment code, avoiding the risk of fraudulent scanning. It is evident that using any example according to this application greatly improves the convenience of payment. Attached Figure Description

[0026] This application will be more fully understood by referring to the following detailed description of specific embodiments in conjunction with the accompanying drawings, wherein the same reference numerals in the drawings refer to the same elements, wherein:

[0027] Figure 1 and Figure 2 The two payment processes under the existing payment architecture are illustrated respectively;

[0028] Figure 3 This is a structural diagram of a payment system based on the example in this application;

[0029] Figure 4 This is a flowchart of a payment method according to some embodiments of this application;

[0030] Figure 5 This is a flowchart of a payment method according to other embodiments of this application;

[0031] Figure 5a This is a schematic diagram of the process by which the first application obtains the device code;

[0032] Figure 6 This is a flowchart of a payment method according to some embodiments of this application;

[0033] Figure 7 This is a flowchart of a payment method according to an embodiment of this application;

[0034] Figure 8 This is a schematic diagram of the payment process based on some specific examples of this application. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation methods of this application will be clearly and completely described below with reference to the accompanying drawings. It should be noted that the described implementation methods are only a part of the implementation methods of the technical solutions of this application, and not all of them. All other implementation methods obtained by those skilled in the art based on the implementation methods described in this application document without creative effort are covered by the protection scope of this application.

[0036] Figure 1 and Figure 2 The diagrams illustrate two payment processes under the existing payment architecture. Figure 1 It is a merchant's QR code payment user. Figure 2 The former refers to the transaction process where the paying user scans the merchant's QR code, while the latter refers to the transaction process where the user scans the QR code.

[0037] Figure 1 In the scanned transaction process shown, the merchant's staff enters the amount due in the merchant's payment management system (MIS) and clicks "Receive Payment." The MIS then calls upon a scanning device to scan the payment QR code provided by the payer. When making the payment, the payer locates the merchant's payment application (the payment app) on their electronic device (such as a mobile phone), opens it, and clicks on the payment code. Upon clicking the payment code, the payment app requests a payment code from the payment backend. After receiving the payment code, the payer can successfully present the QR code to the recipient. The merchant's scanning device scans the code and initiates a payment request to the QR code payment platform using the obtained payment code, receiving the payment result. Thus, the payment is completed.

[0038] Figure 2 In the main QR code payment process shown, when making a payment, the payer locates the merchant's payment application on their electronic device, such as a mobile phone, opens the application, and clicks "Scan to Pay." This obtains the merchant's QR code and merchant ID. The payer then enters the payment amount, clicks "Pay," and a QR code payment message is generated and sent to the QR code payment backend. The QR code payment backend processes the payment and returns the payment result to the payer's payment application. At this point, the QR code payment provider also sends the payment result to the merchant. Thus, the payment is completed.

[0039] Regardless of Figure 1 The scan payment method is still Figure 2 For users, the primary payment method is scanning a QR code, which requires them to select a payment application supported by the merchant. With numerous applications (also known as apps) on a user's phone, searching through them for a compatible payment method is time-consuming, laborious, and results in a poor user experience.

[0040] The following description, in conjunction with accompanying drawings, illustrates a payment system and payment method based on examples from this application. In short, according to this application, a device code is generated for the payment terminal used by the payer. During subsequent payment processes, the payer does not need to search for a specific payment application within the payment terminal; they only need to present the device code to the payee, such as a merchant. Compared to existing payment processes, payer users do not need to consider which payment applications the payee supports, nor do they need to search for supported payment applications from among the numerous payment applications on the payment terminal, saving payer users time and effort and providing a superior payment experience.

[0041] In the examples below, by way of example and not limitation, the device code can be one of the following: a QR code, a barcode, or other identifiable and readable information code. Furthermore, other identifiable or readable information codes not listed herein are also within the scope of the device codes permitted under this application.

[0042] The first terminal is the payment terminal used by the payer, which can be any of the following: a mobile phone, tablet, wearable device such as a smartwatch, laptop, or computer. The second terminal is the terminal used by the payee, such as a merchant, which can be any of the following: a computer, tablet, smartphone, or wearable device. Furthermore, the second terminal may include an image reading device such as a camera; or it may include a barcode scanner, barcode scanning component, or barcode scanning module. The server is not necessarily a single device; it can include multiple electronic devices or the server may be a cloud-based device. Here, electronic devices can be mobile phones, tablets, wearable devices such as smartwatches, laptops, or computers.

[0043] Figure 3 This is a structural diagram of a payment system based on the example in this application. For example... Figure 3 As shown, the payment system includes a first application 30, a second application 40, and a management application 50. The first application 30 can be installed on a first terminal 3, the second application 40 on a second terminal 4, and the management application 50 on a server 5. As an example, the first, second, and third applications can be implemented as software modules through program instructions, and thus installed on the first terminal, second terminal, and server; alternatively, the first, second, and third applications can be implemented as modules through a combination of software and hardware, and thus installed on the first terminal, second terminal, and server. This application does not limit the specific implementation methods of the first, second, and third applications.

[0044] When the payer wants to make a payment, the first application 30 sends a device code request to the management application 50 to obtain the device code. This device code request includes at least the identification information of the first terminal 3, so that the server receiving the device code request can verify the identity of the first terminal 3. Upon receiving the request, the management application 50 generates a device code for the first terminal 3 based on the information carried in the request and sends the generated device code to the first terminal 3. The first application 30 displays the device code on the first terminal 3 so that the second terminal 4 can read it. The second application 40 generates a transaction message after reading the device code on the second terminal 4. The transaction message includes a payment order and the device code. The second application 40 sends the transaction message to the server 5 through the second terminal 4 so that the server 5 can obtain the transaction message. The management application module 50 parses the transaction message obtained by the server 5 to obtain the payment order and the device code, and further determines candidate payment methods. Subsequently, the management application module 50 sends the candidate payment methods and the payment order to the first terminal 3 through the server. After receiving the candidate payment method and payment order from the first terminal 3, the first application 30 immediately launches a payment application based on the candidate payment method to perform the payment based on the payment order. The first application 30 actively launches the payment application corresponding to the payment method, thus eliminating the need for the paying user to manually launch the payment application, greatly improving the convenience of payment.

[0045] In some examples, the payment application that is invoked is the only payment method specified by the candidate payment methods, such as UnionPay QuickPass. In other examples, the payment application that is invoked is selected from multiple candidate payment methods. For example, if the candidate payment methods include UnionPay QuickPass and WeChat Pay, then the invoked payment application is the corresponding payment application of one of these two payment methods. When there are multiple candidate payment methods, according to the example of this application, multiple payment methods can be displayed to the user through the first terminal, and the user can select from them. Alternatively, a priority order of payment methods has been preset in the first terminal 3, so that the payment method with the highest priority among the multiple candidate payment methods is selected as the payment method to be invoked. In this application, the term "invoke" can include launching the selected payment application so that it functions as if it were selected by the customer for payment. In addition, if the first terminal 3 is in a non-screened state when it receives the candidate payment methods and payment order, in this example, the first application 30 also causes the first terminal 3 to light up its screen.

[0046] The first application 30, the second application 40, and the management application 50 communicate with each other through their respective devices. Specifically, the first application module 30 sends and receives information and displays the device code through the first terminal 3, for example, by displaying the device code on the screen of the first terminal 3. The second application 40 sends and receives information through the second terminal 4. The management application 50 sends and receives information through the server 5.

[0047] As mentioned above, by way of example and not limitation, the first application 30, the second application 40, and the management application 50 may each be a software module, such as an application program implemented in a programming language, installed on the first terminal 3, the second terminal 4, and the server 5, respectively. The first application 30 is run by the first terminal 4. When data processing is required, the first application module and the processor of the first terminal 3 work together to process the data. When communication is required, the first application 30 communicates through the communication interface of the first terminal 3. When display is required, it displays the data through the display screen of the first terminal 3. Similarly, the second application 40 is run by the second terminal 4, and the management application 50 is run by the server 5.

[0048] In more specific examples, management application 50 may include different sub-application modules, which may be run by different systems or devices on the server side. For example, management application 50 may include a payment processing module and a device management module. The payment processing module processes payment matters based on payment orders and device code information, while the device management module generates and sends device codes. The payment management module may be an integrated management module that manages multiple payment systems (each payment system corresponds to its own payment platform and provides payment applications for that payment system), such as managing multiple payment applications like UnionPay QuickPass, Alipay Wallet, and WeChat Pay. The device management module and payment management module may be located in one electronic device or separately in different electronic devices. Similarly, the second application 40 may also be executed by multiple devices, such as a part executed by a computer and a part executed by a scanning device.

[0049] In another example, the first application 30, the second application 40, and the management application 50 can be modules implemented by a combination of software and hardware, respectively located in different devices, such as the first terminal 3, the second terminal 4, and the server 5. For example, they can be modules implemented using a programming language and a processor. Alternatively, the first application module 30, the second application module 40, and the management application module 50 can be partially implemented as software applications and partially implemented by a combination of software and hardware. This application does not limit the implementation method of the first application 30, the second application 40, and the management application 50, as long as the functions described herein are achieved.

[0050] According to the examples in this application, the management application 50 may determine candidate payment methods in different ways, as illustrated below. In the first example, payment methods supported by the second terminal 4 are selected as candidate payment methods. In the second example, payment methods supported by both the second terminal 4 and the first terminal 3 are selected as candidate payment methods. More specifically, in the second example, if the payment methods supported by both the second terminal 4 and the first terminal 3 include multiple candidate payment methods, the management application 50 may send all of these candidate payment methods together as candidate payment methods to the first terminal 3; or alternatively, the management application 50 may select one of these multiple payment methods as a candidate payment method and send it to the first terminal 3.

[0051] In some examples, the second application 40 sends the payment methods supported by the second terminal 4 to the server 5. For instance, the second application module 40 includes the payment methods supported by the second terminal 4 in the transaction message. Thus, the transaction message includes the payment order, device code, and the payment methods supported by terminal 4. Alternatively, the second application 40 may send the transaction message and the supported payment methods separately. In this document, "payment order" includes at least the information of the payee, such as the merchant ID. When the payee is a merchant, the payment order is the merchant order.

[0052] If the second application 40 does not send its supported payment methods, the management application 50, after receiving the transaction message from the server 5, searches for the payment methods supported by the second terminal 4 from the pre-stored second-type terminal payment methods. Here, the second-type terminal refers to the terminal being paid, such as a merchant terminal, which may include the payment methods supported by each of the multiple second terminals supported by the server 5. The second-type terminal payment methods pre-configured on the server 5 are updatable; that is, they can be added, deleted, or modified. It should be understood that updates may require verification to ensure their security.

[0053] If the server 5 does not obtain the payment method supported by the first terminal 3, it may use the payment method of the second terminal 4 determined according to at least one of the examples above as a candidate payment method.

[0054] According to examples in this application, upon being triggered, the first application 30 immediately retrieves the payment methods supported by the first terminal 3 from the first terminal 3 and uses them as application information. This application information can be included in the device code request information or sent separately to the server. The device identifier of the first terminal 3 can be any information that can uniquely identify the first terminal 3, such as a device ID. According to some examples in this application, the first application 30 also retrieves the network IP information of the first terminal 3, such as its IP address, upon being triggered and sends it to the server 5. This IP information can, for example, be included in the device code request information sent to the management application.

[0055] In another example, where the payment methods supported by the first terminal 3 are not sent to the server 5, in some cases, after receiving a device code request, the management application module 50 searches for the payment application supported by the first terminal 3 from a pre-stored list of first-type terminal payment methods based on the device identifier of the first terminal 3 in the request. Here, the first-type terminal refers to the payment terminal, which may include the payment methods supported by each of the multiple first terminals supported by the server 5. In another example, the management application 50 may query the first terminal 3, or the first terminal 3 may send information indicating the payment applications it supports after sending the device code request information.

[0056] As mentioned above, the management application 50 parses the transaction message received by the server 5 to obtain the payment order and device code. Further, after determining the candidate payment methods, the management application 50 sends the payment order and candidate payment methods to the first terminal 3 based on the device code. It should be understood that the device code is generated by the management application 50 for the first terminal 3. Therefore, after obtaining the device code by parsing the transaction message, the management application 50 can determine which specific terminal is the first terminal to make the payment. In the example of this application, the management application 50 has embedded information indicating the request for the device code into the generated device code during the device code generation process, such as the device code's representation. For example, when the management application 50 generates the device code for the first terminal 3, it embeds the identification information of the first terminal 3 into the device code. Other methods that can associate the device code with the requesting terminal are also possible and are not limited to those described herein.

[0057] After receiving the candidate payment method and payment order from the management application 50, as described above, if there is only one candidate payment method, the first application 30 will immediately and proactively launch the payment application corresponding to that payment method in the first terminal 3 to perform the payment operation; or if there are multiple payment methods, it will immediately launch the payment application corresponding to the selected payment method to perform the payment operation.

[0058] In another scenario, the first application 30 may also be configured to directly launch the payment application to make a payment if it is determined that there is only one candidate payment method that can be matched in the payment application installed on the first terminal 3, without considering user selection or priority order.

[0059] If the management application 50 selects the same payment method from the payment methods supported by the second terminal 4 and the first terminal 3 (i.e., a payment method supported by both), then the management application 50 will use the payment method supported by both the second terminal 4 and the first terminal 3 as a candidate payment method. Upon receiving this candidate payment method, if the first terminal 3 includes only one payment method, the first application module 30 will directly launch the payment application corresponding to that payment method on the first terminal 3 to perform the payment; otherwise, if it includes multiple payment methods, the first application module 30 will perform the payment based on the payment application selected by the payer from the payment applications corresponding to those multiple payment methods, or select according to a preset priority order.

[0060] In the examples of this application, by way of example and not limitation, the second application can generate transaction messages according to the scanned transaction process. Furthermore, the device code can be generated by the server after the first terminal requests it from the server for each payment transaction, thus dynamically generating the device code and enhancing the security of the payment process. However, as an alternative, it might be more convenient to generate a single device code for the first terminal and use it for long-term purposes without dynamically generating it for each payment transaction; in this example, long-term use could be a preset duration, such as two months, after which the device code is updated.

[0061] Adopting a combination Figure 3 In the aforementioned payment system, the payer only needs to trigger a first application each time a payment is made. In response, the first application immediately requests a device code from the server and displays it to the payee upon receipt, enabling subsequent payment operations. During this process, the user does not need to search through numerous applications on a first terminal, such as a mobile phone, for a merchant-supported payment application when making a payment; they only need to trigger the first application, avoiding accidental operations during the application search and saving significant time. Furthermore, the displayed device code is not a direct payment code, avoiding the risk of fraudulent scanning. Moreover, because the management application sends the payment order and candidate payment methods to the first terminal during the payment process, the first application immediately and proactively launches the payment application on the first terminal, eliminating the need for the user to select and launch a payment application. This user-friendly payment method greatly improves convenience and increases user engagement.

[0062] Figure 4 This is a flowchart of a payment method according to some embodiments of this application. For example... Figure 4As shown, in step S400, a device code request message sent by a first terminal is received. This device code request message is generated when the first application of the first terminal (i.e., the paying terminal) is triggered, and the device code request message includes at least identification information for identifying the first terminal. In step S402, a device code for the first terminal is generated according to the request message and sent to the first terminal. The first terminal displays the device code after receiving it. As an example, the device code may include the identification information of the first terminal so that the corresponding first terminal can be determined according to the identification information in the device code in subsequent payment operations. However, this is only an example and not a limitation, and other information that can be used to identify the first terminal corresponding to the device code may also be built into the device code. In step S404, a transaction message sent by a second terminal (i.e., the paying terminal) is received. This transaction message is generated after the second terminal reads the device code, and it includes a payment order and the device code. In step S406, the transaction message is parsed to obtain the payment order and the device code, and a candidate payment method is determined. In some examples, the payment methods supported by the second terminal are used as candidate payment methods. In other examples, a payment method supported by both the second terminal and the first terminal is selected as a candidate payment method. In step S408, the candidate payment method and payment order are sent to the first terminal based on the device code, so that after the first terminal receives the candidate payment method, a first application on the first terminal can launch a payment application on the first terminal to perform payment based on the payment order.

[0063] Figure 4 The method shown can be combined with the above. Figure 3 The example described is executed by server 5 and management application 50. Regarding the determination of candidate payment methods and the process of the first application launching the payment application, the above is combined with... Figure 3 The examples presented are applicable here, and for the sake of brevity, they will not be elaborated upon further.

[0064] In some examples, the second terminal 4 sends information containing its supported payment methods, which is received by the server 5. For instance, the second terminal's payment methods are included in the transaction message; or, the second terminal 4 sends information containing its supported payment methods to the server 5 separately from the transaction message. In other examples, the server 5 retrieves the payment methods supported by the second terminal 4 from a pre-stored list of second-type terminal payment methods.

[0065] In some examples, the first terminal 3 sends information containing its supported payment methods to the server. For instance, the payment methods of the first terminal 3 may be included in the device code request information, or the first terminal 3 may send information containing its supported payment methods separately from the device code request information. In other examples, the server retrieves the payment methods supported by the first terminal from a pre-stored list of first-type terminal payment methods. Furthermore, the first terminal 3 may also send its IP information to the server, which may be included in the device request information or sent separately. As an example, the server 5 may determine its communication channel with the first terminal 3 based on this IP information before sending the payment order and candidate payment methods. This is merely an example and not a limitation; it should be understood that even if the first terminal 3 does not send its IP information to the server, the server 5 may still identify the first terminal 3 in the network based on its identifier and communicate with it using the existing communication methods between them.

[0066] In the example of this application, IP information may also be used as the identification information of the first terminal 3.

[0067] Figure 4 The method shown is in the form of Figure 3 When server 5 is executed, the first terminal and the second terminal during the execution process can be respectively... Figure 3 The first terminal 3 and the second terminal 4 are in the process. Server 5 executes according to... Figure 4 The payment method shown can achieve the combination of the above. Figure 3 The example described illustrates the functionality of server 5. As an example, Figure 4 The method shown can be implemented as an application program by program instructions, and then loaded into server 5 so that it can achieve integration when executing program instructions. Figure 4 The process of the described method.

[0068] Figure 5 This is a flowchart of a payment method according to other embodiments of this application. The method is executed by a first terminal, which serves as a payment terminal and includes a first application. In step S500, the first application is triggered. In various examples of this application, the first application may be a new application set to the first terminal, or alternatively, the first application may be an existing application in the first terminal, but with the functions performed by the first application described herein added to that existing application. The first application may be triggered via the screen of the first terminal; or via voice; or by the payer's terminal (such as a second terminal), for example, by the payer's terminal being brought close to the first terminal. In step S502, in response to the triggering, the first application displays a device code on the first terminal for the second terminal to read.

[0069] Figure 5aThis is a schematic diagram of the process by which the first application obtains the device code. In step S5021, when the first application is triggered, it immediately obtains the identification information of the first terminal. In step S5023, it sends a device code request message including the identification information to the server. In step S5025, it receives the device code sent by the server, which is generated by the server for the first terminal based on the device code request message. In step S5027, the device code is shown.

[0070] In some examples, upon being triggered, the first application immediately obtains information about the payment methods supported by the first terminal, as application information. This application information may be included in the device code request information and sent to the server, or it may be sent to the server separately. In some examples, upon being triggered, the first application immediately obtains the IP information of the first terminal and includes it in the device code request information and sends it to the server, or it may be sent to the server separately.

[0071] Back Figure 5 The method further includes step S504, receiving candidate payment methods and payment orders sent by the server. In step S506, when the first application receives the candidate payment methods, it performs either the first or second operation. The first operation includes, when the candidate payment methods include only one payment method supported by the first terminal, launching the payment application corresponding to that payment method on the first terminal to perform payment based on the payment order. The second operation includes, when the candidate payment methods include multiple payment methods supported by the first terminal, launching the payment application corresponding to the selected payment method from the multiple payment methods to perform payment based on the payment order. As an example, the selected payment method is determined according to a pre-set payment method priority order, for example, the payment method with the highest priority among the candidate payment methods is selected. Alternatively, the first terminal can display the selected payment method to the user for selection.

[0072] Figure 5 The method shown can be combined Figure 3 The first terminal 3 and the first application 30 are described and executed. (The above is in conjunction with...) Figure 3 The various examples described regarding the first terminal 3 and the first application 30 can all be implemented by a payment method executed by the first terminal according to the examples of this application.

[0073] Figure 6 This is a flowchart of a payment method according to some embodiments of this application. The method is executed by a second terminal, which acts as the terminal being paid to, for example... Figure 3The second terminal 4 is described in step S600. In step S602, after reading the device code, the second terminal generates a transaction message, which includes a payment order and the device code. In step S604, the transaction message is sent to the server. As an example, the second terminal can send information about the payment methods supported by the second terminal to the server; this information can be included in the transaction message or sent separately to the server. According to the example in this application, when the second terminal generates the transaction message in step S602, it can generate it according to the scanned transaction process. Therefore, when executing this method, there is no need to make many changes to the execution process of the second terminal. Figure 6 The method shown can be implemented as an application by an instruction program, for example, the second application is implemented by a second terminal. Figure 6 The method shown can be combined Figure 3 The second terminal 4 and the second application 40 are described and executed. (The above is in conjunction with...) Figure 3 The examples described regarding the second terminal 3 and the second application 30 can all be implemented by a payment method executed by the second terminal according to the examples of this application.

[0074] Figure 7 This is a flowchart of a payment method according to an embodiment of this application. The following will refer to... Figure 3 The payment system shown is executed Figure 7The payment method shown is explained below. In step S700, the first application of the first terminal is triggered via the first terminal 3. In step S702, in response to this triggering, the first application interacts with the server 5 through the following process to obtain a device code and display it to the second terminal 4: After being triggered, the first application 30 obtains the identification information of the first terminal 3; sends a device code request message to the server 5, the device code request message including the identification information; after receiving the device code request message, the server 5 generates a device code for the first terminal 3; and sends the device code to the first terminal 3. In step S706, the second terminal 4 reads the displayed device code and generates a transaction message, which includes a payment order and the device code. For example, the second terminal 4 scans the device code displayed by the first terminal 3, and then generates a transaction message including a payment order and the device code. As an example, this transaction message can be generated according to the scanned transaction process. The payment order is used to indicate the amount to be paid, the receiving account, and other information. The device code is included in the payment information so that the server receiving the payment information can identify which terminal is making the payment. In step S708, the second terminal 4 sends the transaction message to the server 5. In step S710, the server 5 parses the transaction message to obtain the payment order and device code, and determines the candidate payment method. Here, the method of generating the candidate payment method described above in conjunction with the examples is applicable here and will not be repeated. In step S712, the server 5 sends the candidate payment method and the parsed payment order to the first terminal 3. In step S714, after the first terminal 3 receives the candidate payment method, the first application 30 performs one of the following operations: (1) when the candidate payment method includes only one payment method supported by the first terminal, the payment application corresponding to the payment method in the first terminal is launched to make payment based on the payment order; (2) when the candidate payment method includes multiple payment methods supported by the first terminal, the payment application corresponding to the payment method selected from the multiple payment methods is launched to make payment based on the payment order.

[0075] As mentioned above Figure 3 As described, the candidate payment method can be determined by the server 5 through one of the following methods: using the payment methods supported by the second terminal as candidate payment methods; or selecting a payment method supported by both the payment methods supported by the second terminal and the payment methods supported by the first terminal as a candidate payment method. The specific process has been described above.

[0076] also, Figure 7In some examples of the method shown, the first application, after being triggered, also obtains application information, which indicates the payment application supported by the first terminal; and the application information is included in the device code request information and sent to the server, or the application information and the device code request information are sent to the server separately.

[0077] Figure 7 In other examples of the method shown, the device code request information may also include the IP information of the first terminal, so that the server can establish a communication channel with the first terminal through the IP information after receiving the transaction message from the second terminal.

[0078] Figure 7 In some further examples of the method shown, the second terminal may send the payment methods it supports, or the server may retrieve the payment methods supported by the second terminal from a pre-stored list of second-type terminal payment methods. Alternatively, the payment methods supported by the first terminal may be retrieved by the server from a pre-stored list of first-type terminal payment methods.

[0079] The above text combined Figure 3 All examples described can be executed Figure 7 The method shown is implemented in the process, that is, by combining Figure 3 The steps and functions performed by the first terminal, first application, second terminal, second application, server, and management application can all be derived from... Figure 7 The method shown is implemented as described. I will not go into further detail.

[0080] Figure 8 This application describes a payment process based on specific examples. In this process, the first terminal is the payer's mobile phone 3', the second terminal includes the merchant's computer 4a and a scanning device 4b connected to the computer 4a, and the server includes a device management platform 5a. The application scenario in this example is a user, acting as the payer, making a payment to a merchant, acting as the payee, via their mobile phone 3'. Figure 8 In the example, the payment methods supported by the merchant include Alipay, UnionPay, and WeChat Pay.

[0081] Figure 3 The system shown can be combined with Figure 8 In the system architecture shown, for example, the first application module 30 is set in mobile phone 3'; the second application module 40 is set in computer 4a. More specifically, it can be integrated into the payment management system MIS set up by the merchant on computer 4a. It should be understood that the payment management system MIS is the merchant's existing payment management system, as mentioned earlier in this application. Figure 1 and Figure 2One of the systems used by the described merchant; the management application module 50 is implemented in the device management platform 5a.

[0082] After a user purchases goods and intends to pay, the merchant's staff enters the amount to be paid on the payment management system (MIS) of the merchant's computer 4a and clicks (S801) "Receive Payment". After clicking "Receive Payment", the payment management system (MIS) of computer 4a calls (S802) the scanning device 4b. On the user's side, because payment is required, the user clicks the first application module 30 on their mobile phone 3'. The first application module 30 obtains (S803) the device and application information of the mobile phone 3'. In this example, the obtained device and application information includes the mobile phone ID, mobile phone IP information, and the payment methods supported by the mobile phone. Subsequently, the mobile phone 3' constructs the device and application information obtained by the first application module 30 into a device code request message and sends (S804) it to the device management platform 5a. The management application module 50 in the device management platform 5a generates and sends (S806) the device code to the mobile phone 3' based on the mobile phone ID. The user displays the device code received by the mobile phone 3' to the scanning device 4b for the scanning device 4b to scan and obtain the device code (S808). The scanning device 4b sends its device code (S809) to the computer 4a. Upon receiving the device code, the payment management system (MIS) integrated with the second application module 40 assembles the device code and payment order into a transaction message, and sends the transaction message, for example, as a QR code, to the payment fusion module 7 (S810). The payment fusion module 7 extracts the merchant order and device code from the message and sends the name of the payment application supported by the merchant to the device management platform 5 (S811). After receiving the information sent by the platform 7, the device management platform 5 can determine from the device code that the payment terminal corresponding to the code is mobile phone 3', and thus can communicate with mobile phone 3'.

[0083] In this example, the payment methods supported by mobile phone 3' are already included in the device request sent in S804. Therefore, after determining (S812) mobile phone 3', device management platform 5 can determine the payment methods supported by mobile phone 3'. Thus, device management platform 5 extracts (S813) payment methods supported by both merchant device 4a and mobile phone 3' from the payment methods supported by the merchant and mobile phone 3', forming candidate payment methods. Device management platform 5 sends the candidate payment methods and payment order to mobile phone 3' (S814). The first application module 30 on mobile phone 3' searches (S815) for the corresponding payment application based on the candidate payment methods. If there is only one corresponding payment application, it directly launches (S816) that application; or, if there are multiple corresponding payment applications, it launches (S818) the payment application selected by the user. For example, if the corresponding payment applications include UnionPay QuickPass and Alipay, and the user selects UnionPay QuickPass from these two, then UnionPay QuickPass is launched.

[0084] The initiated payment application sends a QR code payment request to the corresponding QR code payment backend for processing (S820). In this specific example, for the QR code payment backend, the payment method between the merchant and the user is similar to a main scan payment; therefore, the QR code payment backend only needs to process the payment according to the main scan payment process without any modifications. After the payment is completed, the payment result is sent to the merchant's computer 4a's MIS system to end the entire payment process.

[0085] In the example above, payment integration module 7 is a standalone module that interacts and communicates with the merchant's MIS system. In practical applications, it can be integrated into the merchant's MIS system. For example, and not as a limitation, payment integration module 7 can be located in the merchant's computer 4a.

[0086] This application also provides a program product comprising program instructions that, when executed, enable any of the payment methods described above. As an example, the program product enables the implementation of the combination of the above... Figure 5 The described method can be integrated into a first terminal as a first application module. This program product can achieve the above integration... Figure 4 The described method can be integrated into the server-side as a management application module. This program product can achieve the above integration... Figure 6 The described method can be integrated into a second terminal as a second application module. This program product can achieve the above integration... Figure 7 When describing the method, it can be combined with Figure 1 The payment system shown.

[0087] This application also provides a storage medium including program instructions that, when executed, enable any of the payment methods described above.

[0088] According to the examples in this application, device codes are used. This means that regardless of whether the merchant or other payee supports WeChat Pay, Alipay, UnionPay QuickPass, or other unlisted payment applications, the payer only needs to obtain and display the device code through the first application (module). If necessary, they only need to select one payment method from those provided by the first application, without needing to search for the required payment application in the terminal application, greatly simplifying the process for the payer. Furthermore, according to the examples in this application, there is no need to display a payment code during the payment process, effectively avoiding the risk of malicious scanning of the payment code and improving security. From the perspective of the merchant or other payee, according to the examples in this application, no system modifications are required; they only need to be able to read the device code and send it to the server, making it simple, user-friendly, and easy to integrate into their existing payment management system.

[0089] In summary, based on the examples in this application, aggregated payment for multiple payment applications is achieved without requiring the payer to manually search for specific payment applications. Furthermore, during the payment process, the process of scanning the payer's payment code is transformed into scanning the device code, making the payment process similar to the main scan transaction. This ensures a good experience for both the payee and the payer while being compatible with the existing payment management MIS transaction processes of the merchant and other payees.

[0090] The technical features in the various embodiments of this application can be combined with each other to form new implementation methods without departing from the spirit of this application and without conflicting with each other. Although specific embodiments of this application have been shown and described in detail to illustrate the principles of this application, it should be understood that this application can be implemented in other ways without departing from such principles.

Claims

1. A payment system, characterized in that, The payment system includes: A first application set on a first terminal is used to obtain the device identifier of the first terminal and generate device code request information including the device identifier when triggered, send the device code request information to the server to obtain the device code, and display the obtained device code. A second application is configured on the second terminal to generate a transaction message after reading the device code shown on the second terminal and to send the transaction message, the transaction message including a payment order and the device code; A management application, located on the server side, is used to receive the device code request information, generate the device code based on the request information and send it to the first terminal, parse the transaction message received by the server to obtain the payment order and the device code, determine candidate payment methods, and send the candidate payment methods and the payment order to the first terminal; and Wherein, the first application is configured to, after the first terminal receives the candidate payment method: when the candidate payment method includes only one payment method supported by the first terminal, launch the payment application corresponding to the payment method in the first terminal to make payment based on the payment order; or, when the candidate payment method includes multiple payment methods supported by the first terminal, launch the payment application corresponding to the payment method selected from the multiple payment methods to make payment based on the payment order.

2. The payment system according to claim 1, characterized in that, The management application is configured to determine the candidate payment method in one of the following ways: The payment methods supported by the second terminal are selected as candidate payment methods; Choose a payment method supported by both the second terminal and the first terminal as a candidate payment method.

3. The payment system according to claim 2, characterized in that, The first application is further configured to acquire application information after being triggered, and to send the application information to the server in the device code request information, or to send the application information and the device code request information separately to the server; wherein the application information is used to indicate the payment application supported by the first terminal.

4. The payment system according to claim 1, characterized in that, The device code request information also includes the IP information of the first terminal. After receiving the transaction message from the second terminal, the server establishes a communication channel with the first terminal through the IP information.

5. The payment system according to claim 2, characterized in that, The second application is further configured to include the payment methods supported by the second terminal in the transaction message, or to send the payment methods supported by the second terminal separately from the transaction message to the server.

6. The payment system according to claim 2, characterized in that, The management application is configured to retrieve the payment methods supported by the second terminal from a pre-stored list of second-type terminal payment methods.

7. The payment system according to claim 2, characterized in that, The management application is also configured to retrieve the payment methods supported by the first terminal from a pre-stored first type of terminal payment methods.

8. The payment system according to claim 1, characterized in that, The second application generates the transaction message according to the scanned transaction process.

9. The payment system according to any one of claims 1 to 8, wherein, The device code: The first application of the first terminal requests the server during each payment operation, and the server generates the payment. or The first application of the first terminal requests the server and the server generates the necessary information so that the first terminal can use it within a preset time period.

10. A payment method, characterized in that, The method is executed by the server, and the method includes: The device code request information sent by the first terminal is received, wherein the device code request information is generated after the first application of the first terminal is triggered, and the device code request information includes at least identification information for identifying the first terminal. In response to the device code request information, a device code for the first terminal is generated; The device code is sent to the first terminal so that the first terminal can display it to the second terminal; Receive a transaction message sent from the second terminal. The transaction message is generated after the second terminal reads the device code and includes a payment order and the device code. Parse the transaction message to obtain the payment order and the device code; Determine candidate payment methods; and The candidate payment method and the payment order are sent to the first terminal based on the device code, so that the first terminal can perform a first application: After the first terminal receives the candidate payment method, if the candidate payment method includes only one payment method supported by the first terminal, the payment application corresponding to that payment method in the first terminal is launched to make payment based on the payment order; or, if the candidate payment method includes multiple payment methods supported by the first terminal, the payment application corresponding to the payment method selected from the multiple payment methods is launched to make payment based on the payment order.

11. The payment method according to claim 10, characterized in that, The candidate payment method is determined by the server through one of the following methods: The payment methods supported by the second terminal are selected as candidate payment methods; Choose a payment method supported by both the second terminal and the first terminal as a candidate payment method.

12. The payment method according to claim 11, characterized in that, The method further includes: Receive application information and / or IP information sent by the first terminal; The application information and / or IP information may be included in the device code request information, or the application information and / or IP information may be sent to the server separately from the device code request information.

13. The payment method according to claim 11, characterized in that, The method further includes: The server receives payment methods supported by the second terminal from the second type of terminal payment methods that are pre-stored.

14. The payment method according to claim 13, characterized in that, The method further includes: The payment methods supported by the first terminal are obtained from the pre-stored first type of terminal payment methods.

15. A payment method, characterized in that, The method is executed by a first terminal, the first terminal including a first application, the method including: Trigger the first application; In response to the trigger, the first application displays a device code on the first terminal for the second terminal to read. The device code is obtained by the first application through the following process: When the first application is triggered, it obtains the identification information of the first terminal; Send a device code request message including the identification information to the server; Receive a device code sent by the server, the device code being generated by the server for the first terminal based on the device code request information; The device code is displayed to the second terminal; The method further includes: Receive the candidate payment method and payment order sent by the server; When the first application receives the candidate payment method on the first terminal, it performs one of the following operations: When the candidate payment methods include only one payment method supported by the first terminal, the payment application corresponding to that payment method in the first terminal is launched to make payment based on the payment order; If the candidate payment methods include multiple payment methods supported by the first terminal, the payment application corresponding to the selected payment method from the multiple payment methods is launched to make payment based on the payment order.

16. The payment method according to claim 15, characterized in that, The method further includes: Upon being triggered, the first application obtains application information indicating the payment applications supported by the first terminal; and The application information may be included in the device code request information and sent to the server, or the application information may be sent to the server separately from the device code request information.

17. The payment method according to claim 16, characterized in that, The device code request information also includes the IP information of the first terminal.

18. The payment method according to claim 17, characterized in that, The selected payment method is chosen through any of the following methods: The payment method with the highest priority in the pre-set priority order; The selection is displayed to the user via a first terminal.

19. A payment method, characterized in that, The method includes: The first application on the first terminal is triggered by the first terminal; In response to the trigger, the first application obtains the device code through the following interaction with the server and displays the device code to the second terminal: Upon being triggered, the first application obtains the identification information of the first terminal; Send device code request information to the server, wherein the device code request information includes the identification information; Upon receiving the device code request information, the server generates a device code for the first terminal; Send the device code to the first terminal; and The second terminal reads the device code shown and generates a transaction message, the transaction message including a payment order and the device code; The second terminal sends the transaction message to the server. The server parses the transaction message to obtain the payment order and the device code; The server determines candidate payment methods and sends the candidate payment methods and the payment order to the first terminal based on the device code; and After receiving the candidate payment method on the first terminal, the first application performs one of the following operations: When the candidate payment methods include only one payment method supported by the first terminal, the payment application corresponding to that payment method on the first terminal is launched to make payment based on the payment order; If the candidate payment methods include multiple payment methods supported by the first terminal, the payment application corresponding to the selected payment method from the multiple payment methods is launched to make payment based on the payment order.

20. The payment method according to claim 19, characterized in that, The candidate payment method is determined by the server through one of the following methods: The payment methods supported by the second terminal are selected as candidate payment methods; Choose a payment method supported by both the second terminal and the first terminal as a candidate payment method.

21. The payment method according to claim 19, characterized in that, The method further includes: Upon being triggered, the first application also acquires application information, which indicates the payment applications supported by the first terminal; and The application information may be included in the device code request information and sent to the server, or the application information may be sent to the server separately from the device code request information.

22. The payment method according to claim 19, characterized in that, The device code request information also includes the IP information of the first terminal, so that the server can establish a communication channel with the first terminal through the IP information after receiving the transaction message from the second terminal.

23. The payment method according to claim 20, characterized in that, The method further includes: the second terminal sending the payment methods supported by the second terminal, or the server obtaining the payment methods supported by the second terminal from a pre-stored second type of terminal payment methods.

24. The payment method according to claim 20, characterized in that, The payment methods supported by the first terminal are obtained by the server from the pre-stored first type of terminal payment methods.

25. The payment method according to any one of claims 10 to 24, wherein, The device code: The first application of the first terminal requests the server during each payment operation, and the server generates the payment. or The first application of the first terminal requests the server and the server generates the necessary information so that the first terminal can use it within a preset time period.

26. A program product, characterized in that, The program product includes program instructions that, when executed, enable the payment method according to any one of claims 10 to 24.

27. A non-temporary storage medium, characterized in that, The storage medium includes program instructions that, when executed, implement the payment method according to any one of claims 10 to 24.

Images