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

Abstract

The present application provides a payment system, comprising: a first application module provided on a first terminal, the first application module being used for sending device code request information during payment so as to acquire a device code, and showing the acquired device code, and the device code request information at least comprising identification information used for identifying the first terminal; a second application module provided on a second terminal, the second application module reading the device code, generating payment information on the basis of the read information, and sending the payment information for payment, and the payment information comprising a payment order and the device code; and a management application module provided at a server, the management application module being used for receiving the device code request information, generating the device code on the basis of the request information, sending the device code to the first application, receiving the payment information sent by the second application module, determining a candidate payment mode, and sending the candidate payment mode and the payment order to the first application, wherein the first application module performs payment on the basis of the candidate payment mode and the payment order. Also provided are a payment method, a program product, etc.

Description

Payment system, payment method, storage medium and program product

[0001] Cross-reference to Related Applications

[0002] This application claims priority to the Chinese patent application No. 202411385844.2, filed on September 29, 2024, entitled “Payment system, payment method, storage medium and program product”, the entire content of which is incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to data processing, and more particularly, to payment technology based on device code. BACKGROUND

[0004] In daily two-dimensional code payment, according to different payment methods of merchants, the payer needs to find the corresponding payment application (APP) to make payment. The whole process is relatively cumbersome, and also cannot prevent the risk of malicious theft of payment code.

[0005] It is necessary to propose an improved payment method. SUMMARY

[0006] According to one aspect of the present application, a payment system is provided to at least solve at least one of the above problems. The payment system comprises: a first application provided in a first terminal, configured to, when 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 acquire a device code, and show the acquired device code; a second application provided in a second terminal, configured to generate a transaction message after the second terminal reads the shown device code, send the transaction message, the transaction message including a payment order and the device code; a management application provided in a server, configured 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 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 the first application is configured to, after the first terminal receives the candidate payment method: in the case where the candidate payment method only includes 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, in the case where 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.

[0007] In the payment system as shown, optionally, the management application is configured to determine the candidate payment method by one of the following ways: taking the payment method supported by the second terminal as the candidate payment method; and selecting the payment method supported by both the second terminal and the first terminal as the candidate payment method.

[0008] In the payment system as shown, optionally, the first application is further configured to acquire application information after being triggered, and send the application information to the server together with the device code request information, or send the application information to the server separately from the device code request information; wherein the application information is used to indicate the payment application supported by the first terminal.

[0009] In the payment system as shown, optionally, the device code request information further comprises 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 of the second terminal.

[0010] In the payment system as shown, optionally, the second application is further configured to include the payment method supported by the second terminal in the transaction message, or send the payment method supported by the second terminal to the server separately from the transaction message.

[0011] In the payment system as shown, optionally, the management application is configured to acquire the payment method supported by the second terminal from the pre-stored payment method of the second terminal.

[0012] In the payment system as shown, optionally, the management application is further configured to acquire the payment method supported by the first terminal from the pre-stored payment method of the first terminal.

[0013] In the payment system as shown, optionally, the second application generates the transaction message according to a scanned transaction process.

[0014] According to another aspect of the present application, a payment method is also provided, which is performed by a server, and the method comprises: 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 comprises identification information used 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 as to be shown to a second terminal by the first terminal; receiving a transaction message sent by the second terminal, wherein the transaction message is generated after the second terminal reads the device code, and the transaction message comprises 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 based on the device code to the first terminal, so that the first application of the first terminal pulls up a payment application in the first terminal to perform payment based on the payment order after the first terminal receives the candidate payment method.

[0015] According to still another aspect of the present application, a payment method is also provided, which is performed by a first terminal, and the method comprises: triggering the first application; and showing a device code by the first terminal in response to the triggering so as to be read by a second terminal. 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; and sends device code request information comprising the identification information to a server; receives 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; and shows the device code to the second terminal.

[0016] According to another aspect of the present application, a payment method is also provided, which is performed by a second terminal, and the method comprises: reading a device code shown by a first terminal; generating a transaction message after reading the device code, wherein the transaction message comprises a payment order and the device code; and sending the payment information and the device code.

[0017] According to another aspect of the present application, a payment method is also provided, which can include: triggering, by a first terminal, a first application of the first terminal; in response to the triggering, the first application acquires a device code and shows the device code to a second terminal by interacting with a server as follows: the first application acquires identification information of the first terminal after being triggered; sends device code request information to the server, the device code request information including 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 shown device code 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 a candidate payment method, and sends the candidate payment method and the payment order based on the device code to the first terminal; and the first application performs one of the following operations after the first terminal receives the candidate payment method: in the case where 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 pulled up to make payment based on the payment order; in the case where the candidate payment method includes multiple payment methods supported by the first terminal, the payment application corresponding to the selected payment method from the multiple payment methods is pulled up to make payment based on the payment order.

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

[0019] In the payment method, optionally, the method further includes: the first application also acquires application information after being triggered, the application information being used to indicate the payment applications 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.

[0020] In the payment method, optionally, the device code request information further includes IP information of the first terminal, so that the server establishes a communication channel with the first terminal through the IP information after receiving the transaction message of the second terminal.

[0021] The payment method shown, optionally, further comprises: sending, by the second terminal, the payment method supported by the second terminal, or obtaining, by the server, the payment method supported by the second terminal from the pre-stored payment method of the second terminal.

[0022] The payment method shown, optionally, the payment method supported by the first terminal is obtained by the server from the pre-stored payment method of the first terminal.

[0023] Further provided is a program product comprising program instructions which, when executed, can implement any of the payment methods described above.

[0024] Further provided is a storage medium comprising program instructions which, when executed, can implement any of the payment methods described above.

[0025] In each of the above examples, the first terminal is, for example, a payment terminal, and the second terminal is, for example, a payee terminal.

[0026] In each of the above examples, the device code is: requested by the first application of the first terminal from the server at 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 as to be used by the first terminal within a preset time length.

[0027] With each example according to the present application, the payer only needs to trigger the first application at each payment to make the payment. In this process, the payer user does not need to find the payment application supported by the merchant from the numerous applications of the first terminal when the payment is to be made, but only needs to trigger the first application fixedly, avoiding the misoperation in the process of finding the payment application and saving time in particular; in the payment process, after the management application sends the payment order and the candidate payment method to the first terminal, the first application will immediately and actively start the payment application in the first terminal to be paid, without the user to select and start the payment application. In addition, the device code shown is not a direct payment code, avoiding the risk that may be caused by the theft scanning. It can be seen that, with any one of the examples according to the present application, the convenience of payment is greatly improved. BRIEF DESCRIPTION OF DRAWINGS

[0028] The present application will be more fully understood from the following detailed description taken in conjunction with the accompanying drawings, in which like references refer to like elements, and in which:

[0029] Fig. 1 and Fig. 2 respectively show two payment processes under the existing payment architecture;

[0030] Fig. 3 is a structural diagram of a payment system according to an example of the present application;

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

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

[0033] Figure 5a is a process diagram of a first application obtaining a device code;

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

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

[0036] Figure 8 is a process diagram of a payment according to some specific examples of the present application. DETAILED DESCRIPTION

[0037] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the following will describe the embodiments of the present application clearly and completely with reference to the accompanying drawings. It should be noted that the described embodiments are only some of the embodiments of the technical solutions of the present application but not all. All other embodiments obtained by those of ordinary skill in the art based on the embodiments described in the present application file without any creative labor are covered by the protection scope of the present application.

[0038] Figures 1 and 2 respectively illustrate two payment processes under the existing payment architecture, wherein Figure 1 is a process in which a merchant scans a payer user and Figure 2 is a process in which a payer user scans a merchant's two-dimensional code, the former is simply referred to as a being-scanned transaction process and the latter is simply referred to as a main-scanning transaction process.

[0039] In the being-scanned transaction process shown in Figure 1, a staff of a merchant inputs an amount to be received in a payment management system of the merchant, clicks to collect money, wherein the payment management system is simply referred to as merchant MIS. The payment management system calls a scanning device to scan a payment two-dimensional code provided by a payer. When paying, the payer looks for a payment application, i.e. payment APP, used by the merchant on an electronic device such as a mobile phone, opens the payment application and clicks to pay a code. When the payer clicks to pay the code, the payment application applies to a payment background for a payment code, and after obtaining the payment code issued by the payment background, the payer can successfully present the two-dimensional code to the payee. The merchant scanning device scans the code and initiates a payment request to a two-dimensional code payment platform through the obtained payment code, and obtains a payment result. Thus, the payment is completed.

[0040] In the main scanning transaction flow shown in FIG. 2, the payer, when making a payment, looks for a payment application used by the merchant on an electronic device such as a mobile phone, opens the application and clicks to make a payment by scanning a code, thereby acquires a two-dimensional code provided by the merchant to obtain the merchant ID, inputs the payment amount, clicks to pay, forms a two-dimensional code payment message, and sends the message to the two-dimensional code payment background. The two-dimensional code payment background processes the payment accordingly and returns the payment result to the payment application of the payer. At this time, the two-dimensional code payment party also sends the payment result to the merchant. Thus, the payment is completed.

[0041] Regardless of the payment by scanning mode of FIG. 1 or the main scanning payment mode of FIG. 2, the user as the payer has to make a payment according to the payment application supported by the merchant. In the case where there are many applications (also known as 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 laborious and provides a poor user experience.

[0042] In the following, the payment system, payment method, etc. according to examples of the present application will be described with reference to the accompanying drawings. Briefly, according to the present application, a device code is generated for a payment terminal used by a payer to make a payment. In a 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 a merchant. Compared with the existing payment process, the payer user does not need to consider which payment application is supported by the payee, and does not need to find the payment application supported by the payee from among the many payment applications of the payment terminal to make a payment, thereby saving the time and effort of the payer user and providing a good payment experience.

[0043] In the following examples, the device code can be one of the following: a two-dimensional code, a bar code, and other information codes that can be recognized or read, by way of example but not limitation. In addition, other information codes that can be recognized or read and are not listed herein are also within the scope of the device code of the present application.

[0044] The first terminal is a payment terminal used by a payer user, which can be any one of a mobile phone, a tablet, a wearable device such as a smart watch, a notebook computer, and a computer. The second terminal is a terminal used by a 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 can 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 device, but can include multiple electronic devices or the server is a cloud device, where the electronic devices can be a mobile phone, a tablet, a wearable device such as a smart watch, a notebook computer, a computer, etc.

[0045] Fig. 3 is a structural diagram of a payment system according to an example of the present application. As shown in Fig. 3, the payment system includes a first application 30, a second application 40 and a management application 50. The first application 30 can be arranged in a first terminal 3, the second application 40 arranged in a second terminal 4, and the management application 50 arranged in a server 5. As an example, the first application, the second application and the third application can be implemented as software modules by program instructions, and thus arranged 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 a combination of software and hardware, and thus arranged in the first terminal, the second terminal and the server. The present application does not limit the specific implementation of the first application, the second application and the third application.

[0046] The first application 30 sends a device code request information to the management application 50 when the payer wants to make a payment, aiming to obtain a device code. The device code request information at least includes identification information of the first terminal 3, so that the server that obtains the device code request information 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, which 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 obtains 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 a 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 pulls up a payment application based on the candidate payment method to make a payment based on the payment order. The first application 30 actively pulls up the payment application corresponding to the payment method, so that the payer user does not need to manually start the payment application, greatly improving the convenience of payment.

[0047] In some examples, the payment application pulled up is the only payment method indicated by the candidate payment methods, for example, WeChat Pay. In other examples, the payment application pulled up is selected from a plurality of candidate payment methods, for example, the candidate payment methods include WeChat Pay and Alipay, and the payment application pulled up is one of the two payment applications. In the case where the candidate payment methods include a plurality of payment methods, according to examples of the present application, the plurality of payment methods can be all shown to the user through the first terminal, and the user can select one of them. Alternatively, the priority order of the payment methods is preset in the first terminal 3, so that the payment method at the top of the priority order among the plurality of candidate payment methods is pulled up. In the present application, the term "pull up" can include starting the selected payment application to work as if it is selected by the user to make payment. In addition, if the first terminal 3 is in an unlit state when it receives the candidate payment methods and the payment order, in this example, the first application 30 also causes the first terminal 3 to light up.

[0048] The first application 30, the second application 40 and the management application 50 communicate with each other through the devices in which they are located. Specifically, the first application 30 sends and receives information through the first terminal 3, displays the device code through the first terminal 3, for example, through 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.

[0049] As mentioned above, by way of example and not limitation, the first application 30, the second application 40 and the management application 50 can be software modules, for example, application programs implemented in a programming language, installed in the first terminal 3, the second terminal 4 and the server 5, respectively. The first application 30 is run by the first terminal 3, and when data needs to be processed, the first application and the processor of the first terminal 3 work together, when communication is needed, the first application 30 communicates through the communication interface of the first terminal 3, and when display is needed, the display screen of the first terminal 3 is used for display. Similarly, the second application 40 is run by the second terminal 4, and the management application 50 is run by the server 5.

[0050] In some more specific examples, the management application 50 can include different sub-application modules and be executed by different systems or different devices of the server. For example, the management application 50 includes a payment processing module for processing payment matters according to payment orders and device code information, and a device management module for generating and sending device codes. The payment management module is, for example, a fusion management module for managing a plurality of payment systems (each payment system corresponds to a payment platform and provides a payment application for the payment system), such as cloud flash payment, Alipay, WeChat, and the like. The device management module and the payment management module can be disposed in one electronic device, or can be disposed separately in different electronic devices. Similarly, the second application 40 can also be executed by a plurality of devices, such as a computer executing a part and a scanning device executing a part.

[0051] In another example, the first application 30, the second application 40, and the management application 50 can be modules implemented by software in combination with hardware, and are disposed in different devices, such as the first terminal 3, the second terminal 4, and the server 5. For example, the modules are implemented by a programming language in combination with a processor. Alternatively, the first application module 30, the second application module 40, and the management application module 50 can be partially implemented by software as an application program and partially implemented by software and hardware. The present application does not limit the implementation manner of the first application 30, the second application 40, and the management application 50, as long as the functions described herein can be achieved.

[0052] According to examples of the present application, the management application 50 can determine the candidate payment methods in different manners, which are illustrated below. In a first example, the payment methods supported by the second terminal 4 are taken as the candidate payment methods. In a second example, the payment methods supported by both the second terminal 4 and the first terminal 3 are taken as the candidate payment methods. For the second example, more specifically, in the case that the payment methods supported by both the second terminal 4 and the first terminal 3 include a plurality of candidate payment methods, the management application 50 can send the plurality of candidate payment methods together to the first terminal 3 as the candidate payment methods; or alternatively, the management application 50 can select one of the plurality of payment methods as the candidate payment method and send it to the first terminal 3.

[0053] 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 can send the transaction message and the supported payment methods separately. In this document, the "payment order" at least includes the information of the payee, such as a merchant ID. In the case that the payee is a merchant, the payment order is a merchant order.

[0054] 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 terminal payment methods upon receiving the transaction message at the server 5. Here, the second terminal refers to the payee terminal, such as a merchant terminal, which can include the payment methods supported by each of a plurality of second terminals supported by the server 5. The second terminal payment methods pre-configured at the server 5 are updatable, i.e., can be added, deleted or modified. It should be understood that the update can need to be verified to ensure the security of the update.

[0055] If the server 5 does not obtain the payment methods supported by the first terminal 3, the payment methods of the second terminal 4 determined according to at least one of the above examples can be taken as the candidate payment methods.

[0056] According to examples of the present application, the first application 30 obtains the payment methods supported by the first terminal 3 upon being triggered and sends the same as the application information. The application information can be included in the device code request information sent, or alternatively, sent to the server separately. The device identification of the first terminal 3 can be any information that can uniquely identify the identity of the first terminal 3, such as a device ID. According to some examples of the present application, the first application 30 also obtains the network IP information, such as the IP address, of the first terminal 3 upon being triggered and sends the same to the server 5. The IP information can be included in the device code request information sent to the management application, for example.

[0057] In another example, i.e., in the case where the payment methods supported by the first terminal 3 are not sent to the server 5, in some examples, the management application module 50 searches for the payment methods supported by the first terminal 3 from the pre-stored first terminal payment methods according to the device identification of the first terminal 3 in the device code request upon receiving the same. Here, the first terminal refers to the payer terminal, which can include the payment methods supported by each of a plurality of first terminals supported by the server 5. In another example, the management application 50 can inquire the first terminal 3 or the first terminal 3 can send information indicating the payment methods supported by the first terminal 3 after sending the device code request information.

[0058] 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, and further, the management application 50 sends the payment order and the candidate payment method to the first terminal 3 based on the device code after determining the candidate payment method. It should be understood that the device code is generated by the management application 50 for the first terminal 3, and thus, the management application 50 can determine the first terminal to be paid after parsing the transaction message to obtain the device code. In the example of the present application, the management application 50 has built the information indicating the request of the device code, such as the representation of the device code, in the generated device code in the process of generating the device code. For example, the management application 50 generates the device code for the first terminal 3, and builds the identification information of the first terminal 3 in the device code. Other ways of associating the device code with the terminal requesting it are also possible, and are not limited to the ones described herein.

[0059] After the first terminal 3 receives the candidate payment method and the payment order from the management application 50, the first application 30 initiates the payment application corresponding to the payment method in the first terminal 3 to perform the payment operation immediately, as described above, in the case of only one candidate payment method; or initiates the payment application corresponding to the selected payment method to perform the payment operation immediately in the case of multiple payment methods.

[0060] In another case, the first application 30 can also be configured to directly pull up the payment application to perform the payment in the case of only one payment application installed in the first terminal 3 matching the candidate payment method, without considering the user selection or the priority order, etc.

[0061] In the case that the management application 50 selects the same payment method supported by the second terminal 4 and the first terminal 3, i.e., the payment method supported by both the second terminal 4 and the first terminal 3, the management application 50 selects the payment method supported by both the second terminal 4 and the first terminal 3 as the candidate payment method. After the first terminal 3 receives the candidate payment method, if it only includes 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 perform the payment; otherwise, if it includes multiple payment methods, the first application module 30 performs the payment according to the payment application selected by the user of the payment party from the payment applications corresponding to the multiple payment methods or according to the preset priority order.

[0062] In the examples of the present application, the second application can generate the transaction message according to the transaction scanning process, by way of example but not limitation. In addition, the generation of the device code can be applied for by the first terminal to the server and generated by the server at each payment transaction, so that the dynamic generation of the device code makes the security level of the payment process higher. However, as an alternative, it can be more convenient to also generate a device code for the first terminal, which is used as a long-term device code without the need for dynamic generation at each payment transaction; but in this example, the long-term use can be a preset time period, for example, 2 months, and the device code is updated after the preset time period ends.

[0063] With the payment system described in conjunction with FIG. 3, the payer only needs to trigger the first application at each payment, in response to which the first application will immediately apply for a device code from the server and display it to the payee after receiving the device code, to perform subsequent payment operations. In this process, the user does not need to search for a payment application supported by the merchant from numerous applications of the first terminal such as a mobile phone when payment is to be made, but only needs to trigger the first application fixedly, avoiding misoperation in the process of searching for the payment application and saving time. In addition, the device code shown is not a direct payment code, avoiding the risk that may be caused by theft scanning. Further, because in this payment process, after the management application sends the payment order and the candidate payment method to the first terminal, the first application will immediately and actively start the payment application to be used for payment in the first terminal, without the need for the user to select and start the payment application, so that the user does not need to pay much attention to the payment method, greatly improving the convenience of payment and increasing user stickiness.

[0064] Figure 4 is a flow chart of a payment method according to some embodiments of the present application. As shown in Figure 4, in step S400, a device code request information sent by a first terminal is received. The device code request information is generated when a first application of the first terminal (i.e. a payment terminal) is triggered, and the device code request information at least includes identification information for identifying the first terminal. In step S402, a device code for the first terminal is generated according to the request information and sent to the first terminal. The first terminal shows the device code after receiving the device code. As an example, the device code can include the identification information of the first terminal so that the corresponding first terminal is determined according to the identification information in the device code in a subsequent payment operation. But this is only an example and not a limitation, and other information that can be used to indicate the corresponding first terminal of the device code can also be built in 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 methods supported by the second terminal are taken as the candidate payment methods. In some other examples, the payment methods supported by both the second terminal and the first terminal are selected as the candidate payment methods. In step S408, the candidate payment methods and the payment order based on the device code are sent to the first terminal, so that the first application of the first terminal pulls up a payment application in the first terminal to perform payment based on the payment order after the first terminal receives the candidate payment methods.

[0065] The method shown in Figure 4 can be performed by the server 5 and the management application 50 in the examples described above in connection with Figure 3. As for the determination of the candidate payment methods and the process of the first application pulling up the payment application, the examples described above in connection with Figure 3 are applicable, and for the sake of brevity, will not be repeated here.

[0066] In some examples, the second terminal 4 sends information including the payment methods supported by the second terminal to the server 5. For example, the payment methods of the second terminal are 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 some other examples, the server 5 obtains the payment methods supported by the second terminal 4 from the pre-stored second terminal payment methods.

[0067] In some examples, the first terminal 3 sends information of payment methods supported by the first terminal 3 to the server. For example, the payment methods supported by the first terminal 3 are included in the device code request information, or the first terminal 3 sends information of payment methods supported by the first terminal 3 separately from the device code request information. In other examples, the server obtains the payment methods supported by the first terminal 3 from pre-stored payment methods of the first terminal. In addition, the first terminal 3 can send its IP information to the server, which can be included in the device code request information or sent separately. As an example, the server 5 can determine the communication channel with the first terminal 3 according to the IP information before sending the payment order and the candidate payment methods. This is only an example and not a limitation, and it should be understood that the server 5 can also determine the first terminal 3 in the network according to the identification of the first terminal 3 without the first terminal 3 sending the IP information to the server 5, and communicate through the original communication channel between the two.

[0068] In the examples of the present application, the IP information can also be used as the identification information of the first terminal 3.

[0069] The method shown in FIG. 4 is executed by the server 5 shown in FIG. 3, and the first terminal in the execution process and the second terminal in the execution process can be the first terminal 3 and the second terminal 4 in FIG. 3, respectively. The server 5 can implement the functions of the server 5 in the examples described above in connection with FIG. 3 when executing the payment method according to FIG. 4. As an example, the method shown in FIG. 4 can be implemented by program instructions as an application program, so as to be loaded into the server 5 to implement the process of the method described in connection with FIG. 4 when the program instructions are executed.

[0070] FIG. 5 is a flowchart of a payment method according to some 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 the examples of the present application, the first application can be a new application installed on the first terminal, or alternatively, the first application can be an existing application in the first terminal, but the existing application is added with the functions performed by the first application described herein. The first application can be triggered by a screen of the first terminal; or triggered by voice; or triggered by a payment terminal (e.g. the second terminal) of a payee, for example, the payment terminal is close to the first terminal, etc. In step S502, in response to the trigger, the first application displays a device code through the first terminal for reading by the second terminal.

[0071] Figure 5a is a process diagram of a first application acquiring a device code. In step S5021, the first application acquires identification information of the first terminal immediately after being triggered. In step S5023, the first application sends device code request information including the identification information to the server. In step S5025, the first application receives a device code sent by the server, which is generated by the server for the first terminal according to the device code request information. In step S5027, the first application displays the device code.

[0072] In some examples, the first application acquires information of payment methods supported by the first terminal immediately after being triggered as application information. The application information can be included in the device code request information sent to the server, or can be sent to the server separately. In some examples, the first application acquires IP information of the first terminal immediately after being triggered, and sends the IP information to the server in the device code request information or separately.

[0073] Returning to Figure 5, the method further includes step S504 of receiving candidate payment methods and a payment order sent by the server. In step S506, the first application performs one of the first operation or the second operation when the first application receives the candidate payment methods in the first terminal. The first operation includes pulling up a payment application corresponding to a payment method supported by the first terminal to make a payment based on the payment order when the candidate payment methods include only one payment method supported by the first terminal. The second operation includes pulling up a payment application corresponding to a selected payment method from the payment methods supported by the first terminal to make a payment based on the payment order when the candidate payment methods include multiple payment methods supported by the first terminal. 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 priority order in the candidate payment methods is selected as the selected payment method. Alternatively, the user can be prompted by the first terminal to select a payment method.

[0074] The method shown in Figure 5 can be performed by the first terminal 3 and the first application 30 described in connection with Figure 3. Each example described above in connection with the first terminal 3 and the first application 30 can be implemented by the payment method performed by the first terminal according to the examples of the present application.

[0075] Figure 6 is a flow chart of a payment method according to yet some embodiments of the application. The method is performed by a second terminal as a payment receiver terminal, for example the second terminal 4 described in Figure 3. In step S600, the second terminal reads a device code shown by a first terminal. In step S602, a transaction message is generated after reading the device code, the transaction message comprising a payment order and the device code. In step S604, the transaction message is sent to a server. As an example, the second terminal can send information of payment methods supported by the second terminal to the server, which can be included in the transaction message or sent to the server separately. According to examples of the application, the second terminal can generate the transaction message in step S602 according to a swipe transaction process, so that no much change is needed to the execution process of the second terminal when performing the method. The method shown in Figure 6 can be implemented as an application by an instruction program, for example the second application implemented by the second terminal. The method shown in Figure 6 can be performed by the second terminal 4 and the second application 40 described in connection with Figure 3. Each example described above in connection with the second terminal 3 and the second application 30 can be implemented by the payment method performed by the second terminal according to examples of the application.

[0076] FIG. 7 is a flow chart of a payment method according to an embodiment of the present application. The payment method shown in FIG. 7 is executed by the payment system shown in FIG. 3. In step S700, a first application of the first terminal is triggered via the first terminal 3. In step S702, in response to the triggering, the first application interacts with the server 5 to obtain a device code and show it to the second terminal 4 by the following process: the first application 30 obtains the identification information of the first terminal 3 after being triggered; sends a device code request information to the server 5, the device code request information including 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 shown device code and generates a transaction message including 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, 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, the 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 used to make 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 the device code, and determines the candidate payment method. Here, the above-described manner of generating the candidate payment method is applicable, and is not 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 is pulled up 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 selected payment method is pulled up to make payment based on the payment order.

[0077] As described above in conjunction with FIG. 3, the candidate payment method can be determined by the server 5 in one of the following ways: the payment method supported by the second terminal is used as the candidate payment method; the payment method supported by both the second terminal and the first terminal is selected as the candidate payment method. The specific process has been described above.

[0078] In some examples of the method shown in FIG. 7, the first application further acquires application information after being triggered, the application information indicating payment applications supported by the first terminal; and the application information is sent to the server in the device code request information, or the application information is sent to the server separately from the device code request information.

[0079] In some examples of the method shown in FIG. 7, the device code request information further includes IP information of the first terminal, so that the server establishes a communication channel with the first terminal through the IP information after receiving the transaction message of the second terminal.

[0080] In some examples of the method shown in FIG. 7, the method further includes sending, by the second terminal, payment methods supported by the second terminal, or acquiring, by the server, payment methods supported by the second terminal from pre-stored payment methods of the second terminal. In addition, payment methods supported by the first terminal are acquired by the server from pre-stored payment methods of the first terminal.

[0081] All examples described above in connection with FIG. 3 can be implemented in the process of performing the method shown in FIG. 7, that is, 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 in connection with FIG. 3 can be implemented by the method shown in FIG. 7. Therefore, no further description is given.

[0082] FIG. 8 is a payment process according to some specific examples of the present application, in which the first terminal is a mobile phone 3' of a payer, the second terminal includes a computer 4a of a merchant and a 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 a user as a payer supports a payment to a merchant as a payee through the mobile phone 3'. In the example of FIG. 8, payment methods supported by the merchant include Alipay, UnionPay, WeChat Pay and the like.

[0083] The system shown in FIG. 3 can be combined in the system architecture shown in FIG. 8, for example, the first application module 30 is arranged in the mobile phone 3'; the second application module 40 is arranged in the computer 4a, and more specifically, can be combined into a payment management system MIS arranged in the computer 4a of the merchant, it should be understood that the payment management system MIS is an existing payment management system of the merchant, just like one of the systems used by the merchant side described above in connection with FIG. 1 and FIG. 2; and the management application module 50 is implemented in the device management platform 5a.

[0084] After the user purchases the goods and intends to pay, the merchant staff inputs the amount to be paid on the payment management system MIS of the merchant computer 4a and clicks (S801) to collect the payment. After clicking to collect the payment, the payment management system MIS of the computer 4a calls (S802) the code scanning device 4b. On the user side, because the payment is to be made, the user clicks the first application module 30 on the 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', which in this example includes the mobile phone ID, the 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 device code request information 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) a device code to the mobile phone 3' according to the mobile phone ID. The user displays the device code received by the mobile phone 3' to the code scanning device 4b for the code scanning device 4b to scan and 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 (S810) the transaction message to the payment fusion module 7 in the form of a two-dimensional code, for example. 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 together to the device management platform 5. After receiving the information sent by the platform 7, the device management platform 5 can determine the payment terminal corresponding to the code as the mobile phone 3' according to the device code, and thus communicate with the mobile phone 3'. In this example, the mobile phone 3' has included the payment methods it supports in the device request sent at S804, so 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', forming 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' looks up (S815) the corresponding payment application on the mobile phone 3' according to the candidate payment methods, directly starts (S816) the application when there is only one corresponding payment application, or starts (S818) the payment application selected by the user when there are multiple corresponding payment applications, for example, the corresponding payment applications include Yunshenpay and Alipay, and the user selects Yunshenpay from the two, and then Yunshenpay is started.

[0085] The activated payment application initiates a QR code payment to the corresponding QR code payment background for payment processing (S820). In the present embodiment, the payment between the merchant and the user is similar to the master scan payment for the QR code payment background, and thus the QR code payment background only needs to process according to the master scan payment process without any change. After the payment is completed, the payment result is sent to the MIS system of the merchant computer 4a to end the entire payment process.

[0086] In the above embodiment, the payment fusion module 7 is a separate module that interacts with the merchant MIS system, and in actual application, it can be fused into the merchant MIS system. By way of example but not limitation, the payment fusion module 7 can be arranged in the merchant computer 4a.

[0087] The present application also provides a program product including program instructions that, when executed, can implement any of the payment methods described above. By way of example, the program product can be incorporated into the first terminal as a first application module when it can implement the method described above in conjunction with FIG. 5. The program product can be incorporated into the server as a management application module when it can implement the method described above in conjunction with FIG. 4. The program product can be incorporated into the second terminal as a second application module when it can implement the method described above in conjunction with FIG. 6. The program product can be incorporated into the payment system shown in FIG. 1 when it can implement the method described above in conjunction with FIG. 7.

[0088] The present application also provides a storage medium including program instructions that, when executed, can implement any of the payment methods described above.

[0089] According to the various examples of the present application, a device code is used, so that regardless of whether the payment recipient such as a merchant supports WeChat, Alipay, Yunshenfu or other payment applications not listed, the payment recipient user only needs to obtain and display the device code through the first application (module), and in the case of need, only selects one from the payment methods provided by the first application, without the need to find the payment application required for payment in the terminal application program, greatly facilitating the payment recipient user. Further, according to the various examples of the present application, the payment process does not require the display of the payment code, effectively avoiding the risk of malicious theft of the payment code and improving the security. From the perspective of the payment recipient such as a merchant, according to the various examples of the present application, the payment recipient only needs to be able to read the device code and send the device code to the server, which is simple, friendly and easy to incorporate into its existing payment management system.

[0090] In summary, according to the examples of the present application, the aggregated payment for multiple payment applications is realized without the need for the payer user to manually find a specific payment application, and in the payment process, the scanning of the payer payment code is converted into the scanning of the device code, the payment process is similar to the main scanning transaction, and the existing payment management MIS transaction process of the paid party such as the merchant is compatible, while ensuring the double good experience of the paid party and the payer.

[0091] The technical features in the embodiments of the present application can be combined with each other without departing from the spirit of the present application and without conflicting with each other, to form new embodiments. Although specific embodiments of the present application have been shown and described in detail to explain 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, comprising: a first application disposed at a first terminal, configured to, when 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 acquire a device code, and show the acquired device code; a second application disposed at a second terminal, configured to, after reading the shown device code at the second terminal, generate a transaction message including a payment order and the device code, and send the transaction message; a management application disposed at the 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 terminal, parse the transaction message received at the server 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 wherein the first application is configured to, after the first terminal receives the candidate payment method: in a case where the candidate payment method includes only one payment method supported by the first terminal, pull up a payment application corresponding to the payment method in the first terminal to perform payment based on the payment order; or in a case where the candidate payment method includes multiple payment methods supported by the first terminal, pull up a payment application corresponding to a selected payment method from the multiple payment methods to perform payment based on the payment order.

2. The payment system of claim 1, wherein, The management application is configured to determine the candidate payment method in one of the following ways: selecting, as the candidate payment method, a payment method supported by the second terminal; selecting, as the candidate payment method, a payment method supported by both the second terminal and the first terminal.

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

4. The payment system of claim 1, wherein, The device code request information further 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 of the second terminal.

5. The payment system of claim 2, wherein, The second application is further configured to include, in the transaction message, a payment method supported by the second terminal, or send the payment method supported by the second terminal to the server separately from the transaction message.

6. The payment system of claim 2, wherein, The management application is configured to acquire the payment method supported by the second terminal from pre-stored second-type-terminal payment methods.

7. The payment system of claim 2, wherein, The management application is further configured to acquire the payment method supported by the first terminal from pre-stored first-type-terminal payment methods.

8. The payment system of claim 1, wherein, The second application generates the transaction message according to a scanned transaction process. 9.A payment method, the method being performed by a server, the method comprising: 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 as to be shown to a second terminal by the first terminal; receiving a transaction message sent by the second terminal, wherein the transaction message is generated after the second terminal reads the device code, and the transaction message includes 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 the first application of the first terminal pulls up a payment application in the first terminal to make payment based on the payment order after the first terminal receives the candidate payment method.

10. The payment method of claim 9, wherein, The candidate payment method is determined by the server in one of the following ways: taking a 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.

11. The payment method of claim 10, wherein, The method further comprises: receiving application information and / or IP information sent by the first terminal; wherein the application information and / or IP information is included in the device code request information, or the application information and / or IP information is sent to the server separately from the device code request information.

12. The payment method of claim 10, wherein, The method further comprises: receiving a payment method supported by the second terminal sent by the second terminal, or obtaining the payment method supported by the second terminal from pre-stored payment methods of the second terminal.

13. The payment method of claim 12, wherein, The method further comprises: obtaining the payment method supported by the first terminal from pre-stored payment methods of the first terminal.

14. A method of payment, wherein, The method is performed by a first terminal including a first application, and the method comprises: triggering the first application; in response to the triggering, the first application shows a device code to be read by a second terminal through the first terminal, wherein the device code is obtained by the first application through the following process: the first application obtains identification information of the first terminal when triggered; sending device code request information including the identification information to a 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; showing the device code to the second terminal.

15. The payment method of claim 14, wherein, The method further comprises: the first application obtains application information indicating payment applications supported by the first terminal after being triggered; and sending the application information to the server in the device code request information, or sending the application information to the server separately from the device code request information.

16. The payment method of claim 15, wherein, The device code request information further includes IP information of the first terminal.

17. The payment method of any one of claims 14 to 15, wherein, The method further comprises: receiving a candidate payment method and a payment order sent by the server; The first application performs one of the following operations when the first terminal receives the candidate payment method: when the candidate payment method only includes one payment method supported by the first terminal, pulling up a payment application in the first terminal corresponding to the payment method to make payment based on the payment order; when the candidate payment method includes multiple payment methods supported by the first terminal, pulling up a payment application corresponding to a selected payment method from the multiple payment methods to make payment based on the payment order.

18. The payment method of claim 17, wherein, The selected payment method is selected by any one of the following methods: a payment method with the highest priority in a pre-set payment method priority order; selected by a user through a first terminal.

19. A method of payment, wherein, The method is performed by a second terminal, and the method comprises: reading a device code displayed by a first terminal; generating a transaction message after reading the device code, the transaction message comprising a payment order and the device code; sending the payment information and the device code.

20. The method of claim 19, wherein, The transaction message is generated by the second terminal according to a scanning transaction process.

21. The payment method of claim 19, wherein, The method further comprises sending information comprising payment methods supported by the second terminal to a server, wherein the information is included in the transaction message or sent separately from the transaction message by the second terminal.

22. A method of payment, wherein, The method comprises: triggering a first application of a first terminal by the first terminal; in response to the triggering, the first application acquires a device code and displays the device code to a second terminal through the following interaction with a server: the first application acquires identification information of the first terminal after being triggered; sends device code request information to the server, the device code request information comprising 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 comprising 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 based on the device code to the first terminal; and the first application performs one of the following operations after the first terminal receives the candidate payment method: when the candidate payment method only includes one payment method supported by the first terminal, pulling up a payment application in the first terminal corresponding to the payment method to make payment based on the payment order; when the candidate payment method includes multiple payment methods supported by the first terminal, pulling up a payment application corresponding to a selected payment method from the multiple payment methods to make payment based on the payment order 23. The payment method of claim 22, wherein, The candidate payment method is determined by the server through one of the following methods: taking payment methods supported by the second terminal as the candidate payment method; selecting, from the payment method supported by the second terminal and the payment method supported by the first terminal, a payment method supported by both as a candidate payment method.

24. The payment method of claim 23, wherein, The method further comprises: The first application further acquires application information after being triggered, the application information being used to indicate a payment application supported by the first terminal; and The application information is sent to the server in the device code request information, or the application information is sent to the server separately from the device code request information.

25. The method of claim 22, wherein, The device code request information further comprises IP information of the first terminal, so that the server establishes a communication channel with the first terminal through the IP information after receiving a transaction message of the second terminal.

26. The payment method of claim 23, wherein, The method further comprises: sending, by the second terminal, the payment method supported by the second terminal, or acquiring, by the server, the payment method supported by the second terminal from pre-stored payment methods of the second terminal.

27. The payment method of claim 23, wherein, The payment method supported by the first terminal is acquired by the server from pre-stored payment methods of the first terminal.

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

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

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: requested by a first application of the first terminal to the server at each payment operation, and generated by the server; or requested by a first application of the first terminal to the server and generated by the server, so as to be used by the first terminal within a preset time length.

Images