TWM530440U - Transaction confirmation system - Google Patents

Abstract

A transaction confirmation system includes a first computing device and a second computing device. The first computing device receives a first transaction request and to determine whether the first transaction request passes a transaction confirmation process. The second computing device generates a transaction message when the first computing device determines that the first transaction request passes the transaction confirmation process and to send the transaction message to the first computing device. The transaction message includes a transaction information link. The first computing device sends the transaction message to a first mobile device. The first mobile device sends the transaction message to a second mobile device. The second mobile device sends receiver information to the first computing device according to the transaction message. The first computing device sends the receiver information to the computing device to execute a first transaction action.

Description

Transaction authentication system

The present disclosure is a transaction authentication technique and, in particular, a transaction authentication system.

In the current trading model, in general, the transaction payee's account number is one of the indispensable information for the execution of the transaction. Once the payee's account number is unknown, the transaction is difficult to complete successfully. The above situation not only limits the flexibility of the transaction, but also is one of the difficult problems to overcome for certain transactions that are worthwhile.

The present disclosure is directed to a transaction authentication system that includes a first computer device and a second computer device. The first computer device is configured to receive the first transaction request and determine whether the first transaction request passes the transaction authentication procedure. The second computer device is configured to generate a transaction message and transmit the message to the first computer device when the first computer device determines that the first transaction request passes the transaction authentication program. The transaction message contains a link to the transaction data. The first computer device is further configured to transmit the transaction message to the first mobile device. The first mobile device transmits the transaction message to the second mobile device. The second mobile device transmits the payment information to the first computer device according to the transaction message. The first computer device is further configured to transmit the payment data to the second computer device to perform the first transaction action.

In summary, even if the payer does not know the information about the payee account, the disclosure may transmit the transaction request through the transaction authentication program to the payee in the form of a transaction message, and the computer device inputs the receipt to the payee. The transaction action can be executed after the data is saved. Therefore, it not only enhances the convenience of the transaction, but also considers the security of the transaction.

The above description will be described in detail in the following embodiments, and further explanation of the technical solutions of the present disclosure is provided.

The following disclosure provides many different embodiments or illustrations for implementing the features of the present disclosure. The disclosure may repeatedly recite numerical symbols and/or letters in the various examples, which are for simplicity and elaboration, and do not in themselves specify the relationship between the various embodiments and/or configurations in the following discussion.

In the scope of the embodiments and claims, "one" and "the" may mean a single or plural unless the context specifically dictates the articles. It will be further understood that the terms "comprising", "comprising", "comprising", and "the" One or more of its other features, regions, integers, steps, operations, elements, components, and/or groups thereof.

As used herein, "about", "about" or "approximately" is generally within an error or range of about 20% of the index value, preferably within about 10%, and more preferably It is about five percent. Unless otherwise stated, the numerical values referred to are regarded as approximations, that is, the errors or ranges indicated by "about", "about" or "approximately".

Please refer to Figure 1. 1 is a schematic diagram of a transaction authentication system 100 in accordance with an embodiment of the present disclosure. Transaction authentication system 100 includes computer device 110 and computer device 120. It should be noted that the computer devices 110, 120 can be implemented as one or more servers.

For convenience of description, the embodiments are described below through a specific type of transaction, but the disclosure is not limited thereto.

In a usage scenario, the payer wants to pay a sum to the payee, but the payer does not know the information about the payee's account (such as the payee's bank account number). The payer can operate the mobile device 130 (e.g., mobile phone, tablet) to generate a first transaction request (e.g., a payment request). For example, the payer can input the amount to be paid to the payee through the mobile device 130 to generate a first transaction request. Next, the mobile device 130 transmits a first transaction request to the computer device 110. The computer device 110 is configured to receive the first transaction request and determine whether the first transaction request passes the transaction authentication procedure.

Specifically, when the computer device 110 determines that the identification message of the mobile device 130 coincides with the preset identification message recorded by the mobile device 130, and receives the confirmation message transmitted by the payer through the mobile device 130 (ie, the payer confirms that the first operation will be performed through the mobile device 130) At the time of the transaction request, the computer device 110 determines that the first transaction request passes the transaction authentication procedure.

Regarding the above-mentioned preset identification message, when the payer executes the first application to log in to the personal identity account through the mobile device 130 (for example, by entering the identity card number) and receives the initial activation code (for example, the user application or the online banking application) The first application captures the identification message of the mobile device 130 and transmits it to the computer device 110 (eg, the first application server). The computer device 110 is further configured to record the identification message of the mobile device 130 as the preset identification message, and establish a correspondence between the payer's personal identity account and the mobile device 130 to identify the message (ie, bind the payer's personal identity account and action). Device 130).

Since the payer can only confirm the execution of the transaction request through the mobile device 130 in which the computer device 110 has established the corresponding relationship, the convenience and security of the transaction are simultaneously improved.

When computer device 110 determines that the first transaction request passes the transaction authentication procedure, computer device 120 (e.g., a bank server) generates the transaction message and transmits it to computer device 110. The computer device 110 is further configured to transmit a transaction message to the payer's mobile device 130. Thus, the payor can operate the mobile device 130 to transmit the transaction message to the payee's mobile device 140 (e.g., via the social software within the mobile device 130), thereby informing the payee of the message of the payment transaction. The payee operable mobile device 140 transmits the payment information (e.g., the payee's bank account information) to the computer device 110 based on the transaction message. The computer device 110 is further configured to transmit the payment information to the computer device 120 to perform a first transaction action (eg, a payment action) corresponding to the first transaction request (eg, a payment request). It should be noted that the transaction information includes a transaction data link, and the payee can select the transaction data link through the mobile device 140 to display the user interface to input the payment data and transmit the data to the computer device 110. In addition, in the case that the payment account input by the payee and the payment account of the payer belong to different banks, the computer device 120 (for example, the bank server to which the payer account belongs) is used to transmit the related information of the first transaction action. To the computer device 150 (eg, the bank server to which the payee account belongs) to complete the first transaction action.

In this way, even if the payer does not know the information about the payee account, the first transaction request (eg, payment request) through the transaction authentication program can be transmitted to the payee in the form of a transaction message, and the computer device 120 After the payee enters the payment information, the first transaction action (for example, completing the payment action) can be performed. This disclosure not only enhances the convenience of the transaction, but also takes into account transaction security.

In one embodiment, the mobile device 130 executes the identity authentication process of the first application before the payer operates the mobile device 130 to transmit the confirmation message to the computer device 110. For example, the payer needs to execute the first application by entering the correct graphic, digital combination, biometric (eg, fingerprint) to confirm whether to execute the transaction request. It should be noted that the payer can set or change the identity authentication procedure, that is, set or change the graphics, digital combination, biometric identification (such as fingerprints of other fingers), and the disclosure is not limited thereto.

In an embodiment, different users can operate the same mobile device 130 to log in to different personal identity accounts through the first application, and the computer device 110 is further configured to establish a correspondence between the same mobile device 130 and different personal identity accounts. That is, the same mobile device is bound to different users). In addition, the computer device 110 can also be used to cancel the correspondence between the personal identity account of one or more users and the mobile device 130 to identify the message (ie, cancel the binding relationship between the mobile device 130 and one or more users).

In one embodiment, the user can change the bound mobile device 130. The user can operate the mobile device 130 to execute the first application to generate the replacement activation code, and then the user operates another mobile device (not shown) to execute the first application to log in to the user's personal identity account and input the activation activation code. The first application retrieves the identification message of the other mobile device and transmits it to the computer device 110. The computer device 110 is further configured to record the identification message of the other mobile device as a preset identification message, and establish a correspondence between the user's personal identity account and the identification message of the other mobile device (ie, the user binds another Mobile device).

In one embodiment, the computer device 110 is further configured to provide a user interface (such as a web interface or a second application interface), and the payee's mobile device 140 is further configured to display a user interface through a transaction data link (eg, The web interface or the second application interface allows the payee to enter the payment information for transmission to the computer device 110 and to transmit the payment data to the computer device 110 (eg, a web server or a second application server). Next, computer device 110 transmits the payment information to computer device 120 (eg, a bank server) to execute the transaction.

Alternatively, in another usage scenario, the payor wants to transfer the money to the payee, and the payer knows the payee's transfer account number. The payer can generate a second transaction request via a web page (eg, an online bank) or an application (eg, a mobile bank). The computer device 110 (such as a web server or an application server) is further configured to receive the second transaction request and determine whether the second transaction request passes the transaction authentication program. When the computer device 110 determines that the second transaction request passes the transaction authentication procedure, the computer device 120 (eg, the bank server) is further configured to perform a corresponding second transaction action (eg, a transfer action). The transaction certification process is as described above and will not be repeated here.

Similarly, in the case where the payee account input by the payee and the payer's payment account belong to different banks, the computer device 120 (for example, the bank server to which the payer account belongs) is more used to transmit the first transaction action. The message is sent to the computer device 150 (e.g., the bank server to which the payee account belongs) to complete the second transaction action.

In an embodiment, after the transaction action is completed, the computer device 110 is further configured to transmit the transaction completion message to the payer's mobile device 130, so the payer can transmit the transaction completion message to the object to be notified (eg, through the mobile device 130). Within the community software), the notified object can quickly know the transaction details without having to go through complicated query actions.

In summary, even if the payer does not know the information about the payee account, the present disclosure can transmit the transaction request through the transaction authentication program to the payee in the form of a transaction message, and the computer device 120 inputs the payee. The transaction action can be executed after the payment information is received. Therefore, it not only enhances the convenience of the transaction, but also considers the security of the transaction.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present case. Anyone skilled in the art can make various changes and refinements without departing from the spirit and scope of the case. Therefore, the scope of protection of this case is considered. The scope defined in the patent application is subject to change.

The above and other objects, features, advantages and embodiments of the present disclosure will become more apparent and understood.
100‧‧‧Transaction Certification System
110‧‧‧Computer equipment
120‧‧‧Computer equipment
130‧‧‧Mobile devices
140‧‧‧Mobile devices
150‧‧‧Computer equipment

The above and other objects, features, advantages and embodiments of the present disclosure will become more apparent and understood.

100‧‧‧Transaction Certification System

110‧‧‧Computer equipment

120‧‧‧Computer equipment

130‧‧‧Mobile devices

140‧‧‧Mobile devices

150‧‧‧Computer equipment

Claims (10)

A transaction authentication system, comprising: a first computer device for receiving a first transaction request and determining whether the first transaction request passes a transaction authentication program; and a second computer device for using the first computer device When the first transaction request is passed through the transaction authentication process, a transaction message is generated and transmitted to the first computer device, wherein the transaction message includes a transaction data link; wherein the first computer device is further configured to transmit the transaction message to a first mobile device that transmits the transaction message to a second mobile device, the second mobile device transmitting a payment data to the first computer device according to the transaction message, the first computer device further Transmitting the receipt data to the second computer device to perform a first transaction action. The transaction authentication system of claim 1, wherein the first application captures one of the first mobile devices when the first mobile device executes a first application to log in to a personal identity account and receives a first activation code. The first identification message is transmitted to the first computer device, and the first computer device is further configured to record the first identification message as a preset identification message and establish a correspondence between the personal identity account and the identification message. The transaction authentication system of claim 2, wherein the first computer device is further configured to determine the first when determining that the identification message is consistent with the preset identification message and receiving the confirmation message transmitted by the first mobile device The transaction request passes the transaction certification process. The transaction authentication system of claim 3, wherein the first mobile device performs the identity authentication procedure of the first application before the confirmation message is transmitted by the first mobile device. The transaction authentication system of claim 2, wherein when the third mobile device executes the first application to log in to the personal identity account and receives a change activation code, the first application captures the third mobile device And transmitting, by the first computer device, the second identification message to the preset identification message, and establishing the personal identity account corresponding to the second identification message. a relationship, wherein the first mobile device generates the change activation code. The transaction authentication system of claim 2, wherein the first computer device is further configured to cancel the correspondence between the personal identity account and the identification message. The transaction authentication system of claim 1, wherein the first computer device is further configured to provide a user interface, and the second mobile device displays the user interface according to the transaction message to transmit the receipt data to the first Computer device. The transaction authentication system of claim 7, wherein the user interface is a web interface or a second application interface, and the second mobile device is further configured to display the web interface or the corresponding webpage through the transaction data link. Two application interface. The transaction authentication system of claim 1, wherein the first computer device is further configured to receive a second transaction request and determine whether the second transaction request passes the transaction authentication procedure, and the second computer device is further configured to When the first computer device determines that the second transaction request passes the transaction authentication program, it performs a second transaction action. The transaction authentication system of claim 9, wherein the first computer device is further configured to transmit a transaction completion message to the first mobile device.