WO2023151246A1

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

Info

Publication number: WO2023151246A1
Application number: PCT/CN2022/109433
Authority: WO
Inventors: 涂进鹏; 郭琦; 徐蓉; 王月姣; 魏晓书; 尹宏宇
Original assignee: 中国银联股份有限公司
Priority date: 2022-02-11
Filing date: 2022-08-01
Publication date: 2023-08-17
Also published as: CN114548975A; TW202333097A

Abstract

A code-scanning payment method, a user terminal, a service device, a system, and a medium, relating to the field of data processing. The method comprises: receiving a payment code request message, the payment code request message comprising position information of a user terminal; obtaining payment waiting duration factor information associated with the position information; under the condition that the payment waiting duration represented by the payment waiting duration factor information associated with the position information is greater than or equal to a preset duration threshold, sending a first payment code feedback message, the first payment code feedback message comprising a first payment code and a second payment code, so that the user terminal displays the first payment code before sensing a trigger signal of a collection acceptance terminal, and switches the displayed first payment code into the second payment code when sensing the trigger signal; and if a payment request message comprises first information, instructing to deduct the payment amount from a payer account indicated by information of the second payment code. Therefore, the code-scanning payment security is improved.

Description

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

Cross References to Related Applications

This application claims the priority of the Chinese patent application 202210130242.7 entitled "Payment Method, User Terminal, Business Equipment, System and Media" filed on February 11, 2022, the entire content of which is incorporated herein by reference middle.

technical field

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

Background technique

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

In the scenario where the scanned payment mode is adopted, 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 the payment, there is a case that the payment code is secretly photographed and stolen, which reduces the user's payment security.

Contents of the invention

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

In the first aspect, the embodiment of the present application provides a scanning code payment method, which is applied to a business system. The method includes: receiving a payment code request message, the payment code request message is generated by the user terminal in response to the payment operation, and includes the location information of the user terminal ; Obtain 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, send the first payment code feedback message, the first payment The 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 when the trigger signal is sensed, the first payment code is displayed. Under the circumstances, switch the displayed first payment code to the second payment code; when the received payment request message includes the first information, instruct to deduct the payment amount from the payer’s account indicated by the first information, and the first information includes the first information Second payment code information.

In the second aspect, the embodiment of the present application provides a code scanning payment method, which is applied to a user terminal. The method includes: sending a payment code request message in response to a received payment operation, where 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 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, including the first payment code and the second payment code; display the first payment code, and switch the displayed first payment code to the second payment code when the trigger signal of the collection acceptance terminal is sensed, so that the business system can use the first information The payment amount is deducted from the payer's account indicated by the first information, where the first information includes the information of the second payment code.

In a third aspect, the embodiment of the present application provides a service device, including: a receiving module, configured 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 acquisition module, Used to obtain payment waiting time factor information associated with the location information; a sending module for sending the first payment code 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 length threshold 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 collection acceptance terminal, In the case of sensing the trigger signal, the displayed first payment code is switched to the second payment code; the payment processing module is used to indicate the payment indicated from the first information when the received payment request message includes the first information The payment amount is deducted from the party's account, and the first information includes information about the second payment code.

In a fourth aspect, an embodiment of the present application provides a user terminal, including: a sending module, configured to send a payment code request message in response to a received payment operation, where the payment code request message includes location information of the user terminal; a receiving module, configured to 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, including the first A payment code and a second payment code; the display module is used to display the first payment code, and in the case of sensing the trigger signal of the collection acceptance terminal, switch the displayed first payment code to the second payment code to The business system uses the first information to deduct the payment amount from the payer's account indicated by the first information, where the first information includes the information of the second payment code.

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

In a sixth aspect, an embodiment of the present application 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 the seventh aspect, the embodiment of the present application provides a code scanning payment system, including a user terminal and a business system; the user terminal is used to send a payment code request message in response to a received payment operation, and 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 the payment waiting time factor information associated with the location information, and send it 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. The first payment code feedback message, 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 in the case of sensing the trigger signal of the payment acceptance terminal, Switch the displayed first payment code to the second payment code; the business system is also used to instruct the payment amount to be deducted from the payer's account indicated by the first information when the received payment request message includes the first information. A message includes information of the second payment code.

In the eighth aspect, the embodiment of the present application 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 second aspect is implemented The scan code payment method.

The embodiment of the present application provides a code scanning payment method, user terminal, business equipment, system and medium. The business system receives a payment code request message including the location information of the user terminal, and according to the payment waiting time factor information associated with the location information, Determine whether the payment waiting time represented by the payment waiting time factor information is greater than or equal to the preset time threshold, 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 payment code The possibility of being stolen by a sneak shot, the service system issues the first payment code and the second payment code for the user terminal. The first payment code is displayed on the user terminal before the user terminal senses the trigger signal sent by the payment 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 second payment code was scanned by the payment acceptance terminal. Since the second payment code is only displayed 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 the 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 the payment with higher security and improve the security of scanning code payment.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the accompanying drawings that need to be used in the embodiments of the present application. Additional figures can be derived from these figures.

FIG. 1 is a schematic structural diagram of an example of an application scenario of a code scanning payment method provided by an embodiment of the present application;

Fig. 2 is a flow chart of an embodiment of the scanning code payment method provided in the first aspect of the present application;

Fig. 3 is a flow chart of another embodiment of the scanning code payment method provided in the first aspect of the present application;

Fig. 4 is a flow chart of another embodiment of the code scanning payment method provided in the first aspect of the present application;

Fig. 5 is a flow chart of another embodiment of the code scanning payment method provided in the first aspect of the present application;

Fig. 6 is a flow chart of an embodiment of the scanning code payment method provided by the second aspect of the present application;

Fig. 7 is a flow chart of another embodiment of the code scanning payment method provided by the second aspect of the present application;

Fig. 8 is a flow chart of another embodiment of the scanning code payment method provided by the second aspect of the present application;

FIG. 9 is a flow chart of an example of the code scanning payment process provided by the embodiment of the present application;

Fig. 10 is a schematic structural diagram of an embodiment of the service equipment provided by the third aspect of the present application;

Fig. 11 is a schematic structural diagram of another embodiment of the service equipment provided by the third aspect of the present application;

Fig. 12 is a schematic structural diagram of another embodiment of the service equipment provided by the third aspect of the present application;

FIG. 13 is a schematic structural diagram of an embodiment of a user terminal provided in the fourth aspect of the present application;

FIG. 14 is a schematic structural diagram of another embodiment of the user terminal provided by the fourth aspect of the present application;

Fig. 15 is a schematic structural diagram of an embodiment of the service equipment provided in the fifth aspect of the present application;

Fig. 16 is a schematic structural diagram of an embodiment of a user terminal provided in the sixth aspect of the present application.

Detailed ways

The characteristics and exemplary embodiments of various aspects of the application will be described in detail below. In order to make the purpose, technical solution and advantages of the application clearer, the application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described here are only intended to explain the present application rather than limit the present application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

With the continuous development of payment technology, code scanning payment has penetrated into various fields. Scanning code payment can include the main scanning payment mode and the scanned payment mode. The main scanning payment mode is the payment method in which the payment user scans the merchant's payment code. The scanned payment mode is a payment method in which the payment code is displayed on the user terminal of the paying user, and the payment code is scanned by the merchant's acceptance terminal. In the scenario where the scanned payment mode is adopted, 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 for the payment, someone will sneak a photo of the payment code displayed on the user terminal, and use the sneak-photographed payment code to make the payment, causing fraudulent swiping of funds in the user's account to which the payment code belongs, which seriously affects the user's payment security.

This application provides a code scanning payment method, user terminal, business equipment, system and medium, which can be used to download payment to the user terminal when the waiting time for payment at the location of the user terminal that needs to be paid is long, such as when the queue for payment is long. Send two different payment codes. When the user terminal is not close to the payment acceptance terminal such as POS (Point Of Sale) machine and other equipment, the user terminal displays one of the payment codes, and the user terminal is close to the payment acceptance In the case of a terminal, the user terminal displays another of the payment codes. It is difficult for other people queuing up around the user at the user terminal to capture another payment code, so when the payment request message received by the business system includes the information of another payment code, normal payment can be allowed, which improves the payment security of the user .

The scanning code payment method in the embodiment of the present application is applied in the scenario of the scanned payment mode, and may involve user terminals, payment acceptance terminals, payment institution systems, business systems, and account management systems. FIG. 1 is a schematic structural diagram of an example of an application scenario of the code scanning payment method provided by the embodiment of the present application. As shown in FIG. 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 payment, and specifically may include a mobile phone, a tablet computer, a smart wearable device, etc., and the specific type of the user terminal 11 is not limited here. The user terminal 11 may be installed with a payment application, and the payment application may be used for payment. The user terminal 11 has a display function and can display the payment code, so that the payment code can be used for payment. The payment code can be a two-dimensional 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 a validity period. After the validity period, the payment code cannot continue to be used, and the payment code needs to be updated.

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

The payment institution system 13 can be used to pay the acquirer, specifically the system of the acquirer. The payment institution system 13 may 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 functions in the payment institution system 13, and can also perform different functions in the payment institution system 13. Functions are 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 liquidation. 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, a settlement subsystem 143, and the like. The business system 14 can issue the generated payment code to the user terminal 11 through the payment institution system 13 . The business system 14 can include one or more than two servers and other business equipment, and different servers and other business equipment in the business system 14 can perform the same function in the business system 14, and can also perform different functions in the business system 14. In the case that the business system 14 includes multiple servers and other business equipment, some business equipment such as servers can belong to the payment code subsystem 141, some business equipment such as servers can belong to the risk control subsystem 142, and some business equipment such as servers can belong to the liquidation subsystem 143.

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

The code scanning payment method, user terminal, service equipment, system and media in this application will be described in sequence below.

The first aspect of the present application 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 business equipment in the business system. Fig. 2 is a flow chart of an embodiment of the code scanning payment method provided in the first aspect of the present application. 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, and may 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 sends a payment code request message to the business system. What the business system receives is the payment code request message sent by the payment institution system. For example, the user performs a payment operation on the user terminal, opens the payment application, and clicks on the "payment code" function, and the user terminal sends a payment code request message to the payment institution system in response to the payment operation.

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, the payment waiting time factor information associated with the location information is acquired.

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, and the like. The payment waiting time factor information includes information on factors affecting the payment waiting time, which can reflect the payment waiting time. Payment waiting time can also be regarded as payment queuing time.

In some examples, the payment waiting time factor information may include one or more of the status information of the payee, the queuing time information of the payee, and the historical waiting time information of users who trade with the payee.

The status information of the payee can represent the busyness of the payee. The busier the payee is, the longer the payment waiting time may be for the paying user. The payee's queuing time information can represent the payee's queuing time. The longer the queuing time, the longer the waiting time for payment. The historical waiting time information of users who have transactions with the payee may include historical information related to payment waiting of users who have transactions with the payee, and the waiting time for payment is determined through the information of users who have transactions with the payee. For example, the historical waiting time information may include payment code request time and payment time, the payment code request time is the moment when the user terminal requests the payment code, the payment time is the moment when the user terminal pays, the time between a user's payment code request time and the payment time The length of time can be used as the payment waiting time of the user, and the payment waiting time of the payee can be determined according to the time between the payment code request time and the payment time of multiple users who have transactions with a payee.

In step S203, when the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to the preset time length threshold, the first payment code feedback message is sent, so that the user terminal obtains the first payment code feedback message , and display the first payment code before sensing the trigger signal of the collection acceptance terminal, and switch the displayed first payment code to the second payment code when the trigger signal is sensed;

The preset duration threshold is a threshold value used to determine the duration of a security risk, which can be set according to scenarios, requirements, experience, etc., and is not limited here. The payment waiting time represented by the payment waiting time factor information is greater than or equal to the preset time threshold, which means that the security risk is relatively high, and it is necessary to implement measures for issuing payment codes with higher security. The payment waiting time represented by the payment waiting time factor information is less than the preset time threshold, indicating that the security risk is small and negligible.

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 the first payment code feedback message to the payment institution system, and the payment institution system can then send the first payment code to the user terminal feedback message. 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, displays the first payment code first, and saves the second payment code. The payment acceptance terminal can send a trigger signal. When the payer user carrying the user terminal is still queuing and has not arrived at the collection acceptance terminal, the user terminal has not sensed the trigger signal sent by the collection acceptance terminal. Before the user terminal has not sensed the trigger signal, that is, the user terminal has sensed the trigger signal, The user terminal displays the first payment code. When the payer user brings the user terminal to the payment acceptance terminal, the user terminal senses the trigger signal sent by the payment acceptance terminal, and can switch the displayed first payment code to the second payment code, so that the payment acceptance terminal can scan Second payment code.

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

In step S204, if the received payment request message includes the first information, it is instructed to deduct the payment amount from the payer's 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 according to the information read from the payment code, and the payment request message includes the information read from the payment code. The collection acceptance terminal sends a payment request message to the payment institution system, and the payment institution system sends a payment request message to the business system.

The first information includes information of the second payment code, and the information of the second payment code is information obtained by reading the second payment code. The payment request message received by the business system includes the first information, indicating that in this scan code payment, the payment acceptance terminal scanned the second payment code, that is to say, the payment acceptance terminal scanned the user terminal to arrive at the payment code. Accepting the second payment code switched at the terminal, the security risk of this scan code payment is relatively small, and normal payment is allowed. The business system may send a transaction message to the account management system to instruct to deduct the payment amount from the payer's account indicated by the first information.

In this embodiment of the application, the service system receives the payment code request message including the location information of the user terminal, and determines whether the payment waiting time represented by the payment waiting time factor information is greater than or equal to The preset time threshold, 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 stolen by sneak shots, and the business system issues a The first payment code and the second payment code. 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 second payment code was scanned by the payment acceptance terminal. Since the second payment code is only displayed 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 the 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 the payment with higher security and improve the security of scanning code payment.

The above-mentioned switching between the first payment code and the second payment code is actively performed by the user terminal without user participation, which can reduce user operations and improve the efficiency of scanning code payment on the basis of ensuring the security of scanning code payment. Moreover, compared with the technical solution of shortening the effective duration of the payment code, the embodiment of the present application does not need to frequently update and issue the payment code, and can also reduce the business of generating and issuing the payment code on the basis of ensuring the security of scanning the code for payment. System handling pressure.

In some embodiments, it may be determined whether the payment waiting time is greater than or equal to a preset time length threshold by checking whether the payment waiting time factor satisfies the condition for issuing a double code. Fig. 3 is a flow chart of another embodiment of the code scanning payment method provided in the first aspect of the present application. The difference between FIG. 3 and FIG. 2 is that the code scanning payment method shown in FIG. 3 may further include step S205.

In step S205, if the payment waiting time factor information associated with the location information satisfies the dual-code delivery condition, 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 length threshold.

The conditions for issuing double codes include the conditions for judging whether there is a risk of the payment code being secretly photographed or stolen in the payment under the payment waiting time factor information condition. The payment waiting time factor information associated with the location information satisfies the dual-code delivery condition, and it is determined that the payment waiting time factor information associated with the location information indicates that the payment waiting time is greater than or equal to the preset time threshold value, indicating payment under the condition of the payment waiting time factor information There is a risk of the payment code being stolen by sneak shots, and the first payment code and the second payment code can be issued to the user terminal through the first payment code feedback message. In some examples, the payment waiting time factor information associated with the location information does not meet the dual-code delivery condition, and it is determined that the payment waiting time represented by the payment waiting time factor information associated with the location information is less than the preset time threshold, indicating that the payment waiting time factor Payment under information conditions does not have the risk of the payment code being stolen by sneak shots, and a payment code can be issued to the user terminal.

For the specific content of the payment waiting time factor information, please refer to the relevant description in the above embodiment, which will not be repeated here.

In some examples, the dual-code delivery conditions may include one or more of the following:

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

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

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

The time period between the payment code request time and the payment time of the user associated with the location information and the payee transaction is greater than or equal to the preset time length threshold.

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

The status information of the payee indicates that the payee is in a busy state of receiving money, and there are more 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 factor information represents If the waiting time for payment is greater than or equal to the preset time threshold, the payment code of the payer user may be stolen by sneak shots, and the first payment code and the second payment code need to be issued to the user terminal.

The status information of the payee indicates that the payee is in the event holding state, and there are many payer users waiting for payment at the payee. If the payment waiting time is greater than or equal to the preset time threshold, the payment code of the payer user may be stolen by a sneak shot, and the first payment code and the second payment code need to be issued to the user terminal. The activities organized by the payee may be promotions or preferential activities, etc., which are not limited here.

The payee's queuing time information represented by the payee's queuing time is basically the same as the payment waiting time, the longer the queuing time, the longer the payment waiting time. The payee’s queuing time information indicates that the payee’s queuing time 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, and the payment code of the payer user may be secretly photographed and stolen possibility, it is necessary to issue the first payment code and the second payment code to the user terminal.

The time between the payment code request time and payment time of the payee transaction user is the payment waiting time, and the time length between the payment code request time and payment time of the payee transaction user’s user’s payment code time is greater than or equal to the preset time threshold, namely If 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 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.

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 switching from the first payment code to the second payment code at the user terminal, the payment acceptance terminal scans the The first payment code is still the first payment code. In order to accurately distinguish the payment that has the risk of stealing and misappropriating, further judgment can be made according to the transaction information included in the payment request message, and corresponding processing can be performed according to the judgment result. Fig. 4 is a flow chart of another embodiment of the code scanning payment method provided in the first aspect of the present application. The difference between FIG. 4 and FIG. 2 is that the code scanning payment method shown in FIG. 4 may further include steps S206 and S207.

In step S206, if the received payment request message includes the second information, if the transaction information satisfies the risk control condition, transaction intervention processing is executed.

The second information includes information of the first payment code, and the information of the first payment code is information obtained by reading the first payment code. The payment request message received by the business system includes the second information, indicating that in this code-scanning payment, the payment acceptance terminal scanned the first payment code. However, the first payment code scanned by the payment acceptance terminal may be the first payment code that was secretly photographed and stolen by others, or it may be the first payment code that has not been switched due to the delay in switching payment codes at the user terminal, but the first payment code that has been secretly photographed and stolen by others. The payment with the payment code is an illegal payment. The first payment code that has not been switched due to the delay in switching the payment code at the user terminal is a legal payment. Illegal payment and legal payment can be further distinguished by checking whether the transaction information included in the payment request message meets the risk control conditions. pay.

The risk control condition is used to determine that the payment indicated by the second information has a risk of embezzlement, and the transaction intervention processing is used to perform security processing on the payment with a risk of embezzlement.

In some examples, the transaction information includes one or more of the following: payee merchant address, payment amount, 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 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 security amount threshold;

The payment frequency is above the safe frequency threshold.

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

In some cases where the payment code is secretly photographed and stolen, the person who secretly photographed the collection code will send the received code to other people, and the other person will pay at the payee in another location. The distance between the location of the payee's merchant address and the location indicated by the location information of the user terminal in the payment code request message and the safety distance threshold can be used to determine whether the payment was made at another location using the first payment code that was secretly photographed. Illegal payments made at the beneficiary's account. The safety distance threshold is the safety threshold value for judging whether the payment is made at the same place, which can be set according to the scene, demand, experience, etc., and is not limited here. 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, which means that the location of the application payment code is far away from the location of the payment, and they are not in the same place. Illegal payment requires transaction intervention.

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

It can also help improve the security of scanning code payment through payment frequency. The safe frequency threshold is the threshold value of the frequency for judging whether the payment frequency is safe, which can be set according to scenarios, needs, experience, etc., and is not limited here. If the payment frequency is higher than the security frequency threshold, if the receiving code is secretly photographed and stolen, it may cause a large loss, and transaction intervention is required.

When the risk control conditions include two or more conditions, the risk control conditions can have a priority, and it can be judged first whether the transaction information meets the risk control conditions with a relatively high priority. If the transaction information meets the risk control conditions with a relatively high priority , can perform transaction intervention processing; if the transaction information does not meet the relatively high priority risk control conditions, then determine whether the transaction information meets the relatively low priority risk control conditions. For example, the risk control conditions include that 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, and the payment amount is greater than the safety amount threshold; if the location of the payee’s merchant address and the location information indicated If the distance between the locations is greater than the safety distance threshold, transaction intervention processing can be performed without judging whether the payment amount is greater than the safety amount threshold; if the distance between the location of the payee’s merchant address and the location indicated by the location information is less than or equal to the safety distance Threshold, and then judge whether the payment amount is greater than the safety amount threshold, if the payment amount is greater than the safety amount threshold, the transaction processing can be performed.

The transaction intervention processing may include: authenticating 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 the case that the payment indicated by the second information has a risk of fraudulent use, the service system may perform identity verification on the user who makes payment using the first payment code corresponding to the second information. Specifically, the service 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 input identity verification information. Identity verification information may include payment account number, payment password, verification code and other information that can prove that the user who requested the payment code made the payment himself, which is not limited here. The user terminal sends identity verification information to the payment institution system, and the payment institution system sends identity verification information to the business system. The business system checks whether the received identity verification information is consistent with the reserved or set identity verification information. If they are consistent, normal payment can continue , if inconsistent, the payment will be suspended.

In the case that the payment indicated by the second information has a risk of embezzlement, the payment indicated by the second information may also be directly suspended to avoid the risk of embezzlement.

In step S207, if the received payment request message includes the second information, if the transaction information does not satisfy the risk control condition, instruct to deduct the payment amount from the payer's 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 embezzlement, and the payment can continue to be made without transaction intervention. The business system may send a transaction message to the account management system to instruct to deduct the payment amount from the payer's account indicated by the second information.

Through transaction information and risk control conditions, the effectiveness of risk monitoring can be improved, the accuracy of identifying payments with embezzlement risks can be improved, and the security of scanning code payments can be further improved.

In some embodiments, if the waiting time for payment is less than the preset time threshold, the risk that the payment code of the payer user will be secretly photographed and stolen is negligible. The business system can issue a single payment code to the user terminal. On the basis of high security, it further reduces the pressure on the business system to generate payment codes and issue payment codes. Fig. 5 is a flow chart of another embodiment of the code scanning payment method provided in the first aspect of the present application. The difference between FIG. 5 and FIG. 2 is that the code scanning payment method shown in FIG. 5 may further include steps S208 and 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 obtains the second payment code feedback message, And display 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 to be small and negligible, and the business system can issue a single payment to the user terminal Code is the third payment code. 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 may send the second payment code feedback message to the payment institution system, and the payment institution system then sends the second payment code feedback message to the user terminal. The user terminal receives the feedback information of the second payment code, obtains the third payment code from the feedback information of the second payment code, and can display the third payment code.

In step S209, if the received payment request message includes the third information, it is instructed to deduct the payment amount from the payer's account indicated by the third information.

The third information includes information of the third payment code, and the information of the third payment code is information obtained by reading the third payment code. The payment request message received by the business system includes the third information, indicating that in this code-scanning payment, the payment acceptance terminal scanned the third payment code. The third payment code was issued when the risk of stealing and stealing the payment code was small, indicating that the security risk of scanning the code payment this time was small, and normal payment was allowed to continue. The business system may send a transaction message to the account management system to instruct to deduct the payment amount from the payer's account indicated by the third information.

When the payment waiting time factor information associated with the location information determines that the risk of the payment code being secretly photographed and stolen is low, the business system issues a single payment code to the user terminal, which can reduce the risk of payment while ensuring the security of scanning code payment. The business system is under pressure to generate payment codes and issue payment codes.

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

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

The payment code request message includes location information of the user terminal. Specifically, the user terminal may first send a payment code request message to the payment institution system, and then the payment institution system 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 acquired by the business system is greater than or equal to the preset time length 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 service system may first send the first payment code feedback message to the payment institution system, and then the payment institution system sends the first payment code feedback message to the user terminal.

In step S303, display the first payment code, and switch the displayed first payment code to the second payment code when the trigger signal of the collection acceptance terminal is sensed, so that the business system can use the first information from the first payment code to the second payment code. The payment amount is deducted from the payer's account indicated by a message.

After receiving the first payment code feedback message, the user terminal first displays the first payment code before sensing the trigger signal of the payment acceptance terminal, and then switches to display the second payment code when it senses the trigger signal of the payment acceptance terminal. payment code.

The first information includes 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, and an acoustic wave signal. For details, please refer to relevant descriptions in the above-mentioned embodiments, and details will not be repeated here.

The specific content of the above step S301 to step S303 can refer to the related description in the above embodiment, and will not be repeated here.

In this embodiment of the application, the user terminal may request the payment code from the service 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. According to the payment waiting time factor information associated with the location information, 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; if the payment waiting time represented by the payment waiting time factor information is greater than or equal to the preset The time threshold is set to determine that the waiting time for payment is long, and there is a possibility that the payment code may be stolen by sneak shots. The user terminal may 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 sent by the payment acceptance terminal, and switches the displayed payment code to the second payment code when the user terminal senses the trigger signal sent by the payment acceptance terminal, so that the user terminal When payment is made at the collection acceptance terminal, what the collection acceptance terminal scans is the second payment code, and the information of the second payment code can be used to continue normal payment through the business system. Since the second payment code is only displayed 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 the 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 the payment with higher security and improve the security of scanning code payment.

The above-mentioned switching between the first payment code and the second payment code is actively performed by the user terminal without user participation, which can reduce user operations and improve the efficiency of scanning code payment on the basis of ensuring the security of scanning code payment. Moreover, compared with the technical solution of shortening the effective duration of the payment code, the embodiment of the present application does not need to frequently update and issue the payment code, and can also reduce the business of generating and issuing the payment code on the basis of ensuring the security of scanning code payment. System handling pressure.

In some embodiments, when the payment waiting time factor information associated with the location information satisfies the dual-code delivery 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 length threshold.

The payment waiting time factor information includes one or more of the status information of the payee, the queuing time information of the payee, and the historical waiting time information of users who trade with the payee. Wherein, the historical waiting time information includes 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 located in the area corresponding to the location information is in a busy state of receiving money;

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

For the specific content of the payment waiting time factor information associated with the location information, the conditions for issuing double codes, etc., please refer to the relevant descriptions in the above embodiments, and will not be repeated here.

In some embodiments, what the payment acceptance terminal reads may also be the first payment code, and it is possible to further distinguish whether the payment corresponding to the first payment code is a payment with a high security risk through the transaction information and risk control conditions in the payment request message. payment. Fig. 7 is a flow chart of another embodiment of the code scanning payment method provided by the second aspect of the present application. The difference between FIG. 7 and FIG. 6 is that the code scanning payment method shown in FIG. 7 may further 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 satisfies the risk control condition, transaction intervention processing is accepted.

The risk control condition is used to determine that the payment indicated by the second information has a risk of embezzlement. The second information includes information about the first payment code. The transaction intervention processing is used to perform security processing on the payment with the risk of misappropriation.

For specific content of step S304, refer to relevant descriptions in the foregoing embodiments, and details are not repeated here.

In some examples, the transaction information includes one or more of the following: payee merchant address, payment amount, and payment frequency. For the specific content of the transaction information, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

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

The payment amount is greater than the security amount threshold;

The payment frequency is above the safe frequency threshold.

For the specific content of the risk control conditions, refer to the relevant descriptions in the foregoing embodiments, and details are not repeated here.

In some examples, the above-mentioned transaction intervention processing includes: performing identity verification on the user of the user terminal; or suspending the payment indicated by the second information.

For the specific content of the transaction intervention processing, refer to the relevant descriptions in the above-mentioned embodiments, which will not be repeated 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 second information indicates Payment proceeds normally.

For the specific content of the payment when 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, please refer to the relevant descriptions in the above embodiments, and details will not be repeated here.

In some embodiments, if the waiting time for payment is less than the preset time threshold, the risk that the payer user's payment code will be secretly photographed and stolen is negligible, and the business system can issue a single payment code to the user terminal. Fig. 8 is a flow chart of another embodiment of the code scanning payment method provided by the second aspect of the present application. The difference between FIG. 8 and FIG. 6 is that the code scanning payment method shown in FIG. 8 may further include steps S305 and S306.

In step S305, when the payment waiting time represented by the payment waiting time factor information associated with the location information acquired by the business system is less than the preset time length 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 payer's account indicated by the third information.

The third information includes information of the third payment code.

The specific content of step S305 to step S306 can refer to the relevant description in the above embodiment, and will not be repeated here.

In order to facilitate the understanding of the code scanning payment method in the embodiment of the present application, the following takes the business system to issue two payment codes at one time, that is, the first payment code and the second payment code, as an example to illustrate the user terminal, payment acceptance terminal, and payment institution Scan code payment process between system, business system and account management system. FIG. 9 is a flow chart of an example of the code scanning payment process provided by the embodiment of the present application. As shown in FIG. 9 , the overall flow of code scanning payment may include steps S401 to S418.

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

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

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

In step S404, the business system judges whether the payment waiting time factor information satisfies the dual-code delivery condition.

In step S405, if the condition for issuing the double code is satisfied, the business system sends a feedback message of the first payment code 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 information of the payment code.

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 information of the read payment code.

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 information of the payment code in the payment request message is the information of the second payment code, jump to step S413; if the information of the payment code 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 deducts the payment amount from the payer's account indicated by the information of the second payment code in response to the transaction message.

In step S415, the business system judges whether the transaction information satisfies the risk control condition. If the transaction information satisfies the risk control condition, go to step S416; if the transaction information does not meet the risk control condition, go to step S417.

In step S416, the business system executes 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 deducts the payment amount from the payer's account indicated by the information of the first payment code in response to the transaction message.

For the specific content in the above step S401 to step S418, please refer to the related content in the above embodiment, which will not be repeated here.

The third aspect of the present application provides a service device. Fig. 10 is a schematic structural diagram of an embodiment of the service equipment provided in the third aspect of the present application. As shown in FIG. 10 , the service device 500 may include a receiving module 501 , an acquiring module 502 , a sending module 503 and a payment processing module 504 .

The receiving module 501 can be used to receive the payment code request message.

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

The obtaining module 502 may be used to obtain payment waiting time factor information associated with the location information.

The sending module 503 can be configured to send the 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 length threshold, so that the user terminal can obtain the first payment code feedback message , and display the first payment code before sensing the trigger signal of the collection acceptance terminal, and switch the displayed first payment code to the second payment code when the trigger signal is sensed.

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, an acoustic wave signal

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

The first information includes information of the second payment code.

Fig. 11 is a schematic structural diagram of another embodiment of the service equipment provided in the third aspect of the present application. The difference between FIG. 11 and FIG. 10 is that the service device 500 shown in FIG. 11 may further include a determination module 505 .

The determination module 505 can be used to determine 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 length threshold when the payment waiting time factor information associated with the location information satisfies the dual-code delivery condition.

The payment waiting time factor information includes one or more of the status information of the payee, the queuing time information of the payee, and the historical waiting time information of users who trade with the payee. Among them, the historical waiting time information includes payment code request time and payment time.

The conditions for issuing double codes include one or more of the following:

Fig. 12 is a schematic structural diagram of another embodiment of the service equipment provided in the third aspect of the present application. The difference between FIG. 12 and FIG. 10 is that the service device 500 shown in FIG. 12 may further include an intervention processing module 506 .

The intervention processing module 506 may be configured to perform transaction intervention processing if the transaction information satisfies the risk control condition when the received payment request message includes the second information.

The payment request message includes transaction information. The second information includes information of the first payment code. The risk control condition is used to determine that the payment indicated by the second information has a risk of embezzlement. Transaction intervention processing is used to securely process payments where there is a risk of misappropriation.

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

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

The payment amount is greater than the security amount threshold;

The payment frequency is above the safe frequency threshold.

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

In some embodiments, the above-mentioned payment processing module 504 can also be configured to instruct to deduct the payment from the payer's account indicated by the second information if the transaction information does not meet the risk control condition when the received payment request message includes the second information. amount.

In some embodiments, the above sending module 503 can also be used to send the 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 the preset time length threshold, so that the user terminal Obtain the feedback message of the second payment code and display the third payment code.

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

The above-mentioned payment processing module 504 may also be configured to instruct to deduct the payment amount from the payer's account indicated by the third information when the received payment request message includes the third information.

The third information includes information of the third payment code.

A fourth aspect of the present application provides a user terminal. Fig. 13 is a schematic structural diagram of an embodiment of a user terminal provided in the fourth aspect of the present application. As shown in FIG. 13 , 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 configured to send a payment code request message in response to the received payment operation.

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

The receiving module 602 may be configured 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 acquired by the business system is greater than or equal to the preset time length 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 switch the displayed first payment code to the second payment code when the trigger signal of the payment acceptance terminal is sensed, so that the business system can use the first information to start from the second payment code. The payment amount is deducted from the payer's account indicated by a message.

The first information includes 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, and an acoustic wave signal.

The payment waiting time factor information includes one or more of the status information of the payee, the queuing time information of the payee, and the historical waiting time information of users who trade with the payee. The historical waiting time information includes payment code request time and payment time.

The conditions for issuing double codes include one or more of the following:

Fig. 14 is a schematic structural diagram of another embodiment of a user terminal provided in the fourth aspect of the present application. The difference between FIG. 14 and FIG. 13 is that the user terminal 600 shown in FIG. 14 may further include a processing module 604 .

The processing module 604 may be configured to accept transaction intervention processing if the transaction information in the payment request message sent by the collection acceptance terminal to the business system satisfies the risk control condition when the first payment code is read by the payment acceptance terminal.

The risk control condition is used to determine that the payment indicated by the second information has a risk of embezzlement. The second information includes information of the first payment code. Transaction intervention processing is used to securely process payments where there is a risk of misappropriation.

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

The payment amount is greater than the security amount threshold;

The payment frequency is above the safe frequency threshold.

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

In some embodiments, the receiving module 602 is further configured to receive the second payment code feedback message when the payment waiting time represented by the payment waiting time factor information associated with the location information acquired by the business system is less than a preset time length threshold.

The second payment code feedback message includes the third payment code

The above-mentioned display module 603 can also be used to display the 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 information of the third payment code.

The fifth aspect of the present application also provides a service device. Fig. 15 is a schematic structural diagram of an embodiment of the service equipment provided in the fifth aspect of the present application. As shown in FIG. 15 , the service device 700 includes a memory 701 , a processor 702 and a computer program stored in the memory 701 and operable on the processor 702 .

In some examples, the above-mentioned processor 702 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

Memory 701 may include read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk storage medium device, optical storage medium device, flash memory device, electrical, optical or other physical/tangible Memory storage device. Thus, in general, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions, and when the software is executed (e.g., by one or multiple processors), it is operable to execute the operations described with reference to the code scanning payment method in the embodiment according to the first aspect of the present application.

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

In an example, the service device 700 may further include a communication interface 703 and a bus 704 . Wherein, as shown in FIG. 15 , the memory 701 , the processor 702 , and the communication interface 703 are connected through a bus 704 to complete mutual communication.

The communication interface 703 is mainly used to realize the communication between various modules, devices, units and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through the communication interface 703 .

The bus 704 includes hardware, software, or both, and couples the components of the business device 700 to each other. For example and without limitation, the bus 704 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (Enhanced Industry Standard Architecture, EISA) bus, a Front Side Bus (Front Side Bus, FSB), Hyper Transport (HT) interconnect, Industry Standard Architecture (ISA) bus, InfiniBand interconnect, Low pin count (Low pin count, LPC) bus, memory bus, Micro Channel architecture (Micro Channel Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-E) bus, Serial Advanced Technology Attachment (Serial Advanced Technology Attachment, SATA) bus, Video Electronics Standards Association local ( Video Electronics Standards Association Local Bus, VLB) bus or other suitable bus or a combination of two or more of these. Bus 704 may comprise one or more buses, where appropriate. Although the embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.

The sixth aspect of the present application also provides a user terminal. Fig. 16 is a schematic structural diagram of an embodiment of a user terminal provided in the sixth aspect of the present application. As shown in FIG. 16 , the user terminal 800 includes a memory 801 , a processor 802 and computer programs stored in the memory 801 and operable on the processor 802 .

In some examples, the above-mentioned processor 802 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

Memory 801 may include read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk storage medium device, optical storage medium device, flash memory device, electrical, optical or other physical/tangible Memory storage device. Thus, in general, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions, and when the software is executed (e.g., by one or multiple processors), it is operable to execute the operations described with reference to the code scanning payment method in the embodiment according to the second aspect of the present application.

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 code scanning payment method in the embodiment of the second aspect above.

In an example, the user terminal 800 may further include a communication interface 803 and a bus 804 . Wherein, as shown in FIG. 16 , a memory 801 , a processor 802 , and a communication interface 803 are connected through a bus 804 to complete mutual communication.

The communication interface 803 is mainly used to implement communication between modules, devices, units and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through the communication interface 803 .

The bus 804 includes hardware, software or both, and couples the components of the user terminal 800 to each other. For example and not limitation, the bus 804 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (Enhanced Industry Standard Architecture, EISA) bus, a Front Side Bus (FSB), Hyper Transport (HT) interconnect, Industry Standard Architecture (ISA) bus, InfiniBand interconnect, Low pin count (Low pin count, LPC) bus, memory bus, Micro Channel architecture (Micro Channel Architecture, MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-E) bus, Serial Advanced Technology Attachment (Serial Advanced Technology Attachment, SATA) bus, Video Electronics Standards Association local ( Video Electronics Standards Association Local Bus, VLB) bus or other suitable bus or a combination of two or more of these. Bus 804 may comprise one or more buses, where appropriate. Although the embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.

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

The user terminal is configured to send a payment code request message in response to the received payment operation, where the payment code request message includes location information of the user terminal.

The business system is used to receive the payment code request message, obtain the payment waiting time factor information associated with the location information, and send the payment waiting time represented by the payment waiting time factor information associated with the location information is greater than or equal to the preset time threshold. A payment code feedback message, 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 switch the displayed first payment code to the second payment code when the trigger signal of the payment acceptance terminal is sensed.

The business system is further configured to instruct to deduct the payment amount from the payer's 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.

For the specific content of the business system, please refer to the relevant descriptions of the business system 14 in the above embodiment and the business system in the code scanning payment method in the above embodiment, and will not be repeated here. The service system may include service equipment. For the specific content of the service equipment, please refer to the relevant descriptions of the service equipment 500 and the service equipment 700 in the above-mentioned embodiments, and details are not repeated here.

For the specific content of the user terminal, please refer to the relevant descriptions of 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 and the user terminal 800 in the above embodiment, and will not be repeated here.

In some embodiments, the code scanning payment system may also include a payment institution system. For details of the payment institution system, please refer to the relevant descriptions of the payment institution system 13 in the above embodiments and 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. For details of the payment acceptance terminal, please refer to the relevant descriptions of the payment acceptance terminal 12 in the above embodiment and the payment acceptance terminal in the scanning code payment method. .

In some embodiments, the code scanning payment system may also include an account management system. For details of the collection acceptance terminal, please refer to the relevant descriptions of the account management system 15 in the above embodiments and the account management system in the code scanning payment method.

The eighth aspect of the present application also 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 in the embodiment of the above-mentioned first aspect can be realized The payment method and the code-scanning payment method in the embodiment of the second aspect can achieve the same technical effect, so in order to avoid repetition, details are not repeated here. Wherein, the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk. etc., are not limited here.

It should be clear that each embodiment in this specification is described in a progressive manner, and the same or similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. place. For the apparatus embodiments, device embodiments, and computer-readable storage medium embodiments, for relevant parts, refer to the description of the method embodiments. The application is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art may make various changes, modifications, and additions, or change the order between steps, after appreciating the spirit of the present application. Also, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present application. It will be understood that each block of the flowchart and/or block diagrams, and combinations of blocks in the flowchart and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that execution of these instructions via the processor of the computer or other programmable data processing apparatus enables Implementation of the functions/actions specified in one or more blocks of the flowchart and/or block diagrams. Such processors may be, but are not limited to, general purpose processors, special purpose processors, application specific processors, or field programmable logic circuits. It can also be understood that each block in the block diagrams and/or flowcharts and combinations of blocks in the block diagrams and/or flowcharts can also be realized by dedicated hardware for performing specified functions or actions, or can be implemented by dedicated hardware and Combination of computer instructions to achieve.

Those skilled in the art should understand that the above-mentioned embodiments are illustrative rather than restrictive. Different technical features in different embodiments can be combined to achieve beneficial effects. Those skilled in the art should be able to understand and implement other modified embodiments of the disclosed embodiments on the basis of studying the drawings, specification and claims. In the claims, the term "comprising" does not exclude other means or steps; the numerical word "a" does not exclude a plurality; the terms "first" and "second" are used to indicate names and not to indicate any specific order . Any reference signs in the claims should not be construed as limiting the scope. The functions of several parts appearing in the claims can be realized by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to obtain beneficial effects.

Claims

A code scanning payment method applied to a business system, the method comprising:

receiving a payment code request message, the payment code request message being generated by the user terminal in response to a payment operation, including location information of the user terminal;

Acquiring payment waiting time factor information associated with the location information;

When the payment waiting time represented by the payment waiting time length factor information associated with the location information is greater than or equal to the preset time length threshold, 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, so that the user terminal obtains the feedback message of the first payment code, and displays the first payment code before sensing the trigger signal of the collection acceptance terminal, and displays the first payment code after sensing the trigger signal In the case of , switch the displayed first payment code to the second payment code;

When the received payment request message includes the first information, it is instructed to deduct the payment amount from the payer's account indicated by the first information, and the first information includes the information of the second payment code.
The method according to claim 1, further comprising:

In the case that the payment waiting time factor information associated with the location information satisfies the dual-code delivery condition, 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 predetermined Set the duration threshold,

Wherein, the payment waiting time factor information includes one or more of the status information of the payee, the queuing time information of the payee, and the historical waiting time information of users who trade with the payee. Time information includes payment code request time and payment time,

The conditions for issuing the double code include one or more of the following:

The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in a busy state of receiving money,

The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in an event holding state,

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

The time length between the payment code request time and the payment time of the user associated with the location information and the payee transaction is greater than or equal to the preset time length threshold.
The method of claim 1, wherein the payment request message includes transaction information,

The method also includes:

If the received payment request message includes the second information, if the transaction information satisfies the risk control condition, execute transaction intervention processing,

Wherein, the second information includes the information of the first payment code, the risk control condition is used to determine that the payment indicated by the second information has a risk of embezzlement, and the transaction intervention process is used for payment that has a risk of embezzlement. Dispose of safely.
The method according to claim 3, wherein,

The transaction information includes one or more of the following: payee merchant address, payment amount, payment frequency;

The risk control conditions include one or more of the following:

The distance between the address of the payee merchant and the location indicated by the location information is greater than a safety distance threshold,

The payment amount is greater than the security amount threshold,

The payment frequency is higher than a safe frequency threshold.
The method according to claim 3, wherein said transaction intervention process comprises:

authenticating the user of the user terminal sending the payment request message including the second information;

or,

Suspend the payment indicated by the second information.
The method according to claim 3, further comprising:

When the received payment request message includes the second information, if the transaction information does not satisfy the risk control condition, instruct to deduct the payment amount from the payer's account indicated by the second information.
The method according to 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, a second payment code feedback message is sent, and the second payment code feedback message includes the third a payment code, so that the user terminal acquires the feedback message of the second payment code and displays the third payment code;

When the received payment request message includes third information, it is instructed to deduct the payment amount from the payer's account indicated by the third information, where the third information includes information about the third payment code.
The method according to any one of claims 1 to 7, wherein the trigger signal includes one or more of the following:

Near field communication signal, bluetooth signal, acoustic wave signal.
A code scanning payment method applied to a user terminal, the method comprising:

In response to the received payment operation, sending a payment code request message, the payment code request message including 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 acquired by the business system is greater than or equal to the preset time length threshold, the first payment code feedback message is received, and the first payment code feedback message is sent by the business system Generate, including the first payment code and the second payment code;

displaying the first payment code, and switching the displayed first payment code to the second payment code when a trigger signal from the payment acceptance terminal is sensed, so that the business system uses the first payment code The information deducts the payment amount from the payer's account indicated by the first information, and the first information includes the information of the second payment code.
The method of claim 9, wherein,

In the case that the payment waiting time factor information associated with the location information satisfies the dual-code delivery 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 length threshold,

Wherein, the payment waiting time factor information includes one or more of the status information of the payee, the queuing time information of the payee, and the historical waiting time information of users who trade with the payee. Time information includes payment code request time and payment time,

The conditions for issuing the double code include one or more of the following:

The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in a busy state of receiving money,

The state information of the payee associated with the location information indicates that the payee located in the area corresponding to the location information is in an event holding state,

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

The time length between the payment code request time and the payment time of the user associated with the location information and the payee transaction is greater than or equal to the preset time length 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 satisfies the risk control condition, accept transaction intervention processing ,

Wherein, the risk control condition is used to determine that the payment indicated by the second information has a risk of theft, the second information includes the information of the first payment code, and the transaction intervention process is used to secure the payment with the risk of theft. deal with.
The method according to claim 11, wherein the transaction information includes one or more of the following: payee merchant address, payment amount, payment frequency;

The risk control conditions include one or more of the following:

The distance between the address of the payee merchant and the location indicated by the location information is greater than a safety distance threshold,

The payment amount is greater than the security amount threshold,

The payment frequency is higher than a safe frequency threshold.
The method according to claim 11, wherein said transaction intervention processing comprises:

authenticating the user of the user terminal;

or,

Suspend the payment indicated by the second information.
The method of claim 11, 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 does not meet the risk control conditions, the second The payment indicated by the second message is carried out normally.
The method of claim 9, further comprising:

When the payment waiting time represented by the payment waiting time factor information associated with the location information acquired by the business system is less than the preset time threshold, receive a second payment code feedback message, the second payment code feedback message includes the first Three payment code;

The third payment code is displayed, so that the business system uses third information to deduct the payment amount from the payer's account indicated by the third information, and the third information includes the information of the third payment code.
The method according to any one of claims 9 to 15, wherein the trigger signal includes one or more of the following:

Near field communication signal, bluetooth signal, acoustic wave signal.
A business device comprising:

A receiving module, configured to receive a payment code request message, the payment code request message is generated by the user terminal in response to the payment operation, including the location information of the user terminal;

An acquisition module, configured to acquire payment waiting time factor information associated with the location information;

A sending module, configured to send a first payment code feedback message when the payment waiting time represented by the payment waiting time length factor information associated with the location information is greater than or equal to a preset time length threshold, and the first payment code feedback message The message includes the first payment code and the second payment code, so that the user terminal obtains the feedback message of the first payment code, and displays the first payment code before sensing the trigger signal of the collection acceptance terminal, and the first payment code is sensed Switching the displayed first payment code to the second payment code when the trigger signal is received;

A payment processing module, configured to instruct to deduct the payment amount from the payer's account indicated by the first information when the received payment request message includes first information, and the first information includes the information of the second payment code information.
A user terminal, comprising:

A sending module, configured to send a payment code request message in response to the received payment operation, where the payment code request message includes the location information of the user terminal;

The receiving module is configured 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 length threshold, and the first payment code The feedback message is generated by the business system, including the first payment code and the second payment code;

a display module, configured to display the first payment code, and switch the displayed first payment code to the second payment code when the trigger signal of the collection acceptance terminal is sensed, so that the The business system uses the first information to deduct the payment amount from the payer's account indicated by the first information, and the first information includes the information of the second payment code.
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 according to any one of claims 1 to 8 is realized.
A user terminal, comprising: a processor and a memory storing computer program instructions;

When the processor executes the computer program instructions, the code scanning payment method according to any one of claims 9 to 16 is realized.
A code scanning payment system, including a user terminal and a business system;

The user terminal is configured to send a payment code request message in response to the received payment operation, and the payment code request message includes the location information of the user terminal;

The business system is used to receive a payment code request message, acquire payment waiting time factor information associated with the location information, and 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 In the case of a duration threshold, 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 switch the displayed first payment code to the second payment code when a trigger signal from the collection acceptance terminal is sensed;

The business system is further configured to instruct to deduct the payment amount from the payer's account indicated by the first information when the received payment request message includes the first information, and the first information includes the second payment code information.
A computer-readable storage medium, computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the scanning code payment method according to any one of claims 1 to 16 is realized .