Resource transfer authentication method, device, computer equipment and storage medium

Abstract

The present application relates to a resource transfer authentication method, apparatus, computer equipment, storage medium and computer program product. The method includes: receiving a first resource transfer service request; sending a first verification code corresponding to the first resource transfer service; the initial state of the first verification code is unverified; receiving a first code to be verified; when the first code to be verified is consistent with the first verification code, updating the state of the first verification code to a first state; the first state is used to indicate that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not been completed. In this method, by setting the state of the first verification code and updating the state of the first verification code after the verification is successful, repeated verification can be avoided, and repeated responses to the first resource transfer service request caused by repeated verification can be avoided.

Description

Technical Field

[0001] The present application relates to the field of security authentication technology, and in particular to a resource transfer authentication method, apparatus, computer equipment, storage medium, and computer program product. Background Art

[0002] To ensure customer security during resource transfers (such as account transactions), SMS verification codes are often required. For example, for a transfer, a customer must first verify the SMS verification code or bank card password before initiating the transfer. Successful verification allows the transfer to proceed. However, during the transaction process, customers may mistakenly initiate multiple transfers, or their account interface information may be stolen, leading to duplicate transactions. For example, if a customer repeatedly enters the verification code during SMS verification, or if the verification code is stolen and reported to the transaction system, the customer's transaction request may be repeatedly responded to, resulting in a single transfer being executed multiple times, compromising the transaction security of the customer's account.

[0003] Therefore, how to avoid duplicate transactions to ensure the security of the transaction process is a technical problem that needs to be solved urgently. Summary of the Invention

[0004] Based on this, it is necessary to provide a resource transfer authentication method, apparatus, computer device, computer-readable storage medium and computer program product that can improve security in response to the above technical problems.

[0005] In a first aspect, the present application provides a resource transfer authentication method. The method includes: receiving a first resource transfer service request; sending a first verification code corresponding to the first resource transfer service; the first verification code is initially in an unverified state; receiving a first pending verification code; when the first pending verification code is consistent with the first verification code, updating the state of the first verification code to a first state; the first state is used to indicate that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not yet been completed.

[0006] In one embodiment, the method further includes:

[0007] When the transfer operation of the first resource transfer service is completed, the state of the first verification code is updated to a second state; the second state is used to indicate that the transfer operation of the first resource transfer service is completed.

[0008] In one embodiment, the method further includes:

[0009] A verification identifier of the first verification code is generated according to a preset rule; the verification identifier is the encoding of the first verification code; and the verification identifier is used to search for a storage record of the first verification code.

[0010] In one embodiment, the verification identifier of the first verification code includes a first part and a second part; the first part is the source address of the first resource transfer service request; and the second part is the time of receipt of the first resource transfer service request.

[0011] In one embodiment, the method further includes:

[0012] Receive a second verification code;

[0013] When the second code to be verified is consistent with the first verification code, first indication information is generated according to the state of the first verification code; the first indication information is used to indicate whether the second code to be verified passes verification.

[0014] In one embodiment, when the second code to be verified is consistent with the first verification code, generating the first indication information according to the state of the first verification code may include:

[0015] When the second code to be verified is consistent with the first verification code, determining whether the state of the first verification code is the initial state;

[0016] When the state of the first verification code is not the initial state, first indication information is generated, and the first indication information is used to indicate that the second code to be verified has not passed the verification.

[0017] In a second aspect, the present application further provides a resource transfer authentication device, which includes a module capable of implementing the method of the first aspect and any one of its implementations.

[0018] In one embodiment, the apparatus comprises:

[0019] A receiving module, configured to receive a first resource transfer service request;

[0020] A sending module, configured to send a first verification code corresponding to the first resource transfer service; an initial state of the first verification code is unverified;

[0021] The receiving module is further configured to receive a first code to be verified;

[0022] The processing module is configured to update the state of the first verification code to a first state when the first verification code is consistent with the first verification code; the first state is configured to indicate that the first verification code has passed verification but the transfer operation of the first resource transfer service has not been completed.

[0023] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor can implement the steps of the method of the first aspect and any one of its implementations when executing the computer program.

[0024] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, can implement the steps of the method of the first aspect and any one of its implementations.

[0025] In a fifth aspect, the present application further provides a computer program product, which includes a computer program that, when executed by a processor, can implement the steps of the method of the first aspect and any one of its implementations.

[0026] The above-mentioned resource transfer authentication method, apparatus, computer device, storage medium and computer program product can avoid repeated verification and avoid repeated responses to the first resource transfer service request caused by repeated verification by setting the status of the first verification code and updating the status of the first verification code after the verification is successful. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 It is a schematic diagram of an applicable scenario of an embodiment of the present application.

[0028] Figure 2 This is a schematic flowchart of a resource transfer authentication method according to an embodiment of the present application.

[0029] Figure 3 This is a schematic flowchart of another resource transfer authentication method according to an embodiment of the present application.

[0030] Figure 4 FIG. 3 is a schematic diagram of an example of step 307 .

[0031] Figure 5 This is a schematic flowchart of another resource transfer authentication method according to an embodiment of the present application.

[0032] Figures 6 to 9 This is a schematic diagram of the terminal interface at different stages of the resource transfer service in an embodiment of the present application.

[0033] Figure 10 This is a schematic structural diagram of a resource transfer authentication device according to an embodiment of the present application.

[0034] Figure 11 This is a diagram of the internal structure of a computer device according to an embodiment of the present application.

[0035] Figure 12 This is an internal structure diagram of another computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0036] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0037] The resource transfer authentication method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store data that server 104 needs to process. The data storage system can be integrated with server 104, or it can be located in the cloud or on another network server. In resource transfer scenarios, such as resource transfer services such as cash remittances, account transfers, farmer withdrawals, and agency bill payments, users often initiate service requests through terminal 102, and the resource transfer service system then executes the service operation. This resource transfer service system can be, for example, a service system located on a server, network device, or cloud device of a financial institution. In an embodiment of the present application, server 104 receives a first resource transfer service request from terminal 102. Server 104 sends a first verification code corresponding to the first resource transfer service to terminal 102. The first verification code is initially in an unverified state. Server 104 receives a first pending verification code from terminal 102. When the first pending verification code matches the first verification code, server 104 updates the first verification code to a first state, indicating that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not yet been completed. Terminal 102 may include, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices may include smart speakers, smart TVs, smart air conditioners, and smart car devices. Portable wearable devices may include smart watches, smart bracelets, and head-mounted devices. Server 104 may be implemented as a standalone server or a server cluster consisting of multiple servers.

[0038] In one embodiment, Figure 2 As shown, a resource transfer authentication method is provided, which is applied to Figure 1 Taking the server 104 in FIG. 1 as an example, the method includes the following steps:

[0039] Step 201: Receive a first resource transfer service request.

[0040] Resources may include, but are not limited to, electronic vouchers, virtual currency, virtual items, funds, etc. Resource transfer may include transferring resources from a first user's account to a second user's account. The first user and the second user are different users, and the first user or the second user may both be individuals or enterprises. Resource transfer may also include a user depositing resources into their own account, or a user withdrawing resources from their own account. A resource transfer service request may be understood as initiating a resource transfer service. In this application, resource transfer may also include resource transactions, such as common transactions such as consumption, transfers, deposits and withdrawals, remittances, and payments. Resource transfer services in financial institutions such as banks often include cash remittances, transfer remittances, withdrawals, or agency payments, etc., which are not listed one by one.

[0041] Step 201 primarily involves receiving a first resource service request, which may be initiated by a user through a terminal device. For example, a user may initiate a resource transfer service request (e.g., a transaction request) through voice or text on the terminal 102 interface, and the server 104 may then receive the request from the terminal 102 through its communication module. If the terminal 102 is a mobile phone, the request may be initiated through a mobile phone application. If the terminal 102 is a computer, the request may be initiated through a transaction website on the computer. Similar operations may be performed for other types of terminal devices, and therefore are not listed here.

[0042] Step 202: Send a first verification code corresponding to the first resource transfer service.

[0043] The initial state of the first verification code is unverified.

[0044] After receiving the first resource transfer service request, server 104 generates a verification code, namely a first verification code, in response to the request. This first verification code can be, for example, a text message verification code. Server 104 then executes step 202 to send the first verification code to terminal 102. Furthermore, server 104 sets the first verification code to an initial state at this time, meaning that it has not been used (i.e., has not passed verification).

[0045] Step 203: Receive a first code to be verified.

[0046] Server 104 can receive the verification code from terminal 102 via the communication interface. For example, a user views the first verification code sent in step 202 on terminal 102 and enters the first verification code through the interface on terminal 102. If the entry is correct, the user enters the first verification code. However, in practice, users may enter incorrectly. After the verification code (here, the first verification code) entered by the user on terminal 102 is sent, it is received by server 104 when executing step 203.

[0047] Step 204: When the first code to be verified is consistent with the first verification code, the state of the first verification code is updated to the first state.

[0048] The first state is used to indicate that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not been completed.

[0049] After receiving the first code to be verified, the server 104 compares the first code to be verified with the first verification code to see if they are consistent (i.e., identical). If the two are consistent, verification has passed (i.e., verification is successful or verification has passed or verification is successful), and the status of the first verification code can be updated. If the two are inconsistent, verification has failed (i.e., failed or unsuccessful), and the status of the first verification code is not updated. Therefore, if other codes to be verified are subsequently received, the status of the first verification code can be used to determine whether to re-verify.

[0050] In the resource transfer authentication method, by setting the status of the first verification code and updating the status of the first verification code after successful verification, repeated verification can be avoided, and repeated responses to the first resource transfer service request caused by repeated verification can be avoided.

[0051] In one embodiment, Figure 3 As shown, another resource transfer authentication method is provided, which can be regarded as Figure 1 An example of the method shown includes the following steps:

[0052] Step 301: Receive a first resource transfer service request.

[0053] Step 301 can be regarded as an example of step 101 .

[0054] Step 302: Send a first verification code corresponding to the first resource transfer service.

[0055] The initial state of the first verification code is unverified.

[0056] Step 302 can be considered as an example of step 102 .

[0057] Step 303: Generate a verification identifier of the first verification code according to a preset rule.

[0058] The verification identifier can be understood as the encoding of the first verification code and is used to search for the storage record of the first verification code.

[0059] The verification identifier can also be the verification code identifier (ID). Each verification code ID is unique, so the corresponding verification code can be searched by ID. If the verification code is a text message verification code, it can be understood that its verification identifier is the number of the text message verification code.

[0060] The generation rules of the verification mark can be diversified, that is, a certain mapping rule can be set to encode the verification code. The so-called generation rule is the preset rule mentioned above.

[0061] In some implementations, the preset rule may be a mapping function, that is, after the first check code is generated, its corresponding check identifier is generated according to the mapping function. In this type of implementation, the check code is generated first and then the check code identifier.

[0062] In other implementations, a verification identifier can be generated based on information in the first resource transfer service request. For example, the verification identifier can be generated based on information such as the sending time, receiving time, source, or account information or user name information contained in the sent content of the first resource transfer service request. In one example, the sending time of the first resource transfer service request and the user's account information can be used as the verification identifier for the verification code of this request. Other examples are similar and will not be repeated here. In this type of implementation, the verification code and the verification code identifier are generated independently.

[0063] In some implementations, the verification identifier of the first verification code includes a first part and a second part; the first part is the source address of the first resource transfer service request; the second part is the time the first resource transfer service request was received. The source address can be a mobile phone number, login address, or the like. In one example, a preset rule uses the mobile phone number of the user initiating the first resource transfer service request and the time the request was received as the verification identifier. For example, if the sending time can be accurate to the millisecond, the verification identifier is a 28-digit numeric code, with the first 11 digits being the mobile phone number and the last 17 digits being the time of receipt, including the year, month, day, hour, minute, second, and millisecond of the time of receipt. For example, assuming the mobile phone number is 12345678901 and the time of receipt is 08:52:54:234 milliseconds on October 12, 2345, the verification identifier generated according to the preset rule is 1234567890123451012085254234.

[0064] However, it should be understood that there is no restriction on the order of the first part and the second part. For example, in the above example, the second part may come first and then the first part, that is, the receiving time comes first and the mobile phone number comes later.

[0065] In another example, the preset rule is to use the card number and sending time in the service information of the first resource transfer service request as the verification identifier. Assuming that the bank card number is 16 digits and the sending time is 17 digits, the generated verification identifier is 33 digits.

[0066] Among the various preset rules described above, if the verification identifier is determined based on a mapping relationship, a mapping function, a mapping table, or an identification code generator can be used to generate the verification identifier. In other words, the verification identifier can be obtained by substituting the first verification code into the mapping function or identification code generator, or by searching a mapping table. If the verification identifier is generated based on the information of the first resource transfer service request, the verification representation can be obtained by performing some processing on the information of the service request. Regardless of the method used to obtain the verification identifier, as long as the uniqueness of the verification identifier can be guaranteed, that is, each verification code corresponds to only one unique verification identifier.

[0067] In subsequent steps, for example, when the state of the first verification code is updated, the storage record of the first verification code can be quickly searched according to the verification identifier, so as to modify the state of the first verification code.

[0068] Step 304: Receive a first code to be verified.

[0069] Step 304 can be regarded as an example of step 103 .

[0070] Step 305: When the first code to be verified is consistent with the first verification code, the state of the first verification code is updated to the first state.

[0071] The first state is used to indicate that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not been completed.

[0072] Step 305 can be considered as an example of step 104 .

[0073] In practice, an optimistic lock can be added to the first verification code, and its status can be marked as the first state. In this case, even if the front-end triggers multiple resource transfer service requests at the same time, such as triggering two transactions, that is, multiple verification codes pass the verification of the first verification code at the same time, or the first verification code is determined to be consistent with the verification code multiple times, the optimistic lock will prevent the first verification code from being repeatedly verified, thereby preventing duplicate transactions.

[0074] Step 306: Receive a second code to be verified.

[0075] The second verification code can be understood as a verification code different from the first verification code, and the two codes may or may not contain the same content. In practice, the first verification code is the verification code entered by the user based on the first verification code displayed on the terminal. The second verification code may be generated by the user re-entering the code or by external interference such as malware. For example, a virus plugin may also receive the first verification code and then resend the verification code. This resent verification code is the second verification code.

[0076] Step 307: When the second code to be verified is consistent with the first verification code, first indication information is generated according to the status of the first verification code.

[0077] The first indication information is used to indicate whether the second code to be verified passes the verification.

[0078] The second verification code is compared with the first verification code for consistency. If they are inconsistent, the second verification code is incorrect, possibly due to incorrect input or a different verification code. In this case, no further processing is required because it will not interfere with subsequent operations, but the user can be informed of the input error. If they are consistent, the second verification code also passes verification with the first verification code. However, since the first verification code has already passed verification with the first verification code, if it passes verification again this time, it will result in duplicate verification, leading to duplicate transactions and losses for the user.

[0079] Therefore, when the second code to be verified is consistent with the first verification code, first indication information can be further generated according to the state of the first verification code.

[0080] That is, if the state of the first verification code is still in the initial state, it means that the first verification code has not been verified. In this case, the second verification code is equivalent to the first verification code. Therefore, the first indication information can be used to indicate that the second verification code has been verified, and the state of the first verification code can be further updated to the first state. However, it should be understood that in this case, the second verification code is equivalent to the first verification code, so this is the first verification of the first verification code, not a repeated verification.

[0081] If the state of the first verification code is no longer in the initial state, including the first state described above and the second state described below, it means that the first verification code has been verified. If the second verification code is still allowed to pass, it will result in a duplicate verification. This is the duplicate verification that may be caused by user errors or external interference, causing financial losses to the user. In this case, the second verification code should not be allowed to pass, and the user can be informed through the first indication information that the verification failed because this is not the first verification.

[0082] Step 308: When the transfer operation of the first resource transfer service is completed, the state of the first verification code is updated to the second state.

[0083] The second state is used to indicate that the transfer operation (eg, payment of the transaction) of the first resource transfer service (eg, transaction) has been completed.

[0084] That is, if the first resource transfer service is completed, the status of the first verification code is updated to transaction completed.

[0085] The method in the embodiment of the present application has a good anti-duplicate effect for situations where customers make mistakes and hackers maliciously initiate a large number of repeated calls. It can be regarded as an authentication scheme to prevent duplicate transactions to ensure transaction security.

[0086] At present, whether it is a website or an application's trading platform (trading system), most interfaces are developed based on the Application Program Interface (API) model. The security of the API is particularly important. There are two commonly used traditional security authentication schemes: one is to prevent malicious third parties from making effective calls by preventing hackers from obtaining valid data. For example, using https access will greatly increase the difficulty of online packet capture; and the use of a server proxy can effectively prevent the real address of the interface from being exposed. Another solution is to solve the problem by adding session, token and other authentication methods to the back-end interceptor, and to limit the number and frequency of interface accesses in the filter. These can be referred to as front-end authentication and back-end authentication, respectively. The above-mentioned front-end authentication and back-end authentication can be superimposed on the solutions of the embodiments of the present application and executed together, thereby further improving the security of the transaction process.

[0087] The following is a specific example to further explain the solution of the embodiment of the present application. Take the cash remittance business of the application as an example, that is, the transaction platform is an application (Application, APP), and the first resource transfer business is a cash remittance business. The user logs in to the application on the terminal and fills in the user's relevant information (that is, the information of the above-mentioned first resource transfer business, which may include card number, transaction amount, etc.) on the information input page. After the information input is completed, a business request is initiated. Jump to the SMS verification code page, and the user will receive the first verification code. The user enters the first code to be verified. If the verification is passed, it will jump to the transaction password page. The user enters the set transaction password, the password transaction is completed, and the account API is called to initiate the transfer. The API interface returns the transfer status to the front end, and the interface jumps to the result display page, prompting information such as successful transaction.

[0088] In the traditional solution, if a third party captures the information of the call through a packet capture tool after entering the first verification code to complete the verification, and successfully decrypts the https protocol package to obtain the account API related token and parameter information, it can maliciously initiate a large number of repeated transactions, or directly tamper with the parameter information to transfer money to others, causing property losses to the user. However, in the solution of the embodiment of the present application, after the business request is initiated as described above, the first verification code received by the user has an initial state. If the state of the first verification code is updated to the first state after the first verification is passed, the verification code that is subsequently verified again will not be able to pass the verification due to the change in the state of the first verification code. In other words, only the verification code that passes the first verification can allow the subsequent process to continue to execute. Even if other verification codes can pass the verification, they will be blocked due to the change in the state of the first verification code, thereby avoiding repeated verification and avoiding the generation of repeated transactions.

[0089] In one embodiment, Figure 4 As shown, step 307 includes:

[0090] Step 401: When the second code to be verified is consistent with the first verification code, determine whether the state of the first verification code is the initial state.

[0091] Step 402: When the state of the first verification code is not the initial state, generate first indication information, and the first indication information is used to indicate that the second code to be verified has not passed the verification.

[0092] That is to say, if it is not the initial state, it means that the first verification code has been verified and passed. This is a secondary verification, which is blocked and notified to the user through the first indication information.

[0093] In one embodiment, Figure 5 As shown, another resource transfer authentication method is provided, which is applied to Figure 1 The terminal 102 and the server 104 in FIG. 1 are used as an example to illustrate. Figure 5 The method shown can be seen as Figure 1 An example of an interaction process between a terminal and a server in the method shown includes the following steps:

[0094] Step 501: The terminal device sends a first transaction request, and the server receives the first transaction request.

[0095] Step 501 can be regarded as an example of step 201 and step 301 . Figure 5 The transaction in is an example of the resource transfer business mentioned above.

[0096] Step 502: The server generates a first verification code and sets the first verification code to an initial state.

[0097] The initial status is unchecked.

[0098] Step 503: The server sends a first verification code, and the terminal device receives the first verification code.

[0099] Step 502 and step 503 can be regarded as an example of step 202 and step 302 .

[0100] Step 504: The terminal device sends a first code to be verified, and the server receives the first code to be verified.

[0101] Step 504 can be considered as an example of step 203 and step 304 .

[0102] Step 505: The server updates the state of the first verification code from the initial state to the first state.

[0103] Step 505 can be considered as an example of step 204 and step 305 .

[0104] It should be noted that Figure 5 The solution of the embodiment of the present application is explained again from the perspective of interaction between the terminal and the server in order to facilitate further understanding of the solution of the embodiment of the present application. For related content, please refer to the relevant introduction above. Figure 5 The operations performed by the server in Figure 2 and Figure 3 The server performs the same operation.

[0105] Figures 6 to 9 This is a schematic diagram of the interface of the terminal at different stages of the resource transfer business of the embodiment of the present application. The resource transfer business is cash remittance. In this example, Figure 6 , the user sends a first transaction request through the terminal device, the first transaction request includes the information of the first transaction, such as user name, remittance card number, reserved phone number and transaction amount, etc. The business category of the first transaction request is cash remittance. Figure 7 As shown, the transaction system (for example, the server where the transaction system is located) generates a text message verification code (i.e., a first verification code) and sends it to the terminal, and the first verification code also has a verification identifier, i.e. Figure 7 If the user enters the first verification code according to the received SMS verification code and passes the verification, the status of the first verification code is updated to the first status, and the page is redirected to the transaction password verification interface, i.e. Figure 8 That is to say, only after the verification is passed will it jump to Figure 8 The interface shown may return if the verification fails Figure 7 The interface shown prompts the user to re-enter. Figure 8In the interface shown, if the user enters the correct transaction password, the transaction system executes the transfer operation of the first transaction request and updates the state of the first verification code to the second state after the transfer operation is completed.

[0106] Since most of the steps in the embodiment of the present application are mainly implemented by the server side, Figure 6-9 It is the terminal interface, so some steps will not be displayed on the terminal interface. Figure 9 As shown, if there is a risk of repeated verification, the solution of the embodiment of the present application will be blocked and a first indication information will be generated. Figure 9 This is an example of the terminal receiving the first indication information, which prompts the user that the transaction status is abnormal.

[0107] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0108] Based on the same inventive concept, embodiments of the present application also provide a resource transfer authentication device for implementing the resource transfer authentication method described above. The implementation solution provided by this device is similar to the implementation solution described in the above-mentioned method. Therefore, the specific limitations in one or more of the following resource transfer authentication device embodiments can be found in the above-mentioned limitations on the resource transfer authentication method and will not be repeated here.

[0109] In one embodiment, Figure 10 As shown, a resource transfer authentication device is provided. The device 1000 includes: a receiving module 1001, a sending module 1002 and a processing module 1003.

[0110] The apparatus 1000 can be used to perform the steps of the resource transfer authentication method described in any of the above implementations. For example, the receiving module 1001 can be used to perform steps 201 and 203, the sending module can be used to perform step 202, and the processing module can be used to perform step 204. For another example, the receiving module 1001 can be used to perform steps 301, 304, and 306, the sending module can be used to perform step 302, and the processing module can be used to perform steps 303, 305, 307, and 308. For another example, the processing module can be used to perform steps 401 and 402.

[0111] Each module in the resource transfer authentication device described above may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in hardware form, or may be stored in a computer device memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0112] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 11 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as the first check code and the status of the first check code. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a resource transfer authentication method is implemented.

[0113] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 12As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface, the display unit and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a resource transfer authentication method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse.

[0114] Those skilled in the art will understand that Figure 11 and Figure 12 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0115] In one embodiment, a computer device is provided, comprising a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: receiving a first resource transfer service request; sending a first verification code corresponding to the first resource transfer service; the initial state of the first verification code is unverified; receiving a first code to be verified; when the first code to be verified is consistent with the first verification code, updating the state of the first verification code to a first state; the first state is used to indicate that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not been completed.

[0116] In one embodiment, when executing the computer program, the processor further implements the following steps: when the transfer operation of the first resource transfer service is completed, updating the state of the first verification code to a second state; the second state is used to indicate that the transfer operation of the first resource transfer service is completed.

[0117] In one embodiment, when the processor executes the computer program, the following steps are further implemented: generating a verification identifier of the first verification code according to a preset rule; the verification identifier is an encoding of the first verification code; and the verification identifier is used to search for a storage record of the first verification code.

[0118] In one embodiment, the verification identifier of the first verification code includes a first part and a second part; the first part is the source address of the first resource transfer service request; and the second part is the time of receiving the first resource transfer service request.

[0119] In one embodiment, when the processor executes the computer program, it further implements the following steps: receiving a second code to be verified; when the second code to be verified is consistent with the first verification code, generating first indication information according to the status of the first verification code; the first indication information is used to indicate whether the second code to be verified passes the verification.

[0120] In one embodiment, when the processor executes the computer program, the processor further implements the following steps: when the second code to be verified is consistent with the first verification code, determining whether the state of the first verification code is an initial state;

[0121] When the state of the first verification code is not the initial state, first indication information is generated, and the first indication information is used to indicate that the second code to be verified has not passed the verification.

[0122] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: receiving a first resource transfer service request; sending a first verification code corresponding to the first resource transfer service; the initial state of the first verification code is unverified; receiving a first code to be verified; when the first code to be verified is consistent with the first verification code, updating the state of the first verification code to a first state; the first state is used to indicate that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not been completed.

[0123] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: when the transfer operation of the first resource transfer service is completed, the state of the first verification code is updated to a second state; the second state is used to indicate that the transfer operation of the first resource transfer service is completed.

[0124] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: generating a verification identifier of the first verification code according to a preset rule; the verification identifier is an encoding of the first verification code; and the verification identifier is used to search for a storage record of the first verification code.

[0125] In one embodiment, the verification identifier of the first verification code includes a first part and a second part; the first part is the source address of the first resource transfer service request; and the second part is the time of receiving the first resource transfer service request.

[0126] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving a second code to be verified; when the second code to be verified is consistent with the first verification code, generating first indication information according to the status of the first verification code; the first indication information is used to indicate whether the second code to be verified passes the verification.

[0127] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: when the second code to be verified is consistent with the first verification code, determining whether the state of the first verification code is the initial state; when the state of the first verification code is not the initial state, generating first indication information, and the first indication information is used to indicate that the second code to be verified has not passed the verification.

[0128] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps: receiving a first resource transfer service request; sending a first verification code corresponding to the first resource transfer service; the initial state of the first verification code is unverified; receiving a first code to be verified; when the first code to be verified is consistent with the first verification code, updating the state of the first verification code to a first state; the first state is used to indicate that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not been completed.

[0129] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: when the transfer operation of the first resource transfer service is completed, the state of the first verification code is updated to a second state; the second state is used to indicate that the transfer operation of the first resource transfer service is completed.

[0130] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: generating a verification identifier of the first verification code according to a preset rule; the verification identifier is an encoding of the first verification code; and the verification identifier is used to search for a storage record of the first verification code.

[0131] In one embodiment, the verification identifier of the first verification code includes a first part and a second part; the first part is the source address of the first resource transfer service request; and the second part is the time of receiving the first resource transfer service request.

[0132] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving a second code to be verified; when the second code to be verified is consistent with the first verification code, generating first indication information according to the status of the first verification code; the first indication information is used to indicate whether the second code to be verified passes the verification.

[0133] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: when the second code to be verified is consistent with the first verification code, determining whether the state of the first verification code is the initial state; when the state of the first verification code is not the initial state, generating first indication information, and the first indication information is used to indicate that the second code to be verified has not passed the verification.

[0134] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. For purposes of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The processors involved in the various embodiments provided herein may be general-purpose processors, central processing units (CPUs), graphics processors (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), data processing logic devices based on quantum computing, and the like, without limitation thereto.

[0135] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0136] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A resource transfer authentication method, characterized in that: The method comprises: receiving a first resource transfer service request, wherein the resource transfer service request is used to initiate a resource transfer service; Sending a first verification code corresponding to the first resource transfer service; the initial state of the first verification code is unverified; Generate a verification identifier of the first verification code according to a preset rule; the verification identifier is the encoding of the first verification code; the verification identifier is used to search for a storage record of the first verification code; Receive a first verification code; When the first code to be verified is consistent with the first verification code, the state of the first verification code is updated to a first state; the first state is used to indicate that the first verification code has been successfully verified but the transfer operation of the first resource transfer service has not been completed; When the transfer operation of the first resource transfer service is completed, the state of the first verification code is updated to a second state; the second state is used to indicate that the transfer operation of the first resource transfer service is completed.

2. The method according to claim 1, characterized in that The verification identifier of the first verification code includes a first part and a second part; the first part is the source address of the first resource transfer service request; the second part is the receiving time of the first resource transfer service request.

3. The method according to claim 1, characterized in that The method further comprises: Receive a second verification code; When the second code to be verified is consistent with the first verification code, first indication information is generated according to the state of the first verification code; the first indication information is used to indicate whether the second code to be verified passes verification.

4. The method according to claim 3, characterized in that When the second code to be verified is consistent with the first verification code, generating first indication information according to the state of the first verification code includes: When the second code to be verified is consistent with the first verification code, determining whether the state of the first verification code is the initial state; When the state of the first verification code is not the initial state, the first indication information is generated, and the first indication information is used to indicate that the second code to be verified has not passed verification.

5. A resource transfer authentication device, characterized in that: The device comprises: A receiving module, configured to receive a first resource transfer service request, wherein the resource transfer service request is used to initiate a resource transfer service; a sending module, configured to send a first verification code corresponding to the first resource transfer service; an initial state of the first verification code is unverified; Generate a verification identifier of the first verification code according to a preset rule; the verification identifier is the encoding of the first verification code; the verification identifier is used to search for a storage record of the first verification code; The receiving module is further configured to receive a first code to be verified; A processing module for updating the state of the first verification code to a first state when the first verification code is consistent with the first verification code; the first state is used to indicate that the first verification code has passed the verification but the transfer operation of the first resource transfer service has not been completed; When the transfer operation of the first resource transfer service is completed, the state of the first verification code is updated to a second state; the second state is used to indicate that the transfer operation of the first resource transfer service is completed.

6. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

8. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images