TWI839876B - QR code payment method, user terminal, business equipment, system and medium - Google Patents

Abstract

The present invention 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 includes: receiving a payment code request message, the payment code request message includes the location information of the user terminal; obtaining the payment waiting time factor information associated with the location information; 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, sending a first payment code feedback message, the first payment code feedback message includes the first payment code and the second payment code, the user terminal displays the first payment code before sensing the trigger signal of the payment acceptance terminal, and switches the displayed first payment code to the second payment code when sensing the trigger signal; if the payment request message includes the first information, instructing to deduct the payment amount from the payee account indicated by the information of the second payment code. According to the embodiment of the present invention, the security of QR code payment can be improved.

Description

QR code payment method, user terminal, business equipment, system and medium

The present invention belongs to the field of data processing, and in particular relates to a code scanning payment method, a user terminal, business equipment, a system and a medium.

With the continuous development of payment technology, QR code payment has penetrated into various fields. QR code payment can include the main scan payment mode and the scanned payment mode. The main scan payment mode is a payment method in which the paying user scans the merchant's payment code. The scanned payment mode is a payment method in which the paying user's user terminal displays the payment code and the merchant accepts the payment by scanning the terminal.

In the scenario of using the scanned payment mode, in order to save payment time, the user will display the payment code on the user terminal in advance. While the user is waiting for payment, there is a possibility that the payment code is secretly photographed and used, which reduces the user's payment security.

The embodiment of the present invention provides a code scanning payment method, user terminal, business equipment, system and medium, which can improve the security of code scanning payment.

In a first aspect, an embodiment of the present invention provides a code scanning payment method, which is applied to a business system, and the method includes: receiving a payment code request message, the payment code request message is generated by a user terminal in response to a payment operation, and includes location information of the user terminal; obtaining payment waiting time factor information associated with the location information; when 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 includes the first payment code and the second payment code, 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 acceptance terminal, and switches the displayed first payment code to the second payment code when sensing the trigger signal; when the received payment request message includes the first information, instructs to deduct the payment amount from the payee account indicated by the first information, and the first information includes the information of the second payment code.

In a second aspect, an embodiment of the present invention provides a code scanning payment method, which is applied to a user terminal, and the method includes: in response to a received payment operation, sending a payment code request message, the payment code request message includes the location information of the user terminal; when the payment waiting time represented by the payment waiting time factor information associated with the location information obtained by the business system is greater than or equal to the preset time threshold, receiving a first payment code feedback message, the first payment code feedback message is generated by the business system, and includes a first payment code and a second payment code; displaying the first payment code, and in response to a trigger signal from the payment acceptance terminal, switching the displayed first payment code to the second payment code, so that the business system uses the first information to deduct the payment amount from the payee account indicated by the first information, and the first information includes information of the second payment code.

In a third aspect, an embodiment of the present invention provides a business device, comprising: a receiving module, used to receive a payment code request message, the payment code request message is generated by a user terminal in response to a payment operation, and includes location information of the user terminal; an obtaining module, used to obtain payment waiting time factor information associated with the location information; and a sending module, used to send a first payment code feedback message when the payment waiting time factor information associated with the location information is greater than or equal to a preset time threshold. The first payment code feedback message includes the first payment code and the second payment code, 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 acceptance terminal, and switches the displayed first payment code to the second payment code when sensing the trigger signal; the payment processing module is used to instruct the payment amount to be deducted from the payer account indicated by the first information when the received payment request message includes the first information, and the first information includes the information of the second payment code.

In a fourth aspect, an embodiment of the present invention provides a user terminal, including: a sending module, for responding to a received payment operation, sending a payment code request message, the payment code request message including the location information of the user terminal; a receiving module, for receiving a first 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 greater than or equal to a preset time threshold, the first payment code feedback message is generated by the business system, and includes a first payment code and a second payment code; a display module, for displaying the first payment code, and in response to a trigger signal from a payment acceptance terminal, switching the displayed first payment code to a second payment code, so that the business system uses the first information to deduct the payment amount from the payee account indicated by the first information, the first information including information of the second payment code.

In the fifth aspect, the embodiment of the present invention provides a business device, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the code scanning payment method of the first aspect is implemented.

In the sixth aspect, the embodiment of the present invention provides a user terminal, including: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the code scanning payment method of the second aspect is implemented.

In a seventh aspect, an embodiment of the present invention provides a code scanning payment system, comprising a user terminal and a business system; the user terminal is used to respond to a received payment operation by sending a payment code request message, the payment code request message including location information of the user terminal; the business system is used to receive the payment code request message, obtain payment waiting time factor information associated with the location information, and when 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, In this case, a first payment code feedback message is sent, and the first payment code feedback message includes the first payment code and the second payment code; the user terminal is also used to display the first payment code, and when sensing the trigger signal of the payment acceptance terminal, the displayed first payment code is switched to the second payment code; the business system is also used to instruct the deduction of the payment amount from the payee account indicated by the first information when the received payment request message includes the first information, and the first information includes the information of the second payment code.

In the eighth aspect, the embodiment of the present invention provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the code scanning payment method of the first aspect or the code scanning payment method of the second aspect is implemented.

The embodiment of the present invention provides a code scanning payment method, a user terminal, a business device, a system and a medium. The business system receives a payment code request message including the location information of the user terminal, and determines whether the payment waiting time indicated by the payment waiting time factor information is greater than or equal to a preset time threshold according to the payment waiting time factor information associated with the location information. If the payment waiting time indicated 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 is secretly photographed and stolen. The business system issues a first payment code and a second payment code to 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 acceptance terminal, and the second payment code is displayed on the user terminal when the user terminal senses the trigger signal sent by the payment acceptance terminal. The payment request message received by the business system includes information about the second payment code, indicating that the payment acceptance terminal scanned the second payment code. Since the second payment code is displayed only when the user terminal senses the trigger signal sent by the payment acceptance terminal, the possibility of being secretly photographed and stolen is very small, so normal payment is allowed to continue. Through the payment code issuance strategy corresponding to the payment waiting time and the switching of the first payment code and the second payment code, it is possible to effectively distinguish payments with higher security and improve the security of code scanning payment.

11: User terminal

12: Payment acceptance terminal

13: Payment institution system

14: Business system

15: Account management system

141: Payment code subsystem

142: Risk control subsystem

143: Clearing the operation metasystem

500:Business equipment

501: receiving module

502: Get module

503: Send module

504: Payment processing module

505: Judgment module

506: Intervention processing module

600,800:User terminal

601: Send module

602: Receiving module

603: Display module

604: Processing module

700:Business equipment

701,801:Memory

702,802:Processor

703,803: Communication interface

704,804:Bus

S201,S202,S203,S204,S205,S206,S207,S208,S209,S301,S302,S303,S304,S305,S306,S401,S402,S403,S404,S405,S406,S407,S408,S409,S410,S411,S412,S413,S414,S415,S416,S417,S418: Steps

In order to more clearly explain the technical solution of the embodiment of the present invention, the following will briefly introduce the diagrams required for use in the embodiment of the present invention. For ordinary technicians in this field, other diagrams can be obtained based on these diagrams without creative labor.

Figure 1 is a schematic diagram of an example of an application scenario of the code scanning payment method provided by an embodiment of the present invention; Figure 2 is a flow chart of an embodiment of the code scanning payment method provided by the first aspect of the present invention; Figure 3 is a flow chart of another embodiment of the code scanning payment method provided by the first aspect of the present invention; Figure 4 is a flow chart of another embodiment of the code scanning payment method provided by the first aspect of the present invention; Figure 5 is a flow chart of another embodiment of the code scanning payment method provided by the first aspect of the present invention; Figure 6 is a flow chart of an embodiment of the code scanning payment method provided by the second aspect of the present invention; Figure 7 is a flow chart of another embodiment of the code scanning payment method provided by the second aspect of the present invention; Figure 8 is a flow chart of another embodiment of the code scanning payment method provided by the second aspect of the present invention; 9 is a flowchart of an example of a code scanning payment process provided by an embodiment of the present invention; FIG. 10 is a structural schematic diagram of an embodiment of a business device provided by the third aspect of the present invention; FIG. 11 is a structural schematic diagram of another embodiment of a business device provided by the third aspect of the present invention; FIG. 12 is a structural schematic diagram of another embodiment of a business device provided by the third aspect of the present invention; FIG. 13 is a structural schematic diagram of an embodiment of a user terminal provided by the fourth aspect of the present invention; FIG. 14 is a structural schematic diagram of another embodiment of a user terminal provided by the fourth aspect of the present invention; FIG. 15 is a structural schematic diagram of an embodiment of a business device provided by the fifth aspect of the present invention; FIG. 16 is a structural schematic diagram of an embodiment of a user terminal provided by the sixth aspect of the present invention.

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

With the continuous development of payment technology, QR code payment has penetrated into various fields. QR code payment can include the main scan payment mode and the scanned payment mode. The main scan payment mode is a payment method in which the paying user scans the merchant's payment code. The scanned payment mode is a payment method in which the user terminal of the paying user displays the payment code, and the merchant accepts the terminal to scan the payment code. In the scenario of the scanned payment mode, in order to save payment time, the user will display the payment code on the user terminal in advance. However, while the user is waiting to pay, someone will secretly take a photo of the payment code displayed on the user terminal, and use the secretly photographed payment code to make a payment, causing theft of funds in the account of the user to whom the payment code belongs, seriously affecting the user's payment security.

The present invention provides a code scanning payment method, user terminal, business equipment, system and medium. When the payment waiting time at the location of the user terminal that needs to pay is long, such as when the queue for payment is long, two different payment codes can be issued to the user terminal. When the user terminal is not close to the payment acceptance terminal such as the point of sale device, i.e., POS machine, etc., the user terminal displays one of the payment codes, and when the user terminal is close to the payment acceptance terminal, the user terminal displays the other payment code. It is difficult for other people queuing around the user of the user terminal to take a picture of the other payment code. Therefore, when the payment request message received by the business system includes the information of the other payment code, normal payment can be allowed, thereby improving the payment security of the user.

The code scanning payment method in the embodiment of the present invention is applied to the scene of the scanned payment mode, which may involve the user terminal, the payment acceptance terminal, the payment institution system, the business system and the account management system. Figure 1 is a schematic diagram of an example of the application scenario of the code scanning payment method provided by the embodiment of the present invention. As shown in Figure 1, the architecture system of the scanning payment method may include a user terminal 11, a payment acceptance terminal 12, a payment institution system 13, a business system 14 and an account management system 15.

The user terminal 11 is a terminal device used by the user to make payments, which may include mobile phones, tablet computers, smart wearable devices, etc. The specific type of the user terminal 11 is not limited here. The user terminal 11 may be installed with a payment application, which can be used for payment. The user terminal 11 has a display function, which can display a payment code, so that payment can be made using the payment code. The payment code may be a QR code or other graphic code, etc., and its specific type is not limited here. The user terminal 11 can interact with the payment institution system 13 and apply for a payment code from the business system 14 through the payment institution system 13. In order to ensure the security of the payment code, the payment code has an expiration date. After the expiration date, the payment code cannot be used any more and needs to be updated.

The payment acceptance terminal 12 is a terminal device used by merchants to interact with the user terminal 11 during the payment process, which may specifically include a POS machine, etc. The specific type of the payment acceptance terminal 12 is not limited here. The payment acceptance terminal 12 may have a scanning function, which can scan the payment code to read the information contained in the payment code. The payment acceptance terminal 12 can initiate a payment request to the payment institution system 13.

The payment institution system 13 can be used for payment acquisition, and specifically can be the system of the acquisition institution. The payment institution system 13 can include one or more than two servers and other business equipment. Different servers and other business equipment in the payment institution system 13 can perform the same function in the payment institution system 13, or can perform different functions in the payment institution system 13, which is not limited here. The payment institution system 13 can transmit the payment request to the business system 14.

The business system 14 can be used to generate and issue payment codes, control payment risks, and perform clearing. The business system 14 may include multiple subsystems, for example, the business system 14 may include a payment code subsystem 141, a risk control subsystem 142, and a clearing operation subsystem 143. The business system 14 may issue the generated payment code to the user terminal 11 through the payment institution system 13. The business system 14 may include one or more business devices such as servers, and different business devices such as servers in the business system 14 may perform the same function in the business system 14 or different functions in the business system 14. When the business system 14 includes multiple servers and other business equipment, some of the servers and other business equipment may belong to the payment code subsystem 141, some of the servers and other business equipment may belong to the risk control subsystem 142, and some of the servers and other business equipment may belong to the clearing operation subsystem 143.

The account management system 15 is a system for managing user accounts, merchant accounts and other accounts. The account management system 15 can interact with the business system 14 to complete the deduction of payment accounts and the collection of payment accounts. The account management system 15 may include one or more servers and other business equipment. Different servers and other business equipment in the account management system 15 can perform the same function in the account management system 15, or they can perform different functions in the account management system 15, which is not limited here.

The following is a description of the code scanning payment method, user terminal, business equipment, system and medium in the present invention.

The first aspect of the present invention provides a code scanning payment method that can be applied to a business system, that is, the code scanning payment method can be executed by the business system, specifically, the code scanning payment method can be executed by a business device in the business system. FIG. 2 is a flow chart of an embodiment of the code scanning payment method provided by the first aspect of the present invention. As shown in FIG. 2, the code scanning payment method may include steps S201 to S204.

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

The payment code request message is used to request a payment code, which can be generated by the user terminal in response to a payment operation. The user terminal generates a payment code request message, which can be sent to the business system through the payment institution system. That is, the user terminal sends a payment code request message to the payment institution system, and the payment institution system then sends a 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, a user performs a payment operation on the user terminal, opens the payment application, and clicks on the "payment code" function. The user terminal responds to the payment operation and sends a payment code request message to the payment institution system.

The payment code request message includes location information of the user terminal. The location information of the user terminal may indicate the location of the user terminal. For example, the location information of the user terminal may include longitude and latitude information of the location of the user terminal.

In step S202, payment waiting time factor information associated with location information is obtained.

After obtaining the location information from the payment code request message, obtain the payment waiting time factor information associated with the location information. The payment waiting time factor information associated with the location information may include the payment waiting time factor information of the merchant at the location indicated by the location information, the payment waiting time factor information of the area where the location indicated by the location information is located, etc. The payment waiting time factor information includes factor information that affects the payment waiting time, which can reflect the payment waiting time. The payment waiting time can also be regarded as the payment queue length.

In some examples, the payment waiting time factor information may include one or more of the payee's status information, the payee's queue time information, the user's historical waiting time information for transactions with the payee, etc.

The payee's status information may indicate how busy the payee is. The busier the payee is, the longer the payment waiting time may be for the payee. The payee's queue time information may indicate the payee's queue time. The longer the queue time is, the longer the payment waiting time will be. The historical waiting time information of the user who transacts with the payee may include historical information related to the payment waiting of the user who transacts with the payee. The payment waiting time is determined by the information of the user who transacts with the payee. For example, historical waiting time information may include payment code request time and 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 pays. The time between a user's payment code request time and payment time can be used as the user's payment waiting time. The payment waiting time of a payee can be determined based on the time between the payment code request time and payment time of multiple users who have transactions with a payee.

In step S203, when the payment waiting time indicated 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 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 acceptance terminal, and switches the displayed first payment code to the second payment code when sensing the trigger signal; the preset time threshold is a threshold value for determining the time that causes security risks, which can be set according to the scene, demand, experience, etc., and is not limited here. When the payment waiting time indicated 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 a payment code issuance measure with higher security needs to be implemented. The payment waiting time indicated by the payment waiting time factor information is less than the preset time threshold, indicating that the security risk is small and can be ignored.

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 then sends a first payment code feedback message to the user terminal. The first payment code feedback message includes the first payment code and the second payment code. The first payment code is different from the second payment code.

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, and may display the first payment code first and save the second payment code. The payment acceptance terminal may send a trigger signal. When the payee user carries the user terminal and is still in the queue but has not yet arrived at the payment acceptance terminal, the user terminal does not sense the trigger signal sent by the payment acceptance terminal. Before the user terminal senses the trigger signal, that is, before the user terminal senses the trigger signal, the user terminal displays the first payment code. When the payee user carries the user terminal to the payment acceptance terminal, the user terminal senses the trigger signal sent by the payment acceptance terminal and may switch the displayed first payment code to the second payment code, so that the payment acceptance terminal scans the second payment code.

In some examples, the trigger signal may include one or more of the following: Near Field Communication (NFC) signal, Bluetooth signal, sound wave signal, etc. The NFC signal may include information of an encrypted NFC tag of the payment acceptance terminal. The Bluetooth signal may include information of a Bluetooth tag of the payment acceptance terminal. The sound wave signal may include information of a sound wave tag, and the sound wave signal may also be a low-frequency sound wave signal of a specific frequency.

In step S204, when the received payment request message includes the first information, it is indicated to deduct the payment amount from the payer account indicated by the first information.

After the payment acceptance terminal scans the payment code displayed on the user terminal, it will generate a payment request message based on the information read from the payment code. The payment request message includes the information read from the payment code. The payment acceptance terminal sends the payment request message to the payment institution system, and the payment institution system then sends the payment request message to the business system.

The first information includes information about the second payment code, and the information about the second payment code is information obtained from the second payment code. The payment request message received by the business system includes the first information, indicating that in this scan code payment, the payment acceptance terminal scanned the second payment code, that is, the payment acceptance terminal scanned the second payment code that was switched only when the user terminal arrived at the payment acceptance terminal. The security risk of this scan code payment is relatively small, and the payment is allowed 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 payee account indicated by the first information.

In the embodiment of the present invention, the business system receives a payment code request message including the location information of the user terminal, and determines whether the payment waiting time indicated by the payment waiting time factor 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 indicated 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 is secretly photographed and stolen. The business system issues a first payment code and a second payment code to 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 acceptance terminal, and the second payment code is displayed on the user terminal when the user terminal senses the trigger signal sent by the payment acceptance terminal. The payment request message received by the business system includes information about the second payment code, indicating that the payment acceptance terminal scanned the second payment code. Since the second payment code is displayed only when the user terminal senses the trigger signal sent by the payment acceptance terminal, the possibility of being secretly photographed and stolen is very small, so normal payment is allowed to continue. Through the payment code issuance strategy corresponding to the payment waiting time and the switching between the first payment code and the second payment code, it is possible to effectively distinguish payments with higher security, improving the security of scanning code payment.

The switching between the first payment code and the second payment code is actively executed by the user terminal without user participation, which can reduce user operations and improve the efficiency of scan code payment on the basis of ensuring the security of scan code payment. Moreover, compared with the technical solution of shortening the validity period of the payment code, the embodiment of the present invention does not need to frequently update and issue the payment code, and can also reduce the processing pressure of the business system that generates and issues the payment code on the basis of ensuring the security of scan code payment.

In some embodiments, whether the payment waiting time factor satisfies the dual code issuance conditions can be used to determine whether the payment waiting time is greater than or equal to the preset time threshold. FIG3 is a flow chart of another embodiment of the code scanning payment method provided by the first aspect of the present invention. FIG3 differs from FIG2 in that the code scanning payment method shown in FIG3 can also include step S205.

In step S205, when the payment waiting time factor information associated with the location information meets the dual code issuance conditions, 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.

The dual code sending condition includes a condition for determining whether the payment under the payment waiting time factor information condition has a risk of the payment code being secretly photographed and stolen. If the payment waiting time factor information associated with the location information satisfies the dual code sending 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, indicating that the payment under the payment waiting time factor information condition has a risk of the payment code being secretly photographed and stolen, the first payment code and the second payment code may be sent 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 meet the dual code issuance conditions. 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, indicating that the payment under the payment waiting time factor information condition does not have the risk of the payment code being secretly photographed and stolen, and a payment code can be issued to the user terminal.

The specific content of the payment waiting time factor information can be found in the relevant descriptions in the above embodiments, and will not be elaborated here.

In some examples, the dual code issuance conditions may include one or more of the following: the status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is busy with payment; the status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is in an event holding state; the queue time information of the payee associated with the location information indicates that the queue time of the payee in the 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 who transacts with the payee associated with the location information is greater than or equal to the preset time threshold.

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

The payee's status information indicates that the payee is busy with payment collection. There are many payer users waiting for payment at the payee. Correspondingly, the payment waiting time of the payer users is longer. That is, the payment waiting time indicated by the payment waiting time factor information is greater than or equal to the preset time threshold. The payment code of the payer user may be secretly photographed and stolen, and the first payment code and the second payment code need to be issued to the user terminal.

The payee's status information indicates that the payee is in an activity state. If there are more payer users waiting for payment at the payee, the payer users will have a longer waiting time for payment. That is, the payment waiting time indicated by the payment waiting time factor information is greater than or equal to the preset time threshold. The payer user's payment code may be secretly photographed and stolen, and the first payment code and the second payment code need to be issued to the user terminal. The activities held by the payee can be promotional or preferential activities, etc., which are not limited here.

The queue time of the payee represented by the queue time information is basically the same as the payment waiting time. The longer the queue time, the longer the payment waiting time. The queue time information of the payee represents that the queue time of the payee is greater than or equal to the preset time threshold, that is, the payment waiting time represented by the payment waiting time factor information is greater than or equal to the preset time threshold. The payment code of the payee user may be secretly photographed and stolen, and the first payment code and the second payment code need to be issued to the user terminal.

The time between the payment code request time and the payment time of the user of the payee transaction is the payment waiting time. If 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 represented by the payment waiting time factor information is greater than or equal to the preset time threshold, the payment code of the payee user may be secretly photographed and stolen, and the first payment code and the second payment code need to be issued to the user terminal.

In some embodiments, the first payment code displayed by the user terminal may be secretly photographed and used for payment, or, because there is a certain delay in the user terminal switching from the first payment code to the second payment code, the payment acceptance terminal still scans the first payment code. In order to accurately distinguish the payment with the risk of being secretly photographed and used, further judgment can be made based on the transaction information included in the payment request message, and corresponding processing can be performed based on the judgment result. Figure 4 is a flow chart of another embodiment of the code scanning payment method provided by the first aspect of the present invention. The difference between Figure 4 and Figure 2 is that the code scanning payment method shown in Figure 4 can also include step S206 and step S207.

In step S206, when the received payment request message includes the second information, if the transaction information meets the risk control conditions, transaction intervention processing is performed.

The second information includes the information of the first payment code, which is the information obtained from the first payment code. The payment request message received by the business system includes the second information, indicating that in this scan code payment, the first payment code is scanned by the payment acceptance terminal. However, the first payment code scanned by the payment acceptance terminal may be the first payment code secretly photographed and stolen by others, or it may be the first payment code that has not been switched due to a delay in the user's terminal switching payment code. However, the payment of the first payment code secretly photographed and stolen by others is an illegal payment, and the first payment code that has not been switched due to a delay in the user's terminal switching payment code is a legal payment. Whether the transaction information included in the payment request message meets the risk control conditions can be used to further distinguish illegal payments from legal payments.

The risk control condition is used to determine whether the payment indicated by the second information has the risk of theft, and the transaction intervention process is used to safely process the payment with the risk of theft.

In some examples, the transaction information includes one or more of the following: the payee's merchant address, the payment amount, and the payment frequency. The payment frequency is the frequency of payment using the first payment code corresponding to the second information.

Risk control conditions include one or more of the following: The distance between the location of the merchant address of the payee and the location indicated by the location information is greater than the safety distance threshold; the payment amount is greater than the safety amount threshold; the payment frequency is higher than the safety frequency threshold.

If the transaction information meets the risk control conditions, it means that the payment corresponding to the transaction information has the risk of theft and transaction intervention is required.

In some cases of secretly photographing and stealing payment codes, the person who secretly photographed the payment code will send the secretly photographed payment code to other people, who will then make payments at payees at other locations. The distance between the payee's merchant address and the location indicated by the user's terminal location information in the payment code request message and the safety distance threshold can be used to determine whether the payment is an illegal payment made at a payee at another location using the first secretly photographed payment code. The safety distance threshold is a safety threshold for determining whether the payment is made at the same location, which can be set based on the scenario, needs, experience, etc., and is not limited here. The distance between the payee's merchant address and the location indicated by the location information is greater than the safety distance threshold, indicating that the location where the payment code was applied and the location where the payment was made are far apart and are not in the same location. This is likely to be an illegal payment that involves secretly photographing and stealing the payment code, and transaction intervention is required.

The payment amount can also be used to help improve the security of QR code payment. The safety amount threshold is the threshold for judging whether the payment amount is safe. It can be set according to the scene, needs, experience, etc., and is not limited here. If the payment amount is greater than the safety amount threshold, if the payment code is secretly photographed and stolen, it may cause a large loss, and transaction intervention is required.

The payment frequency can also be used to help improve the security of QR code payment. The safety frequency threshold is the threshold value for judging whether the payment frequency is safe. It can be set according to the scene, needs, experience, etc., and is not limited here. If the payment frequency is higher than the safety frequency threshold, if the payment code is secretly photographed and stolen, it may cause greater losses and transaction intervention is required.

In the case where the risk control conditions include more than two conditions, the risk control conditions may have a priority order, and the transaction information may be judged first whether it satisfies the risk control conditions with a relatively high priority order. If the transaction information satisfies the risk control conditions with a relatively high priority order, the transaction intervention process may be performed; if the transaction information does not satisfy the risk control conditions with a relatively high priority order, the transaction information may be judged whether it satisfies the risk control conditions with a relatively low priority order. For example, the risk control conditions include the distance between the location of the merchant address of the payee and the location indicated by the location information being greater than the safety distance threshold, and the payment amount being greater than the safety amount threshold; if the distance between the location of the merchant address of the payee and the location indicated by the location information is greater than the safety distance threshold, transaction intervention processing can be performed without further determining whether the payment amount is greater than the safety amount threshold; if the distance between the location of the merchant address of the payee and the location indicated by the location information is less than or equal to the safety distance threshold, then determine whether the payment amount is greater than the safety amount threshold, and if the payment amount is greater than the safety amount threshold, transaction intervention processing can be performed.

The transaction intervention process may include: verifying the identity of the user of the user terminal that sends the payment request message including the second information; or terminating the payment indicated by the second information.

In the event that the payment indicated by the second information has a risk of theft, the business system may verify the identity of the user who uses the first payment code corresponding to the second information to make payment. Specifically, the business system may send an identity verification request message to the payment institution system, and the payment institution system then sends an identity verification request message to the user terminal. In response to the received identity verification request message, the user terminal may display an identity verification interface to prompt the user to enter the identity verification information. The identity verification information may include payment account number, payment password, verification code, etc., which can prove that the user who requested the payment code is the one who made the payment, and is not limited here. The user terminal sends the identity verification information to the payment institution system, and the payment institution system sends the identity verification information to the business system. The business system verifies whether the received identity verification information is consistent with the reserved or set identity verification information. If they are consistent, the payment can continue normally. If they are inconsistent, the payment will be suspended.

If there is a risk of theft in the payment indicated by the second information, the payment indicated by the second information can also be directly suspended to avoid the risk of theft.

In step S207, when the received payment request message includes the second information, if the transaction information does not meet the risk control conditions, it is indicated to deduct the payment amount from the payer account indicated by the second information.

If the transaction information does not meet the risk control conditions, it means that the payment corresponding to the transaction information does not have the risk of theft, and transaction intervention can be omitted and payment can 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 second information.

Through transaction messages and risk control conditions, the effectiveness of risk monitoring can be improved, the accuracy of identifying payments with theft risks can be improved, and the security of QR code payment can be further improved.

In some embodiments, the payment waiting time is less than the preset time threshold, and the risk of the payment code of the payee being secretly photographed and stolen is small and negligible. The business system can issue a single payment code to the user terminal, and on the basis of ensuring the security of the code scanning payment, the pressure of the business system to generate and issue the payment code is further reduced. FIG5 is a flow chart of another embodiment of the code scanning payment method provided by the first aspect of the present invention. The difference between FIG5 and FIG2 is that the code scanning payment method shown in FIG5 can also include step S208 and step S209.

In step S208, when the payment waiting time represented by the payment waiting time factor information associated with the location information is less than the preset time threshold, a second payment code feedback message is sent so that the user terminal receives the second payment code feedback message and displays the third payment code.

The second payment code feedback message includes the third payment code. That is, when the payment waiting time represented by the payment waiting time factor information associated with the location information is less than the preset time threshold, the risk of the payment code being secretly photographed and stolen is considered small and can be ignored. The business system can issue a single payment code, namely the third payment code, to the user terminal. The user terminal displays the third payment code within the validity period of the third payment code and does not trigger the switching of the payment code.

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

In step S209, when the received payment request message includes the third information, it is instructed to deduct the payment amount from the payee account indicated by the third information.

The third information includes the information of the third payment code, which is the information obtained from the third payment code. The payment request message received by the business system includes the third information, which indicates that in this scan code payment, the payment acceptance terminal scanned the third payment code. The third payment code is issued when the risk of stealing the payment code is relatively small, indicating that the security risk of this scan code payment is relatively small, and the payment is allowed 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 payee account indicated by the third information.

When the risk of the payment code being secretly photographed and stolen is determined to be low based on the payment waiting time factor information associated with the location information, the business system issues a single payment code to the user terminal. This can reduce the pressure on the business system to generate and issue payment codes while ensuring the security of scan code payment.

The second aspect of the present invention provides a code scanning payment method that can be applied to a user terminal, that is, the code scanning method can be executed by the user terminal. FIG6 is a flow chart of an embodiment of the code scanning payment method provided by the second aspect of the present invention. As shown in FIG6, the code scanning payment method may include steps S301 to S303.

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

The payment code request message includes the location information of the user terminal. Specifically, the user terminal may first send a payment code request message to the payment institution system, and the payment institution system then sends a payment code request message to the business system.

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

The first payment code feedback message is generated by the business system. The first payment code feedback message includes the first payment code and the second payment code. Specifically, the business system may first send the first payment code feedback message to the payment institution system, and then the payment institution system may send the first payment code feedback message to the user terminal.

In step S303, the first payment code is displayed, and when the trigger signal of the payment acceptance terminal is sensed, the displayed first payment code is switched to the second payment code, so that the business system uses the first information to deduct the payment amount from the payee account indicated by the first information.

After receiving the first payment code feedback message, the user terminal will display the first payment code before sensing the trigger signal of the payment acceptance terminal. When sensing the trigger signal of the payment acceptance terminal, it will switch to display the second payment code.

The first information includes the information of the second payment code.

In some examples, the trigger signal includes one or more of the following: near field communication signal, Bluetooth signal, sound wave signal. For details, please refer to the relevant description in the above embodiments, which will not be elaborated here.

The specific contents of the above steps S301 to S303 can be found in the relevant descriptions in the above embodiments, and will not be elaborated here.

In an embodiment of the present invention, a user terminal can request a payment code from a business system through a payment code request message. The payment code request message includes location information, which can reflect the location of the user terminal when applying for the payment code. The business system determines whether the payment waiting time represented by the payment waiting time factor information is greater than or equal to a preset time threshold based on 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 has been secretly photographed and stolen. 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 from the payment acceptance terminal. When the user terminal senses the trigger signal from the payment acceptance terminal, the displayed payment code is switched to the second payment code, so that when the user terminal makes payment at the payment acceptance terminal, the payment acceptance terminal scans the second payment code, and the payment can be continued normally through the business system using the information of the second payment code. Since the second payment code is displayed only when the user terminal senses the trigger signal from the payment acceptance terminal, the possibility of being secretly photographed and stolen is very small, so normal payment is allowed to continue. Through the payment code issuance strategy corresponding to the payment waiting time and the switching of the first payment code and the second payment code, it is possible to effectively distinguish the payment with higher security and improve the security of code scanning payment.

The switching between the first payment code and the second payment code is actively executed by the user terminal without user participation, which can reduce user operations and improve the efficiency of scan code payment on the basis of ensuring the security of scan code payment. Moreover, compared with the technical solution of shortening the validity period of the payment code, the embodiment of the present invention does not need to frequently update and issue the payment code, and can also reduce the processing pressure of the business system that generates and issues the payment code on the basis of ensuring the security of scan code payment.

In some embodiments, when the payment waiting time factor information associated with the location information meets the dual-code issuance conditions, 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.

Payment waiting time factor information includes one or more of the payee's status information, the payee's queue time information, and the historical waiting time information of the user who transacts with the payee. Among them, the historical waiting time information includes the payment code request time and the payment time.

The conditions for issuing dual codes include one or more of the following: the status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is busy collecting payments; the status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is in an event holding state; the queue time information of the payee associated with the location information indicates that the queue time of the payee in the 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 who transacts with the payee associated with the location information is greater than or equal to the preset time threshold.

The specific contents of the payment waiting time factor information associated with the location information, the conditions for issuing the dual code, etc. can be found in the relevant descriptions in the above embodiments, and will not be elaborated here.

In some embodiments, the payment receiving terminal may also read the first payment code, and the transaction information and risk control conditions in the payment request message may be further used to distinguish whether the payment corresponding to the first payment code is a payment with high security risk. FIG7 is a flow chart of another embodiment of the code scanning payment method provided by the second aspect of the present invention. FIG7 differs from FIG6 in that the code scanning payment method shown in FIG7 may also include step S304.

In step S304, when the first payment code is read by the payment acceptance terminal, if the transaction information in the payment request message sent by the payment acceptance terminal to the business system meets the risk control conditions, the transaction intervention process is accepted.

The risk control condition is used to determine whether the payment indicated by the second information has the risk of theft. The second information includes information of the first payment code. The transaction intervention process is used to safely process payments that have the risk of theft.

The specific content of step S304 can be found in the relevant description in the above embodiment, which will not be elaborated here.

In some examples, the transaction information includes one or more of the following: the merchant address of the payee, the payment amount, and the payment frequency. The specific content of the transaction information can be found in the relevant descriptions in the above embodiments, and will not be elaborated here.

In some examples, the risk control conditions include one or more of the following: the distance between the location of the payee's merchant address and the location indicated by the location information is greater than the safety distance threshold; the payment amount is greater than the safety amount threshold; the payment frequency is higher than the safety frequency threshold.

The specific contents of the risk control conditions can be found in the relevant descriptions in the above embodiments, and will not be elaborated here.

In some examples, the transaction intervention process includes: verifying the identity of the user at the user terminal; or terminating the payment indicated by the second information.

The specific content of transaction intervention processing can be found in the relevant descriptions in the above embodiments, and will not be elaborated here.

In some embodiments, when the first payment code is read by the payment acceptance terminal, 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, the payment indicated by the second information proceeds normally.

The specific content of the payment when the transaction information in the payment request message sent by the above payment acceptance terminal to the business system does not meet the risk control conditions can be found in the relevant descriptions in the above embodiments, which will not be elaborated here.

In some embodiments, the payment waiting time is less than the preset time threshold, and the risk of the payee's payment code being secretly photographed and stolen is small and negligible, and the business system can issue a single payment code to the user terminal. FIG8 is a flow chart of another embodiment of the code scanning payment method provided by the second aspect of the present invention. FIG8 differs from FIG6 in that the code scanning payment method shown in FIG8 can also include step S305 and step S306.

In step S305, 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 the preset time threshold, a second payment code feedback message is received.

The second payment code feedback message includes the third payment code.

In step S306, the third payment code is displayed so that the business system uses the third information to deduct the payment amount from the payee account indicated by the third information.

The third information includes the information of the third payment code.

The specific contents of step S305 to step S306 can be found in the relevant descriptions in the above embodiments, and will not be elaborated here.

In order to facilitate understanding of the code scanning payment method in the embodiment of the present invention, the following takes the example of the business system issuing two payment codes, namely the first payment code and the second payment code, at one time to illustrate the code scanning payment process between the user terminal, the payment acceptance terminal, the payment institution system, the business system and the account management system. FIG9 is a flowchart of an example of the code scanning payment process provided by the embodiment of the present invention. As shown in FIG9, the overall code scanning payment process may include steps S401 to S418.

In step S401, the user terminal responds to the user's payment operation and sends a payment code request message to the payment institution system.

In step S402, the payment institution system sends a payment code request message to the business system.

In step S403, the business system obtains payment waiting time factor information associated with the location information in the payment code request message.

In step S404, the business system determines whether the payment waiting time factor information meets the dual code issuance conditions.

In step S405, if the dual-code issuance conditions are met, 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.

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

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

In step S408, when the user terminal senses the trigger signal sent by the payment acceptance terminal, the user terminal switches to display the second payment code.

In step S409, the payment acceptance terminal scans the payment code displayed on the user terminal and reads the payment code information.

In step S410, the payment acceptance terminal sends a payment request message to the payment institution system. The payment request message includes transaction information and the information of the payment code obtained.

In step S411, the payment institution system sends a payment request message to the business system.

In step S412, the business system identifies whether the payment code information in the payment request message is the information of the first payment code or the information of the second payment code. If the payment code information in the payment request message is the information of the second payment code, jump to step S413; if the payment code information in the payment request message is the information of the first payment code, jump to step S415.

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

In step S414, the account management system responds to the transaction message and deducts the payment amount from the payer's account indicated by the information of the second payment code.

In step S415, the business system determines whether the transaction information meets the risk control conditions. If the transaction information meets the risk control conditions, jump to step S416; if the transaction information does not meet the risk control conditions, jump to step S417.

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

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

In step S418, the account management system responds to the transaction message and deducts the payment amount from the payer account indicated by the information of the first payment code.

The specific contents of the above steps S401 to S418 can be found in the relevant contents of the above embodiments, which will not be elaborated here.

The third aspect of the present invention provides a business device. FIG10 is a schematic diagram of the structure of an embodiment of the business device provided in the third aspect of the present invention. As shown in FIG10, the business device 500 may include a receiving module 501, an acquisition module 502, a sending module 503 and a payment processing module 504.

The receiving module 501 may be used to receive a payment code request message.

The payment code request message is generated by the user terminal in response to a payment operation and includes the user terminal's location information.

The acquisition module 502 can be used to obtain payment waiting time factor information associated with location information.

The sending module 503 can be used to send a first payment code feedback message 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, 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 acceptance terminal, and switches the displayed first payment code to the second payment code when sensing the trigger signal.

The first payment code feedback message includes the first payment code and the second payment code.

In some examples, the trigger signal includes one or more of the following: a near field communication signal, a Bluetooth signal, or a sonic signal.

The payment processing module 504 may be used to instruct, when the received payment request message includes the first information, to deduct the payment amount from the payer account indicated by the first information.

The first information includes the information of the second payment code.

In the embodiment of the present invention, the business system receives a payment code request message including the location information of the user terminal, and determines whether the payment waiting time indicated by the payment waiting time factor 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 indicated 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 is secretly photographed and stolen. The business system issues a first payment code and a second payment code to 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 acceptance terminal, and the second payment code is displayed on the user terminal when the user terminal senses the trigger signal sent by the payment acceptance terminal. The payment request message received by the business system includes information about the second payment code, indicating that the payment acceptance terminal scanned the second payment code. Since the second payment code is displayed only when the user terminal senses the trigger signal sent by the payment acceptance terminal, the possibility of being secretly photographed and stolen is very small, so normal payment is allowed to continue. Through the payment code issuance strategy corresponding to the payment waiting time and the switching between the first payment code and the second payment code, it is possible to effectively distinguish payments with higher security and improve the security of scanning payment.

The switching between the first payment code and the second payment code is actively executed by the user terminal without user participation, which can reduce user operations and improve the efficiency of scan code payment on the basis of ensuring the security of scan code payment. Moreover, compared with the technical solution of shortening the validity period of the payment code, the embodiment of the present invention does not need to frequently update and issue the payment code, and can also reduce the processing pressure of the business system that generates and issues the payment code on the basis of ensuring the security of scan code payment.

FIG11 is a schematic diagram of the structure of another embodiment of the business device provided by the third aspect of the present invention. The difference between FIG11 and FIG10 is that the business device 500 shown in FIG11 may also include a determination module 505.

The determination module 505 can be used to determine whether the payment waiting time factor information associated with the location information is greater than or equal to the preset time threshold when the payment waiting time factor information associated with the location information meets the dual code issuance condition.

Payment waiting time factor information includes one or more of the payee's status information, the payee's queue time information, and the historical waiting time information of the user who transacts with the payee. Among them, the historical waiting time information includes the payment code request time and the payment time.

The conditions for issuing dual codes include one or more of the following: the status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is busy collecting payments; the status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is in an event holding state; the queue time information of the payee associated with the location information indicates that the queue time of the payee in the 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 who transacts with the payee associated with the location information is greater than or equal to the preset time threshold.

FIG12 is a schematic diagram of the structure of another embodiment of the business equipment provided by the third aspect of the present invention. The difference between FIG12 and FIG10 is that the business equipment 500 shown in FIG12 may also include an intervention processing module 506.

The intervention processing module 506 can be used to perform transaction intervention processing when the received payment request message includes the second information and the transaction information meets the risk control conditions.

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 whether the payment indicated by the second information has the risk of theft. The transaction intervention process is used to safely process payments with the risk of theft.

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

In some examples, the risk control conditions include one or more of the following: the distance between the location of the payee's merchant address and the location indicated by the location information is greater than the safety distance threshold; the payment amount is greater than the safety amount threshold; the payment frequency is higher than the safety frequency threshold.

In some examples, the transaction intervention processing performed by the intervention processing module 506 may include: verifying the identity of the user of the user terminal that sends the payment request message including the second information; or suspending the payment indicated by the second information.

In some embodiments, the payment processing module 504 can also be used to instruct the payment amount to be deducted from the payer account indicated by the second information if the transaction information does not meet the risk control conditions when the received payment request message includes the second information.

In some embodiments, the sending module 503 can also be used to send a second payment code feedback message when the payment waiting time represented by the payment waiting time factor information associated with the location information is less than a preset time threshold, so that the user terminal receives the second payment code feedback message and displays the third payment code.

The second payment code feedback message includes the third payment code.

The payment processing module 504 can also be used to instruct the payment amount to be deducted from the payer account indicated by the third information when the received payment request message includes the third information.

The third information includes the information of the third payment code.

The fourth aspect of the present invention provides a user terminal. FIG13 is a schematic structural diagram of an embodiment of the user terminal provided in the fourth aspect of the present invention. As shown in FIG13, the user terminal 600 may include a sending module 601, a receiving module 602 and a display module 603.

The sending module 601 may be used to send a payment code request message in response to a received payment operation.

The payment code request message includes the location information of the user's terminal.

The receiving module 602 can be used to receive the first 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 greater than or equal to the preset time threshold.

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

The display module 603 can be used to display the first payment code, and when sensing the trigger signal of the payment acceptance terminal, the displayed first payment code is switched to the second payment code, so that the business system uses the first information to deduct the payment amount from the payer account indicated by the first information.

The first information includes the information of the second payment code.

In some examples, the trigger signal includes one or more of the following: a near field communication signal, a Bluetooth signal, or a sonic signal.

In the embodiment of the present invention, 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 reflect the location of the user terminal when applying for the payment code. The business system determines whether the payment waiting time represented by the payment waiting time factor information is greater than or equal to the preset time threshold based on 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 is secretly photographed and stolen. 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 from the payment acceptance terminal. When the user terminal senses the trigger signal from the payment acceptance terminal, the displayed payment code is switched to the second payment code, so that when the user terminal makes payment at the payment acceptance terminal, the payment acceptance terminal scans the second payment code, and the payment can be continued normally through the business system using the information of the second payment code. Since the second payment code is displayed only when the user terminal senses the trigger signal from the payment acceptance terminal, the possibility of being secretly photographed and stolen is very small, so normal payment is allowed to continue. Through the payment code issuance strategy corresponding to the payment waiting time and the switching between the first payment code and the second payment code, it is possible to effectively distinguish payments with higher security and improve the security of scanning code payment.

The switching between the first payment code and the second payment code is actively executed by the user terminal without user participation, which can reduce user operations and improve the efficiency of scan code payment on the basis of ensuring the security of scan code payment. Moreover, compared with the technical solution of shortening the validity period of the payment code, the embodiment of the present invention does not need to frequently update and issue the payment code, and can also reduce the processing pressure of the business system that generates and issues the payment code on the basis of ensuring the security of scan code payment.

In some embodiments, when the payment waiting time factor information associated with the location information meets the dual-code issuance conditions, 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.

Payment waiting time factor information includes one or more of the payee's status information, the payee's queue time information, and the historical waiting time information of the user who transacted with the payee. The historical waiting time information includes the payment code request time and payment time.

The conditions for issuing dual codes include one or more of the following: the status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is busy collecting payments; The status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is in an event holding state; The queue time information of the payee associated with the location information indicates that the queue time of the payee in the 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 who transacts with the payee associated with the location information is greater than or equal to the preset time threshold.

FIG14 is a schematic structural diagram of another embodiment of the user terminal provided in the fourth aspect of the present invention. FIG14 is different from FIG13 in that the user terminal 600 shown in FIG14 may also include a processing module 604.

Processing module 604 can be used to accept transaction intervention processing when the first payment code is read by the payment acceptance terminal and the transaction information in the payment request message sent by the payment acceptance terminal to the business system meets the risk control conditions.

The risk control condition is used to determine whether the payment indicated by the second information has the risk of theft. The second information includes the information of the first payment code. The transaction intervention process is used to safely process the payment with the risk of theft.

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

In some examples, the risk control conditions include one or more of the following: the distance between the location of the payee's merchant address and the location indicated by the location information is greater than the safety distance threshold; the payment amount is greater than the safety amount threshold; the payment frequency is higher than the safety frequency threshold.

In some examples, the transaction intervention process includes: authenticating the user of the user terminal; or terminating the payment indicated by the second information.

In some embodiments, when the first payment code is read by the payment acceptance terminal, 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, the payment indicated by the second information proceeds normally.

In some embodiments, the receiving module 602 can 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.

The second payment code feedback message includes the third payment code

The 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.

The third information includes the information of the third payment code.

The fifth aspect of the present invention also provides a business device. FIG15 is a schematic diagram of the structure of an embodiment of the business device provided in the fifth aspect of the present invention. As shown in FIG15, the business device 700 includes a memory 701, a processor 702, and a computer program stored in the memory 701 and executable on the processor 702.

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

The memory 701 may 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., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described in the scanning code payment method in the embodiment according to the first aspect of the present invention.

The processor 702 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 701, so as to implement the code scanning payment method in the embodiment of the first aspect mentioned above.

In one example, the business device 700 may also include a communication interface 703 and a bus 704. As shown in FIG15 , the memory 701, the processor 702, and the communication interface 703 are connected via the bus 704 and communicate with each other.

The communication interface 703 is mainly used to realize the communication between the modules, devices, units and/or equipment in the embodiment of the present invention. The input device and/or output device can also be connected through the communication interface 703.

Bus 704 includes hardware, software, or both, coupling components of business device 700 to each other. By way of example and not limitation, bus 704 may 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 (Serial Advanced Technology Attachment), or a Serial Advanced Technology Attachment (Serial Advanced Technology Attachment). Attachment, SATA) bus, Video Electronics Standards Association Local Bus (VLB) bus or other suitable bus or a combination of two or more of the above. Where appropriate, bus 704 may include one or more buses. Although the embodiments of the present invention describe and illustrate specific buses, the present invention contemplates any suitable bus or interconnect.

The sixth aspect of the present invention also provides a user terminal. FIG16 is a schematic structural diagram of an embodiment of the user terminal provided in the sixth aspect of the present invention. As shown in FIG16, 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.

In one example, the processor 802 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present invention.

The memory 801 may 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., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described in the scanning code payment method in the embodiment according to the second aspect of the present invention.

The processor 802 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 801, so as to implement the scanning payment method in the embodiment of the second aspect mentioned above.

In one example, the user terminal 800 may also include a communication interface 803 and a bus 804. As shown in FIG16 , the memory 801, the processor 802, and the communication interface 803 are connected via the bus 804 and communicate with each other.

The communication interface 803 is mainly used to realize the communication between the modules, devices, units and/or equipment in the embodiment of the present invention. The input device and/or output device can also be connected through the communication interface 803.

The bus 804 includes hardware, software, or both, coupling the components of the user terminal 800 to each other. By way of example and not limitation, bus 804 may 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 (Serial Advanced Technology Attachment), or a Serial Advanced Technology Attachment (Serial Advanced Technology Attachment). Attachment, SATA) bus, Video Electronics Standards Association Local Bus (VLB) bus or other suitable bus or a combination of two or more of the above. Where appropriate, bus 804 may include one or more buses. Although the embodiments of the present invention describe and illustrate specific buses, the present invention contemplates any suitable bus or interconnect.

The seventh aspect of the present invention provides a code scanning payment system, which may include a business system and a user terminal.

The user terminal is used to respond to the received payment operation and send a payment code request message, which includes the location information of the user terminal.

The business system is used to receive a payment code request message, obtain payment waiting time factor information associated with location information, and send a first payment code feedback message when the payment waiting time factor information associated with location information is greater than or equal to a preset time threshold. The first payment code feedback message includes a first payment code and a second payment code.

The user terminal is also used to display the first payment code, and when a trigger signal from the payment acceptance terminal is sensed, the displayed first payment code is switched to the second payment code.

The business system is also used to instruct the payment amount to be deducted from the payer account indicated by the first information when the received payment request message includes the first information, and the first information includes the information of the second payment code.

The specific content of the business system can be found in the business system 14 in the above embodiment and the relevant description of the business system in the code scanning payment method in the above embodiment, which will not be repeated here. The business system may include business equipment, and the specific content of the business equipment can be found in the relevant description of the business equipment 500 and the business equipment 700 in the above embodiment, which will not be repeated here.

The specific content of the user terminal can be found in the user terminal 11 in the above embodiment, the user terminal in the code scanning payment method in the above embodiment, the user terminal 600 in the above embodiment, and the user terminal 800, etc., which will not be repeated here.

In some embodiments, the code scanning payment system may also include a payment institution system. The specific content of the payment institution system can be found in the payment institution system 13 in the above embodiment and the relevant description of the payment institution system in the code scanning payment method.

In some embodiments, the code scanning payment system may also include a payment acceptance terminal. The specific content of the payment acceptance terminal can be found in the payment acceptance terminal 12 in the above embodiment and the relevant description of the payment acceptance terminal in the code scanning payment method.

In some embodiments, the QR code payment system may also include an account management system. The specific content of the payment acceptance terminal can be found in the account management system 15 in the above embodiment and the account management system in the QR code payment method.

The eighth aspect of the present invention also provides a computer-readable storage medium, on which a computer program instruction is stored. When the computer program instruction is executed by a processor, the code scanning payment method in the embodiment of the first aspect and the code scanning payment method in the embodiment of the second aspect can be implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the above-mentioned computer-readable storage medium may include a non-transient computer-readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc., which is not limited here.

It should be made clear that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For the device embodiment, equipment embodiment, and computer-readable storage medium embodiment, the relevant parts can be referred to the description part of the method embodiment. The present invention is not limited to the specific steps and structures described above and shown in the figures. After understanding the spirit of the present invention, technicians in this field can make various changes, modifications and additions, or change the order between the steps. In addition, for the sake of brevity, the detailed description of the known method technology is omitted here.

Aspects of the present invention are described above with reference to the flow chart and/or block diagram of the method, device (system) and computer program product according to the embodiment of the present invention. It should be understood that each square frame in the flow chart and/or block diagram and the combination of square frames in the flow chart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the realization of the function/action specified in one or more square frames of the flow chart and/or block diagram. 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 box in the block diagram and/or flowchart and the combination of boxes in the block diagram and/or flowchart can also be implemented by dedicated hardware that performs the specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

Those skilled in the art should understand that the above embodiments are exemplary rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on the study of the drawings, instructions and the scope of the patent application, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the scope of the patent application, the term "including" does not exclude other devices or steps; the quantifier "one" does not exclude multiple; the terms "first" and "second" are used to identify names rather than to indicate any specific order. Any diagrammatic mark in the claim should not be understood as a limitation on the scope of protection. The functions of multiple parts appearing in the claim can be implemented by a single hardware or software module. The appearance of certain technical features in different subordinate claims does not mean that these technical features cannot be combined to achieve beneficial effects.

S201, S202, S203, S204: Steps

Claims (22)

A code scanning payment method is characterized in that it is applied to a business system, and the method comprises: receiving a payment code request message, the payment code request message is generated by a user terminal in response to a payment operation, and includes location information of the user terminal; obtaining payment waiting time factor information associated with the location information; when 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 The feedback message includes 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 the trigger signal of the payment acceptance terminal, and switches the displayed first payment code to the second payment code when sensing the trigger signal; when the received payment request message includes the first information, instructing to deduct the payment amount from the payee account indicated by the first information, and the first information includes the information of the second payment code. The method as described in claim 1, further comprising: when the payment waiting time factor information associated with the location information satisfies the dual code sending 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 payment waiting time factor information includes one or more of the following: the payee's status information, the payee's queue time information, and the user's historical waiting time information of the transaction with the payee, the historical waiting time information includes the payment code request time and the payment time, and the dual code sending condition includes one or more of the following: Item: The status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is busy with payment collection; the status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is in an event holding state; the queue time information of the payee associated with the location information indicates that the queue time of the payee in the 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 who transacts with the payee associated with the location information is greater than or equal to the preset time threshold. The method of claim 1, wherein the payment request message includes transaction information, and the method further includes: when the received payment request message includes second information, if the transaction information meets the risk control condition, executing transaction intervention processing, wherein the second information includes information of the first payment code, the risk control condition is used to determine whether the payment indicated by the second information has a risk of theft, and the transaction intervention processing is used to securely process the payment with the risk of theft. The method of claim 3, wherein the transaction information includes one or more of the following: the payee merchant address, the payment amount, and the payment frequency; the risk control conditions include one or more of the following: the distance between the payee merchant address and the location indicated by the location information is greater than the safety distance threshold, the payment amount is greater than the safety amount threshold, and the payment frequency is higher than the safety frequency threshold. The method as described in claim 3, wherein the transaction intervention process includes: verifying the identity of the user of the user terminal that sends the payment request message including the second information; or terminating the payment indicated by the second information. The method as described in claim 3, further comprising: When the received payment request message includes the second information, if the transaction information does not meet the risk control conditions, instruct to deduct the payment amount from the payer account indicated by the second information. The method of claim 1, further comprising: when the payment waiting time represented by the payment waiting time factor information associated with the location information is less than the preset time threshold, sending a second payment code feedback message, the second payment code feedback message includes a third payment code, so that the user terminal obtains the second payment code feedback message and displays the third payment code; when the received payment request message includes the third information, instructing to deduct the payment amount from the payee account indicated by the third information, the third information includes information of the third payment code. A method as described in any one of claims 1 to 7, wherein the trigger signal includes one or more of the following: a near field communication signal, a Bluetooth signal, and a sound wave signal. A code scanning payment method is characterized in that it is applied to a user terminal, and the method includes: in response to a received payment operation, sending a payment code request message, the payment code request message includes the location information of the user terminal; when the payment waiting time represented by the payment waiting time factor information associated with the location information obtained by the business system is greater than or equal to a preset time threshold, receiving a first payment code feedback message, the first payment code feedback message is generated by the business system, and includes a first payment code and a second payment code; displaying the first payment code, and in response to a trigger signal from a payment acceptance terminal, switching the displayed first payment code to the second payment code, so that the business system uses the first information to deduct the payment amount from the payee account indicated by the first information, the first information including the information of the second payment code. The method of claim 9, wherein, when the payment waiting time factor information associated with the location information satisfies the dual code sending 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, wherein the payment waiting time factor information includes one or more of the following: the payee's status information, the payee's queue time information, and the user's historical waiting time information of the user who transacts with the payee, the historical waiting time information includes the payment code request time and the payment time, and the dual code sending condition includes one or more of the following: The status information of the payee associated with the location information indicates that the payee in the area corresponding to the location information is busy with payment collection; the status information of the payee in the area corresponding to the location information indicates that the payee in the area corresponding to the location information is in an activity holding state; the queue time information of the payee associated with the location information indicates that the queue time of the payee in the 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 who transacts with the payee associated with the location information is greater than or equal to the preset time threshold. The method of claim 9, further comprising: when the first payment code is read by the payment acceptance terminal, if the transaction information in the payment request message sent by the payment acceptance terminal to the business system meets the risk control condition, accepting transaction intervention processing, wherein the risk control condition is used to determine whether the payment indicated by the second information has the risk of theft, the second information includes the information of the first payment code, and the transaction intervention processing is used to perform security processing on the payment with the risk of theft. The method of claim 11, wherein the transaction information includes one or more of the following: the payee merchant address, the payment amount, and the payment frequency; the risk control conditions include 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 the safety distance threshold, the payment amount is greater than the safety amount threshold, and the payment frequency is higher than the safety frequency threshold. The method as claimed in claim 11, wherein the transaction intervention process includes: verifying the identity of the user of the user terminal; or terminating the payment indicated by the second information. As described in claim 11, when the first payment code is read by the payment acceptance terminal, 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, the payment indicated by the second information proceeds normally. The method as claimed in claim 9, wherein, 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 the preset time threshold, a second payment code feedback message is received, the second payment code feedback message includes a third payment code; the third payment code is displayed so that the business system uses the third information to deduct the payment amount from the payer account indicated by the third information, the third information includes information of the third payment code. A method as described in any one of claims 9 to 15, wherein the trigger signal includes one or more of the following: a near field communication signal, a Bluetooth signal, and a sound wave signal. A business device, characterized in that it includes: a receiving module, used to receive a payment code request message, the payment code request message is generated by a user terminal in response to a payment operation, and includes location information of the user terminal; an obtaining module, used to obtain payment waiting time factor information associated with the location information; a sending module, used to send a first payment code feedback message when 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, the first payment code feedback message The message includes 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 the trigger signal of the payment acceptance terminal, and switches the displayed first payment code to the second payment code when sensing the trigger signal; the payment processing module is used to instruct the deduction of the payment amount from the payer account indicated by the first information when the received payment request message includes the first information, and the first information includes the information of the second payment code. A user terminal is characterized in that it includes: a sending module for sending a payment code request message in response to a received payment operation, wherein the payment code request message includes the location information of the user terminal; a receiving module for receiving a first 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 greater than or equal to a preset time threshold, wherein the first payment code feedback message is generated by the business system and includes a first payment code and a second payment code; a display module for displaying the first payment code and switching the displayed first payment code to the second payment code when sensing a trigger signal from a payment acceptance terminal, so that the business system uses the first information to deduct the payment amount from the payee account indicated by the first information, wherein the first information includes information of the second payment code. A business device, characterized in that it includes: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the scanning payment method as described in any one of claim items 1 to 8 is implemented. A user terminal, characterized in that it includes: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the scanning payment method as described in any one of claim items 9 to 16 is implemented. A code scanning payment system, characterized in that it includes a user terminal and a business system; the user terminal is used to respond to a received payment operation and send a payment code request message, the payment code request message includes the location information of the user terminal; the business system is used to receive the payment code request message, obtain payment waiting time factor information associated with the location information, and send a payment code request message when the payment waiting time factor information associated with the location information is greater than or equal to a preset time threshold. The first payment code feedback message includes the first payment code and the second payment code; the user terminal is also used to display the first payment code, and when sensing the trigger signal of the payment acceptance terminal, the displayed first payment code is switched to the second payment code; the business system is also used to instruct to deduct the payment amount from the payee account indicated by the first information when the received payment request message includes the first information, and the first information includes the information of the second payment code. A computer-readable storage medium, characterized in that a computer program instruction is stored on the computer-readable storage medium, and when the computer program instruction is executed by a processor, a QR code payment method as described in any one of claim items 1 to 16 is implemented.

Images