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

Abstract

The invention provides a payment system, comprising: a first application module arranged at a first terminal and used for sending device code request information to obtain a device code and show the obtained device code during payment, the device code request information at least comprising identification information for identifying the first terminal; the second application module is arranged at a second terminal, reads the equipment code, generates payment information according to the read information, and sends the payment information to wait for payment, and the payment information comprises a payment order and the equipment code; the management application module is arranged at the server side and is used for receiving the equipment code request information, generating the equipment code according to the request information and sending the equipment code to the first application; receiving the payment information sent by the second application module and determining a candidate payment mode; sending the candidate payment mode and the payment order to the first application; wherein the first application module carries out payment according to the candidate payment mode and the payment order. Payment methods, program products, and the like are also provided.

Description

Technical Field

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

[0002] In daily QR code payment, according to the different payment methods of the merchant, the payer needs to find the corresponding payment application (APP) to make the payment. The whole process is cumbersome and cannot prevent the risk of payment code being stolen by malicious payment.

[0003] There is a need to come up with improved payment methods. Summary of the invention

[0004] According to one aspect of the present application, a payment system is provided to solve at least one of the above problems. The payment system includes: a first application set at a first terminal, used to obtain the device identification of the first terminal and generate device code request information including the device identification when triggered, send the device code request information to a server to obtain the device code, and display the acquired device code; a second application set at a second terminal, used to generate a transaction message after the second terminal reads the displayed device code, and send the transaction message, the transaction message including the payment order and the device code; a management application, which is set at the server, used to receive the device code request information, generate the device code according to the request information and send it to the first terminal, parse the device code received by the server, and send the transaction message to the server. transaction message to obtain the payment order and the device code, determine the candidate payment method, and send 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, pull up 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, pull up the payment application corresponding to the payment method selected from the multiple payment methods to make payment based on the payment order.

[0005] In the payment system illustrated, optionally, the management application is configured to determine the candidate payment method in one of the following ways: taking a payment method supported by the second terminal as a candidate payment method; selecting a payment method supported by both the second terminal and 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 include the application information in the device code request information and send it to the server, or send the application information and the device code request information separately to the server; wherein the application information is used to indicate the payment applications supported by the first terminal.

[0007] In the payment system exemplified, optionally, the device code request information also includes 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 illustrated payment system, optionally, the second application is further configured to include the payment method supported by the second terminal in the transaction message, or to send the payment method supported by the second terminal and the transaction message separately to the server.

[0009] In the illustrated payment system, optionally, the management application is configured to obtain the payment method supported by the second terminal from pre-stored second-category terminal payment methods.

[0010] In the illustrated payment system, optionally, the management application is further configured to obtain a payment method supported by the first terminal from pre-stored first-category terminal payment methods.

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

[0012] According to another aspect of the present application, a payment method is also provided, which is executed by a server, and 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 of the first terminal is triggered, and the device code request information at least includes 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 shows it to a second terminal; receiving a transaction message sent from the second terminal, wherein the transaction message is generated after the second terminal reads the device code, and includes a payment order and the device code; parsing the transaction message to obtain the payment order and the device code; determining candidate payment methods; and sending the candidate payment methods and the payment order to the first terminal based on the device code, so that after the first terminal receives the candidate payment method, the first application of the first terminal pulls up a payment application in the first terminal to make a payment based on the payment order.

[0013] According to another aspect of the present application, a payment method is also provided, the method is executed by a first terminal, the method comprising: triggering the first application; as a response to the triggering, the first application displays a device code through the first terminal so that the second terminal can read it. The device code is obtained by the first application through the following process: the first application obtains the identification information of the first terminal when triggered; and sends a device code request message including the identification information to a server; receives the device code sent by the server, the device code is generated by the server for the first terminal according to the device code request message; and displays the device code to the second terminal.

[0014] According to another aspect of the present application, a payment method is also provided, which is executed by a second terminal and includes: 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 the present application, a payment method is also provided, which may include: a first terminal triggering a first application of the first terminal; in response to the trigger, the first application and a server obtain a device code and display the device code to a second terminal through the following interaction with the server: the first application obtains identification information of the first terminal after being triggered; sends device code request information to the server, the device code request information includes the identification information; after receiving the device code request information, 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 includes 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 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, pulls up the payment application corresponding to the payment method in the first terminal to make payment based on the payment order; when the candidate payment method includes multiple payment methods supported by the first terminal, pulls up the payment application corresponding to the payment method selected from the multiple payment methods to make payment based on the payment order.

[0016] The payment method shown, optionally, the candidate payment method is determined by the server in one of the following ways: taking the payment method supported by the second terminal as the candidate payment method; selecting a payment method supported by both the second terminal and the first terminal as the candidate payment method.

[0017] The payment method shown, optionally, also includes: the first application also obtains application information after being triggered, the application information is 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 is sent to the server separately from the device code request information.

[0018] In the payment method shown, optionally, 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.

[0019] The payment method shown, optionally, also includes: the second terminal sending a payment method supported by the second terminal, or the server acquiring the payment method supported by the second terminal from pre-stored second-category terminal payment methods.

[0020] As shown in the payment method, optionally, the payment method supported by the first terminal is obtained by the server from pre-stored first-category terminal payment methods.

[0021] A program product is also provided, the program product comprising program instructions, which can implement any one of the above-mentioned payment methods when executed.

[0022] A storage medium is also provided, the storage medium including program instructions, which can implement any one of the above-mentioned payment methods when executed.

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

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

[0025] By adopting the examples according to the present application, the payer only needs to trigger the first application to make payment each time. In this process, the payer user does not need to look for the payment application supported by the merchant from the numerous applications of the first terminal when paying, but only needs to trigger the first application fixedly, which avoids misoperation in the process of finding the payment application and saves time; in 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 actively start the payment application to be paid in the first terminal, without the user having to select and start the payment application. In addition, the device code shown is not a direct payment code, which avoids the risks that may be caused by unauthorized scanning. It can be seen that the use of any one of the examples according to the present application greatly improves the convenience of payment. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0028] Figure 3 is a structural diagram of a payment system according to an example of the present application;

[0029] Figure 4 is a flow chart of a payment method according to some embodiments of the present application;

[0030] Figure 5 is a flow chart of a payment method according to some other embodiments of the present application;

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

[0032] Figure 6 is a flow chart of a payment method according to some other embodiments of the present application;

[0033] Figure 7 is a flow chart of a payment method according to an embodiment of the present application;

[0034] Figure 8 It is an illustration of the payment process according to some specific examples of this application. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the following will be combined with the accompanying drawings to clearly and completely describe the implementation methods of the present application. It should be noted that the described implementation methods are only part of the implementation methods of the technical solution of the present application and not all of them. All other implementation methods obtained by ordinary technicians in this field based on the implementation methods recorded in the application documents without paying creative work are covered by the protection scope of the present application.

[0036] Figure 1 and Figure 2 The two payment processes under the existing payment architecture are illustrated respectively, among which: Figure 1 The user is a merchant who scans the QR code to pay. Figure 2 It is the payee user scanning the merchant's QR code. The former is referred to as the scanned transaction process, and the latter is referred to as the main scanning transaction process.

[0037] Figure 1 In the scanned transaction process shown, the merchant's staff enters the receivable amount in the merchant's payment management system and clicks to collect payment, where the payment management system is referred to as the merchant MIS. The payment management system calls the scanning device to scan the payment QR code provided by the payer. When paying, the payer looks for the payment application used by the merchant on his electronic device such as a mobile phone, that is, the payment APP, opens the payment application and clicks on the payment code. When the payer clicks on the payment code, the payment application applies for the payment code from the payment background, and after obtaining the payment code issued by the payment background, the payer can successfully present the QR code to the payee. The merchant's scanning device scans the code and initiates a payment request to the QR code payment platform through the obtained payment code, and obtains the payment result. Thus, the payment is completed.

[0038] Figure 2 In the main scanning transaction process shown, when paying, the payer searches for the payment application used by the merchant on his electronic device such as a mobile phone, opens the application and clicks Scan to Pay, thereby obtaining the QR code provided by the merchant to obtain the merchant ID. The payer enters the payment amount, clicks Pay, composes a QR code payment message, and sends the message to the QR code payment backend. The QR code payment backend processes the payment accordingly and returns the payment result to the payer's payment application. At this time, the QR code payer also sends the payment result to the merchant. Thus, the payment is completed.

[0039] Whether Figure 1 The payment method is still Figure 2 For the main scanning payment method, users as payers must pay according to the payment application supported by the merchant. When there are many applications (also called application programs, APPs) on the user's mobile phone, the user has to find the payment application supported by the merchant from among the many applications, which is time-consuming and labor-intensive, and the user experience is not good.

[0040] The following will describe the payment system, payment method, etc. according to the example of this application in conjunction with the accompanying drawings. In short, according to this application, a device code is generated for the payment terminal used by the payer for payment. In the subsequent payment process, the payer does not need to find a specific payment application in the payment terminal, but only needs to show the device code to the payee such as the merchant. Compared with the existing payment process, the payer user does not need to consider which payment application the payee supports, and does not need to find the payment application supported by the payee from the many payment applications of the payment terminal to make payment, which saves the payer user's time and energy and provides a good payment experience.

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

[0042] The first terminal is a payment terminal used by the payee user, which can be any one of a mobile phone, a tablet, a wearable device such as a smart watch, a laptop, and a computer. The second terminal is a terminal used by the payee such as a merchant, which can be any one of a computer, a tablet, a smart phone, and a wearable device. In addition, the second terminal may include an image reading device such as a camera; or the second terminal includes a code scanning device or a code scanning component or a code scanning module. The server is not necessarily a single device, it can include multiple electronic devices or the server is a cloud device. Here, the electronic device can be a mobile phone, a tablet, a wearable device such as a smart watch, a laptop, a computer, etc.

[0043] Figure 3 is a structural diagram of a payment system according to an example of this application. 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 set in the first terminal 3, the second application 40 is set in the second terminal 4, and the management application 50 is set in the server 5. As an example, the first application, the second application and the third application can be implemented as software modules through program instructions respectively, so as to be set in the first terminal, the second terminal and the server; or, the first application, the second application and the third application can be implemented as modules by combining software and hardware, so as to be set in the first terminal, the second terminal and the server. This application does not limit the specific implementation of the first application, the second application and the third application.

[0044] When the payer wants to pay, the first application 30 sends a device code request message to the management application 50, in order to obtain the device code. The device code request message includes at least the identification information of the first terminal 3, so that the server that obtains the device code request message can confirm the identity of the first terminal 3. After receiving the request, the management application 50 generates a device code for the first terminal 3 according to the information carried in the request, and sends the generated device code to the first terminal 3. After the first terminal 3 receives the device code, the first application 30 displays it through the first terminal 3 so that the second terminal 4 can read the device code. After the second terminal 4 reads the device code, the second application 40 generates a transaction message, and the transaction message includes a payment order and a 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 the candidate payment method. Subsequently, the management application module 50 sends the candidate payment method and the payment order to the first terminal 3 through the server. After the first terminal 3 receives the candidate payment method and the payment order, the first application 30 immediately launches a payment application based on the candidate payment method to make payment based on the payment order. The first application 30 actively launches the payment application corresponding to the payment method, so that the payee user does not need to manually launch the payment application, which greatly improves the convenience of payment.

[0045] In some examples, the payment application pulled up is the only payment method specified by the candidate payment method, such as Cloud QuickPass. In other examples, the payment application pulled up is selected from multiple candidate payment methods, for example, the candidate payment methods include Cloud QuickPass and WeChat Pay, and the payment application pulled up is a payment application corresponding to one of the two payment methods. In the case where the candidate payment method includes multiple payment methods, according to the example of this application, multiple payment methods can be shown to the user through the first terminal, and the user can select from them. As an alternative, the priority order of the payment method has been preset in the first terminal 3, so that the payment method with the highest priority among the multiple payment methods in the candidate payment method is used as the payment method to be pulled up. In this application, the term pull up may include starting the selected payment application to make it work as if it is selected by the customer to make a payment. In addition, if the first terminal 3 is in a non-screen state when receiving the candidate payment method and the payment order, in this example, the first application 30 also prompts the first terminal 3 to light up the 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 through the first terminal 3, and displays the device code through the first terminal 3, for example, by displaying the device code on the display 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 be software modules, such as application programs implemented in a programming language, respectively, and are installed in the first terminal 3, the second terminal 4, and the server 5. The first application 30 is run by the first terminal 4. When data needs to be processed, the first application module and the processor of the first terminal 3 work together to process data. When communication is required, the first application 30 communicates through the communication interface of the first terminal 3. When display is required, the display is displayed 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 some more specific examples, the management application 50 may include different sub-application modules and be run by different systems or different devices on the server side. For example, the management application 50 includes a payment processing module and a device management module. The payment processing module is used to process payment matters according to the payment order and the device code information, and the device management module is used to generate and send the device code. The payment management module is, for example, a fusion management module that manages multiple payment systems (each payment system corresponds to its own payment platform and provides a payment application for the payment system), such as managing multiple payment applications such as Cloud QuickPass, Payment Package, and WeChat. The device management module and the payment management module can be set in one electronic device, or they can be set separately in different electronic devices. Similarly, the second application 40 can also be executed by multiple devices, for example, a part is executed by a computer, a part is executed by a scanning device, etc.

[0049] In another example, the first application 30, the second application 40, and the management application 50 may be modules implemented by software combined with hardware, and are respectively set in different devices, such as the first terminal 3, the second terminal 4, and the server 5. For example, a module implemented by a programming language combined with a processor. As an alternative, the first application module 30, the second application module 40, and the management application module 50 may be partially implemented by software as an application program, and partially implemented by software and hardware. This application does not limit the implementation of the first application 30, the second application 40, and the management application 50, as long as the functions described herein can be achieved.

[0050] According to the examples of the present application, the management application 50 may determine the candidate payment methods in different ways, as illustrated below. In the first example, the payment methods supported by the second terminal 4 are used as candidate payment methods. In the second example, the payment methods supported by both the second terminal 4 and the first terminal 3 are used as candidate payment methods. For the second example, more specifically, in the case where 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 the multiple candidate payment methods together as candidate payment methods to the first terminal 3; or alternatively, the management application 50 may select one of the 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 example, the second application module 40 includes the payment methods supported by the second terminal 4 in the transaction message. In this way, the transaction message includes the payment order, the device code, and the payment methods supported by the terminal 4. Alternatively, the second application 40 may also send the transaction message and the supported payment methods separately. In this article, the "payment order" at least includes the information of the payee, such as the merchant ID, etc. In the case where the payee is a merchant, the payment order is a merchant order.

[0052] In the case where the second application 40 does not send the supported payment methods, the management application 50 searches for the payment methods supported by the second terminal 4 from the pre-stored second-type terminal payment methods after receiving the transaction message at the server 5. Here, the second-type terminal refers to the terminal of the payee, such as a merchant terminal, which may include payment methods supported by multiple second terminals supported by the server 5. The second-type terminal payment methods pre-configured at the server 5 are updateable, that is, they can be added, deleted or modified. It should be understood that the update may require verification to ensure the security of the update.

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

[0054] According to the examples of the present application, after the first application 30 is triggered, it immediately obtains the payment method supported by the terminal 3 from the first terminal 3 and uses it as application information. The application information can be included in the device code request information, or as an alternative, sent separately to the server. The device identifier of the first terminal 3 can be any information that can uniquely identify the identity of the first terminal 3, such as the device ID. According to some examples of the present application, the first application 30 also obtains the network IP information of the first terminal 3, such as the IP address, after being triggered, and sends it to the server 5. The IP information can, for example, be included in the device code request information sent to the management application.

[0055] In another example, that is, when the payment methods supported by the first terminal 3 are not sent to the server 5, in some examples, after receiving the device code request, the management application module 50 searches for the payment application supported by the terminal 3 from the pre-stored first-type terminal payment methods according to the device identifier of the first terminal 3 in the request. Here, the first-type terminal refers to the payer terminal, which may include payment methods supported by multiple first terminals supported by the server 5. In another example, the management application 50 may inquire the first terminal 3 or the first terminal 3 may autonomously 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 the device code. Further, after determining the candidate payment method, the management application 50 sends the payment order and the candidate payment method 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 the management application 50 parses the transaction message to obtain the device code, it can determine which terminal is the first terminal to be paid. In the example of the present application, the management application 50 has built-in information that can represent the request for the device code in the generated device code during the process of generating the device code, such as the representation of the device code. For example, when the management application 50 generates a device code for the first terminal 3, the identification information of the first terminal 3 is built into the device code. Other methods that can associate the device code with the terminal requesting it are also possible, and are not limited to those introduced here.

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

[0058] In other cases, the first application 30 may also be configured to directly launch the payment application for payment when it is determined that only one payment application installed on the first terminal 3 can match the candidate payment method, without considering user selection or priority, etc.

[0059] When the management application 50 selects the same payment method from the payment methods supported by the second terminal 4 and the payment methods supported by the first terminal 3, that is, the payment method supported by both, the management application 50 uses the payment method supported by both the second terminal 4 and the first terminal 3 as a candidate payment method. After receiving the candidate payment method, if the first terminal 3 includes only one payment method, the first application module 30 directly pulls up the payment application corresponding to the payment method in the first terminal 3 to make payment; otherwise, if it includes multiple payment methods, the first application module 30 makes payment according to the payment application selected by the payer user from the payment applications corresponding to the multiple payment methods or selects according to a preset priority order.

[0060] In each example of the present application, by way of example and not limitation, the second application may generate a transaction message according to the scanned transaction process. In addition, the device code may be generated by the first terminal applying to the server for each payment transaction and generated by the server, so that the payment process is more secure by dynamically generating the device code. However, as an alternative, it may be more convenient to generate a device code for the first terminal and use it as a long-term device code without dynamically generating it each time a payment transaction is made; however, in this example, the long-term use may be a preset period of time, such as 2 months, and the device code is updated after the preset period of time.

[0061] Adopt a combination Figure 3 In the payment system, the payer only needs to trigger the first application each time when making a payment. In response, the first application will immediately apply for a device code from the server and display it to the payee after receiving the device code for subsequent payment operations. In this process, the user does not need to look for a payment application supported by the merchant from among the numerous applications of the first terminal such as a mobile phone when making a payment. Instead, the user only needs to trigger the first application fixedly, which avoids misoperation in the process of searching for the payment application and saves time. In addition, the device code shown is not a direct payment code, which avoids the risks that may be caused by stealing. Furthermore, because in 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 actively start the payment application to be paid in the first terminal without the user having to select and start the payment application. This payment method that does not require the user to worry about greatly improves the convenience of payment and increases user stickiness.

[0062] Figure 4 is a flow chart of a payment method according to some embodiments of the present application. Figure 4As shown, in step S400, a device code request message sent by a first terminal is received. The device code request message is generated when a first application of a first terminal (i.e., a payee 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. After receiving the device code, the first terminal displays the device code. As an example, the device code may include 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 indicate the first terminal corresponding to the device code can also be built into the device code. In step S404, a transaction message sent by a second terminal (i.e., a payee terminal) is received. The transaction message is generated after the second terminal reads the device code, and 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 method supported by the second terminal is used as a candidate payment method. In some 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 the payment order are sent to the first terminal based on the device code, so that after the first terminal receives the candidate payment method, the first application of the first terminal launches a payment application in the first terminal to make payment based on the payment order.

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

[0064] In some examples, the second terminal 4 sends information including the payment methods it supports, and the server 5 receives the information. For example, the payment method of the second terminal is included in the transaction message; or, the second terminal 4 sends information including the payment methods supported by the second terminal to the server 5 in addition to the transaction message. In other examples, the server 5 obtains the payment methods supported by the second terminal 4 from the pre-stored second-type terminal payment methods.

[0065] In some examples, the first terminal 3 sends information containing the payment methods it supports to the server. For example, the payment method of the first terminal 3 is included in the device code request information, or the first terminal 3 sends information containing the payment methods supported by the first terminal in addition to the device code request information. In other examples, the server obtains the payment methods supported by the first terminal from the pre-stored first-category terminal payment methods. In addition, the first terminal 3 may also send its IP information to the server, and the IP information may be included in the device request information or sent separately. As an example, before sending the payment order and the candidate payment methods, the server 5 may determine its communication channel with the first terminal 3 based on the IP information. This is only an example and not a limitation. It should be understood that in the case where the first terminal 3 does not send the IP information to the server, the server 5 may also determine the first terminal 3 in the network based on the identifier of the first terminal 3, and communicate through the communication method that already exists between the two.

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

[0067] Figure 4 The method shown in Figure 3 When the server 5 shown in FIG. 1 is executed, the first terminal in the execution process and the second terminal in the execution process can be Figure 3 The first terminal 3 and the second terminal 4 in the server 5 execute according to Figure 4 The payment method shown above can be combined Figure 3 The functions of the server 5 in the example described. As an example, Figure 4 The method shown can be implemented as an application program by program instructions, and then loaded into the server 5 so that the server 5 can implement the combination when executing the program instructions. Figure 4 The process of the method described.

[0068] Figure 5 It is a flowchart of a payment method according to some other embodiments of the present application. The method is executed by a first terminal as a payment terminal and the first terminal includes a first application. In step S500, the first application is triggered. In each example of the present 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 the functions performed by the first application described herein are added to the existing application. The first application may be triggered by the screen of the first terminal; or by voice triggering; or by the payer terminal (such as the second terminal) of the payee, for example, the payer terminal is close to the first terminal, etc. In step S502, in response to the trigger, the first application displays the device code through the first terminal for the second terminal to read.

[0069] Figure 5aSchematic diagram of the process of the first application obtaining 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, a device code request message including the identification information is sent to the server. In step S5025, a device code sent by the server is received, and the device code is generated by the server for the first terminal according to the device code request message. In step S5027, the device code is shown.

[0070] In some examples, after being triggered, the first application immediately obtains information about payment methods supported by the first terminal as application information. The application information may be included in the device code request information and sent to the server, or may be sent separately to the server. In some examples, after 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 may be sent separately to the server.

[0071] Back to Figure 5 , the method also includes step S504, receiving the candidate payment method and payment order sent by the service end. In step S506, the first application performs the first or second of the following operations when the first terminal receives the candidate payment method. The first operation includes, when the candidate payment method includes only one payment method supported by the first terminal, pulling up the payment application corresponding to the payment method in the first terminal to make payment based on the payment order. The second operation includes, when the candidate payment method includes multiple payment methods supported by the first terminal, pulling up the payment application corresponding to the payment method selected from the multiple payment methods to make 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 in the candidate payment method in the priority order is selected as the payment method. Alternatively, the payment method can be selected by the user by showing it to the user through the first terminal.

[0072] Figure 5 The method shown can be combined with Figure 3 The first terminal 3 and the first application 30 described above are executed. Figure 3 Each of the examples described with respect to the first terminal 3 and the first application 30 may be implemented by a payment method executed by the first terminal according to an example of the present application.

[0073] Figure 6 is a flow chart of a payment method according to some other embodiments of the present application. The method is executed by a second terminal as a terminal of the payee, for example Figure 3The second terminal 4 described in . In step S600, the second terminal reads the device code shown by the first terminal. In step S602, a transaction message is generated after reading the device code, and the transaction message includes a payment order and the device code. In step S604, a transaction message is sent to the server. As an example, the second terminal may send information containing payment methods supported by the second terminal to the server, and the information may be included in the transaction message or sent separately to the server. According to the example of the present application, when the second terminal generates a transaction message in step S602, it may be generated according to the scanned transaction process. In this way, when executing this method, there is no need to make too many changes to the execution process of the second terminal. Figure 6 The method shown may be implemented by an instruction program as an application, for example, the second application is implemented by the second terminal. Figure 6 The method shown can be combined with Figure 3 The second terminal 4 and the second application 40 described above execute. Figure 3 Each of the examples described with respect to the second terminal 3 and the second application 30 can be implemented by the payment method executed by the second terminal according to the example of the present application.

[0074] Figure 7 is a flow chart of a payment method according to an embodiment of the present application. Figure 3 Payment system shown is implemented Figure 7The payment method shown is described. In step S700, the first application of the first terminal is triggered via the first terminal 3. In step S702, as a response to the triggering, the first application interacts with the server 5 through the following process to obtain the device code and show it to the second terminal 4: the first application 30 obtains the identification information of the first terminal 3 after being triggered; sends the device code request information to the server 5, and the device code request information includes the identification information; after receiving the device code request information, 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 device code shown and generates a transaction message, which includes a payment order and a 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 a device code, and as an example, the transaction message can be generated according to the scanned transaction process. The payment order is used to indicate the amount to be paid this time, the receiving account number and other information, and the device code is included in the payment information so that the server receiving the payment information can identify which terminal is the terminal for 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 the device code, and determines the candidate payment method. Here, the method of generating the candidate payment method described in combination with the examples above is applicable here and will not be repeated. In step S712, the server 5 sends the candidate payment method and the payment order obtained by parsing 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, pull up the payment application corresponding to the payment method in the first terminal so as to make payment based on the payment order; (2) when the candidate payment method includes multiple payment methods supported by the first terminal, pull up the payment application corresponding to the payment method selected from the multiple payment methods so as to make payment based on the payment order.

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

[0076] also, Figure 7In some examples of the method shown, the first application further obtains application information after being triggered, wherein the application information is used to indicate the payment applications supported by the first terminal; and includes the application information in the device code request information and sends it to the server, or sends the application information and the device code request information separately to the server.

[0077] Figure 7 In some other examples of the method shown, the device code request information may also include 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 other examples of the method, the second terminal may send the payment method supported by the second terminal, or the server may obtain the payment method supported by the second terminal from the pre-stored payment methods of the second type of terminal. In addition, the payment method supported by the first terminal may be obtained by the server from the pre-stored payment methods of the first type of terminal.

[0079] Combination of the above Figure 3 All examples described can be executed in Figure 7 The method shown is implemented in the process, that is, combining Figure 3 The steps and functions performed by the first terminal, the first application, the second terminal, the second application, the server and the management application described above can be performed by Figure 7 The method shown is implemented. I will not go into details one by one.

[0080] Figure 8 This is a payment process according to some specific examples of this application. In this payment process, the first terminal is the payee's mobile phone 3', the second terminal includes the merchant's computer 4a and the code scanning device 4b connected to the computer 4a, and the server includes a device management platform 5a. The application scenario of this example is that the user as the payee pays the merchant through his mobile phone 3'. Figure 8 In the example, the payment methods supported by the merchant include Alipay, UnionPay, WeChat Pay and other payment methods.

[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 the mobile phone 3'; the second application module 40 is set in the computer 4a, and more specifically, it can be combined with the payment management system MIS set in the computer 4a by the merchant. It should be understood that the payment management system MIS is the merchant's existing payment management system, as described in the previous text of this application. Figure 1 and Figure 2One of the systems used by the merchant described above; the management application module 50 is implemented on the device management platform 5a.

[0082] After the user purchases the product and intends to pay, the merchant staff enters the amount to be paid on the payment management system MIS of the merchant computer 4a and clicks (S801) to receive the payment. After clicking to receive the payment, the payment management system MIS of the computer 4a calls (S802) the code scanning device 4b. On the user side, because the user wants to pay, the user clicks the first application module 30 on his mobile phone 3', and the first application module 30 obtains (S803) the device and application information of the mobile phone from 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 information and sends (S804) 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 shows the device code received by the mobile phone 3' to the code scanning device 4b so that the code scanning device 4b can scan the code to obtain (S808) the device code. The code scanning device 4b sends (S809) the device code to the computer 4a. After receiving the device code, the payment management system MIS combined with the second application module 40 can assemble the device code and the payment order into a transaction message, and send the transaction message, for example, in the form of a QR code to (S810) the payment fusion module 7. The payment fusion module 7 extracts the merchant order and the device code from the message, and sends (S811) the name of the payment application supported by the merchant to the device management platform 5. After receiving the information sent by the platform 7, the device management platform 5 can determine that the payment terminal corresponding to the code is the mobile phone 3' based on the device code, and can communicate with the mobile phone 3' accordingly.

[0083] In this example, the device request sent by the mobile phone 3' at S804 has included the payment methods it supports. Therefore, after determining (S812) the mobile phone 3', the device management platform 5 can determine the payment methods supported by the mobile phone 3'. In this way, the device management platform 5 extracts (S813) the payment methods supported by both the merchant device 4a and the mobile phone 3' from the payment methods supported by the merchant and the payment methods supported by the mobile phone 3' to form candidate payment methods. The device management platform 5 sends (S814) the candidate payment methods and the payment order to the mobile phone 3'. The first application module 30 on the mobile phone 3' searches (S815) for the corresponding payment application on the mobile phone 3' according to the candidate payment methods. When there is only one corresponding payment application, the application is directly started (S816); or, when there are multiple corresponding payment applications, the payment application selected by the user is started (S818). For example, the corresponding payment applications include UnionPay and Alipay. If the user selects UnionPay from these two, UnionPay is started.

[0084] The activated payment application initiates a QR code payment to the corresponding QR code payment backend for payment processing (S820). In this specific example, for the QR code payment backend, the payment method between the merchant and the user is similar to the main scan payment, so the QR code payment backend only needs to process according to the main scan payment process without making any changes. After the payment is completed, the payment result will be sent to the MIS system of the merchant computer 4a to end the entire payment process.

[0085] In the above example, the payment integration module 7 is an independent module that interacts and communicates with the merchant MIS system. In actual applications, it can be integrated into the merchant MIS system. By way of example and not limitation, the payment integration module 7 can be set in the merchant computer 4a.

[0086] The present application also provides a program product, which includes program instructions, and when these program instructions are executed, any of the payment methods described above can be implemented. As an example, the program product can implement the above combination Figure 5 The method described above can be combined into the first terminal as a first application module. Figure 4 The method described above can be combined with the server as a management application module. Figure 6 The method described above can be combined with the second terminal as a second application module. Figure 7 When the method described is combined Figure 1 Payment system shown.

[0087] The present application also provides a storage medium, which includes program instructions, and when these program instructions are executed, any one of the payment methods described above can be implemented.

[0088] According to the examples of this application, a device code is used. In this way, no matter whether the merchant or other payee supports WeChat, Alipay, Cloud QuickPass or other unlisted payment applications, the payee user only needs to obtain and display the device code through the first application (module). If necessary, just select one from the payment methods provided by the first application, without having to search for the payment application required for payment in the terminal application, which greatly facilitates the payee user. Furthermore, according to the examples of this application, there is no need to display the payment code during the payment process, which effectively avoids the risk of the payment code being maliciously stolen and scanned, and improves security. From the perspective of merchants and other payees, according to the examples of this application, there is no need for the payee to make system improvements. It only needs to be able to read the device code and send the device code to the server. It is simple, friendly and easy to integrate into its existing payment management system.

[0089] In summary, according to the examples of this application, aggregate payment for multiple payment applications is realized without the need for the payer user to manually search for specific payment applications; and in the payment process, the transaction process of scanning the payer's payment code is converted into scanning the device code. The payment process is similar to the main scanning transaction, and is compatible with the existing payment management MIS transaction processes of merchants and other payees, while ensuring a good experience for both the payee and the payer.

[0090] The technical features in the various embodiments of the present application can be combined with each other to form new implementation methods without departing from the spirit of the present application and without conflicting with each other. Although the specific embodiments of the present application have been shown and described in detail to illustrate the principles of the present application, it should be understood that the present 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 is set on the first terminal, and is used to obtain the device identification of the first terminal and generate device code request information including the device identification 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 set in the second terminal is used to generate a transaction message after the second terminal reads the device code shown, and send the transaction message, wherein the transaction message includes a payment order and the device code; a management application, which is arranged at the server end, and is used to receive the device code request information, generate the device code according to the request information and send it to the first terminal, parse the transaction message received by the server end to obtain the payment order and the device code, determine a candidate payment method, and send the candidate payment method and the payment order to the first terminal; and Among them, 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, pull up 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, pull up 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 by one of the following methods: using the payment method supported by the second terminal as a candidate payment method; A payment method supported by both the second terminal and the first terminal is selected as a candidate payment method.

3. The payment system according to claim 2, characterized in that: The first application is further configured to obtain application information after being triggered, and include the application information in the device code request information and send it to the server, or 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 method supported by the second terminal in the transaction message, or to send the payment method supported by the second terminal and the transaction message separately to the server.

6. The payment system according to claim 2, characterized in that: The management application is configured to obtain the payment method supported by the second terminal from pre-stored second-category terminal payment methods.

7. The payment system according to claim 2, characterized in that: The management application is further configured to obtain a payment method supported by the first terminal from pre-stored first-category 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. A payment method, characterized in that: The method is executed by the server, and includes: receiving device code request information sent by a first terminal, wherein the device code request information is generated after a first application of the first terminal is triggered, and the device code request information at least includes 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 shows it to the second terminal; receiving a transaction message sent from the second terminal, wherein the transaction message is generated after the second terminal reads the device code, and includes a payment order and the device code; Parsing the transaction message to obtain the payment order and the device code; Identify 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 after the first terminal receives the candidate payment method, the first application of the first terminal launches a payment application in the first terminal to make payment based on the payment order.

10. The payment method according to claim 9, characterized in that: The candidate payment method is determined by the server in one of the following ways: using the payment method supported by the second terminal as a candidate payment method; A payment method supported by both the second terminal and the first terminal is selected as a candidate payment method.

11. The payment method according to claim 10, characterized in that: The method further comprises: Receiving application information and / or IP information sent by the first terminal; The application information and / or IP information is included in the device code request information, or the application information and / or IP information and the device code request information are sent to the server separately.

12. The payment method according to claim 10, characterized in that: The method further comprises: The payment method supported by the second terminal is received from the second terminal; or, the payment method supported by the second terminal is obtained by the service end from pre-stored payment methods of the second type of terminal.

13. The payment method according to claim 12, characterized in that: The method further comprises: The payment method supported by the first terminal is obtained from pre-stored first-category terminal payment methods.

14. A payment method, characterized in that: The method is performed by a first terminal, the first terminal includes a first application, and the method includes: triggering the first application; In response to the trigger, the first application displays a device code through the first terminal so as to be read by the second terminal, and the device code is obtained by the first application through the following process: The first application acquires identification information of the first terminal when being triggered; Sending a device code request message including the identification information to the server; receiving a device code sent by the server, wherein the device code is generated by the server for the first terminal according to the device code request information; The device code is shown to the second terminal.

15. The payment method according to claim 14, characterized in that: The method further comprises: After being triggered, the first application obtains application information indicating a 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 separately to the server.

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

17. The payment method according to any one of claims 14 to 15, characterized in that: The method further comprises: Receiving the candidate payment method and payment order sent by the server; When the first terminal receives the candidate payment method, the first application performs one of the following operations: When the candidate payment methods include only one payment method supported by the first terminal, launching a payment application corresponding to the payment method in the first terminal to make payment based on the payment order; In a case where the candidate payment methods include multiple payment methods supported by the first terminal, a payment application corresponding to a payment method selected from the multiple payment methods is launched to make payment based on the payment order.

18. The payment method according to claim 16, characterized in that: The selected payment method is selected by any one of the following methods: The payment method with the highest priority in the pre-set priority order; The first terminal is used to display the information to the user and the user selects the information.

19. A payment method, characterized in that: The method is performed by a second terminal, and the method includes: Reading a device code displayed by the first terminal; After reading the device code, a transaction message is generated, wherein the transaction message includes a payment order and the device code; The payment information and the device code are sent.

20. The method according to claim 19, characterized in that The transaction message is generated by the second terminal according to the scanned transaction process.

21. The payment method according to claim 19, characterized in that: The method further includes: sending information including payment methods supported by the second terminal to the service end, wherein the information is included in the transaction message or sent by the second terminal separately from the transaction message.

22. A payment method, characterized in that: The method comprises: The first terminal triggers a first application of the first terminal; In response to the trigger, the first application and the server obtain the device code through the following interaction with the server and display the device code to the second terminal: The first application obtains the identification information of the first terminal after being triggered; Sending device code request information to the server, wherein the device code request information includes the identification information; After receiving the device code request information, the server generates a device code for the first terminal; sending the device code to the first terminal; and The second terminal reads the device code shown and generates a transaction message, wherein the transaction message includes 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 service end 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 After the first terminal receives the candidate payment method, the first application performs one of the following operations: When the candidate payment methods include only one payment method supported by the first terminal, launching a payment application corresponding to the payment method in the first terminal to make payment based on the payment order; In a case where the candidate payment methods include multiple payment methods supported by the first terminal, a payment application corresponding to a payment method selected from the multiple payment methods is launched to make payment based on the payment order.

23. The payment method according to claim 22, characterized in that: The candidate payment method is determined by the server in one of the following ways: using the payment method supported by the second terminal as a candidate payment method; A payment method supported by both the second terminal and the first terminal is selected as a candidate payment method.

24. The payment method according to claim 23, characterized in that: The method further comprises: After being triggered, the first application further acquires application information, where the application information is used to indicate a 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 separately to the server.

25. The payment method according to claim 22, 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.

26. The payment method according to claim 23, characterized in that: The method further includes: the second terminal sending the payment method supported by the second terminal, or the service end acquiring the payment method supported by the second terminal from pre-stored payment methods of the second type of terminal.

27. The payment method according to claim 23, characterized in that: The payment method supported by the first terminal is acquired by the server from pre-stored payment methods of the first type of terminals.

28. A program product, characterized in that The program product comprises program instructions, which can implement the payment method according to any one of claims 9 to 27 when executed.

29. A non-transitory storage medium, characterized in that: The storage medium includes program instructions, which can implement the payment method according to any one of claims 9 to 27 when executed.

30. The system according to any one of claims 1 to 8, the payment method according to any one of claims 9 to 27, wherein: The device code: The first application of the first terminal requests the server for each payment operation and is generated by the server; or The first application of the first terminal requests the server and the server generates the request so that the first terminal can use the request within a preset time period.

Images