TWI789972B - Transaction verification system and method capable of suspending connection - Google Patents

Abstract

A transaction verification system, comprises: a bank server and a mobile device. The bank server is configured to output a coded message when receiving a transaction request. A mobile device connecting to the bank server, the mobile device has a user interface to receive a transaction command. The mobile device outputs the transaction request to the bank server when receiving the transaction command. The mobile device receives the coded message and generates a verification message according to the coded message. The mobile device further inputs the verification message to a verification column of the user interface to output the verification message to the bank server through the user interface. The bank server further performs a verification procedure based on the received verification message. The bank server performs the transaction request when the verification message passes the verification procedure. The present disclosure further discloses a transaction verification method.

Description

Transaction verification system and method with interruptible connection

The present invention relates to an interruptible connection transaction verification system and method, in particular to an interruptible connection transaction verification system and method in which a mobile device and a bank server can verify each other's legitimacy.

In order to provide users with a convenient and secure online transaction mechanism, many banking institutions currently send verification passwords through SMS for verification, so that users do not need to prepare other hardware devices, and only need to pass through the mobile device door agreed with the bank number, you can obtain the verification password in time to complete the transaction or identity verification when making a transaction or making an identity verification request.

However, the verification password sent by SMS can only be used by the bank server to judge the legitimacy of the mobile device, and the mobile device cannot judge the legitimacy of the bank server, and when the message is transmitted between the mobile device and the bank server, If a Man-in-the-middle attack (MITM) is launched, mobile devices and bank servers will not be able to detect it in time, which increases the risk of users mistakenly entering verification information into phishing websites when receiving messages.

In view of the above, the present invention provides a transaction verification system and method that can interrupt the connection to meet the above requirements.

According to an embodiment of the present invention, the transaction verification system with interruptible connection includes: a bank server, which is used to randomly generate and output a coded message when receiving a transaction request; and a mobile device, connected to the bank server , the mobile device has a user interface to receive a transaction instruction, and output the transaction request to the bank server when receiving the transaction instruction, the mobile device receives the coded message, and generates a verification message according to the coded message , the mobile device further inputs the verification message into a verification field of the user interface, so as to output the verification message to the bank server through the user interface, wherein the bank server receives the verification message Further executing a verification procedure based on the verification message, the bank server executes the transaction request when the verification message passes the verification procedure, wherein the coded message includes a keyword associated with the transaction request and a verification code, the key The words include a transfer account, a transaction amount and a transaction type, and the mobile device further judges whether the keyword is a part of the transaction request, and the mobile device judges that the keyword is a part of the transaction request When decoding the verification code into a verification string, and using the verification string as the verification message, when the mobile device determines that the keyword is not part of the transaction request, it interrupts the user interface and the bank Server connection.

According to an embodiment of the present invention, a transaction verification method that can interrupt connection includes: receiving a transaction instruction with a user interface of a mobile device; outputting a transaction request to a bank server when receiving the transaction instruction with the mobile device device; the bank server randomly generates and outputs a coded message to the mobile device when receiving the transaction request; the mobile device generates a verification message based on the coded message; and the mobile device inputs the verification message to the mobile device a verification field of the user interface, so as to output the verification message to the bank server through the user interface; execute a verification procedure based on the verification message with the bank server; and when the verification message passes the verification procedure , execute the transaction request with the bank server, wherein the encoded message includes a keyword associated with the transaction request and a verification code, the keyword includes a transfer-out account, a transaction amount and a transaction type, and the action The device generates the verification message based on the coded message: the mobile device determines whether the keyword is part of the transaction request; when the mobile device determines that the keyword is a part of the transaction request, the action The device decodes the verification code into a verification string, and uses the verification string as the verification message; and when the mobile device determines that the keyword is not part of the transaction request, the mobile device terminates the use The connection between the operator interface and the bank's server.

To sum up, according to the transaction verification system and method with interruptible connection shown in one or more embodiments of the present invention, the mobile device and the bank server can interactively determine each other's legitimacy, so as to avoid information security loopholes. In addition, according to the transaction verification system and method shown in one or more embodiments of the present invention, the mobile device and the bank server can find out in time whether the message is intercepted or attacked by a man-in-the-middle, and based on this Implement countermeasures, and avoid the risk of users mistakenly entering verification information into phishing websites when receiving messages.

The above description of the disclosure and the following description of the implementation are used to demonstrate and explain the spirit and principle of the present invention, and provide a further explanation of the patent application scope of the present invention.

The detailed features and advantages of the present invention are described in detail below in the implementation mode, and its content is enough to make any person familiar with the related art understand the technical content of the present invention and implement it accordingly, and according to the content disclosed in this specification, the scope of the patent application and the drawings , anyone skilled in the art can easily understand the purpose and advantages of the present invention. The following examples are to further describe the concept of the present invention in detail, but not to limit the scope of the present invention in any way.

Please refer to FIG. 1 . FIG. 1 is a block diagram of a transaction verification system that can interrupt connections according to an embodiment of the present invention. The transaction verification system with interruptible connection shown in the present invention preferably includes a mobile device 10 and a bank server 20 , and the mobile device 10 is connected to the bank server 20 in communication.

The mobile device 10 shown in the present invention is, for example, a mobile phone, a notebook computer, a tablet computer, etc.; the bank server 20 is preferably a server inside the bank or other computing devices with computing capability and signal transmission capability inside the bank. In addition, the mobile device 10 shown in the present invention can preferably be used to present a user interface, and the user interface is connected to the bank server 20 through the mobile device 10, so as to transmit data to the bank server 20, or from The bank server 20 receives the data.

In order to explain in detail the transaction verification system and method with interruptible connection disclosed in the present invention, please refer to Fig. 1 and Fig. 2 together, wherein Fig. 2 is a transaction verification method with interruptible connection according to an embodiment of the present invention flow chart.

Step S10: Receive a transaction instruction.

The mobile device 10 can present the above-mentioned user interface to receive a transaction instruction. For example, the user interface presented by the mobile device 10 may have an order input field for the user to enter a transaction order in the order input field, wherein the order input field may be a blank field for the user to enter Enter the transaction order by yourself. The order input field can also be composed of one or more order keys, and the user can click one of the order keys as a transaction order.

Step S20: Output the transaction request to the bank server.

After receiving the transaction instruction, the user interface of the mobile device 10 converts the transaction instruction into a transaction request, and outputs the transaction request to the bank server 20 . In detail, since the transaction instruction is input by the user, after receiving the transaction instruction, the user interface of the mobile device 10 preferably converts the transaction instruction into a corresponding transaction request, and outputs the transaction request to the bank server 20.

For example, the transaction instruction received by the mobile device 10 through the user interface can be "transfer 5,000 yuan from account A of the bank to account B of the bank". After receiving the transaction instruction, the user interface can transfer "transfer from account A of the bank "Transfer 5,000 yuan to account B" is converted into a corresponding transaction request, and the transaction request includes "account number of account A", "account number of account B" and "transfer 5,000 yuan", and the transaction request is output to the bank server through the mobile device 10 device 20.

Step S30: Output the coded message to the mobile device.

After receiving the transaction request, the bank server 20 outputs a corresponding coded message to the mobile device 10 based on the transaction request. That is, the memory of the bank server 20 may pre-store a corresponding table, and the corresponding table records the coded information corresponding to each transaction request. In addition, the bank server 20 may also randomly generate a coded message after receiving the transaction request, and then store the generated coded message and the corresponding transaction request in the memory for future access. In other words, the content of the coded message may be a combination of one or more of English letters, numbers, Chinese characters, symbols, etc., and the present invention does not limit the content of the coded message.

For example, the coded message generated by the bank server 20 is, for example, a message including a verification code. When the bank server 20 outputs the coded message including the verification code to the mobile device 10, it can also send the verification code, transaction request and The basic information of the mobile device 10 (for example, phone number, location, account password for entering the user interface, etc.) and the like are stored in the memory. The implementation of the bank server 20 generating the encoded message including the verification code will be described in detail in FIG. 3 below.

Step S40: Generate a verification message according to the coded message.

After receiving the coded message, the mobile device 10 can generate a corresponding verification message according to the coded message. That is to say, the coded message received by the mobile device 10 may only include the above-mentioned verification code, or include the verification code and a text description about the transaction request. When the coded message only includes a verification code, the verification message can be the verification code; when the coded message includes a verification code and a text description about the transaction request, the verification message can include the verification code and keywords about the transaction request wait. Please refer to the description of FIG. 3 below for the detailed flow of step S40.

Please continue to refer to step S50: inputting the verification information into the verification field of the user interface.

The mobile device 10 inputs the verification message generated by it into the verification field of the user interface, so that when the user confirms that the verification message has been filled in the verification field, he can input a confirmation command (for example, a confirmation key) on the user interface. When the mobile device 10 receives the confirmation command through the user interface, it outputs the verification message to the bank server 20 through the user interface.

Step S60: Execute a verification procedure based on the verification message.

The bank server 20 can execute a verification program based on the received verification message, so as to determine whether the mobile device 10 is a verified device according to the verification message. The verification procedure described above will be described in detail in FIG. 4 and FIG. 5 below.

Step S70: Execute the transaction request.

When the bank server 20 determines that the verification message has passed the verification procedure, it indicates that the mobile device 10 is a device that has passed the verification. Therefore, when the bank server 20 judges that the certificate message has passed the verification procedure, it can execute the transaction request it receives. That is, taking the above-mentioned transaction request including "account number of account A", "account number of account B" and "transfer 5,000 yuan" as an example, the bank server 20 may execute the transfer procedure when judging that the verification message has passed the verification procedure, so as to Transfer the amount of 5,000 yuan from account A to account B.

Accordingly, when the user inputs a transaction instruction, the bank server 20 can execute the transaction request corresponding to the transaction instruction when confirming that the mobile device 10 is a verified device, so as to avoid outputting the verification message to the mobile device by the bank server 20 During the process of 10, the verification message was intercepted by someone with intentions, resulting in information security loopholes.

Please refer to FIG. 1 and FIG. 3 together, wherein FIG. 3 is a detailed flow chart of step S40 shown in FIG. 2 . After the bank server 20 outputs the coded message to the mobile device 10 in step S20, the mobile device 10 can generate a verification message according to the coded message in step S40.

Please refer to step S401 in FIG. 3 : determine whether the keyword is part of the transaction request.

Specifically, the coded message received by the mobile device 10 may include a keyword associated with the transaction request and the aforementioned verification code. When the mobile device 10 judges that the keyword contained in the encoded message is a part of the transaction request, it determines that the bank server 20 has received the correct transaction request, so the mobile device 10 can execute the following step S403.

Taking the above-mentioned transaction request including "account number of account A", "account number of account B" and "transfer 5000 yuan" as an example, when the coded message received by mobile device 10 contains "transfer" and/or "5000 yuan" etc. keywords, the mobile device 10 can determine whether the transaction requests of "account number of account A", "account number of account B" and "transfer 5000 yuan" include keywords such as "transfer" and/or "5000 yuan". It should be noted that the keywords "transfer" and/or "5000 yuan" mentioned above are only examples, and the keywords can also be "account number of account A" and/or "account number of account B", etc. The type of keyword to be restricted.

When the mobile device 10 determines that the transaction request does not contain a keyword, it may execute step S402: control the user interface to disconnect from the bank server.

That is, the mobile device 10 can control the user interface to log out, so as to terminate the connection with the bank server 20 . Because when the mobile device 10 judges that the transaction request does not contain keywords, it means that the transaction request output to the bank server 20 in step S20 may be intercepted and tampered with, or the encoded message received from the bank server 20 in step S30 Tampering was blocked. Therefore, the mobile device 10 can control the user interface to interrupt the connection with the bank server 20 to prevent subsequent messages/signal transmission between the mobile device 10 and the bank server 20 from being intercepted and tampered with again.

In addition, when the mobile device 10 determines that the transaction request does not contain keywords, the user interface may display an instruction input field again for the user to input the transaction instruction in the user interface again.

Please continue to refer to step S401. When the mobile device 10 determines that the keyword is part of the transaction request, the mobile device 10 can execute step S403: decode the verification code into a verification string.

In detail, the verification code generated by the bank server 20 is, for example, a one-time password (One Time Password, OTP), and each one-time password will be deleted after one verification is completed, and the bank server 20 will verify it in the next verification. Regenerating another one-time password from time to time not only saves the memory space of the bank server 20, but also avoids the problem of information security loopholes caused by repeated use of the one-time password.

For example, the verification code in the form of a one-time password can be a verification code randomly generated by the bank server 20, and the verification code can be composed of one or more combinations of English letters, numbers, symbols, etc. The present invention does not apply to the verification code form is restricted.

In addition, the mobile device 10 can decode the verification code into a verification string according to a pre-stored decoding rule. For example, the pre-stored decoding rules such as "0" corresponds to the English letter "A"; "1" corresponds to the English letter "B"; "2" corresponds to the English letter "C"; "25" corresponds to the English letter "Z" and so on and so on. Therefore, when the verification code is "2.14.3.4", the mobile device 10 can decode the verification code into a verification string of "CODE". Or, when the verification code is "13.0.12.4", the mobile device 10 can decode the verification code into "NAME", and use "NAME" as the verification string, and the mobile device 10 can also judge the bank server based on "NAME". 20 is to request the user's name as a verification string, so the mobile device 10 decodes the verification code to generate a verification string, for example, the user's name "Wang Xiaoming".

The aforementioned pre-stored decoding rules are just examples. Numbers can also correspond to English letters. "25" corresponds to the English letter "A"; "24" corresponds to the English letter "B"; "23" corresponds to the English letter "C"; "0" corresponds to The English letter "Z" and so on, or the verification code is presented in English letters, and the verification string is presented in numbers.

After generating the verification string, the mobile device 10 executes step S405: using the verification string as a verification message.

Taking the above verification string as an example, the mobile device 10 can use the verification strings such as "CODE" and "Wang Xiaoming" as the verification message, or when the mobile device 10 judges that the verification code is from the bank server 20, it can directly Use the verification code of "2.14.3.4" as the verification message.

Accordingly, the mobile device 10 can input the verification information into the verification field of the user interface in step S50 , so as to output the verification information to the bank server 20 .

Please refer to FIG. 1 and FIG. 4 together. FIG. 4 is a flowchart of a verification procedure according to an embodiment of the present invention.

After the bank server 20 receives the verification message from the mobile device 10 (step S50 ), the bank server 20 can execute the verification procedure based on the verification message.

Step S601a: Determine whether the verification character string corresponds to the verification code.

Taking the above verification string as an example, the bank server 20 can determine whether the verification string "CODE" corresponds to the verification code "2.14.3.4"; whether the verification string "NAME" corresponds to the verification code "13.0.12.4"; Whether the string "Wang Xiaoming" corresponds to the verification code "13.0.12.4", etc., to determine whether the verification string corresponds to the verification code.

When the bank server 20 determines that the verification string does not correspond to the verification code, the bank server 20 executes step S602a: generating an exception record associated with the mobile device.

That is, when the bank server 20 judges that the verification string does not correspond to the verification code, it means that the bank server 20 is in the process of outputting a coded message to the mobile device 10, and/or the mobile device 10 is outputting a verification message to the bank server 20 During the process, the message may be attacked by Man-in-the-middle attack (MITM), for example, the message is intercepted during transmission, or the message is tampered with during transmission. Therefore, the bank server 20 can generate an abnormal record associated with the mobile device 10, and store the abnormal record in the bank database, and the abnormal record includes, for example, the time when the verification message is received from the mobile device 10, and the user information obtained from the mobile device 10. To receive the account password of the transaction request, etc. In addition, the bank server 20 may also interrupt the connection between the bank server 20 and the mobile device 10 when judging that the verification string does not correspond to the verification code.

Before the bank server 20 executes step S601a, the bank server 20 can further judge whether the verification message is received within a preset time, wherein the preset time is, for example, 5 minutes, etc., but the present invention does not determine the actual length of the preset time be restricted. When the bank server 20 judges that the verification message has not been received within the preset time, then execute step S602a, or interrupt the connection between the bank server 20 and the mobile device 10, so as to avoid the message being intercepted again; and when the bank When the server 20 determines that the verification message is received within the preset time, it further executes step S601a to determine whether the verification string corresponds to the verification code.

Please return to step S601a. When the bank server 20 determines that the verification string corresponds to the verification code, the bank server 20 can execute step S603a: determine that the verification message has passed the verification procedure. That is, when the bank server 20 judges that the verification string corresponds to the verification code, it means that the bank server 20 judges that the mobile device 10 is an authentication device, and the transaction request from the mobile device 10 is an executable transaction request, so the bank The server 20 can execute step S70 as shown in FIG. 2: execute the transaction request.

Please refer to FIG. 1 and FIG. 5 together. FIG. 5 is a flowchart of a verification procedure according to another embodiment of the present invention.

Step S601b: Determine whether the verification message matches the coded message, and whether the transaction amount has not reached the abnormal amount.

Whether the bank server 20 judges whether the verification message conforms to the coded message can be the same as the judging method of the above-mentioned step S601a in FIG. The exception record associated with the mobile device, wherein the above-mentioned exception record can be the same as the exception record of step S602a in FIG. .

The abnormal amount is a normal transaction amount plus an abnormal amount. The normal transaction amount is, for example, the range formed by the amount when the user usually executes the transaction, and the abnormal amount is, for example, 50% of the upper limit of the normal transaction amount range, but the present invention does not limit the setting of the abnormal amount.

For example, when a user usually inputs a transfer instruction, he requests to transfer 3,000 yuan from account A of the bank to account B, and when the abnormal amount is, for example, 1,500 yuan, the abnormal amount is 4,500 yuan. When bank A transfers 5,000 yuan to account B", the bank server 20 can determine whether the transaction amount of 5,000 yuan exceeds the abnormal amount of 4,500 yuan.

When the bank server 20 determines that the transaction amount reaches an abnormal amount, the bank server 20 may execute step S602b: generate an abnormal record associated with the mobile device. And the abnormal record mentioned above may further include the record of this transaction, such as the transaction amount, the time when the transaction request is received from the mobile device 10 , and so on. Accordingly, if the transaction request received by the bank server 20 is a proposed transaction request stolen by a malicious person, the bank server 20 can save the abnormal record for future access, and the bank server 20 can also output the abnormal record to The bank's terminal device can notify the bank clerk, or output the abnormal record to the inspection unit for notification.

Please continue to refer to step S601b. When the bank server 20 judges that the verification message matches the encoded message and the transaction amount does not reach the abnormal amount, the bank server 20 executes step S603b: judging that the verification message and the transaction amount pass the verification procedure.

That is, when the verification message matches the encoded message, and the transaction amount does not reach the abnormal amount, it means that the bank server 20 judges that the transaction request it receives is an executable transaction request, so the bank server 20 can perform the transaction as shown in Figure 2. Step S70.

To sum up, according to the transaction verification system and method with interruptible connection shown in one or more embodiments of the present invention, the mobile device and the bank server can interactively determine each other's legitimacy, so as to avoid information security loopholes. In addition, according to the transaction verification system and method that can interrupt the connection shown in one or more embodiments of the present invention, it is also possible for the mobile device and the bank server to discover in time whether the message is being intercepted or attacked by a man-in-the-middle , and implement the countermeasure accordingly, and can avoid the risk of the user mistakenly inputting the verification information into the phishing website when receiving the message.

Although the present invention is disclosed by the aforementioned embodiments, they are not intended to limit the present invention. Without departing from the spirit and scope of the present invention, all changes and modifications are within the scope of patent protection of the present invention. For the scope of protection defined by the present invention, please refer to the appended scope of patent application.

10:Mobile device 20: Bank server

FIG. 1 is a block diagram of a transaction verification system that can interrupt connections according to an embodiment of the present invention. FIG. 2 is a flowchart of a transaction verification method that can interrupt a connection according to an embodiment of the present invention. FIG. 3 is a detailed flowchart of step S40 shown in FIG. 2 . FIG. 4 is a flowchart of a verification procedure according to an embodiment of the present invention. FIG. 5 is a flowchart of a verification procedure according to another embodiment of the present invention.

10:Mobile device

20: Bank server

Claims (8)

A transaction verification system with interruptible connection, comprising: a bank server, used to randomly generate and output a coded message when receiving a transaction request; and a mobile device, connected to the bank server, the mobile device has a The user interface is used to receive a transaction instruction, and output the transaction request to the bank server when receiving the transaction instruction, the mobile device receives the coded message, and generates a verification message according to the coded message, and the mobile device will further The verification message is input into a verification field of the user interface, so as to output the verification message to the bank server through the user interface, wherein the bank server further executes based on the verification message after receiving the verification message a verification procedure, the bank server executes the transaction request when the verification message passes the verification procedure, wherein the coded message includes a keyword associated with the transaction request and a verification code, the keyword includes a transfer-out account , a transaction amount and a transaction type, the mobile device further determines whether the keyword is a part of the transaction request, and the mobile device decodes the verification code when judging that the keyword is a part of the transaction request is a verification string, and using the verification string as the verification message, when the mobile device determines that the keyword is not a part of the transaction request, it terminates the connection between the user interface and the bank server. The transaction verification system with interruptible connection as described in claim item 1, wherein the transaction request includes a transaction amount, and the bank server executes the verification procedure including: the bank server judges whether the verification message conforms to the coded message, and the Whether the transaction amount does not reach an abnormal amount, the bank server judges that the verification message has passed the verification program when it judges that the verification message matches the coded message and the transaction amount does not reach the abnormal amount, wherein the abnormal amount is a normal The transaction amount plus an abnormal amount. The transaction verification system that can interrupt the connection as described in claim 2, wherein the bank server executes the verification program further includes: when the bank server judges that the transaction amount reaches the abnormal amount, the bank server generates an association with the An abnormal record of the transaction amount is stored in a bank database. The transaction verification system that can interrupt the connection as described in claim 1, wherein the bank server executes the verification program includes: the bank server judges whether the verification character string corresponds to the verification code, and the bank server determines whether the verification When the character string corresponds to the verification code, it is judged that the verification message passes the verification procedure. A transaction verification method capable of interrupting connection, comprising: receiving a transaction instruction with a user interface of a mobile device; outputting a transaction request to a bank server when the mobile device receives the transaction instruction; using the bank server When receiving the transaction request, the device randomly generates and outputs a coded message to the mobile device; generates a verification message based on the coded message with the mobile device; inputs the verification message into the user interface for verification with the mobile device field, so as to output the verification message to the bank server through the user interface; use the bank server to execute a verification process based on the verification message; and when the verification message passes the verification process, use the bank server Execute the transaction request, wherein the coded message includes a keyword associated with the transaction request and a verification code, the keyword includes a transfer-out account, a transaction amount and a transaction type, generated by the mobile device according to the coded message The verification message is: use the mobile device to determine whether the keyword is a part of the transaction request; when the mobile device determines that the keyword is a part of the transaction request, use the mobile device to decode the verification code is a verification string, and uses the verification string as the verification message; and when the mobile device determines that the keyword is not part of the transaction request, the mobile device interrupts the user interface and the bank server device connection. The transaction verification method with interruptible connection as described in claim item 5, wherein the transaction request includes a transaction amount, and executing the verification procedure with the bank server includes: judging whether the verification message matches the coded message with the bank server, And whether the transaction amount has not reached an abnormal amount, wherein the abnormal amount is a normal transaction amount plus an abnormal amount; When the amount is abnormal, the bank server judges that the transaction request passes the verification procedure. The connection-interruptible transaction verification method as described in Claim 6, wherein executing the verification program with the bank server further includes: when the transaction amount reaches the abnormal amount, use the bank server to generate an error message associated with the transaction amount an exception record, and store the exception record in a bank database. The transaction verification method with interruptible connection as described in claim 5, wherein executing the verification program with the bank server includes: judging whether the verification string corresponds to the verification code with the bank server; and when using the bank server When the server judges that the verification character string corresponds to the verification code, and the verification message matches the coded message, the bank server judges that the transaction request passes the verification procedure.

Images