Code scanning payment method, user terminal, service device, system and medium

Abstract

The application discloses a code scanning payment method, a user terminal, a business device, a system and a medium, and belongs to the field of data processing. The method comprises the following steps: receiving a payment code request message, wherein the payment code request message comprises position information of a user terminal; acquiring payment waiting time factor information associated with the position information; in the case that the payment waiting time represented by the payment waiting time factor information associated with the position information is greater than or equal to a preset time threshold, sending a first payment code feedback message, wherein the first payment code feedback message comprises a first payment code and a second payment code, the user terminal displays the first payment code before sensing a trigger signal of a payment receiving terminal, and switches the displayed first payment code to the second payment code in the case that the trigger signal is sensed; and if the payment request message comprises first information, indicating that the payment amount is deducted from the payer account indicated by the information of the second payment code. According to the embodiment of the application, the security of the code scanning payment can be improved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of data processing, and particularly relates to a code scanning payment method, a user terminal, a business device, a system and a medium. BACKGROUND

[0002] With the continuous development of payment technology, code scanning payment has penetrated into various fields. Code scanning payment can include a main scanning payment mode and a scanned payment mode. The main scanning payment mode is a payment mode in which a payment user scans a merchant payment code. The scanned payment mode is a payment mode in which a user terminal of a payment user displays a payment code, and a merchant terminal scans the payment code.

[0003] In a scenario using the scanned payment mode, in order to save payment time, the user will display the payment code in the user terminal in advance. During the user's waiting for payment, there is a case that the payment code is stolen and used, which reduces the payment security of the user. SUMMARY

[0004] The embodiments of the present application provide a code scanning payment method, a user terminal, a business device, a system and a medium, which can improve the security of code scanning payment.

[0005] In a first aspect, the embodiments of the present application provide a code scanning payment method applied to a business system, the method comprising: receiving a payment code request message, the payment code request message being generated by a user terminal in response to a payment operation and comprising location information of the user terminal; obtaining payment waiting time factor information associated with the location information; in a case where a payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to a preset time threshold, sending a first payment code feedback message, the first payment code feedback message comprising a first payment code and a second payment code, so that the user terminal obtains the first payment code feedback message and displays the first payment code before sensing a trigger signal of a payment terminal, and in a case where the trigger signal is sensed, the displayed first payment code is switched to the second payment code; in a case where the received payment request message comprises first information, instructing to deduct a payment amount from a payment account indicated by the first information, the first information comprising information of the second payment code.

[0006] In a second aspect, the embodiments of the present application provide a code scanning payment method applied to a user terminal, which comprises: sending a payment code request message in response to a received payment operation, the payment code request message comprising location information of the user terminal; receiving a first payment code feedback message in a case where a payment waiting time length represented by payment waiting time length factor information associated with the location information obtained by a business system is greater than or equal to a preset time length threshold, the first payment code feedback message being generated by the business system and comprising a first payment code and a second payment code; displaying the first payment code, and switching the displayed first payment code to the second payment code in a case where a trigger signal of a payment accepting terminal is sensed, so that the business system deducts a payment amount from a payer account indicated by first information comprising information of the second payment code.

[0007] In a third aspect, the embodiments of the present application provide a business device, which comprises: a receiving module configured to receive a payment code request message generated by a user terminal in response to a payment operation, the payment code request message comprising location information of the user terminal; an obtaining module configured to obtain payment waiting time length factor information associated with the location information; a sending module configured to send a first payment code feedback message in a case where a payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to a preset time length threshold, the first payment code feedback message comprising a first payment code and a second payment code, so that the user terminal obtains the first payment code feedback message, displays the first payment code before a trigger signal of a payment accepting terminal is sensed, and switches the displayed first payment code to the second payment code in a case where the trigger signal is sensed; and a payment processing module configured to instruct to deduct a payment amount from a payer account indicated by first information comprising information of the second payment code in a case where a received payment request message comprises the first information.

[0008] In a fourth aspect, the embodiments of the present application provide a user terminal, which comprises: a sending module configured to send a payment code request message in response to a received payment operation, the payment code request message comprising location information of the user terminal; a receiving module configured to receive a first payment code feedback message in a case where a payment waiting time length represented by payment waiting time length factor information associated with the location information obtained by a business system is greater than or equal to a preset time length threshold, the first payment code feedback message being generated by the business system and comprising a first payment code and a second payment code; and a display module configured to display the first payment code, and switch the displayed first payment code to the second payment code in a case where a trigger signal of a payment accepting terminal is sensed, so that the business system deducts a payment amount from a payer account indicated by first information comprising information of the second payment code.

[0009] In a fifth aspect, an embodiment of the present application provides a service device, comprising a processor and a memory storing computer program instructions; the processor implements the code payment method of the first aspect when executing the computer program instructions.

[0010] In a sixth aspect, an embodiment of the present application provides a user terminal, comprising a processor and a memory storing computer program instructions; the processor implements the code payment method of the second aspect when executing the computer program instructions.

[0011] In a seventh aspect, an embodiment of the present application provides a code payment system, comprising a user terminal and a service system; the user terminal is configured to send a payment code request message in response to a received payment operation, the payment code request message comprising location information of the user terminal; the service system is configured to receive the payment code request message, acquire payment waiting time factor information associated with the location information, and send a first payment code feedback message comprising a first payment code and a second payment code in a case where a payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to a preset time threshold; the user terminal is further configured to display the first payment code and switch the displayed first payment code to the second payment code in a case where a trigger signal of a payment receiving terminal is sensed; and the service system is further configured to deduct a payment amount from a payer account indicated by first information in a case where the received payment request message comprises the first information, the first information comprising information of the second payment code.

[0012] In an eighth aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium storing computer program instructions, the computer program instructions being executed by a processor to implement the code payment method of the first aspect or the code payment method of the second aspect.

[0013] The embodiment of the application provides a code scanning payment method, a user terminal, a business device, a system and a medium. A business system receives a payment code request message including position information of a user terminal, determines whether a payment waiting time length represented by payment waiting time length factor information associated with the position information is greater than or equal to a preset time length threshold according to the payment waiting time length factor information, and if the payment waiting time length represented by the payment waiting time length factor information is greater than or equal to the preset time length threshold, it can be determined that the payment waiting time length is long, and there is a possibility that the payment code is stolen and used. The business system issues a first payment code and a second payment code for the user terminal. The first payment code is displayed on the user terminal before the user terminal senses a trigger signal sent by a payment receiving terminal, and the second payment code is displayed on the user terminal under the condition that the user terminal senses the trigger signal sent by the payment receiving terminal. The payment request message received by the business system includes information of the second payment code, indicating that the payment receiving terminal scans the second payment code. Since the second payment code is displayed only under the condition that the user terminal senses the trigger signal sent by the payment receiving terminal, the possibility of being stolen and used is very small, so normal payment is allowed to continue. Through the payment code issuing strategy corresponding to the payment waiting time length and the switching of the first payment code and the second payment code, the payment with high security can be effectively distinguished, and the security of the code scanning payment is improved. BRIEF DESCRIPTION OF DRAWINGS

[0014] In order to more clearly illustrate the technical solutions of the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiments of the application. Those skilled in the art can also obtain other drawings according to these drawings without creating any creative labor.

[0015] Figure 1 An architecture schematic diagram of an example of an application scenario of the code scanning payment method provided by the embodiments of the application;

[0016] Figure 2 A flowchart of an embodiment of the code scanning payment method provided by the first aspect of the application;

[0017] Figure 3 A flowchart of another embodiment of the code scanning payment method provided by the first aspect of the application;

[0018] Figure 4 A flowchart of still another embodiment of the code scanning payment method provided by the first aspect of the application;

[0019] Figure 5 A flowchart of still another embodiment of the code scanning payment method provided by the first aspect of the application;

[0020] Figure 6 A flowchart of an embodiment of the code scanning payment method provided by the second aspect of the application;

[0021] Figure 7 Flow chart of another embodiment of the method for scanning code payment provided by the second aspect of the present application;

[0022] Figure 8 Flow chart of yet another embodiment of the method for scanning code payment provided by the second aspect of the present application;

[0023] Figure 9 Flow chart of an example of the scanning code payment process provided by the embodiments of the present application;

[0024] Figure 10 Structural schematic diagram of an embodiment of the business device provided by the third aspect of the present application;

[0025] Figure 11 Structural schematic diagram of another embodiment of the business device provided by the third aspect of the present application;

[0026] Figure 12 Structural schematic diagram of yet another embodiment of the business device provided by the third aspect of the present application;

[0027] Figure 13 Structural schematic diagram of an embodiment of the user terminal provided by the fourth aspect of the present application;

[0028] Figure 14 Structural schematic diagram of another embodiment of the user terminal provided by the fourth aspect of the present application;

[0029] Figure 15 Structural schematic diagram of an embodiment of the business device provided by the fifth aspect of the present application;

[0030] Figure 16 Structural schematic diagram of an embodiment of the user terminal provided by the sixth aspect of the present application. DETAILED DESCRIPTION

[0031] The features and exemplary embodiments of the various aspects of the present application will be described in detail below, in order to make the purposes, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in combination with the drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, but not to limit the present application. The present application can be implemented without some of these specific details by those skilled in the art. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

[0032] With the continuous development of payment technology, code scanning payment has penetrated into various fields. Code scanning payment can include a main scanning payment mode and a scanned payment mode. The main scanning payment mode is a payment method in which a payment user scans a merchant payment code. The scanned payment mode is a payment method in which a user terminal of a payment user displays a payment code, and a merchant terminal scans the payment code. In a scenario using the scanned payment mode, in order to save payment time, the user will display the payment code in advance on the user terminal. However, during the user's waiting for payment, someone may take a picture of the payment code displayed on the user terminal and use the stolen payment code to make a payment, causing the funds in the account of the user to whom the payment code belongs to be stolen, which seriously affects the payment security of the user.

[0033] The present application provides a code scanning payment method, a user terminal, a business device, a system and a medium. In the case that the waiting time for payment at the location of the user terminal requiring payment is long, such as a long queue for payment, two different payment codes are issued to the user terminal. In the case that the user terminal is not close to the payment terminal, such as a point of sale (POS) device, one of the payment codes is displayed on the user terminal. In the case that the user terminal is close to the payment terminal, the other payment code is displayed on the user terminal. Other people queuing around the user of the user terminal are difficult to take a picture of the other payment code. Therefore, in the case that the payment request message received by the business system includes information of the other payment code, normal payment is allowed, and the payment security of the user is improved.

[0034] The code scanning payment method in the embodiments of the present application is applied to a scenario of the scanned payment mode, and can involve a user terminal, a payment terminal, a payment institution system, a business system and an account management system. Figure 1 An architecture diagram of an example of an application scenario of the code scanning payment method provided by the embodiments of the present application is shown in FIG. 1. Figure 1 As shown in FIG. 1, the architecture system of the code scanning payment method can include a user terminal 11, a payment terminal 12, a payment institution system 13, a business system 14 and an account management system 15.

[0035] The user terminal 11 is a terminal device used by a user for payment, and can specifically include a mobile phone, a tablet computer, a smart wearable device, etc. The specific type of the user terminal 11 is not limited herein. The user terminal 11 can be installed with a payment application, and the payment application can be used for payment. The user terminal 11 has a display function and can display a payment code, so as to use the payment code for payment. The payment code can be a two-dimensional code or other graphic code, and the specific type thereof is not limited herein. The user terminal 11 can interact with the payment institution system 13, and apply for a payment code to the business system 14 through the payment institution system 13. In order to ensure the security of the payment code, the payment code has a validity period. After the validity period, the payment code cannot be used continuously and needs to be updated.

[0036] The collection receiving terminal 12 is a terminal device used by the merchant to interact with the user terminal 11 during the payment process, and can specifically include a POS machine and the like, without limitation on the specific type of the collection receiving terminal 12. The collection receiving terminal 12 can have a scanning function and can scan the payment code to read the information contained in the payment code. The collection receiving terminal 12 can initiate a payment request to the payment institution system 13.

[0037] The payment institution system 13 can be used for payment collection, and can specifically be a system of a collection institution. The payment institution system 13 can include one or more servers and the like, and different servers and the like in the payment institution system 13 can perform the same function in the payment institution system 13 or different functions in the payment institution system 13, without limitation. The payment institution system 13 can pass the payment request to the business system 14.

[0038] The business system 14 can be used to generate and issue payment codes, can be used for payment risk control, and can be used for clearing and the like. The business system 14 can include multiple subsystems, for example, the business system 14 can include a payment code subsystem 141, a risk control subsystem 142, and a clearing subsystem 143, and the like. The business system 14 can issue the generated payment code to the user terminal 11 through the payment institution system 13. The business system 14 can include one or more servers and the like, and different servers and the like in the business system 14 can perform the same function in the business system 14 or different functions in the business system 14. In the case where the business system 14 includes multiple servers and the like, some servers and the like can belong to the payment code subsystem 141, some servers and the like can belong to the risk control subsystem 142, and some servers and the like can belong to the clearing subsystem 143.

[0039] The account management system 15 is a system for managing accounts such as user accounts and merchant accounts. The account management system 15 can interact with the business system 14 to complete the deduction of the payment account and the collection of the collection account, and the like. The account management system 15 can include one or more servers and the like, and different servers and the like in the account management system 15 can perform the same function in the account management system 15 or different functions in the account management system 15, without limitation.

[0040] The code scanning payment method, the user terminal, the business device, the system, and the medium in the present application are described in turn as follows.

[0041] The first aspect of the present application provides a code scanning payment method, which can be applied to a business system, i.e., the code scanning payment method can be executed by the business system, and specifically, the code scanning payment method can be executed by a business device in the business system. Figure 2A flowchart of an embodiment of the code scanning payment method according to the first aspect of the present application is shown in FIG. 2. As shown in FIG. 2, the code scanning payment method can include steps S201-S204. Figure 2

[0042] In step S201, a payment code request message is received.

[0043] The payment code request message is used to request a payment code and can be generated by the user terminal in response to a payment operation. The user terminal generates the payment code request message and sends it to the business system via the payment institution system. That is, the user terminal sends the payment code request message to the payment institution system, which then sends the payment code request message to the business system. The business system receives the payment code request message sent by the payment institution system. For example, the user performs a payment operation on the user terminal, opens a payment application, and clicks on the “payment code” function. The user terminal sends a payment code request message to the payment institution system in response to the payment operation.

[0044] The payment code request message includes location information of the user terminal. The location information of the user terminal can indicate the location of the user terminal. For example, the location information of the user terminal can include latitude and longitude information of the location where the user terminal is located.

[0045] In step S202, payment waiting duration factor information associated with the location information is obtained.

[0046] After obtaining the location information from the payment code request message, the payment waiting duration factor information associated with the location information is obtained. The payment waiting duration factor information associated with the location information can include payment waiting duration factor information of a merchant at the location indicated by the location information, payment waiting duration factor information of a region where the location indicated by the location information is located, etc. The payment waiting duration factor information includes factor information that affects the payment waiting duration and can reflect the payment waiting duration. The payment waiting duration can also be regarded as the payment queuing duration.

[0047] In some examples, the payment waiting duration factor information can include one or more of the following: state information of the payee, queuing duration information of the payee, historical waiting time information of users who have traded with the payee, etc.

[0048] ​The state information of the payee can represent the busy degree of the payee. The more busy the payee is, the longer the payment waiting time of the payer can be. The queuing time information of the payee can represent the queuing time of the payee. The longer the queuing time is, the longer the payment waiting time can be. The historical waiting time information of the user who has a transaction with the payee can include historical information related to the payment waiting time of the user who has a transaction with the payee, and the payment waiting time is determined by the information of the user who has a transaction with the payee. For example, the historical waiting time information can include a payment code request time and a payment time. The payment code request time is the time when the user terminal requests the payment code, and the payment time is the time when the user terminal makes the payment. The time between the payment code request time and the payment time of a user can be the payment waiting time of the user. The payment waiting time of the payee can be determined according to the time between the payment code request time and the payment time of multiple users who have a transaction with the payee.

[0049] In step S203, when the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to the preset time threshold, a first payment code feedback message is sent to enable the user terminal to obtain the first payment code feedback message and display the first payment code before sensing the trigger signal of the payee terminal, and switch the displayed first payment code to the second payment code when the trigger signal is sensed.

[0050] The preset time threshold is a threshold value for determining the time length that causes a security risk, which can be set according to the scene, demand, experience, etc., and is not limited herein. When the payment waiting time represented by the payment waiting time factor information is greater than or equal to the preset time threshold, it means that the security risk is relatively large, and the payment code issuing measure with higher security needs to be performed. When the payment waiting time represented by the payment waiting time factor information is less than the preset time threshold, it means that the security risk is relatively small and can be ignored.

[0051] If the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to the preset time threshold, the business system can send a first payment code feedback message to the payment institution system, and the payment institution system can send the first payment code feedback message to the user terminal. The first payment code feedback message includes a first payment code and a second payment code. The first payment code is different from the second payment code.

[0052] The user terminal receives the first payment code feedback message, obtains the first payment code and the second payment code from the first payment code feedback message, can display the first payment code first, and saves the second payment code. The payment receiving terminal can send a trigger signal. When the payer user carrying the user terminal is still in the queue and has not arrived at the payment receiving terminal, the user terminal does not sense the trigger signal sent by the payment receiving terminal, and the user terminal displays the first payment code before the user terminal senses the trigger signal or before the user terminal senses the trigger signal. When the payer user carrying the user terminal arrives at the payment receiving terminal, the user terminal senses the trigger signal sent by the payment receiving terminal, and can switch the displayed first payment code to the second payment code, so that the payment receiving terminal scans the second payment code.

[0053] In some examples, the trigger signal can include one or more of the following: a near field communication (NFC) signal, a Bluetooth signal, a sound wave signal, etc. The NFC signal can include information of an encrypted NFC tag of the payment receiving terminal. The Bluetooth signal can include information of a Bluetooth tag of the payment receiving terminal. The sound wave signal can include information of a sound wave tag, and the sound wave signal can also be a low-frequency sound wave signal of a specific frequency.

[0054] In step S204, in the case where the received payment request message includes the first information, the payment amount is instructed to be deducted from the payer account indicated by the first information.

[0055] After the payment receiving terminal scans the payment code displayed by the user terminal, a payment request message is generated according to the information read from the payment code, and the payment request message includes the information read from the payment code. The payment receiving terminal sends the payment request message to the payment institution system, and the payment institution system sends the payment request message to the business system.

[0056] The first information includes information of the second payment code, and the information of the second payment code is information obtained by reading the second payment code. The payment request message received by the business system includes the first information, indicating that the second payment code is scanned by the payment receiving terminal in this code payment, that is, the second payment code scanned by the payment receiving terminal is switched when the user terminal arrives at the payment receiving terminal, and the security risk of this code payment is smaller, allowing the payment to continue normally. The business system can send a transaction message to the account management system to instruct the payment amount to be deducted from the payer account indicated by the first information.

[0057] In the embodiment of the present application, the business system receives a payment code request message including location information of a user terminal, determines whether the payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to a preset time threshold according to the payment waiting time length factor information associated with the location information, and if the payment waiting time length represented by the payment waiting time length factor information is greater than or equal to the preset time threshold, it can be determined that the payment waiting time length is long and there is a possibility that the payment code is stolen and used. The business system issues a first payment code and a second payment code for the user terminal. The first payment code is displayed on the user terminal before the user terminal senses the trigger signal sent by the payment receiving terminal, and the second payment code is displayed on the user terminal under the condition that the user terminal senses the trigger signal sent by the payment receiving terminal. The payment request message received by the business system includes information of the second payment code, indicating that the payment receiving terminal scans the second payment code. Since the second payment code is displayed only when the user terminal senses the trigger signal sent by the payment receiving terminal, the possibility of being stolen and used is very small, so normal payment is allowed to continue. Through the payment code issuing strategy corresponding to the payment waiting time length and the switching of the first payment code and the second payment code, the payment with high security can be effectively distinguished, and the security of the code scanning payment is improved.

[0058] The switching of the first payment code and the second payment code described above is actively performed by the user terminal without the participation of the user, which can reduce the operation of the user, improve the efficiency of the code scanning payment on the basis of ensuring the security of the code scanning payment. Moreover, compared with the technical solution of shortening the effective time length of the payment code, the embodiment of the present application does not need to frequently update and issue the payment code, and can also reduce the processing pressure of the business system generating and issuing the payment code on the basis of ensuring the security of the code scanning payment.

[0059] In some embodiments, whether the payment waiting time length is greater than or equal to the preset time threshold can be determined by whether the payment waiting time length factor satisfies the double-code issuing condition. Figure 3 The flowchart of another embodiment of the code scanning payment method provided by the first aspect of the present application. Figure 3 Different from Figure 2 The difference between the code scanning payment method shown in Figure 3 The code scanning payment method shown in FIG. 5 can further include step S205.

[0060] In step S205, if the payment waiting time length factor information associated with the location information satisfies the double-code issuing condition, it is determined that the payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to the preset time threshold.

[0061] The double-code issuing condition comprises a condition for judging whether the payment under the payment waiting time factor information condition has the risk of the payment code being stolen and misused. The payment waiting time factor information associated with the location information satisfies the double-code issuing condition, and it is determined that the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to the preset time threshold, which indicates that the payment under the payment waiting time factor information condition has the risk of the payment code being stolen and misused. The first payment code and the second payment code can be issued to the user terminal through the first payment code feedback message. In some examples, the payment waiting time factor information associated with the location information does not satisfy the double-code issuing condition, and it is determined that the payment waiting time represented by the payment waiting time factor information associated with the location information is less than the preset time threshold, which indicates that the payment under the payment waiting time factor information condition does not have the risk of the payment code being stolen and misused. One payment code can be issued to the user terminal.

[0062] The specific content of the payment waiting time factor information can be referred to the related description in the above embodiments, which will not be repeated here.

[0063] In some examples, the double-code issuing condition can comprise one or more of the following:

[0064] The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in a busy state of collecting money;

[0065] The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in an activity holding state;

[0066] The queuing time information of the payee associated with the location information indicates that the queuing time of the payee located in the area corresponding to the location information is greater than or equal to a preset time threshold;

[0067] The time between the payment code request time and the payment time of the user who trades with the payee associated with the location information is greater than or equal to a preset time threshold.

[0068] The area corresponding to the location information is the area where the location indicated by the location information is located, and the size of the area can be set according to the required accuracy of the payee, which is not limited here. In some examples, the area corresponding to the location information can only include one payee.

[0069] The state information of the payee indicates that the payee is in a busy state of collecting money, and there are many payee users waiting for payment at the payee. Correspondingly, the payment waiting time of the payee user is longer, that is, the payment waiting time represented by the payment waiting time factor information is greater than or equal to the preset time threshold, and the payment code of the payee user will have the possibility of being stolen and misused, and the first payment code and the second payment code need to be issued to the user terminal.

[0070] The state information of the payee indicates that the payee is in an active hosting state, and there are many payee users waiting for payment, and correspondingly, the payment waiting time of the payee user is long, that is, the payment waiting time indicated by the payment waiting time factor information is greater than or equal to the preset time threshold, and the payment code of the payee user may be stolen and used, so the first payment code and the second payment code need to be issued to the user terminal. The activity hosted by the payee can be a promotion or preferential activity, which is not limited here.

[0071] The queuing time information of the payee indicates that the queuing time of the payee is basically consistent with the payment waiting time, and the longer the queuing time, the longer the payment waiting time. The queuing time information of the payee indicates that the queuing time of the payee is greater than or equal to the preset time threshold, that is, the payment waiting time indicated by the payment waiting time factor information is greater than or equal to the preset time threshold, and the payment code of the payee user may be stolen and used, so the first payment code and the second payment code need to be issued to the user terminal.

[0072] The time between the payment code request time and the payment time of the user of the payee transaction is the payment waiting time, and the time between the payment code request time and the payment time of the user of the payee transaction is greater than or equal to the preset time threshold, that is, the payment waiting time indicated by the payment waiting time factor information is greater than or equal to the preset time threshold, and the payment code of the payee user may be stolen and used, so the first payment code and the second payment code need to be issued to the user terminal.

[0073] In some embodiments, the first payment code displayed by the user terminal may be stolen and used for payment, or due to the delay in switching the user terminal from the first payment code to the second payment code, the first payment code scanned by the payee terminal is still the first payment code. In order to accurately distinguish the payment with the risk of being stolen and used, further judgment can be made according to the transaction information included in the payment request message, and corresponding processing is performed according to the judgment result. Figure 4 The flowchart of another embodiment of the code scanning payment method provided by the first aspect of the application. Figure 4 Different from Figure 2 The difference is that Figure 4 The code scanning payment method shown in FIG. 6 further includes steps S206 and S207.

[0074] In step S206, if the transaction information satisfies the risk control condition when the received payment request message includes the second information, the transaction intervention processing is performed.

[0075] The second information includes information of the first payment code, and the information of the first payment code is information read from the first payment code. The payment request message received by the business system includes the second information, indicating that the first payment code is scanned by the payment receiving terminal in this time of code scanning payment. However, the first payment code scanned by the payment receiving terminal may be a first payment code stolen and used by others, or a first payment code that has not been switched by the user terminal due to a delay in switching the payment code. However, the payment of the first payment code stolen and used by others is illegal payment, and the first payment code that has not been switched by the user terminal due to a delay in switching the payment code is legal payment, and whether the transaction information included in the payment request message meets the risk control condition can be used to further distinguish between illegal payment and legal payment.

[0076] The risk control condition is used to determine whether the payment indicated by the second information has a risk of being stolen, and the transaction intervention processing is used to safely process the payment with the risk of being stolen.

[0077] In some examples, the transaction information includes one or more of the following: a payment receiving party merchant address, a payment amount, and a payment frequency. The payment frequency is the frequency of payment using the first payment code corresponding to the second information.

[0078] The risk control condition includes one or more of the following:

[0079] The distance between the location of the payment receiving party merchant address and the location indicated by the location information is greater than a safe distance threshold;

[0080] The payment amount is greater than a safe amount threshold;

[0081] The payment frequency is higher than a safe frequency threshold.

[0082] The transaction information meets the risk control condition, indicating that the payment corresponding to the transaction information has a risk of being stolen and needs to be processed by transaction intervention.

[0083] In some cases of stealing and using the payment code, the person who steals the payment code will send the stolen payment code to others, and others will make a payment at a payment receiving party in another location. Whether this payment is illegal payment using a stolen first payment code at a payment receiving party in another location can be determined by the distance between the location of the payment receiving party merchant address and the location indicated by the location information of the user terminal in the payment code request message and the safe distance threshold. The safe distance threshold is a safe threshold value for determining whether it is a payment in the same location, which can be set according to the scene, demand, experience, etc., and is not limited herein. The distance between the location of the payment receiving party merchant address and the location indicated by the location information is greater than the safe distance threshold, indicating that the location of the payment code application and the payment location are far apart and not in the same location, which is likely to be illegal payment of stolen and used payment code, and needs to be processed by transaction intervention.

[0084] The payment amount can also be used to assist in improving the security of the code scanning payment. The security amount threshold is a threshold value of the amount of payment that is determined to be safe. The threshold value can be set according to the scene, demand, experience, etc., and is not limited herein. If the payment amount is greater than the security amount threshold, and the payment code is stolen and used, a large loss can occur, and transaction intervention processing is required.

[0085] The payment frequency can also be used to assist in improving the security of the code scanning payment. The security frequency threshold is a threshold value of the frequency of payment that is determined to be safe. The threshold value can be set according to the scene, demand, experience, etc., and is not limited herein. If the payment frequency is higher than the security frequency threshold, and the payment code is stolen and used, a large loss can occur, and transaction intervention processing is required.

[0086] In the case where the risk control condition includes more than two conditions, the risk control condition can have a priority. The transaction information can be determined whether it meets the risk control condition with a relatively high priority first. If the transaction information meets the risk control condition with a relatively high priority, transaction intervention processing can be performed. If the transaction information does not meet the risk control condition with a relatively high priority, the transaction information can be determined whether it meets the risk control condition with a relatively low priority. For example, the risk control condition includes that the distance between the location of the payee merchant address and the location indicated by the location information is greater than the security distance threshold, and the payment amount is greater than the security amount threshold. If the distance between the location of the payee merchant address and the location indicated by the location information is greater than the security distance threshold, transaction intervention processing can be performed, and it is not necessary to determine whether the payment amount is greater than the security amount threshold. If the distance between the location of the payee merchant address and the location indicated by the location information is less than or equal to the security distance threshold, it is determined whether the payment amount is greater than the security amount threshold. If the payment amount is greater than the security amount threshold, transaction intervention processing can be performed.

[0087] The transaction intervention processing can include: performing identity verification on a user of a user terminal that sends a payment request message including the second information; or, suspending the payment indicated by the second information.

[0088] In a case where the payment indicated by the second information has a risk of being stolen, the business system can perform identity verification on a user who performs payment by using the first payment code corresponding to the second information. Specifically, the business system can send an identity verification request message to the payment institution system, and the payment institution system can send the identity verification request message to the user terminal. The user terminal can display an identity verification interface in response to the received identity verification request message, and prompt the user to input identity verification information. The identity verification information can include a payment account, a payment password, a verification code, and the like, which can prove that the user himself / herself performs the payment, and is not limited herein. The user terminal sends the identity verification information to the payment institution system, the payment institution system sends the identity verification information to the business system, and the business system checks whether the received identity verification information is consistent with the reserved or set identity verification information. If the identity verification information is consistent, the payment can be continued normally. If the identity verification information is not consistent, the payment is stopped.

[0089] In a case where the payment indicated by the second information has a risk of being stolen, the payment indicated by the second information can also be directly stopped to avoid the risk of being stolen.

[0090] In step S207, in a case where the received payment request message includes the second information, if the transaction information does not satisfy the risk control condition, the payment amount is indicated to be deducted from the payer account indicated by the second information.

[0091] The transaction information does not satisfy the risk control condition, indicating that the payment corresponding to the transaction information does not have a risk of being stolen, and the transaction intervention processing can not be performed, and the payment can be continued normally. The business system can send a transaction message to the account management system to indicate that the payment amount is deducted from the payer account indicated by the second information.

[0092] By using the transaction message and the risk control condition, the effectiveness of risk monitoring can be improved, the accuracy of identifying the payment with a risk of being stolen can be improved, and the security of the code scanning payment can be further improved.

[0093] In some embodiments, the payment waiting time is less than the preset time threshold, and the risk of the payer user's payment code being stolen by being taken a photo is small and can be ignored. The business system can issue a single payment code to the user terminal, further reducing the pressure of the business system generating the payment code and issuing the payment code on the basis of ensuring the security of the code scanning payment. Figure 5 A flowchart of still another embodiment of the code scanning payment method provided by the first aspect of the application. Figure 5 Different from Figure 2 The difference between the code scanning payment method shown in Figure 5 The code scanning payment method shown in

[0094] In step S208, in a case where the payment waiting time length represented by the payment waiting time length factor information associated with the location information is less than the preset time length threshold, a second payment code feedback message is sent, so that the user terminal obtains the second payment code feedback message and displays a third payment code.

[0095] The second payment code feedback message includes the third payment code. That is, in a case where the payment waiting time length represented by the payment waiting time length factor information associated with the location information is less than the preset time length threshold, it is considered that the risk of the payment code being stolen and misused is small and can be ignored, and the business system can issue a single payment code, i.e., the third payment code, to the user terminal. The user terminal displays the third payment code within the effective time length of the third payment code and does not trigger the switching of the payment code.

[0096] Specifically, the business system can send the second payment code feedback message to the payment institution system, and the payment institution system can send the second payment code feedback message to the user terminal. The user terminal receives the second payment code feedback information and obtains the third payment code from the second payment code feedback information, and can display the third payment code.

[0097] In step S209, in a case where the received payment request message includes third information, the payment amount is deducted from the payment account indicated by the third information.

[0098] The third information includes information of the third payment code, and the information of the third payment code is information read from the third payment code. The payment request message received by the business system includes the third information, indicating that the third payment code is scanned by the collection terminal in this scan payment. The third payment code is issued in a case where the risk of the payment code being stolen and misused is small, indicating that the security risk of this scan payment is small and allowing the payment to continue normally. The business system can send a transaction message to the account management system to instruct the payment amount to be deducted from the payment account indicated by the third information.

[0099] In a case where it is determined according to the payment waiting time length factor information associated with the location information that the risk of the payment code being stolen and misused is small, the business system issues a single payment code to the user terminal, which can reduce the pressure on the business system to generate and issue payment codes while ensuring the security of scan payment.

[0100] The second aspect of the present application provides a scan payment method, which can be applied to a user terminal, i.e., the scan method can be executed by a user terminal. Figure 6 A flowchart of an embodiment of the scan payment method provided by the second aspect of the present application is shown in FIG. 3. Figure 6 As shown in FIG. 3, the scan payment method can include steps S301 to S303.

[0101] In step S301, a payment code request message is sent in response to a received payment operation.

[0102] The payment code request message comprises location information of the user terminal. Specifically, the user terminal can first send the payment code request message to the payment institution system, and the payment institution system can then send the payment code request message to the service system.

[0103] In step S302, the first payment code feedback message is received when the payment waiting time length represented by the payment waiting time length factor information associated with the location information obtained by the service system is greater than or equal to a preset time length threshold.

[0104] The first payment code feedback message is generated by the service system. The first payment code feedback message comprises the first payment code and the second payment code. Specifically, the service system can first send the first payment code feedback message to the payment institution system, and then the payment institution system can send the first payment code feedback message to the user terminal.

[0105] In step S303, the first payment code is displayed, and the displayed first payment code is switched to the second payment code when a trigger signal of the payment receiving terminal is sensed, so that the service system deducts the payment amount from the payment account indicated by the first information.

[0106] After receiving the first payment code feedback message, the user terminal displays the first payment code before sensing the trigger signal of the payment receiving terminal, and then displays the second payment code when the trigger signal of the payment receiving terminal is sensed.

[0107] The first information comprises information of the second payment code.

[0108] In some examples, the trigger signal comprises one or more of the following: a near field communication signal, a Bluetooth signal, and a sound wave signal. For specific contents, please refer to the related description in the above embodiments, which will not be repeated here.

[0109] For specific contents of steps S301 to S303, please refer to the related description in the above embodiments, which will not be repeated here.

[0110] In the embodiment of the present application, the user terminal can request the payment code from the service system through the payment code request message. The payment code request message includes location information, which can reflect the location of the user terminal when the payment code is applied. The service system determines whether the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to the preset time threshold according to the payment waiting time factor information associated with the location information. If the payment waiting time represented by the payment waiting time factor information is greater than or equal to the preset time threshold, it can be determined that the payment waiting time is long, and there is a possibility that the payment code will be stolen and used. The user terminal can receive the first payment code and the second payment code issued by the service system through the first payment code feedback message. The user terminal displays the first payment code before sensing the trigger signal issued by the payment receiving terminal. If the user terminal senses the trigger signal issued by the payment receiving terminal, the displayed payment code is switched to the second payment code. When the user terminal performs payment at the payment receiving terminal, the payment receiving terminal scans the second payment code, and the information of the second payment code can be used to continue normal payment through the service system. Since the second payment code is displayed only when the user terminal senses the trigger signal issued by the payment receiving terminal, the possibility of being stolen and used is very small, so normal payment is allowed. Through the payment code issuing strategy corresponding to the payment waiting time and the switching of the first payment code and the second payment code, the payment with high security can be effectively distinguished, and the security of the code scanning payment is improved.

[0111] The switching of the first payment code and the second payment code is actively performed by the user terminal, without the participation of the user, which can reduce the operation of the user and improve the efficiency of the code scanning payment on the basis of ensuring the security of the code scanning payment. Moreover, compared with the technical solution of shortening the effective time of the payment code, the embodiment of the present application does not need to frequently update and issue the payment code, and can reduce the processing pressure of the service system generating and issuing the payment code on the basis of ensuring the security of the code scanning payment.

[0112] In some embodiments, in a case where the payment waiting time factor information associated with the location information satisfies the double-code issuing condition, the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to the preset time threshold.

[0113] The payment waiting time factor information includes one or more of the state information of the payee, the queuing time information of the payee, and the historical waiting time information of the user in a transaction with the payee. The historical waiting time information includes the payment code request time and the payment time.

[0114] The double-code issuing condition includes one or more of the following:

[0115] The state information of the payee associated with the location information represents that the payee located in the area corresponding to the location information is in a busy state of receiving payment;

[0116] The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in an active state of holding an event;

[0117] The queuing duration information of the payee associated with the location information indicates that the queuing duration of the payee located in the area corresponding to the location information is greater than or equal to a preset duration threshold;

[0118] The duration between the time of requesting the payment code of the user who trades with the payee and the time of payment associated with the location information is greater than or equal to a preset duration threshold.

[0119] The specific content of the payment waiting duration factor information, the double-code issuing condition, etc. associated with the location information can be referred to the related description in the above embodiments, which will not be repeated here.

[0120] In some embodiments, the first payment code can also be read by the payee terminal, and whether the payment corresponding to the first payment code is a payment with high security risk can be further distinguished by the transaction information and the risk control condition in the payment request message. Figure 7 The flowchart of another embodiment of the code scanning payment method provided by the second aspect of the application. Figure 7 The difference between the code scanning payment method shown in Figure 6 The code scanning payment method shown in Figure 7 may further include step S304.

[0121] In step S304, if the transaction information in the payment request message sent by the payee terminal to the business system satisfies the risk control condition, the transaction intervention processing is accepted in the case that the first payment code is read by the payee terminal.

[0122] The risk control condition is used to determine whether the payment indicated by the second information has a risk of being stolen. The second information includes information of the first payment code. The transaction intervention processing is used to perform a security processing on the payment with a risk of being stolen.

[0123] The specific content of step S304 can be referred to the related description in the above embodiments, which will not be repeated here.

[0124] In some examples, the transaction information includes one or more of the following: payee merchant address, payment amount, and payment frequency. The specific content of the transaction information can be referred to the related description in the above embodiments, which will not be repeated here.

[0125] In some examples, the risk control condition includes one or more of the following:

[0126] The distance between the location of the payee merchant address and the location indicated by the location information is greater than a security distance threshold;

[0127] The payment amount is greater than a security amount threshold value;

[0128] The payment frequency is higher than a security frequency threshold value.

[0129] The specific content of the risk control condition can be referred to the related description in the above embodiments, which will not be repeated here.

[0130] In some examples, the transaction intervention processing includes: authenticating the user of the user terminal; or, suspending the payment indicated by the second information.

[0131] The specific content of the transaction intervention processing can be referred to the related description in the above embodiments, which will not be repeated here.

[0132] In some embodiments, in the case that the first payment code is read by the payee terminal, if the transaction information in the payment request message sent by the payee terminal to the business system does not satisfy the risk control condition, the payment indicated by the second information proceeds normally.

[0133] The specific content of the payment in the case that the transaction information in the payment request message sent by the payee terminal to the business system does not satisfy the risk control condition can be referred to the related description in the above embodiments, which will not be repeated here.

[0134] In some embodiments, the payment waiting time is less than a preset time threshold value, and the risk of the payment code of the payer user being stolen and misused is negligible, so the business system can issue a single payment code to the user terminal. Figure 8 A flowchart of still another embodiment of the code scanning payment method provided by the second aspect of the present application. Figure 8 Different from Figure 6 The difference is that Figure 8 The code scanning payment method shown in the figure can further include steps S305 and S306.

[0135] In step S305, in the case that the payment waiting time factor information represented by the payment waiting time associated with the location information obtained by the business system is less than a preset time threshold value, a second payment code feedback message is received.

[0136] The second payment code feedback message includes a third payment code.

[0137] In step S306, the third payment code is displayed, so that the business system deducts the payment amount from the payer account indicated by the third information by using the third information.

[0138] The third information includes information of the third payment code.

[0139] The specific content of steps S305 to S306 can be referred to the related description in the above embodiments, which will not be repeated here.

[0140] In order to facilitate understanding of the code scanning payment method in the embodiments of the present application, the following takes the example of a business system issuing two payment codes, i.e., a first payment code and a second payment code, at one time to illustrate the code scanning payment process among the user terminal, the payment receiving terminal, the payment institution system, the business system and the account management system. Figure 9 The following is a flowchart of an example of the code scanning payment process provided by the embodiments of the present application. As shown in the figure, Figure 9 the overall code scanning payment process can include steps S401 to S418.

[0141] In step S401, the user terminal sends a payment code request message to the payment institution system in response to a payment operation of the user.

[0142] In step S402, the payment institution system sends the payment code request message to the business system.

[0143] In step S403, the business system acquires payment waiting duration factor information associated with the location information in the payment code request message.

[0144] In step S404, the business system determines whether the payment waiting duration factor information satisfies the double code issuing condition.

[0145] In step S405, if the double code issuing condition is satisfied, the business system sends a first payment code feedback message to the payment institution system. The first payment code feedback message includes the first payment code and the second payment code.

[0146] In step S406, the payment institution system sends the first payment code feedback message to the user terminal.

[0147] In step S407, the user terminal displays the first payment code first and stores the second payment code.

[0148] In step S408, the user terminal switches to display the second payment code in the case where the user terminal senses a trigger signal sent by the payment receiving terminal.

[0149] In step S409, the payment receiving terminal scans the payment code displayed by the user terminal and reads the information of the payment code.

[0150] In step S410, the payment receiving terminal sends a payment request message to the payment institution system. The payment request message includes transaction information and the information of the read payment code.

[0151] In step S411, the payment institution system sends the payment request message to the business system.

[0152] In step S412, the business system identifies whether the payment code information in the payment request message is the first payment code information or the second payment code information. If the payment code information in the payment request message is the second payment code information, the process jumps to step S413; if the payment code information in the payment request message is the first payment code information, the process jumps to step S415.

[0153] In step S413, the business system sends a transaction message to the account management system.

[0154] In step S414, the account management system deducts the payment amount from the payer account indicated by the second payment code information in response to the transaction message.

[0155] In step S415, the business system determines whether the transaction information satisfies the risk control condition. If the transaction information satisfies the risk control condition, the process jumps to step S416; if the transaction information does not satisfy the risk control condition, the process jumps to step S417.

[0156] In step S416, the business system performs transaction intervention processing.

[0157] In step S417, the business system sends a transaction message to the account management system.

[0158] In step S418, the account management system deducts the payment amount from the payer account indicated by the first payment code information in response to the transaction message.

[0159] The specific content in steps S401-S418 can refer to the related content in the above embodiments, which will not be repeated here.

[0160] The third aspect of the present application provides a business device. Figure 10 An embodiment of the business device provided by the third aspect of the present application is shown in a structural schematic diagram. As shown in the figure, the business device 500 can include a receiving module 501, an obtaining module 502, a sending module 503, and a payment processing module 504. Figure 10

[0161] The receiving module 501 can be used to receive a payment code request message.

[0162] The payment code request message is generated by the user terminal in response to a payment operation and includes location information of the user terminal.

[0163] The obtaining module 502 can be used to obtain payment waiting time factor information associated with the location information.

[0164] ​The sending module 503 can be configured to send the first payment code feedback message in a case where the payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to the preset time length threshold, so that the user terminal obtains the first payment code feedback message, and displays the first payment code before sensing the trigger signal of the payment receiving terminal, and switches the displayed first payment code to the second payment code in a case where the trigger signal is sensed.

[0165] The first payment code feedback message includes the first payment code and the second payment code.

[0166] In some examples, the trigger signal includes one or more of the following: a near field communication signal, a Bluetooth signal, and a sound wave signal.

[0167] The payment processing module 504 can be configured to deduct the payment amount from the payer account indicated by the first information in a case where the received payment request message includes the first information.

[0168] The first information includes information of the second payment code.

[0169] In the embodiments of the present application, the business system receives a payment code request message including location information of a user terminal, determines whether the payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to a preset time length threshold according to the payment waiting time length factor information, and if the payment waiting time length represented by the payment waiting time length factor information is greater than or equal to the preset time length threshold, it can be determined that the payment waiting time length is long, and there is a possibility that the payment code will be stolen and used. The business system issues a first payment code and a second payment code for the user terminal. The first payment code is displayed on the user terminal before the user terminal senses the trigger signal sent by the payment receiving terminal, and the second payment code is displayed on the user terminal in a case where the user terminal senses the trigger signal sent by the payment receiving terminal. The payment request message received by the business system includes information of the second payment code, indicating that the payment receiving terminal scans the second payment code. Since the second payment code is displayed only in the case where the user terminal senses the trigger signal sent by the payment receiving terminal, the possibility of being stolen and used is very small, so normal payment is allowed to continue. Through the payment code issuing strategy corresponding to the payment waiting time length and the switching of the first payment code and the second payment code, a payment with high security can be effectively distinguished, and the security of the code scanning payment is improved.

[0170] The switching of the first payment code and the second payment code described above is actively performed by the user terminal without the need for user participation, which can reduce the user's operation, improve the efficiency of the code scanning payment on the basis of ensuring the security of the code scanning payment. Moreover, compared with the technical solution of shortening the effective time length of the payment code, the embodiments of the present application do not need to frequently update and issue the payment code, and can also reduce the processing pressure of the business system generating and issuing the payment code on the basis of ensuring the security of the code scanning payment.

[0171] Figure 11 A structural schematic diagram of another embodiment of the service device provided in the third aspect of the present application is shown in FIG. 6. Figure 11 Different from Figure 10 , the difference lies in that Figure 11 The service device 500 shown in FIG. 6 can further include a determination module 505.

[0172] The determination module 505 can be configured to determine that the payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to a preset time length threshold, in a case where the payment waiting time length factor information associated with the location information satisfies a double-code issuing condition.

[0173] The payment waiting time length factor information includes one or more of the following: state information of the payee, queueing time length information of the payee, and historical waiting time information of a user who has traded with the payee. The historical waiting time information includes a payment code request time and a payment time.

[0174] The double-code issuing condition includes one or more of the following:

[0175] The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in a busy state of receiving payment;

[0176] The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in a state of holding an event;

[0177] The queueing time length information of the payee associated with the location information indicates that the queueing time length of the payee located in the area corresponding to the location information is greater than or equal to a preset time length threshold;

[0178] The time length between the payment code request time and the payment time of the user who has traded with the payee associated with the location information is greater than or equal to a preset time length threshold.

[0179] Figure 12 A structural schematic diagram of another embodiment of the service device provided in the third aspect of the present application is shown in FIG. 6. Figure 12 Different from Figure 10 , the difference lies in that Figure 12 The service device 500 shown in FIG. 6 can further include an intervention processing module 506.

[0180] The intervention processing module 506 can be configured to perform transaction intervention processing if the transaction information satisfies a risk control condition, in a case where the received payment request message includes second information.

[0181] The payment request message includes transaction information. The second information includes information of the first payment code. The risk control condition is used to determine that the payment indicated by the second information has a risk of being stolen. The transaction intervention processing is used to perform security processing on the payment that has the risk of being stolen.

[0182] In some examples, the transaction information comprises one or more of the following: a payee merchant address, a payment amount, a payment frequency.

[0183] In some examples, the risk control condition comprises one or more of the following:

[0184] a distance between the payee merchant address and a location indicated by the location information is greater than a safe distance threshold;

[0185] the payment amount is greater than a safe amount threshold;

[0186] the payment frequency is higher than a safe frequency threshold.

[0187] In some examples, the transaction intervention processing performed by the intervention processing module 506 can comprise: authenticating a user of the user terminal that sends the payment request message comprising the second information; or, suspending the payment indicated by the second information.

[0188] In some embodiments, the payment processing module 504 described above can also be configured to, in the case that the received payment request message comprises the second information, instruct to deduct the payment amount from a payor account indicated by the second information if the transaction information does not satisfy the risk control condition.

[0189] In some embodiments, the sending module 503 described above can also be configured to, in the case that a payor waiting time length factor information represented by the location information represents a payor waiting time length that is less than a preset time length threshold, send a second pay code feedback message, so that the user terminal obtains the second pay code feedback message and displays a third pay code.

[0190] The second pay code feedback message comprises the third pay code.

[0191] The payment processing module 504 described above can also be configured to, in the case that the received payment request message comprises the third information, instruct to deduct the payment amount from a payor account indicated by the third information.

[0192] The third information comprises information of the third pay code.

[0193] The fourth aspect of the present application provides a user terminal. Figure 13 An embodiment of the user terminal provided by the fourth aspect of the present application is shown in the structure diagram. As shown in the figure, the user terminal 600 can comprise a sending module 601, a receiving module 602 and a display module 603. Figure 13

[0194] The sending module 601 can be configured to send a pay code request message in response to a received payment operation.

[0195] The pay code request message comprises location information of the user terminal.​

[0196] The receiving module 602 can be configured to receive the first payment code feedback message in a case where the payment waiting time length represented by the payment waiting time length factor information associated with the location information obtained by the business system is greater than or equal to a preset time length threshold.

[0197] The first payment code feedback message is generated by the business system and includes the first payment code and the second payment code.

[0198] The display module 603 can be configured to display the first payment code and switch the displayed first payment code to the second payment code in a case where a trigger signal of the payment receiving terminal is sensed, so that the business system deducts the payment amount from the payment account indicated by the first information by using the first information.

[0199] The first information includes information of the second payment code.

[0200] In some examples, the trigger signal includes one or more of the following: a near field communication signal, a Bluetooth signal, and a sound wave signal.

[0201] In the embodiments of the present application, the user terminal can request the payment code from the business system through a payment code request message. The payment code request message includes location information, which can represent the location of the user terminal when the payment code is applied. The business system determines whether the payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to a preset time length threshold according to the payment waiting time length factor information. If the payment waiting time length represented by the payment waiting time length factor information is greater than or equal to the preset time length threshold, it can be determined that the payment waiting time length is longer and there is a possibility that the payment code will be stolen and misused. The user terminal can receive the first payment code and the second payment code issued by the business system through the first payment code feedback message. The user terminal displays the first payment code before sensing the trigger signal issued by the payment receiving terminal. The user terminal switches the displayed payment code to the second payment code in a case where the trigger signal issued by the payment receiving terminal is sensed, so that the payment receiving terminal scans the second payment code when the user terminal performs payment at the payment receiving terminal. The second payment code can be used to continue normal payment through the business system by using the information of the second payment code. Since the second payment code is displayed only in a case where the trigger signal issued by the payment receiving terminal is sensed, the possibility of being stolen and misused is very small, so normal payment is allowed. Through the payment code issuing strategy corresponding to the payment waiting time length and the switching of the first payment code and the second payment code, the payment with higher security can be effectively distinguished, and the security of the code scanning payment is improved.

[0202] The switching of the first payment code and the second payment code is actively performed by the user terminal without the participation of the user, which can reduce the operation of the user, improve the efficiency of the code scanning payment on the basis of ensuring the safety of the code scanning payment. Moreover, compared with the technical solution of shortening the effective duration of the payment code, the embodiments of the present application do not need to frequently update and issue the payment code, and can reduce the processing pressure of the business system generating and issuing the payment code on the basis of ensuring the safety of the code scanning payment.

[0203] In some embodiments, in a case where the payment waiting duration factor information associated with the location information satisfies the double-code issuing condition, the payment waiting duration factor information associated with the location information represents a payment waiting duration greater than or equal to a preset duration threshold.

[0204] The payment waiting duration factor information includes one or more than two of the state information of the payee, the queuing duration information of the payee, and the historical waiting time information of the user transacting with the payee. The historical waiting time information includes a payment code request time and a payment time.

[0205] The double-code issuing condition includes one or more of the following:

[0206] The state information of the payee associated with the location information represents that the payee located in the area corresponding to the location information is in a busy state of receiving payment;

[0207] The state information of the payee associated with the location information represents that the payee located in the area corresponding to the location information is in an active state of holding an event;

[0208] The queuing duration information of the payee associated with the location information represents that the queuing duration of the payee located in the area corresponding to the location information is greater than or equal to a preset duration threshold;

[0209] The duration between the payment code request time and the payment time of the user transacting with the payee associated with the location information is greater than or equal to a preset duration threshold.

[0210] Figure 14 The structure schematic diagram of another embodiment of the user terminal provided by the fourth aspect of the present application. Figure 14 Different from Figure 13 The difference between the user terminal 600 shown in the figure and the user terminal 600 shown in the figure is that Figure 14 The user terminal 600 shown in the figure can further include a processing module 604.

[0211] The processing module 604 can be used to, in a case where the first payment code is read by the payee receiving terminal, accept transaction intervention processing if the transaction information in the payment request message sent by the payee receiving terminal to the business system satisfies the risk control condition.

[0212] Risk control conditions are used to determine if a payment indicated by the second information is at risk of being stolen. The second information includes information from the first payment code. Transaction intervention processing is used to securely process payments at risk of being stolen.

[0213] In some examples, transaction information includes one or more of the following: the recipient merchant's address, the payment amount, and the payment frequency.

[0214] In some examples, risk control conditions include one or more of the following:

[0215] The distance between the location of the payee merchant's address and the location indicated by the location information is greater than the safe distance threshold;

[0216] The payment amount exceeds the safe amount threshold;

[0217] The payment frequency exceeds the safe frequency threshold.

[0218] In some examples, transaction intervention processes include: authenticating the user on the user terminal; or, suspending the payment indicated by the second information.

[0219] In some embodiments, if the transaction information in the payment request message sent by the payment acceptance terminal to the business system does not meet the risk control conditions when the first payment code is read by the payment acceptance terminal, the payment indicated by the second information proceeds normally.

[0220] In some embodiments, the receiving module 602 may also be used to receive a second payment code feedback message when the payment waiting time represented by the payment waiting time factor information associated with the location information obtained by the business system is less than a preset time threshold.

[0221] The second payment code feedback message includes the third payment code.

[0222] The aforementioned display module 603 can also be used to display a third payment code, so that the business system can use the third information to deduct the payment amount from the payer's account indicated by the third information.

[0223] The third piece of information includes the third payment code.

[0224] The fifth aspect of this application also provides a business device. Figure 15 This is a schematic diagram of the structure of an embodiment of the service equipment provided in the fifth aspect of this application. Figure 15 As shown, the service device 700 includes a memory 701, a processor 702, and a computer program stored in the memory 701 and executable on the processor 702.

[0225] In one example, the processor 702 can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured to implement one or more integrated circuits that implement embodiments of the present application.

[0226] The memory 701 can include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions that, when executed (e.g., by one or more processors), are operable to perform the operations described with reference to the method of scanning code payment according to the embodiments of the first aspect of the present application.

[0227] The processor 702 runs a computer program corresponding to the executable program code stored in the memory 701 by reading the executable program code, for implementing the method of scanning code payment in the above-mentioned embodiments of the first aspect.

[0228] In one example, the service device 700 can further include a communication interface 703 and a bus 704. As shown, the memory 701, the processor 702, and the communication interface 703 are connected through the bus 704 and complete communication with each other. Figure 15

[0229] The communication interface 703 is mainly used to realize the communication between various modules, devices, units, and / or equipment in the embodiments of the present application. The input device and / or the output device can also be accessed through the communication interface 703.

[0230] ​Bus 704 includes a hardware, software, or both that couples components of business device 700 to each other. As an example and not by way of limitation, bus 704 can include an accelerated graphics port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand (IB) interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or some other suitable bus or interconnect, or a combination of two or more of these. Where appropriate, bus 704 can include one or more buses. Although this application describes and shows a particular bus, this application contemplates any suitable bus or interconnect.

[0231] The sixth aspect of the application also provides a user terminal. Figure 16 An embodiment of the user terminal provided by the sixth aspect of the application is shown in a structural schematic diagram. As shown in the figure, the user terminal 800 includes a memory 801, a processor 802, and a computer program stored in the memory 801 and executable on the processor 802. Figure 16

[0232] In one example, the processor 802 described above can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured to implement one or more integrated circuits of the embodiments of the application.

[0233] ​The memory 801 can include a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions that, when executed (e.g., by one or more processors), are operable to perform the operations described with reference to the method of scanning code payment according to the embodiments of the second aspect of the present application.

[0234] The processor 802 runs a computer program corresponding to the executable program code stored in the memory 801 by reading the executable program code, for implementing the method of scanning code payment in the above-mentioned embodiments of the second aspect.

[0235] In one example, the user terminal 800 can further include a communication interface 803 and a bus 804. As shown, the memory 801, the processor 802, and the communication interface 803 are connected through the bus 804 and complete communication therebetween. Figure 16

[0236] The communication interface 803 is mainly used to implement the communication between various modules, devices, units, and / or equipment in the embodiments of the present application. The input device and / or the output device can also be accessed through the communication interface 803.

[0237] ​Bus 804 includes a hardware, software, or both that couples components of user terminal 800 to each other. As an example and not by way of limitation, bus 804 can include an accelerated graphics port (AGP) or other graphics bus, an enhanced industry standard architecture (EISA) bus, a front-side bus (FSB), a Hyper Transport (HT) interconnect, an industry standard architecture (ISA) bus, an infiniband interconnect, a low pin count (LPC) bus, a memory bus, a micro channel architecture (MCA) bus, a peripheral component interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a serial advanced technology attachment (SATA) bus, a video electronics standards board (VLB) bus, or another suitable bus or a combination of two or more of these. Where appropriate, bus 804 can include one or more buses. Although this application describes and shows a particular bus, this application contemplates any suitable bus or interconnect.

[0238] A seventh aspect of the present application provides a code scanning payment system, which can include a business system and a user terminal.

[0239] The user terminal is configured to send a payment code request message in response to receiving a payment operation, the payment code request message including location information of the user terminal.

[0240] The business system is configured to receive the payment code request message, obtain payment waiting time factor information associated with the location information, and send a first payment code feedback message including a first payment code and a second payment code when a payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to a preset time threshold.

[0241] The user terminal is further configured to display the first payment code and switch the displayed first payment code to the second payment code when a trigger signal of a payment receiving terminal is sensed.

[0242] The business system is further configured to, in a case where the received payment request message comprises the first information, instruct to deduct the payment amount from a payor account indicated by the first information, the first information comprising information of a second pay code.

[0243] The business system can refer to the business system 14 in the above embodiments and the related description of the business system in the above method of scanning code payment. The business system can comprise a business device. The business device can refer to the business device 500, the business device 700, and the like in the above embodiments.

[0244] The user terminal can refer to the user terminal 11 in the above embodiments, the user terminal in the above method of scanning code payment, the user terminal 600, the user terminal 800, and the like in the above embodiments.

[0245] In some embodiments, the scanning code payment system can further comprise a payment institution system. The payment institution system can refer to the payment institution system 13 in the above embodiments and the payment institution system in the above method of scanning code payment.

[0246] In some embodiments, the scanning code payment system can further comprise a payee terminal. The payee terminal can refer to the payee terminal 12 in the above embodiments and the payee terminal in the above method of scanning code payment.

[0247] In some embodiments, the scanning code payment system can further comprise an account management system. The account management system can refer to the account management system 15 in the above embodiments and the account management system in the above method of scanning code payment.

[0248] The eighth aspect of the present application further provides a computer readable storage medium, which stores computer program instructions. When the computer program instructions are executed by a processor, the scanning code payment method in the embodiments of the first aspect and the scanning code payment method in the embodiments of the second aspect can be implemented, and the same technical effects can be achieved. To avoid repetition, the same will not be described here. The computer readable storage medium can include a non-transitory computer readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. The present application is not limited here.

[0249] It should be clarified that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For the device embodiments, equipment embodiments, and computer-readable storage medium embodiments, the relevant parts can be referred to the description section of the method embodiments. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application. Furthermore, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

[0250] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0251] Those skilled in the art will understand that the above embodiments are exemplary and not restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, specification, and claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other means or steps; the quantifier "a" does not exclude a plurality; the terms "first" and "second" are used to identify names and not to indicate any particular order. No reference numerals in the claims should be construed as limiting the scope of protection. The functionality of multiple parts appearing in the claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A code scanning payment method, characterized in that, The method is applied to a business system and comprises the following steps: receiving a payment code request message, the payment code request message being generated by a user terminal in response to a payment operation and comprising location information of the user terminal; obtaining payment waiting time factor information associated with the location information, the payment waiting time factor information comprising one or more of state information of a payee, queue time information of the payee, and historical waiting time information of a user transacting with the payee; in a case where the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to a preset time threshold, sending a first payment code feedback message, the first payment code feedback message comprising a first payment code and a second payment code, so that the user terminal obtains the first payment code feedback message and displays the first payment code before sensing a trigger signal of a payee terminal, and switches the displayed first payment code to the second payment code in a case where the trigger signal is sensed; in a case where the received payment request message comprises first information, instructing to deduct a payment amount from a payee account indicated by the first information, the first information comprising information of the second payment code.

2. The method of claim 1, wherein, Further comprising: in a case where the payment waiting time factor information associated with the location information satisfies a double-code issuing condition, determining that the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to the preset time threshold, wherein the historical waiting time information comprises a payment code request time and a payment time, the double-code issuing condition comprises one or more of the following: the state information of the payee associated with the location information represents that a payee located in an area corresponding to the location information is in a busy state of receiving payment, the state information of the payee associated with the location information represents that a payee located in an area corresponding to the location information is in a state of holding an event, the queue time information of the payee associated with the location information represents that the queue time of a payee located in an area corresponding to the location information is greater than or equal to the preset time threshold, the time between the payment code request time and the payment time of the user transacting with the payee associated with the location information is greater than or equal to the preset time threshold.

3. The method of claim 1, wherein, the payment request message comprises transaction information, the method further comprises: in a case where the received payment request message comprises second information, if the transaction information satisfies a risk control condition, performing a transaction intervention process, wherein the second information comprises information of the first payment code, the risk control condition is used to determine that the payment indicated by the second information has a risk of being stolen, and the transaction intervention process is used to perform a security process on the payment with the risk of being stolen.

4. The method of claim 3, wherein the transaction information comprises one or more of the following: a payee merchant address, a payment amount, and a payment frequency; the risk control condition comprises one or more of the following: a distance between a location of the payee merchant address and a location indicated by the location information is greater than a safe distance threshold, the payment amount is greater than a safe amount threshold, The payment frequency is higher than a security frequency threshold.

5. The method of claim 3, wherein, The transaction intervention processing includes: authenticating a user of the user terminal that sent the payment request message including the second information; or, suspending the payment indicated by the second information.

6. The method of claim 3, wherein, Further includes: in the case where the received payment request message includes the second information, if the transaction information does not satisfy a risk control condition, instructing to deduct a payment amount from a payer account indicated by the second information.

7. The method of claim 1, wherein, Further includes: in the case where the payment waiting time length factor information associated with the location information represents a payment waiting time length less than the preset time length threshold, sending a second payment code feedback message including a third payment code, so that the user terminal acquires the second payment code feedback message and displays the third payment code; in the case where the received payment request message includes third information, instructing to deduct a payment amount from a payer account indicated by the third information, the third information including information of the third payment code.

8. The method according to any one of claims 1 to 7, characterized in that, The trigger signal includes one or more of: a near field communication signal, a Bluetooth signal, and a sound wave signal.

9. A method for payment by scanning a code, characterized by, Applied to a user terminal, the method includes: in response to a received payment operation, sending a payment code request message including location information of the user terminal; in the case where payment waiting time length factor information associated with the location information acquired by the business system represents a payment waiting time length greater than or equal to a preset time length threshold, receiving a first payment code feedback message generated by the business system, including a first payment code and a second payment code, the payment waiting time length factor information including one or more of state information of a payee, queue time length information of the payee, and historical waiting time information of a user transacting with the payee; displaying the first payment code, and in the case where a trigger signal of a payee terminal is sensed, switching the displayed first payment code to the second payment code, so that the business system deducts a payment amount from a payer account indicated by first information including information of the second payment code.

10. The method of claim 9, wherein, in the case where the payment waiting time length factor information associated with the location information satisfies a double code issuing condition, the payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to the preset time length threshold, wherein the historical waiting time information includes a payment code request time and a payment time, the double code issuing condition includes one or more of: the state information of the payee associated with the location information represents that a payee located in an area corresponding to the location information is in a busy state of receiving payment, the state information of the payee associated with the location information represents that a payee located in an area corresponding to the location information is in a state of holding an event, the queue time length information of the payee associated with the location information represents that a queue time length of a payee located in an area corresponding to the location information is greater than or equal to the preset time length threshold, The time length between the payment code request time and the payment time of the user transacting with the payee is greater than or equal to the preset time length threshold in association with the location information.

11. The method of claim 9, wherein, Further comprising: In a case where the first payment code is read by the payee terminal, if transaction information in a payment request message sent by the payee terminal to the business system satisfies a risk control condition, transaction intervention processing is accepted, The risk control condition is used to determine that the payment indicated by the second information has a risk of being stolen, and the second information includes information of the first payment code, and the transaction intervention processing is used to perform security processing on the payment with the risk of being stolen.

12. The method of claim 11, wherein, The transaction information includes one or more of the following: payee merchant address, payment amount, and payment frequency. The risk control condition includes one or more of the following: The distance between the location of the payee merchant address and the location indicated by the location information is greater than a safe distance threshold, The payment amount is greater than a safe amount threshold, The payment frequency is higher than a safe frequency threshold.

13. The method of claim 11, wherein, The transaction intervention processing includes: Identity verification of the user of the user terminal; Or, Aborting the payment indicated by the second information.

14. The method of claim 11, wherein, In a case where the first payment code is read by the payee terminal, if transaction information in a payment request message sent by the payee terminal to the business system does not satisfy a risk control condition, the payment indicated by the second information proceeds normally.

15. The method of claim 9, wherein, In a case where the payment waiting time length factor information associated with the location information obtained by the business system represents a payment waiting time length that is less than the preset time length threshold, a second payment code feedback message is received, and the second payment code feedback message includes a third payment code; The third payment code is displayed to enable the business system to deduct a payment amount from a payee account indicated by third information, and the third information includes information of the third payment code.

16. The method according to any one of claims 9 to 15, characterized in that, The trigger signal includes one or more of the following: Near field communication signal, Bluetooth signal, and sound wave signal.

17. A service device, characterized by Comprising: A receiving module configured to receive a payment code request message generated by a user terminal in response to a payment operation, the payment code request message including location information of the user terminal; An obtaining module configured to obtain payment waiting time length factor information associated with the location information, the payment waiting time length factor information including one or more of the following: state information of a payee, queuing time length information of the payee, and historical waiting time information of a user transacting with the payee. The sending module is configured to send a first payment code feedback message including a first payment code and a second payment code, in a case where the payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to a preset time length threshold, so that the user terminal acquires the first payment code feedback message, displays the first payment code before sensing a trigger signal of a payment receiving terminal, and switches the displayed first payment code to the second payment code in a case where the trigger signal of the payment receiving terminal is sensed. The payment processing module is configured to deduct a payment amount from a payment account indicated by the first information in a case where the received payment request message includes the first information including information of the second payment code.

18. A user terminal, characterized in that The method comprises the following steps: The sending module is configured to send a payment code request message including location information of the user terminal in response to a received payment operation. The receiving module is configured to receive a first payment code feedback message generated by a business system in a case where a payment waiting time length represented by payment waiting time length factor information associated with the location information acquired by the business system is greater than or equal to a preset time length threshold, the first payment code feedback message including a first payment code and a second payment code, and the payment waiting time length factor information including one or more than two of state information of a payment receiver, queuing time length information of the payment receiver, and historical waiting time information of a user transacting with the payment receiver. The display module is configured to display the first payment code and switch the displayed first payment code to the second payment code in a case where a trigger signal of a payment receiving terminal is sensed, so that the business system deducts a payment amount from a payment account indicated by the first information including information of the second payment code.

19. A service device, characterized by The method comprises the following steps: A processor and a memory storing computer program instructions; The processor executes the computer program instructions to implement the code scanning payment method according to any one of claims 1 to 8.

20. A user terminal, characterized by The method comprises the following steps: A processor and a memory storing computer program instructions; The processor executes the computer program instructions to implement the code scanning payment method according to any one of claims 9 to 16.

21. A code scanning payment system, characterized by, The method comprises the following steps: A user terminal and a business system are provided. The user terminal is configured to send a payment code request message including location information of the user terminal in response to a received payment operation. The business system is configured to receive the payment code request message, acquire payment waiting time length factor information associated with the location information, and send a first payment code feedback message including a first payment code and a second payment code in a case where a payment waiting time length represented by the payment waiting time length factor information associated with the location information is greater than or equal to a preset time length threshold, the payment waiting time length factor information including one or more than two of state information of a payment receiver, queuing time length information of the payment receiver, and historical waiting time information of a user transacting with the payment receiver. The user terminal is further configured to display the first payment code, and switch the displayed first payment code to the second payment code upon sensing a trigger signal from a payment receiving terminal; The business system is further configured to, in a case where the received payment request message comprises first information, instruct to deduct the payment amount from a payment account indicated by the first information, the first information comprising information of the second payment code.

22. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the code scanning payment method in any one of claims 1 to 16.

Images