Stateless payment method, computer program product and electronic device

By performing multi-dimensional verification of order data and verification code requests in a stateless payment scenario, the security threat caused by the lack of identity authentication on the bank side is solved, and a high-security payment process is achieved.

CN119090505APending Publication Date: 2024-12-06中国邮政储蓄银行股份有限公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411186134.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-27
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the stateless payment scenarios of merchant systems and banking systems, the lack of identity authentication causes payment requests to be simulated or reproduced, which poses a security threat.

Method used

By receiving the order data and verification code request information sent by the client, multi-dimensional verification includes order number verification, bank card verification, merchant payment status verification and verification code verification, to ensure the legality of payment requests and then go to the bank The payment system initiates payment.

Benefits of technology

Effectively identifying and blocking invalid and illegal requests improve the security of payment, avoid the cumbersome operations of secondary login, and enhance the reliability and security of the payment process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119090505A_ABST
    Figure CN119090505A_ABST
Patent Text Reader

Abstract

The invention provides a stateless payment method, a computer program product and electronic equipment, and the method comprises the steps: receiving order data sent by a client through a merchant system, and determining whether the order data is repeated or not; when the order data is not repeated, receiving verification code request information sent by the client; performing order number verification and bank card verification on the verification code request information, and sending an original verification code to the client when the verification code request information passes the order number verification and the bank card verification; and when payment request information is received, order number verification, bank card verification, merchant payment state verification and verification code verification are performed on the payment request information, and payment is initiated to a bank payment system when the payment request information passes the order number verification, the bank card verification, the merchant payment state verification and the verification code verification. The problem that in the prior art, security threats exist when a bank side does not carry out identity authentication on an operation user who carries out payment is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of payment technology, and in particular to a stateless payment method, a computer program product, and an electronic device. Background Art

[0002] When the merchant system connects to the bank system for active payment, the more common implementation method is to perform login authentication before entering the cashier page to determine the operator's identity information, so that subsequent operations such as bank card binding and payment can be carried out in a safe and controllable environment.

[0003] However, in some business scenarios, the merchant system cannot provide identity authentication when entering the checkout page, and the entire payment process is completed in a stateless multi-step interaction, which may lead to the risk of payment requests being simulated and replayed.

[0004] Common active payment checkout pages generally use login to confirm user identity before entering, thus providing a safe and reliable operating environment for a series of subsequent steps.

[0005] In some special business scenarios, when the mall initiates order payment, the bank does not authenticate the operating user. Since the entire payment scenario is completely run in the Internet environment, and there is no identity authentication status between the operation steps, there may be a risk of being simulated and replayed. In particular, some illegal black industries will use various technical means to conduct penetration attacks on Internet financial services exposed to the public network, posing a huge security threat to payment services. Summary of the invention

[0006] The main purpose of the present application is to provide a stateless payment method, a computer program product and an electronic device, so as to at least solve the problem of security threats in the prior art when the bank does not authenticate the identity of the user performing the payment.

[0007] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a stateless payment method is provided, comprising: receiving order data sent by a client through a merchant system, and determining whether the order data is repeated; if the order data is not repeated, receiving verification code request information sent by the client, the verification code request information including an order number and a bank card ID (Identification); performing order number verification and bank card verification on the verification code request information, and sending an original verification code to the client if the verification code request information passes the order number verification and the bank card verification; if payment request information is received, performing order number verification, bank card verification, merchant payment status verification and verification code verification on the payment request information, and initiating payment to a bank payment system if the payment request information passes the order number verification, the bank card verification, the merchant payment status verification and the verification code verification, the payment request information is request information in response to the original verification code, the payment request information includes the order number and a payment verification code, and the payment verification code is a verification code filled in by the client according to the original verification code.

[0008] Optionally, before performing order number verification and bank card verification on the verification code request information, the method also includes: if the order data is not repeated, storing the order data, the order data including the order number and customer information, performing order number verification and bank card verification on the verification code request information, and if the verification code request information passes the order number verification and bank card verification, sending the original verification code to the client, including: determining whether the order number exists; if the order number exists, determining whether the bank card ID exists; if the bank card ID exists, determining whether the bank card ID belongs to the order customer based on the customer information; if the bank card ID belongs to the order customer, sending the original verification code to the client.

[0009] Optionally, after receiving the verification code request information sent by the client and before determining whether the order number exists, the method further includes: determining whether a first transaction duration exceeds a predetermined duration, the first transaction duration being the duration between the moment when the client sends the order data and the moment when the verification code request information is received; determining whether the order number exists includes: determining whether the order number exists when the first transaction duration does not exceed the predetermined duration.

[0010] Optionally, when the bank card ID belongs to the order customer, sending the original verification code to the client includes: when the bank card ID belongs to the order customer, determining whether the number of SMS received by the mobile phone number corresponding to the bank card ID on that day exceeds the predetermined number of SMS; when the number of SMS received by the mobile phone number on that day does not exceed the predetermined number of SMS, sending the original verification code to the client.

[0011] Optionally, the payment request information is subjected to the order number verification, the bank card verification, the merchant payment status verification and the original verification code verification, and when the payment request information passes the order number verification, the bank card verification, the merchant payment status verification and the verification code verification, payment is initiated to the bank payment system, including: determining whether the order number exists; when the order number exists, determining whether the bank card ID exists; when the bank card ID exists, determining whether the bank card ID belongs to the order customer; when the bank card ID belongs to the order customer, determining whether the status corresponding to the order number is an unpaid status; when the status corresponding to the order number is the unpaid status, determining whether the payment verification code is consistent with the original verification code; when the payment verification code is consistent with the original verification code, payment is initiated to the bank payment system.

[0012] Optionally, before performing the order number verification, the bank card verification, the merchant payment status verification and the verification code verification on the payment request information, the method also includes: upon receiving the payment request information, determining whether a second transaction duration exceeds a predetermined duration, the second transaction duration being the duration between the moment when the client sends the order data and the moment when the payment request information is received, and determining whether the order number exists, including: when the second transaction duration does not exceed the predetermined duration, determining whether the order number exists.

[0013] Optionally, when the bank card ID belongs to the order customer, determining whether the status corresponding to the order number is an unpaid status includes: when the bank card ID belongs to the order customer, determining whether the number of payment failures of the bank card ID on that day exceeds the predetermined number of failures; when the number of payment failures does not exceed the predetermined number of failures, determining whether the status corresponding to the order number is the unpaid status.

[0014] Optionally, receiving order data sent by the client through the merchant system includes: receiving encrypted order data sent by the client through the merchant system; and decrypting the encrypted order data using a private key to obtain the order data.

[0015] According to another aspect of the present application, a computer program product is provided, comprising computer instructions, wherein when the computer instructions are executed by a processor, any one of the stateless payment methods is implemented.

[0016] According to another aspect of the present application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include means for executing any one of the stateless payment methods.

[0017] By applying the technical solution of the present application, the order data sent by the client through the merchant system is first received, and it is determined whether the order data is repeated. Then, if the order data is not repeated, the verification code request information sent by the client is received, and the order number verification and bank card verification are performed on the verification code request information. If the verification code request information passes the order number verification and bank card verification, the original verification code is sent to the client. In response to the original verification code, if payment request information is received, the order number verification, bank card verification, merchant payment status verification and verification code verification are performed on the payment request information. Finally, if the payment request information passes the order number verification, bank card verification, merchant payment status verification and verification code verification, payment is initiated to the bank payment system. Compared with the problem of security threats when the bank does not perform identity authentication on the user performing the payment in the prior art, the present application performs multi-dimensional verification (replay request verification, order number verification, bank card verification, merchant payment status verification and verification code verification) on payment requests without identity authentication context information, that is, it utilizes the verification of information specifications and data patterns interacting in different steps of the payment process, integrating technology and business rule verification, which not only avoids the tedious operation of secondary login, but also can effectively identify and block various invalid, illegal and even malicious requests, ensuring a high level of payment security. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings constituting part of the present application are used to provide a further understanding of the present application. The exemplary embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 A schematic diagram of a payment service process in the prior art is shown;

[0020] Figure 2 A hardware structure block diagram of a mobile terminal for executing a stateless payment method provided in an embodiment of the present application is shown;

[0021] Figure 3A schematic diagram of a process of a stateless payment method provided according to an embodiment of the present application is shown;

[0022] Figure 4 A complete business process diagram of a stateless payment method provided according to an embodiment of the present application is shown;

[0023] Figure 5 A schematic diagram of a verification process for order data provided according to an embodiment of the present application is shown;

[0024] Figure 6 A schematic diagram of a verification process for verification code request information provided according to an embodiment of the present application is shown;

[0025] Figure 7 A schematic diagram of a verification process for payment request information provided according to an embodiment of the present application is shown.

[0026] The above drawings include the following reference numerals:

[0027] 102, processor; 104, memory; 106, transmission device; 108, input and output devices. DETAILED DESCRIPTION

[0028] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0029] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] Payment is a financial activity involving the transfer and transaction of funds. With the rise of e-commerce and online transactions, payment security has become an important issue in protecting the financial security of individuals and enterprises. Common Internet shopping malls generally provide payment services at the cash register. The main business processes are as follows: Figure 1 As shown in the figure, the merchant system and the bank cashier work together to complete the overall payment process: 1) the merchant system transmits the order information to the bank cashier; 2) the user selects the bank card for payment and applies for the payment SMS verification code; 3) the user receives the verification code and fills in the page to initiate the payment transaction; 4) the payment result is notified to the merchant to complete the current transaction. The merchant system usually cooperates with the bank or payment institution to realize the payment function by integrating with the bank's payment gateway system. This integration is usually achieved through API (Application Programming Interface) or SDK (Software Development Kit) so that the mall can communicate and interact with the bank's payment system. When the user submits the order in the merchant system and prepares to pay, the merchant system will pass the user's payment request to the payment cashier. The payment cashier is responsible for verifying the payment information, interacting with the bank's payment gateway system, and returning the payment result to the merchant system so that the merchant system can update the order status and feedback the payment result to the user.

[0032] As introduced in the background technology, there are security threats in the prior art when the bank does not authenticate the identity of the operating user. To solve the above problems, the embodiments of the present application provide a stateless payment method, a computer program product and an electronic device.

[0033] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0034] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 2 1 is a hardware structure block diagram of a mobile terminal of a stateless payment method according to an embodiment of the present invention. Figure 2 As shown, the mobile terminal may include one or more ( Figure 2 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the mobile terminal may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 2 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 2 More or fewer components as shown, or with Figure 2 Different configurations are shown.

[0035] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the stateless payment method in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The transmission device 106 is used to receive or send data via a network. The above-mentioned specific examples of the network may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0036] In this embodiment, a stateless payment method running on a mobile terminal, a computer terminal or a similar computing device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0037] Figure 3 is a flow chart of a stateless payment method according to an embodiment of the present application. Figure 3 As shown, the method comprises the following steps:

[0038] Step S201, receiving order data sent by the client through the merchant system, and determining whether the order data is repeated;

[0039] Specifically, the above order data includes order number and customer information.

[0040] Step S202, when the order data is not repeated, receiving verification code request information sent by the client, the verification code request information including the order number and bank card ID;

[0041] Step S203, performing order number verification and bank card verification on the verification code request information, and sending the original verification code to the client if the verification code request information passes the order number verification and bank card verification;

[0042] Step S204, when payment request information is received, the order number verification, bank card verification, merchant payment status verification and verification code verification are performed on the payment request information. When the payment request information passes the order number verification, bank card verification, merchant payment status verification and verification code verification, payment is initiated to the bank payment system. The payment request information is request information in response to the original verification code. The payment request information includes the order number and payment verification code. The payment verification code is a verification code filled in by the client according to the original verification code.

[0043] Specifically, the payment request information is the request information sent by the client in response to the original verification code.

[0044] Through the above embodiment, the order data sent by the client through the merchant system is first received, and it is determined whether the order data is repeated. Then, if the order data is not repeated, the verification code request information sent by the client is received, and the order number verification and bank card verification are performed on the verification code request information. If the verification code request information passes the order number verification and bank card verification, the original verification code is sent to the client. In response to the original verification code, if the payment request information is received, the order number verification, bank card verification, merchant payment status verification and verification code verification are performed on the payment request information. Finally, if the payment request information passes the order number verification, bank card verification, merchant payment status verification and verification code verification, payment is initiated to the bank payment system. Compared with the problem of security threats when the bank does not perform identity authentication on the user performing the payment in the prior art, the present application performs multi-dimensional verification (replay request verification, order number verification, bank card verification, merchant payment status verification and verification code verification) on payment requests without identity authentication context information, that is, it utilizes the verification of information specifications and data patterns interacting in different steps of the payment process, integrating technology and business rule verification, which not only avoids the tedious operation of secondary login, but also can effectively identify and block various invalid, illegal and even malicious requests, ensuring a high level of payment security.

[0045] Specifically, the execution subject in this application is the bank payment front-end. Replay request verification: Determine whether the above order data is repeated (the bank payment front-end performs a duplication check on the message body).

[0046] In an optional solution, before the verification code request information is subjected to order number verification and bank card verification, the method further includes: when the order data is not repeated, the order data is stored, the order data includes the order number and customer information, the verification code request information is subjected to order number verification and bank card verification, and when the verification code request information passes the order number verification and bank card verification, the original verification code is sent to the client, including: determining whether the order number exists; when the order number exists, determining whether the bank card ID exists; when the bank card ID exists, determining whether the bank card ID belongs to the order customer according to the customer information; when the bank card ID belongs to the order customer, the original verification code is sent to the client. In this embodiment, when the order data is not repeated, the order data is stored to prepare for the subsequent order number verification; determining whether the order number exists, when the order number exists, determining whether the bank card ID exists, when the bank card ID exists, determining whether the bank card ID belongs to the order customer according to the customer information, and when the bank card ID belongs to the order customer, the original verification code is sent to the client, which further ensures that the payment security is high.

[0047] In other embodiments, after receiving the verification code request information sent by the client, before determining whether the order number exists, the method further includes: determining whether the first transaction duration exceeds a predetermined duration, the first transaction duration being the duration between the time when the client sends the order data and the time when the verification code request information is received, and determining whether the order number exists includes: determining whether the order number exists when the first transaction duration does not exceed the predetermined duration. In this embodiment, the reliability of the payment service is further ensured by transaction timeout check (determining whether the first transaction duration exceeds the predetermined duration).

[0048] In actual application, technicians in this field can set the above-mentioned predetermined time length based on empirical values, or obtain it through multiple experiments. This application does not impose any specific restrictions on this.

[0049] In some other optional schemes, when the bank card ID belongs to the order customer, the original verification code is sent to the client, including: when the bank card ID belongs to the order customer, determining whether the number of SMS received by the mobile phone number corresponding to the bank card ID on that day exceeds the predetermined number of SMS; when the number of SMS received by the mobile phone number on that day does not exceed the predetermined number of SMS, sending the original verification code to the client. In this embodiment, the reliability of the payment service is further guaranteed by SMS number verification (determining whether the number of SMS received by the mobile phone number corresponding to the bank card ID on that day exceeds the predetermined number of SMS).

[0050] Specifically, the number of SMS messages received by the mobile phone number corresponding to the bank card ID on that day is the number of SMS messages corresponding to the order number sent by the bank payment front-end on that day received by the mobile phone number.

[0051] In actual application, technicians in this field can set the above-mentioned predetermined number of SMS messages based on experience, or obtain it through multiple experiments. This application does not impose any specific restrictions on this.

[0052] In some further optional schemes, the payment request information is subjected to the order number verification, the bank card verification, the merchant payment status verification and the original verification code verification. When the payment request information passes the order number verification, the bank card verification, the merchant payment status verification and the verification code verification, payment is initiated to the bank payment system, including: determining whether the order number exists; when the order number exists, determining whether the bank card ID exists; when the bank card ID exists, determining whether the bank card ID belongs to the order customer; when the bank card ID belongs to the order customer, determining whether the status corresponding to the order number is an unpaid status; when the status corresponding to the order number is the unpaid status, determining whether the payment verification code is consistent with the original verification code; when the payment verification code is consistent with the original verification code, payment is initiated to the bank payment system. In this embodiment, it is determined whether the order number exists. If the order number exists, it is determined whether the bank card ID exists. If the bank card ID exists, it is determined whether the bank card ID belongs to the order customer. If the bank card ID belongs to the order customer, it is determined whether the status corresponding to the order number is an unpaid status. If the status corresponding to the order number is an unpaid status, it is determined whether the payment verification code is consistent with the original verification code. If the payment verification code is consistent with the original verification code, payment is initiated to the bank payment system, further ensuring the reliability and high security of the payment service.

[0053] In some exemplary embodiments, before the payment request information is subjected to the order number verification, the bank card verification, the merchant payment status verification and the verification code verification, the method further includes: upon receiving the payment request information, determining whether the second transaction duration exceeds the predetermined duration, the second transaction duration being the duration between the time when the client sends the order data and the time when the payment request information is received, and determining whether the order number exists, including: determining whether the order number exists when the second transaction duration does not exceed the predetermined duration. In this embodiment, the reliability and security of the payment service are further guaranteed by the transaction timeout verification (determining whether the second transaction duration exceeds the predetermined duration).

[0054] In some other exemplary embodiments, when the bank card ID belongs to the order customer, determining whether the state corresponding to the order number is an unpaid state includes: when the bank card ID belongs to the order customer, determining whether the number of payment failures of the bank card ID on that day exceeds the predetermined number of failures; when the number of payment failures does not exceed the predetermined number of failures, determining whether the state corresponding to the order number is the unpaid state. In this embodiment, by verifying the number of payment failures (determining whether the number of payment failures of the bank card ID on that day exceeds the predetermined number of failures), the reliability and security of the payment service are further guaranteed.

[0055] In actual application, technicians in this field can set the above-mentioned predetermined number of failures based on empirical values, or obtain it through multiple experiments. This application does not impose any specific restrictions on this.

[0056] In other embodiments, receiving the order data sent by the client through the merchant system includes: receiving the encrypted order data sent by the client through the merchant system; using the private key to decrypt the encrypted order data to obtain the order data. In this embodiment, receiving the encrypted order data, and then using the private key to decrypt the encrypted order data to obtain the order data, ensures the security of the order data during transmission, thereby further ensuring the reliability and security of the payment service.

[0057] Specifically, the encrypted order data is obtained by the merchant system encrypting the order data using a public key using an RSA (Rivest-Shamir-Adleman) asymmetric encryption algorithm.

[0058] Specifically, the complete business process of the stateless payment method of this application is as follows: Figure 4 As shown:

[0059] Action 1 is mainly used to open the cashier page of the merchant system, including the nested page of bank payment. In this process, the merchant system will encrypt the order data (order number and customer information) with the public key using the RSA asymmetric encryption algorithm and send it to the bank-side front-end system (bank payment front-end). The verification rules marked at ① are as follows: Figure 5 As shown: 1. Private key decryption verification: the bank payment front-end uses the private key to decrypt the encrypted order data (encrypted order data); 2. Replay request verification: the bank payment front-end performs a duplication check on the message body (order data).

[0060] Action2 mainly implements the function of requesting to send a payment verification code. The user selects the bank card used for payment on the cashier page and initiates the operation of applying for a verification code. The information submitted for this transaction includes the order number and bank card ID. The verification rules marked at ② are as follows Figure 6 As shown: 1. Transaction timeout verification: verify whether the current payment transaction has timed out (determine whether the first transaction duration exceeds the scheduled duration); 2. Order information verification (order number verification): verify whether the order number exists in the bank payment front-end; 3. Bank card verification: verify whether the bank card exists and belongs to the order customer; 4. SMS number verification: verify whether the number of SMS received by the mobile phone number corresponding to the bank card ID on the same day exceeds the limit,

[0061] Action3 mainly implements the function of initiating payment. The user fills in the received SMS verification code on the order payment page to initiate the payment operation. The information submitted for this transaction includes the order number and verification code. The verification rules marked at ③ are as follows: Figure 7 As shown: 1. Transaction timeout check: verify whether the current payment transaction has timed out (determine whether the second transaction duration exceeds the preset duration); 2. Order information check (order number check): verify whether the order number exists in the bank payment front-end; 3. Bank card check: verify whether the bank card exists and belongs to the order customer; 4. Number of payment failures check: verify whether the number of payment failures for the same bank card on the same day exceeds the limit; 5. Merchant payment status check: initiate a query on the merchant system side to verify that the order is in an unpaid state; 6. Verification code check: verify the SMS payment verification code.

[0062] Specifically, Figure 5 , Figure 6 and Figure 7 As shown, if various checks fail, an exception is returned.

[0063] In order to enable those skilled in the art to more clearly understand the technical solution of the present application, the implementation process of the stateless payment method of the present application will be described in detail below in combination with specific embodiments.

[0064] This embodiment relates to a specific stateless payment method, including the following steps:

[0065] Step S1: receiving the encrypted order data sent by the client through the merchant system, decrypting the encrypted order data using the private key to obtain the order data, and determining whether the order data is repeated;

[0066] Step S2: if the order data is not repeated, store the order data and receive the verification code request information sent by the client, where the verification code request information includes the order number and bank card ID;

[0067] Step S3: Determine whether the first transaction duration exceeds the predetermined duration, where the first transaction duration is the duration between the time when the client sends the order data and the time when the verification code request information is received; if the first transaction duration does not exceed the predetermined duration, determine whether the order number exists; if the order number exists, determine whether the bank card ID exists; if the bank card ID exists, determine whether the bank card ID belongs to the order customer based on the customer information; if the bank card ID belongs to the order customer, determine whether the number of SMS messages received by the mobile phone number corresponding to the bank card ID on that day exceeds the predetermined number of SMS messages; if the number of SMS messages received by the mobile phone number on that day does not exceed the predetermined number of SMS messages, send the original verification code to the client;

[0068] Step S4: receiving payment request information sent by the client, the payment request information is request information in response to the original verification code, the payment request information includes an order number and a payment verification code, and the payment verification code is a verification code filled in by the client according to the original verification code;

[0069] Step S5: Determine whether the second transaction duration exceeds the predetermined duration, the second transaction duration is the duration between the time when the client sends the order data and the time when the payment request information is received; if the second transaction duration does not exceed the predetermined duration, determine whether the order number exists; if the order number exists, determine whether the bank card ID exists; if the bank card ID exists, determine whether the bank card ID belongs to the order customer; if the bank card ID belongs to the order customer, determine whether the number of payment failures of the bank card ID on that day exceeds the predetermined number of failures; if the number of payment failures does not exceed the predetermined number of failures, determine whether the status corresponding to the order number is an unpaid status; if the status corresponding to the order number is an unpaid status, determine whether the payment verification code is consistent with the original verification code; if the payment verification code is consistent with the original verification code, initiate payment to the bank payment system.

[0070] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0071] The present application also provides a computer program product, including computer instructions, which, when executed by a processor, implement at least the following method steps: step S201, receiving order data sent by a client through a merchant system, and determining whether the order data is repeated; step S202, if the order data is not repeated, receiving verification code request information sent by the client, the verification code request information including an order number and a bank card ID; step S203, performing order number verification and bank card verification on the verification code request information, and if the verification code request information passes the order number verification and bank card verification, Send the original verification code to the above-mentioned client; step S204, when the payment request information is received, the above-mentioned order number verification, the above-mentioned bank card verification, the above-mentioned merchant payment status verification and the verification code verification are performed on the above-mentioned payment request information, and when the above-mentioned payment request information passes the above-mentioned order number verification, the above-mentioned bank card verification, the above-mentioned merchant payment status verification and the above-mentioned verification code verification, the payment is initiated to the bank payment system, the above-mentioned payment request information is the request information in response to the above-mentioned original verification code, the above-mentioned payment request information includes the above-mentioned order number and the payment verification code, and the above-mentioned payment verification code is the verification code filled in by the above-mentioned client according to the above-mentioned original verification code.

[0072] Optionally, before performing order number verification and bank card verification on the verification code request information, the method further includes: if the order data is not repeated, storing the order data, the order data including the order number and customer information, performing order number verification and bank card verification on the verification code request information, and if the verification code request information passes the order number verification and bank card verification, sending the original verification code to the client, including: determining whether the order number exists; if the order number exists, determining whether the bank card ID exists; if the bank card ID exists, determining whether the bank card ID belongs to the order customer based on the customer information; if the bank card ID belongs to the order customer, sending the original verification code to the client.

[0073] Optionally, after receiving the verification code request information sent by the client and before determining whether the order number exists, the method further includes: determining whether the first transaction duration exceeds a predetermined duration, the first transaction duration being the duration between the moment when the client sends the order data and the moment when the verification code request information is received, and determining whether the order number exists includes: determining whether the order number exists when the first transaction duration does not exceed the predetermined duration.

[0074] Optionally, when the bank card ID belongs to the order customer, the original verification code is sent to the client, including: when the bank card ID belongs to the order customer, determining whether the number of SMS received by the mobile phone number corresponding to the bank card ID on that day exceeds the predetermined number of SMS; when the number of SMS received by the mobile phone number on that day does not exceed the predetermined number of SMS, sending the original verification code to the client.

[0075] Optionally, the payment request information is subjected to the order number verification, the bank card verification, the merchant payment status verification and the original verification code verification. When the payment request information passes the order number verification, the bank card verification, the merchant payment status verification and the verification code verification, payment is initiated to the bank payment system, including: determining whether the order number exists; when the order number exists, determining whether the bank card ID exists; when the bank card ID exists, determining whether the bank card ID belongs to the order customer; when the bank card ID belongs to the order customer, determining whether the status corresponding to the order number is an unpaid status; when the status corresponding to the order number is the unpaid status, determining whether the payment verification code is consistent with the original verification code; when the payment verification code is consistent with the original verification code, initiating payment to the bank payment system.

[0076] Optionally, before performing the order number verification, the bank card verification, the merchant payment status verification and the verification code verification on the payment request information, the method further includes: upon receiving the payment request information, determining whether a second transaction duration exceeds a predetermined duration, the second transaction duration being the duration between the moment when the client sends the order data and the moment when the payment request information is received, and determining whether the order number exists, including: when the second transaction duration does not exceed the predetermined duration, determining whether the order number exists.

[0077] Optionally, when the bank card ID belongs to the order customer, determining whether the status corresponding to the order number is an unpaid status includes: when the bank card ID belongs to the order customer, determining whether the number of payment failures of the bank card ID on that day exceeds the predetermined number of failures; when the number of payment failures does not exceed the predetermined number of failures, determining whether the status corresponding to the order number is the unpaid status.

[0078] Optionally, receiving order data sent by the client through the merchant system includes: receiving encrypted order data sent by the client through the merchant system; and decrypting the encrypted order data using a private key to obtain the order data.

[0079] An embodiment of the present application also provides an electronic device, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include a method for executing any one of the above-mentioned stateless payment methods.

[0080] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0081] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0082] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0083] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0084] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0085] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0086] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0087] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0088] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0089] From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:

[0090] In the stateless payment method of the present application, first, the order data sent by the client through the merchant system is received, and it is determined whether the order data is repeated. Then, if the order data is not repeated, the verification code request information sent by the client is received, and the order number verification and bank card verification are performed on the verification code request information. If the verification code request information passes the order number verification and bank card verification, the original verification code is sent to the client. In response to the original verification code, if the payment request information is received, the order number verification, bank card verification, merchant payment status verification and verification code verification are performed on the payment request information. Finally, if the payment request information passes the order number verification, bank card verification, merchant payment status verification and verification code verification, payment is initiated to the bank payment system. Compared with the problem of security threats when the bank does not perform identity authentication on the user performing the payment in the prior art, the present application performs multi-dimensional verification (replay request verification, order number verification, bank card verification, merchant payment status verification and verification code verification) on payment requests without identity authentication context information, that is, it utilizes the verification of information specifications and data patterns interacting in different steps of the payment process, integrating technology and business rule verification, which not only avoids the tedious operation of secondary login, but also can effectively identify and block various invalid, illegal and even malicious requests, ensuring a high level of payment security.

[0091] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A stateless payment method, characterized in that: include: Receiving order data sent by the client through the merchant system, and determining whether the order data is repeated; In the case where the order data is not repeated, receiving verification code request information sent by the client, the verification code request information including the order number and the bank card ID; Performing order number verification and bank card verification on the verification code request information, and sending the original verification code to the client if the verification code request information passes the order number verification and the bank card verification; When payment request information is received, the order number verification, the bank card verification, the merchant payment status verification and the verification code verification are performed on the payment request information. When the payment request information passes the order number verification, the bank card verification, the merchant payment status verification and the verification code verification, payment is initiated to the bank payment system. The payment request information is the request information in response to the original verification code. The payment request information includes the order number and the payment verification code. The payment verification code is the verification code filled in by the client according to the original verification code.

2. The stateless payment method according to claim 1, characterized in that: Before performing order number verification and bank card verification on the verification code request information, the method further includes: storing the order data when the order data is not repeated, the order data including the order number and customer information, The verification code request information is subjected to order number verification and bank card verification, and when the verification code request information passes the order number verification and the bank card verification, the original verification code is sent to the client, including: determining whether the order number exists; when the order number exists, determining whether the bank card ID exists; when the bank card ID exists, determining whether the bank card ID belongs to the order customer based on the customer information; when the bank card ID belongs to the order customer, sending the original verification code to the client.

3. The stateless payment method according to claim 2, characterized in that: After receiving the verification code request information sent by the client, before determining whether the order number exists, the method further includes: determining whether a first transaction duration exceeds a predetermined duration, the first transaction duration being the duration between the time when the client sends the order data and the time when the verification code request information is received, Determining whether the order number exists includes: determining whether the order number exists when the first transaction duration does not exceed the predetermined duration.

4. The stateless payment method according to claim 2, characterized in that: In the case where the bank card ID belongs to the order customer, sending the original verification code to the client includes: If the bank card ID belongs to the order customer, determine whether the number of SMS messages received by the mobile phone number corresponding to the bank card ID on that day exceeds the predetermined number of SMS messages; When the number of SMS messages received by the mobile phone number on the same day does not exceed the predetermined number of SMS messages, the original verification code is sent to the client.

5. The stateless payment method according to claim 1, characterized in that: Performing the order number verification, the bank card verification, the merchant payment status verification and the original verification code verification on the payment request information, and initiating payment to the bank payment system when the payment request information passes the order number verification, the bank card verification, the merchant payment status verification and the verification code verification, including: Determine whether the order number exists; If the order number exists, determine whether the bank card ID exists; If the bank card ID exists, determine whether the bank card ID belongs to the order customer; In the case where the bank card ID belongs to the order customer, determining whether the status corresponding to the order number is an unpaid status; When the state corresponding to the order number is the unpaid state, determining whether the payment verification code is consistent with the original verification code; In case the payment verification code is consistent with the original verification code, payment is initiated to the bank payment system.

6. The stateless payment method according to claim 5, characterized in that: Before performing the order number verification, the bank card verification, the merchant payment status verification and the verification code verification on the payment request information, the method further includes: upon receiving the payment request information, determining whether a second transaction duration exceeds a predetermined duration, the second transaction duration being the duration between the time when the client sends the order data and the time when the payment request information is received, Determining whether the order number exists includes: determining whether the order number exists when the second transaction duration does not exceed the predetermined duration.

7. The stateless payment method according to claim 5, characterized in that: In the case where the bank card ID belongs to the order customer, determining whether the status corresponding to the order number is an unpaid status includes: If the bank card ID belongs to the order customer, determining whether the number of payment failures of the bank card ID on that day exceeds a predetermined number of failures; When the number of payment failures does not exceed the predetermined number of failures, it is determined whether the state corresponding to the order number is the unpaid state.

8. The stateless payment method according to claim 1, characterized in that: Receive order data sent by the client through the merchant system, including: Receiving encrypted order data sent by the client through the merchant system; The encrypted order data is decrypted using a private key to obtain the order data.

9. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the stateless payment method described in any one of claims 1 to 8 is implemented.

10. An electronic device, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include instructions for executing the stateless payment method described in any one of claims 1 to 8.